Docu21183 Symmetrix DMX Model 800 1000 2000 3000 EMC Enginuity Release Notes

R E L E A S E N OT E S Symmetrix DMX Model
800/1000/2000/3000
EMC Enginuity
Release Level 5671.32.36
Release Notes
P/N 300-002-406
Rev A02
March 31, 2005
GA Date: 3/31/2005
Revision History: The A02 revision update includes:

Updates to the A01
version of the 5671.32.36 Page 30 - Added the condition " To support more than 8000 devices,
release notes. Solutions Enabler must be upgraded to version 6.0 or higher prior to
NDU." as the third bullet of the Online Non-Disruptive Upgrades
(NDU) General Rules.
These release notes contain supplemental information about EMC

Symmetrix Enginuity release level 5671.32.36. Topics include:
Product Description ............................................................................ 2
New Features and Changes ............................................................... 4
Environment and System Requirements ...................................... 14
Known Problems and Limitations ................................................. 15
Technical Notes .................................................................................. 29
Documentation .................................................................................. 32
Software Media, Organization, and Files ..................................... 34
Troubleshooting and Getting Help................................................ 35
Refer to the EMC Powerlink website at http://powerlink.emc.com for
updates to this document. EMC updates these release notes for each new
generally available version or release and to present newly discovered
information.
1
Product Description
Product Description
This is a new release of Symmetrix Enginuity. The 5671 platform
supports Symmetrix DMX 800, 1000, 2000, and 3000 at emulation
level 32 and Service Processor level 36. Details of the New features
are provided in New Features and Changes on page 4.
Symmetrix Enginuity is the operating environment for the
Symmetrix DMX series. Enginuity manages and ensures the optimal
flow and integrity of information through the different hardware
components of the Symmetrix system.
Enginuity manages all Symmetrix operations, including monitoring
and optimizing internal data flow, ensuring the fastest response to
the user's requests for information, and protecting and replicating
data.
Enginuity provides the following services for the Symmetrix DMX
series:
Manages system resources to intelligently optimize performance
across a wide range of I/O requirements.
Ensures system availability through advanced fault monitoring,
detection, and correction capabilities. Enginuity also provides
concurrent maintenance and serviceability features.
Interrupts and prioritizes tasks from microprocessors and, for
example, ensures that fencing off failed areas takes precedence
over other operations.
Offers the foundation for specific software features available
through EMCs disaster recovery, business continuance, and
storage management software.
Provides functional services for both its host Symmetrix series
and for a large suite of EMC storage application software.
Defines the priority of each task, including basic system
maintenance, I/O processing, application processing (for
example, EMC ControlCenter SRDF, TimeFinder, and EMC
ControlCenter Symmetrix Optimizer).
Provides uniform access through APIs for internal calls and
provides an external interface to allow integration with other
software providers and independent software vendors.
2 EMC Enginuity Release Level 5671.32.36 Release Notes

Product Description
Naming Enginuity platform releases are denoted by a four-digit sequence. The

Conventions first two digits indicate the product supported and the second two
digits indicate sequential changes to the platform.
An Enginuity platform release that begins with a two-digit
sequence of 56 indicates that this platform supports the
Symmetrix DMX 800, 1000, 2000, and 3000.
Symmetrix 8430, 8730, 8230, 8530, and 8830.
Symmetrix 3300/5300, 3400/5400, and 3700/5700.
Symmetrix 3100/5100, 3200/5200, and 3500/5500.
Symmetrix 4200, 4400, and 4800.
Enginuity release level names follow a naming convention of
XXXX.EE.SS, where:
XXXX is the four-digit platform number (as described above)
EE is the two-digit emulation number
SS is the two-digit Service Processor number
For example, 5671.32.36 indicates the:
5671 platform, which is the Symmetrix DMX series
Emulation level is 32
Service Processor level is 36
EMC Enginuity Release Level 5671.32.36 Release Notes 3

New Features and Changes

The modular design of Enginuity permits EMC to build upon
previous serviceability and feature enhancements which allows the
release of new and enhanced Enginuity revisions quickly and easily.
EMC thereby extends the functionality of Enginuity and improves its
reliability with each platform release.
EMCs policy is to provide Symmetrix Enginuity enhancements,
features, and fixes to the customer as quickly as possible by following
an ISO 9001-approved process. New Enginuity releases provide
continuous improvement in performance, reliability, and availability
and are used as tools to manage hardware, software, and Enginuity
more effectively. In this way, customers can keep pace with new
features and enhancements and participate in the continuous
improvement process.
Problem Fix Changes to Symmetrix Enginuity made as a result of problem fixes

Definitions are presented in tabular format. The following information is
included for each fix:
Issue Number Refers to the issue number assigned to the customer reported
problem or the EMC-internal problem tracking number.
Fix Number The unique code number used to track individual changes.
Feature Type The primary Enginuity feature affected. Fix information is grouped
alphabetically by feature type.
Additional Feature Secondary or additional Enginuity features affected by the change.

Type Those fixes that have an additional feature type are presented under
the headings for both the primary and secondary feature affected.
EMC Knowledgebase Refers to the EMC Knowledgebase articles that contain information
ID related to the problem solution.
Impact Level EMC uses a rating system to prioritize the importance of upgrading
to a newer release level within an Enginuity platform. These are
defined below.
Critical (Severity 1). A Critical fix addresses a potentially serious
problem that may have an immediate impact on the customer
site. For Critical fixes, EMC employs a process to ensure the rapid
dissemination of information and implementation of a release.

