R E L E A S E

N OT E S

EMC CX200LC, CX200, CX400, CX600 FLARE

Version 02.04.0.x0.5.002

Release Notes
P/N 085090686 REV A01 February 24, 2003

These release notes contain supplemental information about EMC CX200LC, CX200, CX400, and CX600 FLARE software (previously called Base Software). The software versions are: 02.04.0.20.5.002 (CX200LC, CX200), 02.04.0.40.5.002 (CX400) and 02.04.0.60.5.002 (CX600). Topics include Product Description................................................................................... 2 New Features and Changes...................................................................... 2 Environment and System Requirements ................................................ 3 Fixed Problems ........................................................................................... 4 Known Problems and Limitations........................................................... 7 Technical Notes ........................................................................................ 13 Documentation ......................................................................................... 16 Installation ................................................................................................ 17 Troubleshooting and Getting Help........................................................ 19

Product Description

Product Description
FLARE software controls the operation of 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 a mirror copy of the software for SP A, and disks 0_1 and 0_3 store a mirror copy of the software for SP B. When you power up the storage system, each SP boots and executes FLARE software. FLARE software manages all functions of the storage system. FLARE software supports only the following configurations: a single host dual-host split-bus two clustered hosts

New Features and Changes

The following new features are supported in this release of the product: Support added for the CX200LC model RAID Groups larger than 2 Tbytes may be configured Support added for the DAE2-ATA enclosure for the CX400, CX600 The read cache has been optimized to decrease the time required to fail over and trespass LUNs The CX200LC is a low cost, single storage processor model of the CX200 disk-array storage system. It supports a minimum configuration of drives 0_0 through 0_2 and does not support mirrored write caching. This version of software removes the RAID Group size restriction of 2 Tbytes to allow users to take advantage of the new larger capacity disk drives. Each individual LUN partition within the RAID Group is still restricted to a maximum of 2 Tbytes. This version of software introduces support for the 2-Gigabit Disk-Array Enclosure ATA model (DAE2-ATA). Each enclosure contains 15 ATA drives; these enclosures can be intermixed with existing DAE2 Fibre Channel enclosures. The DAE2-ATA may be configured in any enclosure position except Bus 0 Enclosure 0, which contains the FLARE software and cache vault. RAID Groups must reside entirely either on ATA enclosures or fibre enclosures; you cannot mix them in a configuration. Similarly you can swap hot spares only into like-style LUNs.

EMC CX200LC, CX200, CX400, CX600 FLARE Version 02.04.0.x0.5.002 Release Notes

Environment and System Requirements

This release is available electronically only. It is posted in the Software Download areas of the EMC/CLARiiON Partners page and the Global Services Web page.

Environment and System Requirements

This section identifies the minimum requirements necessary for the proper operation of FLARE with the CX200, CX200LC, CX400 and CX600 storage systems.
Storage-System Type CX200LC Minimum Hardware Requirements 3 disks minimum, installed in slots 0 through 2 of enclosure 0 1 SP (A) 1 Power supply 1 Blower module Minimum Software Requirements EMC ControlCenter Navisphere SP Agent version 6.4 and Navisphere Management Server Base version 6.4. Supported 2-Gbyte Fibre Channel Disks 146-Gbyte low profile 10K rpm 73-Gbyte low profile 10K rpm 36-Gbyte low profile 10K rpm 36-Gbyte low profile 15K rpm

CX200

Minimum of 4 disks installed in slots 0 through 3 of enclosure 0 For write caching 5 disks minimum, installed in slots 0 through 4 of enclosure 0 2 SPs 2 power supplies 1 standby power supply (SPS)

EMC ControlCenter Navisphere SP Agent version 6.4 and Navisphere Management Server Base version 6.4.

146-Gbyte low profile 10K rpm 73-Gbyte low profile 10K rpm 36-Gbyte low profile 10K rpm 36-Gbyte low profile 15K rpm

