Release Notes for Dmx Code 5773

Symmetrix DMX-3, DMX-4 EMC EnginuityRelease Level 5773.160.111

Release NotesP/N 300-011-107 Rev A01 June 8, 2010 GA Date 6/8/10

These release notes contain supplemental information about EMC Enginuity, Release Level 5773.160.111. Topics include:

Product description .............................................................................. 2 New features and changes .................................................................. 3 Changed Features................................................................................. 4 Environment and system requirements .......................................... 61 Known problems and limitations .................................................... 62 Technical notes .................................................................................... 69 Documentation ................................................................................... 69 Software media, organization, and files.......................................... 69 Installation ........................................................................................... 70 Troubleshooting and getting help .................................................... 70

1

Product description

Product descriptionThis is a new release of Symmetrix Enginuity. The 5773 platform supports the Symmetrix DMX-3, DMX-4 emulation level 160 and Service Processor level 111. Details of the new features are provided in New features and changes 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 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 5773.160.111 Release Notes

New features and changes

Naming conventionsEnginuity platform releases are denoted by a four-digit sequence. The 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 57 indicates that this platform supports the Symmetrix DMX-3 and the DMX-4. 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.

Enginuity release level names follow a naming convention of XXXX.EEE.SSS, where:

XXXX is the four-digit platform number (as described above) EEE is the three-digit emulation number SSS is the three-digit Service Processor number 5773 platform, which is the Symmetrix DMX-3, DMX-4 series Emulation level is 160 Service Processor level is 111

For example, 5773.160.111 indicates the:

New features and changesThe 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 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.


3

Fixed problems

New Features

This section identifies: New features and enhancements to existing functionality.

There are no new features added with this Enginuity release.

Changed Features

There are no changed features since the last Symmetrix VMAX Release, 5773.155.107.

Fixed problemsThis section identifies problems fixed in the product software release also detailed online in EMC Issue Tracker. EMC Issue Tracker offers online access for up-to-date product issue information. Product issues can be searched online in EMC Issue Tracker using a keyword, issue number, product feature, or product version. Issue Tracker can be accessed on the EMC Powerlink website at:http://Powerlink.EMC.com

4


Fixed problems

Product issue detailsProduct issues are sorted alphabetically by product feature and by issue number within each product feature. Product issue details include descriptions 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. Knowledgebase IDNumber of a relevant EMC Knowledgebase solution. Host OSOperating system version for the host type. Host TypeHost Type for the problem that is being reported. Problem SummaryHigh-level summary of the problem being reported. SymptomObservable behavior of the problem. Special ConditionsBrief description of the unique scenarios that may need to occur in order to reproduce the issue. Workaround or Fix SummaryDetailed description of what was fixed and any known workarounds. Found In VersionEMC product version where the problem was found. Impact LevelSeverity and impact of the issue. Impact StatementDescription of how the issue might affect the customers environment. Additional FeatureAdditional categorization of problems within an EMC product feature set.


5

Fixed problems

Fixed problems by product featureThis section provides information on fixed problems for the following product features:

Base Functionality on page 7 ESCON Channel on page 19 Fibre Channel on page 20 FICON Channel on page 21 iSeries (AS/400) on page 25 Mainframe on page 26 Mainframe-PPRC on page 27 Mainframe-TPF_MPLF on page 28 Online Configuration Change on page 29 Online Upgrade (NDU) on page 30 Open Replicator on page 30 Open Systems on page 32 RAID on page 32 RAID 5 on page 33 RAID 6 on page 35 SRDF Family on page 36 SRDF Family on page 36 SRDF-GigE on page 39 SRDF/A on page 40 SRDF/AR (SAR) on page 43 SymmWin on page 44 Thin Provisioning on page 52 TimeFinder Family on page 58 TimeFinder-Clones on page 59 TimeFinder-SNAP on page 60

6


Fixed problems

Base Functionality

Issue Number Fix Number Host OS Host Type Problem Summary Symptom Workaround or Fix Summary Found In Version Severity Impact Statement

27517388 48688 Any OS Any Host Enhancement request to add data consistency checking for single slot RAID operations where there are multiple XOR data modifications. Specific RAID 5 and RAID 6 Fixed Block Architecture (FBA) flows are not properly checked for data consistency. This fix adds data consistency checking for single slot RAID operations where there are multiple XOR data modifications. 5773.130.90 1 - Critical Potential Data Corruption

Issue Number Fix Number Host OS Host Type Problem Summary

29502722 47106 Any OS Any Host While debugging a Thin Provisioning issue, the SUMM command issued on a disk adapter for both data and Thin devices takes a long time to execute and drops the disk adapter slice to dead director state. The SUMM command run for data and Thin devices may take a long time to execute. This fix will reduce the number of devices in the loop and makes the SUMM command to display only the sub-totals instead of the count on every Thin or data devices. 5773.130.90 1 - Critical Maintenance Issue

Symptom Workaround or Fix Summary Found In Version Severity Impact Statement


7

Fixed problems


31720812 49576 Any OS Any Host When non-HANS director boards were replaced with HANS director boards, a message sent by a fibre adapter to lock a track was dropped to the same track continuously. This was due to the disk adapter receiving an unlock message for a track it did not own. Errors were logged when a disk adapter was performing a sequential read and was in the process of writing the lock on the cache slot. With this fix, if a disk adapter receives an unlock message for a device or track that it does not own, an empty pointer error will be logged, and we will move the temp_slot_chk_pointer to the address of the slot that the fibre adapter requested to be unlocked. 5773.141.98 1 - Critical Potential Data Unavailability



31884772 49938 Any SUN OS SUN SUN host(s) may lose the visibility of their devices after using symmask commands due to the Auto Contingent Allegiance condition being set improperly on these SUN host's devices. Then the Inquiry SCSI commands going to them are failing. In a fibre adapter port heterogeneous configuration (AIX/SUN) with the SCSI-3 flag set at the adapter level, SUN host(s) may lose the visibility of their devices after using symmask commands for setting hba_flags on new devices. This fix will set the SCSI-3 flag at the port level and not at the adapter level. 5773.138.96 1 - Critical Potential Data Unavailability

Symptom

Workaround or Fix Summary Found In Version Severity Impact Statement

8


Fixed problems


32322262 50094 Any OS Any Host During a vault restore, the IML fails to complete and the disk adapter drops to a dead director state due to the update director function being called prior to the function that initializes the device headers and Global Memory pointers. A disk adapter drops to a dead director state prior to the completion of a vault restore. With this fix, during a vault restore, IML will complete without logging errors. 5773.141.98 1 - Critical Potential Data Unavailability



32429394 49259 Any OS Any Host When an established Business Continuance Volume (BCV) was configured on a disk adapter, maximum write pending limits were reached on the R2 side of the SRDF/A. As a result, the SRDF/A dropped. The customer may experience a potential data unavailability issue when the SRDF/A drops due to the maximum write pending limit being reached by the R2 side. This fix will add ALL_SNGL where the function DAT_Update_Local_Director is called to update the local Non-Volatile Dynamic (NVD) table of the disk adapter using the information stored in the Global Memory. 5773.134.94 1 - Critical Potential Data Unavailability



9

Fixed problems


