Docu82501 - VMAX3 Family With HYPERMAX OS 5977 Operating Environment ReadMe For HYPERMAX OS Service Packs Release Level 5977.952.892 PDF

HYPERMAX OS SERVICE Pack README
EMC VMAX3 Family and VMAX All Flash

with HYPERMAX OS 5977
Operating Environment
ReadMe for HYPERMAX OS Service Packs
Release Level 5977.952.892 ID# 6420
REV 04
June 8, 2017
This HYPERMAX OS Service Pack ReadMe contains specific information for Service
Pack 5977-952-892-6420.exe, HYPERMAX OS Pack registered build 5977_952/0120
and SymmWin registered build 5977_892/5028. Topics include:
ReadMe revision history......................................................................................... 2
Audience ................................................................................................................ 2
Installation............................................................................................................. 2
Service Pack release history .................................................................................. 3
Service Pack overview ........................................................................................... 7
Fixed problems ...................................................................................................... 8
Firmware Pack release history ............................................................................. 42
Manifest .............................................................................................................. 46
Troubleshooting and getting help......................................................................... 48
ReadMe revision history
ReadMe revision history

Table 1 presents the revision history of this document.
Table 1 ReadMe revision history
Revision Date Description
01 February 13, First release of EMC Proactive HYPERMAX OS Pack ReadMe

2017 containing specific information for 5977-952-892-6243.exe,
HYPERMAX OS Pack registered build 5977_952/0015 and SymmWin
registered build 5977_892/5009.
02 April 5, 2017 Second release of EMC Proactive HYPERMAX OS Pack ReadMe

containing specific information for 5977-952-892-6326.exe,
03 June 5, 2017 Third release of EMC Proactive HYPERMAX OS Pack ReadMe

containing specific information for 5977-952-892-6420.exe,
04 June 8, 2017 Corrected description of 94102.
Audience
This document is primarily intended for EMC customers but it can also be used by EMC
Customer Service personnel.
Note: The HYPERMAX OS Service Pack ReadMe document contains technical

information that requires the reader to have some primary knowledge of EMC hardware
and software products.
Installation
HYPERMAX OS release level 5977.952.892 is available for download from
https://support.EMC.com. Please note that the installation procedure can only be
performed by your local EMC representative.
Note: The HYPERMAX OS 5977 Service Pack contains the base and service pack code
(you do not have to install the base code before applying the service pack). This is
different to the 5876 Service Pack install, where you must install the base code before
applying the 5876 service pack code.
Manifest
The manifest file describes the level of each application included in the 5977 Service
Pack. Click the link below to view the manifest file:
Manifest on page 46
2 HYPERMAX OS Release Level 5977.952.892 Service Pack ReadMe

Service Pack release history

Table 2 presents the revision history of the HYPERMAX OS Service Packs for release
level 5977.952.892.
Note: The last HYPERMAX OS Service Pack listed in Table 2 is the most current pack
for release level 5977.952.892. This pack should be treated as a superset of all
previously released packs; that is, it contains all previously released fixes plus any new
or modified fixes. New fixes or OPTs in the Fix numbers/OPT numbers column are
highlighted in bold.
Table 2 HYPERMAX OS Service Pack revision history
HYPERMAX Service HYPERMAX OS SymmWin reg. Fix numbers/OPT Full Firmware

Released OS level Pack ID reg. build build numbers Pack file
02/13/17 5977.952.892 6243 5977_952/0015 5977_892/5009 20018683, 20018833, V.fw_pack_full_5

20018839, 20018848, 977_161207_18015
20018852, 20018867, 2.exe
87709, 89504, 91289,
91424, 91539, 91606,
91665, 91668, 91672,
91901, 91981, 92002,
92022, 92048, 92141,
92161, 92197, 92351,
92363, 92445, 92462,
92470, 92562, 92669,
92671, 92697, 92785,
92787, 93077
HYPERMAX OS Release Level 5977.952.892 Service Pack ReadMe 3

Table 2 HYPERMAX OS Service Pack revision history (continued)

04/05/17 5977.952.892 6326 5977_952/0056 5977_892/5020 20018683, 20018833, V.fw_pack_full_5

20018839, 20018848, 977_170325_0409
20018852, 20018867, 05
87709, 89504, 91289,
91424, 91539, 91606,
91665, 91668, 91672,
91901, 91981, 92002,
92022, 92048, 92141,
92161, 92197, 92351,
92363, 92445, 92462,
92470, 92562, 92669,
92671, 92697, 92785,
92787, 93077,
20018826, 20018847,
20018857, 20018870,
20018876, 20018877,
20018878,
20018880, 87844,
91088, 91553, 91621,
91695, 91861, 92095,
92219, 92295,
92303, 92436,
92502, 92518,
92523, 92556,
92593, 92616,
92632, 92687,
92704, 92749,
92812, 92867,
92898, 92964,
93200, 93203,
93223, 93275,
93289, 93303,
93425, 93437,
93451, 93491,
93508, 93622,
93882, 516505,
516741, 518525

Table 2 HYPERMAX OS Service Pack revision history (continued)

06/05/17 5977.952.892 6420 5977_952/0120 5977_892/5028 20018683, 20018833, V.fw_pack_full_5

20018848, 20018852, 977_170516_1345
20018867, 87709, 35.exe
89504, 91289, 91424,
91539, 91606, 91665,
91668, 91672, 91901,
91981, 92002, 92022,
92048, 92141, 92161,
92197, 92351, 92363,
92445, 92462, 92470,
92562, 92669, 92671,
92697, 92785, 92787,
93077, 20018826,
20018847, 20018857,
20018870, 20018876,
20018877, 20018878,
20018880, 87844,
91088, 91553, 91621,
91695, 91861, 92095,
92219, 92295, 92303,
92436, 92502, 92518,
92523, 92556, 92593,
92616, 92632, 92687,
92704, 92749, 92812,
92867, 92898, 92964,
93200, 93203, 93223,
93275, 93289, 93303,
93437, 93451, 93491,
93508, 93622, 93882,
516505, 516741,
518525, 86956,
90889, 91193, 91443,
91589, 91646, 91654,
91689, 92017, 92047,
92067, 92080,
92189, 92268,
92278, 92285,
92551, 92565,
92581, 92594, 92615,
92645, 92688,
92694, 92751,
92764, 92820,
92945, 93094,
93110, 93177, 93200,
93206, 93225,
93237, 93246,
93290, 93330,
93339, 93373,
93383, 93388,
93402, 93438,
93462, 93477,
93492, 93571,
93585, 93599,
93605, 93613,
93647, 93669,
93683, 93688,
93716, 93765,
93783, 93887,
93892, 93897,
93909, 93931,
93938, 94002,
94020, 94036,
94080, 94102, 94111,
94113, 94197, 94371,
94374, 94382,
94386, 94523*,
94611, 20018855,
20018882,
20018890**

* Fix 94523 in Service Pack #6420 replaces fix 93425

** Fix 20018890 in Service Pack #6420 replaces fix 20018839

Service Pack overview
Service Pack overview

EMC is dedicated to providing a solid support strategy for its customers by ensuring
they have the most up-to-date fixes and enhancements. HYPERMAX OS Service
Packs are a key part of this strategy as they provide important supplementary
information for each Service Release.
This ReadMe covers the HYPERMAX OS VMAX3 Family and the new All Flash
systems. For more information on these systems, see the product pages on
https://support.EMC.com.
Each HYPERMAX OS Service Pack also contains the latest Firmware Pack. The
Firmware Pack ReadMe can be downloaded from: https://support.EMC.com. For the
release history of the Firmware Packs, see Table 17 on page 42.
Two HYPERMAX OS Service Packs are released per code family: one at the target
level and one at the latest code level, with each pack consisting of a set of highly
recommended fixes.
The following information should be noted for each HYPERMAX OS Service Pack:
A new HYPERMAX OS Service Pack should be treated as a superset of all
previously released packs for that code family; that is, a new pack will contain all
previously released fixes plus any new or modified fixes.
If a fix is removed between HYPERMAX OS Service Packs, information will be
included on the fix that has been removed.
If a fix is updated between HYPERMAX OS Service Packs, information will be
included on the revision number of the fix.
All fixes released in an HYPERMAX OS Service Pack will be integrated into the
next Service Release of the code family.

Fixed problems
Fixed problems
This section highlights product issues that are fixed in this HYPERMAX OS Service
Pack. Product issues are listed alphabetically by product feature and by service
request number within each product feature. The following details are available for
each product issue:
Service request numberUnique case number assigned to track the problem. If
the problem was found during product testing by EMC, the case number contains
the abbreviated product name.
Fix numberNumber of the patch or fix for the problem.
Problem summaryHigh-level summary of the problem being reported.
ImpactPotential impact of the issue.
Knowledgebase article (optional)Number of a relevant EMC Knowledgebase
solution.
Additional information (optional)Any additional information about the fix, for
example, if the fix is new, modified, or removed.
Base Functionality
Table 3 Base Functionality
Service
request Fix Knowledgebas Additional
number number Problem summary Impact e article information
83480246 92787 When a VMAX source device has 16 Potential N/A

XCOPY VAAI sessions, the creation of a Data
new session on the target device may fail Unavailability
and log 5F10 errors.
Errors: 5F10
512164SYM 92445 An online engine upgrade activity may Potential N/A

leave the DFOS objects in an invalid Data
state that could impact SnapVX jobs. Unavailability
This is caused by the internal EMC inline
commands FE,STOP followed by a full
board IML (as issued by the SymmWin
script) as these may leave invalid states
in the DFOS red-black tree data
structure.
Errors: BE3E.4A, BE3E.48
83023830 92470 The background VMAX File System (FS) Potential N/A
defragmentation job may leave the FS Data
locked causing SNAP jobs to fail and Unavailability
making the activation of SNAP sessions
for the impacted devices impossible.
Errors: BE3E.48, BE20.45, BE20.50,

3D10.3F

Fixed problems
Table 3 Base Functionality (continued)
Service
511221SYM 92197 During an Online Engine upgrade the Potential N/A

newly added directors my fail to IML and Data
become unavailable. Unavailability
The problem is triggered only if all of the

following conditions are met:
An online code upgrade was
performed from HYPERMAX OS
5977.81x.78x to 5977.945.890 or
higher
Run the SymmWin Compression
Conversion script to enable
compression
Perform an Online Engine upgrade
Errors: 01F2.0A
82609022, 92141 During SNAPVX LINK operations and if Potential 491216

83655206, compression is enabled, the Data Performance
83907184 Services Emulation (EDS) directors may Issue
become 100% CPU busy that impacts
performance.
RAID5 7+1 configurations are more

