MDS 9222i Code Upgrade

sure, just add your components (swithces/arrays/host/powerpath) to E-Lab navigator and it will tell you where you need to be code/firmware/version wise.



not a huge player compared to Brocade/Cisco ..but they do have nice switches.

i've had good experiences with both vendors, Cisco does have a lot of bells and whistles though.

True reboot as in: ethernet down as well as FC down ! Just like you switched of the entire switch and put it back on. I meant downtime on that switch !

For the rest all upgrades were true NDU !!! Very good !

I say B-R-O-C-A-D-E for president !!!! Cisco has way too much bells and whistles. In the FCoE field however Cisco seems to be a major player, but in FC I think Brocade is the winner.

Hey RRR.

Did the reboot happen right away?

Must be user error J/K

I assume the ones that did not reload, the counter is still incrementing and past 497 at this point? I think you talked me into it, NDU all the way.

It's kinda like hotswap memory chips on servers, who would really want to do that...!

Thx

Good question ! I must say that I never stayed around at the customer's site to see if the counter actually now goes over 497 I think my boss would kill me. I have other thnigs to do than watch counters

I see, so you are a CE or a consultant of sorts? Well, if they didn't call you I'm sure things are good.

Thx

Consultant, working for an EMC ASN partner.

Well, I had a very fun day last week upgrading my switches to NX code. Let me tell you something, it was not NDU (I did have to reload).

Turns out the install script was unable to install erroring out with a 0 or 1 return code. After working with the local CE and a level 1 guy on the phone, they were lost! The guy on the phone was typing the same command over and over believing it will run at some point, not.

The call was escalated and got a more SR level guy. He seen this issue before and told us that the current code is hooked to a SSI module that is not even in my system, see below for a "show mod":

Mod Application Image Description Application Image Version
-------- ----------------------------- -------------------------
1 SSI linecard image (Packaged in SAN-OS) 3.3(1c)

I was told reloading the switch will clear this issue, which it did. We then proceeded with the install.

Second switch did the same thing BUT the module was still there, what joy. After about an hr I suggested to try the install anyways and it actually worked! If you did a show mod after the upgrade, the SSI mod was no longer there. Come on, seriously...!

The Sr level tech stated he has seen this many time before. I wish I had this information to begin with. Although the reload did not cause any issues since all but one host is dual connected, I was not ready for this.

Looking at my prod switches, I have the same SSI modules, which means I will prepare for a reload as well.

What is interesting is that these set of switches are in different locations and appear to have the same issue. This tells me it's more of a bug, and not a previous upgrade issue from a CE (loading code for something I don't have).

Hey dynomox, put in reload for your change control

Did you read the release notes ? For some linecards the upgrade isn't NDU indeed !!

Furthermore: if you upgrade from a somewhat older SAN-OS, you might have to upgrade to an intermediate SAN-OS before upgrading to NX-OS 4.1(3a) or something.
The release notes provide further information on specific configurations such as modular switches with older linecards.

Based on what he wrote though, the problem is that he doesn't have that linecard in the switch. So the upgrade the current code he was on was erroneously reporting that there was a SSM lincard in the switch.

Oops, where was I, what was I thinking..... I was fast browsing through the message and only noticed "...line card...". Excuse me. I must have been asleep or something.