32597842 50255 Any OS Any Host Due to an environmental condition, vault drives did not participate in the vault save. As a result, we failed to restore as we tried to use vault drives with a stale vault image during the restore and logged CRC Mismatch errors. The customer may experience data unavailability because we tried to restore the Symmetrix using a stale vault image which leads to CRC mismatches during power up. This fix will mark a vault image as valid only after we have written vault metadata to the disk that contains the vault ID used in determining the integrity and validity of the vault image. This will prevent us from using a stale vault image because of an unsuccessful vault store operation. 5773.134.94 1 - Critical Potential Data Unavailability



32656774 50579 Any OS Any Host When the FE,CE inlines command was run on a disk adapter during an online drive upgrade, multiple drives went into the not ready state. The customer may experience a potential data unavailability issue after a single adapter IML and after all the devices on the disk adapter drop to a not ready state. With this fix, during an online drive upgrade, the only devices that will be in the not ready state after the IML are the invoked spares. 5773.141.98 1 - Critical Potential Data Unavailability

10


Fixed problems


331410SYM 50849 Any OS Any Host The inlines command 8D,FLST needs to be improved so that it stops at the end of the device when reading data ID table groups on a device. The inlines command 8D,FLST to read data ID table groups on a device, may continue to read outside the bounds of the device if the number of groups given go beyond the end of the device. With this fix, the inlines command 8D,FLST will stop at the end of the device and an illegal option will be returned if the user goes past the last track group. 5773.155.107 1 - Critical Maintenance Issue


31869274 49728 Any Open Systems OS Any Open Systems Host While adding a new user to SYMCLI database, a failure occurs with an error message. As a result, it blocks access on the Symmetrix to any host tied to the affected access control name and cause host application failures. The customer may experience an application failure while adding a new user to SYMCLI database as it blocks the access on the Symmetrix and the associated host. With this fix, an error will not occur while adding a new user to SYMCLI database. 5773.134.94 2 - Medium Application Failure

Symptom



11

Fixed problems


32165656 49942 Any OS Any Host When reading the Virtual ID table, a check to see which device we are pointing to starts with head 0. If a previous VSNAP session was cancelled due to corruption, there is no sanity check for it and the disk adapter does not know how to handle it. In this particular case, which is rare, when the customer cancels the VSNAP sessions due to corruption on devices involved in the VSNAP session, the disk adapters may take exceptions and drop to a dead director state. This fix will perform a sanity check for each head in case of corrupted log devices. 5773.141.98 2 - Medium Potential Data Unavailability

Symptom


Issue Number Fix Number Host OS Host Type Problem Summary Symptom

32252534 50189 Any OS Any Host There is no check to determine if an emulation processor monitor thread has the interrupts disabled. During the Full IML of a new remote fibre adapter, one of the processors encountered an interrupt during the IML resulting in it losing access to Global Memory. However the processor did not drop to IMPL monitor as expected. With this fix, there will be checks to determine if interrupts are disabled in each of the processor threads. If interrupts are disabled, they will be turned on and a dial home error will log. 5773.134.94 2 - Medium Maintenance Issue


12


Fixed problems


301518SYM 45311 Any Open Systems OS Any Open Systems Host The syscall that is called to create a Report Remote Target (RRT) session creates SAN Copy information in local and Global Memory. During the session clearing process, if there is a problem, local and global SAN Copy device information will not match. An error was logged on the Symmetrix due to a mismatch in the device number of the SAN Copy information and the Global Memory information. With this fix, no mismatch will occur in the device number and no error will be logged on the Symmetrix. 5773.141.98 2 - Medium Performance



312861SYM 47162 Any OS Any Host Enhancement request for improvement to the A3,ECBD scan so that it can construct iVTOC tables when required and update the appropriate counters. Improvements are needed around handling of DATA devices (specifically, unallocated DATA device tracks) when A3 scans are being run. This fix will add the requested improvements to the A3,ECBD scan. 5773.138.96 2 - Medium Maintenance Issue


13

Fixed problems


325317SYM 50097 Any OS Any Host When SRDF is run with SRDF-GigE adapter and heavy I/O, DMA timeouts and interrupts may occur. The customer may experience periodic exception IMLs on SRDF adapters. With this fix, exception IMLs will not be generated when SRDF is run with SRDF-GigE adapter and heavy I/O. 5773.141.98 2 - Medium Performance


330670SYM 50792 Any Mainframe OS Any Mainframe Host In Mainframe hosts, when IML was run with multi-virtual establish from one source to many virtual devices, establish failed and no session was registered for the pair. The customer may experience a performance issue due to virtual establish failure during IMLs in Mainframe hosts that run with multi-virtual establish from one source to many virtual devices. With this fix, multi-virtual establishes from one source to many virtual devices will not fail during IML. 5773.155.107 2 - Medium Performance

14


Fixed problems


330811SYM 50758 Any OS Any Host When the inlines command D0 is issued, the run_spin_up function fails and the recovery_task_retry_counter is not incremented, but the task does not timeout. The customer may experience an application failure, because on issuing the inlines command D0, the run_spin_up function fails and the recovery_task_retry_counter is not incremented. With this fix, the function init_ph_dv_failure_counters will be deleted in the run_spin_up function. 5773.155.107 2 - Medium Application Failure


321160SYM 49505 Any OS Any Host The device flag for Fixed Block Architecture (FBA)-shared and the FBA-CKD-shared bits in the physical device record field displays incorrect status. As a result, few errors are logged while updating the shared flags for each device. The customer may experience a performance issue as the device header field excludes the Mainframe adapters and the physical device record field displays incorrect status of the shared flags for each device. With this fix, the physical device record field will display the correct status of the shared flags for each device and ensure that no errors are logged while updating the shared flags. 5773.141.98 3 - Low Performance

Symptom



15

Fixed problems


26488744 43001 Any OS Any Host Enhancement request so that when there is an incorrect speed drive initialization or a wrong speed, it is easier for the PSE to determine this by changing the display to yellow. Currently when there is an incorrect speed drive initialization or a wrong speed, it is difficult for the PSE to determine this due to the display being in white. With this fix, a yellow color will be displayed that indicates any failure during the drive initialization or an incorrect speed drive in the system. 5773.123.83 4 - Enhancement Maintenance Issue


32657734 50333 Any OS Any Host After the Enginuity 5772 to 5773 NDU, the Group ID Number (GIDN) table may get corrupted and enhancements are required to improve the GIDN table displays. The customer may experience corruption in the displays of the GIDN table after the Enginuity 5772 to 5773 NDU. This fix will improve the displays of the GIDN table and also introduce the 8F,DPR display. 5773.155.107 4 - Enhancement Maintenance Issue

16


Fixed problems


291624SYM 44416 Any OS Any Host An enhancement request to change the mode selection of all the SATA drives operating behind the Northstar card to reduce the SMART polling threshold from 60 seconds to 24 hours. Performance impact for Symmetrix systems running SATA drives due to the SMART polling threshold of the Northstar card. This fix will reduce the SMART polling threshold of SATA drives operating behind the Northstar card from 60 seconds to 24 hours. 5773.130.90 4 - Enhancement Performance


322275SYM 49521 Any OS Any Host Enhancement request to capture details of an R1 to R2 resynchronization error. No customer reported symptoms. This fix will add more detailed errors when a resynchronization job fails on the R2 side. 5773.141.98 4 - Enhancement Maintenance Issue