The primary Customer Engineer or Regional Technical Specialist

will meet with the customer to review the impact of the problem
and the fix on the customers operating environment and to
recommend an upgrade at the earliest opportunity. The customer
determines whether to perform the upgrade. However, if the
customer chooses not to perform certain recommended upgrades,
such as those required to correct a Critical issue, EMC may be
unable to support the customer environment.
Medium (Severity 2). A fix with a rating of Medium includes
reliability improvements, serviceability changes, and new
features. A fix with a Medium rating should be installed at the
next planned site activity. The primary Customer Engineer will
review the Enginuity release notes with the customer during
normally scheduled planning meetings. If the customer has down
level Enginuity installed (more than four release levels old), the
Customer Engineer will initiate actions comparable to a Critical
upgrade.
Low (Severity 3). A fix with a Low rating level usually resolves
specific customer-defined issues and/or provides routine
enhancements. Each customer should analyze fixes with a Low
rating level on a case-by-case basis to determine its impact. In
conjunction with the customer, the primary Customer Engineer
will determine when site-specific action should be taken.
Symptom A brief description of the observable system behavior that is

addressed by the fix.
Host Type Identifies specific host types affected by the change, or indicates that
changes are not related to any specific host type.
Host OS Identifies the specific host operating system that are affected by the
fix, or indicates that fixes are not related to any specific operating
system.
Impact Statement A brief statement of the impact to expect if the fix described is not
implemented.
Special Conditions An indication of the likelihood the symptom will occur, and under
what conditions the symptom can be expected to appear.
Problem Summary A description of the problem identified and resolved by the fix.
Fix Summary A description of the fix that resolved the problem.

New Features This section identifies:

New features and enhancements to existing functionality
This section details the changes implemented by the current release.
None
Problem Fixes This section details the changes implemented by the current
Enginuity release level. The following Enginuity features are affected:
Base Functionality................................................................................ 6
Mainframe PPRC ................................................................................. 9
SRDF Family ........................................................................................ 11
SymmWin............................................................................................ 12
TimeFinder.......................................................................................... 13
Base Functionality
Issue Number 199920SYM
Fix Number 25927
Feature Type Base Functionality
Additional Feature Type None
EMC Knowledgebase ID None
Impact Level Medium
Symptom Add an enhancement to Enginuity 5671 to allow the system to

detect when to use message bus mode for sequential read
tasks.
Host Type Any host type
Host OS Any operating system
Impact Statement Performance

Issue Number 199920SYM (continued)
Special Conditions None
Problem Summary Add an enhancement to Enginuity 5671 to allow the system to

detect when to use message bus mode for sequential read
tasks.
Fix Summary The fix turns on RAID 5 parallel prefetch and adds a switch
which can be adjusted between parallel prefetch and message
mode.
Issue Number 12538460
Fix Number 26381
EMC Knowledgebase ID emc83494
Impact Level Medium
Symptom Add an enhancement so the director will reprogram the M5

memory board once it is detected that the memory board has
lost programming.
Impact Statement None
Problem Summary The director should reprogram the M5 memory board once it is
detected that the board has lost programming.
Fix Summary When a director detects that a memory board has lost
programing it will send a message alerting all directors of the
problem and then the director will reprogram the memory board
with the data saved in the NVD.
Fix Number 27085

Impact Level Medium
Symptom The customer may encounter errors during an IML.
Impact Statement Potential Data Unavailability
Problem Summary The test area in the 4D test on CPU A may potentially use the
test area in test 4C on CPU B. The test area (for each CPU) is
not aligned.
Fix Summary The fix makes sure tests 4D and 4C use the same test buffer
and that there are indicators in the test data to identify CPU and
test.
Fix Number 27264
Impact Level Critical
Symptom Certain maintenance commands are returning a not done

status. This is only when used in a particular parameter. Other
parameters work correctly.
Impact Statement Maintenance Issue

Problem Summary The commands to invalidate and validate a single track on a

disk director or remote director do not work. This only applies in
the P1 parameter. If used in the P3 parameter it works as usual.
Fix Summary The fix solves the problem with an earlier flag that was not
thoroughly removed from the routine and has now been
replaced.
Fix Number 27444
Impact Level Medium
Symptom The customer encountered no problems.
Problem Summary When attempting to validate or invalidate an entire volume

using EC0/EC1, the D0 command occasionally returns a "NOT
DONE 0A", but still appears to have completed the task.
Fix Summary Fixed the problem of the D0 command occasionally returning

an incorrect error.
Mainframe PPRC
Fix Number 27007
Feature Type Mainframe - PPRC
Additional Feature Type SRDF/A

Issue Number 12534203 (continued)
Impact Level Medium
Symptom The customer may encounter PPRC Establish failures when

SRDF/A is active in the same Symmetrix or when running
multiple PPRC Establishes at the same time.
Host Type Any Mainframe host
Host OS Any Mainframe operating system
Impact Statement Application Failure
Problem Summary When trying to lock a table for SRDF/A but the table is already
locked that turns into a failure of the PPRC establish command.
Fix Summary The fix changes the method by which we do the table lock so
the Establish commands will not fail.
Fix Number 27396
Feature Type MainFrame - PPRC
Impact Level Medium
Symptom The TSO CQUERY and GDPS CQUERY sometimes show the
primary SSID value of 0000 from a query of the secondary
Symmetrix DMX.
Host Type Any Mainframe host.
Host OS Any Mainframe operating system

