RELEASE NOTES

EMC Symmetrix VMAX 40K, VMAX 20K/VMAX Series EnginuityOperating Environment

Release Level 5876.159.102

Release Notes
P/N 300-014-192 REV 01 Oct 17, 2012

These release notes contain supplemental information about EMC Enginuity release 5876.159.102 for Symmetrix VMAX 40K, VMAX 20K/VMAX Series. Topics include:

Revision history ........................................................................................................ 2 Product description................................................................................................... 2 New features............................................................................................................. 3 Changed features...................................................................................................... 6 Known problems and limitations............................................................................. 17 Troubleshooting and getting help............................................................................ 22

Revision history

Revision history
Table 1, Revision History, presents the revision history of this document.
Table 1 Revision History Revision A01 Date Oct 17, 2012 Description First release of Enginuity release 5876.159.102 for Symmetrix VMAX 40K, VMAX 20K/VMAX Series

Product description
This is a new release of the Enginuity operating environment supporting Symmetrix VMAX 40K, VMAX 20K/VMAX emulation level 159 and Service Processor level 102. Details of the new features are provided in New features on page 3. Enginuity is the operating environment for the Symmetrix VMAX 40K, VMAX 20K/VMAX Series. Enginuity manages and ensures the optimal flow and integrity of information through the different hardware components of the Symmetrix system. Note: Enginuity operating environment installation is coordinated through EMC Global Services or through your local EMC office. Enginuity provides the following services for Symmetrix VMAX 40K, VMAX 20K/VMAX systems:

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. For example, Enginuity 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, and ProSphere Symmetrix Package Enhanced, 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.

Enginuity Release Level 5876.159.102 Release Notes

New features

New features
The 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. EMC thereby extends the functionality of Enginuity and improves its reliability with each release. EMCs policy is to provide 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.

Features and enhancements

This section identifies features and enhancements to existing functionality.
Product type Base hardware Feature Mixed DAE configurations Description Symmetrix VMAX 40K systems support standard 15-drive DAEs that contain 3.5 or 2.5 drives and 25-drive high density DAEs that contain 2.5 drives. Only one type of DAE could be used in Enginuity 5876.82.57. Now in Enginuity 5876.159.102, Symmetrix VMAX 40K systems allow you to mix standard and high density storage bays in the array. The new Li-Ion SPS battery pack is supported. Compared with lead-acid SPS, it has less weight, longer life, and it is modular and easily replaceable. The new Li-Ion SPS is fully backward compatible with lead-acid SPS and supports all existing SPS commands and queries. You can mix Li-Ion and lead-acid SPS within a system. All VMAX family platforms with Enginuity 5876 provide an increased level of awareness and interoperability with EMC VFCache Flash-caching solutions. EMC VFCache is a server Flash-caching solution that reduces latency and accelerates throughput to improve application performance. The combination of VMAX with Enginuity 5876 and VFCache provides the following support: VMAX awareness of VFCache VMAX reporting of VFCache performance statistics VMAX reporting of VFCache errors VFCache documentation is available at EMC Online Support: http://support.EMC.com.

Li-Ion SPS support

VFCache

Base software

Support for Thin Provisioning in Microsoft Window Server 2012 is supported. Four new SCSI Microsoft Windows commands are supported: UNMAP, Get LBA Status, Log Sense with Logical Block Server 2012 (Win8) Provisioning log page, and inquiry page B2. Host I/O Limits Enginuity 5876.159.102 introduces front end performance limits (quotas) to be defined by the user and associated with storage groups. The quota definitions contain the operating parameters of the I/Os per second and/or bandwidth limitations. A defined quota is equally divided amongst the total number of directors included in the masking view associated with the storage group for which the quota is defined. All devices in that storage group share that quota.

Enginuity Release Level 5876.159.102 Release Notes

New features

Product type Base software

Feature VP Compression

