This post is more than 5 years old
4 Posts
0
1421
Need Help: MDS9509 firmware upgrade
The firmware of our 4 MDS9509 switches is going to be upgraded from 2.1(2b) to 3.2(3a).
EMC proposed to upgrade 2.1(2b) to 3.0(2) first, and then from 3.0(2) to 3.2(3a). All of these are supposed to be finished in several hours.
As it is the first time for us to upgrade the switch firmware, could someone suggest what shall we pay attention to or what preparation work should be done before the upgrade?
I know this question sounds dumb but really need help....
Thank you very much!!
EMC proposed to upgrade 2.1(2b) to 3.0(2) first, and then from 3.0(2) to 3.2(3a). All of these are supposed to be finished in several hours.
As it is the first time for us to upgrade the switch firmware, could someone suggest what shall we pay attention to or what preparation work should be done before the upgrade?
I know this question sounds dumb but really need help....
Thank you very much!!
healyj
141 Posts
0
November 28th, 2017 06:00
Hi there,
In our effort s to clean up the forum, we came across your question / statement.
If the question / statement is still valid, not expired and you need an update please reach out again and we try to get it answered.
As for now we set it to “answered.”
Regards,
Jim
dynamox
2 Intern
2 Intern
•
20.4K Posts
0
May 30th, 2008 05:00
AranH1
2.2K Posts
0
May 30th, 2008 09:00
That being said, there have been a few notices from Cisco about problems with 9500 series upgrades, there were some issues with flash modules that I recall. EMC can check your switches to determine if these notices apply to your switches.
But EMC should ensure that there are also no incompatible components in your infrastructure. If they have not checked, ask them to prior to the upgrade.
bodnarg
385 Posts
0
June 2nd, 2008 06:00
Since all but 1 server were dual connected there was no harm other than a lot of powerpath error messages. There was an alert on the issue we had and it was on one of the earlier versions of 3.02 and I believe has been resolved in later releases.
Related note - checking compatability is critical as well. We did have a case where the combination of the initial Cisco code we had (can't recall exact version), Solutions Enabler, and AIX without a certain patch could result in syminq hanging and possibly crashing the host.
We ran across this after having a host with a syminq command that hung and luckily were able to get the correct patches and firmware installed prior to having issues.
But once again - both you and EMC need to do your homework before upgrading
fresaj
4 Posts
0
June 2nd, 2008 19:00
I am now checking the competency between the components.
Long way to go...
fresaj
4 Posts
0
June 2nd, 2008 19:00
I will have to check out all the known problems and confirm them with EMC...
It's my first time to arrange such task.. tough but I am learning many things!
fresaj
4 Posts
0
June 2nd, 2008 19:00
Actually, it's the first project I am in charge (!!!), it's pretty stressful...
especially when our servers are not all installed with powerpath... I am really worried...
AranH1
2.2K Posts
0
June 3rd, 2008 07:00
hersh1
197 Posts
0
July 14th, 2008 12:00
As far as your original question about things to do prior or doing the upgrade. Backup all the running configs is something we always do. If possible try this upgrade process on a test switch if you have one. In another thread the talk about the fact that the 3.2 code will not fit on the Generation 1 bootflash with the current release (so 3.0.2 kickstart.bin and sys.bin + 3.2 kickstart.bin and sys.bin). We had this problem also and left only the old kickstart in place during the upgrade. This should only be an issues with the Generation (SUP1) 1 supervisors, not enough space in the bootflash.
ConnectrixHelpe
259 Posts
0
July 14th, 2008 13:00
I don't have all the details on exactly what issue you ran into on the upgrade but it could possibly be the following.
ETA emc185406: MDS-9000 Switches: Under certain circumstances, Generation 1 modules may reload during a SAN-OS upgrade, due to Compact Flash unable to partition for new code.
These and other issues are documented in both Cisco's and EMC release notes and in our knowledgebases. Did you open a case with EMC on the issues you encountered?
Thank you.
hersh1
197 Posts
0
July 15th, 2008 06:00