Problem Summary A CQUERY done on the Primary side displays the Primary and
Secondary CU SSIDs correctly, whereas the CQUERY on the
Secondary Side displays the Primary CU SSID as 0000.
Fix Summary Fixed the CQUERY routine for the secondary side of the PPRC
pair.
SRDF Family
Fix Number 27198
Feature Type SRDF Family
Symptom Add back the call to the function that set the R1 to R2 copy
threshold.
Problem Summary The capability to set the disk adapter copy threshold was
mistakenly removed from Enginuity 5671.
Fix Summary The fix adds back the call to the function that set the R1 to R2
copy threshold.

SymmWin
Fix Number 20002600
Feature Type SymmWin
Symptom Add new IMPL flags
Impact Statement None
Problem Summary Add a new flag "alg_pf_rec_for_msg_mode" and change the

default value for "alg_da_max_seq_pf_tracks" from "2" to "4".
Fix Summary The fix added new flags to the IMPL routine. The fix added new
flags to the IMPL routine.
Fix Number 20002969
Feature Type SymmWin
Additional Feature Type Online Maintenance Procedure
Impact Level Medium
Symptom The customer may encounter potential Data Unavailibility

during the recovery of memory mapping after a memory board
replacement.
Impact Statement Potential Data Unavailability

Problem Summary During an online memory remove, the F4,ISAV command is not
issued. This leaves an incorrect copy of the memory segment
tables in the NVD of all directors.
Fix Summary The fix changes the memory remove procedure to save the
memory map prior to removal.
TimeFinder
Fix Number 27032
Feature Type TimeFinder
Symptom The customer may encounter Data Loss or Data Unavailability

during an instant restore.
Impact Statement Potential Data Loss or Data Unavailability
Problem Summary The instant restore scrubbing (clean up) routine is not working
properly. Scrubbing is slow and may not finish causing possible
Data Loss or Data Unavailability. It can also additionally be
responsible for the loss of disk adapters.
Fix Summary Fixed the problem with the instant restore scrubbing routine.

Environment and System Requirements
Environment and System Requirements

Enginuity 5671.32.36 provides new features and enhancements to
mainframe and open systems environments. For detailed information
on environment and system requirements, when the Enginuity is
released for general availability (GA), review the EMC Support Matrix
at http://powerlink.emc.com.

Known Problems and Limitations

This section identifies:
Limitations to the functionality of this release
Other issues, such as known performance limits under certain
conditions
Product Updated Number Limitation
Base Functionality N 500.02 When RAID 5 is configured, cache slot lock timeouts and timeouts on the host
directors can occur during Disk Adapter, PBC, LCC or FEBE replacements.
N 500.03 During an emergency power down using the red (EPO) switch, all data may not
destage in cache and data loss may occur.
N 500.05 Virtual Devices and SAV are no longer options in the SymmWin volumes map
under Special Types. New virtual or SAV devices must be added or existing
volumes must be deleted and re-added as virtual or SAV volumes.
N 500.06 Attempting to expand a striped Meta Group may cause a failure.
BS2000 N 1200.01 For a 2105 controller type, MOD-27 devices can only be configured for attached
MVS systems. Since BS2000 mainframes do not support MOD-27 devices, CKD
devices with more than 32,000 cylinders cannot be configured for BS2000 in this
case.
N 1200.03 Minimum version V4.0A07 of BS2000/OSD software, SHC-OSD is required to

manage the TimeFinder and SRDF features from the host.
N 1200.04 BS2000/OSD only supports up to 7 aliases per device, but tolerates 15. If 15
aliases are configured on the Symmetrix, the following corrections on BS2000
are required: A0521999 for VM2000 V7.0 and A0522283 for SM2 as of
V14.0B02. The 15 aliases only have been tested with OSD V5.0C and OSD
V6.0.
N 1200.05 Minimum version V4.0A07 of BS2000/OSD software SHC-OSD is required to

manage TimeFinder with RAID 5 BCVs from the host.
N 1200.06 Online code upgrades must be performed with minimum I/O load. This applies to
upgrades from 5670 and within the 5671 code family.
iSeries (AS/400) N 100.01 When moving AS/400 devices from one Auxiliary Storage Pool (ASP) to another,
the mirror resynchronization of the devices must complete before moving the
same devices again.
iSeries (AS/400) N 2000.01 SRDF/TimeFinder Manager is not supported with 5671 code.
Software
N 2000.02 CopyPoint is not supported with 5671 code.

Mainframe N 620.01 An Amdahl Host cannot run SynchSort on a Symmetrix DMX over FICON
channels unless the Amdahl CPU IU pacing fix is included in channel code
FNM, level L41387.
N 620.02 Connecting both ESCON ports A and B on the same processor is not supported.
The support is limited to a single port on each processor.
N 620.03 FDR Compaktor jobs may intermittently fail. Enginuity incorrectly rejects some
extents.
N 620.04 For non-standard sized CKD device sizes, such as mod 2-, FDR jobs may issue
commands with an invalid cylinder number. The command is rejected, but the job
retries successfully.
Offline Code N 1300.01 The Symmetrix DMX must be running Enginuity 5670.83.78 (or higher) prior to
Upgrades upgrading to 5671 Enginuity using the offline code load procedure.
Online N 210.02 The maximum number of CKD addresses (including aliases) which can be
Configuration mapped or unmapped from an ESCON and/or FICON adapter in a single
Change upgrade cannot exceed 2,580 (assuming each base address has the maximum
allowable 16 alias addresses).
Online Maintenance N 810.02 If a Front End/Back End (FEBE) director is missing from the Symmetrix, or a
Procedures FEBE in the Symmetrix is disabled for an extended period of time, the Symmetrix
may incorrectly log a power-loss notification. The Symmetrix will continue to
function.
N 810.03 In SRDF Family environments, the SymmWin procedure to replace a director

