docu42938_Symmetrix-DMX-3,-DMX-4-Enginuity-Release-Notes-5773.184.130.pdf

RELEASE NOTES

These release notes contain supplemental information about EMC® Enginuity release 5773.184.130. Topics include:

◆ Revision history ........................................................................................................ 2◆ Product description................................................................................................... 2◆ EMC Symmetrix Enginuity deployment strategy ......................................................... 2◆ New features............................................................................................................. 3◆ Changed features...................................................................................................... 3◆ Fixed problems ......................................................................................................... 3◆ Environment and system requirements ................................................................... 15◆ Known problems and limitations............................................................................. 16◆ Troubleshooting and getting help............................................................................ 21

Symmetrix® DMX-3™, DMX-4™

Enginuity™ Operating EnvironmentRelease Level 5773.184.130

Release NotesP/N 300-014-158 REV A02

September 5, 2012

Revision history

Revision historyThe following table presents the revision history of this document:

Product descriptionThis is a new release of Symmetrix® Enginuity operating environment supporting the Symmetrix DMX-3™, DMX-4™ emulation level 184 and Service Processor level 130. Details of the new features are provided in “New features” on page 3.

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 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 EMC’s 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 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.

EMC Symmetrix Enginuity deployment strategyThe modular design of Enginuity permits EMC to build upon previous serviceability and feature enhancements and allows the release of new and enhanced Enginuity revisions quickly and easily. This allows EMC to extend the functionality of Enginuity and improves its reliability with each platform release.

It is the policy of EMC 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

Revision Date Description

A01 August 28, 2012 First release of Enginuity™ version 5773.184.130.

A02 September 5, 2012 Removed fix 51076 as it was not included in the release of Enginuity.

2 Enginuity Release Level 5773.184.130 Release Notes

New features

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.

After the initial release of a major Enginuity version there are two types of minor version releases. They are a Service Release (SR) and a Maintenance Release (MR).

◆ A Service Release is scheduled at three-month intervals for each major Enginuity version per year; however, major legacy Enginuity versions may see longer intervals between Service Releases.

◆ A Maintenance Release is an unscheduled release and is specific to critical issues discovered post-Service Release.

Note: EMC also employs a Target Release recommendation. After a Service or Maintenance Release achieves the quality criteria (which includes runtime hours, limited Severity 1 issues, and successful completion of top customer activities), an Enginuity revision becomes a candidate for a Target Release. EMC recommends that customers should plan to make a change to an EMC Target Release recommendation twice per year.

New featuresThere are no new features added with this Enginuity release.

Changed featuresThere are no changed features since Enginuity release 5773.176.124.

Fixed problemsThis section highlights product issues that are fixed in this Enginuity release. Product issues are sorted alphabetically by product feature and by issue number within each product feature. Product issue details are available for each product issue:

◆ Issue Number: Unique 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 Number: Number of the patch or fix for the problem.

◆ Problem Summary: High-level summary of the problem being reported.

◆ Severity: Severity and potential impact of the issue.

◆ Primus Number (optional): Number of a relevant EMC Knowledgebase solution.

Note: The most up-to-date product issues for EMC Enginuity are detailed online in the EMC Issue Tracker, available on EMC Online Support at: http://support.EMC.com.

Enginuity Release Level 5773.184.130 Release Notes 3

http://support.emc.com

Fixed problems

Base Functionality

Issue Number(S): 48120750 Fix Number: 64013

Problem Summary: Starting from Enginuity level 5773.176.124, drive-related errors that invoked Global Sparing in previous versions should invoke a spare drive first, before drive swapping and rebuilding. In a few cases, however, a spare drive is not invoked at all.

Severity: 1 - Potential Data Unavailability

Issue Number(S): 46988970 Fix Number: 63517, 58858, 63494

Problem Summary: During the extent table recovery triggered by FICON link errors, inconsistencies between device records andI/O records flags may lead to extent errors and potential data unavailability/loss events.

Severity: 1 - Potential Data Loss/Unavailability


Problem Summary: After a Symmetrix DMX system is upgraded to Enginuity level 5773.167.115 and higher, potential performance issues may occur on metadevices.

Severity: 1 - Potential Performance Issue


Problem Summary: When the online loopback test fails with a timeout, it does not clean up the I/O exchanges. This may lead to an exception after the subsequent initialization process (IML).