17

Fixed problems


330392SYM 50787 Any OS Any Host Enhancement request to add a new inlines command for the device statistics buffer since the existing inlines command works for a single device and does not clear the host performance statistics for a device range. Due to a change in the device statistics buffer for Enginuity 5773, a new inlines command is needed that clears the host performance statistics for a range of devices. This fix will add a new inlines command which will clear the host performance statistics for a device range. 5773.141.98 2 - Medium Maintenance Issue



32034128 49809 Any OS Any Host A clone copy may become stuck when a Hot Spare is invoked against a RAID group with 7+1 protection, and then at a later time is invoked against a RAID group with 3+1 protection. The customer reported a clone copy becoming stuck. This fix will eliminate the stuck RAID jobs for this case. 5773.141.98 1 - Critical Potential Data Unavailability

18


Fixed problems


332560SYM 50975 Any OS Any Host When job cleanup is done at the time of SCSI reset, the data slot locked during the task read full track, in response to Disk Media errors during media scrubbing operation, is not unlocked. The customer may experience a potential data unavailability issue when the process of job cleanup during SCSI reset does not unlock the data slot locked by the task read full track operation that occurs in response to Disk Media errors during the media scrubbing operation. With this fix, Enginuity will be modified to unlock the data slot for the task read full track operation. 5773.155.107 2 - Medium Application Delay


ESCON Channel


329814SYM 50712 Any Mainframe OS Any Mainframe Host After a halt-I/O takes place on one port of an ESCON adapter, unconditional disconnect sequence is observed on the ESCON port with Fixed Block Architecture (FBA) I/O. The customer may experience an application delay due to unconditional disconnect sequence observed on the ESCON port with FBA I/O after a halt-I/O takes place on the other port of the same ESCON adapter. May only occur when FBA devices are configured on the ESCON adapter.

Special Conditions


19

Fixed problems


This fix will set the executing_port variable in the logical disconnect task end when the ESCON adapter handles a FBA I/O, so that there are no unconditional disconnects. 5773.155.107 2 - Medium Application Delay

Fibre Channel


29764910 50161 Any Open Systems OS Any Open Systems Host Due to a large number of devices configured to a single fibre adapter, there was a delay on the I/O to meta head as the first meta member does not start the execution until the second meta member completes all the open commands. The customer may experience a performance issue due to a large number of devices configured to a single fibre adapter that causes a delay to respond to the command among the meta members. With this fix, the large number of devices will be divided into small meta devices so that all the meta members will respond to the command on time. 5773.138.96 1 - Critical Performance

Symptom



32088932 50535 Any Open Systems OS Any Open Systems Host An adapter that is not part of a PowerPath group does not remove a lock after it realizes that it cannot access a device that was reserved from a PowerPath host.

20


Fixed problems


A device was being used by a number of hosts with PowerPath. A Logical Unit Number (LUN) and at least one host that did not have PowerPath became inaccessible to the customer. With this fix, an adapter that is not part of a PowerPath group will be able to release the device lock that was reserved from a PowerPath host. 5773.141.98 2 - Medium Potential Data Unavailability


29145088 47062 Any Open Systems OS Any Open Systems Host Since the 8F, STAT inlines command was updated to collect device response times on all meta members, there have been some situations when there are not enough available buffers to gather response time statistics for all devices on the fibre adapter. Customer performance may be affected in large configurations when gathering meta member response times, due to the limit of 1024 buffers on a fibre adapter. This fix will provide additional buffers for collecting meta member response time statistics. 5773.134.94 4 - Enhancement Performance


FICON Channel

Issue Number Fix Number Knowledgebase ID Host OS Host Type

32023846 49781 emc227007 Any Mainframe OS Any Mainframe Host


21

Fixed problems

Problem Summary

When the Service Processor had a script failure, LOGREC sent a large amount of old SIM alert messages to the MVS Console due to a problem with env_data_sense_bytes using an improper number of bytes for the SSID. The customer may experience a performance impact if the Service Processor has a script failure and cannot dial home. An environmental error was logged and SIM alert messages were sent to the MVS console. Along with this, LOGREC sent a large amount of old SIM alert messages, causing host performance impact. This fix will check the SSID for the environmental error code in the LOGREC event history to ensure that it has the correct SSID value and is not zero. 5773.134.94 1 - Critical Performance

Symptom



32443912 50450 Any OS Any Host When a recoverable disk error logged on a RAID 10 device, the disk adapter performed a full-track read of the track and overwrites the write pending data in cache. A RAID 10 device logged a recoverable disk error but dropped to write disabled status. Later, FICON adapters logged data miscompare errors and disk adapters logged data miscompare errors. With this fix, the track will not become write pending, and a disk error will not be logged. 5773.141.98 1 - Critical Potential Data Unavailability


Issue Number Fix Number Host OS Host Type

33701764 50822 Any Mainframe OS Any Mainframe Host

22


Fixed problems

Problem Summary Symptom Workaround or Fix Summary Found In Version Severity Impact Statement

Establish/Remove Logical Path (ELP/RLP) activity from Initial Program Loads (IPLs) of other Logical Partitions (LPARs) affected the online state of a previously working device. The customer may experience a potential data unavailability issue when the FICON adapters drop dead and when I/Os are halted from the routine get_sio_dvlp_pointer. With this fix, ELP/RLP processing will be changed to use only the logical path index, ignoring the device index, which may be invalid in that case.3 5773.138.96 1 - Critical Potential Data Unavailability


320934SYM 49492 Any Mainframe OS Any Mainframe Host The way that the GST queue handles duplicate SIM MSG needs to be changed. A FICON adapter is flooding the Mainframe Master Console with duplicate SIM MSG alerts. With this fix, in the GST queue, the time and details of the last error will be remembered, and this will be used to make sure the same message is not sent again within 10 minutes of the previous message. 5773.141.98 1 - Critical Potential Data Unavailability


31412578 49494 Any Mainframe OS Any Mainframe Host When setting 2107 mode, the adapter that receives the command 27-1D is presenting ending status, before other adapters execute the set system characteristics function.


23

Fixed problems


The customer reported that after setting 2107 mode, the first device of the Channel Unit (CU) still reported 3990. With this fix, the command 27-1D will not present channel end and device end before other adapters can execute the set system characteristics function. 5773.141.98 2 - Medium Maintenance Issue


312216SYM 47838 Any Mainframe OS Any Mainframe Host When the End of File (EOF) record was written by using a long Channel Command Word (CCW) count, Logic errors were logged, because all the extra count Information Units (IUs) did not arrive when the CCW Direct Multiple Access (DMA) was closed. The customer may experience an application failure when the EOF record is written by using a long CCW count which results in the logging of Logic errors. With this fix, the DMA end will not be executed before waiting for the extra count of the IUs and the EOF record will not be written by using a long CCW and Logic errors will not be logged. 5773.138.96 2 - Medium Application Failure



321162SYM 49586 Any Mainframe OS Any Mainframe Host The 2107 command Read Configuration Data (RCD) returns all logical paths for physical box, which exceeds the 2107 limit of 1280 paths per port. That is not consistent with command Set Interface Identifier (SII) which returns results for the split.