EMC CX200LC, CX200, CX400, CX600 FLARE Version 02.04.0.x0.5.002 Release Notes

Fixed Problems

StorageSystem Type CX400, CX600

Minimum Hardware Requirements Minimum of 5 disks installed in slots 0 through 4 of enclosure 0 on loop 0 For write caching 2 SPs 2 power supplies 1 standby power supply (SPS)

Minimum Software Requirements EMC ControlCenter Navisphere SP Agent version 6.4 and Navisphere Management Server version 6.4.

Supported 2-Gbyte Fibre Channel Disks 146-Gbyte low profile 10K rpm 73-Gbyte low profile 10K rpm 36-Gbyte low profile 10K rpm 36-Gbyte low profile 15K rpm

Supported ATA Disks 250-Gbyte low profile ATA 5400 rpm

Fixed Problems
This section identifies issues fixed with this release or recent previous releases. Since this is the first release of the CX200LC, there are no fixed problems.

Problem

Detail

CX200, CX400, CX600 If a hot spare is physically larger Fixed in Revision: 02.04.0.x0.5.002 than the failed drive it is replacing, the size of the hot spare Solution: Update FRU table with swapped FRUs capacity will be reported as the size of the failed drive from the time during the completion of a swap. the failed drive is replaced until the hot spare is swapped out. [80816] CX600 Occasional problems with reverting to a previous Fixed in Revision: 02.04.0.60.5.002 version of software using the NDU Revert procedure if the Solution: This was a very intermittent problem in early storage system is experiencing high I/O load at the time of revisions of the software and can no longer be reproduced. the NDU. You will see the following error: Operation Failed : The primary SP did not return after an upgrade (0x71518009) [73361] CX600 Apparent long Agent response times in DMP environment when a peer SP is rebooting. [79194] CX600 Command execution times for DMP's vxdctl on CX600 do not recover fully after letting I/O quiesce. [79203] Fixed in Revision: 02.04.0.60.5.002 Solution: Redesigned the Read cache lrus to improve performance. Fixed in Revision: 02.04.0.60.5.002 Solution: Redesigned the Read cache lrus to improve performance.

EMC CX200LC, CX200, CX400, CX600 FLARE Version 02.04.0.x0.5.002 Release Notes

Fixed Problems

Problem CX200, CX400, CX600 SPS self-test is lighting the enclosure Fault LED and generating event code 2580 (Storage Array is Faulted) that many customers look for when checking status of the array. [79259] CX600 Cache occasionally disabling after SPS test. When the SPS is being tested, the power supply fault (AC_FAIL) is expected and ignored. When the SPS transitions from Testing to Recharging, the SP will sometimes detect a power supply fault (AC_FAIL) after the SPS testing was over and disable the cache. [82424, 82661]

Detail Fixed in Revision: 02.04.0.x0.5.002 Solution: Do not light the fault LED or log this event code if the power failure was due to a scheduled SPS test and there is a second SPS installed. Fixed in Revision: 02.04.0.60.5.002 Solution: This was caused by a race condition between the code that processes the Power Supply status and the code that communicates with the SPSs. A fix was put in to synchronize the two pieces of code.

CX200, CX400, CX600 Array suffers from TCP/IP seq. no. Fixed in Revision: 02.04.0.x0.5.002 predictability issue. [80560] Solution: Add Microsoft Hotfix Q243835 to the Base package to reduce the predictability of TCP/IP initial sequence numbers. CX200, CX400, CX600 Excessive Verify Aborted messages in the Event Log. [79246] CX200, CX400, CX600 Excessive Verify Started messages in the Event Log. [79247] Fixed in Revision: 02.04.0.x0.5.002 Solution: Log only one message per unit instead of one per FRU. Fixed in Revision: 02.04.0.x0.5.002 Solution: Log only one message per unit instead of one per FRU.