Description Enginuity version 5876.159.102 introduces compression capabilities for Virtually Provisioned environments (VP compression) that provide customers with 2:1 or greater data compression for very infrequently accessed data. EMC defines infrequently accessed data as that which is not accessed within month-end, quarter-end, or year-end activities, nor accessed as part of full backup processing. Data within a thin pool may be compressed manually for an individual device or group of devices, via Solutions Enabler, Mainframe Enabler, or Unisphere for VMAX. Alternatively, inactive data may be compressed automatically for thin devices that are managed by FAST VP (see FAST support for VP Compression (FAST VP Compression) on page 4). In order for data to be compressed, the thin pool containing the data must be enabled for compression. Only allocated extents are compressed. Full spare coverage is initiated on initial configurations for Symmetrix VMAX systems. Direct sparing does not permanently relocate a drive to a suboptimal location in the array, for example, another disk director slice or loop. 5876.159.102 supports up to four tiers per FAST VP policy when used with FTS. FTS is the tier that includes externally provisioned storage provided by the Federated Tiered Storage (FTS) feature. FAST VP Compression uses the VP Compression mechanism to automatically compress inactive data for devices associated with a FAST VP policy. FAST VP is enabled at the system level by setting the FAST VP Time to Compress control parameter. The time to compress may be set between 40 and 400 days, or never never means FAST VP will not compress data. Data that is seen to be inactive for a period of time longer than the time to compress will be considered eligible for automatic compression. FAST VP Compression performs compression at the sub LUN level. It requires that the FAST VP policy contain a pool that has been enabled for compression. The Virtual Provisioning UNMAP T10 SCSI Block command for open systems hosts is supported. This command allows hosts to reclaim reserved but unused disk space. Federated Live Migration (FLM) supports clustered host configurations. Refer to EMC Simple Support Matrix EMC Federated Live Migration for details on supported source arrays and host operating systems. Federated Tiered Storage (FTS) gives you the ability to attach external storage to Symmetrix arrays by using either SAN or direct-attach topology. Fibre Channel arbitrated loops are required in direct-attached solutions between external and target Symmetrix port. FTS interoperability matrix at https://elabnavigator.emc.com/jsp/legacy_support.jsp provides greater detail on FTS support of external arrays. Introduced in 5876.159.102, customers can decide if the FTS tier (the tier that includes externally provisioned storage) can be treated as the lowest performing tier, or a higher tier based on the performance characteristics of the attached third party array. Enginuity 5876.159.102 supports FTS tiers to be associated with a technology type. The technology associated with the FTS tier indicates to the FAST VP controller the expected performance from the tier. This feature enables you to place the FTS tier at the right location for the expected performance of the external tier. SRDF supports data replication between thick and thin FBA devices with full functionality in cascaded SRDF and SRDF/Star topologies.

Full spare coverage

FAST VP

FAST VP support for 4 tiers FAST support for VP Compression (FAST VP Compression)

Virtual Provisioning Federated Live Migration (FLM) Federated Tiered Storage (FTS)

Support for Thin Provisioning UNMAP Enhancements for FLM Additional 3rd party array support

FAST VP support for FTS tier

SRDF family

Thick-to-thin support in cascaded SRDF and SRDF/Star topologies for FBA devices SRDF/A write pacing enhancements

TimeFinder sessions off SRDF/A R2 devices in cascaded SRDF topologies are supported. This feature requires that the SRDF/A device pacing be active on the R21 devices and that the first cascaded leg operate in synchronous mode.

Enginuity Release Level 5876.159.102 Release Notes

New features

Product type SRDF family

Feature Thick-to-thin Support for CKD devices Zero space reclamation Thick-to-thin support for CKD devices in all SRDF topologies except SRDF/EDP SRDF interfamily connectivity

Description SRDF supports thick-to-thin CKD device pairs. 5876.159.102 is required on arrays configured with thin CKD SRDF devices. Thick-to-thin device pairs are supported in two-site and three-site concurrent and cascaded topologies, including SRDF/Star. Zero space reclamation across SRDF links including thick-thin SRDF device pairs is supported. Both FBA and CKD device pairs are supported. SRDF supports data replication between device pairs that use mixed thick and thin CKD devices with full functionality in two-site, concurrent SRDF, cascaded SRDF, and SRDF/Star topologies.

SRDF supports the following interfamily connectivity: 5876.159.102 5876.159.102: Full SRDF support including thick-thin connectivity for FBA and CKD device pairs. 5876 5875.231.172/5875.198.148 (FBA devices only): Full SRDF support including thick-thin connectivity for FBA device pairs. 5876.159.102 5773 (FBA and CKD devices): Full SRDF support including thick (5773)-thin(5876.159.102) connectivity for FBA and CKD device pairs. 5876.159.102 5671 (FBA and CKD devices): Migration only functionality for FBA and CKD devices including thick (5671)-thin(5876) device pairs. For more details, refer to EMC Online Support at http://support.EMC.com and search for SRDF Two-site Interfamily Connectivity. This feature allows you to perform a VP Snap restore to a TimeFinder/Clone target. For example, in an A > B > C cascaded configuration (where A > B is TimeFinder/Clone and B > C is VP Snap), you can copy data from device C to device B, and then you can incrementally restore to A (via device B). You can complete this operation without terminating the TimeFinder/Clone session or any existing VP Snap sessions off of the TimeFinder/Clone source device or target device. This feature allows you to recreate a TimeFinder/Clone copy without terminating VP Snap sessions that are cascading off of the TimeFinder/Clone target.