24


Fixed problems


ICKDSF command ANALYZE UNIT(xxxx) NODRIVE NOSCAN ALLOWONLINE does not retrieve all established logical paths. With this fix, the RCD command will return results for the split, consistent with the SII command. 5773.141.98 3 - Low Application Failure


281396SYM 42833 Any Mainframe OS Any Mainframe Host Due to a mismatch between the target Fibre Channel (FC) and source FC incremental relation under the active relation background copy, an incorrect host combination rejects the command and logs a FlashCopy error on the FICON adapter. The customer may experience a maintenance issue on the FICON adapter as the incorrect sense information for the FlashCopy restore command returns with an invalid restore. With this fix, the correct sense information for FlashCopy restore command will be returned with valid restore and no FlashCopy error will be logged on the FICON adapter. 5773.123.83 4 - Enhancement Application Failure


iSeries (AS/400)


31729178 49903 OS/400 iSeries


25

Fixed problems


Enhancement request to iVTOC all the new and the recycled Symmetrix devices from another host before presenting them to the iSeries AS/400 host or it may lead to multiple issues. The customer may experience a maintenance issue due to the absence of iVTOC, as the contents are not zeroed out before using the Symmetrix devices on another host. With this fix, all the devices will be iVTOCed when presenting them to the iSeries AS/400 host. 5773.138.96 4 - Enhancement Maintenance Issue

Mainframe


32290698 50156 Any Mainframe OS Any Mainframe Host A Parallel Access Volumes (PAV) token reported on a fibre adapter command is reflecting the previous PAV mode, after a command 27-1D PAV mode switch. FlashCopy will not run to one device when PAV is turned on. With this fix, when the host issues a fibre adapter command, after a command 27-1D PAV mode switch, but before a command F9 completes, the control unit will report the PAV mode to which it is switching. 5773.138.96 1 - Critical Application Failure


32727620 50389 Any Mainframe OS Any Mainframe Host

26


Fixed problems


When the dataset has more than 256 bytes and there is no active FlashCopy session on the device, the Symmetrix displays incorrect length on the dataset. The customer may experience a performance issue as Symmetrix displays incorrect length due to an inactive FlashCopy session on the data sets. With this fix, all the data extents will be completely read before returning. 5773.134.94 3 - Low Performance

Mainframe-PPRC


33205456 50593 Any Mainframe OS Any Mainframe Host While running the GDPS script, some PPRC devices had DUPLEX status whereas the Target Not Ready (TNR) was set incorrectly on the SRDF link. As a result, a Data Corruption error was logged and dropped the device to a not ready state. The customer may experience potential data corruption during the GDPS script as the Peer to Peer Remote Copy (PPRC) devices are not in the suspend state when the PPRC resynchronization command is issued. This fix will update the PPRC devices suspend state when the PPRC resynchronization command is issued and no Data Corruption error will be logged during the GDPS script. 5773.155.107 1 - Critical Potential Data Corruption

Symptom



27

Fixed problems

Mainframe-TPF_MPLF


20780478 43320 Any Mainframe OS Any Mainframe Host An old version of TPF RDC interpreted a 3390 emulation for a 3380 device. This causes it to fail the emulation check leaving it unable to be varied online. The customer was unable to vary online a 3390 device because TPF PUT level 8 does not recognize RDC byte 6 bit 6 (prefix enabled). With the fix, specific RDC bits will only be turned on if command 27-1D is received. 5773.130.90 2 - Medium Application Failure


319726SYM 49268 Any Mainframe OS Any Mainframe Host CRC errors may log in a Mainframe TPF_MPLF environment if early DMA is allowed without being protected by a device lock, extent, or TPF NAME lock. The customer may experience CRC errors being logged in a Mainframe TPF_MPLF environment, due to inconsistent data if the early DMA read is done before locking the cache slot, and multi-access read/write is allowed without multi-extent protection. With this fix, early DMA will be blocked if it is not protected by a device lock, extent, or TPF NAME lock. 5773.141.98 2 - Medium Application Failure


28


Fixed problems

Online Configuration Change


309123SYM 20008787 Any OS Any Host When the Online Configuration Change script is run to add new IP addresses to the existing SRDF-GigE groups, the SRDF group becomes offline. The customer may experience an application failure, if the SRDF group becomes offline when new IP addresses are added to the existing SRDF-GigE groups. This fix will skip steps that require the SRDF group to go offline while adding new IP addresses to the existing SRDF-GigE groups. 5773.138.96 2 - Medium Application Failure


32240590 20009198 Any OS Any Host When adding disks and devices, one of the newly added disks failed. The disk replacement script was used to replace this drive. The disk replacement script is not meant to handle drives that have volumes configured with not ready flags. During a disk drive replacement script, Track ID allocation errors led to cache slot timeout errors, cache slot lock errors, task timeout errors, and Track ID table read errors, causing a data unavailable situation for the customer.

Symptom


29

Fixed problems


With this fix, the disk replacement script will not be allowed to handle a drive that has a not ready bit set. 5773.138.96 4 - Enhancement Potential Data Unavailability

Online Upgrade (NDU)


32600490 50296 Any Open Systems OS Any Open Systems Host An Enginuity 5772 to 5773 NDU may cause a Group ID Number (GIDN) table corruption. While performing an Enginuity 5772 to 5773 NDU, the GIDN table is converted, and this conversion may cause problems with the table. Although this issue can occur during a NDU and not initially result in a problem for the customer, it may cause a problem later on. With this fix, during an Enginuity 5772 to 5773 NDU, the GIDN table will not be corrupted. 5773.141.98 1 - Critical Potential Data Unavailability


Open Replicator


28429972 46300 Any OS Any Host

30


Fixed problems


Open Replicator copy push currently flushes tracks immediately out of cache; this does not leave a tail for prefetch to follow while making prefetch determination. Poor performance during the cold Open Replicator push sessions. With this fix, avoid flushing tracks from cache after they are pushed and the duration of the session will be longer. 5773.134.94 1 - Critical Performance


31557914 49090 Any Open Systems OS Any Open Systems Host There were performance issues on the local host I/Os when an Open Replicator hot pull was performed by using the ceiling option to modify the Open Replicator throughput. The customer may experience performance issues in the local host I/Os when there is an Open Replicator hot pull by using the ceiling option. With this fix, the host I/Os will increase when the ceiling value is decreased for the Open Replicator throughput. 5773.138.96 1 - Critical Performance


318055SYM 49031 Any Open Systems OS Any Open Systems Host During an Open Replicator foreground operation, the link dropped causing a timeout at data transfer. This incremented the same queue record which was used but the cylinder and head matched the original values.


31

Fixed problems


An Open Replicator miscompare error logged during a hot pull session. With this fix, no mismatch will occur between Open Replicator session queue record and the cylinders original values. 5773.141.98 3 - Low Potential Data Unavailability

Open Systems


303142SYM 45738 Any Open Systems OS Any Open Systems Host Enhancement request to add the new Read End Of Track algorithm to work for Flash drives. Performance problems may occur with the new Read End Of Track algorithm for Flash drives. With this fix, the new Read End Of Track algorithm will work for Flash drives. 5773.134.94 4 - Enhancement Performance

RAID