Problem Summary: When the time of day (TOD) is updated close to 12 a.m. (midnight), the time kept by TOD may fall 24 hours behind. The following initialization process may update the control unit (CU) timer with an incorrect TOD, causing the directors to be 24 hours behind.

Severity: 2 - Potential Maintenance Issue


Problem Summary: In the process of a full initialization procedure (IML) of Enginuity after a disk director is replaced, another disk director may become unavailable.



Fixed problems

Issue Number(S): 45807664, 46379536, 45983286, 46435374

Fix Number: 64000

Problem Summary: If there are Memory Module failures on a memory board during the power-up of the Symmetrix system, the initialization procedure (IML) may fail. As a result, the system may not start.



Problem Summary: If the FEBE director on one power zone is replaced while the other power zone loses power, the Symmetrix system will be forced to vault. Enginuity should not allow the FEBE on one power zone B to be replaced if the other power zone is powered down.



Problem Summary: If timeouts occur during a remote Virtual Snap operation, the information on the target virtual device is not cleaned. As a result, the session state of the target virtual device becomes inconsistent, and customers cannot retry or terminate the Virtual Snap operation.

Severity: 1 - Potential Application Failure


Problem Summary: The Global Sparing feature should not allow a failed drive to be swapped with a drive that has smaller capacity. Otherwise, a dual-device failure may occur if another member of the RAID group also fails before a correct capacity drive is in place.



Problem Summary: If a dynamic spare drive is invoked when the SymmWin Global Sparing feature is already running against the same disk that caused the spare invocation, an incorrect device mirror state may occur.



Problem Summary: If the Environmental Control Module (XCM) loses Ethernet connectivity, the director cannot receive environmental updates from power subsystems. This may cause the Symmetrix system to vault.



Fixed problems

Issue Number(S): 381468SYM Fix Number: 58086

Problem Summary: A failed RS232 hub may cause the Symmetrix DMX-3 system to vault.



Problem Summary: Enginuity did not properly handle deferred SCSI check conditions with recovered sense keys. This may cause global memory errors, as well as RAID-related errors.

Severity: 1 - No Impact


Problem Summary: If the devices have invalid tracks on the SRDF mirror, and the SRDF mirror is in a not-ready state, then the TimeFinder/Clone session on the same devices may become very slow. As a result, customers may experience increased system write-pending levels.



Problem Summary: The director may become unavailable if too many print statements are logged in the EMC Service Processor or printed in the inline screen.



Problem Summary: This Federated Live Migration (FLM) enhancement adds support for Windows 2003 and 2008 clusters, and Linux Device Mapper (DM).



Problem Summary: In rare cases, the master director responsible for updating the system clock becomes not ready but it is still updating the system clock. This could lead to SRDF links timing out incorrectly because two directors are updating the system time.



Fixed problems

ESCON Channel


Problem Summary: Broadcasting a device scan to a not-ready director on a Symmetrix system may lead to a potential data-unavailability situation if the not-ready director accepts the device scan and begins running stale tasks left over from when it became unavailable.



Problem Summary: This enhancement minimizes the impact of streaming errors in the error collection buffer. With this enhancement, the error-analyzing tools can be used more effectively in the root-cause analysis and recovery process.


Issue Number(S): 39634230, 44890126 Fix Number: 57996

Problem Summary: When a connection with an external fabric switch fails, Enginuity retries multiple times to reestablish the connection. The first attempt to reconnect has the correct timeout value, however, the following attempts time out easily, preventing successful reconnection.

Severity: 2 - Potential Connectivity Issue


Problem Summary: The GigE connection between two Symmetrix systems running Enginuity 5773 and 5875 (and higher) failed to recover after continuous link issues.



Problem Summary: When mainframe mapping configuration changes are being made on ESCON directors with two ports assigned with two different splits, multiple ESCON directors may become unavailable.



Fixed problems

Fibre Channel

FICON Channel

Mainframe


Problem Summary: After a storage area network (SAN) event, such as a zoning change or a link issue, errors may be logged on the Fiber Channel director that is connected to the VPLEX system, and the VPLEX system may lose access to the LUNs.


Primus Number(S): emc284344


Problem Summary: The detected errors in the IOSO501 channel were logged on all hosts attached to the FICON adapter after a cyclic redundancy check (CRC) error occurred to only one of the paths, and the link was disconnected. With this fix, the hosts are able to recover from the disconnection.