TimeFinder family

Support restore from a TimeFinder cascaded VP Snap to a fully copied clone Support incremental refresh of clone while persisting TimeFinder cascaded VP Snap sessions TimeFinder Clone incremental restore to a source that has active TimeFinder/Snap or TimeFinder VP Snap sessions TimeFinder Refresh Clone with cascaded Snap persistence TimeFinder Cascaded Snap restore to fully copied clone without terminating clone sessions

This feature allows you to perform an incremental restore to a TimeFinder/Clone source device that has active TimeFinder/Snap or VP Snap sessions off of it (without terminating the TimeFinder/Snap or VP Snap sessions). This feature only supports an incremental restore to the original source device.

This feature allows you to recreate a TimeFinder/Clone copy without terminating TimeFinder/Snap sessions that are cascading off of the TimeFinder/Clone target.

This feature allows you to perform a TimeFinder/Snap restore to a TimeFinder/Clone target. For example, in an A > B > C cascaded configuration (where A > B is TimeFinder/Clone and B > C is TimeFinder/Snap), you can copy data from device C to device B, and then you can incrementally restore to A (via device B). You can complete this operation without terminating the TimeFinder/Clone session or any existing TimeFinder/Snap sessions off of the TimeFinder/Clone source device or target device.

Enginuity Release Level 5876.159.102 Release Notes

Changed features

Changed features
The following limitations have been removed in Enginuity 5876.159.102:

Product Support for thin CKD 3390 SRDF devices Federated Live Migration (FLM) Online maintenance procedures TimeFinder VP Snap Mainframe

Updated Number Y

Limitation

9300.00 If thin CKD devices are used with SRDF/Star, Concurrent SRDF, Cascaded SRDF solutions, only VMAX 40K or VMAX 20K/VMAX Series arrays running Enginuity 5876 can be used. 2100.11 FLM does not support online configuration changes on front-end ports during an active FLM session. 810.01 Do not change the types of more than 50 percent of the directors in a single configuration change operation.

Y Y Y

8000.00 An SRDF Establish operation may fail if the target R2 device had been the source of TimeFinder VP Snap session, and if the device has unallocated tracks prior to the SRDF establish operation. 9900.00 Thin mainframe FBA devices cannot be mapped to FICON directors.

Enginuity Release Level 5876.159.102 Release Notes

Fixed problems

Fixed problems
This section highlights products issues that are fixed in this Enginuity release. Product issues are listed alphabetically by product feature and by issue number within each product feature. The following details are available for each product issue:

Issue 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. SeveritySeverity 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.

Base Functionality

Issue Number(S): 48035816, 48654268

Fix Number: 65161

Problem Summary: During a RAID rebuild operation, cache errors may occur due to a race condition with device locks. Severity: 1 - Potential Data Unavailability

Issue Number(S): 49499728

Fix Number: 64951

Problem Summary: When customers replace or remove initiators using symaccess replace or symaccess remove on the Symmetrix system, the front-end directors may become unavailable when there are large number of initiator groups on the Symmetrix system. Severity: 1 - Potential Data Unavailability

Issue Number(S): 49388402, 49423944

Fix Number: 64864

Problem Summary: The CPU utilization of a disk director is high even though there are only a few I/Os running in the Symmetrix system. This could happen if many devices are in precopy synchronization mode and the disk-director CPU is busy scanning data to be copied. Severity: 1 - Potential Performance Issue

Enginuity Release Level 5876.159.102 Release Notes

Fixed problems

Issue Number(S): 49219826

Fix Number: 64785

Problem Summary: Temporary power loss could cause the Symmetrix VMAX systems to come online without a proper Vault Restore causing data loss. Severity: 1 - Potential Data Unavailability

Issue Number(S): 402611SYM

Fix Number: 64504

Problem Summary: This is an enhancement to remove the check for engine power supply to prevent false alarms and unnecessary dial home events. This applies to Symmetrix VMAX 40K systems only. Severity: 1 - Potential Maintenance Issue

Issue Number(S): 48802220

Fix Number: 64506

Problem Summary: If administrator configures LUN masking on VMware ESX to begin with LUN number 1, the ESX may not be able to connect to VMAX iSCSI port and LUN discovery may fail. With this fix, the issue is resolved. Severity: 1 - Potential Connectivity Issue Primus Number(S): emc298869

Issue Number(S): 48478338

Fix Number: 64554

Problem Summary: In the Symmetrix VMAX 40K, VMAX 20K/VMAX systems, the xx2F.xx error (Disk SCSI Sense error) may not be uniquely logged on different Logical Block Address, cylinder, head information, causing it difficult to determine what data might be effected. Severity: 2 - Potential Maintenance Issue