28536568 47803 Any OS Any Host Disk scans were aborted with the message: Online scan cancelled for device.

32


Fixed problems


When a disk scan encounters a cylinder head which has a media error, it gets hung for a few seconds and then aborts the scan. With this fix, disk scans will not abort until they complete. 5773.134.94 2 - Medium Maintenance Issue

RAID 5


28123492 46995 Any OS Any Host An error logs on a disk adapter indicating bad parity. This error will occur only on one disk adapter and to one physical drive and there will be no other errors on the drive. If a drive fails and it does not log hardware errors, but instead only logs logical errors, and it is RAID 5 with optimized writes, then it is possible that the corresponding parity track on another member of the RAID group will be built with bad parity. This fix will perform the parity sanity checking during optimized writes and adds a check for CRC validation. 5773.130.90 1 - Critical Potential Data Unavailability





33

Fixed problems

Problem Summary Symptom

Cache slot lock timeout errors log when a RAID 5 device is in the I/O blocking mode during a fast IML and a host adapter rebuild request is blocked from being sent to the other RAID members. A Fast IML with a fibre loop recovery occurring moves a RAID 5 device into the I/O blocking mode. In order to service a read, it is necessary to send a host adapter rebuild request to the other RAID members, but the request is blocked, which may lead to a data loss situation for the customer. With this fix, when creating a task, if we are in the I/O blocking mode, a force host adapter rebuild will allow the task to be created so that clean up can take place. 5773.134.94 1 - Critical Potential Data Unavailability



322594SYM 50890 Any OS Any Host The disk adapter logic is not checking who owns the cache slot before writing the data which causes CRC errors. The customer may experience a potential data unavailability issue during the RAID 5 operations if the disk adapter does not check for the owner of the cache slot before the data is written on those slots. This fix will ensure that the RAID 5 operations retain data slot locks at key transition points so that the disk adapters check for the owner of the cache slot before the data is written on those slots. 5773.141.98 1 - Critical Potential Data Unavailability


34


Fixed problems


328460SYM 50459 Any OS Any Host When the function check_if_need_to_invalidate_parity considers parity as the source of data, the data and parity are invalidated for a RAID 5 track resulting in data unavailability. The customer may experience a potential data unavailability issue if the function check_if_need_to_invalidate_parity() considers parity as the source of data that invalidates the data and parity for a RAID 5 track. This fix will remove Hot Spares from any source of data check and will exclude parity from a mirror level check so that data and parity are not invalidated for a RAID 5 track. 5773.155.107 1 - Critical Potential Data Unavailability


RAID 6


32501124 51016 Any OS Any Host The physical consistency bit set on a RAID 6 device during a rebuild allows the disk adapter to know which tracks still need to have rebuild tasks generated. The physical consistency bit may be cleared if a data miscompare error logs during the rebuild. Equipment check and CRC errors may occur if the physical consistency bit on a RAID 6 device is cleared prematurely after a rebuild error.

Symptom


35

Fixed problems


This fix will ensure that the physical consistency bit on a RAID 6 device is cleared when the data track is invalidated. 5773.134.94 2 - Medium Potential Data Unavailability


33044858 50433 Any OS Any Host The D8C inlines command with the FORCE option does not work on unrebuild tracks for RAID 6 devices. Issuing D0,D8C inlines command with the FORCE option, in a RAID 6 environment results in an Online Scan Cancelled error. With this fix, the Online Scan Cancelled error will not occur while issuing the D0,D8C inlines command with the FORCE option, in a RAID 6 environment. 5773.141.98 2 - Medium Maintenance Issue

SRDF Family

Issue Number Fix Number Knowledgebase ID Host OS Host Type Problem Summary

30656804 49872 emc223884 Any Mainframe OS Any Mainframe Host During Geographically Dispersed Disaster Restart (GDDR) operation, the SRDF mirrors of the device that are also part of a SRDF/Star site swap indicates a not ready state on the link and displays a dark blue X on the A7 display.

36


Fixed problems


After each swap, a dark blue X was displayed on the A7 display under the SRDF mirrors while performing a GDDR operation. With this fix, a dark blue X will not be displayed on the A7 display under the SRDF mirrors during the GDDR operation. 5773.134.94 1 - Critical Application Failure


32925240 50547 Any OS Any Host The write pending pyramid search algorithm for mirrored devices becomes stuck while checking a track that is partial write pending and invalid locally. This causes other SRDF write pending tracks coming from the partner Symmetrix not to destage. A SRDF Migration terminates unexpectedly due to write pendings building up to the point that the R1 devices will drop not ready on the SRDF links. This fix will allow the algorithm to randomize the starting cylinder based on the system base timer to avoid pyramid search becoming stuck on some tracks. 5773.141.98 2 - Medium Performance



28430222 50137 Any Mainframe OS Any Mainframe Host The clone operation fails if an R2 clone source device is in the not ready SRDF state. The customer may experience failure of the clone operation if SRDF is in the not ready state.


37

Fixed problems


With this fix, Enginuity will allow a SRDF device that is marked not ready as a source of clone control commands. 5773.134.94 2 - Medium Application Failure


326018SYM 50244 Any OS Any Host When one of the SRDF internal functions fail, incorrect information is given for failed SRDF I/Os and many unexpected errors are logged on the host adapters. Also, the registers get corrupted and SRDF/A errors are logged. The customer may experience issues due to failure of one of the SRDF internal functions. With this fix, only expected errors will be logged on the host adapter when SRDF I/Os fail. 5773.155.107 2 - Medium Application Failure



328082SYM 50503 Any OS Any Host When an attempt is made to move a large numbers of devices between SRDF groups by using SYMCLI, a common lock timeout may occur. The customer may experience an application delay due to common lock timeout during the process of moving a large numbers of devices between SRDF groups by using SYMCLI.

38


Fixed problems


With this fix, the move will work properly, but if a large number of groups is selected to be moved, SYMCLI will send only 100 devices at a time. 5773.155.107 2 - Medium Application Delay


326917SYM 50354 Any OS Any Host Enhancement request to add a log in Global Memory to store a history of name server lists. There are occasions after an online Enginuity load or after a temporary network issue a full IML of both GigE and Fibre SRDF adapters had to be performed in order to recover the SRDF link. This fix will add a log in Global Memory to store a history of name server lists which will contain the current and previous lists. 5773.155.107 4 - Enhancement Maintenance Issue

SRDF-GigE


32669046 50261 Any OS Any Host The initiator side of a SRDF-GigE setup detects paths to another SRDF-GigE director that it does not have, due to old targets not being cleared. It then retries to create this link, but never succeeds. This will affect SRDF performance.


39

Fixed problems


The customer may experience reduced SRDF performance, reduced IO/s, increased latency, and SRDF control operations may take longer, when operating with SRDF-GigE adapters. This fix will clear out old target entries before they can be reused to keep the data structure accurate. 5773.134.94 2 - Medium Potential Data Unavailability

SRDF/A


29705448 47824 Any OS Any Host Destage of write pendings was slowed by clone copy on the R2 even if devices were at the Dynamic Maximum Write Pending (DMWP) ceiling. There should be a provision to dynamically change the copy priority or stop it when devices hit the DMWP ceiling. SRDF/A dropped due to restore delays on the R2 caused by a slow destage of write pendings to devices at DMWP. With this fix, when a device write pending count or system write pending count is high (more than half of the write pending limit), copy urgency will be lowered at the device level. 5773.138.96 1 - Critical Application Delay




