ironcheflouie

updated

17 years ago

0

2485

September 28th, 2009 12:00

MDS 9222i Code Upgrade

Hi All. It has been a long time since my last post...!

I am in the process of upgrading my MDS 9222i switches from 3.3(1c) to probably NX 413a (prob a "period" in there somewhere but not sure where :-).

The existing code has been very good with the exception of the well known 497 day reload, which is the only reason why I am upgrading.

1. Who has done an upgrade similar to mine (HW, existing and target code, etc)?

2. Any issues with a NDU upgrade? My gut tells me to reload (warm and fuzzy feeling to see the uptime reset to zero) after any type of upgrade but if it is truly safe then maybe I will not.


Thanks guys!
  • RRR

    6 Operator

    •

    5739 Posts

    690

    0

    Posted October 1st, 2009 02:00

    During the upgrade, so no real problem there ;) But still unexpected..... And I must say, it happened to me only once on a Cisco switch, so I wouldn't worry too much about this. All the other upgrades were true NDU's, so FC kept on going as it should.
  • RRR

    6 Operator

    •

    5739 Posts

    959

    0

    Posted September 29th, 2009 02:00

    We've done upgrades of 9124, 9124e, 9134 and 9222i and I think of the 30+ switches 1 suffered from a true reboot (9124 from SAN-OS 3.3.1c to NX-OS 4.1(1c)).

    Until august this year our target code was 4.1(1c), but now it's 4.1(3a). The 497 day bug was the main reason that we informed all of our customers to have their firmwares upgraded to 3.3.2 or (our advice) NX-OS 4.1(1c). We've been busy working on this upgrade since december last year.
  • dynamox

    11 Legend

    •

    20419 Posts

    •

    87439 Points

    813

    0

    Posted September 29th, 2009 06:00

    i am going to 4.1.1b from 3.2.(3a) on October 17 ..will let you know how it goes :)
  • RRR

    6 Operator

    •

    5739 Posts

    813

    0

    Posted September 29th, 2009 07:00

    Sure. You should be ok as long as you have 2 fabrics.
    After you've done, you know the drill. But read the release notes as in some upgrades you first need to upgrade to a version inbetween the start and end firmware level !
  • 813

    0

    Posted September 29th, 2009 08:00

    Thanks for the response dynamox.

    It will be close, I will be around that time too :-). This is DR so not too worried. Prod will come 30 days later. Please let me know how it goes as well.

    Do you plan to reload the switches?

    Is there a reason why you are going with 4.1.1b and not 4.1.3a (1 rev back??)
  • 959

    0

    Posted September 29th, 2009 08:00

    Thanks for the response RRR.

    What does it mean by true reboot (497 bug)?

    Did you reload your switches manually after the upgrades or was it truly NDU?

    Since December, all I can say is wow!
  • dynamox

    11 Legend

    •

    20419 Posts

    •

    87439 Points

    813

    0

    Posted September 29th, 2009 09:00

    i am hoping it's an NDU upgrade, worth case scenario ..powerpath will take care of failover. I have to go to 4.1.1b because i have McData and Brocade in the same fabric and last i checked 4.1.3a was not listed in interoperability document.
  • 820

    0

    Posted September 29th, 2009 10:00

    Brocade, McData and Cisco? Someone must be studying for a cert :-)

    Or, enjoys complex environments.
  • 820

    0

    Posted September 29th, 2009 10:00

    You mean there is a place to check compatibility? ;-) I don't check, that is why I am posting.

    Is that a joke, did not know Qlogic plays in that space.
  • dynamox

    11 Legend

    •

    20419 Posts

    •

    87439 Points

    820

    0

    Posted September 29th, 2009 10:00

    don't mention it man, i just need to add Qlogic switches to the mix and i will be all set :)

    every time i need to make fabric changes, i am going crazy looking at e-lab/esm making sure everything is compatible.