Problem Summary: During a drive-rebuild procedure, the FICON director may become unavailable while referencing a RAID 10 stripe member.



Problem Summary: In extremely rare cases, FICON directors may become unavailable due to illegal access errors, which are caused by channel command words (CCW) for reset not being properly allocated.



Problem Summary: Coupling Facility Data Set volumes are forced offline due to the I/O timeouts that occur during the switch from Parallel Access Volume (PAV) mode to Hyper Parallel Access Volume (HPAV) mode.



Fixed problems

Online Configuration Change

Online Upgrade (NDU)

Open Replicator


Problem Summary: The online configuration change that adds or removes an R1 mirror to/from the R2 device may alter the SRDF flags of the SRDF devices, rendering them Write Disabled.



Problem Summary: Configuration changes cannot be made while the disk-scan script is in operation in either attended or unattended mode.




Problem Summary: The online drive-add procedure should fail if the physical capacity of the new drive is smaller than the capacity specified in the configuration file. Otherwise, a potential data-unavailability situation may occur.



Problem Summary: During an online drive upgrade procedure, if the added disk array enclosure (DAE) is empty, and its preset speed is different from the actual speed, the disk director may become unavailable, which could lead to data unavailability events.



Problem Summary: In rare cases, the state of an Open Replicator session may be misreported as invalid in Solutions Enabler.




Fixed problems

RAID 5

RAID 6


Problem Summary: The symrcopy recreate command with Open Replicator may time out and render the status of the target Open Replicator session as Recreated.

Severity: 2 - Potential Application Failure



Problem Summary: A drive power cycle can keep locking the tracks that are locked during a RAW Write operation if CA_REBUILD is set for the RAW write operation. As a result, timeout errors may occur upon any attempt to access the locked track.



Problem Summary: If a RAID 5 SRDF group experiences a dual failure, such as one drive has media errors, while another drive in the same group is being rebuilt, timeout errors may occur on the channel. This may lead to potential data-unavailability events.



Problem Summary: When a RAID 5 device has both data and parity track unavailable and there is a TimeFinder/Clone copy on that track, Enginuity consumes too many RAID cache slot, impacting RAID operations.



Problem Summary: Host timeouts could occur when a RAID 6 device has one member not ready and one member with media errors.




Fixed problems

SRDF Family


Problem Summary: On the thick SRDF R2 site that is connected with a thin SRDF R1 site with unallocated thin tracks, TimeFinder/Snap or TimeFinder/Clone operations may fail with errors.



Problem Summary: SRDF recognizes only GOOD and UNIT CHECK SCSI statuses coming back from R2 devices. An unexpected SCSI status spoofed by a network equipment is treated by R1 devices as a successful completion from R2 devices. This may lead to replication data loss events.



Problem Summary: During a power-on or a full-initialization procedure, SRDF directors may become unavailable. If this happens, the SRDF devices could be incorrectly left ready on the SRDF links, causing host timeouts.




Problem Summary: In rare cases, SRDF replication operations may become slow or even stop, and scrubber errors may be logged against the directors, indicating a number of tasks have expired.



Problem Summary: In a cascaded SRDF topology with unallocated thin tracks or never been written to by host (NWBH) tracks on an R21 device, a read request may be incorrectly serviced from the R21 to the R1 (instead of forcing a multi-hop read from the R2 to the R21 to the R1).

Severity: 1 - Potential Data Loss


Problem Summary: In a cascaded SRDF/Star topology, with the first leg of the devices in adaptive-copy mode and not ready on the SRDF links, the second leg may report inconsistency of SRDF/A groups.



Fixed problems

SRDF-Dynamic

SRDF-GigE

SRDF/A


Problem Summary: When a disk director becomes unavailable, Enginuity may incorrectly update the SRDF device flags, causing host timeouts.

Special Conditions: The problem occurs if the device-level dynamic SRDF setting was disabled.



Problem Summary: In a unique SRDF configuration over GigE, where DMX systems on the R1 side are directly connected to an extender, the longer-than-expected network latency may cause auto-negotiation failures, in which case manual intervention is needed to recover the link.



Problem Summary: If the remote Symmetrix system is running Enginuity 5876, write-pending and cache errors may occur in the SRDF spillover devices in the Symmetrix system running Enginuity 5773.

Severity: 1 - Potential Application Delay


Problem Summary: Count-key-data (CKD) format host writes may cause SRDF/A sessions to become unavailable.



