Unsolved
This post is more than 5 years old
5 Practitioner
•
274.2K Posts
1
4245
Problem with new release CX5-Bundle-05.32.000.5.201
During upgrade 05.31.000.5.709 to the last release 05.32.000.5.201 the script stopped in 4 step "Running check scripts" without being able to move forward......i m doing the upgrade with release 05.32.000.5.015........without problem
diardobj
12 Posts
0
February 28th, 2013 13:00
The jump from r31 to r32 introduces a script that checks for certain error conditions. There are certain instances where a pre-scan needs to be initiated to clear the condition prior to the upgrade. Right now, tech support will have to be contacted for the specific work-around.
Potential related Primus article(s): emc306064
GearoidG
251 Posts
0
February 28th, 2013 16:00
If you are upgrading from Rel 31 to Rel 32 there is a check script that checks if your array was ever vulnerable to ETA
emc308955. Emc306064 is the the recovery method that Support should follow if you are upgrading from Rel 31. Support need to verify if this applies or not. Not doing these checks can result in having an outage
Regards
Gearoid
diardobj
12 Posts
0
February 28th, 2013 17:00
Thank you for clarifying Gearoid!
eddynav
17 Posts
0
April 1st, 2013 07:00
If the SMLink_check script indicates that pools were created under "susceptible code" and emc306064 needs to be followed, does that mean that the upgrade from 31 to 32 will require an outage or can it still be done non-disruptively?
diardobj
12 Posts
0
April 25th, 2013 08:00
That is dependent on the actual state of the devices that were created with the susceptible code. Did the check provide any further information?