Unsolved
This post is more than 5 years old
53 Posts
0
2781
VMAX code upgrade 5874 > 5875
Hi,
Old Code Level : 5874.248.194
- New Code Level : 5874.259.201
- Loading Epack Registered Build: 5874_259_0011_201_5002.zip ontop of Code Level : 5874.259.201
- GSPatch GS5874_1.0.0.12
Online InterFamily Code Upgrade from 5874 to 5875 with Epack Load.
- Old Code Level : 5874.259.201
- New Code Level : 5875.269.201
- Loading Epack Registered Build: 5875_269_0005_201_5005 ontop of Code Level : 5875.269.201.
Please advise...
Regards,
MAwais
MelbSteve
38 Posts
0
December 13th, 2012 13:00
Hi MAwais,
I assume the question is, are these the correct code levels?
The Enginuity levels look good however the Registered build for 5875 is not.
You should look up primus emc258136 which recommends Registered Build 5875_269/0006 / 5875_201/5003 although there is a new release 5875_269/0016 / 5875_201/5011 which would be better.
Steve
Rasmmacias
108 Posts
0
December 18th, 2012 01:00
Primus ID
Change Type
Description
emc277902
Enginuity Changes
ETA emc277902: After an upgrade from Enginuity 5874 to 5875 or 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 value is changed from 90 seconds to 240 seconds.
£