Problem Summary: A sanity-check mechanism is added to SRDF/A to ensure that SRDF/A sessions can drop cleanly.



Fixed problems

SymmWin


Problem Summary: The performance may degrade on the R2 side of a SRDF/A group when perma-cache is used.



Problem Summary: During the rebuild of an R2 device that has Asynchronous Copy on First Write (ACOFW) enabled in an SRDF/A configuration, errors continued to log against the disk adapters, even though there were no problems with the read operations and the rebuild process.



Problem Summary: An internal SymmWin script (BBlocks) that is used for handling uncorrectable drive media errors could incorrectly work on not-ready spare drives, impacting the performance of the DMX system.



Problem Summary: Spinning down two members of a RAID 6 configuration will leave the devices in a degraded mode. Enginuity should display a warning message before users proceed to spin down two members of a RAID 6 configuration.



Problem Summary: This enhancement adds more properties extracted from the Symmetrix configuration file into the initial microcode program loading (IMPL) report to help with the installation or modification of Symmetrix systems.



Problem Summary: This enhancement collects the Scan Error Utility script to capture the errors identified during a disk scan and present them in the form of a table.



Fixed problems

TimeFinder/Clone


Problem Summary: This enhancement improves the thermal stability of the Standby Power Supply and updates two part numbers (PN 078-000-095 replaces PN 078-000-050, PN 078-000-096 replaces PN 078-000-054).



Problem Summary: A director replacement may impact the system performance.



Problem Summary: Enginuity 5773 may not always be able to read the statuses of all components. When it fails to read the status of a component which is in a busy state, it may misreport the component as offline and trigger an alert in Symmetrix Management Console.




Problem Summary: An internal SymmWin script (BBlocks) that is used for handling unrecoverable disk media errors may occasionally fail to handle such errors.



Problem Summary: When a data integrity field (DIF) error occurs on the source device during a TimeFinder/Clone session, the error is copied from the source device to the target device, causing data corruption on the target track.



Problem Summary: If two TimeFinder/Clone sessions are on the same source device with one active and copied and the other inactive and in precopy-sync mode, copy rate may be affected on other devices that have higher copy priority (active session in copy-in-progress state).



Environment and system requirements

TimeFinder/Snap

Virtual Provisioning

Environment and system requirementsFor detailed information on environment and system requirements when Enginuity is released for general availability (GA), consult the EMC Support Matrix (ESM), available through E-Lab™ Interoperability Navigator (ELN) at: http://elabnavigator.EMC.com, under the PDFs and Guides tab.


Problem Summary: If two TimeFinder/Clone sessions are on the same device with one session being active and the other being newly created and inactive, Asynchronous Copy on First Write (ACOFW) may not be used for writes. Otherwise, performance issues may occur.




Problem Summary: Performance issues may occur when a host tries to access a device that used to be a TimeFinder/Clone target because the Non-Exc Access (NXA) flag is not re-enabled when the source/target relationship is removed.



Problem Summary: During TimeFinder/Snap sessions, SAVE device pointer errors may cause the disk directors to get in an extended loop and eventually become unavailable.



Problem Summary: The recovery from uncorrectable media errors on SRDF thin devices could cause an incorrect handling of the write-pending indication on the SRDF mirror.



http://elabnavigator.emc.com




Known problems and limitations

Known problems and limitationsThis section identifies:

◆ Limitations to the functionality of this release.

◆ Other issues, such as known performance limits under certain conditions.

Table 1 Known problems and limitations (page 1 of 6)

Product Updated Number Limitation

BS2000 N 1200.01 Minimum version V6.1A02 of the FSC software SHC-OSD is required to manage Enginuity 5773-related features from a BS2000 host.

N 1200.02 BS2000/OSD only supports up to seven aliases per device, but tolerates 15.

N 1200.03 Cascaded SRDF is not currently supported for BS2000 hosts.

N 1200.04 Virtual ProvisioningTM is not supported for BS2000 hosts.

Compatible Native Flash

N 6750.00 Compatible Native Flash is not currently supported with Cascaded SRDF or SRDF/Star.

Enterprise Flash Drives

N 6700.01 Enterprise Flash Drives are allowed with DMX-4 systems only. They cannot be configured in DMX-3 systems.

N 6700.05 A maximum of eight Flash drives per slice are allowed. More Flash drives per slice require RPQ.

