IOS Management

Unanswered Question
May 29th, 2008

Looking for a methodology for the management of IOS's for CISCO gear, cant seem to find anything, cheers Glenn

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
gma_young Tue, 06/03/2008 - 21:16

Thanks, however I represent a customer and not a partner, so am not auhtorised to obtain the tool. I was after more of a methodology, I have spoken to a CISCO sales/systems engineer who tells me there is no methodology of such for Cisco. I am checking out the Safe Harbor/Golden bridge stuff as well as referencing the other info relating to IOS management on cisco.com, and I will write something which suites our organisation, cheers

Ryan Carretta Tue, 06/03/2008 - 22:10

I'm not sure what you mean when you ask about methodology.

There are many different variants of IOS for different products. For example, the latest code on routers is the 12.4 train, but for all switches (and some routers like the 7600) we are still pulling from 12.2 code.

As a general rule for 12.4, the mainline train should be the most stable. The 'T' train will have some new features that, while tested, may not yet be considered tried and true. The X train could be considered early adopter code.

For switches, I like to stick to the general rule that the higher the last number, the better as far as stability goes. So, I would venture a guess that 12.2(18)SXF14 has less bugs than 12.2(33)SXH2a. The EWA train on the 4k would follow the same pattern as compared to the SG train. That being said, there are often major enhancements between trains where some of the bigger bugs are fully ironed out instead of worked-around.

Safe harbor code should always at the very least be a good starting point for you, and the release notes will prove invaluable if you know what features you will be running ahead of time.

Actions

This Discussion