Too many bugs

Unanswered Question
Aug 9th, 2007


When looking for an IOS for a router, how many bugs are considered to be too buggy? How do you determine which IOS to pick?



I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Edison Ortiz Thu, 08/09/2007 - 07:44

When looking for an IOS, first you select the IOS that has the features you need.

Second, you examine if the bugs listed against this IOS will affect your network. For instance, if you are planning to run IPSec and there is a bug listed against the IPSec service where the router would crash under heavy load, then you need to determine if it's worth the risk. You need to investigate if there is another IOS release that has addressed that bug while keeping the features you need.

Other bugs are not as critical and you can have a functional network with an IOS that has listed bugs. Really hard to find an IOS that is bug free.


sundar.palaniappan Thu, 08/09/2007 - 07:58

When choosing IOS if possible go with GD (General Deployment) code as it's considered more stable code.

Instead if you have to choose an ED (Early Deployment) release, that inherently may contain some bugs, then review the release notes for the release of software that you want to use and that would show most/all caveats in that particular release. If the bugs in the release notes aren't something that doesn't either affect your situation or if it isn't of a severe nature you may want to go with that release.

Typically any code with extremely high amount of known bugs Cisco would pull them off the software download page.




This Discussion