N 6700.06 At least one spare Flash drive is required.

N 6700.08 Flash drives cannot be placed in powervault locations (first 4 slots in each direct-connected DAE).

N 6700.09 SFS volumes are not allowed on Flash drives.

N 6700.13 Striped volumes (metavolumes and CKD RAID 10) cannot go across Flash drives and HDDs. (This is automatically blocked, as Flash drives are in their own disk group, and striping is not allowed across disk groups.)

N 6700.16 SecureErase is not supported with Flash drives.

N 6700.19 Symmetrix Optimizer does not swap volumes within a Flash drive in a disk group.

N 6700.20 Dynamic sparing between unlike media types (such as Flash drive and HDD) is not allowed.

4 Gb Fibre Channel N 2200.01 The minimum required versions of driver and HBA firmware for support of direct FC-AL topology attachment of the HP-UX are: For the driver, 4 GB AB378A and AB379A HBA model with HP-UX 11.23, and for the firmware, FibrChanl-01.B.11.23.08 revision ISP Code Version 4.0.90.

InfoMover (IFS) N 2085.00 Enginuity 5773 requires IFS 2.8 and Solutions Enabler 6.5 and higher.

Instant VTOC N 8100.01 iVTOC is supported on RAID 1 and RAID 6 FBA devices only.

ISCSI Channel N 3300.02 With HP hosts, there is a limitation of no more than 255 LUNs per iSCSI port.



iSeries (AS/400) N 100.06 Enginuity 5773 supports the IBM Power 6 hardware for Series I, the new 4-Gbit Smart IOAs dual-port Fibre Channel cards (IBM FC 5749/CCIN 576B, and IBM FC 5774/CCIN 5774), and the V6R1 operating system. Note that IBM no longer supports 2105 emulations with these new fibre cards.

iSeries (AS/400) Software

N 110.01 CopyPoint is not supported beyond SRDF/TimeFinder Manager 5.4.0.

N 110.02 SRDF/TimeFinder Manager 6.0 is the minimum version supported with Enginuity 5773.

N 110.03 iASP and Cascaded SRDF support are included in SRDF/TimeFinder Manager 6.0.1 patch release, which went GA on 6/19/08. Minimum Enginuity version is 5773.123.83.

Mainframe N 600.01 If a split configuration is used in MF FlashCopy, IBM APAR OA10765 is required to prevent data overlay/corruption.

N 600.02 If using FDR version prior to v5.4/56, then 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.

N 600.03 An Amdahl Host cannot run SyncSort on a Symmetrix DMX array over FICON channels unless the Amdahl CPU IU pacing fix is included in channel code FNM, level L41387.

N 600.06 Virtual Provisioning is not supported on CKD devices.

N 600.07 Cascaded SRDF/Star requires Level Set maintenance package EMC0801 and higher.

Mainframe PAV N 660.01 Supports up to 127 aliases to a base device.

Mainframe PPRC N 670.01 Online Enginuity upgrades are not recommended while running PPRC commands, as the commands may time out.

N 670.02 Concurrent SRDF and SRDF mirroring from R1 to larger R2 device are not supported with PPRC operations.

Mainframe TPF N 7700.01 RAID 5 and/or RAID 6 devices are only to be used in TPF for test environments. They are not qualified for production.

N 7700.02 Maximum allocated locks is restricted to 0X1000 locks, per SSID.

Mainframe: XRC N 680.01 When XRC devices enter and exit long busy state, the host may attempt to write past the end of the track upon the retry of the write command. The track then has bad data.

N 680.02 EMC applications such as EMC Mainframe SNAP, TimeFinder/Mirror, or TimeFinder/Snap, cannot be used against XRC primary devices.

Online Maintenance Procedure

N 810.03 A selective VTOC should not be used on Virtual Provisioning DATA devices if they are bound to thin devices.

Online Non-Disruptive Upgrades (NDU)

N 470.01 See the EMC Support Matrix for full support and software limitations.





Online Non-Disruptive Upgrades (NDU)

N 470.02 An NDU process requires a re-image of the Service Processor (SP). While the re-image is in progress, the SP is disabled, including any call-home capabilities.

N 470.03 Non-Hans directors are not supported.

N 470.04 NDU is not allowed if the Dynamic spare is invoked.

N 470.05 NDU is not allowed if the active TimeFinder/Clone sessions are not target protected or are not copied and active. (see Primus solution - EMC182592.)