Fixed in Revision: 02.04.0.x0.5.002 CX200, CX400, CX600 Hot spare equalize not progressing due to equalize checkpoints being overwritten Solution: Added RAID Group locking of hot spare during during LUN assignment on trespasses. [83322] swaps and improved assigns for dual assignable units. CX200, CX400, CX600 Multiple Background Verifies are running in the RAID driver at the same time. [79218] CX600 Storage processor failed with a HEMI_CPU1_WATCHDOG panic (0x00000041) when a LUN owning virtually all of the cache pages in a 2-Gbyte cache is trespassed to the peer SP. [83381, 83540] CX200, CX400, CX600 The following error message was logged: Could not format SP Busy performance statistics. [83273] CX200, CX400, CX600 If Navisphere has a view of the storage system that is not current and attempts to delete more LUNs than are currently in a Storage Group, the following error will appear in the log: Exception: Caught unexpected exception creating instance K10NDUAdmin.. [ 83402] Fixed in Revision: 02.04.0.x0.5.002 Solution: Fixed multiple issues in the starting and aborting of background verifies. Fixed in Revision: 02.04.0.60.5.002 Solution: Corrected errors in flush code that could result in the code being stuck in a search loop for a time that exceeds the timeout value. Fixed in Revision: 02.04.0.x0.5.002 Solution: Change to eliminate logging of NT Pdh (MS performance reporting) library errors. Fixed in Revision: 02.04.0.x0.5.002 Solution Requests to delete more LUNs than are configured in the Storage Group are now rejected regardless of the Navisphere view of the storage system.

EMC CX200LC, CX200, CX400, CX600 FLARE Version 02.04.0.x0.5.002 Release Notes

Fixed Problems

Problem CX200, CX400, CX600 If a hardware fault causes one SP to reboot regularly and at high frequency, occasionally this can cause the peer SP to fail if caching was enabled. This is caused by an internal invalid state transition brought about by restarting frozen I/O on a functionally normal SP too soon. The code path did not take into account an SP rebooting then dying again during a specific synchronization point in its restart process. I/O is briefly frozen on the surviving SP while coordinating the startup of the peer SP after it failed. [79573] CX400, CX600 An HP/UX host is unable to access more than 128 logical units in the subsystem. [82008]

Detail Fixed in Revision: 02.04.0.x0.5.002 Solution: Finish properly handling the second failure of the rebooting SP before restarting I/O stopped due to the first peer failure.

Fixed in Revision: 02.02.0.x0.5.007 Solution: Corrected logical unit identifier reporting in the Report LUNs SCSI command for HP initiators.

Fixed in Revision: 02.02.0.x0.5.007 CX400, CX600 Possibility of ID value changing on Sun Clusters 3.0 and Solaris 8 and 9 Volume Manager after Solution: Made ID value persistent across NDUs. an NDU to FLARE software 02.02.0.x0.5.006. Changing ID results in volumes not being accessible. CX400, CX600 Possibility of ID value changing on Sun Clusters 3.0 and Solaris 8 and 9 Volume Manager. Changing ID results in volumes not being accessible. [80848] CX400, CX600 Cache disabling under heavy I/O during SPS testing. [81244] Fixed in Revision: 02.02.0.x0.5.006 Solution: Corrected ID initialization.

Fixed in Revision: 02.02.0.x0.5.006 Solution: Added a settle count to allow longer time window to verify that the SPS test has ended.

CX600 Under some circumstances, Event Log messages Fixed in Revision: 02.02.0.60.5.003 that would be logged very early in the powerup process (such as CRUs becoming enabled) are left out of the log because they occur prior to the log being up and active. All events are internally traced in case they are needed to diagnose a powerup failure, but they will not appear in the customer Event Log. A future release of the software will address this issue. [75576] Fixed in Revision: 02.02.0.60.5.003 CX600 Group reservation on a LUN that has persistent registration with APTPL=1 set is not cleared on power loss or dual SP reboot. This situation occurs only if the storage system loses power or reboots while the host remains operational. [76233] CX600 A failure to successfully perform an NDU operation Fixed in Revision: 02.02.0.60.5.003 can result in three versions of the software package existing on the storage system. This condition prevents revert operations until the next NDU is performed, or the extra copy is manually removed. [75391] CX600 A hang or panic on an SP can very infrequently leave the SP unable to locate the proper drivers. [76080] Fixed in Revision: 02.02.0.60.5.003