Issue Number(S): 401955SYM

Fix Number: 64703

Problem Summary: Enginuity disk scrubbing could incorrectly drop a disk write disabled or not ready. This may result in data unavailability/loss events. Severity: 2 - Potential Maintenance Issue

Issue Number(S): 48388886, 48541996, 48889076, 48671078

Fix Number: 64214

Problem Summary: A specific Host writes I/O profile (like 4 KBytes writes I/O) could increase I/O response time impacting performance. Severity: 1 - Potential Maintenance Issue

Enginuity Release Level 5876.159.102 Release Notes

Fixed problems

Issue Number(S): 47523544

Fix Number: 63868

Problem Summary: Timeout errors while attempting to lock a cache slot may cause the 282C error (CRC error). This fix adds more detail to the trace information when the XX12 error (cache error) occurs due to slot lock not being freed for 30 seconds. Severity: 4 - Potential Data Loss/Data Unavailability

Issue Number(S): 397606SYM

Fix Number: 64179

Problem Summary: FTS enhancement to automatically recover eDisks from a dual physical path failure after both physical paths are restored. Severity: 4 - Potential Data Loss/Data Unavailability

Issue Number(S): 46824102

Fix Number: 64409

Problem Summary: Errors occur after the fast initialization process if the SRDF static mirror configuration change is performed on a large number of devices. Severity: 1 - Potential Data Loss/Data Unavailability

Issue Number(S): 48825562, 49687200

Fix Number: 63894

Problem Summary: This enhancement recovers the metadata without running a drive replacement procedure when a device becomes not ready during a Vault Recovery procedure. Severity: 4 - Potential Maintenance Issue

Fibre Channel

Issue Number(S): 47422916

Fix Number: 63644

Problem Summary: A Fibre Channel director may become unavailable if it keeps receiving messages from the HBA of a host that is no longer logged in the Fibre Channel director. Severity: 1 - Potential Data Loss/Data Unavailability

Mainframe

Issue Number(S): 49096586

Fix Number: 65002

Problem Summary: Poor I/O response and high IOSQ time can be observed in certain configurations that run SRDF/A in Multi-Session Consistency (MSC) mode with Hyper Parallel Access Volumes (HyperPAV) on Symmetrix systems. Severity: 1 - Potential Performance Issue

Enginuity Release Level 5876.159.102 Release Notes

Fixed problems

Online Configuration Change

Issue Number(S): 49580868

Fix Number: 65031

Problem Summary: An FBA front-end director could become not operational during an online mapping configuration change. Severity: 1 - Potential Data Unavailability

Issue Number(S): 385720SYM

Fix Number: 61981

Problem Summary: Online configuration changes made during an FLM session may incorrectly cause FLM to auto failback. Severity: 2- Potential Maintenance Issue

Online Maintenance Procedure

Issue Number(S): 49169354

Fix Number: 65020

Problem Summary: FBA front-end director, after logging 90FF exception error, could constantly loop into initial microcode program load (IMPL) causing cache slot lock errors. Severity: 1 - Potential Data Loss/Data Unavailability

Open Replicator

Issue Number(S): 49717576

Fix Number: 65047

Problem Summary: During an Open Replicator migration session, Open Replicator incremental session flag is not set correctly to the local directors. As a result, Open Replicator pace may become very slow. Severity: 1 - Potential Performance Issue Primus Number(S): emc301630

SRDF Family

Issue Number(S): 46213220

Fix Number: 64305

Problem Summary: SRDF links could bounce performing online configuration changes on the SRDF R2 system and having SRDF configured as J0 mode and Single Round Trip (SiRT) enabled. Severity: 2 - Potential Data Unavailability

10

Enginuity Release Level 5876.159.102 Release Notes

Fixed problems

Issue Number(S): 45769774

Fix Number: 63815

Problem Summary: Running EMC Enginuity ECDD scan against CKD SRDF devices could cause SRDF/A to drop logging CACA.20 errors. Severity: 1 - Potential Data Unavailability Primus Number(S): emc294711

Issue Number(S): 397646SYM

Fix Number: 63756

Problem Summary: If an SRDF group contains many large devices, the SRDF directors on the R1 side become unavailable when the invalid tracks are copied from the secondary site and the track tables are merged. Severity: 1 - Potential Data Loss/Data Unavailability

SRDF-Dynamic

Issue Number(S): 48577580

Fix Number: 64521

Problem Summary: SRDF R1/R2 personality swap could fail if the SRDF links bounce during the operation. Severity: 1 - Potential Data Loss/Data Unavailability Primus Number(S): emc298497