N 470.06 System criteria for NDU for SRDF over Fibre Channel: Use 4Gb/s link speeds auto negotiate must be set. The remote Symmetrix system must be Symmetrix DMX 3 and DMX 4. On the remote DMX 3 system, Enginuity level must be 5671-target level. On the remote DMX 4 system, Enginuity level must be 5772-target level.

N 470.07 SRDF/A over GigE may have to be deactivated due to 128 second limbo (depends on cache configuration).

N 470.08 NDU with direct connect is supported for HP-UX 11.31 only with the new driver FibrChanl-01.B.11.23.08, which also contains an HBA firmware update ISP Code Version 4.0.90.

N 470.09 NDU is not supported on Windows iSCSI hosts, unless all I/O is halted.

N 470.10 NDU is not supported for TPF environment.

N 470.11 When downgrading from 5773 to 5772, original 5772 configuration file must be used. The downgrade must be performed offline, and all changes made on the 5773 operating environment will be lost, including dynamic SRDF and TimeFinder/Snap changes.

Online Upgrade: Add DAs/DAEs

N 960.01 A maximum of two drives can be added in one configuration change procedure.

Open Replicator N 400.02 No more than 1024 active Open Replicator sessions are supported at any one time.

N 400.03 During an Open Replicator Hot 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.

N 400.04 Online configuration changes to Open Replicator devices are restricted.

N 400.05 Open Replicator sessions should not be defined, suspended, or re-created when the write-pending count is over 50%.

N 400.06 It is not recommended to run a Clariion's array LUN-based Trespass mode while connected to a Symmetrix system performing Open Replicator operations.

Open Systems HP N 590.01 HP-UX 11.23 does not support the OS2007 flag.HP-UX 11.31 supports the OS2007 flag.

Oracle Checksum & Generic Safe Write

N 690.01 Oracle Checksum and Generic SafeWrite are not supported with Concurrent SRDF.





Oracle Checksum & Generic SafeWrite

N 690.02 Oracle Checksum and Generic SafeWrite are not supported with Cascaded RDF devices, ESCON RA RDF Link, and SRDF/A Multi-hop.

N 690.03 Checksum does not support RAID 6 and thin devices and R2 devices of SRDF/S.

RAID 5 N 660.01 In SRDF/A Delta Set Extension (DSE) pools, RAID 5 devices are not qualified as Delta Set SAVE devices.

RAID 6 N 640.04 Oracle Double Checksum and Generic SafeWrite are not supported on RAID 6 devices.

N 640.06 RAID 6 CKD 3380 devices are not supported.

Symmetrix Service Credential, Secured by RSA

N 3100.00 Symmetrix DMX systems connected to EMC by way of the Secure Remote Support Gateway cannot use connected token provisioning. Use the disconnected method to provision tokens for these systems.

N 3100.01 The Software Authenticator Solution is a “break-the-glass” method that allows the customer and EMC together to enable access to the Symmetrix DMX array in case of emergency. Not implementing this solution at a site could limit support access, which may impact Service Level Agreements in responding to a service event.

N 3100.02 EMC Service Enabled Partners cannot access the EMC Central Manager at this time and must use their organization’s Partner Representative to provision tokens until Central Manager is available.

N 3100.04 Service Enabled Partners must use Software Authenticators or Partner Default tokens on Symmetrix DMX array until they get direct access to the EMC Central Manager.

N 3100.06 EMC Direct cannot use Software Authentication on DMX, except for Emergency solution.

N 3100.07 Symmetrix DMX systems not installed in EMC’s install base (CSI) database, with proper remote support connection choices, cannot enable SSC.

N 3100.08 Software Authentication options (Emergency Solution and SE Partner Implementation) do not include a unique user identifier in the audit log. It is assumed that the service partner organization will build their own internal procedures to verify that service access is properly administered.

SRDF Family (SRDF/S)

N 300.00 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.06 If concurrent write is enabled in synchronous mode write-pending issues may occur on a link bounce.

N 300.07 If, with concurrent SRDF, an operation is performed on either link that temporarily or permanently write disables the R1 device, the state of the other link will be affected. This could cause problems for an application writing to the R1 device.

SRDF/A N 360.01 At distances greater than 100 miles, timeouts may occur if you transition to a synchronous mode of operation with ESCON FarPoint.

N 360.02 The Open Systems and mainframe software are not qualified to work together to control the same sessions.