may require manual intervention when replacing a Remote Adapter. The SRDF
link may not find a valid system attached because the validity information was
cleared.
N 810.04 If the SymmWin procedure to set the time or date is run immediately after
updating the time or date on the service processor, the SymmWin procedure will
fail. Re-boot the service processor after changing the time and date to prevent
the failure.
N 810.06 Drive code load maintenance procedures must be done with I/O limited to 100
I/O per second per Disk Adapter CPU.
N 810.09 The amount of time needed to complete the SymmWin procedure to Remove a
Dynamic Spare is directly impacted by the number of invalid tracks remaining to
copy to the spare and the I/O for the disk being removed from the spare device.
Online N 700.01 Please refer to the Technical Notes section of the release notes for a complete
Non-Disruptive list of limitations and requirements.
Upgrades (NDU)
N 700.03 Re-SNAP transactions must not run during an online upgrade. This causes file
TimeFinder errors as re-SNAP cannot close the SDDF session on the source.

N 700.05 Online Non-Disruptive Upgrades are not supported on systems with ESCON
adapters where both A and B ports are connected.
Open Replicator N 400.01 No more than 128 active Open Replicator sessions are supported at any stage.
N 400.02 Online configuration changes to Open Replicator devices is restricted. A

maximum of 128 active sessions is allowed. After a fast IML, director ceiling
values are reset.
N 400.03 Open Replicator sessions may not resume automatically after a power loss and
may fail during a power cycle recovery.
N 400.04 An online upgrade or online code load has the potential to cause the SET
PROTECTION BIT step to fail during the fast IML. The SET PROTECTION BIT
step will need to be restarted.
N 400.05 Open Replicator sessions should not be defined, suspended or re-created when
the Write Pending count is over 50 percent.
N 400.06 During a Hot Open Replicator Pull session, newly written data to the active
Symmetrix Open Replicator device can be lost in the event of an adverse failure.
The gold copy on the source storage device is unaffected and the session can be
restarted.
Optimizer N 1800.01 Optimizer is not supported on a Symmetrix running Enginuity 5568 or 5670 when
there is an SRDF link to a remote Symmetrix running Enginuity 5671 with more
than 8,000 logical volumes.
Persistent Group N 610.01 PGR devices are not supported for more than 8,000 of the 16,000 possible
Reservation (PGR) devices in the entire Symmetrix. I/O is limited to no more than 70,000 I/O's per
second.
SRDF Family N 300.01 SRDF Family deployments over extended distance using IP are required to follow
the Site Qualification (SQ) process. The Solutions Validation Center - Business
Continuance (SVC BC) group manages this process.
N 300.02 Please refer to the Technical Notes section of the release notes for a complete
list of limitations and requirements when performing Online Non-Disruptive
Upgrades with the SRDF Family.
N 300.03 Online Enginuity upgrades are not recommended while running PPRC
commands as the commands may time out.
N 300.04 If a non-protected R2 device enters a not ready state, the R1 device on the
remote Symmetrix link may become not ready before a hot spare can be fully
invoked against the R2 device.
N 300.05 Recovery from failure of two or more members of a RAID 5 R1 device may result
in XOR errors and RAID devices on the same physical disk becoming not ready.

N 300.07 Concurrent SRDF, Parity RAID, and R1 to larger R2 are not supported with
PPRC operations.
N 300.09 SRDF pairings are limited to the highest Symmetrix serial number that the oldest
code supports. Only the first 8,000 devices of the Symmetrix 5671 to the
Symmetrix 5670 can be linked. This is true for both Static and Dynamic SRDF.
N 300.10 Static SRDF devices cannot be added or removed in an RDF group that contains
more than 0x800 (2048) devices. This restriction applies to all ESCON, Fibre,
and GigE link connections.
N 300.11 A minimum release level of Enginuity 5568.67.26 is required on the Symmetrix 5

to connect to a Symmetrix DMX running Enginuity 5671.
N 300.12 Symmetrix systems running Enginuity 5267 or 5567 require patch 23600 for
SRDF connections to a Symmetrix DMX running Enginuity 5671.
SRDF/A N 360.01 Transition to Journal 0 mode of operation with ESCON FarPoint of distances
greater than 100 miles may cause timeouts.
N 360.02 If a non-protected R2 device enters a not ready state, the R1 device on the
remote Symmetrix link may become not ready before a hot spare can be fully
invoked against the R2 device.
N 360.03 Please refer to the EMC Solutions Enabler V6.0 Release Notes (P/N
300-002-095 Rev A01) for limitations and restrictions related to creating
TimeFinder/Clones or TimeFinder/Snaps of R2 volumes while running SRDF/A.
N 360.04 Only one Concurrent SRDF mirror can be in SRDF/A mode.
N 360.05 Solutions Enabler does not allow Concurrent SRDF and BCV devices in the
same Composite Group.
N 360.09 The Open Systems and Mainframe Multi-Session Consistency (MSC) will not
work together to control the same sessions.
N 360.10 The Open Systems and Mainframe software will not work together to control the
same sessions.
N 360.11 The minimum Symmetrix Control Facility version is scf540 with the sf540a3
maintenance patch applied. The minimum SRDF version is srdf530 with the
sr53002 maintenance patch applied.
N 360.12 A Gatekeeper device is required and cannot be an SRDF, BCV, FBA, SRDF/A,
Virtual or Dynamic SRDF device.
N 360.13 The maximum number of sessions is 64 sessions per Symmetrix and eight
sessions per Remote Adapter.
N 360.14 Consistent Deactivate for a MSC group is not supported for Mainframe.