exposed to this issue because the
problem is triggered when the EDS
relocation queue size (mostly 1-3 tracks)
is less than the back-end RAID slice size.
82453818, 92161 On VMAX arrays configured with RAID6 Potential N/A

82585090 10K drives, a spike of Host I/O workload Data
may cause the back-end director to Unavailability
generate a large amount of Raid Queues
per single DATA device and run out of
S&F (Store and Forward) buffers. As a
result, the drives may drop Not Ready
and the directors log AD3E, CE3E, DADA
errors.
Errors: AD3E, CE3E, DADA
82147432 91901 Snapshots may fail (by design) because Potential N/A
the RDP space is exhausted. RDP Page Data
Frame (PF) utilization reported by EMC Unavailability
applications (such as Solutions Enabler)
can appear unexpectedly low when a
system has FTS encapsulated DATA
devices in the configuration.
The discrepancy between the Flash and

PF values for RDP is caused by the PF
calculation that does not exclude
encapsulated devices as expected.
Snapshots may fail due to lack of flash
space, but the incorrect RDP utilization
did not present a clear indication that the
system was close to a limit.

Fixed problems
Service
84300212, 92048 During a VMAX Online Engine Upgrade Potential N/A

84074828, activity, the programming of the Data
84149540 firmware on the 16 Gbps FC 4 Port I/O Unavailability
Modules SLIC may fail.
The problem occurs when the SLIC is
delivered with firmware level 1.1.53.100.
Errors: 28.33BA.01.
81808528 91668 Issuing EMC internal inline "ITAC" Potential N/A

maintenance commands (as Data
F0,CE,ITAC,CLPL) may trigger 033F Unavailability
errors and the VMAX directors might
become unavailable.
Errors: 033F
83269422 91665 VMAX EDS directors may log DSA driver Potential N/A
timeouts (C003 errors) due to internal Data
lock contentions between CPU cores. In Unavailability
most cases the error is recovered, but in
rare cases, it may result in the EDS
director becoming unavailable.
Errors: C003
82879298, 92351 The EDS director may log 7F50.60 errors No impact 491706
83954012, for deallocated DATA device tracks.
84004648, This happens because when the DATA
84046214, device track scrubber is verifying a
6234638 standard back-end track that is pending
deallocation, it attempts to retrieve the
front-end DATA device track for the
back-end pending deallocation track but
it only gets back fffff/ffffffff because
the back-end track is not allocated.
Errors: 7F50.60
77622526, 87844 iSCSI Directors might log page faults Potential N/A Added on
84824872 (0EFF exceptions) followed by a boot Data 04/05/17.
sequence initialization. This is caused Unavailability
because of out of bounds access of the
timer table.
Errors: 0EFF
84225516 92436 If during an offline full system IML, a Potential N/A Added on
director fails to complete the IML and is Data Loss/ 04/05/17.
manually recovered by issuing an offline Data
single director IML (inline command Unavailability
FE,CE), the director may come online
with stale Page Frame (PF) repository
information causing track meta data
corruption in global memory.

Fixed problems
Service
83068208, 92616 This fix resolves an issue where after Potential N/A Added on
85044744 changing the VMAX Guest OS (GOS) Application 04/05/17.
subnet to 172.19.xx.xx, the customer host Failure
may not be able to connect to the guest.
For example, if a GOS subnet set as
172.18.xx.xx that is also used by the host
is changed to 172.19.xx.xx, the customer
host can be pinged from the VMAX
Service Processor, but guests cannot
connect to it.
513711SYM 92749 The FAST compliance Data Move Engine Potential N/A Added on
(DME) may timeout if one of the tracks Performance 04/05/17.
has pend-complete work that cannot be Issue
finished (for example it has a stuck write
pending).
This fix ensures that the DME engine
skips this track and moves the remaining
tracks for all move types except drains.
82444662 92888 When a Non-Disruptive Migration (NDM) Potential 492880 Added on

session is cancelled and then recreated, Application 04/05/17.
NDM may not preserve a non-birth ID for Failure
the device resulting in the failure to
create a device ID after the device was
previously used by NDM.
84064518 93200 The Symmwin script Convert TDAT Potential N/A Added on
Compression Ratio may fail at step Data 04/05/17.
Validate_System_Impl and post the Unavailability
error Message 0x00000550.0x4C4B:
"Invalid Configuration. Configuration File
Was Not Updated", due to a discrepancy
between the SymmWin available
memory calculation and the HYPERMAX
OS calculation.
Errors: 0x00000550.0x4C4B
515682SYM 93275 This fix resolves an issue where starting Potential N/A Added on
a compression on a Storage Resource Data 04/05/17.
Pool (SRP) that is already 95% full may Unavailability
cause the SRP to reach the out of space
limit.
509327SYM 91621 VMAX FAST SRP compliance moves may Potential N/A Added on
stop due to an internal SRPC task Performance 04/05/17.
timeout. Issue
This problem may trigger when LREP

zones (containing RDP nodes) need to
be expanded on the next source write. If
RDP moves occur on the source device
in that state, then the data movement
engine may get stuck in a loop in that
zone and eventually times out.

Fixed problems
Service
510223SYM 91861 The internal EMC inline command Potential N/A Added on
DA,,SAS,PHYS,VIEW may report Maintenance 04/05/17.
incorrect DAE director port relations. Issue
This display problem could impact users
during an online Engine add activity.
82846098, 92502 VMAX arrays with compression enabled Potential 495421 Added on
84496526 may experience performance impact Performance 04/05/17.
under a heavy Host Write workload. A Issue
DATA device pool may get created for
compression favoring some back-end
directors over others, resulting in an
unbalanced workload for the back-end
and performance impact.
This issue is caused by the internal
compression DATA device choosing
algorithm which favors directors with the
largest amount of configured RAID
groups.
510735SYM 92095 The VMAX array may Vault when the Potential N/A Added on
array is configured with two engines and Data 04/05/17.
there is a faulty SPS on the second Unavailability
engine. This issue may occur when one
of the following replacements activities
are performed on the second engine:
Director replacement, DIMM
replacement, SIB replacement, and MM
replacement.
This fix ensures that SymmWin prevents
these replacements until the SPS is
recovered.
81150282 91553 A write failure during a Flash SLIC Potential 489618 Added on
firmware programming may result in the Maintenance 04/05/17.
SLIC becoming unavailable. This fix Issue
improves the recovery from Flash SLIC
firmware write failures.
515659SYM 93289 This fix is needed to recognize the VPD Potential N/A Added on
information for the new 1m IB cable (part Maintenance 04/05/17.
number 038-004-065-01) used in the Issue
VMAX 250F models. This cable is
installed in 250F systems running
HYPERMAX OS 5977.1xxx.1xxx. In the
event this VMAX array is downgraded to
HYPERMAX OS 5977.952.892, the fix is
needed to recognize the cable and
prevent 03F2.98 errors.
Errors: 03F2.98
84225516 93437 This enhances the internal EMC FDTR Potential 495273 Added on
recovery scan, enabling the scan to Recovery 04/05/17.
recover tracks with meta data BCRC Issue
mismatches and compression sanity
check error due to missing compressions
header on disk.

Fixed problems
Service
84347496 93491 The online deletion of a large range Potential N/A Added on
(approximately 800 devices) of Data 04/05/17.
encapsulated DATA devices while the Unavailability
compression SRP DCE scan is running,
may cause the EDS directors to become
unavailable and log exception errors
(0EFF.FF).
Errors: 0EFF.FF
06238523 93508 After running the SymmWin compression Potential 495290 Added on
script to covert an uncompressed 128K Performance 04/05/17.
SRP pool that is more than 88% Issue
allocated, a compressed disk pool might
not get created.
80720156 92556 On a VMAX 250F array with two Potential 488953 Added on
configured engines, a director IML may Data 04/05/17.
leave all logical paths offline and log Unavailability
03F2.78 errors.
Exposed Environment: SLIC

add/change, memory add, director
replacement, SIB replacement, and
fabric cable replacement are exposed to
this problem.
Errors: 03F2.78
82816326 92704 During an Online Engine Add activity, an Potential N/A Added on
online Fast IML a director may log C30B Data 04/05/17.
errors and become unavailable. Unavailability
Errors: C30B
85194678 518525 EEM Struts 2 DSA Component No Impact 497270 Added on

Unisphere, CVE vulnerability 04/05/17.
CVE-2017-5638
Use this OPT to request EEM version
1.3.0.308.
516505SYM 516505 Use this OPT to request EMC Remote No Impact 495313 Added on
version 7.15.02. 04/05/17.
492668SYM 86956 This fix blocks the MIRD parameter of No Impact N/A Added on
the EMC internal inline command 06/05/17.
98,SCAN,CACH, ...
For example:
98,SCAN,CACH,CBNK/FBNK,MIRD

Fixed problems
Service
83917976 94371 On arrays running HYPERMAX OS Potential N/A Added on

5977.952.892, the Storage Group (SG) Performance 06/05/17.
Compression ratio could be less than Issue
expected due to the internal hysteresis
analysis mechanism that could block
tracks that show compatible
compressibility to be compressed.
Exposed Environments: Thin

Provisioning Compression
06980218,8574 94374 The VMAX internal diagnostics may not Potential 498554 Added on
9914 detect a director with a faulty director Data 06/05/17.
NVRAM component. Unavailability
This fix improves environmental
diagnostics to detect a faulty NVRAM
and post the 0257 error every 4 hours.
85731948 94386 On VMAX 250F arrays with two engines, Potential N/A Added on
an Ethernet message path failure may Data 06/05/17.
cause host I/O timeouts, and xx3C AB3E Unavailability
errors are logged. This is caused because
in the event of an Ethernet path failure,
the array may choose an incorrect
alternative path triggering host I/O
timeouts.
Errors: xx3C AB3E
85225602, 94113 An online configuration change for Potential 498506 Added on

86057482, creating eDisk devices larger than 6.2 TB Data 06/05/17.
86057480 may consume more Meta Data space Unavailability
than expected by SymmWin.
The VMAX back-end and EDS directors
may log 10BC, BE10 errors and
subsequent configuration changes may
fail.
Errors: 10BC, BE10
518429SYM 94020 This fix initializes unused compression No Impact N/A Added on
meta data fields to safely cover future 06/05/17.
implementation of these fields and online
code upgrades.
85139224 94080 The FASTVP demotion of idle extents Potential 497274 Added on
may increase the EDS directors CPU Performance 06/05/17.
workload (% busy) to a point of Issue
impacting host I/O performance.
This fix disables the movement of "idle
data".

Fixed problems
Service
85127954, 94002 A director hardware failure (C004 errors) Potential N/A Added on
85756798, may result in the secondary director Data 06/05/17.
85780824 located on the same engine to become Unavailability
non operational and consequently
triggering the VMAX to Vault.
Exposed environment: VMAX 250F