SRDF/A N 360.04 Only one concurrent SRDF mirror can be in SRDF/A mode.

N 360.06 The maximum number of sessions is 128 sessions per Symmetrix DMX array and 32 sessions per Remote Adapter.

N 360.07 TimeFinder/Snap from an SRDF/A R2 device is not supported.

SRDF: Cascaded N 6100.01 The multi-job feature must be turned off on the primary site in Cascaded MSC environments that use CKD devices.

SRDF: Fibre Channel

N 3500.01 In Fibre Channel SRDF environment, the auto-negotiate option must be set to use 4Gb link speeds.

SRDF Inter Family: 5773 - 5267

N 3600.01 5773 to 5267 is not supported.


N 3600.02 5773 to 5568 is supported for SRDF migration only.


N 3600.03 5773 to 5671 supports full SRDF functionality of the Enginuity 5671.


N 3600.04 5773 to 5771 is not supported.

SRDF: PPRC N 310.01 Online Enginuity upgrades are not recommended while running PPRC commands, as the commands may time out.

N 310.02 PPRC is limited to utilizing only the first 64 RA groups.

N 310.03 Concurrent SRDF and SRDF mirroring from R1 to larger R2 device are not supported with PPRC operations.

N 310.04 EMC applications, such as EMC Mainframe SNAP, TimeFinder/Mirror, or TimeFinder/Snap, cannot be used against XRC primary devices.

SRDF/ Star N 6500.01 Any three-site SRDF/Star configuration that links more than five Symmetrix systems per site requires an RPQ.

N 6500.02 SRDF over ESCON is not supported with SRDF/Star.

Symmetrix Data Mobility Manager (SDMM)

N 340.01 Symmetrix Data Mobility Manager (SDMM) is not supported.

TimeFinder/Snap N 430.01 Solutions Enabler does not allow the use of RAID 10 devices as a VDEV in TimeFinder/Snap.

N 430.02 No TimeFinder/Snaps are allowed on RAID 5 thin devices.

N 430.03 TimeFinder/Snap from an SRDF/A R2 device is not supported.

Virtual Provisioning N 6800.02 Virtual Provisioning is not supported on CKD devices.

N 6800.03 Time/Finder Mirror is not supported.

N 6800.04 R1 to larger R2 with Virtual Provisioning is not supported.

N 6800.05 Virtual Provisioning is not supported with ESCON SRDF.

N 6800.06 SRDF is not allowed on RAID-5 thin devices.

N 6800.08 Delta Set Extension is not allowed on thin-provisioned SRDF/A sessions.




Troubleshooting and getting help

Troubleshooting and getting helpEMC support, product, and licensing information can be obtained as follows:

Product information — For documentation, release notes, software updates, or information about EMC products, licensing, and service, go to EMC Online Support (registration required) at:

http://support.EMC.com

Technical support — For technical support, go to EMC Online Support, and click the icons and links in the Service Center section to create a service request, or contact Customer Service. Note that to open a service request, you must have a valid support agreement. Contact your EMC sales representative for details about obtaining a valid support agreement or with questions about your account.

Fully Automated Storage Tiering for Symmetrix DMX Series (FAST)

N 6200.00 When a meta head is added to the device list that is already associated with a device rule, a warning message is displayed that the device is in more than one device list.

N 6200.01 FAST on DMX cannot move logical devices between different RAID groups.

N 6200.02 In order for meta devices to be moved in and out of the Enterprise Flash Drive storage tires, the meta devices must be identical in size and number of members.

N 6200.03 The number of meta members supported by FAST depends on the RAID type (note that the number of meta members includes the meta head): RAID 6 14+2 - 11 membersRAID 6 7+1 or RAID 5 7+1- 23 membersRAID 5 3+1- 46 membersRAID 1- 93 members




http://support.emc.com

Troubleshooting and getting help

Copyright © 2012 EMC Corporation. All rights reserved. Published in the USA.

Published September, 2012

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.

EMC2, EMC, and the EMC logo are registered trademarks or trademarks of EMC Corporation in the United States and other countries. All other trademarks used herein are the property of their respective owners.

For the most up-to-date regulatory document for your product line, go to the technical documentation and advisories section on EMC Online Support.


Documents

docu42938_Symmetrix-DMX-3,-DMX-4-Enginuity-Release-Notes-5773.184.130.pdf