EMC CX200LC, CX200, CX400, CX600 FLARE Software

Version 02.16.yyy

Release Notes
P/N 300-002-135 REV A01 January 12, 2005

These release notes contain supplemental information about EMC CX200LC, CX200, CX400, and CX600 FLARE software (previously called Base Software). The software versions are 02.16.200.5.004 for the CX200LC and CX200 02.16.400.5.004 for the CX400 02.16.600.5.004 for the CX600 Product Description................................................................................... 2 New Features and Changes...................................................................... 2 Environment and System Requirements ................................................ 4 Fixed Problems ........................................................................................... 5 Known Problems and Limitations......................................................... 15 Technical Notes ........................................................................................ 21 Documentation ......................................................................................... 25 Installation ................................................................................................ 25 Troubleshooting and Getting Help........................................................ 28 Copyright and License Information ...................................................... 29

Topics include

Product Description

Product Description
FLARE software is the component of the FLARE Operating Environment that controls the operation of the CX200LC, CX200, CX400, and CX600 disk-array storage systems. Each storage system ships with a complete copy of FLARE software installed on the first four disks on back-end loop 0. Disks 0_0 and 0_2 store mirrored copies of the software for SP A, and disks 0_1 and 0_3 store mirrored copies of the software for SP B (except for the CX200LC). When you power up the storage system, each SP boots and executes FLARE software. FLARE software manages all functions of the storage system and supports very basic configurations. Customers desiring larger configurations, especially multiple host configurations, will benefit from an available Access Logix option enabler (see the Access Logix Release Notes, P/N 300-002-138). FLARE software supports only the following configurations: a single host dual-host split-bus two clustered hosts

New Features and Changes

Lun Migration
LUN migration is a feature that will, without disruption of host applications, allow a user to change performance and other characteristics of an existing LUN by migrating data from a source LUN to a destination LUN with the same or larger capacity and with desired characteristics within a single storage system. After LUN migration the original source LUN will be destroyed, the destination LUN will take on the source LUN's identity, and host I/O requests will continue to the destination LUN. This process occurs with no disruption to host I/O. Migration can be performed from a source LUN to a destination LUN of different characteristics, including Raid Geometry, drive types (FC vs. ATA), disk utilizations, and disk locations. Migration rate can be specified at initial configuration time and changed during migration to control performance impact. Migration has no data availability disruption to host or layered driver applications to the source LUN. It copies the content of the source LUN to the destination LUN while mirroring writes to both source and destination. It services host reads from the source LUN. 2
EMC CX200LC, CX200, CX400, CX600 FLARE Software Release Notes

New Features and Changes

Migration will hide the destination LUN from host or other layered driver. Upon completion of a migration the destination LUN atomically takes on source LUN's identity, including LUN nice name, WWN and LUN ID while keeping its other own parameters. The destination LUN is then exposed to the host or other layered driver and the source LUN is destroyed. A customer can cancel a migration. In this case the source LUN is left intact and unchanged while the destination LUN is destroyed for security reasons. Migration handles failure cases including recoverable and nonrecoverable errors.

Two Drive R1/0

With this release a 2-drive R1/0 LU can be configured. This LU will support all features that exist on a 4+ drive R1/0 LU. The main advantage of a 2-drive R1/0 LU over a R1 LU is that it will support RAID Group expansion.

EMC CX200LC, CX200, CX400, CX600 FLARE Software Release Notes

Environment and System Requirements

Environment and System Requirements

This section identifies the minimum requirements necessary for the proper operation of FLARE with the CX200LC, CX200, CX400, and CX600 storage systems.
Storage-System Type CX200LC Minimum Hardware Requirements
3 disks

Minimum Software Requirements Navisphere SP Agent version 6.16 and Navisphere Management Server version 6.16.

Supported 2-Gbyte Fibre Channel Disks Please see ESM.

Supported ATA Disks Please see ESM.

minimum, installed in slots 0 through 2 of enclosure 0

1 SP (A) 1 power supply 1 blower module

For write caching CX200, CX400, CX600

5 disks

minimum, installed in slots 0 through 4 of enclosure 0

2 SPs 2 power supplies 1 standby power

supply (SPS)

EMC CX200LC, CX200, CX400, CX600 FLARE Software Release Notes

Fixed Problems

Fixed Problems
This section identifies issues fixed with this release or recent previous releases. In addition to the following fixes, this release contains all fixes documented in prior releases of FLARE 02.xx software for the CX200, CX400 and CX600 platforms. See the FLARE Release Notes (P/N 085090686) for details.

Problem CX200, CX400, CX600 Benign 0x873 errors entered into the event log at powerup. (105148)

Detail Fixed in Revision: 02.16.xxx.5.004 Solution: Do not log the 0x873 errors unless the condition still persists at the end of Flare driver entry.

Fixed in Revision: 02.16.xxx.5.004 CX200, CX400, CX600 SP left in a non pingable and unresponsive state after a re-imaging attempt. (111471) Solution: Added data verification test. CX200, CX400, CX600 Degradation seen in large write Fixed in Revision: 02.16.xxx.5.004 performance during backup to ATA disks. (115796) Solution: Add performance fixes for large element host writes and R3 cache writes. CX200, CX400, CX600 After power failure cache dumped followed immediately by SPB panic. (113981) CX200, CX400, CX600 Default metaLUN stripe element multiplier defaults to 40 resulting in a stripe depth too large. (106602) CX200, CX400, CX600 NDU issues seen during Customer NDU testing. (107442, 107891, 109695, 110515, 112989, 113786, 114034, 115210, 117903) CX200, CX400, CX600 Storage system bug checks when Cisco name server switch logs into the storage system during name server query. New switch behavior. (108142) CX200, CX400, CX600 Occasionally cannot bind new LUs to an RG after multiple trespasses occur while the RG is expanding. (109828). Fixed in Revision: 02.16.xxx.5.004 Solution: Remove recursion in cache code that caused stack overflow. Fixed in Revision: 02.16.xxx.5.004 Solution: Changed default stripe element multiplier to 4. Fixed in Revision: 02.16.xxx.5.004 Solution: Added fixes and enhancements to the code to make NDU more robust. Fixed in Revision: 02.16.xxx.5.004 Solution: Reject unexpected / illegal login from name server. Fixed in Revision: 02.16.xxx.5.004 Solution: Correctly handle concurrent RG expansion and LU trespasses.

