Unsolved
This post is more than 5 years old
1 Rookie
•
35 Posts
0
1182
June 8th, 2011 00:00
why upgrade FOS 5.3.0d,6.0.0b,6.1.0C,6.2.0e,6.3.1a
We try to force Customer agree to upgrade FOS on the ED48000B FOS v5.3.0d to 6.3.1a by following reason .
1.right now currently FOS is v5.3.0d this code is EOSL.
2. as I know this code we have some problem on it .
such as some time FOS V5.3.0d CP master and CP stanby out of sync their themself. this situation may take risk . may be need to reboot CP stanby to resynce or if resynce not successfully we need to reboot master CP this activity may take risk to all host connect to SAN Switch .
3. they have more benefit from upgrade FOS version.
Upgrade FOS on ED-48000B to version 5.3.0d
Upgrade FOS on ED-48000B to version 6.0.0b
Upgrade FOS on ED-48000B to version 6.1.0c
Upgrade FOS on ED-48000B to version 6.2.0e
Upgrade FOS on ED-48000B to version 6.3.1a
from release note new code could support
1. 8 Gbs port speed.
2. support VSAN .
3. etc..
Customer would like to upgrade but they want very good reason why need to upgrade .
Ed Schulte
2 Intern
•
151 Posts
1
June 28th, 2011 09:00
Hi foundation,
Not sure if you had an answer already:
Besides all the other valid reasons, if the switches are running EOSL firmware, he is officially not able to get Vendor support anymore. In customer Support they are officially not allowed to escalate if there is a serious issue on the switch. The Connectivity engineers are only allowed to do their "best effort", and if the customer wants something extra or any other questions answered / fixed the first request will be, upgrade first then see if the problem is fixed.
So the customer is better of upgrading in a controlled fashion, to the EMC target code, then waiting for something to happen, and then need to upgrade in a "panic".
Regards,
Ed