N 360.15 Consistent Deactivate for a MSC group is not supported for open systems hosts.
N 360.16 TimeFinder/Clones or TimeFinder/Snaps of R2 volumes are not supported in

Mainframe environments.
SRDF/Star N 370.01 Automated procedures for SRDF/Star are not currently available.
N 370.02 Please refer to the SRDF/Star for z/OS - An Implementation and Usage Primer,
Version 1.0, Rev A01 (P/N 300-002-264) for more information.
N 370.03 Any SRDF/Star configuration which links more than five Symmetrix systems
requires an RPQ.
N 370.04 SRDF over ESCON is not supported with SRDF/Star
Symmetrix Data N 350.01 Symmetrix Data Migration Service is limited to the first 8,000 volumes with a
Migration Service range of 0 7,999 devices.
(SDMS)
Symmetrix Data N 340.01 Symmetrix Data Mobility Manager (SDMM) is not supported.
Mobility Manager
(SDMM)
Symmetrix DMX 800 N 510.01 Enginuity 5671 can not be installed on a Symmetrix DMX 800 if more than one
Symmetrix is being controlled by a single service processor.
TimeFinder Family N 1000.01 During a TimeFinder Restore to a RAID 5 standard device, invalid tracks may
occur on some data mirrors.
N 1000.02 A TimeFinder Restore to a degraded RAID 5 device does not complete if the
device is degraded after the copy starts.
TimeFinder/Clone N 1010.03 Running a TimeFinder/Clone on CKD devices from an open systems host is not
supported.
N 1010.04 No online IMLs (code loads or configuration changes) can be run while a
TimeFinder Clone establish or restore operation is active.
N 1010.05 RAID 5 BCV Clone Emulation for Mainframe is not supported.
N 1010.06 Solutions Enabler does not allow the use of striped CKD Meta devices in
TimeFinder/Clone.
N 1010.07 Solutions Enabler does not allow the use of CKD devices in TimeFinder/Clone
emulation mode unless patch 26469 is loaded.
TimeFinder/Mirror N 1020.03 If AC power is lost while a TimeFinder establish is in progress, a mirror device
may become not ready on a subsequent IML.
TimeFinder/Snap N 1030.02 Solutions Enabler does not allow the use of Striped CKD Meta devices in
TimeFinder/Snap.

N 1030.03 VSNAP from a SRDF/A R2 device is not currently supported.
N 1030.04 Some virtual restores and persistent restores may not complete.
N 1030.05 A sanity check error may appear indicating a mismatch between the pyramid and
the write_request bitmaps. The errors are recoverable and they must be
investigated and addressed. These errors only occur on Meta devices.
N 1030.06 Data with a non-standard R0 is not copied to the target correctly.
N 1030.07 Inline commands (E8) on a virtual device with a virtual restore session that is not
completing may log a CKD format error.
Viewing Issues with 1. Issues for Symmetrix DMX now appear online with the EMC
EMC Issue Tracker Issue Tracker which is available on the EMC Powerlink
website:
http://powerlink.emc.com/
Issue Tracker has the ability to export search results to Microsoft
Excel.
This section provides information on how to:
Access and find Issue Tracker on Powerlink
Create and view Issue Tracker searches and results
View issue details
With Issue Tracker you can look up the following types of
ControlCenter issues:
Open (existing) issues in Symmetrix DMX
Customer and other issues fixed with Enginuity 5670.80.75 and
above
Logging On to To access Issue Tracker, you must log on the EMC Powerlink website.
Powerlink Follow these steps:
1. From a browser, connect to Powerlink at
http://powerlink.emc.com

2. Enter your valid Powerlink username and password on the User

Login dialog box. If you are a new Powerlink user, select New
Member Registration, and a username and password will be
sent to you by e-mail.
Figure 1 User Login
3. Click Login to open the Powerlink home page. If a security

message appears, click Yes to continue.
Opening Issue To open Issue Tracker from the Powerlink home page:
Tracker 1. Click the Support tab to display the Support home page.
2. Select Issue Tracker from the Self Help section of the Support
home page to display the Issue Tracker Search screen, Figure 2
on page 22.
You can select Issue Tracker Help from the upper right corner of all Issue
Tracker screens.

Figure 2 Issue Tracker Search Window
If you know the Issue Number, you can enter it in the Quick Search
field to display the issue details. For more information, refer to Quick
Search on page 26.
To search for all, or a selection of Symmetrix DMX-related issues, you
must first select Symmetrix DMX from the Product drop-down
menu. The Issue Tracker screen refreshes after product selection and
you can then search for Symmetrix DMX issues according to your
desired criteria.
For additional search information refer to Additional Search Options on
page 26.

Viewing all Symmetrix DMX-related Issues