40


Fixed problems

Problem Summary

Delta Set Extension cleanup runs for at least one hour after SRDF/A drops due to non-user requests. Slots are kept in cache until spillover cleanup completes and may cause host timeouts due to lack of write pending space in the system. After an SRDF/A drop, slots are kept in cache until spillover cleanup completes. This may take a very long time causing host timeouts. With this fix, the SRDF/A group cache consumption will decrease and will reach zero before spillover cleanup is completed. 5773.134.94 1 - Critical Potential Data Unavailability



31995412 49921 Any OS Any Host An error was logged on the SRDF adapter when the COUNTS_IN operation failed on an R21 device and SRDF/A dropped. SRDF/A will hang and eventually drop in certain Cascaded SRDF environments. With this fix, errors will not be logged on the R21 device when SRDF/A performs the process of I/O transfer. 5773.155.107 1 - Critical Application Delay


33769566 50961 Any OS Any Host The disk adapter increments twice the copy I/O in the SRDF queue for every copy I/O. As a result, the SRDF queue reports SRDF QUEUE FULL to the disk adapter even if the actual number of copy I/O is half the actual queue size.


41

Fixed problems


The customer may experience a performance issue while copying the invalid tracks in a SRDF/A group when SRDF/A is active. With this fix, the actual number of copy I/O will be equal to the actual queue size while copying the invalid tracks in an SRDF/A group with an active SRDF/A session. 5773.141.98 1 - Critical Performance


30384582 49902 emc226755 Any Mainframe OS Any Mainframe Host SRDF/A keeps specific transfer cycle counters for reporting purposes. With IMS WADS, copying the counters (two per device) while holding the SRDF/A lock for that SRDF group is taking up the time and blocking the close syscall from completing. The customer may experience intermittent long response times on IMS WADS data sets during a SRDF/A cycle switch. With this fix, we will wait to update the cycle statistics until after the SRDF/A window closes. 5773.134.94 2 - Medium Application Delay



34803562 43980 Any OS Any Host When the last device is removed from an active SRDF/A session with movepair, the SRDF/A session may not drop.

42


Fixed problems


The customer may experience an application failure when the SRDF/A session stays active in spite of removing all the devices from an SRDF/A group with movepair. With this fix, the SRDF/A session will become inactive when all the devices are removed from the SRDF/A group. 5773.134.94 2 - Medium Application Failure


326875SYM 50342 Any OS Any Host When a disk adapter tried to deallocate the entire Thin track group and remove the SRDF/A duplicate slots, instead of marking the SRDF/A duplicate slots as invalid, the standard slot was removed leading to SRDF/A Hash errors. The customer may experience an application delay due to SRDF/A getting stuck during the deallocation of the track groups on the Thin devices. This fix will reassign the cache slot pointer in the Track ID to the duplicate slot after the invalids are set, so that the slot will not get removed from the SRDF/A cycle, but the deallocation of the entire Thin track group will continue. 5773.155.107 2 - Medium Application Delay


SRDF/AR (SAR)

Issue Number Fix Number Knowledgebase ID Host OS

13703011 30369 emc123534 Any Mainframe OS


43

Fixed problems

Host Type Problem Summary Symptom Workaround or Fix Summary Found In Version Severity Impact Statement

Any Mainframe Host A device not ready was sent after an Enginuity Consistency Assist (ECA) clear due to an adapter other than the adapter that the I/O is issued on, clearing the ECA. The customer reported that the Consistency Group tripped on a device that was iinvolved in SRDF/AR and had just been involved in a consistent split. With the fix the Consistency Group will not trip. 5773.79.58 2 - Medium Application Delay

SymmWin


32150612 20009298 Any OS Any Host During a configuration change, NDU, or Enginuity upgrade, the step that does cache checking is not able to recover a locked cache slot that is left from a failed syscall. This step should be changed to allow recovering a cache slot in this condition. Currently, during a configuration change, NDU, or Enginuity upgrade, if a locked scratch slot from a failed syscall is detected, the scripts will halt with a message that the script cannot continue due to a cache problem. This requires PSE intervention if more than four cache slots are found in this condition. This fix changes the relevant step in the cache checking procedure, to recover the locked cache slots rather than halt the script and issue the red box message. 5773.138.96 1 - Critical Maintenance Issue

Symptom

Special Conditions Workaround or Fix Summary Found In Version Severity Impact Statement

44


Fixed problems


33449098 20009337 Any OS Any Host Enhancement request to improve the NDU script failure message when the script is failed for an invoked Hot Spare during an NDU from Enginuity 5772 to Enginuity 5773. The message should clearly indicate the potential danger in continuing with the script. The customer may experience a maintenance issue if a Hot Spare is invoked during an NDU from Enginuity 5772 to Enginuity 5773. The NDU script detected this situation and failed the script, but the failed script was resumed due to the failure message not clearly indicating the situation. This fix will improve the NDU script failure message and will add a new flag to prevent accidentally resuming the failed script. 5773.155.107 1 - Critical Maintenance Issue

Symptom



29790708 20008684 Any OS Any Host During a permanent sparing process, a duplicate dds.log was getting generated from the original dds.log. As a result, it dialed home and was repeatedly calling out for a bad spare drive replacement. A duplicate dds.log is generated with similar information from the original dds.log and dials home, indicating a replacement needed to be performed when actually it has already been performed.

Symptom


45

Fixed problems


With this fix, the failed drive will only be reported once. 5773.134.94 2 - Medium Maintenance Issue


31327210 20008997 emc223017 Any OS Any Host The step to toggle volumes ready after the unmap is not in the Quick SDDR script, this step is only in the regular SDDR script, so devices that are unmapped with Quick SDDR are left not ready after unmapping from host. A customer set a device not ready and unmapped it. The unmap completed successfully; however, the device remained not ready. With this fix, when using Quick SDDR script, the devices that are unmapped with Quick SDDR will not be left in a not ready state after unmapping from the host. 5773.138.96 2 - Medium Potential Data Unavailability



309123SYM 20008787 Any OS Any Host When the Online Configuration Change script is run to add new IP addresses to the existing SRDF-GigE groups, the SRDF group becomes offline. The customer may experience a maintenance issue, because the SRDF group becomes offline when new IP addresses are added to the existing SRDF-GigE groups.

46


Fixed problems


This fix will skip few steps that require the SRDF group to become offline while adding new IP addresses to the existing SRDF-GigE groups. 5773.138.96 2 - Medium Maintenance Issue


26174396 20008014 Any OS Any Host If a Hot Spare fails in the Symmetrix DMX and the user cannot attach to any error to run the Returned Material Authorization (RMA), the RMA script will not show the location of the Hot Spare that has failed. While running the RMA script to replace a Hot Spare, the Hot Spare does not show up in the Please define the physical of the failing drive part of the RMA script. With this fix, the RMA script will display the location of the Hot Spare that has failed. 5773.79.58 3 - Low Maintenance Issue



32599868 20009244 Any OS Any Host Enhancement request for before and after the NDUs, the information of a Group ID Number (GIDN) should be saved, and a display should be added for grouping. Enhancement request to add display for grouping prior to and after the NDUs.