EMC CX200LC, CX200, CX400, CX600 FLARE Version 02.04.0.x0.5.002 Release Notes

Known Problems and Limitations

Problem CX600 SP Agent not running after an NDU of layered drivers. [76298] CX600 With newer revisions of the CX600 Storage Processor (SP) heavy I/O load can result in starvation of resources to service certain I/O read requests. [78099]

Detail Fixed in Revision: 02.02.0.60.5.003 Fixed in Revision: 02.01.0.60.5.009 Solution: The 3.02 version of BIOS that is included in the 02.01.1.60.5.009 Access Logix software package modifies the setting of one of the programmable hardware bits to correctly prioritize requests. No changes were made to the Access Logix software. Fixed in Revision: 02.01.0.60.5.009 Solution: The 2.15 version of Extended POST code that is included in the 02.01.1.60.5.009 Access Logix software package has been updated to recognize the new part number and allow the new SP to be used as a field spare. No changes were made to the Access Logix software. Fixed in Revision: 02.01.0.60.5.008 Solution: This patch removes the drive from operation as soon as the drive reports Predictive Failure, instead of letting it continue operation in a degraded fashion.

CX600 A new version of the CX600 Storage Processor(SP) is planned for future release. This SP will have a new part number that the current revision of the Extended POST code will not recognize as a compatible field spare replacement board. [78102] CX600 When a drive fails such that it generates extremely frequent sector remap operations, it may slow down its I/O response time so much that the Storage Processor (SP) times out waiting for a response. When a drive fails in this way, it detects the frequency of remaps and reports a PFA (predictive failure analysis) error, which is logged in the customer Event Log. Although such failures are extremely intermittent, they may result in excessive SP failovers if the SP times out during the remap operations. Currently, a customer must replace the drive to fix this problem. [77100]

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.

EMC CX200LC, CX200, CX400, CX600 FLARE Version 02.04.0.x0.5.002 Release Notes

Known Problems and Limitations

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.

Description CX200, CX400, CX600 An NDU operation may fail occasionally with the following error: Operation Failed: An SP rebooted unexpectedly (0x71518011). [76325]

Detail Frequency Very Intermittent when an NDU is performed. Effect The software installation will fail. Prevention/Resolution Reduce the I/O load to the storage system and repeat the NDU. This is due to an operating system issue and will be resolved in a future release.

CX200LC, CX200, CX400, CX600 The following message always appears in the Event Log at storagesystem powerup: 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]

Frequency Every time Effect Error message appears in the Event Log or on the screen. Prevention/Resolution The message is benign and should be ignored.

EMC CX200LC, CX200, CX400, CX600 FLARE Version 02.04.0.x0.5.002 Release Notes

Known Problems and Limitations

Description

Detail

CX200, CX400, CX600 An NDU operation should not Frequency Very Intermittent be performed while an expansion is being performed on Effect a LUN. [78740] An NDU operation may fail if it is performed while a LUN is being expanded. Prevention/Resolution Do not start an NDU operation while an expansion of a LUN is being performed. CX400, CX600 If the back-end fibre cables are swapped between loop 0 and loop 1 on a running storage system, behavior could be unpredictable for several seconds before the storage system panics intentionally. Exact behavior is based on the I/O traffic in progress. Swapping these cables is a very destructive action because you are disconnecting your software database disks from the storage system and connecting them to an auxiliary connection. [76311] Frequency Every Time back-end cables are swapped while running. Effect Storage system panics and ability to recover could be compromised. Prevention/Resolution Never swap back-end bus cables on a running system. If you accidentally remove your back-end cables from a running storage system, please be sure you reconnect them to their original positions.