To view a list of all Symmetrix DMX-related issues (Open and Fixed):
With Symmetrix DMX selected as Product, accept the default
selections, and then click Submit. A list of all Symmetrix
DMX-related issues appear on an Issue Tracker Results screen.
Printing Issue Tracker To export your results to Microsoft Excel for viewing or printing,
Results select Excel from the drop-down menu in the Output To: field of the
Issue Tracker Search screen, and then print the Excel output.
Figure 3 Issue Tracker Search Results
Table 1 describes the fields that appear in Issue Tracker Results.
Table 1 Fields in Issue Tracker Search Results
Column Brief Description
Issue Number An unique case number used to track the product issue. If
you reported the problem to EMC Customer Support, use
the case number.
Product EMC product name, for example, Symmetrix DMX.
Problem Summary Brief summary of the product issue.

Table 1 Fields in Issue Tracker Search Results (continued)
Column Brief Description
Product Feature Product feature categories that vary for individual EMC
products. For example, SRDF/A is a feature listed for
Symmetrix DMX.
Fixed In Version Enginuity version which includes a fix for the issue.
Fixed in version field remains blank until the issue is fixed.
Impact Level Impact of the issue. Impact levels include: Critical,

Medium, Low, and Enhancement.
Status Status of the issue being reported, including:

OpenEscalated to EMC Engineering and under
investigation.
FixedInvestigated and resolved in an available EMC
software release or patch. To determine where the fix was
made, check the Fixed In Version field.
Host OS Host operating system where the issue was found.
Host Type Host type where the issue was found.
Working with Search From the list of issues that appear in the Issue Tracker Search Results,
Results you can view Issue Tracker Details for each issue. To view details of
a particular issue:
Click the Issue Number or right-click the Issue Number and
select Open. The Issue Tracker Details screen opens to display the
details for that issue, (Figure 4 on page 25).

Figure 4 Issue Tracker Details Window
The Issue Information on the top part of the Issue Tracker Details
window lists data from the Issue Tracker Results with additional
information appearing in the Environmental Information. Table 2
describes these fields.
Table 2 Environment Information Fields of Issue Tracker Details Window
Field Name Description
Product Feature Product feature categories that vary for individual EMC
products.
Symptom Detail of the symptom of the product issue.
Fix Summary Work around if available for Open issues or a summary of

what was fixed to resolve the product issue.
Found In Version Version in which the issue was found.
Fixed In Version Version which includes a fix for the issue.

If the issue is not fixed, the field appears blank.

Table 2 Environment Information Fields of Issue Tracker Details Window
Field Name Description
Knowledgebase ID EMC Knowledgebase ID for the EMC Knowledge Base

article.
Host OS Host operating system where the issue was found.
Host Type Host type where the issue was found.
Additional Feature Additional information for issues within a product feature

set. For example, Symmetrix has a Product Family called
SRDF. The additional feature type, or subcategory, is
GigE.
Fix Number The number of a patch or fix released by EMC for

individual EMC products.
Impact Statement A description of how the problem could affect a systems

environment.
Special Conditions A brief description of the unique scenarios that may need
to occur in order to reproduce the issue.
Additional Search Start a new search by selecting the Issue Tracker Search option in the
Options upper right corner of any Issue Tracker screen.
The Issue Tracker Search screen is divided into two areas:
Quick Search
Advanced Search
Quick Search Use the Quick Search option to quickly locate a particular issue:
1. Enter the Issue Number in the Quick Search field, and then click
Submit to display the Issue Tracker Search Results screen
(Figure 3 on page 23).
If you reported the issue to EMC Customer Support, use the case number.

Figure 5 Quick Search
If no issue exists for that Issue Number, the following message appears:
No issues were found that match your criteria.
Searching a Range of Use the Issue Tracker Search screen to limit the search results to only
Symmetrix DMX Issues include issues that match particular search criteria. Use any
combination of the following Advanced Search criteria, and then
click Submit:
Remember to select Symmetrix DMX from the Product drop-down menu

first, wait for the screen to refresh with Symmetrix DMX information, and
then begin using the Advanced search features.
Keyword(s)
To limit the search results to only include issues that have a
particular phrase or a particular word(s) associated with it (for
example: masking, or alerts), select the type of keyword search
criteria to use, and then type in the phrase or keyword(s).
The default is exact phrase, which does not initiate keyword

searching if the input field remains blank.
Keyword(s)All Words
To search for an issue that contains more than one desired
word in its title or description, use the all words selection
from the Keyword(s) drop down menu, then enter one word,
then a space, then the next word, and so on.
For example, to search for an issue that contains the words
Symmetrix and the word mapped, enter:
Symmetrix mapped

Product
To limit the search results to only include product-specific
issues, select that product name, Symmetrix DMX, from the
drop-down list.
Product Feature
To limit the search results to only include feature-specific
issues, select a feature from the drop-down list.
The default is any, which does not initiate feature-specific searching.
Status
To limit the search to only include issues that have a specific
status associated with them, select that status from the Status
drop-down list.
The default is any, which does not initiate status-specific searching.
Severity
To limit the search to only include issues that have a specific
severity level associated with them, select that level from the
Severity drop-down list.
The default is any, which does not initiate severity-specific searching.
Found In Version
To limit the search results to include only those issues that
were found in a particular software version, in the Found In
field, select the desired version number.
Fixed In Version
To limit the search results to include only those issues that
were fixed in a particular software version, select the desired
version number in the Fixed In field.

Technical Notes
Technical Notes
Hardware Related There are two new files included in this Enginuity package for the
Files Symmetrix DMX. The fibrecode files are new and include new
revision code Dx0D for the Seagate 73gb and 146gb drives.
fibrecode.zip
fibrecode.dat
Software Related There is a new version of Opimizer to support new drives.

Files Optimizer V5.5-561-1.0
Online General Rules

