One of my favourites was inserting and removing configuration commands and watching the alignment errors to run by or just a plain crash. Or if you make the mistake of playing with EIGRP, you'll see the boxen spit out scheduler related stuff. Pete Jared Mauch wrote:
Typically testing for (allegedly) fixed defects and historicial problems unique to ones environment is normal.
Depending on the level of detail of buglists, etc.. people also test to insure that there are no reintroduction of old bugs as well as counter bugs, snmp issues, etc..
- jared
On Thu, Nov 21, 2002 at 01:50:06PM -0500, Tom Holbrook wrote:
Just curious what testing protocol people use with router code (IOS or JunOS for example) when considering deployment of a new version. Obviously the deployment would be made incrementally, but I wonder if you do anything more than running it in a lab router for a couple of weeks before the initial deployment.
Thanks -Tom
__________________ Tom Holbrook Sr. Network Engineer Earthlink - Atlanta
'Safe?' said Mr. Beaver...'Who said anything about safe? 'Course he isn't safe. but he's good. He's the King, I tell you.' --The Lion, the Witch and the Wardrobe