CX200LC, CX200, CX400, CX600 If the read cache Frequency Very Intermittent when prefetch parameters are prefetch parameters are set to the value zero while a being set to 0 while caching. large prefetch is in progress then the storage processor Effect could fail with the code (0x01e00053). [84077] One Storage Processor panics and restarts automatically. Prevention/Resolution If you wish to stop read cache prefetching, you should disable the feature rather than set the parameters to zero. This will be fixed in a future release of the software. CX200LC, CX200, CX400, CX600 Occasionally if a drive is removed and replaced in a RAID Group where a LUN is binding, and then a subsequent drive in the RAID Group fails before all of the LUNs have been rebuilt, the Storage Processor can fail with code (0x02008023). [83412] Frequency Intermittent under specified conditions Effect One Storage Processor panics and restarts automatically. Prevention/Resolution To avoid this problem, do not remove or insert any drives in a RAID Group that is currently binding LUNs. Either wait for the bind operation to complete or cancel the bind by issuing an Unbind command to the LUN. This will be fixed in a future release of the software.

EMC CX200LC, CX200, CX400, CX600 FLARE Version 02.04.0.x0.5.002 Release Notes

Known Problems and Limitations

Description CX200LC, CX200, CX400, CX600 If a RAID Group experiences a double fault while it is in the middle of an expansion operation, it may result in a state that cannot be recovered without intervention. This situation occurs when a RAID Group expansion is zeroing the expansion disks and two of the original data drives are removed; as a result, the LUN enters a shutdown state. If the drives are reinserted so that the LUN transitions back to the degraded state and the second insertion is coincident with the completion of the expansion zeroing process, then contention for a lock within the FLARE operating system can exist. Note that for the LUN to recover from shutdown to disabled, the original data drive must have been reinserted. [83851] CX200LC, CX200, CX400, CX600 In some circumstances when binding a LUN using the block count option, the LUN capacity Navisphere reports does not exactly match the LUN capacity allocated. This is due to a rounding error in the code. [84083]

Detail Frequency Extremely Intermittent under specified conditions Effect The RAID Group can no longer be assigned to a storage processor. Prevention/Resolution Do not insert drives into a LUN that is expanding. If you encounter this failure scenario please contact your service provider for the appropriate steps to recover this RAID Group.

Frequency Every Time if the requested block count is greater than a multiple of the LUN stripe size by a number of blocks less than the number of data drives in the LUN. Effect The reported capacity of the LUN will exceed the actual capacity of the LUN. Prevention/Resolution To avoid this problem, either bind LUNs using the MB or GB option for sizing, or if using the block count, make sure that the count is a multiple of the stripe size. This will be corrected in a future release of the software.

CX200LC, CX200, CX400, CX600 Sometimes when a storage processor is shutting down as part of an NDU operation the following message appears in the Event Log: > Process ktdump terminated with exit code 0. This is an artifact of internal tracing code to support the diagnosis of field failures. [82254] CX200LC, 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 to the array correctly. [83371]

Frequency Frequent during an NDU operation Effect Error message appears in the Event Log. Prevention/Resolution The message is benign and should be ignored. It will be eliminated in a future release of the software.

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.

10

EMC CX200LC, CX200, CX400, CX600 FLARE Version 02.04.0.x0.5.002 Release Notes

Known Problems and Limitations

Limitations
This section lists issues that may affect the configuration or repair of the storage system. CX200LC, CX200, CX400, and CX600 Storage Systems 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. 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. Non-Disruptive Software Installation (NDU) and DAE2-ATA Enclosures If a disk array contains a DAE2-ATA enclosure in its configuration, you should not perform a non-disruptive software installation (NDU) while significant I/O activity is occurring to LUNs bound on that enclosure. If an NDU is attempted with a significant I/O load on DAE2-ATA LUNs, some of the ATA drives may become faulted during the NDU process. If this should happen, you can clear the condition by power-cycling the DAE2-ATA enclosure. Software Commits After performing a non-disruptive software installation (NDU), you are not allowed to bind LUNs 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 to 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.