Non-Disruptive Before upgrading to the Enginuity 5671 family, the Symmetrix
Upgrades (NDU) DMX must already be running the latest version of Enginuity
5670.
Solutions Enabler 5.4 is not supported with 5671 Enginuity.
Solutions Enabler must be upgraded to version 5.5 or higher prior
to NDU.
To support more than 8000 devices, Solutions Enabler must be
upgraded to version 6.0 or higher prior to NDU.
The Symmetrix DMX must be running Tag Based Cache (TBC)
prior to upgrading the code.
All configuration files for 5671 Enginuity are subject to SymmWin
policing rules. The policing rules will validate:
Cache Requirements
Power requirements
Whether the Symmetrix DMX is TBC only
Configuration files must be saved and validated with the latest
version of 5670 SymmWin before upgrading. The 5670
configuration file should be clearly marked and stored in a secure
place. The configuration file must be saved and validated with
5671 SymmWin prior to attempting to perform the upgrade
procedure.
TimeFinder Restore transactions are not supported while the
NDU is in progress.

Technical Notes
All Symmetrix DMX 800 systems running 5671 Enginuity will

require a dedicated service processor. SymmWin Launcher is not
supported in 5671.
SRDF General Rules

NDU is to be performed on one Symmetrix at a time. Upgrading
all systems connected by SRDF at the same time is not supported.
The maximum recommended I/O per second is 1,000 per Disk
Adapter while performing NDU.
In SRDF environments, all systems connected to NDU candidates
must be at the minimum NDU-supported code level to ensure
that all patches are applied on the remote systems.
SRDF Journal 1 mode is not allowed during NDU. If J1 is active,
the procedure will abort and state that it is necessary to switch to
J0 mode for the duration of the procedure.
Certain SRDF link events (046D/047D) are expected during
NDU. EMC personnel should set filters on the system prior to
beginning the procedure.
Online code load is not recommended while running
DRDF/PPRC commands as the commands could time out.
In any SRDF environment where the remote Symmetrix is
running 5568 Enginuity code, the remote Symmetrix must
already be running the latest version of 5568 Enginuity code.
SRDF links from a Symmetrix DMX running 5671 Enginuity to a
Symmetrix DMX running 5669 Enginuity will not be supported.
Any systems linking a 5670 Symmetrix DMX to 5669 Symmetrix
DMX must upgrade the 5669 Symmetrix DMX prior to upgrading
either system to 5671 Enginuity code.
Symmetrix DMX running 5671 Enginuity linked to a Symmetrix
running 5x67 Enginuity will be limited to data migrations only.
NDU to 5671 Enginuity while remote systems are running 5x67
Enginuity is not supported.
NDU is not supported in 5670 to 5568 SRDF/GigE Domino
environments.
NDU on a Symmetrix DMX which is acting as an R2 SRDF/A
system is not possible while SRDF/A is active. The R2 link must
be disabled out of SRDF/A mode to proceed. This is due to a
change in the use of COVD devices.

Technical Notes
NDU is not allowed if only one SRDF link is supporting a

Domino SRDF group.
NDU not allowed if only one link is in an SRDF group. The link
will bounce impacting consistency.
Dynamic SRDF commands should not be issued while the online
upgrade is in progress.
The link recovery time in switched FC environments cannot be
accurately predicted because of factors outside of EMC's control,
including switch recovery time and the topology of the fabric.
There is a possibility that consistency groups, Domino groups or
SRDF/A may fail during NDU. Zoning the SRDF links separately
from all other links may mitigate this problem.
SRDF NDU - 5670 to 5671 with remote Symmetrix at 5568

Please see SRDF General Rules
5568.67.26 is required to be on the 5568 Symmetrix prior to
upgrading the Symmetrix DMX to 5671 Enginuity. 5568.67.26 is
required to establish SRDF linkage from the Symmetrix 5 to a
Symmetrix DMX for NDU to 5671 if the links are down.
NDU from Enginuity 5670 to Enginuity 5671 is not supported
when there are protected tracks for full device snap sessions.
Please see EMC KnowledgeBase ID emc81051.
SRDF NDU - 5670 to 5671 with ESCON Remote Adapters (campus)

SRDF NDU - 5670 to 5671 with ESCON Remote Adapters (FarPoint)

Some errors (xx23/xx24/D310/D510) may occur during NDU on
Farpoint SRDF links. These are known errors and are recoverable.

Documentation
SRDF NDU - 5670 to 5671 with Fibre Channel Remote Adapters

(pt-pt)
SRDF NDU- 5670 to 5671 with Fibre Channel Remote Adapters

(switched)
Information for EMC Personnel and Change Control (CCA)

Procedures
EMC personnel should refer to the Enginuity Reference Database
on the SSR website for any known issues.
EMC personnel should refer to the Global Services website for a
full description of the Configuration Review process (CSP2021).
All upgrades require a configuration review.
The original 5670 configuration file and the configuration file
saved with 5671, as well as the upgrade procedure must be
uploaded to CCA when the activity is submitted for review.
All CCA activities without the required documents or files will be
rejected.
All 5670 to 5671 upgrades will be reviewed by Engineering for the
first 30 days after release.
Any request to downgrade from 5671 Enginuity to 5670
Enginuity must be approved.
Documentation
Documentation
Updates
Permanent Member The Permanent Member Sparing feature described in Chapter 5 of the
Sparing Symmetrix DMX1000, DMX2000, and DMX3000 Product Guide, (P/N
300-000-661 Rev A06 ) and the DMX800 Product Guide,
(P/N 300-000-664 Rev A06) is not supported in this release of
Enginuity 5671.

