1 EMC Navisphere Event Monitor Event Codes Release 19 Technical Note 10/11/2005 This technical note contains information on these topics: Basic Array Features 4 MirrorView 59 SnapView 126 SAN Copy 152 IP4700 155 Introduction This technical note is intended to serve as a referenceable and searchable list of events available within Navisphere ® Event Monitor. EMC® employees and customers planning to create customer Event Monitor templates using explicit events can use this list to search for event codes relative to an event of interest. All event codes fall into five major categories: Basic Array Features MirrorView™ SnapView™ SAN Copy™ IP 4700 The four levels of severity are: Information Warning Error Critical Error Events that are common across all CLARiiON® generations and models have three- or four-digit hexadecimal event codes. Storage-system events are three-digit hexadecimal numbers, while events pertaining to Event
156
Embed
Technical Note - img2.timg.co.ilimg2.timg.co.il/forums/1_161476647.pdf · CLARiiON dial-home template is used by EMC ... An Illustrative Overview of CLARiiON ... EMC Navisphere Event
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
1
EMC Navisphere Event Monitor Event Codes
Release 19
Technical Note
10/11/2005
This technical note contains information on these topics:
Basic Array Features 4 MirrorView 59 SnapView 126 SAN Copy 152 IP4700 155
Introduction This technical note is intended to serve as a referenceable and searchable list of events available within Navisphere® Event Monitor. EMC® employees and customers planning to create customer Event Monitor templates using explicit events can use this list to search for event codes relative to an event of interest. All event codes fall into five major categories:
Basic Array Features MirrorView™ SnapView™ SAN Copy™ IP 4700 The four levels of severity are:
Information Warning Error Critical Error Events that are common across all CLARiiON® generations and models have three- or four-digit hexadecimal event codes. Storage-system events are three-digit hexadecimal numbers, while events pertaining to Event
Monitor operation are four-digit hexadecimal numbers. Event codes that are exclusive to FC4700 and CX series systems have eight-digit hexadecimal event codes. Event severity for each category of event can be deciphered from the event code in the following manner:
Informational codes — require no action by the user. Informational codes are valuable to engineering in helping to establish history.
For common events: the Informational codes are generally three-digit hexadecimal numbers that begin with 6 or 7: for example, 601 and 734.
Event codes pertaining to Event Monitor itself are four-digit hex numbers that begin with 2, 3, 4, or 6. EMC Development uses the first two digits to identify various internal software components. The last two digits provide information regarding the severity of the event, and they range from 00 to 3f: for example, 2000 and 4010.
For codes exclusive to FC4700 and CX series systems, the fifth digit is 0.
Warning codes — these are normal and require no action unless they occur frequently.
For common events: the Warning codes are generally three-digit hexadecimal numbers that begin with 8: for example, 805.
Event Monitor Warning codes are four-digit hex numbers that begin with 2, 3, 4, or 6. The last two digits represent the warning level and range from 40 to7F: for example, 2041 and 6041.
For codes exclusive to FC4700 and CX series systems, the fifth digit is 4.
Error codes — typically require action by you or a support engineer.
For common events: generally, the Error codes are three-digit hexadecimal numbers that begin with 9: for example, 90C.
Event Monitor Error codes are four-digit hex numbers that begin with 2 and range from 2n80 to 2nBF: for example, 2181.
For codes exclusive to FC4700 and CX series systems, the fifth digit is 8.
Critical Error codes — typically require action by you or a support engineer.
For common events: The Critical Error codes are three-digit hexadecimal numbers that begin with the hex number a: for example, a02.
Event Monitor Critical codes are four-digit hex numbers that begin with 2 and range from 2nC0 to 2nFF: for example 20C5.
For codes exclusive to FC4700 and CX series systems: the fifth digit is C.
The Event Codes are arranged by category (Basic Array Features, MirrorView, SnapView, SAN Copy, and IP4700). All error codes within these categories are then listed by severity (Critical Error, Error, Warning, and Informational).
Related Documentation and Links The following EMC manuals, white papers, and websites provide information that is helpful in the deployment of Navisphere Event Monitor. The Navisphere Manager Administrator’s Guide provides explicit steps for setup and deployment. The Event Monitor Illustrative Overview presentation provides examples of various topologies as well as troubleshooting steps. Managing CLARiiON with SNMP is helpful to those interested in using Event Monitor to set up SNMP traps. Lastly, the CLARiiON dial-home template is used by EMC Customer Support to monitor events on customer systems. Custom templates are derived from the Call Home template by selecting the Create New Template Based On option within Navisphere Manager.
Event Codes The tables on the following pages include all the events available in Navisphere Event Monitor.
Basic Array Features
Critical Error 0x0A02 SCSI Bus Dead
0x0A05 NON VOL Not Initialized
0x0A06 Chassis Shutdown
0x0A07 CRU Powered Down
0x0A08 Database Sync Error
0x0A09 CRU Drive too Small
0x0A0A The inserted drive is too large considering the number of drives in the Raid Group. The drive does not become active when it is inserted.
0x0A0B Inconsistent DB detected
0x0A0C Flare Database write error. Please contact Tech Support immediately for further triage.
0x0A11 Peer SP is physically removed. Communication between SPA and SPB is down.
0x0A11 SP Removed
0x0A12 Cache Memory Hard Error
0x0A13 CRU Type Unsupported
0x0A14 CRU Database Reconstructed
0x0A15 RAID Group Database Reconstructed
0x0A16 Unsupported Drive Firmware
0x0A17 CRU Unformatted
0x0A18 CRU Drive Causing Loop Failure
0x0A19 Virtual Array Database Reconstructed
0x0A20 Checksum Format Unsupported
0x0A21 The power supply wattage rating is incorrect. Please make sure that a power supply with the required wattage rating is inserted.
0x0A22 The wattage rating for this power supply cannot be determined possibly due to error in reading resume PROM.
0x0A23 Peer SP is down because of hang/crash/bugcheck. The peer SP hardware is present but it is down for the reasons mentioned above. Communication between SPA and SPB is down.
0x0A24 Drive has a bad transmitter and will be taken offline. Please replace the drive.
0x0A25 Enclosure state change.
0x20c0 SP busy, couldn't respond to at least one Critical event on the SP
0x0911 The SPS Power cable 1 is not configured properly (not getting power supplied by SPS). Power cable 1 is to the xPE on Chameleon2 and is to the X1 enclosure on X1.
0x0912 The SPS Power cable 2 is not configured properly (not getting power supplied by SPS). Power cable 2 is to the first Katana enclosure on Chameleon2. This is not applicable for X1.
0x0913 The serial connection between the SP's and SPS's are crossed. This results is SP A controlling SPS B and vice versa. This condition makes it difficult to properly identify failing component.
0x0914 There are multiple cables (Power 1, Power 2, Serial) that are improperly configured.
0x0968 Unable to clear BBU card. Verify that no I/O is being written to the card, that the card is in the correct chassis, and is not faulted.
0x096E Batteries on the NVRAM card have failed to charge fully within the allotted time. Card is failed.
0x0970 Replace system fan 1.
0x0971 Replace system fan 2.
0x0972 Replace system fan 3.
0x0973 Replace system fan 4.
0x0974 Replace system fan 5.
0x0975 Replace CPU fan 6.
0x0976 Replace CPU fan 7.
0x0977 Replace power supply A.
0x0978 Replace power supply B.
0x0979 PROM and Database do not contain a valid serial number. Core Software is creating one for you. Please call your service provider as soon as possible.
0X097A An ATA disk rebuild/equalize started, and the disk write cache could not be enabled to optimize the rebuild/equalize time.
0X097B An ATA disk rebuild/equalize started, and the disk write cache could not be disabled.
0x2080 SP busy, couldn't respond to at least one Error event on the SP
0x2085 Event Monitor has encountered the following Error event, which could not be properly processed.
0x2086 Unable to read events from this Windows log.
0x2180 SP has been removed on host
0x2181 SP is faulted on host
0x2182 The computer has rebooted from bugcheck (0x3e8):<bugcheck_details>
0x2183 The computer has rebooted from bugcheck (0x3e9):<bugcheck_details>
0x2280 The central agent is attempting to monitor a remote host but is unable to resolve the hostname of the remote host
0x40008043 A Hi5 RAID group was created with multiple cache LUNs. This occurs during a bind of a LUN and indicates that the bind has failed.
0x40008044 An installed software package must be committed before this command can be accepted.
0x40008045 The error occurs only when an attempt is made to create Hi5 LUN with FC47000 software that does not support this RAID type.
0x40008046 The logical unit cannot be expanded because it is private.
0x40008047 A Navisphere CLI baseuuid command has been rejected, because the uuid value submitted is out of range.
0x40008048 An attempt to get the Array's Nice Name failed. It could not be read from the PSM because the PSM file that contains it is already open.
0x40008049 This code is used if there is a problem accessing the PSM while getting or setting the array's Nice Name.
0x4000804A Cannot read the array's Nice Name because the PSM file containing it is not using the current PSM format.
0x4000804B Currently this error is only used when an IOCTL to CMI to get the SP ID times out.This is likely to result in a poll failure.
0x4000804C This error indicates that the TLD list is missing items, resulting in a failure of the current command. Other commands make work fine.
0x4000804D This error indicates a malformed TLD list, resulting in a failure of the current command. Other commands make work fine.
0x4000804E
There was a failure trying to access one of the COM DLLs,, either of the layered driver DLLs, or K10HostAdminLib.DLL, K10FlareAdminLib.DLL, K10SystemAdminLib.DLL, or K10NduAdminLib.DLL. This usually indicates a severe configuration problem. One possible cause is that the DLL was compiled in a different environment than that present on the SP. That is, the versions of other DLLs that this DLL uses may differ.
0x4000804F The current bind failed, and subsequent binds will probably fail also. The problem is that the PSM cannot be accessed to determine if the Base NDU package is committed. A reboot might help.
0x40008050 The request to unbind a LUN has failed because the LUN has been allocated for use by a Layered Driver.The LUN must be unbound from the Layered Driver first.
0x40008051 If X1-lite is in non-HA mode, the ownership of a LUN could only be set to the local SP because of non-HA mode feature. E.g. binding a LUN would fail with this error if the assignment condition mentioned isn't met.
0x40008052 Cannot read feature from AdminLib.
0x40008053 Unbind failed-LU May Be Private.
0x40008054 Unable to expand RAID group or bind units. Software upgrade in progress.
0x40008059 Transfer of ownership of LUN <ID> failed
0x4000805A You are not allowed to transfer LUN <ID> to the other SP
0x4000805B Already using this IP address
0x4000805C Default Storage Group cannot be changed on this platform
0x40008100 Thread's IO state is invalid.
0x40008101 Pipe handle state is invalid.
0x40008102 The pipe state is inconsistent with other state data, such as the IO state.
0x40008103 The state is not a legal value.
0x40008104 The state is inconsistent with what just happenned.
0x40008105 One or more required buffers are full.
0x40008106 Reading a pipe yielded less data than expected, or no data at all. Could also be that NT indicated there was more pipe data, but none was available.
0x40008107 The MessageDispatcher detected an error, see text. This error code appears only in the event log messages.
0x40008108 The MessageDispatcher detected an error during initialization, see text. This error code appears only in the event log messages.
0x40008109 Private LUN attribute not applicable/changeable
0x41008000 The command for running the governor is K10Governor -<Params>, Param could be r, d, c, a, or p. This error is thrown when the input command hasn't that format.
0x41008001 Can't start governor, could be that that termination event (WaitForSingleObject) isn't in the signaled state or the time-out interval elapses, also could be failure on starting the service's thread.
0x41008002 Failure in calling function StartServiceCtrlDispatcher()
0x41008003 Failure in starting Governor service
0x41008004 Caught ASSERT or INT5
0x41008005 Cannot start Monitor thread after the retry limit has been reached.
0x41008006 Monitor can't start a process which Must Run
0x41008007 Can't create a process
0x41008008 A process object's state is signaled when the process terminates. A process terminated during startup.
0x41008009 A process timed out during startup
0x4100800A process got a wait failure during startup
0x4100800B A process failed
0x4100800C Process timed out waiting for a startup event.
0x4100800D There are no processes for monitor to start.
0x4100800F Monitor got a WaitForMultipleObjects() failure.
0x41008010 A Must Run process failed.
0x41008011 An unexpected return from main wait.
0x41008012 A process that was supposed to complete before others started exceeded its timeout interval.
0x41008013 Got an exception when trying to call InDegradedMode() to see if Sp is degraded.
0x41008014 Process did not respond to its terminate event. The Governor will stop it with TerminateProcess( ).
0x41008015 Unable to open the trace device when the tracing object was instantiated.
0x41008016 Unable to write a trace message to the trace buffers.
0x41008017 The Governor was unable to start any of the processes on its list.
0x41008100 Unable to delete an old dump. Old dumps are deleted to allow space for new ones. Obsolete.
0x41008101 Unknown fatal error.
0x41008102 Unable to read the registry entry that contains the name NT uses for the system dump file.
0x41008103 Name of the dump file read from the registry was NULL.
0x41008104 Unable to allocate memory to hold the name of the dump file.
0x41008105 Unable to expand the environment variables in the dump file name.
0x41008200 PSMdumper encountered an error. Check the Event Log text for details. There may also be a secondary error code in the data section of the event.
0x41008201 Unable to allocate memory to hold the PSM object.
0x41008202 Unable to allocate memory for a buffer.
0x41058000 A required registry value is missing.
0x41058001 A required registry key is missing.
0x41058002 Buffer provided was too small to hold the registry value.
0x41058003 Registry value is not of the expected type.
0x41058004 Unable to create or delete a key.
0x41058005 Unable to write a value to the registry
0x41058006 Could not convert a registry string into an integer.
0x41058007 Bad argument given to an internal function.
0x41058008 Unrecognized tag sequence.
0x60018000 Unrecognized database ID. This Database ID is not implemented and out of range
0x60018001 Unrecognized opcode. This opcode is not implemented and out of range.
0x60018002 Unrecognized item spec. This item spec is not implement and out of range.
0x60018003 This error will be thrown when maximum timeout ( 2 mins ) elapses when waiting for an asynchronous response from DeviceIoControl.
0x60018004 For a Read operation, the data returned is not as expected, i.e. EMPTY data, wrong size, or wrong structure.
0x60018005 Unrecognized TLD tag.
0x60018006 For an input TLD list, some data (TAG, data, field etc.) is missing.
0x60018007
In order to generate target wwn (Generate a single Type 6 (SIX) WWN using the K10_WWID struct as a container), call COM K10FlareAdminLib, DbId = K10_FLAREADMIN_DB_PASSTHROUGH, OpCode = MM_MPCODE_PEER
0x60018008 LUN divined from device name doesn't match LUN reported by FLARE.
0x60018009 The data returned from IOCTL call has the wrong size.
0x6001800A IOCTL failed, see data section for source error
0x6001800B Subroutine failed, see data section for source error
0x70008000 Unrecognized database ID in CDB.
0x70008001 Unrecognized op code in command.
0x70008002 Unrecognized item specifier in command.
0x70008003 Timed out waiting for an asynchronous response from a DeviceIoControl.
0x70008004 Other DeviceIoControl Error. NOT a timeout.
0x70008005 Command or functionality not supported
0x70008006 .Incorrect data element size.
0x70008007 PSM file version not supported
0x70008008 Trying to put private LU in a virtual array.
0x70008009 Pointer that was expected to be NULL wasn't.
0x7000800A Illegal input argument. Currently only posted by logging.
0x7000800B Illegal options bits for an initiator record.
0x7000800C File error; see description
0x7000800D An attempt to add an initiator to a port has failed because the number of initiators has already reached the maximum.
0x71108000 The MPS driver failed to load.
0x71108001 UMps sent a request to the MPS device driver with an unexpected size.
0x71108002 UMps sent an unsupported request to the MPS device driver.
0x71108003 The driver failed to load for the specified reason.
0x71108004 An underlying CMI conduit was assumed open when in fact it was not.
0x71108400 One of the parameters (i.e. filament handle, destination, buffer, etc.) passed to UMps was invalid (i.e. NULL or Zero).
0x7110880C A message re-transmission request arrived when the transmission was in an unexpected state.
0x7110880D Insufficient system resources existed to send an MPS level acknowledgement back to the sender.
0x7110880E Insufficient system resources existed to deliver an incoming message to a MPS client.
0x7110880F An unexpected version was received from the UMps open filament request.
0x71108810 An unexpected version was received from the UMps close filament request.
0x71108811 An unexpected version was received from the UMps synchronous-send request.
0x71108812 An unexpected version was received from the UMps synchronous-receive request.
0x71108813 An unexpected version was received from the UMps release received message request.
0x71108814 CMI returned an unexpected status immediately in the IOCTL call for a send transmission request.
0x71108815 CMI returned an unexpected status in the callback for a send transmission request.
0x71108816 CMI returned an unexpected status immediately in the IOCTL call for a re-transmission request.
0x71108817 CMI returned an unexpected status immediately in the IOCTL call for a re-transmission message.
0x71108818 The internal MPS transmission type (i.e. synchronous or asynchronous transmission) is invalid.
0x71108819 An underlying CMI conduit was assumed open on the unload-path when it was not.
0x7110881A A client of MPS returned an unexpected value from their callback routine.
0x7110881B The MPS memory budget was exceeded at initialization time.
0x7110881C The IRP allocation failed due to insufficient system resources after the request was assured to be within the memory budget of MPS.
0x7110881D The MDL allocation failed on the UMps synchronous-send request due to insufficient system resources after the request was assured to be within the memory budget of MPS.
0x7110881E The MDL allocation failed on the UMps synchronous-receive request due to insufficient system resources after the request was assured to be within the memory budget of MPS.
0x7110881F The first software version of MPS received a message re-transmission request for an earlier version.
0x71108820 The underlying CMI conduit id specified by a MPS client at filament open time was already open.
0x71108821 A MPS client freed a message unexpectedly.
0x71108823 The allocation for the safety net object failed. The first parameter specifies the transmission header for which the object was being allocated. The other parameters are 0.
0x71108824 MPS could not locate the internal safety net structure for a transmission. The first parameter specifies the opaque transmission handle from the sender. The other parameters are 0.
0x71118002 Inserting a Lock into the Lock Map returned Hash out of Range Error.
0x71118004 A new lock could not be inserted. HT_InsertBucket() returned an error.
0x71118008 Intenal Distributed Lock Service error.
0x7111800A Distributed Lock Service could not open its MPS filament.
0x7111800B Distributed Lock Service could not allocate a message.
0x7111800C Distributed Lock Service intenal error. The Clerk received an unknown message type.
0x7111800E The Local SP is being asked to process an unknown lock operation.
0x7111800F Distributed Lock Service could not allocate memory for a Distributed Lock.
0x71118013 The Local SP has been asked to open a lock while another Lock operation is in progress on the Local SP.
0x71118014 The Local SP could not find or create the requested Lock.
0x71118015 The Local SP has been asked to Close a Lock that has not been completely opened, or is the process of being closed.
0x71118017 The Local SP has been asked to Close a Lock while another Lock Operation is in progress.
0x71118018 The Local SP has been asked to Close a Lock that does not exist.
0x7111801C An illegal conversion request was made.
0x7111801D The Local SP has been asked to Convert a Lock while another Lock Operation.
0x7111801E The Local SP has been asked to Convert a Lock that does not exist.
0x7111801F The Local SP has been asked to Convert a Lock to an illegal mode
0x71118024 The Local SP has been asked to force a lock's mail box while another lock operation is in progress on the Local SP.
0x7111802A Distributed Lock Service iternal error.
0x7111802B Distributed Lock Service, processing pended lock operations on behalf of failing Peer, encountered an unexpected operation.
0x7111802C Distributed Lock Service, processing pended lock operations on behalf of failing Peer, received bad status
0x71118033 The Local SP's attempt to get its SPID failed.
0x71118034 The Local SP could not allocate memory for its lock tables.
0x71118035 The Local SP could not find a cabal registration while processing a cabal join request.
0x71118036 The Local SP could not find the cabal registration for a joining peer.
0x71118039 Distributed Lock Service inernal error
0x7111803A The Distributed Lock Service attempt to shut down the Valet failed
0x7111803B The Distributed Lock Service attempt to shut down the Clerk failed
0x7111803C The Distributed Lock Service attempt to shut down the Executioner failed
0x71118042 Could not remove a Ghost lock from the Valet tables.
0x71118043 Could not destroy a Ghost lock.
0x71118044 The Distributed Lock Service Valet's attempt to Remove a Lock from internal tables failed.
0x71118045 The Distributed Lock Service Valet's attempt to Remove a Lock from internal tables failed
0x71118049 The Distributed Lock Service's attempt to leave the Cabal failed
0x7111804A The Distributed Lock Service attempt to initialize the Message Passing Service failed
0x71118055 While dismissing the Peer SP, a registration with an unexpected state was encountered
0x71118056 The Distributed Lock Service Doorman, processing a Lock Reply, Read an invalid Peer Cabal Registration.
0x71118057 Closing all locks on behalf of failing Peer, received bad status
0x71118058 Could not allocate memory to send a Join Request to Peer SP
0x71118059 Could not allocate memory to send a Leave Notification to Peer SP.
0x7111805A Could not allocate memory to send a Join Request to Peer SP.
0x7111805B Could not add a lock to the Distributed Lock Service lock map
0x7111805C Could not find a lock immediately after creation
0x7111805E A Lock Operation requested by the Peer SP was not completed in the required time. The Lock's Name appears as Data in the System Event Log
0x7111805F A Lock Operation requested by the Peer SP was not completed in the required time. The Lock's Name appears as Data in the System Event Log
0x71118060 A allocation to add a Lock Request to the list of Requests to be times out failed. The Lock's Name is in the Data field in the System Event Log.
0x71118061 A Lock Request could not be added to the list of Requests to be timed out
0x71118062 A allocation to add a Lock Request to the list of Requests to be times out failed. The Lock's Identifier is in the Data field in the System Event Log.
0x71118063 A Lock Request could not be added to the list of Requests to be timed out
0x71178009 ScsiTarg can't use a port which it claimed (too many ports found).
0x7117800A DiskTarg or CMIscd registration with ScsiTarg failed.
0x7117800B DiskTarg or CMIscd activation with ScsiTarg failed.
0x7117800C
The table of host connections (also called initiators) for this port is full. Each port is only allowed 32 host connections. Note that in the interests of redundancy, a host may have multiple connectsions to a single port on the array. So that number of host connectsions may be greater. The log entry should contain text of the form "No room to add initiator, SP-X port Y.", where X is A or B, and Y is 0 or 1. The last 16 bytes of the hex data associated with the log message will contain the WWN of the initiator that we were unable to add.
0x7117800D Cannot initialize CMM, got status %2.
0x7117800E Old PSM file used to store host configuration data has been updated since the new PSM file has been created, or the new PSM file does not exist. Conversion utility (HsCx00ToCx50Conversion) must be executed.
0x7117B264 Host operation aborted by host, but cancellation not completed within 3 minutes.
0x71188000 Generic CMI Error Code.
0x71188001 Could not determine my own SP ID.
0x71188002 Invalid Engine Number in SP ID.
0x71188003 Could not determine its own SP Index.
0x71188004 Could not determine the peer's SP Index.
0x71188005 No Transport Devices were found.
0x71188006 Could not allocate contiguous Bundle buffer.
0x71188007 Could not allocate Device Info Table.
0x71188008 Transport Device failed to initialize.
0x71188009 Serial Line to peer failed to initialize.
0x7118800A Could not open Control Conduit.
0x7118800B Could not get Device Object of a Transport Device.
0x7118800C Handshake with Transport Device never returned.
0x7118800D Handshake with Transport Device failed.
0x7118800E SP Index Table has overflowed.
0x7118800F Gate Table has overflowed.
0x71188010 Could not open SPID pseudo-device.
0x71188011 Could not get the Device Object of the SPID pseudo-device.
0x71188012 Could not allocate an IRP to contact the SPID pseudo-device.
0x7127897C A Disk was failed or removed. This error shall be logged in NT system event log in addition to HOST_FRU_POWERED_DOWN.
0x71298000 Unable to initialize memory mapping of poll data. Polls will fail.
0x71298001 Unable to initialize allocate memory for poll data. Polls will fail.
0x71298002 Unable to create mutex used to prevent overlapping polls. Poll will fail.
0x71298003 Unable to obtain poll data.
0x71298004 Unable to obtain size of poll data. Poll will fail.
0x71298005 Timeout while waiting to obtain mutex used to prevent overlapping Poll results. Another process that polls may be hung.
0x71298006 Unable to obtain Flare poll mutex. The 2nd error code in the NT log entry may indicate the reason for the failure. It possible that future poll attempts will succeed, or even future requests for data from the current poll.
0x71298007 Illegal value in Flash control command.
0x71298008 Unexpected return value in WaitForSingleObject(). Indicates a serious software or OS problem.
0x71298009 More LUNs than allowed. Could indicate a version mismatch between FlareCom.dll and flare driver.
0x7129800A More RAID Groups than allowed. Could indicate a version mismatch between FlareCom.dll and flare driver.
0x7129800B Illegal number of SPs were seen in the poll data either 0 or >2. Could indicate a version mismatch between FlareCom.dll and flare driver, which is why a revert is recommended, if new software was just installed.
0x7129800C The SP key is invalid.
0x7129800D Please contact your service provider.
0x7129800E The key is not of the proper component type.The text may give more detail.
0x7129800F The key for this component is invalid.
0x71298010 The FlareData object passed to the FlareArray constructor is NULL.
0x71298011 A Flare IOCTL returned the wrong amount of data.
0x71298012 At least one of the values supplied to create a key is invalid. This may mean that expected hardware is missing.
0x71298013 The CDB specified in a pass-thru command is invalid, probably too large.
0x71298014 Unable to obtain the SP ID from the SPID driver. See text for details. No polling can take place.
0x71298015 Data supplied for pass thru write is too big.
0x71298016 An attempt was made to flash LEDs on an XPE enclosure. This is not supported.
0x71298017 This error indicates a problem with FlareData lock management. A deadlock with the device map lock is likely, indicated by a Lockwatch
warning The problem may be solved by rebooting the SP.
0x71328001 SMBus hardware error <Error status>
0x71388001 Unable to read configuration from the PSM.
0x713A8009 An installed software package must be committed before creating/configuring a MetaLUN
0x713A800D An attempt to delete a MetaLun has failed .
0x713A800E An attempt to delete a MetaLun has failed .
0x713A800F The MetaLun requested in the current operation cannot be found.
0x713A8010 The MetaLun requested in the current operation cannot be found.
0x713A8011 The MetaLun requested in the current operation cannot be found.
0x713A8012 Poll Information Inconsistent.
0x713A8013 Poll Information Inconsistent.
0x713A8014 Poll Information Inconsistent.
0x713A8015 The requested operation cannot be done because of an NDU operation is already in progress. Allow the operation to complete first.
0x71408000 Required data is missing from the TLD list.
0x71408002 Wrong TLD config by Navi
0x71408003 Not supported (e.g. set more than one instance)
0x71408004 Failure in getting data from flare
0x71408005 Can not find object requested
0x71408006 Command refers to more than 2 SPs.
0x71408007 A command to set an iSCSI alias contains a nonprinting character.
0x71408009 Invalid MTU size.
0x7140800A Invalid port speed.
0x71478001 This storage processor has most likely rebooted and servers may have lost access to data. No action required. A command was completed which was not active.
0x71478002 This storage processor has most likely rebooted and servers may have lost access to data. No action required. An incorrect Sector Map length was generated during 520 to 512 address conversion.
0x71478003 This storage processor has most likely rebooted and servers may have lost access to data. No action required. An unexpected event has been received for the current state.
0x71478004 This storage processor has most likely rebooted and servers may have lost access to data. No action required. SFD Illegal State Machine execution.
0x71478005 This storage processor has most likely rebooted and servers may have lost access to data. No action required. A Request Object is required by this function.
0x71478006 This storage processor has most likely rebooted and servers may have lost access to data. No action required. The Sector Lock List is corrupted for a drive.
0x71478007 This storage processor has most likely rebooted and servers may have lost access to data. No action required. The Sector Locker Destructor was called with outstanding locks active for a drive.
0x71478008 This storage processor has most likely rebooted and servers may have lost access to data. No action required. Attempt to release memory not allocated by Memory Class.
0x71478009 This storage processor has most likely rebooted and servers may have lost access to data. No action required. Initialization running out of contiguous memory.
0x7147800A This storage processor has most likely rebooted and servers may have lost access to data. No action required. Edge Cache found inconsistency in sectors.
0x7147800B This storage processor has most likely rebooted and servers may have lost access to data. No action required. Edge Cache find overlapping edge page in use.
0x7147800C This storage processor has most likely rebooted and servers may have lost access to data. No action required. Not enough request available in edge cache.
0x7147800D This storage processor has most likely rebooted and servers may have lost access to data. No action required. Failed to create PNP device.
0x7147800E This storage processor has most likely rebooted and servers may have lost access to data. No action required. Failed to attach PNP device.
0x7147800F This storage processor has most likely rebooted and servers may have lost access to data. No action required. Unknown execution class.
0x71478010 This storage processor has most likely rebooted and servers may have lost access to data. No action required. Corrupted SGL.
0x71478011 This storage processor has most likely rebooted and servers may have lost access to data. No action required. SFD can not allocate temporary buffer for Inquiry.
0x71478012 This storage processor has most likely rebooted and servers may have lost access to data. No action required. SFD received non NULL Inquiry for bus on port 0.
0x71478013 This storage processor has most likely rebooted and servers may have lost access to data. No action required. SFD recevied NULL Inquiry for bus on port 0.
0x71478014 This storage processor has most likely rebooted and servers may have lost access to data. No action required. SFD received out of range flare drive.
0x71478015 This storage processor has most likely rebooted and servers may have lost access to data. No action required. SFD read received SGL list more than
0x71478016 This storage processor has most likely rebooted and servers may have lost access to data. No action required. SFD read received SGL list not divisible by 512.
0x71478017 This storage processor has most likely rebooted and servers may have lost access to data. No action required. SFD Read could not allocate IRP.
0x71478018 This storage processor has most likely rebooted and servers may have lost access to data. No action required. SFD Read could not allocate either IrpC or SrbC.
0x71478019 This storage processor has most likely rebooted and servers may have lost access to data. No action required. SFD write received SGL list more than 64K.
0x7147801A This storage processor has most likely rebooted and servers may have lost access to data. No action required. SFD write received SGL list not divisible by 512.
0x7147801B This storage processor has most likely rebooted and servers may have lost access to data. No action required. SFD write could not allocate IRP.
0x7147801C This storage processor has most likely rebooted and servers may have lost access to data. No action required. SFD write could not allocate either IrpC or SrbC.
0x7147801D This storage processor has most likely rebooted and servers may have lost access to data. No action required. SFD IrpDoneCompletion received SGL list more than 64K.
0x7147801E This storage processor has most likely rebooted and servers may have lost access to data. No action required. SFD IrpDoneCompletion received SGL list not divisible by 512.
0x7147801F This storage processor has most likely rebooted and servers may have lost access to data. No action required. SFD IrpDoneCompletion unknown status.
0x71478020 This storage processor has most likely rebooted and servers may have lost access to data. No action required. SFD handlePnpQueryDeviceRelations no localIrp.
0x71478021 This storage processor has most likely rebooted and servers may have lost access to data. No action required. SFD handlePnpRequests received IRP_MN_QUERY_ID.
0x71478022 This storage processor has most likely rebooted and servers may have lost access to data. No action required. SFD handlePnpRequests received IRP_MN_QUERY_RESOURCE_REQUIREMENTS.
0x71478023 This storage processor has most likely rebooted and servers may have lost access to data. No action required. SFD handlePnpRequests received IRP_MN_QUERY_RESOURCE.
0x71478024 This storage processor has most likely rebooted and servers may have lost access to data. No action required. SFD handlePnpRequests received unknown request.
0x71478025 This storage processor has most likely rebooted and servers may have lost access to data. No action required. SFD - Can not allocate IRP.
0x71478026 This storage processor has most likely rebooted and servers may have lost access to data. No action required. SFD: sendIoctl: Unknown IOCTL.
0x71478027 This storage processor has most likely rebooted and servers may have lost access to data. No action required. SFD sendIoctl: IRP_MJ_SCSI: Unknown IOCTL with Unknown SRB.
0x71478028 This storage processor has most likely rebooted and servers may have lost access to data. No action required. SFD: sendIoctl: Unknown IOCTL for MajorFunction IRP_MJ_DEVICE_CONTROL.
0x71478029 This storage processor has most likely rebooted and servers may have lost access to data. No action required. SFD: sendIoctl: Unknown IOCLT with Unknown SRB Function with unknown SRB ioctl.
0x7147802A This storage processor has most likely rebooted and servers may have lost access to data. No action required. SFD: sendIoctl: Unknown Major Function.
0x7147802B This storage processor has most likely rebooted and servers may have lost access to data. No action required. SFD sendSrb - no irp!
0x7147802C This storage processor has most likely rebooted and servers may have lost access to data. No action required. SFD: sendSrb - no myIRP or mySrb!
0x7147802D This storage processor has most likely rebooted and servers may have lost access to data. No action required. SFD setupIrpSrb can not allocate Sense buffer.
0x714A800C Package not committed. Commit the Base package before starting or modifying a LUN migration
0x714A8014 A Migration configuration operation has failed. This Migration may have already been cancelled.
0x714A801A A metaLUN member LUN may not be migrated to a metaLUN.
0x71508012 An illegal value was specified for the type of AutoTrespass.
0x71518000 The command contained an unknown operation ID.
0x71518001 The command contained an unknown operation code.
0x71518002 The command did not contain a required name or path.
0x71518003 This file is either not a valid upgrade file or is corrupt. It may have been corrupted during a file transfer. Obtain a new copy and retry the upgrade.
0x71518004 Installation did not occur. At least one software package requires another package to be installed at the same time.
0x71518005 The software package specified is not installed.
0x71518024 An attempt to uninstall software on the master SP failed
0x71518025 A delete or free of memory failed
0x71518026 An SP failed to reboot
0x71518027 An SP failed to reboot
0x71518028 A sync operation had a failure.
0x71518029 A read from PSM failed.
0x7151802A A read from the ToC failed
0x7151802B A rename in the ToC Mirror function failed
0x7151802C The array was unable to determine the disk free space.
0x7151802D The array was unable to determine the size of the disk.
0x7151802E The array has an incorrectly partitioned disk.
0x7151802F The array had an error while handling the SPID.
0x71518030 The array had an error while handling the WWN.
0x71518031 The array had an error while getting the port id.
0x71518032 The array had an error while setting the port id.
0x71518033 The array had an error while synchronizing SP times
0x71518034 Failed to disable cache settings
0x71518035 Failed to restore cache settings
0x71518036 NDU failure: Unknown argument
0x71518037 An internal error occurred and the software package could not be committed. Ensure that the PSM is available and retry the commit. Otherwise call service provider
0x71518038 An internal error occurred during the creation of a service. Call service provider
0x71518039 Cannot upgrade both ephemeral and persistent packages together.
0x7151803A Access Logix cannot be uninstalled
0x7151803B A sync operation is required. Reboot either SP
0x7151803C Permit attribute dependency not met. This package is not allowed on this platform type.
0x7151803D Installation will break an existing permit dependency. The already installed package needs to be replaced by a newer version.
0x71558000 Required data is missing from the TLD list.
0x71558002 Wrong TLD config by Navi
0x71558003 Not supported (e.g. set more than one instance)
0x71558007 The command has been rejected because the number of Storage Groups has already reached the maximum.
0x71558009 A command has been rejected because it involves changing an object that is only accessible on the peer SP.
0x7155800a Authentication secret is the same as a secret in the other direction.
0x7155800b This command requires that Portal Groups exist.
0x7155800c Port data not available.
0x7155800d No IP Prop object defined for port.
0x7155800e Cannot find port with specified key.
0x71558010 No Portal was defined for the specified port.
0x71558013 The iSCSI name contains an illegal character.
0x71558014 The user name contains an illegal character.
0x71558015 The submitted iSCSI name is too large.
0x71558016 The submitted user name is too large.
0x71558017 You already have the maximum number of CHAP credentials.
0x71558018 You have already created the maximum number of Portal Groups.
0x71558019 You cannot create any more IP Properties for this port.
0x71568001 This storage processor has most likely rebooted and servers may have lost access to data. No action required. The CMIpci recovery thread encountered an unknown recovery control event.
0x71568002 This storage processor has most likely rebooted and servers may have lost access to data. No action required. The CMIpci driver received more I/O requests that it could concurrently process.
0x71568003 This storage processor has most likely rebooted and servers may have lost access to data. No action required. The recovery thread was unable to allocate a page of recovery blocks.
0x71568004 This storage processor has most likely rebooted and servers may have lost access to data. No action required. A message was received from the peer SP with an unknown message type.
0x76008000 Unrecognized database ID in CDB.
0x76008001 Unrecognized op code in command.
0x76008002 Unrecognized item spec in command.
0x76008003 Timed out waiting for an asynch. Response from a DeviceIoControl.
0x76008004 wrong size for struct expected.
0x76008005 DeviceIoControl failure, other than a timeout.
0x76008009 Did not init an object before using - programmer error
0x7600800A Subroutine failed; see data section for source error
0x7600800B Precondition not met/logic error.
0x7600800C Cannot alloc or free memory
0x7600800D Registry key in unexpected format
0x7600800E Cannot query key/value; See data section for source error.
0x7600800F Cannot read value; See data section for source error.
0x76008010 The PSM Driver is not accessible
0x76008011 The PSM LU is not bound.
0x76008012 The file opened for read, or sized, has not been initialized by this class
0x76008013 An unlinked reference to a public LU was found and removed
0x76008014 Transaction system exceeded nesting maximum.
0x76008015 Unable to get the WWN seed from the SP data
0x76008016 Network adapter key not found
0x76008018 Network adapter key not found
0x7600801A
The port is not yet available for configuration. Recovery: This error should clear when initialization is completed. If it persists, a reboot will usually clear it. The procedure for attempting recovery without a reboot depends on how far the initialization got and is too detailed to be covered in this document.
0x7600801a The port is not yet available for configuration
0x7600801B First part of IP address cannot be > 223
0x7600801C First part of IP address cannot be = 127
0x7600801D First part of IP address cannot be = 0
0x7600801E This particular IP address is illegal
0x7600801F First part of the Gateway IP address cannot be > 223
0x76008020 First part of the Gateway IP address cannot be = 127
0x76008021 The last bit of the Subnet mask must be 0
0x76008022 The Subnet mask can contain at most one transition between ON and OFF bits
0x76008023 Subnet mask value is illegal
0x76008100 DGSSP encountered an error with a subroutine; see message details
0x76008101 Found single bit ECC error. See message details.
0x76008102 Found multibit ECC error. See message details.
0x79508021 Can't set default gateway in the registry.
0x79508022 Can't set DHCP flag in the registry.
0x79508023 NetID is not in the range, i.e. not one of the following: DomainName, IPAddress, DHCP, SubnetMask, DefaultGateway.
0x79508024 TLD data was not of the expected type. Usually this is caused by numeric data that should fit in a long being larger than sizeof(long).
0x79508025 Unexpected bytes returned from an IOCTL call.
0x79508026 Subroutine failed, see data section for source error.
0x79508027 Logic error.
0x79508028 An XLU was scrubbed from the database due to inconsistant data
0x79508029 Can not add a layer if the LUN is expanding
0x7950802B Normally, the code that generates this error is only executed during NDU of the Base package. Therefore, this error should result in NDU failure. The NDU should not be retried until the cause of the error is determined.
0x7950802C Normally, the code that generates this error is only executed during NDU of the Base package. Therefore, this error should result in NDU failure. The NDU should not be retried until the cause of the error is determined.
0x7950802D Normally, the code that generates this error is only executed during NDU of the Base package. Therefore, this error should result in NDU failure. The NDU should not be retried until the cause of the error is determined.
0x7950802E Normally, the code that generates this error is only executed during NDU of the Base package. Therefore, this error should result in NDU failure. The NDU should not be retried until the cause of the error is determined.
0x79508030 This LUN is being used by another application which will not allow it to be used simultaneously by this application.
0x79508036 An attempt was made to insert a layered driver into the device stack of an LU with an operation in progress (expansion, for example), but the layered driver doesn’t support that operation.
0x79508037 An attempt was made to start an operation (expansion, for example) with a layered driver on the LU’s device stack that doesn’t support the operation.
0x79508038 An attempt was made to take a LU private while an operation is in progress that is not supported by the layered driver.
0x79508039 The specified LUN cannot be found and may have been deleted. Retry the operation with a valid LUN.
0x80004003
Windows NT error, defined in winerror.h. This error occurs when performing a Read or Write operation, the input pointer is NULL, e.g. For write operation, input TLD list (or buffer) is NULL, buffer size is 0, or error value address is NULL; for a read operation, error value address is NULL.
Windows NT error , defined in winerror.h. This error occurs when preconditions are not satisfied for a read or write operation, e.g. For a write operation: Any of the following Preconditions is not satisfied: Buffer Size >= 0 if Buffer Size > 0, input buffer is not NULL if Buffer Size = 0, input buffer is NULL, Error value address is not NULL.
0x8A0C Flare Database write error. Please contact Tech Support immediately for further triage.
Warning 0x0801 Soft SCSI Error
0x0802 Illegal SCSI Bus Interrupt
0x0803 Recommend Disk Replacement
0x0804 Single Bit Error
0x0805 Read Memory Errors; Logging Disabled
0x0806 The storage system has adjusted its parameters appropriately for the current disks
0x0810 Single Bit Error
0x0820 Soft Media Error
0x0840 Data Sector Invalidated
0x0850 Enclosure State Change
0x0851 Enclosure Address Error
0x0852 Enclosure Duplicate Address Error
0x0854 The LCC cables are connected to the wrong input port. Make sure that the LCC input cable is connected to the primary port.
0x0855 xPE Enclosure State Changed
0x0856 Enclosure 2.5V power fault
0x0857 Enclosure 3.3V power fault
0x0860 Recoverable Reset Event
0x0861 SBERR Detected for SP
0x0862 Single-bit ECC Error in Write Cache
0x0863 Single-bit ECC Error in Read Cache
0x0864 Mirror Sector Invalidated
0x0865 Log Hardware Error
0x0866 LCC Upgrade Error: %x
0x0867 The read can fail because of: 1.The device might not be present 2.The device might be dead 3.I2C bus error 4.Checksum Error.
0x0870 Battery on the SP Board is either low or missing. Install new battery.
0x0871 SP boot disk is not mirrored.
0x0873 Customer boots system and Flare's ATM detects one CMI connection is down.
0x0875 Enclosure <number>, Cabling is incorrect to BE Loop.
0x0876 Enclosure does not support 4G mode.
0x0877 Drive Initialization Failure on Drive %s
0x0878 LCC report a General Fault
0x0879 lccgetlog request failed
0x2040 Event Monitor log was backed up and cleared
0x2045 Event Monitor has encountered the following Warning event, which could not be properly processed.
0x2046 This Windows log has wrapped. Events in this log will not be processed.
0x2047 The system time has been set backwards. This may affect event collection.
0x2140 SP slot is EMPTY on host
0x2141 SP busy, couldn't respond to at least one Warning event on the SP
0x2240 Communication failed with host
0x2241 Communication failed with host agent
0x2242 Communication failed with SP agent
0x2541 Response to PSM read request exceeded 115 seconds.
0x40004000 The MessageDispatcher received an explicit shutdown command.
0x40004001 The MessageDispatcher detected an error during initialization, see text. This error code appears only in the event log messages.
0x40004002
An error occurred trying to open a PDH query (PdhOpenQuery). See the second error code in the event log for the cause of the error, listed in pdhmsg.h. The PDH library is currently used for the SP Busy and Idle fields in Pages 0x26 and 0x2C.
0x40004003
An error occurred trying to add a counter to a PDH query. See the second error code in the event log for the cause of the error, listed in pdhmsg.h. The PDH library is currently used for the SP Busy and Idle fields in Pages 0x26 and 0x2C.
0x40004004
An error occurred trying to get data for a PDH query (PdhCollectQueryData). See the second error code in the event log for the cause of the error, listed in pdhmsg.h. The PDH library is currently used for the SP Busy and Idle fields in Pages 0x26 and 0x2C.
An error occurred tyring to get a formatted counter from PDH query data (PdhGetFormattedCounterValue). See the second error code in the event log for the cause of the error, listed in pdhmsg.h. The PDH library is currently used for the SP Busy and Idle fields in Pages 0x26 and 0x2C.
0x40004006
An error occurred tyring to close a PDH query. See the second error code in the event log for the cause of the error, listed in pdhmsg.h. The PDH library is currently used for the SP Busy and Idle fields in Pages 0x26 and 0x2C.
0x40004007 An error occurred tyring to read or write NT registry values. Currently only used to save running counts of SP Busy and Idle tics.
0x4040 User was denied access.
0x4041 Password is invalid.
0x4042 No user roles defined.
0x4043 Specified user already exists.
0x4044 Role value specified is invalid.
0x4046 Update of the accounts file encountered an error.
0x4047 Selected user is the only global administrator.
0x4048 Scope value specified is invalid.
0x4049 Username is invalid.
0x404A User does not exist.
0x404B Update of the local user information failed.
0x404C Credentials do not match.
0x404D Error encountered during the deletion of the user account.
0x404E Security initialization failed.
0x404F Unable to write data to persistent storage - file not updated.
0x4052 Change user request failed.
0x41004000 SP is in degraded mode.
0x41004001 A process did not post a startup event within the allotted time.
0x41004002 A process ran to completion without ever posting a startup event
0x41004100 DumpManager encountered an error, but it should not necessarily otherwise effect the operation of the array.
0x41004101 Unable to delete an old dump. Old dumps are deleted to allow space for new ones.
0x41004200 PSMdumper encountered an error, but it should not necessarily otherwise effect the operation of the array. Check the Event Log text for details.
0x41004201 Could not find a PSM file.
0x41004202 Could not access the PSM file because it is currently in use.
0x4D47 No available LUs for cloning on the system.
0x4D48 Specified LU is not available for cloning.
0x4D49 The Clone Private LUNs have not been allocated.
0x4D50 The protected restore is not supported.
0x4D51 The optional fast recovry is not supported.
0x4D52 Can not add clone, the Max number of clones are already present on CloneGroup.
0x4D53 Can not add clone, since a clone in the clone group is syncing or reverse syncing.
0x4D54 Unable to sync or reverse sync clone before it be fractured.
0x4D55 Unable to reverse sync clone because it is Out-Of-Sync.
0x4D56 Unable to reverse sync clone because a clone in its CloneGroup is either Synchronizing or Reverse Synchronizing.
0x4D57 Unable to sync clone because a clone in its Clone Group is either Reverse Synchronizing or Reverse Out-Of-Sync.
0x4D58 Unable to deallocate CPL while there is still clone group.
0x71054607 Consistency Group %2 has been force promoted while Consistency Group service on the remote system was in degraded mode. Check for Consistency Group and MirrorView error messages on the remote system.
0x71114001 Distributed Lock Service internal status that indicates that lock with the specified name has not been found.
0x71114002 Distributed Lock Service internal status that prevents a lock name from being added twice.
0x71114003 Distributed Lock Service internal status that indicates that a search of the Lock Map by Cabal Lock Id failed.
0x71114004 Distributed Lock Service status that indicates the a lock is being opened. The caller will receive a call back when the open is complete.
0x71114005 Distributed Lock Service status that indicates the a lock is being closed. The caller will receive a call back when the open is complete.
0x71114006 Distributed Lock Service status that indicates the a lock is being converted. The caller will receive a call back when the open is complete.
0x71114009 Distributed Lock Service internal status.
0x7111400A An attempt with the DLS_CLIENT_CONVERT_LOCK_NO_WAIT flag to request to convert a lock was denied.
0x7111400B The Peer SP is being dismissed. Dismissal will be complete when the Peer is a Zombie.
0x71244007 Login Failed disk <number> [timeout|ERROR <code>]
0x71244008 Mirror Database initialized on disk <number>
0x71244009 No Mirror Database address could be read on disk <number> [R|W]
0x7124400A Buffer modified on write <number of sectors> sectors written to LBA <lba> ([WE or WC])
0x71294000 Unable to release the lock that prevents Polling while reading Poll data. This is not debilitating unless the lock cannot be reaquired later
0x71294001 Unable to release the mapping of shared memory used for Poll data. This is not debilitating unless the memory cannot be remapped later
0x71294002 Unable to close mutex used for Poll locking. The mutex is closed when a FlareData object destructs.
0x713e4001 The NVRAM device was not found on the scanned PCI buses. Internal error - call your service provider
0x713e4005 The device could not be mapped. Internal error - call your service provider
0x713e4006 The Library was asked to perform an unknown operation. Internal error - call your service provider
0x71564001 All internally allocated data transfer buffers are in use - performance may be degraded.
0x71574001 Migration Sync Manager. Migration driver has invalidated the destination LUN <lun number> at sector <LBA> (source LUN <lun number>).
0x71574002 The migration error was unable to continue due to a synchronization error between the source and destination. Most likely either the source or destination has entered the shutdown state. <lun number>.
0x71584001 SPCollect was not launched successfully.
0x71584002 There is not enough disk space available for SPCollect to run.
0x71584003 Unable to delete spcollect file: %s
0x76004000 EMPTY transaction log. Only seen in diagnostic apps.
0x76004001
This warning is posted when the Admin layer updates the list of public LUNs by removing any entries that are stale. The text explains which LUNs were removed and/or why. Examples are: Scrubbed XLU: Duplicate XLU found Scrubbing <Name of LUN> Scrubbed Extra XLUs Scrubbed Unconsumed XLUs
0x76004003 While cleaning up a failed transaction, the transaction recovery failed. The PSM transaction was cleared to prevent repeated retries.
0x76004100 DGSSP agent non-fatal condition
0x76004101 Found a warning form POST. See text for details.
0x062B 1. SPS Power cable 1 is configured improperly. 2. Check the appropriate Power cable and make sure it is connected to the SPS and not plugged directly into the power bar.
0x062C 1. SPS Power cable 2 is configured improperly. 2. Check the appropriate Power cable and make sure it is connected to the SPS and not plugged directly into the power bar.
0x062D SP-to-SPS cables are configured improperly. Check the SP-to-SPS cables to make sure they are configured properly.
0x062E Multiple SPS cables are configured improperly Check all SPS cables (Power & Serial) to make sure they are configured properly.
0x062F The SPS is ready, but the SPS configuration is invalid. Look at SPS status to get more specific information about how the SPS is incorrectly configured and then correct the configuration.
0x0630 Fan Installed
0x0631 VSC Installed
0x0632 AC Box Installed
0x0633 Fan Speed Increased
0x0634 Fan Speed Decreased
0x0635 Inconsistent Check Information
0x0636 BBU Removed
0x0637 BBU Recharging
0x0638 BBU Enabled
0x0639 System Cache Enabled
0x063A The enclosure is operating in 1 GIG mode. Hardware jumper setting on the enclosure is 1 GIG.
0x063B The enclosure is operating in 2 GIG mode. This is Normal operation for Chameleon2 array.
0x063C The SPs Serial Port is not setup correctly for SPS communications. Check the Default operating system setting to make sure that COM2 is not being used as the Debug port
0x063E A port glitch was detected by the LCC.
0x063F Resume PROM information was read successfully.
0x069D A Bad Drive or LCC is causing Fibre Channel to be Hung. The process of isolating the bad hardware has started
0x069E A Bad Drive or LCC is causing Fibre Channel to be Hung. The Process of isolating the bad hardware has completed.
0x069F Read cache enabled.
0x06A0 Disk soft media error.
0x06A1 The two extended status in the Navi event log displays the last 8 characters of serial numbers in hex format.
0x06A2 Hot Spare is now replacing a failed drive.
0x06A3 Hot Spare is no longer replacing a failed drive.
0x06C0 BE (Backend) Fibre Loop Error
0x06C1 BE (Backend) Fibre Loop Down
0x06C2 BE (Backend) Fibre Loop Hung
0x06C3 BE (Backend) Fibre Loop Operational
0x06C4 BE (Backend) Fibre Loop Node Fault
0x06C5 BE (Backend) Fibre Node Login Retry
0x06C6 BE (Backend) Fibre Node Login Failed
0x06C7 Fibre Channel Unknown Event
0x06C9 Fibre Unknown
0x06CA Front-end Fibre Timeout Due to Full FIFO
0x06CB Back-end Fibre Timeout Due to Full FIFO
0x06CC The SPS configuration has changed and needs to be tested. No action required unless the SPS test fails (will see other event messages in that case).
0x0750 A disk was inserted and its logical structure was processed.
0x0751 This message is seen when the SP is booting up.
0x0752 A disk was removed.
0x0753 This message is seen when the SP is booting up.
0x0754 Logical format of the disk was partially incorrect and was reconstructed successfully.
0x0755 Certain sectors on the disk might be corrupted.
0x0756 Reconstruction of a disk logical structure was interrupted.
0x0757 A disk was inserted and its logical structure was processed. The manufacture zero mark was detected.
0x0760 Power Supply A on the xPE is Restored
0x0761 Power Supply B on the xPE is Restored
0x0762 Fan Module C on xPE has been installed or repaired.
0x0763 Fan Module B on xPE has been installed or repaired.
0x0764 Fan Module A on xPE has been installed or repaired.
0x0765 Fan Module C on xPE is faulted or removed.
0x0766 Fan Module B on xPE is faulted or removed.
0x0767 Fan Module A on xPE is faulted or removed.
0x0768 A fan is faulted on the xPE.
0x0770 The ulog message is 'Recommend disk firmware upgrade'.
0x0771
Recovery:A host read or write command was aborted. This is normal and the command will be retried by the host in most cases. Among the possible causes of this are: disabling the cache and pulling cables. If these messages persist or become frequent, please contact your service provider.
0x0773 Power Supply A AC Power on the xPE has been restored
0x0774 Power Supply B AC Power on the xPE has been restored
0x0793 Enclosure <number>, Cabling is correct to BE Loop.
0x0794 Enclosure <number>, Cabling is connected to BE Loop.
0x0795 Attempt to mark unit as cache clean has failed with an error. If the unit fails to assign then have your service provider clear clean/dirty flag of the unit.
0x0798 The Drive Port Bypass Circuit Status changed.
0x079C HOST_DRIVE_PBC_STATUS_CHANGED messages in the ULOG. The drive may or may not power down prior to seeing the above error code. The drive will however power down after this error code is logged.
0x079D An ATA disk rebuild/equalize started, and the disk write cache was enabled to optimize the rebuild/equalize time.
0x079E An ATA disk rebuild/equalize halted or completed and the disk write cache was disabled.
0x079F A get enclosure event log request has completed successfully for this enclosure.
0x07A1 Sniff Verify was enabled by the user on a unit.
0x07A2 Sniff verify disabled by user.
0x07A2 Sniff Verify was disabled by the user on a unit.
0x07A3 User control of sniff verify is enabled.
0x07A3 User Control of Sniff Verify Enabled.
0x07A4 User control of sniff verify is disabled.
0x07A4 User Control of Sniff Verify Disabled.
0x07A5 Drive removed, seen by local SP. Removed either physically, via software or a fru signature failure.
0x07A6 Drive removed, seen by peer SP.Removed either physically, via software or a fru signature failure.
0x07A7 Drive removed, seen by either SP, acknowledged by both SPs completes.
0x07A8 Enclosure added.
0x2000 Application Starting Up
0x2002 Response Test Request
0x2003 SP busy, couldn't respond to at least one Informational event on the SP
0x2004 Test Event
0x2005 Event Monitor has encountered the following event, which could not be properly processed. Internal information only. No customer action required.
0x2006 Able to read events from this Windows log.
0x2200 Communication now successful with host
0x2201 Initial contact with host failed
0x2500 Storage system has no faults
0x2700 Path to an array is up
0x4000 The specified user is not logged in.
0x40000000 A MP for Flare was handled entirely in pre-hook of Redirector but completed w/success. This is converted to S_OK by stack proc's pre-hook error handler.
0x40000001 The MessageDispatcher is entering/exiting. Informational message. If there is a real error, it should be reported elsewhere.
0x40000002 SP time has been changed in response to a command to do so.
0x40000003 Private LUN attribute not applicable/changeable
0x7111000F The Local SP died, and is being resurrected.
0x71120002 DLU Driver Entry() has been called.
0x71120003 DLU Driver Entry has returned.
0x71120004 User DLU Driver has been unloaded.
0x71130002 UDLS Driver Entry() has been called.
0x71130003 UDLS Driver Entry has returned.
0x71130004 UDLS has been unloaded.
0x71150002 PSM Driver Entry() has been called.
0x71150003 PSM Driver Entry() has returned.
0x71150004 PSM has been unloaded.
0x71150005 The PSM default container has been read and processed.
0x71150006 There are no more Secondary LUs on the Persistent Container List.
0x7115000B The IO to Flare from the PSM driver failed and it could not reach the PSM LU.
0x71160000 The DiskTarg driver is starting.
0x71160001 The DiskTarg driver is unloading.
0x71170000 The ScsiTarg driver is starting.
0x71170001 The ScsiTarg driver is unloading.
0x71170002 ScsiTarg claimed a Port (for FE or CMI).
0x71170003 DiskTarg or CMIscd successfully registered with ScsiTarg.
0x71170004 DiskTarg or CMIscd activation with ScsiTarg succeeded.
0x71170005 DiskTarg or CMIscd deactivation and de-registration with ScsiTarg succeeded.
0x71170006 WWN is being changed for a host port.
0x71170007 During admin configuration change, peer SP died.
0x71170008 A Fibre Channel connection has become inactive.
0x71170009 A Fibre Channel connection has become active.
0x7117000A During admin configuration change, peer SP was unable to reply to primary SP over the CMI channel. It is likely the primary SP crashed and is rebooting.
0x7117000B A CLARiiON array has logged-in to a non-MirrorView Fibre Channel port. It is likely that the physical connection between the two arrays was not intended.
0x71240015 UnitState change for disk <number> (<previous state code> <current state code>) <previous state> to <current state>.
0x71240016 Unit State: <unit state> P=<primary disk state> (<primary disk state code>) S=<secondary disk state> (<secondary disk state code>)
0x71240017 Stopping retries on disk <disk number> (<disk state code>).
0x71240018 Remap on disk <number> LBA <lba>.
0x71240019 NtMirror driver attempting login on disk <number> (<attempt count>).
0x7124001A NtMirror driver could not login disk <number> (<attempt count>) - declaring disk removed.
0x7124001B Rebuild terminated for disk <number> (LBA <lba>)
0x7124001C Can't access the SMBUS driver.
0x7124001D Can't read the WWN seed from the SMBUS driver.
0x7124001E The WWN seed read from the mid-plane resume PROM is invalid.
0x71270006 Text is of the form Bus N Disk M status: The data aread contains sense data froma back end disk drive.
0x71270794 Enclosure <number>, Cabling is connected to BE Loop.
0x71270795 Attempt to mark unit as cache clean has failed with an error <error>. If the unit fails to assign then have your service provider clear clean/dirty flag of the unit.
0x7127079A Attempt to clear cache dirty unit %x has failed. The peer SP has valid data.
0x71058184 Allocating the write intent log for the mirror being created failed
0x71058185 Allocating the write intent for the mirror being promoted failed
0x71058186 Automatic fracturing of the image to enable setting the write intent use on failed. Manually fracture the secondary and then set the write intent log usage.
0x71058187 Maximum mirrors already allocated on the system
0x71058188 Maximum number of mirrors on the system
0x71058189 Mirror lock error, bucket number out of range
0x7105818A Mirror lock error, unexpected status from insert bucket
0x7105818B Mirror not found when attempting to acquire bucket lock
0x7105818C Image not found when attempting to acquire bucket lock
0x7105818D Mirror lock error, mirror state no memory
0x7105818E K10 specified already holds a secondary image
0x7105818F Invalid buffer size during get of compatibility mode
0x71058190 Invalid revision ID udring get of compatibility mode
0x71058191 Invalid revision ID during setting of compatibility mode
0x71058192 Invalid buffer size during setting of compatibility mode
0x71058193 Invalid revision ID during setting of compatibility mode
0x71058194 Invalid revision ID or buffer size during setting of compatibility mode
0x71058195 Unable to send to peer during setting of compatibility mode
0x71058196 Something failed during admin operation. Driver will enter degraded mode. Reboot the SP.
0x71058197 Internal MirrorView failure during adding of mirror
0x71058198 Failure to set WIL due to using same name for SPA and SPB
0x71058199 Unable to deallocate WIL since in use
0x7105819A An error occurred while trying to send an update notification to the peer SP. Incorrect revision of software installed on one SP.
0x7105819B Communication with the peer SP failed. Check the status code printed in eventlog to determine cause of communication failure.
0x7105819D Failed to validate a request received from a remote K10. One of the SPs has wrong software revision installed.
0x7105819E
Promoting a secondary image was allowed, but recreating the secondary images failed due to two incompatible admin operations being performed at the same time. Its possible when cross mirroring to get into a deadlock situation if you are doing promotion or add / delete secondary operations at the same time. To prevent this we check current operations and do not add the secondary to a promoted image to prevent the deadlock.
0x7105819F The user has attempted to set mirror's quiesce threshold value less than 10 seconds.
0x71058524 Error during synchronization, mirror device not ready
0x71058525 Unable to allocate the write intent memory
0x71058526 Mirror failed to allocate the write intent memory
0x71058527 Unable to assign ownership of all mirrors, not enough memory
0x71058528 Unable to quiesce the MirrorView driver within three minutes
0x71058529 Unable to add secondary image
0x7105852A Unable to assign ownership of all mirrors, not enough memory
0x7105852B Unable to verify the remote array version during add secondary operation. Check connectivity between the arrays.
0x7105852C The Write Intent Log is faulted.
0x7105852D Invalid slave license
0x7105852E Invalid slave license. System will panic and should come back up and correct situation automatically.
0x7105852F Unable to initialize the Distributed Lock. System will panic and should come back up and correct situation automatically.
0x71058530 Unable to open the Distributed Lock. System will panic and should come back up and correct situation automatically.
0x71058531 Unable to acquire semaphore. System will panic and should come back up and correct situation automatically.
0x71058532 Slave license is invalid. System will panic and should come back up and correct situation automatically.
0x71058533 Slave license is invalid. System will panic and should come back up and correct situation automatically.
0x71058534 An IOCTL for trespassing a lun failed. System will panic and should come back up and correct situation automatically.
0x71058535 Synchronization of a fractured slave image failed due to memory unavailability. System will panic and should come back up and correct situation automatically.
0x71058536 Allocating memory for a RM_WRITE_REQUEST structure failed. System will panic and should come back up and correct situation automatically
0x71058537 An error occurred while trying to compute the percentage completed of a sync operation. System will panic and should come back up and correct situation automatically
0x71058538 Value used to calculate extent bad. SP will reboot and correct the problem.
0x71058539 Loading of the Remote Mirror driver failed.
0x7105853A Call to flare to get disk geometry timed out after 3 minutes. SP will reboot and should fix problem.
0x7105853C Unable to find the specified consumed device while walking through the list of consumables.
0x7105853D MirrorView was unable to read from a disk block and is adjusting the synchronization accordingly to proceed.
0x7105853E No Memory for Mirror %2 for Deleted Watch List.
0x71058541 Unknown error or status code received, status = %.
0x71058542 An IRP is hung or lost on the secondary.
0x71058544 Two Mirrors attempted to use the same slot in WIL. Turn off all WIL usage by mirrors and then turn usage of WIL by mirrors back on and reboot the SPs.
0x71058545 The WIL LUs are not available. Verify the LUs aren't faulted and then reboot the SPs. If the problem persists, then turn off all use of the WIL and then re-enable the WIL for the mirrors.
0x71058546 The WIL LUs are not available. Verify the LUs aren't faulted and then reboot the SPs. If the problem persists, then turn off all use of the WIL and then re-enable the WIL for the mirrors.
0x71058547 MirrorView encountered an IRP which was cancelled more than once
0x71058548 MirrorView could not locate the mirror in question to perform an internal operation
0x7105854C MirrorView was unable to find an image for a mirror with arrested IO, after the mirror was trespassed. We shouldn’t hit this case unless something is really wrong! Contact customer support if problem persists.
0x7105854D MirrorView was unable to pause I/O within certain time frame. Contact customer support if problem persists.
0x71058600 Mirroring driver load failed
0x71058601 Insufficient memory available to load driver
0x71058602 Loading of the Remote Mirror driver failed.
0x71058603 Invalid Remote Mirror transport command. SP will reboot and should correct the issue.
0x71058700 Attempt to open a CMI conduit that's already open
0x71058701 Unexpected failure attempting to close a CMI conduit
0x71058702 Unexpected failure attempting to transmit data down a CMI conduit
0x71058703 Unexpected failure attempting to release received message resources
0x71058704 Invalid CMI buffer size detected
0x71058705 Unexpected CMI error status on transmitting CMI message
0x71058706 Unexpected failure on the conduit closed callback path
0x71058707 Received a response before the transport manager was even initialized
0x71058708 Attempted to release message resources before the transport manager was even initialized
0x7105870F Insufficient memory to allocate transport extension data structure
0x71058710 Could not access the CMI device object
0x71058711 Insufficient memory to allow command delivery.
0x71058712 Command to another SP timed out
0x71058713 Driver is degraded so no response send
0x71058714 Allocating memory for a RM_WRITE_REQUEST structure failed. System will panic and should come back up and correct situation automatically
0x71058800
Promoting a secondary image was disallowed because 2 promote operations were proceeding at the same time in a manner that could result in a system panic.Introduced in Chameleon 2 Release 2, X1, and Longbow 5.
0x71058900 Buffer passed to admin code is of invalid size when creating Consistency Group.
0x71058901 The revision ID is invalid when creating Consistency Group.
0x71058902 The Consistency group already exists with the given name.
0x71058903 The Consistency group attributed were in a bad format.
0x71058904 The Consistency group attributes are too long.
0x71058905 The Consistency Group name is invalid.
0x71058906 The Consistency Group type is unknown to Clutch.
0x71058907 The Clutch error code is unknown.
0x71058908 Buffer passed to admin code is of invalid size when destroying Consistency Group.
0x71058909 The revision ID is invalid when destroying Consistency Group.
0x7105890A The Consistency group could not be found. The Cg Id needs to be checked.
0x7105890B Buffer passed to admin code is of invalid size when getting Consistency Group properties.
0x7105890C The revision ID is invalid when getting Consistency Group properties.
0x7105890D Buffer passed to admin code is of invalid size when setting Consistency Group properties.
0x7105890E The revision ID is invalid when setting Consistency Group properties.
0x7105893E MirrorView Consistency Group Promote failed due to an unknown image.
0x7105893F There is nothing to promote in the Consistency Group.
0x71058940 A Consistency Group promotion cannot be performed on a group with missing members.
0x71058941 Consistency Group Promote failed. Secondary is not local to this array.
0x71058942 The Consistency Group cannot be promoted because one or more mirrors are missing from the group.
0x71058943 Consistency Group is in an invalid state for Consistency Group synchronization.
0x71058944 Consistency Group %2 is in an invalid group state %3 for Consistency Group synchronization.
0x71058945 The Consistency Group is in an invalid group state for Consistency Group admin fracture.
0x71058946 Consistency Group Promote failed due to a group Promote already running for the Consistency Group.
0x71058947 Consistency Group command cannot be executed at this time. Try again later.
0x71058948 Consistency Group Sync failed due to a group Sync already running for the Consistency Group.
0x71058949 Returned response is of unexpected length or different version number.
0x7105894A Group Create and Add request to the secondary array failed. Check the connectivity and status for the secondary array, including its software version.
0x7105894B Returned response is of unexpected length or different version number.
0x7105894C Remove member and destroy group request to the secondary array failed. Check the connectivity and status for the secondary array.
0x7105894D Returned response is of unexpected length or different version number when adding member.
0x7105894E Add Group Member request to the secondary array failed. Check the connectivity and status for the secondary array.
0x7105894F Returned response is of unexpected length or different version number when removing member.
0x71058950 Remove group member request to the secondary array failed. Check the connectivity and status for the secondary array.
0x71058951 The Consistency group already exists with the given name on the remote array.
0x71058952 The Consistency group attributed were in a bad format on the remote array.
0x71058953 The Consistency group attributes are too long on the remote array.
0x71058954 The Consistency group name is invalid on the remote array.
0x71058955 The Consistency group type is unknown to Clutch on the remote array.
0x71058956 The Clutch error code is unknown on the remote array.
0x71058957 The remote array returned an error on Consistency Group creation.
0x71058958 Consistency Group Promotion failed because promotion would cause group to be out-of-sync.
0x71058959 Consistency Group Operation failed due to group not being initialized.
0x7105895A Consistency Group Operation failed due to group not being initialized on the remote system.
0x7105895B Consistency Group operations not allowed due to group initialization failure. Rebooting the SP may correct the problem.
0x7105895C Consistency Groups operation failed due to MirrorView being degraded on remote system.
0x7105895D Consistency Groups operation failed due to remote group group not found on remote system.
0x7105895E Consistency Groups operation failed due to group not found.
0x7105895F Consistency Groups operation failed due to member not found.
0x71058960 Consistency Groups operation failed. Local member count does not match remote member coung.
0x71058961 A member cannot be removed from a group with locality remote.
0x71058962 A matching image could not be found.
0x71058963 Admin operation on mirror in a Consistency Group is not allowed.
0x71058964 CG addmember fails when user tries to add an image to CG in invalid state.
0x71058965 CG addmember fails when user tries to an image to CG in invalid condition.
0x71058966 Consistency Group addmember fails when user tries to an image to group that is inactive.
0x71058967 Peer SP already has a Consistency Group with this group ID.
0x71058968 Peer SP already has a Consistency Group with this group Name.
0x71058969 Admin Fracture a secondary Consistency Group on the Remote Array is not allowed.
0x7105896A
Adding secondary for %2 during promotion failed due to Consistency Group membership on the remote system. Group configuration needs to be checked as there appears to be membership mismatch between systems.
0x7105896B Remote system for Consistency Group %2 attempted a promote for mirror %3. The secondary for this mirror may now be invalid on this
system. Check group configuration on both systems for membership mismatch.
0x7105896C Cannot remove the secondary image for mirror %2 because it belongs to a consistency group. Check group configuration on both systems for membership mismatch.
0x7105896D Consistency Group add member failed since local and remote groups do not have same membership count.
0x7105896E Consistency Group %2 add member failed because the local member count does not match the remote member count. Check group membership on both the local and remote systems.
0x7105896F Cannot promote Consistency Group %2 because not all images are in-sync or consistent. Promotion is not allowed if an image is in a syncing or out-of-sync state.
0x71058970 Cannot promote Consistency Group %2 because doing so will lead to the group being out-of-sync. Force out-of-sync promote may be chosen to promote the group.
0x71058971 Cannot synchronize Consistency Group %2 because not all secondary image conditions are admin fractured or waiting on admin. Check connectivity and fracture state for each mirror.
0x71058972 It is not allowed to add a secondary image to a mirror that already has one secondary image and is part of a CG.
0x71058973 It is not allowed to destroy an image that is part of a Consistency Group.
0x71058974 It is not allowed to remove a secondary image from a mirror in a CG.
0x71058975 It is not allowed to deactivate or activate a mirror in a Consistency Group. But the minimum images required, quiesce threshold, and write log usage is allowed to be changed for a mirror in a Consistency Group.
0x71058976 It is not allowed to change the recovery policy to auto for a mirror in a Consistency Group.
0x71058977 If the secondary itself is in a Consistency Group, promote of this indivual secondary image is not allowed.
0x71058978 It is not allowed to fracture a mirror that is in a Consistency Group individually.
0x71058979 It is not allowed to individually synchronize a mirror that is in a Consistency Group.
0x7105897A CG addmember failed due to the CG condition is INVALID.
0x7105897B CG addmember failed due to the CG condition is ADMIN_FRAC.
0x7105897C CG addmember failed due to the CG condition is SYS_FRAC.
0x7105897D CG addmember failed due to the CG condition is WAIT_ON_ADMIN.
0x7105897E CG addmember failed due to the CG condition is INACTIVE.
0x7105897F A consistency group synchronize operation is not allowed when the group state is Scrambled.
0x71058980 A consistency group synchronize operation is not allowed when the group state is Incomplete.
0x71058981 A consistency group synchronize operation is not allowed when the group state is Local Only.
0x71058982 Consistency Group %2 cannot be promoted because one or more mirrors are missing from the group.
0x71058983 Consistency Group %2 is in an invalid group state %3 for group admin fracture.
0x71058984 Remote Create Consistency Group and Add Member Transport Error = %2.
0x71058985 Remote Destroy Consistency Group Remove Member Transport Error = %2.
0x71058988 MirrorView requires the installed package be committed in order to create a Consistency Group.
0x71058989 MirrorView requires the installed package be committed in order to add a Consistency Group member.
0x7105898A A member cannot be removed from a secondary group without the override flag.
0x7105898B Consistency group fracture operation fails because the specified group has no members.
0x7105898C MirrorView Consistency Group Sync failed due to the remote group being incomplete.
0x7105898D
Consistency Group %2 could not be synchronized because the remote group is in an incomplete state. The Consistency Group configuration needs to be checked on both the local and remote system for missing images or mirrors.
0x7105898E MirrorView Consistency Group Sync failed due to promotion in progress on the remote system.
0x7105898F Consistency Group %2 could not be synchronized because the remote system is in the process of promoting the group.
0x71058990 Promotion of Consistency Group %2 failed due to insufficient memory.
0x71058996 Consistency Groups operation failed because group on remote array is local.
0x71058997 Consistency Groups operation failed because mirror image on remote array is not a group member.
0x71058998 Consistency Groups operation failed because mirror image on remote array is not a member of this group.
0x7105899A Consistency Groups operation failed because there's not enough memory available to build the peer update message. MirrorView Consistency Group will go degraded due to this failure %2.
0x7105899B Consistency Groups operation failed because there's not enough memory available to build the remote update message. MirrorView Consistency Group will go degraded due to this failure %2.
0x7105899C Consistency Groups operation failed because there's not enough memory available to build the clutch attributes buffer. MirrorView Consistency Group will go degraded due to this failure %2.
0X7105899D Consistency Groups operation failed because the secondary array of mirror being added doesn't match other secondary arrays in group.
0x7105899E The Consistency Group is already administratively fractured.
0x7105899F The Consistency Group Name cannot be changed while the secondary (remote) system is not reachable. When the MirrorView connection is restored, retry the name change.
0x710589A0 Consistency Groups failed to create group %2 with status %3
0x710589A1 Consistency groups failed to destroy group %2 with status %3
0x710589A2 Consistency groups failed to add mirror %2 to group %3:%4 with status %5
0x710589A3 Consistency Groups has failed to remove member %2 from the group %3:%4 with status %5
0x71528009 Message received on this SP was not serviced due to message protocol mismatch. Upgrade both the primary and secondary arrays to the same software revisions
0x7152800C An operation on the secondary or peer SP took too long to complete and the SP was rebooted to cause a dump
0x71528015 SnapView returned an error on an attempt to query snap session status
0x71528016 SANcopy returned an error on an status query
0x71528017 Failed to start an incremental update for the group. Look at the status errorcode to determine the cause of failure
0x7152801F Mirrorview/A failed to trespass during an incremental udpate. Look at the status errorcode to determine the actual cause of the failure
0x71528031 The group specified to be promoted will cause the existing primary group to become out-of-sync. Promote locally or promote out of sync needs to be selected
0x71528033 Group state is not valid for promote to proceed
0x71528034 Cannot promote a scrambled group. The user will need to remove members from group to restore group to normal state first
0x71528035 Caught an exception. Look at the status errorcode to determine the actual cause of the exception
0x71528037
MirrorView/A, reboot because the system was unable to clean up memory after failure to write to PSM during mirror creation. The system should automatically clean up on reboot. Contact customer support if problem persists
0x71528038 MirrorView/A Error contacting Driver, unable to clean up XLUs during create
0x71528039 Unused
0x7152803A MirrorView/A, unable to locate mirror to destroy. Check input data
0x7152803B MirrorView/A, unable to destroy a mirror with secondary images
0x71528045 The maximum number of FAR array connections has been reached
0x7152804C MirrorView/A could not find a valid initiator record to associate with a storage group. Verify MirrorView connectivity is enabled between the arrays
0x7152804E Unused
0x71528056 Mirror ID not found during request to add secondary image. Primary image may need to be destroyed and recreated to proceed
0x71528057 The mirror specified already has the maximum number of secondary images
0x71528058
MirrorView/A, The mirror specified doesn't not have any open image slots. Destroy and recreate the primary image and attempt the add secondary operation again. If this doesn't correct the issue then the array needs to have each SP rebooted, one at a time
0x71528059 Invalid number of update conditions specified during add secondary. Verify update data was provided for the new image
0x7152805A Invalid number of update descriptions provided during add secondary. Verify the update data was provided for the new image
0x7152805B Invalid update tag or period provided during add secondary. Verify the update data was provided for the new image
0x7152805C Invalid update tag for sync rate data. Verify the sync rate data was provided for the new image
0x7152805D Invalid update tag for latency setting. Verify the update data was provided for the new image
0x7152806D Invalid remote array response, destroy secondary image failed. Verify the mirrorview connection between the arrays and try again
0x7152806E
Invalid Peer response, failed to retry admin command on peer. One of the SPs in the array is either down or unable to handle the operation. Either correct the SP issue or trespass the LU associated to the mirror and retry the administrative command again
0x7152806F Add secondary failed, remote array couldn't locate necessary data. The primary image may need to be destroyed and recreated to correct the issue
Verify the mirrorview connection between the arrays is working properly
0x71528071 Add secondary failed, the operation failed on the remote array. Check that replication cache is set up on the remote array and all installed software on the remote array is working properly
0x71528072 Mirror ID not found on the remote array during request to remove secondary image. Verify secondary image exists on remote array
0x71528073 The image specified to be removed wasn't found
0x71528074 The image specified to be removed wasn't found
0x71528075
MirrorView/A, the image to be removed has an invalid image condition for removal. You may need to fracture the secondary image and attempt the operation again. If the image is already fractured, it may have been in transition when the operation was recieved, so try the removal operation again
0x71528076 The image specified wasn't found on the remote array. Verify the image exists on the remote array and image data is accurate in display.
0x71528077 The image specified wasn't found on the remote array. Verify image information is accurate, you may need to refresh display or query the remote array for accurate data
0x71528078 During remove image freeing replication cache use failed. When the system reboots it should clean up the issue
0x71528079 The image specified for promotion wasn't found. Refresh the image data or verify the command was send to the correct array
0x7152807A The mirror specified for promotion wasn't found. Refresh the mirror data or verify the command was send to the correct array
0x7152807B The image specified to be promoted was in an invalid condition for promotion. Promotion may only be performed on a mirror image which is consistent or in-sync
0x7152807C The image specified to be promoted was unable to contact other images in the mirror. Restore connection to remote arrays or use of a Local Promote or Promote Out-of-sync operation will be required to continue
0x7152807D The image specified to be promoted will cause the existing primary to become out-of-sync
0x7152807E MirrorView/A, The remove of the remote image occured, but destruction of some internal data failed. The internal data structures will be removed the next time the SP reboots
0x7152807F The remote promote operation failed due to a conflicting operation in progress. Retry the operation when no other admin operations are in progress
0x71528080 During a promote operation, an invalid type of promote was specified
0x71528081 The image condition was invalid for a normal promote. The image cannot be a Master image and the image must be either in-sync or consistent
0x71528082 The image condition was invalid for a out-of-sync promote. The image cannot be a Master image and the image must be either in-sync or consistent
0x71528083 The image to be removed wasn't found. Refresh the mirror data on the array and retry the operation
0x71528084 The image condition was invalid for a local promote. The image cannot be a Master image and the image must be either in-sync or consistent
0x71528086 The check remote version received an invalid response. Verify the mirrorview connection to the remote array is operating properly
0x71528087 The check remote version couldn't find the image specified. Verify the mirrorview connection to the remote array is operating properly
0x71528088 The promote image couldn't find the image specified. Refresh the image information or attempt a Local Promote Operation
0x7152808A The promote operation received an invalid response from the remote array. Verify the installed software on both arrays are compatable versions
0x7152808B The promote operation couldn't find an open slot for secondary <secondary>. The data on the remote array needs to be reloaded in memory. Reboot the remote array one SP at a time
0x7152808C The promote operation failed for the remote image. The remote image couldn't be added to the promoted mirror. Verify full mirrorview connectivity with the remote array
0x7152808D Unable to locate far group in the database. Refresh the user data and retry the operation
0x7152808E Unable to create far group in the database. Make sure a group with the same name doesn't already exist
0x7152808F Unable to destroy far group from the database. Refresh the user information and retry the operation
0x71528090 Unable to add member to group in the database. Refresh the user information and retry the operation
0x71528091 Unable to add member to group in the database. Refresh the user information and retry the operation
0x71528092 A required service on the array didn't start and group operations are unavailable. Reboot the SP and if the problem persists contact customer support
0x71528093 The group name you are attempting to create has invalid characters. Rename the group and try again
0x71528094 The maximum number of groups on the array currently exists so the operaton failed
0x71528095 A service on the array required for group operations has failed. The SP will need to be rebooted, if the problem persists contact customer support
0x71528096 The destroy group operation failed since the group still has members
0x71528097 The group to be destroyed wasn't found. Refresh the user information and retry the operation
0x71528098 Mirror specified is already a member of the group
0x71528099 The specified mirror to be added wasn't found. Refresh the user information and retry the operation
0x7152809A Unable to find the group when you attempted to add a member. The group may not have been created or may have been destroyed
0x7152809B The group already has the maximum number of members
0x7152809C The add member to group operation failed. The image you attempted to add must be the same role as the other members in the group (primary / secondary)
0x7152809D Mirror to be added to group has too many members
0x7152809E The mirror specified is already a member of a group
0x7152809F The add member operation failed since the group is currently scrambled
0x715280A0 The remove member operation to a group failed since the group wasn't found. Refresh the user information and retry the operation
0x715280A1 The image specified to be removed from the group wasn't a member of the group. Refresh the user information and retry the operation
0x715280A2 The fracture command was send to the wrong array for the group
0x715280A3 The request operation data was incorrectly formated. Verify the data in the request
0x715280A4 The request operation data was incorrectly formated. Verify the data in the request
0x715280A5 The TLD didn't have a group property tag. The request operation data was incorrectly formated. Verify the data in the request
0x715280A6 The TLD didn't have a group id tag. The request operation data was incorrectly formated. Verify the data in the request
0x715280A7 The TLD didn't have a group override tag. The request operation data was incorrectly formated. Verify the data in the request
0x715280A8 The TLD didn't have a group property type tag. The request operation data was incorrectly formated. Verify the data in the request
0x715280A9 The TLD didn't have a local luid tag. The request operation data was incorrectly formated. Verify the data in the request
0x715280AA The TLD didn't have a far group enum list tag. The request operation data was incorrectly formated. Verify the data in the request
0x715280AB The TLD didn't have a group update data tag. The request operation data was incorrectly formated. Verify the data in the request
0x715280AC The TLD didn't have a group update description list tag. The request operation data was incorrectly formated. Verify the data in the request
and if the problem continues contact customer support
0x715280C4 The clutch driver failed and the group properties couldn't be returned. Reboot the SP and if the problem continues contact customer support
0x715280C5 The clutch driver failed to set the group properties. Reboot the SP and if the problem continues contact customer support
0x715280C6 The TLD didn't have a create group request tag
0x715280C7 The TLD didn't have a create group response tag. The request operation data was incorrectly formated. Verify the data in the request
0x715280C8 The TLD didn't have a destroy group tag. The request operation data was incorrectly formated. Verify the data in the request
0x715280C9 The TLD didn't have a destroy group response tag. The request operation data was incorrectly formated. Verify the data in the request
0x715280CA The TLD didn't have a add member group request tag. The request operation data was incorrectly formated. Verify the data in the request
0x715280CB The TLD didn't have a add member group response tag. The request operation data was incorrectly formated. Verify the data in the request
0x715280CC The TLD didn't have a remove member group request tag. The request operation data was incorrectly formated. Verify the data in the request
0x715280CD The TLD didn't have a remove member group response tag. The request operation data was incorrectly formated. Verify the data in the request
0x715280CE The TLD didn't have a fracture group request tag. The request operation data was incorrectly formated. Verify the data in the request
0x715280CF The TLD didn't have a fracture group response tag. The request operation data was incorrectly formated. Verify the data in the request
0x715280D0 The TLD didn't have a sync group request tag. The request operation data was incorrectly formated. Verify the data in the request
0x715280D1 The TLD didn't have a sync group response tag. The request operation data was incorrectly formated. Verify the data in the request
0x715280D2 The TLD didn't have a promote group request tag. The request operation data was incorrectly formated. Verify the data in the request
0x715280D3 The TLD didn't have a promote group response tag. The request operation data was incorrectly formated. Verify the data in the request
0x715280D4 The TLD didn't have a get properties group request tag. The request operation data was incorrectly formated. Verify the data in the request
0x715280D5 The TLD didn't have a get properties group response tag. The request operation data was incorrectly formated. Verify the data in the request
0x715280D6 The TLD didn't have a set properties group request tag. The request operation data was incorrectly formated. Verify the data in the request
0x715280D7 The TLD didn't have a set properties group response tag. The request operation data was incorrectly formated. Verify the data in the request
0x715280D8 Name specified <name> is not unique on the array
0x715280D9 Name specified <name> is not unique on the remote array
0x715280DA Get Mirror Properties failed, Mirror ID specified <ID> not found
0x715280DB Get Image Properties failed, Mirror ID specified <ID> not found
0x715280DC Get Image Properties failed, Mirror ID specified <ID> not found
0x715280E4 FAR could not access the group shared memory. Reboot the SP
0x715280E5 The group to be promoted couldn't be found. Verify the group id and array location is correct
0x715280E6 The group to be promoted was in an invalid state
0x715280E7 The deadlock prevent flag was set, so the group promote failed. Try again in a few minutes
0x715280E8 The group promote failed since the command was send to an array with primary images
0x715280E9 The mirror Id specified to set mirror properties wasn't found
0x715280EA The mirror Id specified to set image properties wasn't found
0x715280EB The mirror image specified to set image properties wasn't found
0x715280EC The mirror image specified to set image properties was NULL
0x715280ED The set image role failed since we couldn't contact the driver
0x715280EE The get device info failed since we couldn't contact the driver
0x715280EF MirrorView/A could not allocate memory needed to process the Enum Shadow LU command.
0x715280F2 The add image operation failed since we couldnt find the mirror specified. Refrehs user data
0x715280F3 The remove image operation failed due to incorrect rev ID send to peer. Verify both SPs are working properly
0x715280F4 The remove image operation failed due to incorrect rev ID received from peer. Verify both SPs are working properly
0x715280F5 Invalid Protective sessions status while promoting group <group>. Attempt to fracture and resynch the group if possible. Otherwise remove group members and retry the promote on the individual mirrors
0x715280F6 Invalid response while checking status of remote group <group>. Verify all arrays are running the same revision of software
0x715280F7 Invalid response received while trying to create ISC session from peer. Check if peer is alive or not.
0x715280FB Unable to locate image <image> of mirror <mirror> of group <group>
0x715280FC Unable to locate image <image> of mirror <mirror> of group <group>
0x715280FD Unable to contact remote FarMon during group promote
0x71528105 MirrorView/A - the secondary LU specified for adding a secondary
0x7152811A MirrorView/A - A member cannot be added to a group if the command is recieved on a secondary array
0x7152811B Incremental update has completed successfully. Mirrorview/A is unable to communicate with the secondary array to stop the protective snap session. Check the mirrorview connection between the arrays
0x7152811C Incremental update has completed successfully. Mirrorview/A is unable to destroy protective snap session after the copy has completed. Look at the status errocode to determine the actual cause of the error
0x7152811D Unable to start an incremental update. Mirrorview/A is unable to communicate with the secondary array to create protective snap session
0x7152811E Unable to create protective snap session on the secondary array. Check to see if enough cache has been allocated on the secondary array. Look at the status error code to determine actual cause of the error
0x7152811F SANCopy session has failed for the mirror. Look at the status error code to determine actual cause of error
0x71528120 SANCopy session has failed for the mirror. As a result the group which this mirror is a part of will be admin fractured. Look at the status error code to determine to actual cause of error
0x71528121 SANCopy session for the mirror has failed because it has detected a link failure. Look at the status error code for more details
0x71528122 SANCopy session for the mirror has failed because it has detected a link failure. As result the group which the mirror is a part of will be system fractured. Look at the status error code for more details
0x71528123 SANCopy returned an error on an attempt to mark the session for the mirror. Look at the status error code to determine the actual cause of error
0x71528124 SANCopy returned an error on an attempt to start the session for the mirror. Look at the status error code to determine the actual cause of error
0x71528125 Incremental update for the group has completed successfully. Mirrorview/A is unable to communicate with the secondary array to stop the protective snap sessions for the group
0x71528126
Incremental update has completed successfully. Mirrorview/A is unable to destroy protective snap sessions after the copy has completed for the group. Look at the status errocode to determine the actual cause of the error
0x71528127 Unable to start an incremental update. Mirrorview/A is unable to communicate with the secondary array to create protective snap session
0x71528128 Unable to create protective snap sessions for the group on the secondary array. Check to see if enough cache has been allocated on the secondary array. Look at the status error code to determine actual cause of the error
0x71528129 SANCopy returned an error on an attempt to consistently mark sessions for the group. Look at the status error code to determine the actual cause of error
0x7152812A SANCopy returned an error on an attempt to start the session for the group. Look at the status error code to determine the actual cause of error
0x71528130 MirrorView/A - incorrect revision Id in promote package sent to peer SP
0x71528131 MirrorView/A - mirror not found to promote
0x71528132 MirrorView/A - mirror image not found to promote
0x71528133 MirrorView/A - mirror during promote operation not found
0x71528139 MirrorView/A - Clutch returned an unknown error during a group operation
0x7152813A MirrorView/A - The group on the remote array could not be created due to invalid properties
0x7152813B MirrorView/A - The group on the remote array could not be created because the group name is illegal
0x7152813C MirrorView/A - The group on the remote array could not be created because the number of groups that can be created on an array has been exceeded
0x7152813D MirrorView/A - An attempt was made to create a group with the same name as an existing group on the remote array
0x7152813E MirrorView/A - Creating a group on the remote array failed because Clutch did not understand the group type set by far on the remote array
0x7152813F MirrorView/A - Creating a group on the remote array failed because clutch returned an error.
0x71528140 MirrorView/A - Creating a group on the remote array failed because returned an unknown error.
0x71528141 MirrorView/A - The remote group could not be created as part of the addmember operation
0x71528144 An attempt was made to system fracture the group. Farconfig failed to system fracture the group. Look at the status errorcode to determine the actual cause
0x71528145 An attempt was made to admin fracture the group. Farconfig failed to admin fracture the group. Look at the status errorcode to determine the actual cause
0x71528146 An attempt was made to admin fracture the image. Farconfig failed to admin fracture image. Look at the status errorcode to determine the actual cause
0x71528147 An attempt was made to system fracture the image. Farconfig failed to system fracture image. Look at the status errorcode to determine the actual cause
An attempt was made to sync a system fractured image, since MirrorView/A detected that the link was up. But farconfig failed to sync the image. Look at the status errorcode to determine the actual cause of the error
0x71528149
An attempt was made to sync an the system fractured group. Since MirrorView/A detected that the link was up. Although farconfig failed to sync the image. Look at the status errorcode to determine the actual cause of the error
0x7152814A Mirrorview/A failed to trespass a mirror in a groupduring an incremental udpate. Look at the status errorcode to determine the actual cause of the failure
0x7152814B Group that is promoted is not a secondary group
0x7152814C MirrorView/A - the mirror specified to be promoted wasn't found. Refresh User data
0x7152814D MirrorView/A - the mirror specified to be promoted wasn't found. Refresh User data
0x71528164 MirrorView/A - the primary image location in the mirror wasn't found during add image. User may need to destroy and recreate the primary image
0x71528165 MirrorView/A - the add member to group failed, unable to locate mirror to add. Refresh User data
0x71528166 MirrorView/A - the remove member to group failed, unable to locate mirror to add. Refresh User data
0x71528167 MirrorView/A - the force destroy failed due to internal I/O in flight draining. I/O processing to secondary images has been aborted so try again
0x71528169 Mirrorview/A is unable to communicate with secondary array and trespass the destination LU for the mirror's secondary image while starting an incremental update
0x7152816A Mirrorview/A failed to trespass the destination LU for the mirror's secondary image while starting an incremental update. Look at the status errorcode to determine the actual cause of the error
0x7152816B
Mirrorview/A failed to communicate with the peer SP or the secondary array on an attempt to trespass the destination LU and start a copy for a member in the in the group. As a result of this error the group will be system fractured
0x71528173 Peer owns some of the group members and is not alive
0x71528174
MirrorView/A failed to modify the image property. Internally unable to find a required data structure necessary for the operation. Reboot the SP and if this doesn't fix the issue the image may need to be removed and re-added to the mirror
0x71528175 MirrorView/A failed to modify the image property. The image is in process of updating the secondary image. Wait until the update completes or fracture the image and then modify the properties
0x71528176 MirrorView/A failed to remove a secondary image. The mirror Id was null on the secondary This shouldn't ever happen and you may need to force destroy the primary and secondary image
0x71528177
MirrorView/A failed to remove a secondary image. The local image of the mirror is a primary image, so this command will fail. Most likely the local image was promoted while the connection to the old primary was down. Check the mirror Ids to diagnose and will probably need to force destroy the old primary image
0x7152817A Cannot remove a secondary image that is participating in a group
0x7152817B Cannot promote a secondary image that is participating in a group
0x7152817C Cannot force destroy a member participating in a group
SANCopy session for the mirror has terminated because of a reboot. As a result the mirror will be systemfractured. If the recovery policy for the mirror is set to auto then the mirror will be automatically synced. Look at the status error code for more details
0x7152817E
SANCopy session for the mirror has terminated because of a reboot. As a result the group which this mirror is a part of will be system fractured. If the recovery policy for the group is set to auto then the group will be automatically synced. Look at the status error code for more details
0x7152817F MirrorView/A, the admin command was not send to the array hosting the primary image of the mirror
0x71528180 Operation prohibited as MirrorView/A is in degraded mode
0x71528181 An unexpected error occurred while performing a transact operation, that is communicating with another sp. Look at the status errocode to determine the acutal cause of the error
0x71528182 An unexpected error occured while sending a response back to the originator SP. Look at the status errocode to determine the acutal cause of the error
0x71528183 Invalid peer response, create group on peer failed
0x71528184 Invalid peer response, addmember on peer failed
0x71528185 Invalid peer response, remove member on peer failed
0x71528186 Invalid peer response, commit on peer failed
0x71528187 Invalid remote response, add member failed on remote array
0x71528188 Invalid remote response, remove member failed on remote array
0x71528189
MirrorView/A, the mirror destroy operation failed since the mirror is rolling back. Until the mirror has completed the rollback the data on the LUN is in an invalid state. Once the rollback is complete the data will be returned back to the last known usable state and a destroy operation may proceed at that time
0x7152818A MirrorView/A, the maximum number of mirror images already exist on the mirror so the operation failed
0x7152818B Mirror update to PSM failed
0x7152818C MirrorView/A failed to unmark a session on attempting to system fracture the mirror. As a result the mirror will be admin fractured and MirrorView/A operations will be degraded
0x7152818D MirrorView/A is going to degraded mode. Check the event log prior to this event for errors and subsequent corrective actions. After taking any necessary corrective actions, reboot this SP
0x7152818E MirrorView/A failed to unmark a session after the session aborted for the mirror. As a result MirrorView/A operations will be degraded
0x7152818F MirrorView/A promote failed since the primary image is currently updating the secondary image. Fracture the secondary image and attempt
0x71528190 MirrorView/A promote failed since the primary image is currently rolling back. Wait for the rollback to complete and attempt the operation again
0x71528191 MirrorView/A reset of secondary image LU to allow I/O failed. Remove MirrorView/A from the LU device stack to clean up the problem
0x71528192 MirrorView/A primary image rolling back so promote operation on the image failed
0x71528193 MirrorView/A during a promote an update was running so the old primary was not converted as part of the promote operation
0x71528194 MirrorView/A during an admin operation an exception was caught. Check the eventlog on the array for indications of the problem and retry the command if possible
0x71528195 MirrorView/A during an admin operation an exception was caught. Check the eventlog on the array for indications of the problem and retry the command if possible
0x71528199 Group doesn't contain any members that can be promoted
0x7152819A
MirrorView/A, the force destroy operation on a primary image failed since an active update was in progress. Fracture the secondary image and then retry the operation. If fracturing the image isn't an option, then remove the MirrorView cables between the arrays until the mirror fractures and try again
0x7152819B The session for the mirror has failed because the primary array has run out of cache. As a result of this error, the mirror will be adminfractured. Add more cache LUN's on the primary array and retry a sync
0x7152819C The session for the mirror has failed because the secondary array has run out of cache. As a result of this error, the mirror will be adminfractured. Add more cache LUN's on the secondary array and retry a sync
0x7152819D
The session for the mirror has failed because the primary array has run out of cache. As a result of this error, the group which this mirror is a part of will be admin fractured. Add more cache LUN's on the primary array and retry the sync
0x7152819E
The session for the mirror has failed because the secondary array has run out of cache. As a result of this error, the group which this mirror is a part of will be admin fractured. Add more cache LUN's on the secondary array and retry the sync
0x715281A0 Unable to admin fracture the group member
0x715281A1 Unexpected member image condition of an admin fractured group
0x715281A2 Unable to system fracture the group member
0x715281A3 Unexpected member image condition of system fractured group
0x715281A4 MirrorView/A - During an enumeration of mirrors an exception was caught. Try the operation again and if the problem persists reboot the SP.
0x715281A5 MirrorView/A - An exception was caught while attempting to set image properties. Retry the operation and if unsuccessful you should reboot the SP to clean up the problem.
0x715281A6 MirrorView/A - The member to be removed was not found in the groups database.
0x715281A7 MirrorView/A - The member to be removed was not found in the groups database.
0x715281A8
MirrorView/A - The secondary image array ID could not be found in the mirror data. The member cannot be removed from the secondary, use force remove in order to remove the member from the local and remote arrays.
0x715281A9 MirrorView/A - The member could not be removed from the secondary, but the remove succeeded on the primary.
0x715281AA Peer's destroy group response is not valid.
0x715281AB MirrorView/A - An exception was caught while attempting to fracture an image. Retry the operation and if unsuccessful you should reboot the SP to clean up the problem.
0x715281AC MirrorView/A - An exception was caught while attempting to fracture an image. Retry the operation and if unsuccessful you should reboot the SP to clean up the problem.
0x715281AD Incremental session abort failed
0x71528200 The FAR Admin database version number is incorrect. The correct dll will need to be loaded to correct the problem
0x71528201 Unable to get device handle. Try operation again and if fails then reboot the SP
0x71528202 The TLD didn't have an a valid operation qualifier
0x71528203 The TLD didn't have an a valid destroy operation tag
0x71528204 The TLD didn't have an a valid FAR ID operation tag
0x71528205 The TLD didn't have an a valid FAR ID operation tag length
0x71528206 The TLD didn't have an a valid create operation tag
0x71528207 The TLD didn't have an a valid lu id for create operation
0x71528208 The TLD didn't have an a valid lu id for create operation
0x71528209 The TLD didn't have an a valid FAR name for create operation
0x7152820A The TLD didn't have an a valid FAR name for create operation
0x7152820B The TLD didn't have an a valid FAR description for create operation
0x7152820C The TLD didn't have an a valid FAR enum mirrors tag
0x7152820D The TLD didn't have a valid FAR enum type
0x7152820E The TLD didn't have a valid FAR enum type
0x7152820F The TLD didn't have a FAR add image tag
0x71528255 The TLD didn't have an a valid FAR Group ID operation tag length
0x71528256 The TLD didn't have an a valid FAR Group ID operation tag length
0x71528257 The TLD didn't have an a valid FAR Group ID operation tag length
0x71528258 The TLD didn't have an a valid FAR Group ID operation tag length
0x71528259 The TLD didn't have an a valid FAR ID operation tag
0x7152825A The TLD didn't have an a valid FAR ID operation tag length
0x7152825B The TLD didn't have an a valid FAR ID operation tag
0x7152825C The TLD didn't have an a valid FAR ID operation tag length
0x7152825D The TLD didn't have an a valid LU ID operation tag
0x7152825E The TLD didn't have an a valid LU ID operation tag length
0x7152825F The TLD didn't have an a valid LU ID operation tag
0x71528260 The TLD didn't have an a valid LU ID operation tag length
0x71528261 The fracture type specified (<type>) wasn't valid
0x71528262 The sync type specified (<type>) wasn't valid
0x71528263 The TLD didn't have an a valid FAR Group ID operation tag length
0x71528264 The TLD didn't have an a valid FAR Group ID operation tag length
0x71528265 The TLD didn't have an a valid FAR Group ID operation tag length
0x71528266 The tag for the group id to sync was not found
0x71528267 The tag for the group id to fracture was not found
0x71528268 The tag for the group id to promote was not found
0x71528269 The tag for the fracture condition was not found
0x7152826A The tag for the fracture condition is invalid
0x7152826F Only local promote is accepted on a group that is currently rollingback
0x71528270 The tag for the group over-ride flag was not found
0x71528271 The TLD didn't have an a valid FAR Group override tag length
0x71528272 The tag for the group over-ride flag was not found
0x71528273 The TLD didn't have an a valid FAR Group override tag length
0x71528274 The shadow LU that we were attempting destroy was associated with a mirror. Remove the mirror before attempting this operation
0x71528275 The add image operation failed due to an invalid update period specified ( > 4 weeks)
0x71528276 The set image operation failed due to an invalid update period specified ( > 4 weeks)
0x71528277 MirrorView/A - An exception was caught while attempting to fracture an image. Retry the operation and if unsuccessful you should reboot the SP to clean up the problem.
0x71528278 The group id tag is not found in the TLD sent to get properties of a group
0x7152831D Unable to find the image in the database
0x7152831E Invalid response from peer while updating mirrors
0x7152831F Invalid response from secondary while updating mirrors
0x71528320 Unable to find the mirror in the database during administrative synchronize operation
0x71528321 Current image condition doesn't allow sync request to proceed for this image. Make sure the image is not already synchronizing or system fractured.
0x71528322 Current group state doesn't allow the sync to proceed for this group. Make sure the group is not scrambled or in an invalid state.
0x71528323 Sync cannot proceed on this group as one of the members is not fractured.
0x71528324 Unable to start the sync as the session is still active
0x71528327 All the protective sessions exist on this array
0x71528328 None of the protective snap sessions exist on this array
0x71528329 Group members protective sessions are in scrambled existence
0x7152832E Unable to verify the status of protective session <session>
0x71528332 Invalid group state to proceed with sync
0x71528334 Group is not admin fractured for the sync to proceed
0x71528336 Failed to obtain protective session status
0x71528337 Fracture command must be issued from the primary sp
0x71528338 Sync command must be issued from primary sp
0x7152833B Sync cannot proceed as the image state is not consistent
0x7152833D Group fracture command is not issued from the primary array
0x7152833E Group synchronize command is not issued from the primary array
0x7152833F Group fracture command is not issued from the primary array
0x71528340 Group synchronize command is not issued from the primary array
0x71528342 The current group condition doesn't allow fracture to proceed. Make sure the group is not already admin fractured.
0x71528343 Sync cannot proceed as the group state is not consistent.
0x71528345 Fracturing individual group member is not allowed
0x71528346 Synchronization of individual group member is not allowed
0x71528347 Image fracture failed due to internal error
0x71528348 Unexpected member image condition at the end of group system fracture
0x71528349 Unexpected member image condition at the end of group admin fracture
0x7152834A Group member incremental session fracture failed
0x7152834B Unable to system fracture the group member
0x7152834C Unable to admin fracture the group member
0x7152834D Unexpected member image condition during group member auto sync
0x7152834E Unexpected member image condition during group member admin sync
0x71528351 Failed to activate member session <session> Check the last image error field for the failure
0x71528352 Failed to trespass group members remote LU <lun> Check if remote connection is up and running
0x71528353 Failed to sync group member on peer <peer> Check the last image error field for more info
0x71528354 Cannot synchronize a normal image. Either the image must have been fractured or the image must have manual update as it's update type for the sync request to proceed.
0x71528355 Cannot synchronize a group that is already syncing.
0x71528356 Cannot synchronize a normal group. Either the group must have been fractured or the group must have manual update as it's update type for the sync request to proceed.
0x71528357 Cannot synchronize an updating group.
0x71528358
MirrorView detected that the secondary image has gone bad because of which it is permanently fractured. This can happen if the incremental snap session stops because of faulted cache luns. The user won’t be able to perform any operations on this mirror or on the group if this mirror is part of a group. The permanently fractured image has to be removed and and added back for mirroring to continue for this mirror.
0x71528359 Permanently fracturing secondary image %1. Remove the image and add it back for the mirror to be operational again.
0x7152835A The user tried to synchronize an image that had been fractured permanently because of which sync operation cannot proceed.
0x7152835B The user tried to synchronize a group that has one or more members permanently fractured because of which the sync operation cannot proceed.
0x7152835C
MirrorView detected that some of the group members have gone bad because of which it is permanently fractured. This can happen if the members incremental snap session stops because of faulted cache luns. The user won’t be able to perform any operations on this group. The permanently fractured members have to be removed for the group to be operational again.
0x7152835D The user attempted to synchronize a secondary image that is currently syncing because of which the sync request is rejected.
0x7152835E The user attempted to synchronize a secondary image when an update is running for that image because of which the sync request is rejected.
0x7152835F The user attempted to synchronize a secondary image that is currently
system fractured because of which the sync request is rejected.
0x71528360 The user attempted to synchronize a secondary image that is already in synchronized state because of which the sync request is rejected.
0x71528361 The user attempted to synchronize a secondary image when the fracture is still in progress because of which the sync request is rejected.
0x71528362 The user attempted to synchronize a group that is already synchronized because of which the sync request is rejected.
0x71528363 The user attempted to synchronize a group that is currently system fractured because of which the sync request is rejected.
0x71528364 The user attempted to synchronize a group that is currently system fractured because of which the sync request is rejected.
0x71528365 Starting MirrorView PSM rollback due to mirror count mismatch %1
0x71528368 The response received from peer SP while synchronizing the image is not valid.
0x71528369
MirrorView caught an exception while trying to sync an image in response to a request from peer to perform the sync. The sync request will fail and the image will remain admin fractured. Check the event log for any possible errors.
0x7152836A
MirrorView caught an exception while trying to check the status of protective session in response to a requestfrom primary while syncing the image. The image will remain fractured. Check the event log for any possible snap messages. Retry sync after possible errors are fixed.
0x7152836B
MirrorView caught an exception while trying to check the status of protective sessions in response to a request from primary while syncing a group. The image will remain fractured. Check the event log for any possible snap messages. Retry sync after possible errors are fixed.
0x7152836D The user tried to fracture a scrambled group because of which the fracture request is rejected.
0x7152836F The user tried to synchronize a scrambled group because of which the sync request is rejected.
0x71528370 The user tried to synchronize a group when some of the members are rolling back because of which the sync request is rejected.
0x71528371 Group member protective session missing during sync %1
0x7152837B The group id specified to set group properties is not valid
0x7152837C Failed to UnMark member session during sync cleanup %1
0x71528400 Memory initialization failed with status = <status>. SP will reboot
0x71528401 MirrorView/A cannot determine IRP stack size. Loading of the MirrorView/A driver failed. SP will reboot
0x71528402 Driver failed to load. Status: <status>
The MirrorView/A driver has entered degraded mode (status <status>). Administrative actions and I/O to all mirrors may fail. Check the event log prior to this event for errors and subsequent corrective actions. After taking any necessary corrective actions, reboot this SP. If the problem persists, contact customer support
0x71528404 MirrorView/A cannot create a name for the device under binding.
0x71528406 Unknown device type on trespass execute: Parameters: 1) Received Device Type 2) A pointer to the IRP 3) A pointer to the IRP stack location 4) The line number
0x71528407 The device was not found on the peer, this could indicate an inconsistent database
0x71528408 The MirrorView/A driver could not allocate memory to satisfy the trespass request. Parameters: 1) A pointer to the device type 2) A pointer to the IRP 3) The line number 4) 0
0x71528409 The MirrorView/A driver could not allocate memory to satisfy the trespass request
0x7152840A
Driver was unable to read the target device on the primary array because the device is not ready. Parameters: 1) A pointer to the consumed device. 2) A pointer to the IRP 3) A pointer to the IRP stack location 4) The line number
0x7152840B
Driver was unable to read the target device on the secondary array because the device is not ready. Parameters: 1) A pointer to the consumed device. 2) A pointer to the IRP 3) A pointer to the IRP stack location 4) The line number
0x7152840C
Driver was unable to read the shadow device on the secondary array because the device is not ready. Parameters: 1) A pointer to the consumed device. 2) A pointer to the IRP 3) A pointer to the IRP stack location 4) The line number
0x7152840D
Driver was unable to read the target device on the primary array because the device is owned by the peer SP. Parameters: 1) A pointer to the exported device. 2) A pointer to the IRP 3) A pointer to the IRP stack location 4) The line number
0x7152840E
Driver was unable to read the target device on the secondary array because the device is owned by the peer SP. Parameters: 1) A pointer to the exported device. 2) A pointer to the IRP 3) A pointer to the IRP stack location 4) The line number
0x7152840F
Driver was unable to read the shadow device on the secondary array because the device is owned by the peer SP. Parameters: 1) A pointer to the exported device. 2) A pointer to the IRP 3) A pointer to the IRP stack location 4) The line number
0x71528410 The MirrorView/A driver could not process a read request because of an unknow I/O role. This could indicate an inconsistent database. Parameters: 1) Device role. 2) A pointer to the IRP 3) A pointer to the
The MirrorView/A driver could not process a read request because of an unknow I/O role. This could indicate an inconsistent database. Parameters: 1) Device role. 2) A pointer to the IRP 3) A pointer to the IRP stack location 4) The line number
0x71528412
Driver received unexpected read request to the shadow device on the primary. This indicates an incorrect storage group configuration. Parameters: 1) A pointer to the exported device. 2) A pointer to the IRP 3) A pointer to the IRP stack location 4) The line number
0x71528413
Driver was unable to write to the target device on the primary array because the device is not ready. Parameters: 1) A pointer to the consumed device. 2) A pointer to the IRP 3) A pointer to the IRP stack location 4) The line number
0x71528414
Driver was unable to write to the shadow device on the secondary array because the device is not ready. Parameters: 1) A pointer to the consumed device. 2) A pointer to the IRP 3) A pointer to the IRP stack location 4) The line number
0x71528415
Driver was unable to write to the target device on the primary array because the device is owned by the peer SP. Parameters: 1) A pointer to the exported device. 2) A pointer to the IRP 3) A pointer to the IRP stack location 4) The line number
0x71528416
Driver was unable to write to the target device on the secondary array because the device is owned by the peer SP. Parameters: 1) A pointer to the exported device. 2) A pointer to the IRP 3) A pointer to the IRP stack location 4) The line number
0x71528417
Driver was unable to write to the shadow device on the secondary array because the device is owned by the peer SP. Parameters: 1) A pointer to the exported device. 2) A pointer to the IRP 3) A pointer to the IRP stack location 4) The line number
0x71528418
The MirrorView/A driver could not process a write request because of an unknow I/O role. This could indicate an inconsistent database. Parameters: 1) Device role. 2) A pointer to the IRP 3) A pointer to the IRP stack location 4) The line number
0x71528419
The MirrorView/A driver could not process a write request because of an unknow I/O role. This could indicate an inconsistent database. Parameters: 1) Device role. 2) A pointer to the IRP 3) A pointer to the IRP stack location 4) The line number
0x7152841A
Driver received unexpected write request to the shadow device on the primary. This indicates an incorrect storage group configuration. Parameters: 1) A pointer to the exported device. 2) A pointer to the IRP 3) A pointer to the IRP stack location 4) The line number
0x7152841B Driver failed to obtain its consumable devices from PSM
0x7152841D Driver cannot locate the named consumable devices
0x7152841E Driver cannot locate the requested consumable devices by WWID
0x7152841F Driver cannot allocate memory needed for adding a consumable device
0x71528420 Driver cannot allocate memory needed for writing consumable devices to PSM
0x71528421 Driver cannot allocate memory needed for reading consumable devices from PSM
0x71528422 Driver failed to receive correct header data from PSM
0x71528423 Driver failed to receive a correct revision ID from PSM
0x71528424 Driver failed to receive correct consumable data from PSM
0x71528425 Driver failed to update its compatibility mode data in PSM
0x71528426 Driver received an unknown ioctl request.
0x71528427 Driver timed out after waiting for 3 minutes to obtain disk geometry information from Flare. SP will reboot and should correct the problem
0x71528428 Driver received an invalid bind request (buffer size). Check the versions of MirrorView/A driver and Admin DLL and make them consistent
0x71528429 Driver received an invalid bind request (revision ID). Check the versions of MirrorView/A driver and Admin DLL and make them consistent
0x7152842A Driver received an invalid unbind request (buffer size). Check the versions of MirrorView/A driver and Admin DLL and make them consistent
0x7152842B Driver received an invalid unbind request (revision ID). Check the versions of MirrorView/A driver and Admin DLL and make them consistent
0x7152842C Driver received an invalid enum objects request (buffer size). Check the versions of MirrorView/A driver and Admin DLL and make them consistent
0x7152842D Driver received an invalid enum objects request (revision ID). Check the versions of MirrorView/A driver and Admin DLL and make them consistent
0x7152842E Driver received an invalid get compatibility mode request (buffer size). Check the versions of MirrorView/A driver and Admin DLL and make them consistent
0x7152842F Driver received an invalid get compatibility mode request (revision ID). Check the versions of MirrorView/A driver and Admin DLL and make them consistent
0x71528430 Driver received an invalid put compatibility mode request (buffer size). Check the versions of MirrorView/A driver and Admin DLL and make them consistent
0x71528431 Driver received an invalid put compatibility mode request (revision ID). Check the versions of MirrorView/A driver and Admin DLL and make
0x71528432 Driver received an invalid shutdown request (buffer size). Check the versions of MirrorView/A driver and Admin DLL and make them consistent
0x71528433 Driver received an invalid shutdown request (revision ID). Check the versions of MirrorView/A driver and Admin DLL and make them consistent
0x71528434 Driver received an invalid create shadow LU request (buffer size). Check the versions of MirrorView/A driver and Admin DLL and make them consistent
0x71528435 Driver received an invalid create shadow LU request (revision ID). Check the versions of MirrorView/A driver and Admin DLL and make them consistent
0x71528436 Driver unable to locate the specified target device when processing a create shadow LU command. Check the WWN of the target device
0x71528437 Driver unable to create a shadow device on a target device that already has a shadow. Check the WWN of the target device
0x71528438 Driver received an invalid destroy shadow LU request (buffer size). Check the versions of MirrorView/A driver and Admin DLL and make them consistent
0x71528439 Driver received an invalid destroy shadow LU request (revision ID). Check the versions of MirrorView/A driver and Admin DLL and make them consistent
0x7152843A Driver received a destroy shadow LU request with an incorrect device name. Check the device map and the layered drivers on the device stack
0x7152843B Driver unable to locate the specified target device when processing a create shadow LU command. Check the WWN of the target device
0x7152843C Driver received an invalid enumerate shadow LU request (buffer size). Check the versions of MirrorView/A driver and Admin DLL and make them consistent
0x7152843D Driver received an invalid enumerate shadow LU request (revision ID). Check the versions of MirrorView/A driver and Admin DLL and make them consistent
0x7152843E Driver received an invalid get generic properties request (buffer size). Check the versions of MirrorView/A driver and Admin DLL and make them consistent
0x7152843F Driver received an invalid get generic properties request (revision ID). Check the versions of MirrorView/A driver and Admin DLL and make them consistent
0x71528440 Driver received an invalid get device properties request (buffer size). Check the versions of MirrorView/A driver and Admin DLL and make them consistent
0x71528441 Driver received an invalid get device properties request (revision ID). Check the versions of MirrorView/A driver and Admin DLL and make them consistent
0x71528442 Driver received an invalid set device properties request (buffer size). Check the versions of MirrorView/A driver and Admin DLL and make them consistent
0x71528443 Driver received an invalid set device properties request (revision ID). Check the versions of MirrorView/A driver and Admin DLL and make them consistent
0x71528444 Driver received an invalid query ownership and hold request (buffer size). Check the versions of MirrorView/A driver and Admin DLL and make them consistent
0x71528445 Driver received an invalid query ownership and hold request (revision ID). Check the versions of MirrorView/A driver and Admin DLL and make them consistent
0x71528446 Driver received an invalid release ownership request (buffer size). Check the versions of MirrorView/A driver and Admin DLL and make them consistent
0x71528447 Driver received an invalid release ownership request (revision ID). Check the versions of MirrorView/A driver and Admin DLL and make them consistent
0x71528448 Driver received an invalid trespass LU request (buffer size). Check the versions of MirrorView/A driver and Admin DLL and make them consistent
0x71528449 Driver received an invalid trespass LU request (revision ID). Check the versions of MirrorView/A driver and Admin DLL and make them consistent
0x7152844A Driver failed to open PSM device after the maximum number of attempts. SP will reboot and should correct the problem
0x7152844B Driver failed to open PSM device because it is not ready for read. SP will reboot and should correct the problem
0x7152844C Driver was unable to commit changes made by a bind request. SP will reboot
0x7152844D Driver was unable to back out of a failed bind. SP will reboot
0x7152844E Driver was unable to commit a rebind operation. SP will reboot
0x7152844F Driver was unable to commit changes made by an unbind. SP will reboot
0x71528450 Driver received an incorrect response (message size) from updating its peer's consumable. Check the versions of MirrorView/A driver and Admin DLL and make them consistent
0x71528451 Driver received an incorrect response (revision id) from updating its peer's consumable. Check the versions of MirrorView/A driver and
0x71528452 Driver was unable to update peer's consumable. Check peer communication status
0x71528453 Driver received an incorrect response (message size) from updating its peer's compatibility mode. Check the versions of MirrorView/A driver and Admin DLL and make them consistent
0x71528454 Driver received an incorrect response (revision id) from updating its peer's compatibility mode. Check the versions of MirrorView/A driver and Admin DLL and make them consistent
0x71528455 Driver was unable to update peer's compatibility mode. Check peer communication status
0x71528456 Driver received an incorrect message (revision id) while processing a bind consumable request from the peer. Check the versions of MirrorView/A driver and Admin DLL and make them consistent
0x71528457 Driver received an incorrect message (revision id) while processing a rebind consumable request from the peer. Check the versions of MirrorView/A driver and Admin DLL and make them consistent
0x71528458 Driver received an incorrect message (revision id) while processing an unbind consumable request from the peer. Check the versions of MirrorView/A driver and Admin DLL and make them consistent
0x71528459 Driver received an incorrect message (revision id) while processing an update consumable request from the peer. Check the versions of MirrorView/A driver and Admin DLL and make them consistent
0x7152845A Driver received an incorrect message (revision id) while processing an update compatibility mode request from the peer. Check the versions of MirrorView/A driver and Admin DLL and make them consistent
0x7152845B Driver was unable to commit changes made by a set device properties request. SP will reboot
0x7152845C Driver unable to unbind the target device because its shadow device still exists
0x7152845D Driver was unable to allocate required memory for Transport component. SP will reboot
0x7152845E Driver was unable to open the CMI device. SP will reboot
0x7152845F Driver was unable to send a messagae because it is degraded. SP will reboot
0x71528460 Driver received an unexpected MPS message. SP will reboot
0x71528461 Driver was unable to allocate memory for sending a response message. SP will reboot
0x71528462 Driver was unable to allocate memory for processing a received message. SP will reboot
0x71528463 Driver detected a duplicate mailbox in opening a request filament. SP will reboot
0x71528464 Driver detected a duplicate mailbox in opening a response filament. SP will reboot
0x7152846C Driver received an invalid set backdoor read request (buffer size). Check the versions of MirrorView/A driver and Admin DLL and make them consistent
0x7152846D Driver received an invalid set backdoor read request (revision ID). Check the versions of MirrorView/A driver and Admin DLL and make them consistent
0x7152846E Driver could not obtain the resources necessary to satisfy the request
0x7152846F Driver received an invalid sequence of requests. A query ownership call was executed while another was in progress
0x71528470 Driver received an invalid sequence of requests. A release ownership call was executed before a query ownership was received
0x71528471
The MirrorView/A driver detect that a shadow device is not associated with a target device when processing an ownership loss request. Parameters: 1) A pointer to the consumed device. 2) A pointer to the IRP 3) A pointer to the IRP stack location 4) The line number
0x71528472 Driver received an invalid sequence of requests. A trespass execute was received while one was in progress
0x71528473 Driver received an invalid invalid status from an internal routine
0x71528474 Driver timed out after waiting for 3 minutes to obtain raid information from Flare. SP will reboot and should correct the problem
0x71528500 MirrorView/A monitor is consuming memory more than the acceptable maximum working set size. As a result of this error MirrorView/A monitor will be restarted cleanly
0x71528501 MirrorView/A driver has not started
0x71528600
MirrorView_A, caught an exception when attempting to remove an image. Retry the operation if necessary and check the eventlog for additional information. It may be necessary to reboot the SP to clean up the problem
0x71528601 MirrorView_A, caught an exception when attempting to add an image. Retry the operation if necessary and check the eventlog for additional information. It may be necessary to reboot the SP to clean up the problem
0x71528602 An unknown exception has been caught parsing the returned response output buffer for consistent mark status
0x71528603 SANCopy did not return a valid response output buffer with consistent mark status
0x71528604 An unknown exception has been caught parsing individaul image marks status on a consistent mark failure
MirrorView_A, caught an exception when attempting to promote an image on the peer SP. Retry the operation if necessary and check the eventlog for additional information. It may be necessary to reboot the SP to clean up the problem
0x71528606
MirrorView_A, caught an exception when attempting to promote an image. Retry the operation if necessary and check the eventlog for additional information. It may be necessary to reboot the SP to clean up the problem
0x71528607 An unknown exception has been caught fracturing the image or a group on a failure to query incremental snap session
0x71528608 Failed to query incremental snap session. As a result the group which this mirror is a part of will be admin fractured. Look at the status error code for more details
0x71528609 Failed to query incremental snap session. As a result the group which this image is a part of will be admin fractured. Look at the status error code for more details
0x7152860A An unknown exception has been caught updating last image error on a consistent mark failure
0x7152860B An unknown exception has been caught enumerating secondary images
0x7152860C An unknown exception has been caught enumerating groups
0x7152860D An unknown exception has been caught servicing message for remote add member
0x7152860E An unknown exception has been caught servicing message for remote add member and creating a group
0x7152860F An unknown exception has been caught servicing message for remote remove member
0x71528610 An unknown exception has been caught servicing message for remote remove member and destroy a group
0x71528611 An unknown exception has been caught during a walk group list operation
0x71528612 An unknown exception has been caught during a walk group members operation
0x71528613 An unknown exception has been caught during a group state calculation
0x71528614 An unknown exception has been caught during a group scrambled state test
0x71528615 An unknown exception has been caught while setting a mirrors membership during cleanup
0x71528616 An unknown exception has been caught while resetting a mirrors membership during cleanup
0x71528617 MirrorView/A, an exception was caught while creating a group. Retry the operation and if unsuccessful you should reboot the SP to clean up the problem
0x71528618 MirrorView/A, an exception was caught while destroying a group on the remote array. Retry the operation and if unsuccessful you should reboot the SP to clean up the problem
0x71528619 MirrorView/A - Peer's set throttle group response is not valid
0x7152861A An unknown exception has been caught while sending the set throttle command to sancopy
0x7152861B An unknown exception has been caught while setting throttle on the correct SP
0x7152861C An unknown exception has been caught while setting throttle for a group member
0x7152861D An unknown exception has been caught while setting throttle for a group member
0x7152861E An unknown exception has been caught while servicing set throttle on the peer
0x71528621 An unknown exception has been caught querying sancopy status
0x71528622 An unknown exception has been caught walking group list
0x71528623 The member could not be added because the image role of the remote image is not secondary
0x71528624 The member could not be added because the image role of the remote image is not secondary
0x71528625 The member could not be added because there is no secondary image on the remote array
0x71528626 The member could not be removed because there is no secondary image on the remote array
0x71528627 During cleanup it was found that the group was normal but the individual mirror images in the group was not normal. As a result the group was adminfractured. Retry a sync on the group
0x71528628
Mirror sanity check has failed while creating protective session on the secondary array before the start of an update. The externalID's for the mirror on the primary array and mirror on the seconedary array dont match. This indicates that the secondary mirror was promoted when there was no connection between the primary and secondary array
0x71528629 Mirror sanity check has failed while creating protective session on the secondary array before the start of an update. Unable to locate mirror on the secondary array to perform the sanity check
0x7152862A Mirror sanity check has failed while creating protective session on the secondary array before the start of an update. Failed to accqurire database mutex on the secondary array to perform the sanity check
0x7152862B An unknown exception has occured during a sanity check on the secodary arrray while creating protective session before the start of an update
0x7152862C Failed to create protective snap session on the seoncdary array for a group. Look a the status error code to determine the actual cause of the error
0x7152862D Failed to create protective snap session on the seoncdary array for a group. Look a the status error code to determine the actual cause of the error
0x7152862E An unknown exception has been caught while cleaning up access control
0x7152862F The mirror id of the member in the primary group differs from the mirror id on the remote array
0x71528630 The primary group id and the remote group id stored with the secondary group do not match
0x71528631 Caught exception while promoting the group
0x71528632 The message received will not be serviced because it contains an unknown opcode
0x71528633 The image specified for promotion wasn't local. Reissue the command to the array where the promoted image resides
0x71528634 Cannot add a secondary image to a mirror in a scrambled group. Remove the mirror from the group and retry the command
0x71528637 An unknown exception has been caught obtaining group update data
0x71528638 An unknown exception has been caught starting an update for the group
0x71528639 An unknown exception has been caught while performing a consistent mark operation
0x7152863A An unknown exception has been caught while performing a group activate
0x7152863B An unknown exception has been caught checking if the group members are normal
0x7152863C An unknown exception has been caught checking if the group members are aborted
0x7152863D An unknown exception has been caught by MirrorView/A monitor's exception filter. As a result MirrorView/A monitor will be shutdown and restarted
0x7152863E
Unable to create protective snap session on secondary array. SnapView returned an error on an attempt to create a protective snap session due to lack of free cache LUN's on secondary array. As a result of the error the mirror will be admin fractured. Add more cache LUN's on the secondary array and retry the sync request
Unable to create protective snap sessions for the group on the secondary array. SnapView returned an error on an attempt to create protective snap sessions for the group due to lack of free cache LUN's on secondary array. As a result of the error the group will be adminfractured. Add more cache LUN's on the secondary array and retry the sync request
0x71528640 An unknown exception has been caught performing a consistent mark on one sancopy session
0x71528641 Failed to create MirrorView/A Group
0x71528642 Failed to create MirrorView/A Group
0x71528643 Failed to destroy MirrorView/A Group
0x71528644 Failed to destroy remote MirrorView/A Group
0x71528645 Failed to add member to MirrorView/A Group
0x71528646 Failed to add member to remote MirrorView/A Group
0x71528647 Failed to remove member from MirrorView/A Group
0x71528648 Failed to remove member from remote MirrorView/A Group
0x71528649 Failed to set properties for a MirrorView/A Group
0x7152864A Setting the Group Id with the mirror during cleanup
0x7152864B Re-setting the Group Id with the mirror during cleanup
0x7152864C MirrorView/A - A member cannot be added to a group if the group is invalid
0x7152864D MirrorView/A - A member cannot be removed from a group if the group is invalid
0x7152864E Changing the locality of a group due to a failed promote group operation
0x7152864F Failed to commit member data during group promote
0x71528650 Failed to commit member data while promoting remote group
0x71528651 Snap test performed as part of adding secondary image failed because of which the secondary image won’t be created.
0x71528652 An unkown exception has been caught while attempting to regenerate devicemap.
0x71528653 Cannot set the synchronization rate for a mirror participating in a group
0x7152867B Cannot proceed with promote as remote image is a member of a group.
0x7152867C Caught an Exception while attempting to fix the group with invalid group condition.
0x7152867D Mirrorview failed to trespass during an incremental udpate. As a result the group which this mirror is a part of will be admin fractured. Look at the last image error to determine the actual cause of the failure.
0x7152867E Mirrorview failed to trespass because the connection to the secondary array is not available. As a result the mirror will system fracture.
0x7152867F Mirrorview failed to trespass because the connection to the secondary array is not available. As a result the group which this mirror is a part of will be system fractured.
0x715287C The update period specified while setting group properties is not valid
Warning
0x71054500 A number of Bad Blocks found in this sync, Slave invalidation has been performed.
0x71054600 Consistency Group %2 has been deactivated. Check log for group promote or group error recovery.
0x71054601 Remote system for Consistency Group %2 has successfully completed a local-only promote. Secondary images in the group will be removed from the group on this system.
0x71054602
Consistency Group is not initialized or is degraded on the remote system for group %s. Subsequently not all Consistency Group sync safety checks can be performed. Check the Consistency Group setup on the remote system.
0x71054603
The remote Consistency Group for group %2 could not be found on the remote system. Subsequently not all Consistency Group sync safety checks can be performed. Check the Consistency Group setup on the remote system.
0x71054604 The membership count for Consistency Group %2 is different on the local and remote system. Check the Consistency Group setup on the local and remote system.
0x71054605
The membership count for Consistency Group %2 does not match on the local and remote system and a force promote command was received for this group. It is strongly recommended that the group membership be corrected prior to any other operations or use of this Consistency Group.
0x71054606
Consistency Group %2 has been force promoted while the MirrorView driver on the remote system was in degraded mode. The consistency group on this system may now only have primary images. Check for MirrorView errors on the remote system.
0x71054608 Consistency Group %s2 has been force promoted while the Write Intent Logs (WIL) were faulted. Mirrors in the group may now no longer be set to use the WIL. Check for faults on the WIL LUNs.
A problem has occurred on the SP and this SP has failed to unquiesce I/O. This is not a problem caused by MirrorView/A. MirrorView/A is only reporting the problem. MirrorView/A will not be able to perform its poll operations or service any incoming/outgoing messages from this SP until the problem has been corrected
0x71524002
While updating the status for a failed descriptor, MirrorView/A checks that the array on which the SANCopy descriptor failed holds the primary image. If it is not a primary image, then a descriptor for this image should not exist at all. It is likely a case where the user attempted to promote an image which is updating, and the descriptor on the primary image is left behind. As a result MirrorView/A will remove the descriptor
0x71524003 Mirrordatabase is unable to locate an image for the specified descriptor. Also the session for the specified descriptor has failed or aborted. As a result MirrorView/A has removed the orphaned descriptor
0x71524004 Orphan protective session is removed
0x71524005 Orphan secondary image is removed
0x71524006 Cannot proceed with normal promote of group <group> as members protective sessions exist
0x71524007 Cannot proceed with normal group promote due to bad connectivity
0x71524008 Failed to obtain maximum number of images that can be created on this system from the registry
0x71524009 Failed to obtain maximum number of groups that can be created on this system from the registry
0x7152400A Failed to obtain maximum members that can be added to a group on this system from the registry
0x7152400D A protective snap session already exists before the start of an update. An incremental update will be started with the existing protective snap session.
Information 0x71050101 Unable to deallocate write intent log during destroy operation
0x71050102 Received a request to create a mirror
0x71050103 Received a request to destroy a mirror
0x71050105 Received a request to add a secondary image
0x71050106 Received a request to remove a secondary image
0x71050107 Received a request to get mirror properties
0x71050108 Received a request to set mirror properties
0x71050109 Received a request to get image properties
0x7105010A Received a request to set image properties
0x71050136 Received a request from our peer SP to halt I/O to an LU
0x71050138 Cookie on the old primary differs from the secondary during a promote operation
0x71050139 The LU will be rebound after this rebind
0x7105013A The MirrorView driver received a command to update the compatability mode
0x7105013B Adding secondary image with Image state as Insync for mirror %2:%3
0x7105013C Create a new consistency group.
0x7105013D Destroying consistency group.
0x7105013E Add member to consistency group.
0x7105013F Remove a member from a consistency group.
0x71050140 Received a request to get properties for Consistency Group/s.
0x71050141 Received a request to set properties for a Consistency Group.
0x71050142 Consistency Group %2:%3 is created.
0x71050143 Consistency Group %2 is destroyed.
0x71050144 Member %2 is added to the Consistency group %3.
0x71050145 Member %2 is removed from the Consistency group %3.
0x71050146 Properties of Consistency Group %2 has been set.
0x71050147 Synchronization of Consistency Group %2 started.
0x71050148 Synchronization of Consistency Group %2 returned successfully.
0x71050149 Promote of Consistency Group %2 started.
0x7105014A Remote system has started a promotion of Consistency Group %2. This group will be deactivated during the promote.
0x7105014B Remote system has started a local-only promotion of Consistency Group %2. This group on this system will no longer be viable for Consistency Group services.
0x7105014C User requested a local only promote for Consistency Group %2. This group will contain primary images only.
0x7105014D Promote of Consistency Group %2 returned successfully.
0x7105014E Remote system successfully promoted Consistency Group %2.
0x7105014F Fracture of Consistency Group %2 returned successfully.
0x71050150 Consistency Group %2 has been activated.
0x71050152 Consistency Group %2 promotion starting from Mixed state.
0x71050153 A force remove has been requested for Consistency Group %2.
0x71050154 A force destroy has been requested for Consistency Group %2.
0x71050156 Received request to create remote consistency group and add member.
0x7100C01C Snap Chunk Repository did not find Target Particulars when they should already have been allocated
0x7100C01D Snap Chunk Repository did not find Cache Particulars when they should already
0x7100C01F The Release of the Dist Lock Semaphore in napCopyCacheDLSReleaseCallbackSemaphore() STATUS_SEMAPHORE_LIMIT_EXCEEDED exception.
0x7100C020 The Release of the Dist Lock Semaphore in napCopyCacheDLSxxxPermit() STATUS_SEMAPHORE_LIMIT_EXCEEDED exception.
0x7100C022 A Cache Assign Permit Lock Convert to an Unexpected mode in SnapCopyCacheDLSPermitCallback()
0x7100C023 A Cache Assign Permit Lock could not be opened in SnapCopyCacheDLSCreatePermit()
0x7100C025 A Cache Assign Permit Lock could not be opened in SnapCopyCacheDLSSurrenderPermit()
0x7100C026 A Cache Assign Permit Lock could not be opened in SnapCopyCacheDLSSurrenderPermit()
0x7100C029 SnapView SnapCopyPageAvailable() caused the context's Semaphore to overflow
0x7100C02A SnapView SnapCopyVMIOComplete() caused the context's Semaphore to overflow
0x7100C02B SnapCopyDeltaMapMergeRegion() was called with an invalid Direction
0x7100C02C SnapCopyDeltaMapPlyBitsBlock() was called with an invalid Operation
0x7100C02D SnapCopyDeltaMapPlyRegion() is trying to perform a non-read operation on an uninitalized Delta Bits Region. Only GET and GET_NEXT_SET should ever see an uninitialized Delta Bits Region
Error 0x71008000 Invalid DBID sent to Admin Library
0x71008001 Invalid OP Code sent to Admin Lib
0x71008002 Invalid ISPEC sent to Admin Library
0x71008003 Ioctl from Admin Lib to driver timed out
0x71008004 Admin lib could not open driver
0x71008005 An administrative shutdown was given to the driver
0x71008006 For a multitude of possible reasons, the SnapView driver failed to load during the boot sequence.
0x71008007 Creation of the device structure for SnapView failed
0x71008008 Creation of the symlink to the driver device object failed
0x71008009 Deletion of the symlink to the driver device object failed
0x7100800A The SnapView driver could not create a device (i.e. Target Lun, Snap Lun, etc...)
0x7100800B Open/Close received for unknown device
0x7100800C IOCTL packet revision is invalid
0x7100800D Deletion of the specified device failed
0x7100800E SnapView driver has exceeded its memory allocation or system is really out of memory
0x7100800F The SnapView driver has tried an operation on a target Lun that does not exist.
0x71008010 SCLUN does not exist
0x71008011 SnapView has tried to bind itself into a device that it is already bound to.
0x71008012 Specified logical unit does not exist
0x71008013 The command issued cannot be performed against this device because this device is a source lun. Please retry the command using only SnapShot devices.
0x71008013 Logical Unit is not a Snapshot
0x71008014 Cannot unbind a SSLUN while there are active sessions
0x71008015 Cannot unbind a SSLUN while it has SCLUNs defined
0x71008016 Logical Unit already exists in the Reserved Lun Pool
0x71008017 Logical Unit does not exist in the Reserved Lun Pool
0x71008018 The Reserved Lun cannot be removed unless it is assigned to this SP
0x71008019 The Reserved Lun cannot be removed while sessions are actively using it
0x7100801A The Reserved Lun cannot be opened
0x7100801B Unable to get the geometry information for Reserved Lun
0x7100801C There is no more room in the Reserved Lun Pool
0x7100801D The Reserved Lun Pool has its maximum number of devices
0x7100801E PSM driver could not be opened
0x7100801F SnapView could not open the specified PSM data file
0x71008020 SnapView could not close the specified PSM data file
0x71008021 SnapView could not read from the specified PSM data file
0x71008022 SnapView could not write to the specified PSM data file
0x71008023 The specified SnapView PSM data file has been created.
0x71008024 SnapView tried to access the wrong PSM file
0x71008025 A call to the PSM driver has returned an error.
0x71008026 SnapView could not open the MPS driver.
0x71008027 SnapView is experiencing difficulties in opening a filament.
0x7100807B SnapView has discovered an inconsistency in SnapView Cache metadata. SnapView is stopping Sessions.
0x7100807C Due to an internal inconsistency, the RollBack operation on device cannot continue
0x7100807D Session already exists with different session attributes
0x7100807E Incremental Session is not marked
0x7100807F Incremental Session is marked
0x71008080 Session is not incremental
0x71008081 Session is incremental
0x71008082 Session has invalid copy type
0x71008083 Existing Reserved Lun does not support Incremental sessions
0x71008084 Cannot mark Incremental session while a Rollback is in progress
0x71008085 Invalid granularity value specified for session
0x71008086 The tracking granularity cannot be changed while copy session is active
0x71008087 A Read request was received while session has copy type Incremental
0x71008089 Maximum number of Snapshots already created for this array
0x7100808A A SnapView Reserved LUN did not have sufficient space for the minimum map regions
0x7100808B A SnapView snapshot already exists with the specified name
0x7100808D Incremental session %s is in progress.
0x7100808E A SnapView Multi-lun Consistent Mark operation was attempted against a session which is already marked consistently. Only unmarked sessions can be marked.
0x7100808F
SnapView Multi-lun Consistent operation was attempted against a device which is already involved in another Multi-lun Consistent operation. Only one Multi-lun Consistent operation is allowed against a given device at one time. Allow the first one to complete and retry the operation.
0x71008090 SnapView Multi-lun Consistent operation was aborted. Please retry the operation. If the problem persists, please contact support.
0x71008091 An operation against a SnapView session is being disallowed because the session is currently involved in a consistent operation intiated by the user or the array itself.
0x71008092 SnapView is not available for user requests
0x71008098 A SnapView Multi-lun Consistent <type> operation was already in progress before this SP was ready to participate. Refer to this message only if the SnapView Multi-lun Consistent <type> operation fails on the other SP.
0x710080A2 An error occurred on Lun <number> due to a trespass while attempting a SnapView Multi-lun Consistent <type> operation. Please retry the operation.
0x710080A6 SnapView session <number> already exists and cannot have new devices added to it.
0x710080A8 The user attempted to perform an operation specified more target luns than allowed by the array for the operation.
0x710080A9 SnapView requires the installed package to be committed by NDU before the operation can be performed. Please commit the FLARE-Operating-Environment package and retry the operation.
0x710080AB The user tried to start a session that would surpass the limits for this platform.
0x710080AE The command issued cannot be performed against this device because this device is a SnapShot device. Please retry the command using only source luns.
0x710080AF A start operation was attempted using a session name that is too long.
0x710080B0 A generic request/response operation was attempted using an invalid opcode.
0x710080B1 A generic request/response operation was atempted specifying no luns. This operation requires luns to be specified. Please retry the command specifying at least one lun.
0x710080B2 A disk operation from SnapCopy failed to complete successfully on LUN %2. Please check the state of the LUN and retry the operation.
0x710080B3
The requested start session or create snapshot operation cannot be completed for LUN %2. The maximum number of objects has been reached. Please destroy all snapshots and stop all sessions for another LUN currently in use and retry this operation.
0x71268000 Invalid database ID detected in admin DLL
0x71268001 Invalid operation code detected in admin DLL
0x71268010 Required property missing from operation.
0x71268021 Invalid Source LU specified for creating a CloneView
0x71268022 The LU specified for the Clones Private LUN (CPL) is already in use
0x71268028 Could not access specified Clones device
0x71268029 Request to create a CloneView specifies an invalid LU ID value
0x7126802A Request to add Clone does not specify a CloneView ID
0x7126802C Request to add a Clone specifies an invalid LU ID value
0x7126802D Request to get CloneView properties specifies an invalid CloneView ID
0x7126802E Request to get Clone properties specifies an invalid CloneView ID
0x7126802F Request to get Clone properties specifies an invalid Clone ID
0x71268032 Request to destroy a CloneView specifies an invalid CloneView ID
0x71268033 Request to define the Clones Private LUN (CPL) specifies an invalid LU ID for SP A
0x71268034 Request to define the Clones Private LUN (CPL) specifies an invalid LU ID for SP B
0x71268035 Request to set CloneView properties specifies an invalid CloneView ID
0x71268036 Request to remove a Clone specifies an invalid CloneView ID
0x71268037 Request to remove a Clone specifies an invalid Clone ID
0x71268038 Request to fracture a Clone specifies an invalid CloneView ID
0x71268039 Request to fracture a Clone specifies an invalid Clone ID
0x7126803A Request to synchronize a Clone specifies an invalid CloneView ID
0x7126803B Request to synchronize a Clone specifies an invalid Clone ID
0x7126803C Request to set Clone properties specifies an invalid CloneView ID
0x7126803D Request to set Clone properties specifies an invalid Clone ID
0x7126803E An invalid name was specified for a CloneView
0x71268047 No synchronization delay value was specified for a Clone
0x7126804B Request to quiesce an LU failed
0x7126804C Request to unquiesce an LU failed
0x7126804D Request to unquiesce the CloneView Failed
0x7126804E Specified Source LU is already part of an existing CloneView.
0x7126804F Specified Clone LU is already part of an existing CloneView.
0x71268050 An existing Clone in the CloneView is reverse-out-of-sync or reverse-syncing. A new Clone cannot be added.
0x71268051 An existing CloneView has the same name as the specified CloneView
0x71268052 The recovery policy for the specified Clone was attempted to be set to auto when the clone was consistent and waiting on admin
0x71268053 The write intent logs are already allocated, not allocating again
0x71268054 Fast recovery feature is already in use, cannot enable it again
0x71268055 Fast recovery feature is already not in use, cannot disable it again.
0x71268056 The array set count specified for the operation must be 1.
0x71268059 Clones Consistent Fracture operation failed. Any necesssary re-synchronizations have been performed. Please correct any individual device failures and verify the state of the clones before re-trying the operation.
0x7126805A
Clones Consistent Fracture operation failed. One or more devices failed to initiate a re-synchronization after one clone failed to fracture. Please correct any individual devices failures and verify the state of the clones before re-trying the operation.
0x7126805B Clones Consistent Fracture Operation failed. Attempting to consistently fracture one or more clones already fractured, which is not allowed. Only un-fractured clones can be consistently fractured.
0x7126805C Clones Consistent Fracture operation failed to initialize. Please correct any
individual devices failures and verify the state of the clones before re-trying the operation.
0x7126805D
Clones Consistent Fracture Operation cleanup failed. The Clones driver cannot verify if the consistent operation completed successfully or not. Please retry the operation. Manual intervention may be required to resume consistent operations.
0x7126805E The Clones Consistent operation was not attempted against this device due to a failure of the Consistent operation against another device involved in this operation.
0x7126805F The Clones Consistent operation was not attempted because the maximum number of Consistent operations are already in progress on this array. Allow operations to complete and retry the operation.
0x71268060 A Clones Consistent Fracture operation was attempted against a clone that was already fractured. Only clones that are not fractured can be fractured consistently.
0x71268061 A Clones Consistent operation was attempted against a device already involved in another Consistent operation. Allow previously running commands to complete and retry the operation.
0x71268062 A Clones Consistent operation was aborted by this device. Please retry the operation.
0x71268063 The Clones Consistent operation failed due to an internal error. Please contact your support provider.
0x71268064 The Clones Consistent operation failed to start because of internal error. Please contact your support provider.
0x71268065 The Clones Consistent operation failed to locate required source lun information to perform the operation. Please verify the state of your clone source lun and retry the operation.
0x71268066 The Clones Consistent operation failed to locate the required clone information to perform the operation. Please verify the state of your clone lun and retry the operation.
0x71268068 A Clones Consistent operation was performed on a device whose WWN was not found in the Multi-lun Consistent operation SP report.
0x71268069 A Clones Consistent operation was performed on a device whose WWN was not found in the Multi-lun Consistent operation SP report.
0x7126806A A Clones Consistent operation encountered an unknown or unhandled transition.
0x7126806C
A Clones Consistent %2 operation was already in progress before this SP was ready to participate. Refer to this message only if the Clones Consistent %3 operation fails on the other SP. If operation succeeded, do nothing. If operation failed, then retry the operation. If operation continues to fail, please contact your support provider.
0x7126806D A Consistent %2 operation was attempted that specified more devices than allowed for the array type. Only %3 devices are allowed for this operation for this array. Please retry the operation using the correct number of devices.
0x7126806E
A Consistent %2 operation was attempted that specified more clones with the same clone source lun to be fractured than allowed. Only %3 clone device(s) with the same source lun are allowed to be fractured for this operation on this array. Please retry the operation using the correct number of clone devices.
0x71268071 An error occurred on LUN %2 due to a trespass while attempting a Clone Multi-LUN %3 operation. Please retry the operation.
0x71268100 Unable to either complete or back out of a bind operation
0x71268101 Unable to either complete or back out of a rebind operation
0x71268102 Unable to complete an unbind operation
0x71268103 Unable to either complete or back out of a create CloneView operation
0x71268104 Failed to add a Clone to a CloneView
0x71268106 Unable to allocate memory during the update of a CloneView
0x71268107 Unable to allocate memory required to commit changes
0x7126810B Invalid response returned from peer SP from a create CloneView request
0x7126810C Invalid response returned from peer SP from a destroy CloneView request
0x7126810D Invalid response returned from peer SP from a CloneView update request
0x7126810E Invalid response returned from peer SP from a get consumable request
0x7126810F Invalid response returned from peer SP from a set driver properties request
0x71268110 Invalid response returned from peer SP from an update state request
0x71268117 Invalid revision in create CloneView request received from peer SP
0x71268118 Invalid revision in destroy CloneView request received from peer SP
0x71268119 Invalid revision in update CloneView request received from peer SP
0x7126811A Invalid revision in set driver properties request received from peer SP
0x7126811B Invalid revision in stage update request received from peer SP
0x7126811D The ?staged update? pointer was not NULL when it should have been
0x7126811E A request to bind a Clones object into a device stack specified a buffer of invalid size
0x7126811F A request to bind a Clones object into a device stack specified a buffer with an invalid revision
0x71268120 A request to unbind a Clones object from a device stack specified a buffer of invalid size
0x71268121 A request to unbind a Clones object from a device stack specified a buffer with an invalid revision
0x71268123 A request to enumerate objects specified a buffer of invalid size
0x71268534 An IOCTL for trespassing a lun failed. System will panic and should come back up and correct situation automatically
0x71268535 Synchronization of a fractured Clone failed due to memory unavailability. System will panic and should come back up and correct situation automatically
0x71268536 Failed to locate the Slave image during a sync operation.
0x71268537 Failed to allocate memory to process a write request
0x71268539 Extent Log information is invalid
0x7126853A An unexpected situation has occurred during a trespass operation
0x7126853B Frozen Clones COD Resources being used and cannot be deallocated
0x71268540 Unable to find the specified consumed device while trespassing
0x71268541 Unable to allocate resources required for trespassing the Frozen Clone Log
0x71268542 Unable to initialize the Frozen Clone Log prior to trespassing it
0x71268543 Unable to copy the Frozen Clone Log prior to trespassing it.
0x71268546
Failed to read the Frozen Clones Log from disk. If a Clone was reverse-syncing with protected restore enabled, it has been fractured.Performing a reverse-sync operation may cause a full reverse-sync.You may want to reallocate your CPL to clean up the problem.
0x71268547 An I/O request was received by the wrong SP. The SP will panic and resolve itself
0x71268548 Trespass operation failure, could not trespass unfractured clone.
0x71268600 Clones driver load failed
0x71268602 Unable to initialize the system memory during Clones startup
0x71268603 Unable to determine the IRP stack size
0x71268604 The CPL LUNs must be allocated
0x7126870A Unrecognized MPS event received by the transport manager
0x7126870B Insufficient memory available for asynchronous response processing
0x7126870C Detected a duplicate MPS mailbox name in use
0x7126870F Insufficient memory to allocate transport extension data structure
0x71268711 Insufficient memory to allow command delivery.
0x71268712 Command to another SP timed out
0x71268713 Driver is degraded so no response send
0x71268714 An illegal transport command was initiated.
0x71268802 Clone Group size or revision ID incorrect in peer response on message - Stage Update Cleanup.
0x71288006 The RollBack Driver could not create %2.
0x7128801E Some RollBack data could not be read, so block %2 on LUN %3 (%4) has been marked bad.
0x71004016 This Direct Linear Map Initialized Bitmap Region needs to be initialized.
0x71004017 This Direct Linear Map Modified Bitmap Region needs to be initialized.
0x71004018 This Direct Linear Map Region needs to be initialized.
0x71004019 This Direct Linear Map Region contains no modified Source LU Chunks
0x7100401A This Direct Linear Map Region contains no Copy Chunk for the Source LU Chunk
0x7100401B This Direct Linear Map Bitmap Region is already Initialized
0x7100401C The Direct Linear Map subsystem found a Moribund Session during a Locate Chunk
0x7100401D The Direct Linear Map subsystem found a Moribund Session during a Record Chunk
0x7100401E The Snap Chunk Repository subsystem found no Free Chunks in a Region
0x7100401F The Snap Chunk Repository subsystem found no Free Chunks on a Cache LU
0x71004020 The Snap Chunk Repository is looing for a Chunk it cannot find.
0x71004021 The Snap Direct Linear Map has been asked to Locate or Record a Copy Chunk with no Session specified.
0x71004022 Simulation mode SnapView Sessions are not supported by this version of SnapView.
0x71004023 The Source LU cannot be unbound because a Reserved Lun associated with it is being scavenged for moribund Chunks
0x71004024 A Scavenge was started when a Scavenge was already in progress.
0x71004025 A stored Requisitioned Chunk count may be inaccurate, because a Search is in progress.
0x71004026 A stored Requisitioned Chunk count may be inaccurate, because a Scavenge is in progress.
0x71004027 A stored Requisitioned Chunk count may be inaccurate, because a Search took place after the last Scavenge.
0x71004028 A stored Requisitioned Chunk count may be inaccurate, because a Scavenge took place after the last Scavenge. I don't think this should happen.
0x71004029 A stored Requisitioned Chunk count may be inaccurate, because a Search took place during the last Scavenge.
0x7100402A The Cache LU cannot be removed from the Target becuase it has some Direct Linear Map Entries.
0x7100402B The Cache LU cannot be removed from the Target becuase either the Direct Linear Map or Chunk Repository Subystems are using it.
0x7100402C The Cache LU cannot be removed from the Target because the number of Requistioned Chunks is not known to be correct.
0x7100402D The VM Region subsystem could not find a Cache List Entry that should be in the LedgerThe VM Region subsystem could not find a Cache List Entry that should be in the Ledger
0x7100402E The VM Region has walked all avialable Cache Lus
0x7100402F The Chunk Repository is out of Chunks.
0x71004030 The Direct Linear Map subsystem found a Invalid Session during a Locate Chunk
0x71004031 The Direct Linear Map subsystem found an Invalid Session during a Locate Chunk
0x71004032 The Chunk Repository subsystem has not allocated any Private Data for the Target LU.
0x71004033 The Chunk Repository subsystem has not allocated any Private Data for a Cache LU.
0x71004034 A VM Reference Cache LU Header operation could not find the region.
0x71004035 A VM Get DLM TOC operation could not find the region.
0x71004036 A VM Release DLM TOC operation could not find the region.
0x71004037 A VM Get Chunk TOC operation could not find the region
0x71004038 A VM Release Chunk TOC operation could not find the region.
0x71004039 A VM operation that accesses the Ledger Catalog has found an EMPTY Catalog.
0x7100403A A VM Release Chunk TOC operation could not find the region.
0x7100403F
An error occurred while trying to perform a SnapView Multi-lun Consistent Mark Operation. The cleanup of the operation failed and further Multi-lun Consistent operations may fail as a result. Manual intervention may be required to resume operations.
0x71004041 The SnapView Multi-lun Consistent operation was not attempted because the maximum number of Multi-lun Consistent operations are already in progress on this array.
0x71004042 The SnapView Multi-lun Consistent operation encountered a problem.
0x71004047 An error occurred while trying to perform a SnapView MLC Start Operation and the attempt to cleanup the operation was successful.
0x71004048 An error occurred while trying to perform a SnapView MLC Start Operation and the attempt to cleanup the started session failed.
0x71004049 An error occurred while trying to perform a SnapView MLC Start Operation. The initialization of the operation failed.
0x7100404A An error occurred while trying to perform a SnapView MLC Start Operation. The cleanup of the operation failed.
0x7100404B An error occurred while trying to perform a SnapView MLC Operation. The cleanup of the operation failed.
Critical Error 0x712AC006 Unable to locate the device. Check that this device exists. (WWN)
0x712AC007 Unable to locate the device. Check that the device with this WWN exists. (WWN)
0x712AC015 A bad block was encountered on the source device. (WWN)
0x712AC018 An attempt has been made to access a device beyond the end of the device. (WWN)
0x712AC01D Unable to access the device. Check cables and zoning. (WWN)
0x712AC01E An attempt to write to a write-protected disk occurred. Correct the attributes of the device and restart the session. (WWN)
0x712AC020 A bad device type was encountered. Check the device to ensure that San Copy supports this device. (WWN)
0x712AC025 This LU will need to be manually trespassed over to the SP that started the session. (WWN)
0x712AC027 The Maximum number of destinations has been exceeded.
0x712AC02A Transfer failed because the Source device is inaccessible from the peer SP. This is probably due to incorrect zoning on the switch or the device is not in the correct storage group. (WWN)
0x712AC02C The specified session already exists.
0x712AC031 The length of the SAN Copy session name is invalid
0x712AC033 The desired LUN cannot be accessed as another host/initiator has reserved it. Please unmount the device before starting the SAN Copy session. (WWN: <wwn>)
0x712AC034 An Initial Copy is required to this Destination
0x712AC035 This Session contains one or more Destinations that require an Initial Copy
0x712AC036 The User Link Bandwidth must be >= 16 kilobits
0x712AC038 The Session cannot be marked if it is active or contains a failed Source or Destinations(s)
0x712AC039 The Session cannot be unmarked if it is active or contains a failed Source or Destinations(s)
0x712AC03A The command failed because the specified Copy Session was not an Incremental Copy Session
0x712AC03F The command failed because one or more failed destinations exist on this SAN Copy Session
0x712AC040 This command cannot be performed on a Marked SAN Copy Session
0x712AC041 This command cannot be performed on an Unmarked SAN Copy Session
0x712AC042 An error occured communicating with SnapView. Please turn off and then back on again the incremental property of this session to resolve the problem. This will results in all destinations requiring a full copy
0x712AC043 An error occured communicating with SnapView. Please turn off and then back on again the incremental property of this session to resolve the problem. This will results in all destinations requiring a full copy
0x712AC044 This command failed because no new destinations exist
0x712AC046 The Session has completed successfully and is in an inconsistent state
0x712AC047 The destination has completed successfully and is in an inconsistent state
0x712AC04A This SAN Copy Session must be started before it can be restarted
0x712AC04C The Incremental property of this SAN Copy Session is being modified. A new destination cannot also be added at the same time
0x712AC04D A SAN Copy Session can only be modified to be InSync is when it is also being modified to be an Incremental SAN Copy Session
0x712AC04E An error occured while removing a SAN Copy Session during the removal of all of them. Make sure the remaining SAN Copy Sessions are not active and try the command again
0x712AC054 The Stop Command failed on copy session <session> on auto-recovery
0x712AC055 Resume of copy session <session> failed on auto-recovery
0x712AC056 Copy session <session> failed due to all paths failure on device with WWN <wwn>
0x712AC059 The OriginatorID specified with the particular command does not match the OriginatorID used to store the SAN Copy Session
0x712AC05A The OriginatorID specified with the particular command is not a valid value
0x712AC05B The maximum number of SAN Copy Sessions that can be consistently marked together has been exceeded
0x712AC05C The FilterID specified with the particular command is not a valid value
Error
0x712A8007 Access denied to the device. Check the connectivity and security attributes of the device. (WWN)
0x712A8008 Not enough memory resources to complete the request. The request can be tried later when the memory become available.
0x712A800C An invalid throttle value was received. The throttle value must be an integer between 1 and 10.
0x712A8017 The source device specified in the session failed. (WWN)
0x712A8018 The following destination device specified in the session failed. (WWN)
0x712A8019 All the destination devices specified in the copy session have failed.
0x712A801F The source device could not be found. This is probably due to incorrect zoning on the switch or the device is not in the correct storage group. (WWN)
0x712A8020 The source LU is not present on the back end. (WWN)
0x712A8021 The destination device could not be found. This is probably due to incorrect zoning on the switch or the device is not in the correct storage group. (WWN)
0x712A8022 An invalid copy configuration was requested. When the source is a frontend device all destination devices must be on the backend..
0x712A8033 A session was active when the Storage Processor (SP) rebooted. The session may be restarted.
0x712AC062 This Copy Session could not be created because the limit of total Sessions for SAN Copy/E has been reached. Delete one or more existing sessions to create another.
0x712AC063 This Copy Session could not be created because the limit of Incremental Sessions for SAN Copy/E has been reached. Delete an existing Incremental Session to create another.
0x712AC064 This Copy Session could not be created. SAN Copy/E does not support destination LUs on the same storage system (WWN: %2) Choose a destination LU on a remote storage system which has SAN Copy installed.
0x712AC065 SAN Copy/E attempted to access a destination device on a storage system without SAN Copy installed, or with a software revision not supported by SAN Copy/E. (WWN: %2).
0x712AC066 SAN Copy/E cannot copy data from a source LUN on a remote storage system.(WWN: %2)
0x712AC067 This configuration is not supported! Either install SAN Copy or uninstall SAN Copy/E immediately!
0x712AC068 SAN Copy does not support specification of CLARiiON or Symmetrix devices by port WWN and LUN. Retry the operation using some other method of device specification.
Warning
0x712A4000 The unbind request failed because the LU is currently being used in an active session. Retry the unbind request after the session completes or is stopped
Information 0x712A000D Copy Command is queued.
0x712A0014 The session cannot be started or modified as it is already active.
0x712A0019 The session failed because either the source or all destinations have failed.
0x712A002B Auto-recovery of the copy session <session> in progress
EMC believes the information in this publication is accurate as of its publication date. The information is subject to change without notice.
THE INFORMATION IN THIS PUBLICATION IS PROVIDED "AS IS." EMC CORPORATION MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND WITH RESPECT TO THE INFORMATION IN THIS PUBLICATION, AND SPECIFICALLY DISCLAIMS IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Use, copying, and distribution of any EMC software described in this publication requires an applicable software license.