arrays
Errors: C004, 0EFF.FF, 0DFF.FF,

93FF.FF
06339381, 94102 Under heavy I/O workload, VMAX3 Potential 496770 Added on
85987942 arrays may experience performance Performance 06/05/17.
degradation due to message queue lock Issue
contentions between the Fibre Channel
director and the EDS director.
Exposed environment:
VMAX3 Single-Engine
(100K/200K/400K/450F/850F)
VMAX3 Dual- Engine (250F)
Errors: 02CE
83917976 93783 The FAST algorithm gives higher priority Potential N/A Added on
to uncompressed moves over Performance 06/05/17.
compressed moves which may result in Issue
the 128K pool with a lot of compressible
non red hot data leading to lower overall
compression ratio.
06187710 93669 This fix is an enhancement to Syscall No Impact N/A Added on

9202_A1 and the EMC internal inline 06/05/17.
command C4,PAUS which are used to
disable back-end ports, ensuring these
commands verify that the peer port EMC
SCSI Enclosure Services (ESES) is
operational before disabling the ports.
83033408, 93683 The message bus hardware problems Potential N/A Added on
84784530, that are causing package loss may lead Data 06/05/17.
85191748, to Cyclic Redundancy Check Meta Data Unavailability
84621150, corruption on the Data Services
84913362 Emulation (EDS) directors.
Errors: 60.EC2C.00.

Fixed problems
Service
84577398, 93330 In a VMAX 250F fabric less environment, Potential 495633 Added on
85634162 the code may fail to recover the Ethernet Data 06/05/17.
path after an MMCS replacement or Unavailability
other maintenance activities as listed
below.
Exposed environment: SLIC

add/change, memory upgrade, director
replacement, SIB replacement, and
fabric cable replacement are exposed to
this problem.
Errors: 10.04F2.80, 03F2.78
517016SYM 93887 In VMAX 250F fabric less environment, No Impact N/A Added on
an MMCS failure of the IM directors may 06/05/17.
log 30.BE10.05 errors due to the code
incorrectly checking communication on
the Ethernet paths even if the
communication fails over to the CMI
message.
Errors: 30.BE10.05
83917976 93613 This fix resolves an issue where Thin No Impact N/A Added on
Provisioning FAST statistics may report 06/05/17.
112k compressibility tracks as
compressible even when this FAST tier
does not exist.
84528732, 93931 This fix is introduces EMC inline No Impact N/A Added on
85271070 commands, 80,CRDT,GETQ and 06/05/17.
80,CRDT,SETQ,<value>, to set the FAST
internal parameter qos requested xfer
rate for diagnostic purposes.
84491040, 93647 If during an Online VMAX Engine (DAE) Potential 495693 Added on
84349238 upgrade the user rapidly reseats multiple Data 06/05/17.
DAE cables, the EMC SCSI Enclosure Unavailability
Services (ESES) may fail to initialize
causing the VMAX array to Vault.
84515806 93716 When SymmWin retrieves the fabric path Potential N/A Added on
configuration, the Sycall 920E_04 may Data 06/05/17.
return the incorrect Remote Actual FRU Unavailability
ID due to fabric IB cables errors,
04E0.05, and 04E0.08. This problem may
cause the SymmWin director
replacement script to disable the fabric
path of the incorrect director.
Errors: 04E0.05, 04E0.08

Fixed problems
Service
84515806 93492 On a VMAX 250F two engine system, a Potential N/A Added on
director or SLIC hardware failure may Data 06/05/17.
cause multiple directors to become non Unavailability
operational (DD state) after logging
C007 errors. The software for the
internal data transfer driver (DSA driver)
may report C007 errors against an
incorrect slot id preventing the code
from isolating the faulty hardware.
Errors: C007
516085SYM 93402 When a single IB cable is faulty or Potential N/A Added on

disconnected the VMAX is performing a Data 06/05/17.
Fast IML ($F2 or $FD command) the Unavailability
directors may become non operational
(DD state).