Documentation
SRDF Interfamily The SRDF Product Guide, (P/N 300-001-165 Rev A03) incorrectly
Connectivity states that connections from Symmetrix systems running Enginuity
5670 to 5671 are not supported. SRDF connectivity from Enginuity
5670 to 5671 is supported. The correct table appears below.
.
Table 1-2 SRDF Interfamily Connectivity Support
Symmetrix
3x30/5x30 Symmetrix Symmetrix Symmetrix Symmetrix Symmetrix
Running 8000 Running 8000 Running DMX Running DMX Running DMX Running
Symmetrix Models 5267 5567 5568 5669 5670 5671
Symmetrix Yes Yes Yes No Yes a b Yes a b

3x30/5x30
Running 5267
Symmetrix 8000 Yes Yes Yes No Yes a b Yes

Running 5567
Symmetrix 8000 Yes Yes Yes Yes Yes Yes

Running 5568
Symmetrix DMX No No Yes Yes Yes No

Running 5669
Symmetrix DMX Yes a b Yes a b Yes Yes Yes c Yes

Running 5670
Symmetrix DMX Yes a b Yes a b Yes No Yes Yes d

Running 5671
a. Used for migration to higher levels of Enginuity code only.
b. Only ESCON and Fibre Channel connections (no FarPoint) are supported.
c. SRDF/A is only supported with Enginuity level 5670 and higher.
d. SRDF/Star Mainframe is only supported with Enginuity level 5671 and higher.
Documentation Refer to the Support section of the EMC Powerlink website at

Support http://powerlink.emc.com for the most recent general
availability (GA) documentation updates.
Comments Any suggestions will help us continue to improve the accuracy,

organization, and overall quality of the user publications. Please send
a message to mailto:techpub_comments@emc.com with
comments and requests for enhancements.

Software Media, Organization, and Files
Software Media, Organization, and Files

Enginuity software installation is coordinated through EMC Global
Services or through your local EMC office.
For information on related software environment and system
requirements, refer to the EMC Support Matrix on EMC Powerlink
website at: http://powerlink.emc.com.

Troubleshooting and Getting Help

Contact the Worldwide Customer Support Center at:
United States: (800) 782-4362 (SVC-4EMC)
Canada: (800) 543-4782 (543-4SVC)
International: (508) 497-7901
For release notes updates, support matrices and additional
information on the EMC products and services available to customers
and partners, refer to the Support section of EMC Powerlink website
at: http://powerlink.emc.com.

Copyright 2005 EMC Corporation. All rights reserved.

EMC 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. EMC CORPORATION
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 EMC software described in this publication requires an
applicable software license.
Trademark Information

Docu21183 Symmetrix DMX Model 800 1000 2000 3000 EMC Enginuity Release Notes

Hochgeladen von

Dokumentinformationen

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Docu21183 Symmetrix DMX Model 800 1000 2000 3000 EMC Enginuity Release Notes

Hochgeladen von

Copyright:

Verfügbare Formate

R E L E A S E N OT E S Symmetrix DMX Model

March 31, 2005

Revision History: The A02 revision update includes:

These release notes contain supplemental information about EMC

2 EMC Enginuity Release Level 5671.32.36 Release Notes

Naming Enginuity platform releases are denoted by a four-digit sequence. The

EMC Enginuity Release Level 5671.32.36 Release Notes 3

New Features and Changes

Problem Fix Changes to Symmetrix Enginuity made as a result of problem fixes

Additional Feature Secondary or additional Enginuity features affected by the change.

4 EMC Enginuity Release Level 5671.32.36 Release Notes

The primary Customer Engineer or Regional Technical Specialist

Symptom A brief description of the observable system behavior that is

Fix Summary A description of the fix that resolved the problem.

EMC Enginuity Release Level 5671.32.36 Release Notes 5

New Features This section identifies:

Issue Number 199920SYM

Fix Number 25927

Feature Type Base Functionality

Additional Feature Type None

EMC Knowledgebase ID None

Impact Level Medium

Symptom Add an enhancement to Enginuity 5671 to allow the system to

Host Type Any host type

Host OS Any operating system

Impact Statement Performance

6 EMC Enginuity Release Level 5671.32.36 Release Notes

Issue Number 199920SYM (continued)

Special Conditions None

Problem Summary Add an enhancement to Enginuity 5671 to allow the system to

Issue Number 12538460

Fix Number 26381

Feature Type Base Functionality

Additional Feature Type None

EMC Knowledgebase ID emc83494

Impact Level Medium

Symptom Add an enhancement so the director will reprogram the M5

Host Type Any host type

Host OS Any operating system

Impact Statement None

Special Conditions None

Issue Number 206722SYM

Fix Number 27085

Feature Type Base Functionality

Additional Feature Type None

EMC Enginuity Release Level 5671.32.36 Release Notes 7

Issue Number 206722SYM (continued)

EMC Knowledgebase ID None

Impact Level Medium

Symptom The customer may encounter errors during an IML.

Host Type Any host type

Host OS Any operating system

Impact Statement Potential Data Unavailability

Special Conditions None

Issue Number 207639SYM

Fix Number 27264

Feature Type Base Functionality

Additional Feature Type None

EMC Knowledgebase ID None

Impact Level Critical

Symptom Certain maintenance commands are returning a not done

Host Type Any host type

Host OS Any operating system

Impact Statement Maintenance Issue