CX200, CX400, CX600 If a user starts a RAID Group Fixed in Revision: 02.16.xxx.5.004 expansion and then unbinds all of the LUNs in the RAID Solution: Check for a valid RG table before modifying it. Group prior to the expansion completing, the RAID Group will become inaccessible. (107799

EMC CX200LC, CX200, CX400, CX600 FLARE Software Release Notes

Fixed Problems

Problem CX200, CX400, CX600 Rebuild panic "RBLD_PEER_OUT_OF_SYNC" (0x0070001C). This panic has been seen in the following dimms - 94610, 94991, 95144, 97938, 104094, 107089, 108786, 115237, 115461, 116497, 117670.

Detail Fixed in Revision: 02.16.xxx.5.004 Solution: Added new and improved rebuild processing support in code base. This enhancement addressed the RBLD_PEER_OUT_OF_SYNC panic seen in multiple dimms. It also made the rebuild code in general more robust and better able to handle abnormal conditions.

CX200, CX400, CX600 On rare occasions, due to heavy Fixed in Revision: 02.07.016 trespass activity for Mirrored LUNs, a Storage Processor Solution: Fixed code to handle buffers in an optimized may encounter a panic (0xE111805F) (117334) fashion. CX200, CX400, CX600 If a drive fails in an ATA enclosure and is faulted by FLARE, sometimes the replacement drive never comes ready for use by FLARE. It stays in the powering up state until the system is reset. (109727) CX200, CX400, CX600 If a drive fails in an ATA enclosure and is faulted by FLARE, sometimes the replacement drive is not recognized as being physically inserted in the enclosure. It is unusable until the system is reset. (114461) CX200, CX400, CX600 On very rare occasions, the Storage Processor may encounter a panic (0xE1118041) when it receives malformed network requests (117801) CX200, CX400, CX600 If one of the Storage Processor panics or reboots for an unrelated reason while a trespass is in progress, the LUN will become inaccessible until the surviving Storage Processor is rebooted (117853) CX200, CX400, CX600 In some cases when the array was previously configured as a NAS backend and then converted to SAN prior to the upgrade, Storage Processor may fail to reboot as a part of the NonDisruptive Upgrade. (115324) Fixed in Revision: 02.07.015 Solution: Upgrade to the latest FLARE code that contains Yukons FRUMON firmware code 1.53 that runs on the Bridge Control Card (BCC) Fixed in Revision: 02.07.015 Solution: Upgrade to the latest FLARE code that contains Yukons FRUMON firmware code 1.53 that runs on the Bridge Control Card (BCC) Fixed in Revision: 02.07.015 Solution: Use the latest version of the code that handles the erroneous network traffic appropriately. Fixed in Revision: 02.07.015 Solution: Fixed bug in Trespass error handling code to handle unexpected peer Storage Processor reboots

Fixed in Revision: 02.07.015 Solution: Enchanced NAS to SAN conversion code to automatically remove NAS specific configuration information.

CX600 On very rare occasions, Storage Processor may Fixed in Revision: 02.07.015 encounter a panic (0x01982013) when one of the chip Solution: Added code to handle the specific error components on the Storage Processor returns condition. erroneous result (115559) CX600 On rare occasions, Storage Processor may encounter a panic (0x05060004) when it runs out of memory. (117043) Fixed in Revision: 02.07.014 Solution: Fixed memory leak in FLARE that lead to the panic

EMC CX200LC, CX200, CX400, CX600 FLARE Software Release Notes

Fixed Problems

Problem CX200, CX400, CX600 Online DAE2-ATA enclosure additions are prohibited if the enclosure being added has down-rev firmware from what is on the storage system. (112512) CX200, CX400, CX600 Online BCC replacements are prohibited if the BCC has down-rev firmware from what is on the array. (112512)

Detail Fixed in Revision: 02.07.015 Solution: Upgrade to the latest FLARE code that contains Yukons FRUMON firmware code 1.53 that runs on the Bridge Control Card (BCC) to remove this restriction for future upgrades. Fixed in Revision: 02.07.015 Solution: Upgrade to the latest FLARE code that contains Yukons FRUMON firmware code 1.53 that runs on the Bridge Control Card (BCC) to remove this restriction for future upgrades. Fixed in Revision: 02.07.015 Solution: Upgrade to the latest FLARE code that contains Yukons FRUMON firmware code 1.53 that runs on the Bridge Control Card (BCC) Fixed in Revision: 02.07.015 Solution: Upgrade to the latest FLARE code that contains Yukons FRUMON firmware code 1.53 that runs on the Bridge Control Card (BCC) Fixed in Revision: 02.07.013 Solution: Improved LUN binding algorithm that takes care of Storage Processor panic during a degraded Bind in a more graceful fashion Fixed in Revision: 02.07.013 Solution: Added special code to handle power glitch events caused by faulty drives on back end. Fixed in Revision: 02.07.011 Solution: Storage-system software will correctly handle the error. Fixed in Revision: 02.07.011 Solution: This problem is very rare and is manifested by the way BCCs respond to certain faults on the backend. FLARE is reacting to the error messages sent by the BCCs. The fix is a two-part fix: Improved error handling by FLARE Uprade to the latest firmware code (Yukons FRUMON code) that handles these situations in a more graceful manner.

CX200, CX400, CX600 After an NDU while the BCC firmware is being updated, the possibility exists that all drives could fault in the target enclosure, or the target enclosure could become unresponsive, or the SP could panic. (116162) CX200, CX400, CX600 Occasionally during periods of heavy I/O, all fault lights on an enclosure are lit and Storage Processor on the B-side loses access to all drives in the enclosure. (117160) CX200, CX400, CX600 On rare occasions, Storage Processor may continuously reboot if it takes a panic while binding a LUN in a degraded RAID Group. (115232) CX200, CX400, CX600 Storage Processor may panic (0x0000000 or 0xE115800C) when a drive with faulty hardware causes power glitch. (116311) CX200, CX400, CX600 Storage Processor may panic (0x0000001e) due to certain unexpected disk drive underrun events. (114139) CX200, CX400, CX600 One or more drives in an ATA enclosure are stuck in Transitioning state. This can happen when one of the Bridge Control Cards (BCC) in an ATA enclosure crashes and reboots, and while it is rebooting the peer BCC card in this enclosure also crashes and reboots. This causes the drive(s) to get stuck in powerup mode on either one of the two backend (BE) buses connecting to this enclosure. (114121, 108858)

EMC CX200LC, CX200, CX400, CX600 FLARE Software Release Notes

Fixed Problems

Problem

Detail

CX200, CX400, CX600 FRU stuck in Transitioning state Fixed in Revision: 02.07.011 after a bad drive is inserted because the lock Solution: The fix involves checking if the peer storage information is erroneously dropped. (114116) processor is waiting for us to release the lock before clearing the lock information. If it is waiting, then send an appropriate response to the peer before clearing the lock information. CX600 A chip errata for one of the components on the Fixed in Revision: 02.07.011 storage processor could result in a processor hang. The Solution: New BIOS microcode to address this HW chip failure has not been observed. (113250) errata CX200, CX400, CX600 If two of drives 0_0_0 through 0_0_2 are faulted and then one is replaced, under rare conditions the storage processor may panic with code 0xE115800C. (114460) Fixed in Revision: 02.07.011 Solution: Fixed race condition in the LUN assignment code.

Fixed in Revision: 02.07.011 CX200, CX400, CX600 LUNs belonging to a doublefaulted RAID Group (RG) are not marked as unowned Solution: Correctly mark LUN(s) as unowned when resulting in poor failover performance. The problem was double-faulted. observed when a storage system serves as a backend for a Celerra/NAS environment. (113903) Fixed in Revision: 02.07.011 CX200, CX400, CX600 Storage Processor may encounter a panic (0x0000000) if the attached host Solution: Modified login validation algorithm to reject sends login-frames containing invalid World Wide Node illegal login frames with appropriate error message. (WWN) name and Class of Service information. (114802) Fixed in Revision: 02.07.010 CX200, CX400, CX600 LUNs may fail to assign (go unowned) after a drive replacement, a hot spare Solution: Correct defect in code that determines the equalize where the hot spare is a different size than the rebuild checkpoint following drive replacement. drive it replaced, and then a trespass to the peer SP. (112437) CX200, CX400, CX600 Installation of some software packages required for conversion operations will fail if running the 02.07.005 (CX200) or the 02.07.007 (CX400, CX600) version of the FLARE Operating Environment. (111885) CX200, CX400, CX600 Storage Processor may encounter a panic (0x00800131) following replacement of all drives in the storage system with previously used drives. (108866) CX200, CX400, CX600 Storage processor may encounter a panic (0x0070001d) if one of the FLARE database drives (0, 1 or 2) fails while the peer storage processor is in a failed or powered down state and the storage system is in the process of rebuilding the peers error log database. (109402) Fixed in Revision: 02.07.006 (CX200); 02.07.008(CX400, CX600) Solution: Fixed NULL pointer in code that installs conversion and recovery software images. Fixed in Revision: 02.07.005 (CX200); 02.07.007 (CX400, CX600) Solution: Remove inappropriate revision check that caused the panic. Fixed in Revision: 02.07.005 (CX200); 02.07.007 (CX400, CX600) Solution: Correctly handle the case where a drive fails while an error log rebuild is in progress.

EMC CX200LC, CX200, CX400, CX600 FLARE Software Release Notes

Fixed Problems

Problem CX200, CX400, CX600 Enhance disk drive error reporting so that errors that were previously reported as 801 Soft SCSI Bus Error with sense key of 09 will now be reported as 803 Recommend Drive Replacement with sense key of 09 to enable filtering the benign 801 errors from the more serious drive replacement cases. (109674) CX200, CX400, CX600 Storage processor may encounter a panic (0x7115800C) if committing new software while drive 0 is removed from the storage system. (Note that it is recommended that all system errors be resolved prior to upgrading and committing new software.) (108575)

Detail Fixed in Revision: 02.07.005 (CX200); 02.07.007 (CX400, CX600) Solution: Disk drive check condition 04 (hardware error) is now reported as Recommend Drive Replacement instead of Soft SCSI Bus Error. Fixed in Revision: 02.07.005 (CX200); 02.07.007 (CX400, CX600) Solution: Query all drives for revision information at commit time instead of just drive 0, in case drive 0 is removed.

CX200, CX400, CX600 Trespass of a metaLUN failed to Fixed in Revision: 02.07.005 (CX200); 02.07.007 (CX400, CX600) trespass one of the component LUNs due to a prior error connecting to the LUN. (110509) Solution: Correctly handle error path when a host fails to connect to a LUN. CX200, CX400, CX600 LUNs fail to assign (unowned) after drive replacement, a hot spare equalize where the hot spare is a different size than the drive it replaced, and then a trespass to the peer SP. This problem only occurs if LUN partition 0 of the RAID Group (RG) has been unbound. All LUNs on the RG will become unowned if any in the RG attempt a trespass.(110437) CX200, CX400, CX600 RAID Group expansion operation may hang following multiple trespass operations. (108856) CX200, CX400, CX600 Storage Processor may encounter a panic (0xe111800b) under certain intermittent network error conditions. Storage system reboots and resumes normal operation. (110277) CX200, CX400, CX600 Storage Processor may encounter a panic (0x019n1001) when it receives a switch name server login while a name server query is in progress. This is illegal switch behavior, but has been observed on one occasion. (108141) CX200, CX400, CX600 Under certain conditions when attempting to establish a new MirrorView connection, or re-establish an existing connection following a Storage Processor reboot, the login to establish the connection fails due to a collision of operations between the peer Storage Processors. Recovery required disabling and re-enabling the connection. (108869) Fixed in Revision: 02.07.005 (CX200); 02.07.007 (CX400, CX600) Solution: Fix defect in the address calculation code in the hot spare swap-out routine.

Fixed in Revision: 02.07.005 (CX200); 02.07.007 (CX400, CX600) Solution: Fixed case where expansion operation is not correctly restarted following trespass. Fixed in Revision: 02.07.005 (CX200); 02.07.007 (CX400, CX600) Solution: Fixed excessive memory usage in certain network error paths. Fixed in Revision: 02.07.005 (CX200); 02.07.007 (CX400, CX600) Solution: Reject the illegal login instead of panicking the storage system. Fixed in Revision: 02.07.005 (CX200); 02.07.007 (CX400, CX600) Solution: Correct defect in the flag management in the Test Unit Ready code path.

EMC CX200LC, CX200, CX400, CX600 FLARE Software Release Notes

Fixed Problems

Problem

Detail

CX200, CX400, CX600 Fibre driver encountered a panic Fixed in Revision: 02.07. 001 (CX200, CX400, CX600) following drive firmware download. Storage processor Solution: Fixed contention issue during disk firmware would have rebooted anyway as a result of the drive download. firmware upgrade. (97865) CX200, CX400, CX600 When powering up pre-zeroed disk drives for the first time (typically a new storage system or new enclosure) the drives may hang in the powering up state. This occurs only on the very first powerup, so if the storage system was pre-configured and powered up at the factory this will not occur at a customer site. For storage systems that are not preconfigured at the factory, for add-on enclosures or for add-on disk drives, please see the recommended workaround. (97503) CX200, CX400, CX600 On rare occasions, disk drives exhibit a failure behavior where they repeatedly go offline and return online on one back-end Fibre Channel bus, by asserting and releasing one of their two port bypass bits. The frequency of the state changes and the fact that only one SP has visibility to the behavior, can result in the two CLARiiON storage processors getting out of sync with respect to their view of the state of this drive. This can lead to the drive getting stuck in the powerup state. (106302) Fixed in Revision: 02.06.013 (CX200, CX400); 02.06.012 (CX600) Solution: Eliminate discarded write operation when both SPs try to concurrently perform a FRU signature write.

Fixed in Revision: 02.06.013 (CX200, CX400); 02.06.012 (CX600) Solution: Improve the peer-to-peer synchronization during the drive powerup process.

CX200, CX400, CX600 RAID Group rebuild and trespass operations collided resulting in SP panics (0xE117B264). (105350) CX200, CX400, CX600 MetaLUN configuration operations (changing Aggregate Volume parameters or LUN nice name expansion rate) while expanding a metaLUN or performing I/O that spans multiple components of the metaLUN can result in SP failure. (106299)

Fixed in Revision: 02.06.013 (CX200, CX400); 02.06.012 (CX600) Solution: Added special RAID Group busy handling for rebuild completion. Fixed in Revision: 02.06.013 (CX200, CX400); 02.06.012 (CX600) Solution: MetaLUN I/O manager needs to check for quiesce for a configuration change operation before generating I/O instead of after.

CX200, CX400, CX600 MetaLUN support fails to initialize a stack correctly, which can result in errors during non-I/O operations such as trespass. This problem has been observed only while testing a future release of the software, but has the potential to fail in the current software. (104717)

Fixed in Revision: 02.06.011 (CX200, CX400); 02.06.010 (CX600) Solution: Correctly initialize the IRP stack.

10

EMC CX200LC, CX200, CX400, CX600 FLARE Software Release Notes

Fixed Problems

Problem CX200, CX400, CX600 Replacing drive 0 on a running storage system can result in an SP panic (0x00800131 or 0x0070001c) due to referencing invalid database information on the replacement drive. (102037) CX200, CX400, CX600 If a metaLUN is assigned a Nice Name that includes any of the following characters (>, <, &, ,) then on a subsequent reboot the metaLUN will become inaccessible and the storage system may become unmanaged. (104268) CX200, CX400, CX600 When a storage system is powered up with drive 0 removed, FLARE may fail to swap in a hot spare if it has not completed its powerup cycle. (104386) CX200, CX400, CX600 If a metaLUN is bound with certain offset values, then the user will be unable to perform an Expansion operation on that metaLUN. (103786) CX200, CX400, CX600 Under certain stressful I/O load conditions, the storage system may not respond to a front-end fibre login command (PLOGI or PRLI) before FLARE times out. This could inhibit the ability of some hosts to log in and communicate with the storage system. (104349) CX200, CX400, CX600 Race condition in metaLUN ownership code can result in an SP panic during metaLUN trespass if one of the component LUNs is double-faulted. (104510)

Detail Fixed in Revision: 02.06.011 (CX200, CX400); 02.06.010 (CX600) Solution: Compare revision information on all database drives to determine whether drive 0 is valid. Fixed in Revision: 02.06.011 (CX200, CX400); 02.06.010 (CX600) Solution: Store special characters as escape sequences for the name parser. Fixed in Revision: 02.06.011 (CX200, CX400); 02.06.010 (CX600) Solution: FLARE will wait for the hot spare to be in the Ready state prior to attempting to swap it in. Fixed in Revision: 02.06.011 (CX200, CX400); 02.06.010 (CX600) Solution: Correct metaLUN expansion code to correctly account for bind offsets. Fixed in Revision: 02.06.011 (CX200, CX400); 02.06.010 (CX600) Solution: Increase the login timeout value.

Fixed in Revision: 02.06.011 (CX200, CX400); 02.06.010 (CX600) Solution: Add additional locking in the metaLUN trespass code path.

CX200, CX400, CX600 The last disk drive on the back- Fixed in Revision: end fibre loop may fail after software upgrade. (102498) 02.06.007 (CX200, CX400); 02.06.006 (CX600) Solution: Correctly initialize a pointer used by the fibre driver. CX200, CX400, CX600 Incorrect handling of an unexpected variation of disk drive under-run errors can result in returning old data on a read operation. The data on the disk is correct. This was encountered during disaster recovery simulation on a test lab storage system that included a number of old drives experiencing these under-run errors. (97773) CX200, CX400, CX600 Storage processor may encounter a panic (0x01964036) when it receives a front-end target reset or abort. (102502) Fixed in Revision: 02.06.007 (CX200, CX400); 02.06.006 (CX600) Solution: Correctly detect and handle this particular error condition.

Fixed in Revision: 02.06.007 (CX200, CX400); 02.06.006 (CX600) Solution: Correct abort handling to avoid corruption of a pointer.

EMC CX200LC, CX200, CX400, CX600 FLARE Software Release Notes

11

Fixed Problems

Problem CX200, CX400, CX600 Storage processor may encounter a panic (0x80000003) when doing misaligned I/O to metaLUNs with SAN Copy and Read Cache enabled. (103141) CX200, CX400, CX600 Hot spare gets stuck in the powerup state when the system experiences back-end loop failures. (103237)

Detail Fixed in Revision: 02.06.007 (CX200, CX400); 02.06.006 (CX600) Solution: Fixed race condition in metaLUN handling code for cases where data is in the Read Cache and responds immediately. Fixed in Revision: 02.06.007 (CX200, CX400); 02.06.006 (CX600) Solution: Improved peer synchronization and error recovery in hot spare handling when one storage processor detects back-end loop failure. Fixed in Revision: 02.06.007 (CX200, CX400); 02.06.006 (CX600) Solution: Fixed an error in the FRU number masking when a hot spare is swapped in.

CX200, CX400, CX600 Storage processor may encounter a panic (0x00300027) when a failed drive is replaced on a 02.06 FLARE array with a drive previously installed in a storage system running 02.04 or earlier, or that has 02.05 installed but not committed. A hot spare must be running in place of the original failed drive at the time of the replacement for this failure to occur. (103054) CX200, CX400, CX600 Due to a resource queuing issue in the Clean/Dirty processing code, if synchronous bursts of I/O are done to very large numbers of LUNs, I/O response time can degrade due to conflicts in marking LUNs clean or dirty. This performance degradation is likely to be seen only if performing this pattern of I/O simultaneously to 500 or more LUNs. (100271) CX200, CX400, CX600 Enclosure 0 Fault LED remains lit after powerup if an SPS is not installed in the storage system. All customer installations require an SPS, so this is just a manufacturing test issue. (100216)

Fixed in Revision: 02.06.006 (CX200, CX400); 02.06.005 (CX600) Solution: Fix a resource queuing issue in the Clean/Dirty processing code.

Fixed in Revision: 02.06.006 (CX200, CX400); 02.06.005 (CX600) Solution: Correctly detect peer powerup complete and turn off the fault LED. Do not wait for SPS test to complete if one isnt installed. Fixed in Revision: 02.06.002 Solution: Prefetch priority altered to prevent any possibility of collision and to ensure that the operations are completed in the correct order.

CX200LC, CX200, CX400, CX600 Under certain rare conditions and only after a previous fault leaving a RAID 3 or RAID 5 LUN degraded, a read operation can collide with a pre-fetch operation resulting in incorrect data. The data is not modified and remains correct on the media. This has been detected only in EMC test labs (98801). CX200LC ,CX200, CX400, CX600 Drive firmware download to drives 0-3 can fail causing the system to become unmanaged (SPs hang and do not reboot). (92624)

Fixed in Revision: 02.06.001 Solution: Do not process discoveries when a download is in progress.

12

EMC CX200LC, CX200, CX400, CX600 FLARE Software Release Notes

Fixed Problems

Problem

Detail

CX200LC, CX200, CX400, CX600 If a rebuilding vault Fixed in Revision: 02.06.001 drive (drives 0-4) is removed there is a very small Solution: Corrected the handling of a canceled rebuild possibility that rebuilds will not start up again when the when in the RB_STARTING state. removed drive has been reinserted. The rebuild complete percentage for LUNs on that drive will be stuck at zero percent complete. Note: On large units, which are servicing heavy I/O, the rebuild complete percentage may not change for up to 10 hours. (90342) CX200, CX400, CX600 An NDU operation may fail occasionally with the following error: Operation Failed: An SP rebooted unexpectedly (0x71518011). (76325) CX600 A cache configuration change will fail with the following error: The requested configuration would create a write cache size larger than the safe area. (0x6000277) while trying to configure more than 2048 Mbytes of write cache with 2 Kbytes cache page size OR trying to configure a 2-Kbyte cache page size when the write cache size is greater than 2048 Mbytes. (91568) Fixed in Revision: 02.06.001 CX200LC, CX200, CX400, CX600 The following message always appears in the Event Log at storage- Solution: Change the ErrorControl value to zero so that system powerup: the OS ignores this error and does not log it. Event Code:0x1b72 > Description: The following bootstart or system-start > driver(s) failed to load: atapi Additionally, if a support engineer uses SymmRemote to access the storage system, the following message appears in a pop-up window: At least one service or driver failed during system startup. Use Event Viewer to examine the event log for details. This behavior is expected at this time. (74321) CX200, CX400, CX600 Storage processor panic occurs when booting a storage system where a large number of LUN components of a metaLUN are inaccessible due to faulted or removed enclosures. (94506) Fixed in Revision: 02.06.001 Solution: Modify metaLUN code to discontinue retrying failed accesses beyond where the SP will experience a time-out and panic. It is also recommended that enclosures including bound LUNs be repaired or reconnected prior to an NDU or voluntary storagesystem reboot. Fixed in Revision: 02.06.001 Solution: Incorporated OS hot fix.

Fixed in Revision: 02.06.001 Solution: Correctly set up the cache bitmaps to allow the user to configure a write cache greater than 2 Gbytes if the cache page size is set to 2 Kbytes.

EMC CX200LC, CX200, CX400, CX600 FLARE Software Release Notes

13

Fixed Problems

Problem

Detail

Fixed in Revision: 02.06.001 CX200, CX400, CX600 Storage processor panic (0x00220013) occurs when removing an enclosure that Solution: Changed the order of shutdown messages to has 256 or more LUNs bound on it. (92961) the peer and the SFE module so that if the peer message causes a pend, the SFE message is not sent. CX200, CX400, CX600 On a heavily loaded system, sniffing appears to stop after vigorous I/O activity, though still reported as enabled. (95239) Fixed in Revision: 02.06.001 Solution: Set the READY_NOTIFICATION flag in the verify code path.

CX400, CX600 Storage processor panic (0x000000d1) Fixed in Revision: 02.06.001 occurs during destroy of an inactive snapshot, when I/O Solution: Changed iterator to store the 'next' pointer was running to the source LUN. (93016) prior to returning the 'current' pointer. This allows the caller to freely delete the current pointer, without affecting the 'nextObject' call. CX200, CX400, CX600 Storage processor panic (0x8288c620) occurs when changing metaLUN expansion rate from ASAP to High. (95798) Fixed in Revision: 02.06.001 Solution: In aggregate expansion manager increase the area that a spin lock is spanning in HALT_EXPANSION handler, such that it spans both the check and set, not just the set. Eliminates a race condition with the thread when checking and switching states. Fixed in Revision: 02.06.001 Solution: Check for any rebuild stops in progress before sending new rebuild requests to RB. Use correct unit number when canceling rebuild requests. Fixed in Revision: 02.06.001 Solution: Updated cm_peer_sys_db_msg when there are simultaneous configuration change requests and on the even controller (request was getting lost).

CX200, CX400, CX600 Storage processor panic (0x00700007) RBLD_UNKNOWN_STATE occurs under certain timing conditions, when trespassing a LUN that includes an equalizing FRU. (87752) CX200, CX400, CX600 Navisphere hangs when repeatedly turning statistics logging on and off on both storage processors. Database updates from the two SPs collide. (89382)

Fixed in Revision: 02.06.001 CX200, CX400, CX600 LCC replacement causes double SP panic (0xe1318014) due to memory not Solution: Panic SPB with unreleased client messages being freed on lost contact by a layered driver. (94121) after contact is lost; rather than a split-brain panic on SP A as it boots. This will prevent a double panic situation. CX200, CX400, CX600 CRU signature errors occur after upgrading from FLARE 02.04 code. (94329) Fixed in Revision: 02.06.001 Solution: Put in fix so that database code will convert to a new layout instead of reconstructing the data directory and zeroing out user database area. Fixed in Revision: 02.06.001 Solution: Only LOGOUT HBAs that are affected by RSCN and no longer exist in the name server after an RSCN. Fixed in Revision: 02.06.001 Solution: Corrected case where the system may not return the correct WWN on a login

CX200, CX400, CX600 Array RSCN/LOGO behavior becomes extremely disruptive in SAN environments. (89551) CX200, CX400, CX600 Connectrix switch logs into CX600 array. (93984)

14

EMC CX200LC, CX200, CX400, CX600 FLARE Software Release Notes

Known Problems and Limitations

Problem CX600 CX600 hung in cache code when powering up following an NDU to 02.05 software. (94758)

Detail Fixed in Revision: 02.06.001 Solution: Fix handling of CA_PEER_FROZEN in SYNCING state if not cache idle.

CX400, CX600 Storage processor panic occurs when Fixed in Revision: 02.06.001 receive CORRUPT_CRC request from a mirror primary Solution: Flush sync queue when cache is going clean. to a mirror secondary at the same time the write cache writes out its last dirty pages. (95997) Fixed in Revision: 02.06.001 CX200LC, CX200, CX400, CX600 The navijarcli.exe program, which is used by spcollect, sometimes hangs Solution: The navijarcli.exe program has been on exit, thus causing spcollect to hang. (94368) replaced by navicimcli.exe, which does not hang. CX200, CX400, CX600 SP will panic if attempting to commit FLARE software on an array configured with less than five drives. (99323) Fixed in Revision: 02.06.001 Solution: Updated code to make sure the Vault LUN is present prior to accessing its properties.

Known Problems and Limitations

This section identifies outstanding issues with this release, and important warnings associated with the connectivity and compatibility of this product. It also provides useful recommendations.

Known Problems Frequency

The frequencies for the known problems listed in this section have the following meanings:
Frequency Every Time Very Frequent Frequent Intermittent Very Intermittent Extremely Intermittent Definition Occurs whenever the specific condition is met. Occurs between 30 and 50 percent of the time when the specific cause is repeated. Occurs between 10 and 30 percent of the time when the specific cause is repeated. Occurs between 1 and 10 percent of the time when the specific cause is repeated. Occurs less than 1 percent of the time when the specific cause is repeated. Failure mechanism may never be seen except under the most stressful QA test environments.

EMC CX200LC, CX200, CX400, CX600 FLARE Software Release Notes

15

Known Problems and Limitations

Description CX200, CX400, CX600 Under certain rare circumstances, the firmware update process that follows the NDU procedure will exhibit one of the following failure modes. These fault modes do not result in loss of access; however, manual corrective action is necessary by your EMC Service Representative. 1. 2. 3. An individual drive will be faulted An enclosure fault will be indicated, and the Navisphere log will show a RESUME prom error One of the BCC controllers will fault, causing loss of access to a DAE2-ATA enclosure on one side only.

Detail Frequency Extremely Intermittent after an NDU if an enclosure/storage system exhibits one of the failure modes listed here. Effect Fault light on an ATA enclosure lights up and/or Error message appears in the Navisphere logs Prevention/Resolution Please contact your EMC Service Representative.

CX200, CX400, CX600 Do not physically remove an ATA drive from the DAE2-ATA enclosure if that drive is actively running I/O.

Frequency Intermittent when an ATA drive that is actively running I/O is removed. Effect This drive or any replacement drive that is inserted in that slot may not successfully power up. Prevention/Resolution Suspend all I/O to the drive before removing it. If the storage system experiences this failure or you must replace the drive under active I/O load then please contact your EMC Service Representative.

CX200, CX400, CX600 During an NDU operation the following message appears in the Event Log: > The file system structure on the disk is corrupt and unusable. Please run the chkdsk utility on the device \Device\Harddisk0\Partition1 with label This is due to an intentionally scheduled run of the chkdsk utility to verify that all files were transferred and installed on the storage system correctly. (83371) CX200, CX400, CX600 Trespass timeouts can occur if you attempt to perform an NDU under I/O load when metaLUNs are configured to include more than 30 LUNs from a single RAID Group. (96958)

Frequency Every time an upgrade or revert occurs Effect Error message appears in the Event Log. Prevention/Resolution The message is expected and should be ignored.

Frequency Intermittent during NDU under load. Effect MetaLUN trespass times out and an SP panic (0xe117b264)
occurs.

Prevention/Resolution Do not configure metaLUNs with over 30 component LUNs from a single RAID Group. MetaLUNs are intended to aggregate LUNs from different RAID Groups.

16

EMC CX200LC, CX200, CX400, CX600 FLARE Software Release Notes

Known Problems and Limitations

Description CX200, CX400, CX600 - When performing one or more LUN migrations in the AIX operating environment with PowerPath 4.2 installed, errors may be logged to the host operating system indicating reservation conflict or device busy on certain commands. These are benign error messages and have no adverse effect on the operation of the AIX host or CLARiiON storage system. A later version of PowerPath 4.x for AIX is expected to eliminate the error messages. (109068) CX200, CX400, CX600 - The storage system will fail to log out initiators when all initiators are removed from the zone the storage system is in leaving just the one storage system port. The removal of initiators is accomplished by either physically removing all initiators at the same time or by rezoning. (118871).

Detail Frequency Intermittent under conditions described. Effect No effect on I/O or other storage-system operation. Prevention/Resolution Run a version of PowerPath for AIX that is later than release 4.2.

Frequency Every time Effect Initiator resources for the removed initiators stay consumed until a rezoning is performed. If the removed initiators are returned they will use the existing resources. Prevention / Resolution Ensure at least one other host or storage-system port is in the same zone.

Limitations
This section lists issues that may affect the configuration or repair of the storage system. CX200LC, CX200, CX400, and CX600 Storage Systems Background Verify (BV) When using Navisphere CLI to start a background verify on an SP that does not own a LUN, the command is accepted, but the log shows a BV started/BV aborted. This happens every time a background verify is started on an SP that does not own a LUN. Non-Disruptive Software Installation (NDU) You should not perform a non-disruptive software installation (NDU) when significant I/O activity is occurring. Note: Software upgrades on the CX200LC will always be disruptive because it is a single SP system. Restrictions during Non-Disruptive Software Installation (NDU) You cannot initiate any bind or expansion operations while an NDU is in progress. The software will reject any attempts to do so.

EMC CX200LC, CX200, CX400, CX600 FLARE Software Release Notes

17

Known Problems and Limitations

Non-Disruptive Software Installation (NDU) and Tru64 UNIX Servers If a Tru64 UNIX server is connected to more than 180 LUNs on a single SP, you should not perform a non-disruptive software installation (NDU) while significant I/O activity is occurring. Software Commits After performing a non-disruptive software update (NDU), you cannot bind or unbind LUNs, or create or destroy RAID Groups until you have committed the new software. Once software is committed, you cannot revert to the previous revision of software. You can revert only before the software is committed. Additionally, you must commit the currently active software before attempting an NDU of a new package. When performing an NDU commit, do not execute other configuration administration commands until the commit is complete. This includes unbinding LUNs, creating/destroying mirrors, adding/removing secondary mirrors, allocating/deallocating the remote mirror write intent log, creating/deleting a snapshot, adding/removing a LUN to/from the snap cache, adding/deleting snap clones, or allocating/deallocating snap clones private LUNs. Additionally, if the commit operation fails to complete for any reason, (such as a power failure), retry the commit operation. Once the commit has been issued, it is not possible to revert the installation. Unbinding LUNs If you try to unbind a LUN while the LUN is performing I/O, the operation fails and the LUN becomes inaccessible. To avoid this situation, make sure all I/O to the LUN has stopped before unbinding it. To correct this situation, stop all I/O and then unbind the LUN. Disk Address Conflicts FLARE software cannot manage disk or enclosure address conflicts on the back-end buses. If you insert disks that do not follow standard FCAL addressing in the storage system, FLARE software may unintentionally shut down disks currently installed in the storage system or exhibit some other type of failure, such as panics or system hangs. This also happens if you add a new DAE2 to a CX-Series storage system that has its enclosure address in conflict with another DAE2 on the same back-end loop. You can recover by removing the disks you just installed and then powering the storage system down and up. To avoid problems, you should double-check all cabling and enclosure address settings 18
EMC CX200LC, CX200, CX400, CX600 FLARE Software Release Notes

Known Problems and Limitations

when you add enclosures or make any changes to their addresses or cabling. (CX200, CX400 only) Always set the enclosure address on the DPE to enclosure address 0 or the storage system will not power up properly. DAE2 Replacement Restrictions You can install only Fibre Channel drives in the DAE2 enclosures with link control cards (LCCs) and only ATA drives in the DAE2-ATA enclosures with FC-to-ATA link control cards. If you install the wrong drive type, the system will not recognize it. If you replace an LCC card with the incorrect type, it will not successfully power up and operate. Although you can mix FC and ATA enclosures within a storage system, once you have installed an enclosure and created RAID Groups, you cannot replace that enclosure with an enclosure set to the same enclosure number but of the other type unless you first destroy all of the RAID Groups. DAE2-ATA Application Limitations The standard DAE2 enclosure (Fibre Channel disks) has better performance than the DAE2-ATA (ATA disks). The DAE2-ATA is targeted for applications where speed is not critical, such as backup storage. Do not use a LUN in the DAE2-ATA as a host OS boot device. NDU on a Busy Windows Server If an NDU operation is performed on an array connected to a Windows host with PowerPath installed and that host is too busy, PowerPath may be unable to trespass all LUNs from one SP to the other during the NDU operation. This would cause application I/O to those LUNs to fail. To avoid this issue, before you start an NDU, from the Windows Task Manager Performance screen, verify that the CPU usage on the host is less than 50%. Reduce host activity if necessary. If CPU usage exceeds 75%, PowerPath will frequently fail to trespass some LUNs. By reducing host CPU usage to 50% or below, sufficient margin exists to ensure that LUNs will be trespassed correctly and the array upgrade will be nondisruptive. LUN Migration 1. The Migration of a component LU which is part of an aggregate LU is not supported in this release. 2. 3. The destination LUN must be a 'public' LUN when it is chosen for migration (this is the normal case). The destination LUN may not be in use by any other layered feature.
EMC CX200LC, CX200, CX400, CX600 FLARE Software Release Notes

19

Known Problems and Limitations

4. 5.

The destination LUN may not be in a user defined Storage Group. Migration and LUN expansion are mutually exclusive operations. An expanding LUN may not be migrated, and a migrating LUN may not be expanded. The source lun can not be a private LUN. If the source LUN is being used by a layered application, it may only be migrated to a LUN of the same size. After a migration completes the data reported in the inquiry command will still reflect the LUN's original RAID type. The new RAID type is visible through the Navisphere interface. This behavior is as designed and required to maintain compatibility with some operating systems. The maximum number of migrations that can be executing at one time is 4.

6. 7. 8.

9.

New Maximum Settings For Read / Write Cache Size With this release the maximum memory available for cache has decreased on the CX200 and CX400 platforms. The CX600 platform has not changed. This change is the result of reallocation of some memory in support of new features for this release. Before an NDU if the total size of read and write cache per SP is greater than the value listed below then after the NDU the original settings will not be restored. This will result in read and write cache being disabled. The cache will stay disabled until the values are adjusted to be within the new limits. CX200 CX400 236 Mbytes 612 Mbytes

This condition will be noted in the Navisphere Event Log with the following entry: Failed to restore cache settings. Original Cache settings cannot be restored, Memory available for cache is less than the memory required by original cache settings.

20

EMC CX200LC, CX200, CX400, CX600 FLARE Software Release Notes

Technical Notes

Technical Notes
This section includes important information that does not appear anywhere else.

CX200LC, CX200, CX400, and CX600 Storage Systems

NDU This upgrade should not be installed on a system that is in any way faulted. This upgrade will not fix a system that is already exhibiting problems. SP Startup EMC recommends that you reboot an SP only during periods of light I/O activity.
Disk Firmware Downloads

When downloading new disk firmware (a Customer Service procedure only), you must do the following before starting the download operation: 1. 2. Disable the storage-system write cache. Pause all I/O requests to the storage system.

You must download disk firmware to the disks in the following order: 1. 2. 3. Download disk firmware to disk 0_2 and 0_3. Download disk firmware to disks 0_0 and 0_1 Download disk firmware to all the other disks in the storage system.
The storage system reboots after each download.

Note: Current Seagate drive firmware does not come back online following the download of firmware to other drives and the subsequent reboot of drive 0. If this happens, remove drive 0 and reinsert it into the storage system.

EMC CX200LC, CX200, CX400, CX600 FLARE Software Release Notes

21

Technical Notes

CAUTION If only one SP is running when you download disk firmware, do not start the second SP until the download completes. DAE2 Firmware Download FLARE software packages include DAE2 LCC controller FRUMON code. Following an NDU, new FRUMON code will automatically install on each enclosure in the storage system. This process takes approximately 10 minutes per enclosure. DAE2-ATA enclosures that do not have any drives inserted will not upgrade. If drives are later inserted, the enclosure must be power-cycled, or the enclosure LCC card disconnected and reconnected in order for the enclosure FRUMON to complete its upgrade. Note that FRUMON upgrade on diskless enclosures is supported with this revision of software, so upgrades from this release to a future release of software will not have the restriction detailed above. Soft Logical Sector Data Errors A soft logical sector data error indicates that the data redundancy information for a sector stored on a redundant LUN is not valid. These errors occur because a power failure or FRU failure interrupted a write in progress. FLARE software fully recovers from these errors, and reports them to the Event Log only for informational purposes. When the storage system returns to a fully functional state, the sniff-verify utility finds all redundant data inconsistencies and takes the necessary steps to correct them. A write to a sector with inconsistent redundant information also corrects the inconsistency. These errors are normal in the event of a power failure. Event Log Entries Appear Out of Order FLARE software may not always enter items into the Event Log in the order that they occurred. This happens only when several events occur at approximately the same time. Time stamps are correct. Power Failing with LUNs Bound Across DPE/DAE2s LUNs bound across enclosures in a storage system may be marked for rebuild on a power failure because the power to a DPE connected to an SPS stays on until the cache dump is complete. EMC recommends that you do not bind LUNs across enclosures that include a DPE connected to an SPS.

22

EMC CX200LC, CX200, CX400, CX600 FLARE Software Release Notes

Technical Notes

Hot Spare Ownership Once a hot spare is assigned to a degraded LUN, that LUN owns it until either the LUN is repaired and the equalize completes or the LUN is unbound. If the LUN is accidentally double-faulted because you removed the wrong disk during repair, then re-inserting the incorrectly removed disk should cause the LUN to return to its original state (including continued operation with the hot spare engaged). DAE2-ATA Drive Ownership and Activity LED Behavior In the DAE2-ATA enclosure, the two FC-to-ATA link controller cards (LCCs) share ownership of the drives based on I/O load. If one FC-toATA LCC is removed from the enclosure, the remaining LCC will take and hold ownership of all of the enclosure drives. When this occurs, the drive activity lights will steadily blink at a rapid rate. The activity light behavior will return to normal when the missing LCC card is replaced. Disk Insertion and Removal When inserting or removing more than one disk from a storage system, you must pause between each removal or insertion to allow the storage system to recover. Before inserting or removing the next disk module you should make sure that A newly inserted disk's amber light is off and its green light has returned to a normal state: on or blinking due to I/O in progress. On a disk removal, the green lights for the other disks return to a normal state: on or blinking due to I/O in progress. The storage system appears to have resumed normal operation.

Database Disk Replacement You should replace a disk in slots 0_0, 0_1, or 0_2 of DPE enclosure 0 only when the storage system is fully operational. The disks in these slots are FLARE software database disks. Each database disk contains an image of the storage-system configuration and current operating status. FLARE software ensures that the newly inserted disk has the correct database information copied to it when it is installed while the storage system is running. If you insert a disk into one of these slots when the storage system is powered off, the correct FLARE software database information is not written to the replaced database disk. This can result in storage-system configuration problems when the storage system is powered up or if another database disk fails. If you install a FLARE software database disk and you find that existing LUNs are not enabled or caching cannot be enabled or disabled, contact your EMC customer service representative.
EMC CX200LC, CX200, CX400, CX600 FLARE Software Release Notes

23

Technical Notes

Software Image Disk Replacement The FLARE software image is stored on disks 0_0, 0_1, 0_2 and 0_3. Disks 0_0 and 0_2 form a mirror with SP A's software, and disks 0_1 and 0_3 form a mirror with SP B's software. You should never remove and/or replace both disks in one of the mirrors at the same time. If you do, no software will exist to support that SP, and it will become nonfunctional. Extended Inquiry Info Extended Inquiry information is not available when running with DMP failover mode in a Fibre Open initiator type.

CX200LC, CX200, and CX400 Storage Systems

SP Will Not Power Up When DPE Power Supply Module Is Unplugged If a DPE power supply module is unplugged when you power up the storage system, it does not come up until you plug the power supply module back in.

CX600 Storage Systems

SPE LCC Failure Management FLARE software is designed to panic with a 0x00800094 code if it is not able to access any disks on its back-end loop. This ensures the integrity of user data when an SP loses access to its vault and FLARE software database disks and initiates a trespass of this SP's LUNs to the peer SP. This panic is a very unlikely event and typically only an SPE LCC hardware failure causes it. Following the panic, the SP attempts to reboot several times, and fails to completely initialize as long as this hardware failure is present. In this situation, the SP remains in a shutdown state. After the LCC is repaired, you need to power-cycle the storage system or remove the SP that panicked and re-insert it (effectively power-cycling the SP) to allow the SP to reboot and return to an operational state. SP Will Not Power Up When SPE Fan Module Is Unplugged If the SPE fans are unplugged when you power up the storage system, it does not come up until you plug the fans back in.

24

EMC CX200LC, CX200, CX400, CX600 FLARE Software Release Notes

Documentation

Documentation
The following table lists the applicable documents for this product release. These documents ship with Navisphere Manager.
Part Number 069001125 Publication EMC Navisphere Manager Administrator's Guide

Installation
FLARE software is installed on the storage system at the factory . The 02.16 release supports a new packaging model where the entire FLARE Operating Environment is pre-installed in the factory or available in the upgrade bundle. Optional software components are enabled by purchasing and installing the appropriate enabler package. Please refer to the FLARE Operating Environment Release Notes (P/N 300-001-793) for additional details. This section describes the following: Installation restrictions Installation procedures

Please refer back to the Software Commits section for additional information relevant to software upgrades.

Installation Restrictions
This section describes installation restrictions for the various storage-system types. Note: Hosts running the Microsoft Windows 2000 operating system could be susceptible to data loss during a LUN expansion operation unless Windows 2000 Service Pack 4 is installed. For this reason, it is strongly recommended that all Windows 2000 host servers be upgraded with Windows 2000 Service Pack 4 before this FLARE software is installed. For additional details on the Windows 2000 issue, see EMC Solution ID emc73538 and Microsoft Knowledge Base Article 327020.

EMC CX200LC, CX200, CX400, CX600 FLARE Software Release Notes

25

Installation

Installation Restrictions You cannot install Access Logix software on a CX200LC. You cannot install the ThirtyDriveOption enabler on a CX200LC. The CX200LC is restricted to 15 drives. If you have the 01.01.01 ThirtyDriveOption enabler installed on a CX200 running 02.04 FLARE, when you upgrade to the 02.16 software you must install the 01.02.01 ThirtyDriveOption enabler in the same NDU. If you are running 02.05 or earlier FLARE code and Access Logix software is installed on your array, when you upgrade to the 02.16 software you must install the Access Logix Enabler package in the same NDU as the 02.16 FLARE code. Once the Access Logix Enabler package is installed on your array, subsequent upgrades of FLARE software will not disable the Access Logix capability. Access Logix remains enabled on the array. When installing a new version of FLARE software, you must not remove an SP or reboot the storage system while the software installation is in progress. Doing so may leave the storage system in a transient state from which it cannot be restarted. Please wait for the entire installation process to complete and automatically reboot. You cannot enable SnapView, MirrorView,or SAN Copy software on storage systems with only FLARE software, because SnapView, MirrorView, and SAN Copy require Access Logix software. You cannot enable SnapView, MirrorView, or SAN Copy software on a CX200LC or CX200 storage system. DAE2-ATA enclosures must have at least one disk drive inserted in order to upgrade the enclosure FRUMON code. This restriction is removed if you are running 02.07.016 FLARE or higher.

CX200LC

CX200

CX400

CX600

26

EMC CX200LC, CX200, CX400, CX600 FLARE Software Release Notes

Installation

Installation Procedure
For storage systems where EMC does not support using the Wizard, only a service provider should perform the installation procedure. Refer to the Navisphere Manager Release notes, P/N 300-001-808, for a list of supported storage systems. EMC recommends limiting software installation (non-disruptive upgrade) to periods of light I/O activity. To install FLARE software, follow these steps: 1. 2. 3. 4. 5. 6. 7. 8. 9. Verify there are no faults on the array before you begin. If there are faults, repair them before continuing with the upgrade or commit. Locate the packages you will load. Pick a time of lighter I/O load. Pre-bind any new LUNs you may want later if a commit will be delayed for any reason. Consult the appropriate documentation for other recommendations. Use the Wizard where appropriate. Monitor progress. Evaluate the results of the installation. Commit the software when ready. (Note: If drive 0 has been removed or faulted since the software has been installed, do not proceed with the commit. Contact your service provider to repair drive 0 prior to software commit.)

Installation Procedures Use the Software Installation Wizard found in Navisphere Manager. For more information on the Wizard, refer to Managers online help or Chapter 5 in the EMC Navisphere Manager Administrators Guide (P/N 069001125). For further information on software installations and upgrades, refer to the EMC CLARiiON Software Installation Guide (P/N 300001-504). This manual may be found on the EMC PowerLink web site. Only a service provider should perform the installation procedure.

CX200LC

CX200

CX400

CX600

EMC CX200LC, CX200, CX400, CX600 FLARE Software Release Notes

27

Troubleshooting and Getting Help

Troubleshooting and Getting Help

This section provides specific instructions for contacting EMC Customer Support and obtaining additional information about EMC products. Where to Get Help For questions about technical support and service, contact your service provider. If you have a valid EMC service contract, contact EMC Customer Service at: United States: (800) 782-4362 (SVC-4EMC) Canada: Worldwide: (800) 543-4782 (543-4SVC) (508) 497-7901

Follow the voice menu prompts to open a service call, then select CLARiiON Product Support. Sales and Customer Service Contacts For the list of EMC sales locations, please access the EMC home page at: http://www.emc.com/contact/ For additional information on the EMC products and services available to customers and partners, refer to the EMC Powerlink website at: http://powerlink.emc.com For CLARiiON documentation, after you log in to Powerlink, select Support > Document Library.

28

EMC CX200LC, CX200, CX400, CX600 FLARE Software Release Notes

Copyright and License Information

Copyright and License Information

Copyright 2005 EMC Corporation. All Rights Reserved. EMC believes the information in this publication is accurate as of its publication date. However, 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, CLARiiON, Navisphere, and PowerPath are registered trademarks and Access Logix, FLARE, MirrorView, Powerlink, SAN Copy, and SnapView are trademarks of EMC Corporation. All other trademarks used herein are the property of their respective owners.

Info-ZIP Copyright
This is version 2002-Feb-16 of the Info-ZIP copyright and license. The definitive version of this document should be available at ftp://ftp.info-zip.org/pub/infozip/license.html indefinitely. Copyright (c) 1990-2002 Info-ZIP. All rights reserved. For the purposes of this copyright and license, "Info-ZIP" is defined as the following set of individuals: Mark Adler, John Bush, Karl Davis, Harald Denker, Jean-Michel Dubois, Jean-loup Gailly, Hunter Goatley, Ian Gorman, Chris Herborth, Dirk Haase, Greg Hartwig, Robert Heath, Jonathan Hudson, Paul Kienitz, David Kirschbaum, Johnny Lee, Onno van der Linden, Igor Mandrichenko, Steve P. Miller, Sergio Monesi, Keith Owens, George Petrov, Greg Roelofs, Kai Uwe Rommel, Steve Salisbury, Dave Smith, Christian Spieler, Antoine Verheijen, Paul von Behren, Rich Wales, Mike White This software is provided "as is," without warranty of any kind, express or implied. In no event shall Info-ZIP or its contributors be held liable for any direct, indirect, incidental, special or consequential damages arising out of the use of or inability to use this software. Permission is granted to anyone to use this software for any purpose, including commercial applications, and to alter it and redistribute it freely, subject to the following restrictions: Redistributions of source code must retain the above copyright notice, definition, disclaimer, and this list ocnditions. Redistributions in binary form (compiled executables) must reproduce the above copyright notice, definition, disclaimer, and this list of conditions in documentation and/or other materials provided with the distribution. The sole exception to this condition is redistribution of a standard UnZipSFX binary as part of a self-extracting archive; that is permitted without inclusion of this license, as long as the normal UnZipSFX banner has not been removed from the binary or disabled. Altered versions--including, but not limited to, ports to new operating systems, existing ports with new graphical interfaces, and dynamic, shared, or static library versions--must be plainly marked as such and must not be misrepresented as being the original source. Such altered versions also must not be misrepresented as being Info-ZIP releases--including, but not limited to, labeling of the altered versions with the names "Info-ZIP" (or any variation thereof, including, but not limited to, different capitalizations), "Pocket UnZip," "WiZ" or "MacZip" without the explicit permission of Info-ZIP. Such altered versions are further prohibited from misrepresentative use of the Zip-Bugs or Info-ZIP e-mail addresses or of the Info-ZIP URL(s). Info-ZIP retains the right to use the names "Info-ZIP," "Zip," "UnZip," "UnZipSFX," "WiZ," "Pocket UnZip," "Pocket Zip," and "MacZip" for its own source and binary releases.

EMC CX200LC, CX200, CX400, CX600 FLARE Software Release Notes

29

Expat Copyright
Copyright (c) 1998, 1999, 2000 Thai Open Source Software Center Ltd Permission is hereby granted, free of charge, to any person obtaining a copy of this Expat software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. EMC is using a modified version of the above software in CX -Series FLARE versions 02.05.x.xx.x.xxx and higher. In accordance with the above license the EMC modified Expat source is available to users of this Expat software. The Expat source may be found here: http://www.emc.com/ClariionOpenSource/

30

EMC CX200LC, CX200, CX400, CX600 FLARE Software Release Notes