47

Fixed problems


With this fix, a new step will be added before and after loading Enginuity in order to display the GIDN tables. 5773.141.98 3 - Low Maintenance Issue


327290SYM 20009256 Any OS Any Host Enhancement request to change the variable capacity from longint to the longword, so that it supports 2TB drives and does not log Range Check errors. The customer may experience a maintenance issue due to a large size of the drive, which may cause the SymmWin script to fail while replacing the spare drive. With this fix, no failure will occur in the SymmWin script while replacing the spare drive and no Range Check errors will be logged. 5773.155.107 3 - Low Maintenance Issue


331188SYM 20009362 Any OS Any Host During an online configuration change script, some of the Thin devices were not marked as user not ready while adding the new Thin devices. The customer may experience a performance issue while adding a new Thin device as only few Thin devices are marked as user not ready.

48


Fixed problems


With this fix, the script handles the changes to the 98, FRMT inlines command and ensures that all the Thin devices are marked user not ready after being added. 5773.155.107 3 - Low Performance


25885528 20008512 Any OS Any Host Enhancement request to have a dial home created for when a Configuration/New Install script of a Symmetrix is run and the VTOC portion of the script fails. No customer reported symptoms. With this fix, under a dedicated flag, upon a script failure, a call home will be initiated. 5773.123.83 4 - Enhancement Maintenance Issue


26596358 20009396 Any OS Any Host Enhancement request to update the Environmental Control Module (XCM) replacement script to verify the status of the hex switches. If the hex switches display FE on power up, the Symmetrix system prevents the adapter from coming online. The customer may experience a potential data unavailability due to hex switches on both the XCM scripts being incorrectly set to FE instead of 08.

Symptom


49

Fixed problems


With this fix, the XCM replacement script will be updated to verify that the hex switches are set to 08. 5773.130.90 4 - Enhancement Maintenance Issue


27957628 20008463 Any OS Any Host Enhancement request to display the warning or errsfile.log for two and half minutes before a Symmetrix dials home during the process of field unit replacements and the running of other scripts. During the process of field unit replacements and running of other scripts, Symmetrix unnecessarily dialed home. With this fix, the warning or errsfile.log will be displayed for two and half minutes so that it can close before the popup from the previous error polling comes up in cases where error polling is triggered by errors and runs after the rest time. 5773.134.94 4 - Enhancement Maintenance Issue



32240590 20009198 Any OS Any Host When adding disk and devices, one of the newly added disks went bad. The disk replacement script was used to replace this drive. The disk replacement script is not meant to handle drives that have volumes configured with not ready flags.

50


Fixed problems

Symptom

During a disk drive replacement script, Track ID allocation errors led to cache slot timeout errors, cache slot lock errors, task timeout errors, and Track ID table read errors, causing a data unavailable situation for the customer. With this fix, the disk replacement script will not be allowed to handle a drive that has a not ready bit set. 5773.138.96 4 - Enhancement Potential Data Unavailability



312474SYM 20008658 Any OS Any Host Enhancement request to add a step in the SymmWin script to check the Last Recharge date on the Standby Power Supply (SPS) package. If the date is older than six months, it should be replaced by another spare part from stock. The customer may experience a delay in a SPS replacement if the Last Recharge date on the SPS package is more than six months old and has to be replaced by another spare part. With this fix, a step will be added to the SymmWin script to verify the Last Recharge date on the SPS package. The outdated SPS will be replaced by another spare part and hence, errors will not be logged. 5773.138.96 4 - Enhancement Maintenance Issue



324508SYM 20009304 Any OS Any Host Enhancement request to update the existing SymmWin warning message for the SRDF D0 inline Local to Remote (LTOR) options.


51

Fixed problems


No customer reported symptoms. With this fix, a correct SymmWin warning message will be displayed for all the LTOR options. 5773.141.98 4 - Enhancement Maintenance Issue


325714SYM 20009214 Any OS Any Host Enhancement request to add the support for 600GB 15K drives for policing dll. No customer reported symptoms. This fix will add support of the 600GB 15K drives for policing dll. 5773.155.107 4 - Enhancement Maintenance Issue

Thin Provisioning


29739474 47764 Any Mainframe OS Any Mainframe Host When there is a Thin device with SRDF invalid tracks, a disk adapter may spend a long time scanning invalids without doing any copy. A SRDF invalid track is sent from remote adapter to disk adapter in order to copy to SRDF, so this scan is not needed.

52


Fixed problems


Thin Provisioning devices are doing slow write destages, causing the Symmetrix DMX to hit system write pending thresholds. This fix will disable this scan for this case. 5773.134.94 1 - Critical Performance


32210340 50096 Any Open Systems OS Any Open Systems Host After a SQL dump to a virtual device pool, the disk adapter did not change the destaging priority because it was unaware that the write pending limit had been reached on the Thin devices in the pool. After a SQL dump to a virtual device pool, the customer experienced poor performance on Thin device destaging. With this fix, the disk adapter will change the destaging priority after a SQL dump to a virtual device pool. 5773.141.98 1 - Critical Performance



32691722 50890 Any OS Any Host Write pending delay and write space timeout errors log due to the cycle time required for the disk adapter to clean up the Virtual Snap sessions. The customer may experience a potential data unavailability issue when using Virtual Snap and the LOG/SAV pool becomes filled.


53

Fixed problems


This fix will ensure that Enginuity checks for lock validity in all the logic flows and checks will be added where it was previously lacking. 5773.138.96 1 - Critical Potential Data Unavailability


32395346 50083 Any OS Any Host Due to the absence of 8D,,,FLST inlines command to run as a background task, the Thin provisioning clean up utility drops the disk adapter to the Configuration File monitor mode in the data device. A scrubbing error may be logged if the Thin provisioning clean up utility in the data device drops the disk adapter to the IMPL monitor mode. This fix allows the 8D,,,FLST inlines command to run as a background task to prevent the disk adapter dropping to dead director state. 5773.141.98 2 - Medium Maintenance Issue



320152SYM 49348 Any OS Any Host Enhancement request to add logic so that, the scrubbing mechanism checks the Thin device pool information of each drive to detect pool corruption. No customer reported symptom.

54


Fixed problems


This fix will add a logic so that, the scrubbing mechanism checks the Thin device pool information of each drive to detect pool corruption. 5773.141.98 2 - Medium Maintenance Issue


326875SYM 50342 Any OS Any Host When a disk adapter tried to deallocate the entire Thin track group and remove the SRDF/A duplicate slots, instead of marking the SRDF/A duplicate slots as invalid, the standard slot was removed leading to SRDF/A Hash errors. The customer may experience an application delay due to SRDF/A getting stuck during the deallocation of the track groups on the Thin devices. This fix will reassign the cache slot pointer in the Track ID to the duplicate slot after the invalids are set so that, the slot will not get removed from the SRDF/A cycle, but the deallocation of the entire Thin track group will continue. 5773.155.107 2 - Medium Application Delay



333082SYM 51011 Any OS Any Host Since THIN_TASK11_INFO was not aligned to a structure based on eight bytes, the dv_read starts reading four bytes early. As a result, the IML considers that there is no task to resurrect and gets stuck. The customer reported that the Thin Provisioning operation had failed or had hung after an IML.

