Unsolved
This post is more than 5 years old
1 Rookie
•
119 Posts
0
5308
June 15th, 2016 02:00
VMAX Enginuity/Microcode Update
Hello,
Can any one please refer to any documents or links that will show step by step Updating Enginuity version on VMAX?
Thanks,
0 events found
No Events found!


Ugin
1 Rookie
•
122 Posts
1
June 15th, 2016 02:00
The steps are simple, but you need to engage field team to do that or contact RCM team.
Is it in family or out of family upgrade?
All patch installations are done by EMC Customer Service rep.
Primus ID
Change Type
Description
emc277902
Enginuity Changes
ETA emc277902: After an upgrade from Enginuity 5874 to 5875or an in-family 5875 upgrade, SRDF with Dynamic Flow Control can exhibit SRDF performance degradation
emc280103
InterFamily Enginuity Upgrade
emc280103: TimeFinder Clone copies become slow after a Non Disruptive Upgrade (NDU) from 5874 to 5875. Any high QOS value can affect the clone copy after an NDU.
emc278020
InterFamily Enginuity Upgrade
emc278020: Symmetrix VMAX: ORS Activate or Terminate fails. The customer workaround for this issue is to run ORS without precopy
emc270405
InterFamily Enginuity Upgrade
emc270405: Backup procedure for GNS before NDU from 5874 to 5875.
emc201214
InterFamily Enginuity Upgrade
emc201214: Enginuity 5875 requires a minimum version of Solutions Enabler 7.2.
Reference emc267712 for what version of EMC mainframe software products are required for Enginuity 5875.
emc254662
InterFamily Enginuity Upgrade
emc254662: Symmetrix VMAX: 5875: SymmWin Hint 40004910: A bay location is missing or improperly configured for bay xx. It will now be required to fill in the floor/tile bay location for all bays and whether the bay is a separated/dispersed bay.
emc261084
All Changes
ETA emc261084: Symmetrix VMAX, SE, and SMC:Performing modifications using SMC with SE 7.2 to a recently renamed SG, IG, or PG, may cause masking inconsistencies
emc220390
Director Changes, InterFamily Enginuity Upgrade, System Changes, Vols Assignment Change
ETA emc220390: Symmetrix 8000, DMX, and V-Max Series: Cluster environments that require setting the PER bit and have a single HBA configured to both the A and B port of an FA have not been qualified and could experience validation or failover issues.
The workaround is to change the configuration to have the HBA connected to different FA director ports (e.g., FA-5A a and FA-5B a).
emc177492
All Changes
TSA emc177492: Symmetrix DMX: EMC's recommended setting for the Cache Fast Write Flag in the Symmetrix at Enginuity 5x71
Fix: Fix 31584 released in Enginuity Level 5771.104.114.
Refer to EMC knowledgebase article emc129402 for additional information.
emc194364
InterFamily Enginuity Upgrade, Enginuity Changes, System Changes
ETA: Celerra bug: Symmetrix interfamily and in-family NDU upgrades may cause attached Celerra systems to panic. Celerra will lose all paths connecting to the Symmetrix. Even though all the paths and devices on the Symmetrix will come back up in approximately 15 seconds, it may take Celerra longer to recover completely from this event. Fixed with Celerra patch version 5.5.35.100 and 5.6.38.203. In the patch, the tolerated timeout
SunshineM
1 Rookie
•
119 Posts
0
June 15th, 2016 03:00
thanks for the info, but I am looking for those steps to upgrade. If anyone can provide me. I want to try it in our lab.
Ugin
1 Rookie
•
122 Posts
0
June 15th, 2016 03:00
There are lot of steps involved to check pre & post upgrade, to make it simple i can say install the exe file(target code) in your SP and run the Code Load Procedures.
As this forum can be viewed by all audience, i cannot share the detailed steps here.
Upgrade procedure is restricted to internal audience only.
Ugin
1 Rookie
•
122 Posts
0
June 15th, 2016 04:00
That's why i mentioned, its restricted. Only Field team / RCM team will do the upgrade (EMC personnel).
Though the steps are simple, there are lot more things to check pre and post upgrade.
If you need more details, please check with your local EMC team.
SunshineM
1 Rookie
•
119 Posts
0
June 15th, 2016 04:00
I have access to SolveDesktop, but cannot find this procedure.