SRDF/A

Issue Number(S): 49470900

Fix Number: 65134

Problem Summary: The Symmetrix VMAX system could reach system maximum write pending when SRDF/A group pacing is set to a non-zero value and the SRDF links drop offline. Severity: 1 - Potential Data Unavailability

Issue Number(S): 48207256

Fix Number: 64113

Problem Summary: During the SRDF/A restore cycle, if SRDF/A encounters a device-level write pending limit, it will skip this device and look for other devices that may need to be restored. This may take up a lot of time and lead to potential performance issues. Severity: 1 - Potential Data Loss/Data Unavailability Primus Number(S): emc296307

Enginuity Release Level 5876.159.102 Release Notes

11

Fixed problems

TimeFinder/Clone

Issue Number(S): 49408824

Fix Number: 64975

Problem Summary: If a TimeFinder/Clone or TimeFinder/Clone emulation source device is configured as RecoverPoint VMAX Splitter, the changes to the source device is not tracked for differential refresh of the target device. A subsequent refresh to target may result in corrupted backup. Severity: 1 - Potential Data Loss/Data Unavailability

TimeFinder/Snap

Issue Number(S): 48697166

Fix Number: 64417

Problem Summary: TimeFinder VP Snap sessions became inactive and logged errors on multiple disk directors due to a full data pool. Severity: 1 - Potential Data Unavailability

Virtual Provisioning

Issue Number(S): 48889808

Fix Number: 65155

Problem Summary: If during an online configuration change, a Thin Data device drops Not Ready, and the associated Thin device is SRDF protected, critical inconsistency errors may be logged against the disk director. This may lead to data loss/unavailability events. Severity: 1 - Potential Data Loss/Data Unavailability

Issue Number(S): 49036286

Fix Number: 64692

Problem Summary: The EMC commands used for displaying pool reserved capacity (PRC) values of a thin pool may return incorrect values. This is due to the pool-level PRC counters not being updated properly in the Global Memory. Severity: 2 - No Impact

Issue Number(S): 399069SYM

Fix Number: 64069

Problem Summary: This enhancement adds a new parameter to the command so the command will find physically inconsistent thin tracks and print the associated thin device and tracks. Severity: 4 - Potential Maintenance Issue

12

Enginuity Release Level 5876.159.102 Release Notes

Fixed problems

Serviceability fixes

Issue Number(S): 400217SYM

Fix Number: 20012641

Problem Summary: This enhancement runs the RMA script when a field replaceable unit (FRU) is added to the bad FRU tab in Symmwin. Severity: 4 - Potential Maintenance Issue

Issue Number(S): 47824692

Fix Number: 63879

Problem Summary: The Online configuration change initialization procedure (IML) could take a long time to complete impacting the host. The problem is triggered by the IML code spending too much time in checking Symmetrix Differential Data Facility (SDDF) sessions. Severity: 1 - Potential Data Unavailability

Issue Number(S): 396657SYM

Fix Number: 20012443

Problem Summary: This is an enhancement of the Online Engine upgrade script to detect bent pins in the engine midplane. Severity: 4 - Potential Maintenance Issue

Issue Number(S): 379233SYM

Fix Number: 20012255

Problem Summary: This fix enables Enginuity to upgrade EMULEX code in the FICON director without the need to take the directors or ports offline. Severity: 4 - Potential Maintenance Issue

Issue Number(S): 45404602

Fix Number: 62730

Problem Summary: This enhancement for the memory upgrade script in Symmetrix VMAX 40K and VMAX 20K/VMAX systems introduces a test to its director pair before placing the system in degraded mode. This ensures that no double memory failure occurs during the upgrade. Severity: 4 - Potential Data Unavailability

Enginuity Release Level 5876.159.102 Release Notes

13

Fixed problems

Optimizer

Issue Number(S): 402920SYM

Fix Number: 402920

Problem Summary: On large scale configurations where there are more than 500 storage groups, it may take a long time to read and process FAST parameters. This fix creates two mutex objects: one for reading configuration parameters; one for reading and processing FAST parameters. Severity: 1- Potential Connectivity Issue

Issue Number(S): 403968SYM

Fix Number: 403968

Problem Summary: FAST DP may fail when reading parameters with empty tiers or policies. This causes FAST DP to lose connection to the server. Severity: 1- Potential Connectivity Issue

Issue Number(S): 405166SYM

Fix Number: 405166

Problem Summary: This fix improves the performance and scalability of FAST parameters. Severity: 1- Potential Connectivity Issue

Issue Number(S): 405489SYM

Fix Number: 405489

Problem Summary: The FAST VP engine may consume large amount of memory when there is a large number of storage groups (more than 1,000) under management. Severity: 1- Potential Performance Issue