(two engines
Errors: C004
85796218, 93388 During an online Disk Array Enclosure Potential 498879 Added on
85529002 (DAE) upgrade to a DAE daisy chained Data 06/05/17.
configuration the VMAX may go offline Unavailability
and Vault.
This problem may trigger when the SAS
topology table (called ESES) has one of
the primary entries deleted during the
physical installation of the new DAE
being daisy chained to the existing SAS
chain on the engine.
Errors: BE38.EC are logged during the

LCC firmware upgrade. C03E.XX ,
XX2B.36 errors may also log.

Fixed problems
Service
84131340, 93605 Migrating hosts may experience Potential 495555 Added on

85250272, performance impact while data is Performance 06/05/17.
85444264, transferring from VMAX/VMAX2 array to Issue
85780824 the VMAX3 array after NDM Cutover is
issued.
Technical details:
The array's Enterprise Delivery Services
(EDS) emulation is in charge of
background copy services and is
responsible for performing the physical
data migration, using SRDF, during
Non-Disruptive Migrations (NDM). An
issue can occur where a race condition
will start on the VMAX3 while searching
for copy jobs from the source
VMAX/VMAX2 to the VMAX3. A search
request is sent multiple times and these
requests reset a global search pointer for
the device. This elongates the search
request and elevates the CPU cycle
usage of the EDS emulation. Read Miss
requests at that point are affected by the
elevated CPU usage on the EDS
emulation.
84016272 93373 This enhancement introduces the error No Impact N/A Added on
code 2A.01F2.1A for alerting that the 06/05/17.
VMAX Syslog is being written at a high
rate due to streaming errors in the
system.
Intensive writes to the boot flash drive,
that contains the syslog, may reduce its
life span.
85113610, 93237 The internal EMC inline command Potential N/A Added on
85316292 98,9,<dev> may cause the director to Data 06/05/17.
become non operational (DD state). This Unavailability
may occur when the command is issued
on large devices (32 TB) with XCOPY
running. Extents are used by the
applications that implement XCOPY,
ODX, Flash Copy.
84070272, 93225 Ethernet errors such as 10.00F2.28 may Potential N/A Added on
83033408, lead to track CRC Meta Data corruption Data 06/05/17.
84784530, as xx2C errors. This fix enables Strict Unavailability
85191748, priority queue for board to board
84621150, ethernet traffic on the same VMAX
85315688, engine.
84913362
Errors: 10.00F2.28, xx2C

Fixed problems
Service
83259292 93462 If during the process of destaging a Potential 494095 Added on

partial write pending track from cache to Data 06/05/17.
disk the write operation fails, the VMAX Unavailability
may set the track to a Data Unavailable
Track (DUT) and log 60BC errors
indicating that the track cant be rebuilt.
Errors: 60BC
83006950 93177 A DAE upgrade or drive upgrade may fail Potential N/A Added on
when the user inserts multiple new Data 06/05/17.
drives in a short amount of time Unavailability
generating invalid entries in the EMC
SCSI Enclosure Services (ESES) table.
Errors: BC2B.43, 270B.07
82581050, 92945 VMAX eNAS Control Station Potential N/A Added on

75083346, performance may drop after upgrading Performance 06/05/17.
79588716, from HYPERMAX OS 5977.691.684 to a Issue
83957550 higher service release. A high level of
block I/O on the Fibre Channel directors
may directly impact the performance of
the eNAS Control Station when adding
new File Systems.
513859SYM 92820 When a single IB cable is faulty or Potential N/A Added on

disconnected the VMAX may start Data 06/05/17.
logging memory access errors and Unavailability
impact fabric failover/recovery
operations.

(two engines)
Errors: 4C04-indicating that the ADMA

transfer size exceeds the maximum size
513801SYM 93290 This fix resolves an issue where during an Potential N/A Added on
online DAE upgrade or an online drive Data 06/05/17.
upgrade the VMAX may fail to detect the Unavailability
newly added drives.
83199144, 92694 The VMAX array may not check the CRC Potential N/A Added on
83033408, validity of a track in cache when it is Data 06/05/17.
84784530, copied on disk as a compressed track. Unavailability
85191748, This fix ensure that a track in cache with
84621150, CRC Meta Data corruption is not copied
84913362 to disk as a compressed track.
Errors: C12C.E0, ED2C.EE
82453818 92764 In an AIX host environment, online No Impact N/A Added on

masking changes on the VMAX may 06/05/17.
trigger Disk Operation Errors on the
host (sense 02/04/00) causing the host
application to perform a retry.

Fixed problems
Service
512992SYM 92615 The attempt of destaging a compressed Potential N/A Added on

track that was fenced in cache can lead Data 06/05/17.
to the Write Pending being pinned in Unavailability
cache until another write to that track is
received.
When a compressed track gets fenced
(for DEDA errors, or dual raid failure, or
un-rebuildable tracks), the track is
unable to commit to the back end for
destage as tracks with the
NCW_SUSPECT bit set are skipped
without this fix.
Errors: 283E.DD, 7F3E.01 on the EDS

directors
85113610 92565 After extent SNAP sessions are Potential N/A Added on
terminated the internal scrubber doesnt Data 06/05/17.
remove the extent object from the Meta Unavailability
Data Table (MDP), this may eventually
prevent the application from creating
new extents. Extents are used by the
ODX, Flash Copy.
83199694 92581 Maintenance activities on directors may Potential 492394 Added on

leave stale cache slot lock impacting Data 06/05/17.
host I/O. Unavailability
The failure may be caused by a race
condition that may leave a cache slot
locked in the primary memory area, but
not in the secondary.
Expose activities:
Replace Director,
Replace DIMM,
Replace SIB,
Maintenance on Director where IML is
performed.
82680100, 92268 When the host application tries to ready Potential N/A Added on
85113610, a source track of an extent SNAP, that is Data 06/05/17.
85316292 also flagged as Deferred Table Rebuild Unavailability
(DTR), the I/O may timeout.
Errors: 283C
82259054, 92751 When a track gets fenced by the EDS Potential 494933 Added on
83259292 director back to the front end, the TDEV Data 06/05/17.
local mirrors are set invalid without Unavailability
checking if the remote (SRDF) mirror is
available. This may occur when the BE
track gets marked as Data Unavailable
Track (DUT) or corruption is detected in
the write destage flow.
Errors: B9.60BC.15

Fixed problems
Service
82398744, 92080 If during a power up IML a director takes Potential 491837 Added on
82181268 more than 2 minutes to synchronize the Data 06/05/17.
TOD clock it becomes not operational Unavailability
(DD state). This fix increases the timeout
to 4 minutes.
509126SYM 92047 The FAST de-allocation activity may No Impact N/A Added on
trigger 87.7F75.E2 errors on the EDS 06/05/17.
directors.
This fix reduces the impact (scheduling)
on tasks using generic task array (GTA)
when there are a lot of active data
movement tasks.
81807168, 91589 In a FAST environment, some I/O profiles Potential N/A Added on
84528732, in the Storage Group may not meet the Performance 06/05/17.
85136486, SLO compliance. Issue
6413689, The internal FAST parameter,
85271070 PROMO_CUTOFF, is used to decide
when a track can be promoted. SLO
promotions from the 10K pool to an
Enterprise Flash Drive (EFD) pool may
be prevented when the I/O profiles
default value of 0.5 is too high.
85281644 91654 Under rare circumstances the exception Potential N/A Added on
handling logic may cause stuck Write Data 06/05/17.
Pendings on a TDAT device. Unavailability
This issue forces exception errors on a
back end director resulting in the
corruption of a device scheduler mask
used to determinate if Write Pendings
need to be copied to disk.
84858764, 91193 Running a Sync XCOPY with many Potential 497005 Added on
85113610 extent sessions may trigger stuck write Data 06/05/17.
pending (WP) on the device SRDF Unavailability
mirror. This problem may lead to 5F16.EO
errors (XCOPY timeout) and 2B2A
errors which in an SRDF/A environment
will cause SRDF/A to become
inconsistent.
84622236 94382 Potential SNAP Extent session failures Potential N/A Added on
caused by a race condition between Data 06/05/17.
Extent establish thread and an internal Unavailability
scrubber job.
As result we may have missing target or
source extent meta data objects.
Errors: 833C, BE10.EF, BE10.E1

Fixed problems
eNAS
This service pack includes fixes introduced in eNAS Service Pack 8.1.11.282. More
information on these fixes is available in the VMAX eNAS 8.1.11.282 Release Notes on
https://support.emc.com.
Table 4 eNAS
Service
05998564, 516741 Buffer overrun condition causes DM to No Impact N/A Added on

85066428, PANIC. 04/05/17.
85217922, Use this OPT to request eNAS version
85100976, 8.1.11.282.
84049594,
84824838,
84707076,
85085184
Enhancement
Table 5 Enhancement
Service
514712SYM, 93077 ETA 494233; This enhancement Potential N/A

514320SYM, introduces support for IBM z/VM Data
514038SYM V6.4 for VMAX and VMAX3 arrays. Unavailability
502523SYM 89504 This enhancement improves the No Impact N/A

performance of Mainframe SRDF
Autoswap operations and the
performance of the EMC internal SRDF
inline commands F0,CE,RDFU and
F0,CE,RDFF.
84515806 93599 VMAX 250F (two engines); This No Impact N/A Added on
enhancement introduces EMC internal 06/05/17.
inline commands to faster recover the
director CMI Atomic queues without
having to Fast IML the director.
The inline are part to the
1b,ifab,@cmiatomic commands.
517971SYM 93897 In the event of CRC data corruption the No Impact N/A Added on
VMAX Data Engine Driver (DEDD PLX 06/05/17.
driver) may stream messages in the
syslog (01F3.FA errors). The
enhancement prevents these messages
to be logged unless specifically
requested.
506681SYM 92285 This enhancement improves the TDEV No Impact N/A Added on
full device user de-allocation execution 06/05/17.
time (command symdev free -all).

Fixed problems
Table 5 Enhancement (continued)
Service
509921SYM 90889 This enhancement improves Recovery No Impact N/A Added on

Tools to allow the user to more 06/05/17.
efficiently recover data that fails to
decompress due to corrupted data or
meta data.
Added option PRGE to the FDTR internal
VMAX recovery scan.
Fix 90889 replaces Fix 93515 from
HYPERMAX OS 5977.952.892.
Fibre Channel
Table 6 Fibre Channel
Service
83816078 93203 The host I/O limit set by the user on the Potential N/A Added on
VMAX front-end directors may not be Performance 04/05/17.
enforced after one of the Fibre Channel Issue
directors is replaced or a experiences a
full IML.
84325318 91088 After a Fibre Channel director Potential N/A Added on

replacement, the director may fail to Maintenance 04/05/17.
bring the ports online due to the code Issue
failing to verify if the SFS devices are
mounted online.
This check is obsolete for any
HYPERMAX OS 5977.xxxx releases.
84431874, 93585 SRDF/A may stop transferring data Potential 495900 Added on
84481922, (cycling) when the Fibre Channel Data 06/05/17.
82317254 emulation does not properly handle the Unavailability
aborted I/O cleanup of a SCSI unmap
(opcode=0x42) command that is causing
track meta data sector signature errors.
Errors: 2A2C on Fibre Channel directors

and 052C.BC on SRDF directors.

Fixed problems
Table 6 Fibre Channel (continued)
Service
84178330, 93571 A Windows 2012 SCSI-3 Cluster reboot Potential 495486 Added on
85148272, or failover operation may trigger a Data 06/05/17.
84463658 discrepancy between the PGR Unavailability
(Persistent Group Reservation) and the
device lock preventing the cluster to
recover.
This problem is rare, the VMAX Fibre
Channel director needs to process the
next cluster SCSI Reserve or Release
commands before the lock of the
previous command is released.
Errors: 5F3C.04 indicating failures in

setting to set an exclusive Access bit,
DB0D.63 indicating a mismatch between
the device PGR flag and the device lock.
83330582 93000 This fix introduces a low priority task to Potential 493311 Added on
scrub the stale DVIN entries on the Fibre Application 06/05/17.
Channel directors. Failure
Stale DVIN entries can build up on Fibre
Channel ports over time when initiators
log into the fabric, each time with
different Fibre Channel IDs (FCID). SAN
environments with switches using NPIV
can be susceptible to this.
There are 8192 DVINs available in total
for each Fibre Channel director, with
many stale DVIN entries it is possible to
reach the maximum limit and log
FD22.CD, FE11.17 and CD22.03 errors.
Errors:
FD22.CD - indicating a DVIN could not be
allocated.
FE11.17 - indicating a WWN leaves the
fabric and without a valid DVIN (i.e.
FFFF).
CD22.03 - indicating an initiator tag is
invalid.
509607SYM 92067 A device lock may be prematurely Potential N/A Added on

released when two PGR Data 06/05/17.
Persistent-Reserve 5E commands are Unavailability
issued on the same device and executed
concurrently on the same FA. This can
lead to inconsistencies in the Persistent
Reservations and 70.1222.03 errors on
the Fibre Channel directors.

Fixed problems
iSCSI Channel
Table 7 iSCSI Channel
Service
83817802, 92697 Multiple hosts issuing small block I/Os Potential N/A N/A
83402924 on VMAX iSCSI directors that are Performance
configured with only three cores may Issue
increase the I/O response time, and
impacting performance as a result.
Errors: 8E38.BE
83911154 93206 When the iSCSI director is performing No Impact 494155 Added on
GID changes it may trigger a recoverable 06/05/17.
page fault exception 2A.0EFF.FF error.
Exposed environment: HP Unix host

running PowerPath and performing
continuous GID changes.
Errors: 2A.0EFF.FF, 75.DB3E.11,

F9.DB3E.23
Mainframe
Table 8 Mainframe
Service
82893540, 92785 On a Mainframe SRDF environment, Potential 492583

82885238 when the host application is updating the Data
same SRDF track multiple times, an Loss/Data
update may get overwritten in the R1 site Unavailability
before it gets propagated to the R2 site
resulting in a data mismatch between the
SRDF devices (EC85 errors).
Errors: EC85

Fixed problems
Table 8 Mainframe (continued)
Service
81808528 91672 In Mainframe environments, concurrent Potential 489590

copy jobs may trigger ITAC messages Data
that fill the EDS queue (5F10.E1 errors) Unavailability
preventing new concurrent copy jobs
from being created.
When the FICON director sends the

terminate command for concurrent copy
to the EDS and it fails, it can leave a task
code of zero which is invalid and this
results in 0122 errors. Then, if the ITAC
MSG queue gets filled, it results in
5F10.E1 errors and no more concurrent
copy tasks can take place.
Errors: 0122.6F, 0122.07, 5F10.E1.
81479290 92671 In Mainframe environments, during a No impact 492811

host LPAR IPL time, a Master Start
Pending error could be logged.
Error: Master Start Pending receiving

on all systems against catalog volume
IEF196I IOS071I xxxx,*MASTER*, START
PENDING
IOS071I xxxx,*MASTER*, START
PENDING 247
81788858 91289 Running Mainframe zHPF with Potential 481198

SRDF/Asynchronous (SRDF/A) may Data
trigger streaming 77CA and 80CA errors Unavailability
on the FICON directors. The problem
happens on a specific zHPF chain which
starts with the commands 0x50 or 0x60.
Errors: 77CA, 80CA
81793668 92002 On an SRDF Mainframe zHPF Potential 489082

environment the EDS directors on the Data
SRDF R2 VMAX array may log 4910.04 Unavailability
errors preventing the CKD tracks to be
destaged on disk. The problem may
occur when the zHPF 0xE7/0x95
command (by design) does not write
record zero on the first track.
Errors: 4910.04
511292SYM 92219 This Mainframe Concurrent Copy Potential N/A Added on

terminate command may fail and log Application 04/05/17.
C53E.1C error when the timestamp of Failure
the command goes negative.
This fix ensures the internal scrubber
cleans the failed Concurrent Copy
session allowing the application to retry.
Errors: C53E.1C

Fixed problems
Service
82837596 92523 In a Mainframe Enabler environment, Potential 492137 Added on

SNAP jobs may fail when the VMAX Data 04/05/17.
array is executing Syscall 014C.01 on an Unavailability
extent which starts from the last cylinder
of a device.
The Mainframe Joblog may report the

following error:
EQCA032E
SCST|SCTT(xxxx.xx.xx) BAD RC, 3E
DATA value
or
SCST|SCTT(xxxx.xx.xx) I/O FAILED,
DOIO RC rc
Cause
A syscall (xxxx.xx.xx) returned
unexpected data during a call to check
the track status.
or
A syscall (xxxx.xx.xx) I/O failed with the
indicated return code.
ESNP542E
EMC SNAP API - I/O ERROR
CHECKING INDIRECT STATUS
Cause: An I/O error occurred while
checking the indirect status of the target
extent.
83363122 92867 In Mainframe environments, the Potential 493424 Added on

Mainframe Flash jobs may fail with RC=8 Data 04/05/17.
and the job log posting the error Unavailability
"ADR305E (001)-SB109 (01), Unable to
serialize VTOC on volume XXXXXXXX".
83032850, 93223 The Mainframe FICON directors QLOGIC Potential 492332 Added on
83720524 driver may incorrectly detect that the Data 04/05/17.
link is down, triggering host I/O aborts Unavailability
and host channel selective reset.
Errors: 4B17.00, 103D
84911878 93882 ETA 496928 Potential 496739 Added on

Access methods reading Mainframe PDS Data 04/05/17.
(Partitioned Data sets) when running Unavailability
HYPERMAX OS 5977 with Fix 92024
may receive I/O errors which may result
in data unavailability.

Fixed problems
Service
520944SYM 94523 Using Parallel Clone on Mainframe SRDF Potential 494712 Added on
devices with FlashCopy enabled may Data 06/05/17.
cause the SRDF devices to become Not Unavailability
Ready on the SRDF links. The problem
may trigger when Mainframe devices are
performing an extent parallel clone copy
and a dataset delete is issued before the
copy completed.
Errors: 0530.05, 052F.30/33, F03F.05
84808136, 94197 When a Concurrent Copy job runs in Potential 497759 Added on
84915282, parallel to a Thin reclaim operation it Application 06/05/17.
85880170 may log DA2C errors on the FICON Failure
directors indicating that the Concurrent
Copy Read Track Image command (DA)
detected Meta Data CRC corruption
errors.
Errors: DA2C
85093720 94111 Even after mainframe devices have been Potential 497620 Added on
brought offline, Innovation FDR and EMC Application 06/05/17.
TimeFinder may report the devices Failure
Dynamic Path Recognition (DPR) state
as online.
The problem may trigger after a
reconfiguration effecting the addressing
of the FICON director boards. Syscall
9206, used to read the DPR state
information from the VMAX array, may
report stale information.
518926SYM 94036 In rare circumstances, the Mainframe Potential N/A Added on

FICON director may log CRC meta data Data 06/05/17.
corruption errors (xx2C) due to the Unavailability
DEDD PLX driver incorrectly handling
the DIF bytes.
Exposed environment: one engine

VMAX 250F arrays
Errors: xx2C
06515092 93938 Mainframe Read Multiple Channel Potential 497024 Added on

Command Word (CCW) does not Data 06/05/17.
propagate residual byte count to last Unavailability
CCW when the previous CCW completes
reading all data on a track.
Exposed environment: Only VMAX3

arrays running HYPERMAX OS 5977 are
exposed.

Fixed problems
Service
84172092 93438 In a Mainframe environment, when Potential 495120 Added on

running the job IBM DFDSS ADRDSSU Performance 06/05/17.
Data Set Dump to disk the system may Issue
experience performance impact.
When the mainframe track does not have
a standard record 0, the VMAX brings
the track into cache even if this
operation is not necessary, triggering
write misses, and elongate the write I/O
response time.
80408524 93383 In a Mainframe environment, after a Potential 494988 Added on

TimeFinder BCV Clone split operation Application 06/05/17.
the application may fail to bring the first Failure
BCV device online, a subsequent attempt
succeeds.
Errors: The Mainframe host logs:

IEF359I RESERVED OR BROKEN DASD
DEVICE xxxx NOT VARIED ONLINE
No errors are logged on the VMAX array.
83628822 93246 In a Mainframe environment after a Potential 494263 Added on

FICON Hyper Parallel Access Volume Data 06/05/17.
(HPAV) online configuration changes the Unavailability
FICON ports may have an incorrect
HPAV setting resulting in the following
mainframe error messages:
IEA436I I/O ERROR DURING DEVICE
INITIALIZATION
IEE764I END OF IEE103I RELATED
MESSAGES
IEE103I UNIT 83CE NOT BROUGHT
ONLINE 868
514322SYM 93477 In a Mainframe environment after an Potential 495327 Added on

online configuration change adding CKD Application 06/05/17.
devices, the FICON (EF) directors may Failure
log C610.02 errors indicating that the
device attention message buffer is not
initialized. This problem may effect
mainframe applications because the
attention messages may misbehave.
85415176 92189 When a Mainframe host I/O on an SRDF Potential 499198 Added on
device fails with Unit Check status due Application 06/05/17.
to an Invalid Track Format, the FICON Failure
directors may incorrectly report End of
Cylinder in the sense byte. As a result,
Mainframe applications may generate
IEC603I messages.
76675466, 86956 ETA 498674: VMAX3, VMAX, Mainframe Potential 463467 Added on
76967496, Systems: RMF high pend times and Performance 06/05/17.
85269798, catalog contentions may result in data Issue
85415176, unavailability.
8582992

Fixed problems
Online Upgrade
Table 9 Online Upgrade
Service
82511304, 93110 For VMAX3 arrays originally installed Potential 483916 Added on
82550928, with HYPERMAX OS 5977.250.189, a Data 06/05/17.
83743162, Non-Disruptive Upgrade (NDU) to Unavailability
83296286, HYPERMAX OS 5977.813.785 or
84236580, 5977.814.786 may trigger an exception on
84838858 the Fibre Channel directors and render
them unavailable.
Errors: 2A.0DFF.FF, 2A.0EFF.FF,

28.D80B.0B
Open Systems
Table 10 Open Systems
Service
81758366, 91539 Fibre Channel directors may become Potential 489584

81845796, unavailable after logging eight Data
82365178 2A.0EFF.FF events with bad trap Unavailability
emul_EXa and emul_EX9 errors.
The problem may trigger when a device
is executing the TUR command while a
masking change is removing the same
device from the Storage Group (SG).
Errors: 2A.0EFF.FF
SRDF/A
Table 11 SRDF/A
Service
83112500, 92562 In an SRDF/A environment, in the rare Potential 492535

84368126 event of an SRDF/A hash chain Data
inconsistency, VMAX arrays start Unavailability
streaming 56CA.04/05/06 errors, and
SRDF directors may become unavailable.
Errors: 56CA.04, 56CA.05, 56CA.06,

20CE.xx, EC85

Fixed problems
Table 11 SRDF/A (continued)
Service
509791SYM 92462 In an SRDF/A environment, failed MCMS Potential 490239

operations could lead to corrupted Data
SRDF/A cycles, resulting in data Unavailability
inconsistency on the R2 side of an
SRDF/A group.
Errors: 903E, xxCA
83117238 92518 The EMC internal inline command Potential 492261 Added on
F0,CE,SNMB,COMT,<group> may fail to Recovery 04/05/17.
recover an SRDF/A cycle in a hold state Issue
caused by an SRDF/A link drop.
5468382, 92812 Certain VMAX configurations may be Potential 493026 Added on

83467906 susceptible to causing host response Performance 04/05/17.
time impact after an SRDF/A link drop Issue
and during the cleanup activity. SRDF/A
cleanup may trigger a lock contention
that may impact the response times of
the array.
Exposed environments: Configurations

with a large number of SRDF directors
that have several cores assigned to them
may be exposed to this problem.
515737SYM 93303 When an SRDF/A link drops (CACA Potential 495820 Added on
errors), the SRDF code may incorrectly Data 04/05/17.
handle the SRDF Transfer log cleanup Unavailability
creating inconsistence between the R1
and R2 devices (EC85 errors),
preventing the devices from entering a
ready state on the SRDF links.
Errors: EC85
SRDF Family
Table 12 SRDF Family
Service
81650606, 87709 Environments with SRDF configuration Potential 490969

83718210 with Consistency Group (CG) enabled Performance
may see a performance impact of 10 ms Issue
per Write I/O. The problem may occur
when an SRDF split is performed on a
device that has two SRDF mirrors or
when SYMAPI fails to send Syscall 814E
to close a CG ECA window.

Fixed problems
Table 12 SRDF Family (continued)
Service
80797466 92022 Running a high workload (approximately Potential 487942

20,000 I/O sec) on one SRDF director in Data
Journal-0 mode may cause the director Unavailability
to become unresponsive an eventually
become unavailable.
A temporary workaround could be to
reduce workload to the SRDF directors
and/or add more directors to assist with
distributing the workload.
Errors: D80B.5D, 01F2, 02F2
81238134, An SRDF/STAR activation may fail due to Potential 463729 Added on

81761374, old Session-in-Change (SIC) that are Data 04/05/17.
06196235 present on the devices. The problem may Unavailability
trigger if a Local Replication queue on
the EDS director becomes corrupt. This
queue is used by the EDS directors to
manipulate the protection bits for the
STAR SDDF session and corruption may
occur if the queue was actively being
used during a FAST IML which tries to
re-initialize the queue with the active
entries.
Errors: 5F10.56
83524880, 91695 When a host application is generating Potential 490485 Added on

83775696 Null Track writes (as a result of SCSI Data 04/05/17.
unmap commands, Write Same with 0 Unavailability
data, or XCOPY with 0 data) on the
SRDF devices, the SRDF directors may
log EC85 and DC2C errors indicating a
Metadata Sector Signature mismatch
between the R1 and R2 tracks.
Errors: EC85, DC2C
509442SYM 92295 Online removing a dynamic SRDF group Potential 489973 Added on
from an SRDF director when the devices Data 04/05/17.
are configured as cascaded SRDF (R21) Unavailability
and in SRDF Adaptive Copy Disk mode
may result in stuck Write Pending on the
R21 devices.
Special conditions: The problem is

experienced when the last group on the
SRDF director is being removed while
the SRDF groups still exist on the array.
Errors: 2B2A error.

Fixed problems
Service
06314381, 93451 In a PowerPath with SRDF/Metro Potential 495536 Added on

06013232 environment, PowerPath may see the Data 04/05/17.
SRDF devices from the two VMAX arrays Unavailability
as different devices instead of the same
SRDF/Metro device.
This is a problem with the SRDF Metro
device ID handling of devices that were
previously spoofed (Flexible Device
Geometry or Spoof Geometry).
The host log reports ALERT:
PowerPath:Status:Already exists. Failed
to register device. User should unclaim
paths.
06302914 93622 When a host job, such as Windows Potential 495614 Added on
defragmentation, is generating large Data 04/05/17.
amounts of copy command of tracks with Unavailability
NULL (zero) while SRDF/A is in spillover
mode, SRDF/A may drop and log
CACA.12 errors. This happens because
host unmap operations in SRDF/A
spillover are treated as full track destage
even when the tracks contain zeros
causing SRDF/A SRP pool to fill-up and
eventually causing SRDF/A to drop.
Errors: CACA.12
517877SYM 93892 When a parallel clone session on a R1 Potential N/A Added on

device is withdrawn, the parallel clone Data 06/05/17.
RDF information may not get cleared. Unavailability
This results in SRDF invalids not getting
set when required due to incorrectly
believing the device is still in a parallel
clone session.
This results on R1 updates not getting
copied to the R2 side which result in
SRDF data miscompare errors (EC85).
Errors: EC85, D03E
84333502, 93909 When the VMAX Fibre Channel directors Potential 427641 Added on
84209846, detects host write have CRC corruption Data 06/05/17.
84481922 (xx2C error) the corrupted track may be Unavailability
added to an SRDF/A cycle preventing
SRDF from transferring data to the
remote VMAX.
This fix will clean up corrupted tracks
locally before theyre versioned for use
with SRDF/A to allow SRDF/A to
continue running.
Errors: xx2C errors on the Fibre Channel

directors, 052C errors on the SRDF
directors

Fixed problems
Service
83502884 93765 In an SRDF Active-Active environment, Potential N/A Added on

the VMAX may report the incorrect local Application 06/05/17.
system serial number when the host Failure
application issues a standard inquiry CDB
command.
84171038 93339 VMAX 250F; In an SRDF GigE Potential 494869 Added on

configuration between a VMAX3 array Data 06/05/17.
running HYPERMAX OS 5977 and a Unavailability
VMAX array running Enginuity 5876, the
SRDF RE director may intermittently
detect Meta data CRC corruption, error
0338, D102, 052C, 062C and the RDF
device may become not ready in the RDF
links.
This issue is specific to RE directors on a
VMAX3 array (that has an Asteroid SLIC)
connected to RE directors on a VMAX2
(that has a Mesocyclone IO Module
Carrier).
83615688, 93094 In an SRDF/Metro environment, the host Potential N/A Added on

83671788, may experience I/O timeouts when Data 06/05/17.
85481874 issuing ATS commands on a VMAX Unavailability
running SRDF/Metro in Active-Active
mode.
The Fibre Channel directors may log
F31C.07, 283C.07 (I/O timeout) and
8810.32 (data slot locked and lock was
released) errors.
Errors: F31C.07, 283C.07, 8810.32
85264732 92645 A stuck Write Pending (WP) track on an Potential N/A Added on
SRDF/A cache slot may cause SRDF/A Data 06/05/17.
to become inconsistent and log 2B2A Unavailability
errors.
Fix 92645 corrects the stuck WP tracks.
508899SYM 91689 In an SRDF/A environment with a VMAX Potential N/A Added on

array running Enginuity 5876 connected Data 06/05/17.
to a VMAX3 array running HYPERMAX Unavailability
OS 5977, the write same of a NULL
(zero) track may cause the internal SRDF
Data Compare (RDC) scan to falsely log
meta data mis-compare errors.
Errors: DC2C, EC85.

Fixed problems
SymmWin
Table 13 SymmWin
Service
83600980 20018867 On a VMAX array with eNAS installed, No impact N/A

the SyrInfo SymmWin script when
invoked by the SymmWin scheduler may
fail at the step Prepare_eNAS_SYR_file
with an exception preventing the output
XML file to be generated.
82896818 20018852 The SymmWin script SyrInfo that is used Potential 494735
for collecting drives Spare coverage may Maintenance
fail at the step Issue
Log_Spare_Coverage_Info and post the
error: Message 0x0000708E.0x10AA:
Script Exception Occurred.
511229SYM 20018848 During the Management Guest (EEM) Potential N/A

Online add, the SymmWin script Data
generates new intra guest keys for the Unavailability
Tools Guest causing a mismatch between
the keys on the MMCS and the Tools
containers, causing other online Tools
Guest upgrades to fail.
509654SYM 20018833 The SymmWin script Online Code Potential N/A

Upgrade incorrectly prevents the user Maintenance
for upgrading from HYPERMAX OS Issue
5977.945.890 or 5977.952.892 to
5977.10xx.10xx even if the upgrade is
valid.
80730218 20018683 SymmWin may not trigger a dial home to Potential N/A
replace Not Ready Spare drives when Data
coverage for drives drops to the deferred Unavailability
maintenance threshold level.
509199SYM 20018826 An online configuration change to Potential N/A Added on

remove external (encapsulated) disks Data 04/05/17.
may fail due to the invoking of Syscall Unavailability
9247_84_00 failing with an error
message.
Errors: 160
512005SYM 20018847 During an online or offline Fast IML Potential N/A Added on
SymmWin (SPCM service) may lose Data 04/05/17.
communication with the VMAX directors. Unavailability
84070272 20018870 When simplified SymmWin registers to Potential N/A Added on

use Management File Transfer (MFT), it Maintenance 04/05/17.
may trigger an internal SymmWin Issue
memory leak that may cause the MMCS
to become unresponsive or reboot.
Errors: 04DA.09

Fixed problems
Table 13 SymmWin (continued)
Service
516366SYM 20018876 The SymmWin script SYRINFO does not No Impact N/A Added on
collect the Feature Registration for 04/05/17.
compression, because Syscall
922B_01_08 is used to collect the
Feature Registration but it only
processes 147 out of the 154 records
available.
516185SYM 20018877 The SymmWin Online Compression Potential N/A Added on

Conversion script may issue an Online Data 04/05/17.
IML ($F2 inline command) before the Unavailability
conversion is completed. This is due to
the step
"Monitor_Mdp_Elm_Tables_Creation"
monitoring the compression using the
incorrect Syscall.
84193518 20018878 The SymmWin Health Check script may No Impact 494671 Added on
fail to read the dual inline memory 04/05/17.
module (DIMM) vital product data (VPD)
and incorrectly report a missing DIMM.
This problem may trigger on VMAX 250F
arrays when the DIMM configuration is
not uniform between the engines.
Errors: 0485.7x
81150282 20018880 On a VMAX array with DARE enabled, if Potential N/A Added on
during an online drive upgrade activity Maintenance 04/05/17.
new drives are relocated from one slot to Issue
another (usually done for debugging
purposes), it may result in a mismatch
between the drive WWN and the DARE
WWN triggering I/O failures.
Simulating a drive replacement

addresses the problem.
83206122 20018857 The SymmWin script that is used to Potential N/A Added on
change the dynamic subnet IP uninstalls Data 04/05/17.
the eHA Unisphere Database even when Unavailability
the subnet C change (used by Guest OS)
is not affected by the IP changes.
The script fails and posts the error

message 0x000017B9.0xBAD0C:
Script found a container that has a
critical service "stopped or failed".
518756SYM 20018890 This fix resolves an issue where the No Impact N/A Added on
Usage Intelligence (UI) files sent by 06/05/17.
SymmWin to EMC via ConnectEMC may
get corrupted. The problem may trigger
when ConnectEMC fails to transmit the
file and the next file is appended to the
previous one making it unreadable.
This SymmWin fix overwrites the UI files.

Fixed problems
Table 13 SymmWin (continued)
Service
517122SYM 20018882 Under rare circumstances the SymmWin Potential N/A Added on
Director Replacement script may disable Data 06/05/17.
the fabric paths on the incorrect director Unavailability
at step
BrdRpl_Disable_Phys_Fabric_Paths. A
director hardware fault may cause
Syscall 920E_04, used by Symmwin to
retrieve fabric path configuration, to
return incorrect data.
83108948 20018855 In a Mainframe environment, when the Potential N/A Added on

user tries to perform an online change of Data 06/05/17.
the VMAX configuration to enable Hyper Unavailability
PAV on a single split the SymmWin script
may fail with the following error:
Message 0x00007083.0x4053:
Syscall failure. Result is
CNFG_SYSC_ILLEGAL_INPUT
Procedure Aborted!
TimeFinder-Clones
Table 14 TimeFinder-Clones
Service
513083SYM 92632 The SRDF copy is inadvertently being Potential N/A Added on
blocked when the SRDF R1 device is a Data 04/05/17.
clone emulation target and the R2 Unavailability
source device is established in precopy
mode. In this case the invalid tracks on
the R1 SRDF mirror devices wont be
processed.
Exposed environments: This problem

has been introduced by the fix 90742 at
5977.945.890.
05362560 92688 When a clone is in a precopy in-active Potential N/A Added on

state the SnapVX background recovery Data 06/05/17.
scan is incorrectly decrementing the Unavailability
clone target sequence number triggering
the error 3D10.5D on the Data Services
Emulation (EDS) directors.
Errors: 3D10.5D
509725SYM 92017 LREP CLONE restore performance is not Potential N/A Added on
linear with devices larger than 1 TB. Performance 06/05/17.
Issue

Fixed problems
TimeFinder-Family
Table 15 TimeFinder-Family
Service
83602182 92278 In a mix cascade Clone VPSnap Potential 493724 Added on

environment, the copy clone may stop Data 06/05/17.
(stuck Version Write Pending track) and Unavailability
the host read I/O may fail with a timeout
(74.283C.01 error). An internal
background define task, related to a
Cascaded Clone copy, may become
stuck causing high utilization on the EDS
directors.
Cascaded Clone example: Clone A to B

and VPSnap B to C
Errors: 74.283C.01
81584582, 92551 This fix improves the information logged No Impact 490385 Added on
81661500 by the 5f10.7c error to help diagnose 06/05/17.
XCOPY Extent problems.
TimeFinder-SNAP
Table 16 TimeFinder-SNAP
Service
05587063 92669 SnapVX may fail when the Target State Potential 491012
Table index references a non-existent Data
cache slot. This is caused because a Unavailability
Lock holder is read as a cache slot
leading to C010, C110, 3D10.90 errors and
a SNAP linked target or symclone
failures. The problem is triggered by an
incorrect entry in an internal SnapVX
data structure known as DPD.
Errors:82.3D10.90, 21.C110.71

Fixed problems
Table 16 TimeFinder-SNAP (continued)
Service
05428287, 91424 SnapVX snapshots may intermittently Potential 491901

83088788 fail and log a 3D10 error. This is caused Data
by the SNAP RDP Cleanup task that runs Unavailability
after a snapshot is terminated to cleanup
RDP nodes and could return an RDP
node twice leading to 3D10 errors and
failed snapshots.
Exposed environments: Configurations

running HYPERMAX OS 5977.813.785
and above.
Errors: 3D10.xx
511833SYM 92363 Dell EMC ProtectPoint backup copy may Potential N/A
stop and SnapVX jobs may fail due to Data
incorrect values of SnapVX status bits Unavailability
kept in an internal SnapVX data structure
known as DPD.
05129776, 91981 Clone copies may fail and generate Host Potential 490689
82453818 I/O timeout errors (2A3C.14) when an Data
Fibre Channel director becomes Unavailability
unavailable due to hardware failure. This
happens because clone Version Write
Pending tracks (VWP) are left
incomplete, the sectors of these tracks
are not set Write Pending (WP) and the
TAG is not updated.
82421078 91606 The internal VMAX LREP scrubber takes Potential N/A
session-in-change while scrubbing Application
extents to avoid contention on the Failure
extents with control commands. This
could cause control commands to fail
because they cannot get
session-in-change. The scrubber should
only check if session-in-change is held
on the device when checking extents and
check the device later if it is held.
82162456 92593 This fix resolves an issue where the Potential N/A Added on
customer ProtectPoint backup may not Data 04/05/17.
complete even though the Symcli Unavailability
commands report the copy at 99% and
in-progress. This issue may occur when
the target ProtectPoint device has an
invalid local mirror, causing the SnapVX
copy to fail to complete.

Fixed problems
Service
83267448, 92687 The SYMCLI command synsnapvx Potential 493618 Added on

83290678, establish may fail with the error Failed Data 04/05/17.
84193860 to process consistency window Unavailability
management request due to an
application failing to close the SnapVX
Enginuity Consistency Assist (ECA)
window.
The most common reasons are:
- The SYMCLI command was interrupted
with a Control-C while the window was
open.
- The hosts lost access to the Gate
Keeper devices.
- The host/application crashed before
the command completes.
84865414 92964 When a director is unavailable, the Potential N/A Added on

SnapVX sessions may fail due to internal Data 04/05/17.
lock contentions on the SnapVX internal Unavailability
meta data structure (RDP).
Special Conditions: The problem is

more likely to occur when director one
becomes unavailable.
Errors: 3D10.68, AE3E.04/06
85113610, 93688 Extent session creation on a source Potential N/A Added on

85316292 device may corrupt the SESSION Data 06/05/17.
STATUS information of all other Unavailability
subsequent sessions on the same
device.Extents are used by the
ODX, Flash Copy
512818SYM 92594 Creating a snapshot on a source device Potential N/A Added on

that has multiple write pending tracks Data 06/05/17.
followed by a SnapVX restore to the Unavailability
same device may cause the SnapVX
restore operation to become stuck.
509384SYM 91646 After creating a SnapVX Snapshot linked Potential N/A Added on
to the Target device, the copy may stop Data 06/05/17.
with the protection count failing to Unavailability
progress.
This may occur when the source device
has multiple write pendings (WP)
resulting in a possible deadlock situation
between the Snap and EDS metadata
which prevents the WP from destaging.

Fixed problems
Service
85113610, 91443 Potential extent session failures may Potential N/A Added on
85316292 occur while running SNAP and Data 06/05/17.
Mainframe Concurrent Copy operations Unavailability
logging:
5F10.2F errors indicating a mismatch
between device ready state and
session bits
5F10.27 errors could be logged during
sanity check for device
protection/indirect bits, it indicates
inconsistency in the device
protection/indirect bits
Extents are used by the applications that
implement XCOPY, ODX, Flash Copy.

Firmware Pack release history

Each HYPERMAX OS Service Pack also contains the latest Firmware Pack. The
complete ReadMe document for Firmware Packs Release Level 5977 is available on
https://support.EMC.com. The release history of the Firmware Packs for the 5977
code family along with the released fw_pack_full.exe files is shown in Table 17.
Note: The OPT numbers column provides the Service Release OPT number (SR OPT)
for the Firmware Packs. Only EMC personnel have access to the OPT system. Please
contact your local EMC representative for details.
Table 17 Firmware packs release history
Release DriveDB/SSDB
date Full firmware pack file Firmware update file(s) Description revision
5 June, fw_pack_full_5977_170516 fw_170413_001628_PM40096_ Updated Toshiba Phoenix M4 DriveDB rev.:

2017 _134535.exe 5SRB096C.zip LWPD drive firmware to 5977.156000
fw_170413_001726_PM40192_ PC47. The update disables
5SRB192C.zip potential premature
fw_170413_001737_PM40384_ endurance throttling that
5SRB384C.zip could cause performance
impact.
3 May, fw_pack_full_5977_170423 fw_170328_013155_MKP7200_ Updated HGST Mars-K+ DriveDB rev.:

2017 _130151.exe HUS72402.zip drive firmware to H3B0. 5977.156000
fw_170328_013202_MKP7400 The update includes
_HUS72404.zip improvements to assert
handling, performance, and
reporting for failure analysis.
5 April, fw_pack_full_5977_170325 fw_170220_145530_REX0040_ Updated Samsung REX DriveDB rev.:

2017 _040905.exe P1635N04.zip PM1633 and PM1635 drive 5977.156000
fw_170220_145940_REX0080_ firmware to EQP9. The
P1635N08.zip update includes
fw_170220_145945_REX0096_ miscompare/DIF error
P1633N09.zip recovery timer modification
fw_170220_145950_REX0160_ and fixes for 04/29 errors
P1635N16.zip during VTOC and Secure
fw_170220_145957_REX0192_ Erase.
P1633N19.zip Updated Seagate
fw_170220_150002_REX0384_ Thunderbolt drive firmware
P1633N38.zip to TS17 to address a scenario
fw_170306_124434_THBA030_ where speed negotiation
STTBSND4.zip could fail.
fw_170306_124914_THBA060_
STTBSND2.zip
fw_170306_124941_THBA120_
STTBSND1.zip
6 March, fw_pack_full_5977_170301 fw_170203_141723_RXA0768_ Updated Samsung REX DriveDB rev.:

2017 _084800.exe PA33N7T6.zip PM1633a high capacity drive 5977.156000
fw_170203_141854_RXA1536_ firmware to EQHA for 7.68TB
PA33N15T.zip and 15.36TB drives. The
update includes
miscompare/DIF error
recovery timer modification
and fixes for 04/29 errors
during VTOC and Secure
Erase.

Table 17 Firmware packs release history (continued)
12 January, fw_pack_full_5977_161207 fw_161026_145003.zip DriveDB support is added for DriveDB rev.:

2017 _180152.exe fw_161111_143301_PM40096_5 Toshiba Phoenix M4 drives. 5977.156000
SRB096C.zip The new drivedb.bin version
fw_161111_143322_PM40192_5 is 5977.156000.
SRB192C.zip Added support for Toshiba
fw_161111_143328_PM40384_5 Phoenix M4 drives with
SRB384C.zip firmware level PC42.
fw_161121_172946_PM30040_ Updated Toshiba Phoenix M3
4SVB040C.zip firmware to PC0D.
fw_161121_173120_PM30080_4 Added support for Samsung
SVB080C.zip REXa low capacity drives
fw_161121_173126_PM30160_4 with firmware level EQL3.
SVB160C.zip Added support for Samsung
fw_161121_173131_PM10096_4 REXa high capacity drives
SRB096C.zip with firmware level EQH9.
fw_161121_173137_PM10192_4
SRB192C.zip
fw_161121_173143_PM10384_4
SRB384C.zip
fw_161111_142440_RXA0768_P
A33N7T6.zip
fw_161111_143253_RXA1536_P
A33N15T.zip
17 October, fw_pack_full_5977_160930 fw_160830_163046_AL4A030_ Updated Samsung REX DriveDB rev.:

2016 _180739.exe AL14EL03.zip LWPD drive firmware to 5977.155000
fw_160830_163104_AL4A060_ EQP8.
AL14EL06.zip Added support for Toshiba
fw_160830_163113_AL4A120_A AL14SE 10K SAS drives with
L14EL12.zip firmware 0C05.
fw_160929_135807_REX0040_ DriveDB support is added for
P1635N04.zip Toshiba AL14SE drives.
fw_160929_135828_REX0080_
P1635N08.zip
fw_160929_135839_REX0096_
P1633N09.zip
fw_160929_135849_REX0160_
P1635N16.zip
fw_160929_135900_REX0192_
P1633N19.zip
fw_160929_135910_REX0384_
P1633N38.zip
fw_160915_003206.zip
12 August, fw_pack_full_5977_160809 fw_160809_140101_REX0080_ Fixed reporting the firmware

2016 _130906.exe P1635N08.zip revision for Samsung REX
800GB drives. The firmware
rex0080_eqp6.bin released
with
fw_pack_full_5977_160712_1
22752 incorrectly reported
the firmware revision as EQP
instead of EQP6.

22 July, fw_pack_full_5977_160712 fw_160624_143628_ssdb.bin.zi Updated Samsung REX SSDB rev.:

2016 _122752.exe p LWPD drive firmware to 0x0022
fw_160610_203604_REX0040 EQP6.
_P1635N04.zip
fw_160610_203720_REX0080_ Added fix for Samsung REX
P1635N08.zip Flash Drives to prevent the
fw_160610_203732_REX0096_ drives from going write
P1633N09.zip disable (logging 882F with a
fw_160610_203756_REX0160_ sense byte of 0B41)
P1635N16.zip triggering host IO timeout
fw_160610_203809_REX0192_ errors AB3E, 283C.
P1633N19.zip
fw_160610_203823_REX0384_
P1633N38.zip
27 June, fw_pack_full_5977_160621 fw_160621_163208_PM30040_ Updated Toshiba Phoenix M3

2016 _130129.exe 4SVB040C.zip firmware to PC0B.
fw_160621_163231_PM30080_
4SVB080C.zip
fw_160621_163305_PM30160_
4SVB160C.zip
fw_160621_163316_PM10096_
4SRB096C.zip
fw_160621_163330_PM10192_
4SRB192C.zip
fw_160621_163342_PM10384_
4SRB384C.zip
10 June, fw_pack_full_5977_160603 fw_160602_181201_SC+0020_ Updated Hitachi Sunset Cove

2016 _153650.exe HUSMH842.zip Plus firmware to C350.
fw_160602_181539_SC+0040_
HUSMM144.zip
fw_160602_181543_SC+0080_
HUSMM148.zip
fw_160602_181546_SC+0160_
HUSMM141.zip
16 May, fw_pack_full_5977_160516 fw_160207_152212_MGL7200_ Updated Seagate Megalodon

2016 _131447.exe ST2000NX.zip firmware to GS1F, HGST King
fw_160207_152225_MGL7400_ Cobra-F firmware to K7P0,
(limited ST4000NX.zip and Toshiba AL13 firmware to
release via fw_160503_170704_AL3E030_ 0B08.
Epack AL13SXB3.zip
only) fw_160505_205506_KCFE030
_HUC15603.zip
10 fw_pack_full_5977_151201 fw_151016_161423_THBA030_S Adding Seagate Thunderbolt

December, _142015.exe TTBSND4.zip (300GB/600GB/1.2TB)
2015 fw_151016_161444_THBA060_ support with firmware TS14,
STTBSND2.zip and updated Seagate
fw_151016_161504_THBA120_S Lightning 10K drives to
TTBSND1CLAR1200.zip firmware LS1F.
fw_151030_163837_LGLA030_
ST300MM0.zip
fw_151030_164210_LGLA060_
ST600MM0.zip

23 fw_pack_full_5977_151016_ fw_150928_175518_SC+0020_ Added support for HGST

October, 101126.exe HUSMH842.zip Sunset Cove Plus drives
2015 fw_150928_175527_SC+0040_ (with firmware level C29C),
HUSMM144.zip and updated firmware
fw_150928_175532_SC+0080_ (JS0D) for Seagate
HUSMM148.zip YellowJacket drives.
fw_150928_175538_SC+0160_
HUSMM141.zip
fw_150928_171413_YJTE030_S
T930065.zip
25 fw_pack_full_5977_150918 fw_150910_190329_CBFA030_ Full support is introduced for

September _110905.exe HUC10183.zip HGST Cobra-F 10K drives
, 2015 fw_150910_190342_CBFA060_ with HYPERMAX OS
HUC10186.zip 5977.691.684.
fw_150910_190353_CBFA120_ NOTE: This Firmware Pack is
HUC10181.zip not available as a standalone
update, only as part of
HYPERMAX OS
5977.691.684.
25 May, fw_pack_full_5977_150519 fw_150511_144129_AL3E030_A Added new drive support for

2015 _115505.exe L13SXB3.zip Toshiba AL13SX 15K 300GB
SAS drives.
28 April, fw_pack_full_5977_150422 N/A The following files are

2015 _083420.exe removed from the Firmware
Pack:
fw_141205_173712.zip
fw_150217_160649.zip
fw_150220_155838_KCFE0
60_HUC15606.zip
fw_141212_212429_KCFE06
0_HUC15606.zip
The previously released

fw_pack_full_5977_150404_
074605.exe is recalled and
replaced by the new
fw_pack_full_5977_150422_
083420.exe
2 March, fw_pack_full_5977_150220 fw_150217_160649.zip Removed support for King

2015 _124910.exe fw_150220_155838_KCFE060_ Cobra-F 15K SAS 600 GB
HUC15606.zip 2.5 drives.
9 January, fw_pack_full_141218_11353 fw_141205_173712.zip Adding drive support for King

2015 3.exe fw_141212_212348_KCFE030_ Cobra-F 15K SAS 300 GB
HUC15603.zip and 600 GB 2.5 drives.
fw_141212_212429_KCFE060_
HUC15606.zip

Manifest
Manifest
Table 18 lists the level of each application included in this Service Pack. In this Service
Pack, the applications that have changed to support All Flash are:
SymCLI RT
Tools Guest
eNAS Guest
DM Guest
Management Guest
Table 18 Manifest for Service Pack 5977.952.892 ID# 6326
Table 19
Application Level
Build 5977-952-892-6420.exe
Built On May 30, 2017 12:02:08
Installer Script Version 5977.706
SymmWin 5977_892/5028
uCode Registered Build 5977_952/0120
Firmware Pack V.fw_pack_full_5977_170516_134535
Tools Guest V.8.3.0.328
McAfee xDAT V.8218
Chat Server V.14.053
SGDB Agent V.10.23
SymCLI RT V.V8.3-2252-0.0
ConnectEMC V.5.04.18
SSCKeyClient V.3.3.0.0
EMCRemote V.7.15.02
SSC V.3.1.0.10
Remotely Anywhere V.3.00.18
Tomcat V.9.77.2.0.3.269
Simplified SymmWin V.9.77.2.0.3.269
PXE V.8.3.0.305
RSync V.1.4.0.0
EGCB V.1.132
MMCS Image V.MMCS0509
Firewall Configuration Tool V.1.1.5

Manifest
Table 19
Application Level
Firewall Rules V.1.0.6
eNAS Guest V.8.1.11.282
DM Guest V.8.1.11.282
Management Guest V.1.3.0.308
Installer MD5 570625d4b2f16c31c09dd966de0c192f
Tools MD5 1bf1451507ec0063fc373a91a35dffca
eNAS MD5 7d9442fe058a6ab809afd9fd93f0c637
DM MD5 93fad8abb21cd6e8822530b941dc28a2
Management MD5 1a1394253c802419342cf1701f3e58e4
Image MD5 6528e31eb39999ad971b39dbc8c20210

Troubleshooting and getting help

EMC support, product, and licensing information can be obtained at EMC Online
Support.
Note: To open a service request through EMC Online Support, you must have a valid
support agreement. Contact your EMC sales representative for details about obtaining
a valid support agreement or to answer any questions about your account.
Product information
For documentation, release notes, software updates, or for information about EMC
products, licensing, and services, go to EMC Online Support (registration required) at:
https://support.EMC.com
Technical support
EMC offers a variety of support options.
Support by Product EMC offers consolidated, product-specific information on the
Web at:
https://support.EMC.com/products
The Support by Product web pages offer quick links to documentation, white papers,
advisories (such as frequently used Knowledgebase articles), and downloads. It also
provides more dynamic content, such as: presentations, discussions, relevant
Customer Support Forum entries, and a link to EMC Live Chat.
EMC Live Chat Open a Chat or instant message session with an EMC Support
Engineer.
Symmetrix System Viewer Illustrates the system hardware, incrementally
scalable system configurations, and available host connectivity offered for VMAX3
systems. To download this standalone utility, go to EMC Online Support.
eLicensing support
To activate your entitlements and obtain your array license files, visit the Service
Center on https://support.EMC.com, as directed on the License Authorization Code
(LAC) letter e-mailed to you.
For help with missing or incorrect entitlements after activation (that is, expected
functionality remains unavailable because it is not licensed), contact your EMC
Account Representative or Authorized Reseller.
For help with any errors applying license files through Solutions Enabler, contact the
EMC Customer Support Center.
If you are missing an LAC letter, or require further instructions on activating your
licenses through EMC Online Support, contact EMC's worldwide Licensing team at
licensing@emc.com or call:
North America, Latin America, APJK, Australia, New Zealand: SVC4EMC
(800-782-4362) and follow the voice prompts.
EMEA: +353 (0) 21 4879862 and follow the voice prompts.

Copyright 2017 Dell Inc. or its subsidiaries. All rights reserved.
Published June, 2017
Dell believes the information in this publication is accurate as of its publication date. The information is subject to change without
notice.
THE INFORMATION IN THIS PUBLICATION IS PROVIDED AS-IS. DELL MAKES NO REPRESENTATIONS OR WARRANTIES
OF ANY KIND WITH RESPECT TO THE INFORMATION IN THIS PUBLICATION, AND SPECIFICALLY DISCLAIMS IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. USE, COPYING, AND DISTRIBUTION OF
ANY DELL SOFTWARE DESCRIBED IN THIS PUBLICATION REQUIRES AN APPLICABLE SOFTWARE LICENSE.
Dell, EMC, and other trademarks are trademarks of Dell Inc. or its subsidiaries. Other trademarks may be the property of their
respective owners. Published in the USA.

Docu82501 - VMAX3 Family With HYPERMAX OS 5977 Operating Environment ReadMe For HYPERMAX OS Service Packs Release Level 5977.952.892 PDF

Transféré par

Informations du document

Titre original

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

Docu82501 - VMAX3 Family With HYPERMAX OS 5977 Operating Environment ReadMe For HYPERMAX OS Service Packs Release Level 5977.952.892 PDF

Transféré par

Droits d'auteur :

Formats disponibles

HYPERMAX OS SERVICE Pack README

EMC VMAX3 Family and VMAX All Flash

Release Level 5977.952.892 ID# 6420

ReadMe revision history

Table 1 ReadMe revision history

Revision Date Description

01 February 13, First release of EMC Proactive HYPERMAX OS Pack ReadMe

02 April 5, 2017 Second release of EMC Proactive HYPERMAX OS Pack ReadMe

03 June 5, 2017 Third release of EMC Proactive HYPERMAX OS Pack ReadMe

04 June 8, 2017 Corrected description of 94102.

Note: The HYPERMAX OS Service Pack ReadMe document contains technical

2 HYPERMAX OS Release Level 5977.952.892 Service Pack ReadMe

Service Pack release history

Table 2 HYPERMAX OS Service Pack revision history

HYPERMAX Service HYPERMAX OS SymmWin reg. Fix numbers/OPT Full Firmware

02/13/17 5977.952.892 6243 5977_952/0015 5977_892/5009 20018683, 20018833, V.fw_pack_full_5

HYPERMAX OS Release Level 5977.952.892 Service Pack ReadMe 3

Table 2 HYPERMAX OS Service Pack revision history (continued)

HYPERMAX Service HYPERMAX OS SymmWin reg. Fix numbers/OPT Full Firmware

04/05/17 5977.952.892 6326 5977_952/0056 5977_892/5020 20018683, 20018833, V.fw_pack_full_5

4 HYPERMAX OS Release Level 5977.952.892 Service Pack ReadMe

Table 2 HYPERMAX OS Service Pack revision history (continued)

HYPERMAX Service HYPERMAX OS SymmWin reg. Fix numbers/OPT Full Firmware

06/05/17 5977.952.892 6420 5977_952/0120 5977_892/5028 20018683, 20018833, V.fw_pack_full_5

HYPERMAX OS Release Level 5977.952.892 Service Pack ReadMe 5

* Fix 94523 in Service Pack #6420 replaces fix 93425

6 HYPERMAX OS Release Level 5977.952.892 Service Pack ReadMe

Service Pack overview

HYPERMAX OS Release Level 5977.952.892 Service Pack ReadMe 7

83480246 92787 When a VMAX source device has 16 Potential N/A

512164SYM 92445 An online engine upgrade activity may Potential N/A

Errors: BE3E.4A, BE3E.48

Errors: BE3E.48, BE20.45, BE20.50,

8 HYPERMAX OS Release Level 5977.952.892 Service Pack ReadMe

Table 3 Base Functionality (continued)

511221SYM 92197 During an Online Engine upgrade the Potential N/A

The problem is triggered only if all of the

82609022, 92141 During SNAPVX LINK operations and if Potential 491216

RAID5 7+1 configurations are more

82453818, 92161 On VMAX arrays configured with RAID6 Potential N/A

Errors: AD3E, CE3E, DADA

The discrepancy between the Flash and

HYPERMAX OS Release Level 5977.952.892 Service Pack ReadMe 9

Table 3 Base Functionality (continued)

84300212, 92048 During a VMAX Online Engine Upgrade Potential N/A

81808528 91668 Issuing EMC internal inline "ITAC" Potential N/A

10 HYPERMAX OS Release Level 5977.952.892 Service Pack ReadMe

Table 3 Base Functionality (continued)

82444662 92888 When a Non-Disruptive Migration (NDM) Potential 492880 Added on

This problem may trigger when LREP

HYPERMAX OS Release Level 5977.952.892 Service Pack ReadMe 11

Table 3 Base Functionality (continued)

12 HYPERMAX OS Release Level 5977.952.892 Service Pack ReadMe

Table 3 Base Functionality (continued)

Exposed Environment: SLIC

85194678 518525 EEM Struts 2 DSA Component No Impact 497270 Added on

HYPERMAX OS Release Level 5977.952.892 Service Pack ReadMe 13

Table 3 Base Functionality (continued)

83917976 94371 On arrays running HYPERMAX OS Potential N/A Added on

Exposed Environments: Thin

Errors: xx3C AB3E

85225602, 94113 An online configuration change for Potential 498506 Added on

Errors: 10BC, BE10