EMC CX200LC, CX200, CX400, CX600 FLARE Version 02.04.0.x0.5.002 Release Notes

11

Known Problems and Limitations

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, you should not issue a revert because the software could be left in an inconsistent state. 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 CX400 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 when you add enclosures or make any changes to their addresses or cabling. (CX400, CX600 only) Always set the enclosure address on the DPE to enclosure address 0 or the array will not power up properly. DAE2 Replacement Restrictions You can installed 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.

12

EMC CX200LC, CX200, CX400, CX600 FLARE Version 02.04.0.x0.5.002 Release Notes

Technical Notes

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.

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

CX200LC, CX200, CX400, and CX600 Storage Systems

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. 4. Download disk firmware to disk 0_2. Download disk firmware to disk 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 Version 02.04.0.x0.5.002 Release Notes

13

Technical Notes

CAUTION If only one SP is running when you download disk firmware, do not start the second SP until after the download is complete. DAE2 Firmware Download FLARE and Access Logix 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. 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. Error Log Entries Appear Out of Order FLARE software may not always enter items into the Error 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. 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 14
EMC CX200LC, CX200, CX400, CX600 FLARE Version 02.04.0.x0.5.002 Release Notes

Technical Notes

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. Software Image Disk Replacement 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
EMC CX200LC, CX200, CX400, CX600 FLARE Version 02.04.0.x0.5.002 Release Notes

15

Documentation

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 non-functional.

CX200LC, CX200, and CX400 Storage Systems

DPE Power Supply Module Unplugged Causes SP to Not Power Up 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 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. SPE Fan Module Unplugged Causes SP Not to Power Up If you have your SPE fans unplugged when you power up the storage system, it does not come up until you plug the fans back in.

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

16

EMC CX200LC, CX200, CX400, CX600 FLARE Version 02.04.0.x0.5.002 Release Notes

Installation

Installation
Flare Software is installed on the storage system at the factory. This section describes the following: Installation Restrictions Installation Procedures Please refer back to the section on Software Commits for additional information relevant to software upgrades.

EMC CX200LC, CX200, CX400, CX600 FLARE Version 02.04.0.x0.5.002 Release Notes

17

Installation

Installation Restrictions
This section describes installation restrictions for the various storage-system types.
Installation Restrictions You cannot install Access Logix software on a CX200 LC. You cannot install the ThirtyDriveOption package on a CX200LC. The CX200LC is restricted to 15 drives. You cannot install FLARE software on a storage system with the Access Logix software. You must install a new revision of the SP Agent along with FLARE software revision in the same NDU operation. 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 install 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 install 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. CX200LC CX200 CX400 CX600

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 0850090645, for a list of supported storage systems. EMC recommends limiting software installation (non-disruptive upgrade) to periods of light I/O activity.

18

EMC CX200LC, CX200, CX400, CX600 FLARE Version 02.04.0.x0.5.002 Release Notes

Troubleshooting and Getting Help

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 ControlCenter Navisphere Manager Version 6.X Administrators Guide (P/N 069001125). Only a service provider should perform the installation procedure.

CX200LC

CX200

CX400

CX600

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 Web site at: http://powerlink.emc.com For CLARiiON documentation, after you log in to Powerlink, select Support (or Services) > Document Library > CLARiiON.

EMC CX200LC, CX200, CX400, CX600 FLARE Version 02.04.0.x0.5.002 Release Notes

19

Copyright and License Information

Copyright 2003 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, and Navisphere are registered trademarks and Access Logix, ControlCenter, FLARE, MirrorView, PowerPath, 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 of conditions. 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.

20

EMC CX200LC, CX200, CX400, CX600 FLARE Version 02.04.0.x0.5.002 Release Notes