Issue Number(S): 48668100

Fix Number: 405489

Problem Summary: FAST VP does not move data and the SPTM service crashes and does not start up due to issue with the install process. Severity: 1- Potential Application Failure

Issue Number(S): 406207SYM

Fix Number: 406207

Problem Summary: The logs for cftZoneRecord may be truncated because they are too long. This fix breaks the log into smaller pieces to avoid the logs being truncated. Severity: 2- No Impact

14

Enginuity Release Level 5876.159.102 Release Notes

Fixed problems

Issue Number(S): 406744SYM

Fix Number: 406744

Problem Summary: Upon shutdown of the FAST VP engine, the engine by mistake clears the FAST VP movement polices, which prevents the FAST VP movement. Severity: 2- Potential Application Failure

Enginuity Release Level 5876.159.102 Release Notes

15

Environment and system requirements

Environment and system requirements

Enginuity operating environment release level 5876.159.102 provides new features and enhancements to mainframe and Open Systems environments. For detailed information on environment and system requirements, consult the EMC Support Matrix (ESM), available through E-Lab Interoperability Navigator (ELN) at: http://elabnavigator.EMC.com, under the PDFs and Guides tab. Note: The most up-to-date product issues for EMC Enginuity are detailed online in the EMC Issue Tracker, available on the EMC Online Support at: http://support.EMC.com.

16

Enginuity Release Level 5876.159.102 Release Notes

Known problems and limitations

Known problems and limitations

This section identifies:

Limitations to the functionality of this release Other issues, such as known performance limits under certain conditions

Table 2 Known Problems and Limitations. Product Meta reconfiguration improvements Meta reconfiguration for thin striped metadevices Configuration and provisioning (concurrent scripts) Fully Automated Storage Tiering for Virtual Pools (FAST VP) Updated Number N Limitation

4040.00 On a heavily loaded array, the meta reconfiguration script may time out during the session-creation phase. 8300.00 The meta reconfiguration feature does not verify if a thin pool is large enough to handle the expanded meta size.

5000.00 The system limitation for concurrent upgrade procedures is five. Using SEs Configuration Manager, customers are able to run a maximum of four concurrent upgrade procedures. Using SymmWin, EMC Global Services (GS) are able to run five concurrent upgrade procedures. 3100.03 If a Thin Pool is under FAST VP control, it cannot be deleted.

N N N N Federated Live Migration (FLM) N N N N N

3100.04 Encapsulated external devices cannot be used with FAST VP. 3100.05 FAST (full volume movements) is not supported with FTS. Only FAST VP in virtually provisioned FTS environments is supported. 3100.06 4 tiers support is not supported for FAST (full volume movements). 3100.07 Compression is not supported for FAST (full volume movements). 2100.01 FLM supports a maximum of 32 device pairs at one time per host. 2100.02 FLM does not perform load balancing across multiple Fibre Channel directors. 2100.03 FLM does not support the migration of boot devices. 2100.04 FLM has been qualified with a maximum of eight source-array and eight target-array paths. 2100.05 When creating the required FLM SAN zones between the source Symmetrix DMX Series array and the target Symmetrix VMAX Series array, create individual zones between the front-end Fibre Channel ports. Creating mesh-line zones is not supported. 2100.06 On AIX with Veritas Volume Manager (VxVM), to unset the identity of the target FLM device: 1. Shut down the host server. 2. Unset the device identity. 3. Restart the host server. This ensures that VxVM sees the new target devices correctly.

2100.07 If the target Symmetrix VMAX Series array has 8,192 or more devices, the Veritas Volume Manager (VxVM4.1) must be loaded on Red Hat Linux 4.2 hosts before the FLM target device identity can be unset.

Enginuity Release Level 5876.159.102 Release Notes

17

Known problems and limitations

Product Federated Live Migration (FLM)

Updated Number N N N N N

Limitation

