This post is more than 5 years old
6 Operator
•
5.7K Posts
0
3003
December 4th, 2008 04:00
MDS reboot after 497 days uptime
Hey guys,
I just read an important article on the Cisco website about a flaw in some SAN-OS's. Read it on http://www.cisco.com/en/US/ts/fn/631/fn63178.html
The most current SAN-OS EMC recommends is only 3.3 (1c) and this issue is according to Cisco solved in SAN-OS version 3.3(2) and up as well as NX-OS 4.1 (1b) and up.
I have most switches upgraded to 3.3(1c) now, but still this worries me. does anyone know when EMC releases newer versions ?
I just read an important article on the Cisco website about a flaw in some SAN-OS's. Read it on http://www.cisco.com/en/US/ts/fn/631/fn63178.html
The most current SAN-OS EMC recommends is only 3.3 (1c) and this issue is according to Cisco solved in SAN-OS version 3.3(2) and up as well as NX-OS 4.1 (1b) and up.
I have most switches upgraded to 3.3(1c) now, but still this worries me. does anyone know when EMC releases newer versions ?
No Events found!


ConnectrixHelpe
259 Posts
0
December 4th, 2008 09:00
EMC and Cisco are in constant contact in regards to any issues that are found and any field notice they may release. EMC released ETA emc199417 along with Cisco's Field Notice on the issue. The issue is resolved in both 4.1(1b) and 3.3(2) code. NX-OS 4.1(1b) is EMC GA and 3.3(2) is available via RPQ as it is still in testing at EMC. An RPQ is a process that EMC extends support to code before it is generally released. You can contact your local EMC support representative to inquire about an RPQ. Your local EMC support representative can also inform you when EMC plans to release 3.3(2) officially. As it is a future release I am unable to post that information on this board.
Also just as some background, the reason for the delay in EMC support of MDS code after Cisco GA's it, is our additional testing. Multiple groups at EMC perform weeks of testing on the code after it is received from Cisco. EMC works to ensure that the code will work with all approved solutions and that serviceability requirements are met. We work with Cisco to find any issues and if necessary get new versions of code that resolve any found issues. This additional testing and documentation takes time and creates the difference in release dates for Cisco versus EMC.
Thank you.
dynamox
11 Legend
•
20.4K Posts
•
87.4K Points
0
December 4th, 2008 04:00
AranH1
2.2K Posts
0
December 4th, 2008 08:00
.... time to schedule a reboot.
AranH1
2.2K Posts
0
December 4th, 2008 09:00
Thanks for chiming in here. I do appreciate the additional testing that EMC performs on the MDS code before releasing it as GA. I think EMC does more interoperability testing across it's entire product line than any other vendor I have worked with and supports a large range of configurations. But the flip side is the time it takes to have releases available for the end users. An understandable delay, but a delay nonetheless.
dynamox
11 Legend
•
20.4K Posts
•
87.4K Points
0
December 4th, 2008 13:00
RRR
6 Operator
•
5.7K Posts
0
December 4th, 2008 13:00
dynamox
11 Legend
•
20.4K Posts
•
87.4K Points
0
December 4th, 2008 13:00
RRR
6 Operator
•
5.7K Posts
0
December 4th, 2008 13:00
ConnectrixHelpe
259 Posts
0
December 4th, 2008 13:00
Thank you.
RRR
6 Operator
•
5.7K Posts
0
December 4th, 2008 13:00
RRR
6 Operator
•
5.7K Posts
0
December 4th, 2008 14:00
dynamox
11 Legend
•
20.4K Posts
•
87.4K Points
0
December 4th, 2008 14:00
AranH1
2.2K Posts
0
December 4th, 2008 14:00
RRR
6 Operator
•
5.7K Posts
0
December 4th, 2008 14:00
I've done this tons of times and never had FC downtime ! Attached HBA's don't know about the switch being upgraded
RRR
6 Operator
•
5.7K Posts
0
December 4th, 2008 14:00
I know for a fact that upgrades for the 9124, 9134 and 9222i are nondisruptive for FC traffic.