nanog mailing list archives
Re: Testing router code before deployment
From: Jared Mauch <jared () puck Nether net>
Date: Thu, 21 Nov 2002 15:06:13 -0500
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
-- Jared Mauch | pgp key available via finger from jared () puck nether net clue++; | http://puck.nether.net/~jared/ My statements are only mine.
Current thread:
- Testing router code before deployment Tom Holbrook (Nov 21)
- Re: Testing router code before deployment Petri Helenius (Nov 21)
- Re: Testing router code before deployment Jared Mauch (Nov 21)
- Re: Testing router code before deployment Petri Helenius (Nov 21)