2100.08 You cannot load Enginuity while running active FLM sessions on the array. 2100.09 Symstat is not showing throughput statistics on a control device in an Open Replicator pull session (FLM). 2100.12 Front-end port settings on the source and the target arrays must be identical in order to activate an FLM session. 2100.14 Extra masking in the target array causes a precondition check to fail and blocks the activation of the session. 2100.15 When a DMP rescan is initiated in a state where the FLM session is active, and the target and source paths are passive, the passive paths to the source device are removed. If a manual or automatic failback is initiated at this time, I/O fails because paths to the target devices do not exist. 2100.16 FLM does not support Microsoft dynamic volumes and Cluster Shared Volumes (CSV) as cluster resources in Windows 2008 SCSI-3 MCS Clusters. 2100.17 In a two-node Windows 2003 cluster with PowerPath 5.3 (build 310), PowerPath displays duplicate paths after a cluster node crash or restart during an FLM session. 2100.18 In Windows 2003 cluster environments with PowerPath 5.3 and McAfee Antivirus installed, the default McAfee Antivirus Exclusion policies may limit device access during cluster resource moves. 2100.19 In Linux systems with Veritas DMP and FCoE HBAs installed, the device path names cannot be recognized by Veritas DMP. Because no paths are detected, FLM cannot use the host. 2100.20 In a Windows 2003 PowerPath Cluster, a precondition check fails if a node in the cluster is restarted after the FLM session creation but prior to the session activation. 2100.21 Port flags on the source and target arrays must be configured exactly the same in order to activate an FLM session. If this is not possible, the symforce option can be used as a workaround. 2100.22 FLM does not support the migration from R1 source devices in clustered environments.

N N N

SRDF compression for Fibre RA

2200.00 Write Acceleration (WA) on Fibre Channel SRDF links requires that software (VMAX 40K, VMAX 20K/VMAX) and hardware (VMAX 40K only) compression be disabled. 2200.01 SRDF hardware compression over Fibre Channel is only available on VMAX 40K arrays.

Mainframe: TPF_MPLF

N N N

670.02 670.04 670.05 680.00

RAID 5 and/or RAID 6 is only to be used in TPF for test environments, not in production. The EMC Product Suite for TPF 7.1.0.0 is required. The maximum number of allocated locks is 65,280 (FF00 hex) per SSID. The maximum number of active locks is 262,144 (40,000 hex) per frame. When XRC devices enter and exit a long busy state, the host may mis-orientate the I/O on the retry and overwrite the track and attempt to write past the end of the track, leading to potential data corruption. Follow all IBM-prescribed XRC optimizations to avoid long busy conditions to mitigate the exposure. Problem ticket opened with IBM - S3 APAR OA17943.

Mainframe: XRC

FlashCopy

2070.00 Utilizing a split configuration requires IBM APAR OA10765 to prevent data overlay/corruption.

18

Enginuity Release Level 5876.159.102 Release Notes

Known problems and limitations

Product SRDF: Peer-to-Peer Remote Copy (PPRC)

Updated Number N 330.00

Limitation PPRC is limited to utilizing only the first 64 SRDF groups.

N N Online maintenance procedures N

330.01 330.02 810.00

Online Enginuity upgrades are not recommended while running PPRC commands, as the commands may time out. PPRC operations do not support SRDF pairs in which the R2 device is larger than the R1 device. RAID 5 and/or RAID 6 drives may become unavailable during an engine replacement. This occurs when: Two or more members of the same RAID 5 group are configured within the same engine. Three or more members of the same RAID 6 group are configured within the same engine.

FTS

N N N N N N N

8400.01 FTS with SRDF does not support SRDF/Star environment. 8400.02 FTS with SRDF does not support encapsulated R2 device. SRDF Swap for encapsulated FTS storage is not supported. 8400.03 FTS with SRDF does not support DSE save devices on external disks. 8400.04 FTS with SRDF does not support diskless R21 devices. 8400.05 Each dual initiator pair of DX directors must be configured within a single engine. 8400.06 You cannot add a BCV attribute to an encapsulated thin device (TDEV). 8400.07 If all DX links become unavailable to an FTS device, the device may become unavailable to the host after the link recovery process completes. The EMC Global Services personnel must get involved to make the device ready to the host. 8400.08 The maximum size of external array owned LUNs is 60TB. 8400.09 External devices must be configured to a separate thin pool. External and regular VMAX Series devices cannot be mixed within the same thin pool. 8400.10 Data at Rest Encryption (DARE) is not supported on external devices. 8400.11 FTS external devices cannot be used for Vault Drives. 8400.12 Each DX pair can support a maximum of 14K logical units. The maximum number of Logical Unit Numbers (LUNs) per external array storage port is 8K.

N N

N N

SRDF interfamily connectivity

N N

8600.00 SRDF interfamily 5876.159.102 5773 limitation: Enginuity 5773 must be at minimum of 5773.176.124. 8600.01 SRDF interfamily 5876.159.102 5671 limitation: SRDF thick-to-thin connectivity is only available in SRDF migration mode. Enginuity 5671 must be at minimum of 5671.81.78. 1200.09 Minimum version V9.0 of the BS2000 software SHC-OSD with SYMAPI V7.5.0 is required to manage the Enginuity related features from a BS2000 host. 9000.00 Please refer to the RecoverPoint Release Notes to enable heterogeneous replication configurations where device size is different between the source and the target device or enhanced thin device integration. 8500.00 RAID 6 (14+2) devices are not supported.