Symptom


55

Fixed problems


This fix will align the Thin structures to eight bytes, so that after an online IML they can successfully resurrect and complete the task. 5773.155.107 2 - Medium Maintenance Issue


327232SYM 50385 Any OS Any Host When issuing the 8D,,,STRP inlines command on the data device, the allocation table corrupts the code and logs a Thin Device error. As a result, this corruption is corrected by executing the auto recovery code. The customer may experience a performance issue as 8D,,,STRP inlines commands causes the auto recovery code to invoke. With this fix, the 8D,,,STRP inlines command will not cause the auto recovery to invoke. 5773.155.107 3 - Low Performance



331188SYM 20009362 Any OS Any Host During an online configuration change script, some of the Thin devices were not marked as user not ready while adding the new Thin devices. The customer may experience a performance issue while adding a new Thin device as only few Thin devices are marked as user not ready.

56


Fixed problems


With this fix, the script handles the changes to the 98, FRMT inlines command and ensures that all the Thin devices are marked user not ready after being added. 5773.155.107 3 - Low Performance


307853SYM 47086 Any OS Any Host Enhancement request to add a Fix Allocation Table (FAT) scan to recover all track groups for data and Thin devices. No customer reported symptoms. This fix will create a Fix Allocation Table (FAT) scan to recover all track groups for data and Thin devices. 5773.138.96 4 - Enhancement Maintenance Issue


327276SYM 50410 Any OS Any Host Enhancement request to improve the 98,POOL,RBLD inlines command as it cannot rebuild a single pool if the common area information is lost. No customer reported symptoms.


57

Fixed problems


With this fix, the 98,POOL,RBLD inlines command can rebuild all the pools. 5773.155.107 4 - Enhancement Maintenance Issue

TimeFinder Family


329169SYM 50674 Any OS Any Host The application protection count does not get decremented in reset_ccopy_protection_bit for a LOG device after the protection is cleared. This leaves an invalid counter for the LOG device and it is this counter that is checked when the drain is starting. Log device draining may fail due to protected tracks seen on the log device. With this fix, application protection count will get decremented to zero in reset_ccopy_protection_bit for log device after the protection is cleared. 5773.155.107 2 - Medium Application Failure



332011SYM 50930 Any OS Any Host When the log devices in the pool have a write pending delay, I/O timeout errors are logged against the virtual devices, because write to the multi-virtual target devices returned success status although the data was not copied to the virtual device.

58


Fixed problems


The customer may experience I/O timeouts against the virtual devices that are in a multi-virtual relationship. With this fix, there will not be any I/O timeouts on the virtual devices on a multi-virtual relationship. 5773.155.107 2 - Medium Performance

TimeFinder-Clones


31765132 49777 Any Open Systems OS Any Open Systems Host Cache errors were logged on a meta member and copy errors were logged on the Business Continuance Volume (BCV) after an online meta expansion IML occurred with TimeFinder Clone. These errors were caused by a slot lock incorrectly set by a fibre adapter. The customer may experience a potential data unavailability issue during an online striped meta expansion resulting in I/O and meta expansion script timeouts. With this fix, no errors will be logged, because the slot lock will not be incorrectly set. 5773.134.94 1 - Critical Potential Data Unavailability



28430222 50137 Any OS Any Host The clone operation fails if an R2 clone source device is in the not ready SRDF state.


59

Fixed problems


The customer may experience failure of the clone operation if SRDF is in the not ready state. With this fix, Enginuity will allow a SRDF device that is marked not ready as a source of clone control commands. 5773.134.94 2 - Medium Application Failure


32624760 50396 Any Open Systems OS Any Open Systems Host Normally, NXA (non-exclusive access) is enabled on devices and it allows the reads to be done with a cache slot lock instead of a device lock. Access mode for clone targets No Copy on Read feature can be changed on a fibre adapter. The customer may experience a performance issue if NXA is disabled and the device reads are done with a cache slot lock instead of a device lock. This fix will correctly set the access mode for the clone target device with a No Copy on Read feature. 5773.155.107 2 - Medium Performance


TimeFinder-SNAP


335436SYM 51420 Any Mainframe OS Any Mainframe Host When activating a multi-virtual device on a Mainframe, after the Establish is issued and then the query is performed, the query shows the 46xx session, but is missing the 56xx session.

60


Environment and system requirements


When running a multi-virtual create on a Mainframe, not all sessions show up on the query. With this fix, the query will show all sessions for a multi-virtual device on a Mainframe. 5773.155.107 1 - Critical Application Failure


331353SYM 50886 Any Mainframe OS Any Mainframe Host If multi-virtual devices are created, some tracks remain in the SAVEDEV SNAPPOOL after all the Virtual Snap and restore sessions are terminated. Few tracks remained in the log devices due to high virtual device pointer count. The customer may experience an application delay due to some tracks remaining in the SAVEDEV SNAPPOOL after all the Virtual Snap and restore sessions are terminated when multi-virtual devices are created. With this fix, there will be no more residual tracks in the SAVEDEV SNAPPOOL when all the multi-virtual sessions are removed. 5773.155.107 2 - Medium Application Delay

Symptom


Environment and system requirementsEnginuity 5773.160.111 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), consult the EMC Support Matrix (ESM), available through E-Lab Interoperability Navigator (ELN) at: http://elabnavigator.EMC.com, under the PDFs and Guides tab.


61

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 8) Number 1000.06 1200.01 1200.02 1200.03 1200.04 6750.00 6700.01 6700.05 6700.06 6700.08 6700.09 6700.13 Limitation With the maximum number of logical devices, the total number of logical devices is dependent on the RAID protection type. Minimum version V6.1A02 of the FSC software SHC-OSD is required to manage 5773 related features from a BS2000 host. BS2000/OSD only supports up to 7 aliases per device, but tolerates 15. Cascaded SRDF is not currently supported for BS2000 hosts. Virtual Provisioning is not supported for BS2000 hosts. Compatible Native Flash is not currently supported with Cascaded SRDF or SRDF/STAR. Flash drives are allowed with DMX-4 systems only. They cannot be configured in DMX-3 systems. Max 8 Flash drives per slice is allowed (64 Flash drives per quadrant). More Flash Drives per slice require RPQ. At least one spare Flash drive is required. Flash drives cannot be placed in powervault locations (first 4 slots in each direct connected DAE). SFS volumes are not allowed on Flash drives. Striped volumes (metavolumes and CKD RAID 10) cannot go across Flash drives and HDDs (this is automatically blocked as Flash drives will be in their own disk group, and striping is not allowed across disk groups) SecureErase is not supported with Flash drives. Symmetrix Optimizer will not swap volumes within a Flash drive in a disk group Dynamic sparing between unlike media types (i.e. Flash drive and HDD) is not allowed.

Product Base Functionality BS2000

Updated N N N N N

Compatible Native Flash Flash Drives

N N N N N N N

N N N

6700.16 6700.19 6700.20

62


Known problems and limitations

Table 1

Known problems and limitations (page 2 of 8) Number 22

Date post:	24-Oct-2014
Category:	Documents
Upload:	shahbaz-alam
View:	264 times
Download:	5 times

Release Notes for Dmx Code 5773

Documents