BS2000 RecoverPoint

N N

DMS

Enginuity Release Level 5876.159.102 Release Notes

19

Known problems and limitations

Product Support for thin CKD 3390 SRDF devices

Updated Number N

Limitation

9300.01 Thin CKD devices are not supported in SRDF/EDP solutions.

9300.03 Thick-to-thin CKD connectivity limitations in two-site SRDF solutions: The array containing the thin CKD devices must be running Enginuity 5876.159.102 or higher The array containing the thick CKD devices must be running Enginuity 5671, 5773, 5875, or 5876. Note: Enginuity 5773 and 5875 require an EPAC to be installed. Contact customer service representative for more detail. 9300.04 Thick-to-thin CKD connectivity limitations in concurrent and cascaded (non-Diskless) SRDF solutions: The array containing the thin CKD device must be running Enginuity 5876.159.102 or higher The array containing the thick CKD device must be running Enginuity 5773, or Enginuity 5876.159.102 or higher. Note: Enginuity 5773 requires an EPAC to be installed. Contact customer service representative for more detail. 9300.05 Thin CKD devices are not supported in SRDF/EDP or SRDF/Star implementations that use SRDF/EDP. 9300.06 Thick-to-thin CKD connectivity limitations in SRDF/Star solutions: The arrays containing the thin CKD devices must be running Enginuity 5876.159.102 or higher The arrays containing the thick CKD devices must be running Enginuity 5876.159.102 or higher.

FAST VP SRDF coordination GigE SRDF TimeFinder VP Snap

N N N

9500.00 Coordinating data movements with FAST VP on both sides of the SRDF links is only available in a two-site SRDF topology. 9600.00 IPSec is available only with 1 Gb/s GigE SRDF ports. 8100.01 Open Replicator with TimeFinder VP Snap supports PUSH operation only.

N N Host performance limits N N

8100.02 SRDF R1 and R2 devices can be the source but not the target devices in TimeFinder VP Snap sessions. 8100.03 TimeFinder VP Snap does not support thin CKD devices. 9800.0 0 Host performance limits feature is not supported on the FCoE protocol.

9800.01 If a command to delete a view is sent by the host that the view is constructed against, but not by a dedicated administration host, the connectivity may be lost and subsequent commands may fail. 9820.00 VP Compression will be limited to a maximum of 10TB of compressed data per engine. 9820.01 VP compression is intended for use with data that is seldom and lightly utilized. In the event that compressed data pools receive significant I/O workload, a system-wide performance impact can be expected.

VP Compression; FAST VP Compression VP Compression; FAST VP Compression

20

Enginuity Release Level 5876.159.102 Release Notes

Known problems and limitations

Product Thin FBA compression Support SYNC COMMIT for IDP Zero Space Reclamation

Updated Number N N

Limitation

9830.00 Thin FBA compression is not supported over the Mainframe channel. 9840.00 The command sync/commit is not supported for THIN CKD devices. This functionality is required for IDP secure erase as well as ICKDSF TRKFMT ERASEDATA utilities. 9300.02 Zero space reclamation is not supported for thick-thin FBA and CKD device pairs in which the thick device resides in a DMX array running Enginuity version 5671. Enginuity 5876.159.102 is required on arrays configured with thin devices.

Enginuity Release Level 5876.159.102 Release Notes

21

Troubleshooting and getting help

Troubleshooting and getting help

EMC support, product, and licensing information can be obtained on the EMC Online Support site as described next. Note: To open a service request through the EMC Online Support site, 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 service, go to the EMC Online Support site (registration required) at: http://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, as well as more dynamic content, such as presentations, discussion, 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 Customer Procedure Generator For customized documentation for managing EMC Symmetrix storage systems, go to EMC online support, and download this stand-alone utility. The Symmetrix Procedure Generator is updated regularly by EMC and contains a 30-day expiration timer to ensure you always have the latest validated procedures. Symmetrix System Viewer Illustrates the system hardware, incrementally scalable system configurations, and available host connectivity offered for Symmetrix VMAX systems, go to the EMC online support, and download this stand-alone utility.

eLicensing support
To activate your entitlements and obtain your Symmetrix license files, visit the Service Center on http://support.EMC.com, as directed on your 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 a LAC letter, or require further instructions on activating your licenses through the Online Support site, contact EMC's worldwide Licensing team at licensing@emc.com or call:

22

Enginuity Release Level 5876.159.102 Release Notes

Troubleshooting and getting help

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 2012 EMC Corporation. All rights reserved. Published in the USA. Published October, 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.

Enginuity Release Level 5876.159.102 Release Notes

23