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

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

2

Basic Array Features

EMC Navisphere Event Monitor Event Codes Release 19 Technical Note

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.


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.


Critical Error codes — typically require action by you or a support engineer.

3



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.

Navisphere Manager Administrator’s Guide http://powerlink.emc.com/MediumFreq/300-001-

808_A02_elccnt_0.pdf

Navisphere Event Monitor – An Illustrative Overview of CLARiiON Alerting Architecture and Setup

http://avatar.eng.emc.com/docbase/view.asp?type=presentations&doc_identifier=090091038003b1f1&doc_source=DCTM&nav_source=NAVIGATION&doc_title=Navisphere%20Event%20Monitor

White paper - Managing CLARiiON with SNMP http://avatar.eng.emc.com/docbase/view.asp?type=wh

itepapers&doc_identifier=09009103800401

EMC Call Home Template http://www.cs.isus.emc.com/csweb2/dgweb/servicetoo

ls/index.html

4



Event Codes The tables on the following pages include all the events available in Navisphere Event Monitor.


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

5



0x20c5 Event Monitor has encountered the following Critical event, which could not be properly processed.

0x7118C000 Generic CMI Critical Error Code.

6



Error 0x0901 Hard SCSI Error

0x0903 Fan Removed

0x0904 VSC Removed

0x0905 Chassis Overtemperature

0x0906 Unit Shutdown

0x0907 Controller Firmware Panic

0x0908 Hardware Fault - Cache Disabling

0x0909 Cache Dump Failed

0x090A Assign fails - Cache dirty unit

0x090B Controller Cannot initialize cache

0x090C Cache Image Exceeds Memory Size

0x090D BBU or SPS Removed

0x090E BBU Failed

0x090F Cache Recovered with Errors

0x0910 Cache Recovery Failed

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.

0x0920 Hard Media Error

0x0921 Host Vault Load Failed

0x0922 Host Vault Load Inconsistent

0x0923 Host Vault Load Failed Bitmap OK

0x0924 Host Vault Disks Scrambled

0x0925 Single Board Cache; Need PROM Update

0x0926 RAID-3 Unit Cannot Assign - No Memory

0x0927 Old RAID-3 - Can't Assign

0x0928 RAID-3 Initialization Failure - No Memory

7



0x0929 Front End Fibre Link Down

0x0930 PCMCIA Card Write Protected While Active

0x0931 PCMCIA Card Battery Failed

0x0932 PCMCIA Card Absent or Inserted Incorrectly

0x0933 PCMCIA Card POST Test Failed

0x0934 PCMCIA Card Doesn't Match Subsystem, Cache Data Locked

0x0935 PCMCIA Card too small for currently configured write cache

0x0936 PCMCIA Card Hardware Failure

0x0937 Command Failed

0x0938 Invalid RAID Type for RAID 3 Bandwidth

0x0939 Invalid RAID Type to convert

0x0940 BBU Faulted

0x0941 BBU on line

0x0942 Excessive single-bit ECC errors on SP memory module

0x0944 Hard Peer Bus Error

0x0945 Diskmail SP Link Down

0x0946 Diskmail SP Link Down, will suspend peer

0x0947 Diskmail SP Link Down, will suspend self

0x0948 Diskmail SP Link Down, will reboot

0x0949 Illegal UpRev Configuration

0x094A Illegal DownRev Configuration

0x094B Unsupported Unit Type, can't assign

0x094C Can't assign due to Bad Expansion Checkpoints

0x094D Can't assign due Expansion Checkpoints Database Mismatch

0x094F Uncorrectable Verify Error

0x0950 Degraded Powerfail Verify Data Loss

0x0951 CRU Signature Error

0x0952 Single Fan Fault

0x0960 Power Supply A on xPE was removed or faulted

0x0961 Power Supply B on the xPE was faulted or removed

0x0962 Multiple Fan Faults on the xPE

0x0963 Power Supply A AC Failure Detected on the xPE

0x0964 Power Supply B AC Failure Detected on the xPE

0x0966 Cannot enable write cache due to cache dirty unit(s).

0x0967 The storage system cannot write to the cache card because of an IO DMA failure. Please replace the cache card.

8



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.





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

0x2381 Poll failure

0x2480 Disk Failure

0x2481 Fan Failure

0x2482 Power Supply Failure

0x2483 LCC Failure

0x2484 Enclosure Failure

0x2580 Storage system is faulted

9



0x2780 Path to an array is down

0x40008000 The SP must be A or B.

0x40008001 Address is NULL or too long

0x40008002 Header malformed

0x40008003 The layer is not 'U' or 'K'.

0x40008004 No header where header required

0x40008005 Timed out on an internal IO or DeviceIoControl.

0x40008006 The OS did not detect an error, but the number of bytes requested (to read or write) was not the actual number read or written.

0x40008007 Malformed Ack struct - wrong size or bad contents.

0x40008008 Data (usually ModePage or TLD) wrong size, did not checksum, or contained incorrent values.

0x40008009 Ran out of memory

0x4000800A Could not get security from client

0x4000800B data too large to send to kernel proc

0x4000800C not a known modepage to dispatch

0x4000800D don't know this CDB code in Redirector

0x4000800E Redirector client allowed too little buffer, or IOCTL buffer too small

0x4000800F configuration is not complete on the machine

0x40008010 int3, int5, etc

0x40008012 Data size in MManInBufHdr bad. Was trying to get XLU or VARRAY data.

0x40008013 Peer is apparently dead - can't communicate with it.

0x40008014 Unknown AAQ/AAS database ID

0x40008015 Do not support SC VLUs in bind, unbind

0x40008016 PSM LU not initialized

0x40008017 This port value out of range for WWN creation

0x40008018 You cannot expand an LU in the K10 array

0x40008019 Object name illegal or unexpected

0x4000801A Could not access a DLS object.

0x4000801B Attempt to insert driver in wrong place on stack

0x4000801C Could not create and/or access device map file, which is memory mapped.

0x4000801D Memory mapped file too small to hold data

0x4000801E Error using device map file lock/mutex

0x4000801F Operation needs lock, but don't own it

0x40008020 Error closing PSM file

10



0x40008021 Error in WaitForSingleObject, WaitForMultipleObjects or extended versions. This is NOT a timeout.

0x40008022 One or more of the required services is not started

0x40008023 Cannot close a driver handle

0x40008024 Fairness value greater than that supported by system

0x40008025 Unsupported version of an internal structure (incoherent install)

0x40008026 LU Indirection is not supported in Page 37

0x40008027 cannot change MP8 Or RCE bits in hostoptions

0x40008028 You may not change autotrespass via page37 Genral Feat, Param8

0x40008029 You may not use VLU-based trespass with this API

0x4000802A IO is pending, but we are not set for async IO!

0x4000802B Multiple methods of determining the specified LUN yield different results.

0x4000802C Lun count was not the expected value

0x4000802D PSM incorrectly configured. Usually means PSM LUN is an illegal value.

0x4000802E Unable to remove a Page 37 parameter

0x4000802F Mode Page 37 contained an unsupported default.

0x40008030 An input argument was invalid

0x40008031 Array has been booted but the K10 drivers did not start (NDU degraded mode). This is not the same as RAID 5 degradation.

0x40008032 Not allowed to set write cache on PSM LU

0x40008033 Request number of connections exceeded the allowed maximum.

0x40008034 A pointer was expected to be NULL, but wasn't.

0x40008035 A pointer was unexpectedly found to be NULL.

0x40008036 Handle was set to INVALID_HANDLE_VALUE but there was no error (say from GetLastError( ) ).

0x40008037 The PSM LU has double faulted.

0x40008038 An attempt was made to trespass a private LU

0x40008039 Other DeviceIoControl Error. NOT a timeout.

0x4000803A Invalid System Serial Number entered

0x4000803B Logic error

0x4000803C Subrouting failed, see data section for source error.

0x4000803D Expanding a LUN is illegal if there is more than one LUN in the RAID group.

0x4000803E A LUN used by a layered driver cannot be expanded.

0x4000803F The specified LUN is not in the Device Map.

0x40008040 Enabling Write Cache is illegal while NDU is in progress

11



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.

12



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.

0x4100800E A memory allocation failure.

13



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.

14



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).

15



0x71108401 An attempt was made to open a filament with a mailbox name that was already in use.

0x71108402 An attempt was made to send a transmission, receive a transmission, or close a filament with an invalid filament.

0x71108403 A client on the destination did not have a filament open with a mailbox name identical to the sender.

0x71108404 An attempt was made to release a received message that did not exist.

0x71108405 Insufficient system resources existed to complete the transaction.

0x71108406 The specified timeout for a receive operation expired.

0x71108407 The client terminated during UMps initialization.

0x71108408 The client specified a timeout of zero, and the message was not waiting on the synchronously received message queue.

0x71108409 UMps could not open a handle to the MPS device driver.

0x7110840A The destination specified by the send request was unreachable.

0x7110840B The underlying CMI Conduit was not open for communications on the destination.

0x7110840C The MPS device driver experienced an access violation (bad pointer) while attempting to satisfy the request.

0x7110840D An internal UMps error occurred.

0x71108800 The default underlying CMI conduit that MPS uses was already open by a non-MPS component.

0x71108801 A mapping from a kernel status value to the UMps error code did not exist.

0x71108802 A close filament request from UMps did not succeeded synchronously.

0x71108803 Insufficient system resources existed to deliver or receive a message synchronously.

0x71108804 Insufficient system resources existed to close an underlying CMI conduit (unload path).

0x71108805 A message transmission was attempted on a closed underlying CMI conduit.

0x71108806 CMI rejected the request due to invalid buffer size.

0x71108807 Insufficient system resources existed to send a request to CMI.

0x71108808 An unexpected event was received from CMI

0x71108809 MPS received an unexpected version in the MPS level acknowledgement from the peer SP.

0x7110880A The transmission was in an unexpected state when a MPS level acknowledgement arrived.

0x7110880B The transmission was in an unexpected state when a CMI transmission completion event arrived.

16



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.

17



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

18



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

19



0x71118064 A Lock Request could not be found on a list of Request to be timed out



0x71118067 A Lock Request could not be removed from a list of Request to be timed out

0x71118068 A Lock Request could not be removed from a list of Request to be timed out

0x7111806D The Peer sent an Open Lock Request using an invalid Protocol version

0x7111806E The Peer sent an Local Open Reply using an invalid Protocol version

0x7111806F The Peer sent a Close Lock Request using an invalid Protocol version

0x71118070 The Peer sent a Close Lock Reply using an invalid Protocol version

0x71118071 The Peer sent a Convert Request using an invalid Protocol version

0x71118072 The Peer sent a Convert Reply message using an invalid Protocol version

0x71118073 The Peer sent a Convert Conflict using an invalid Protocol version

0x71118074 The Peer sent a Force Mailbox using an invalid Protocol version

0x71118075 The Peer sent a Join Request using an invalid Protocol version

0x71118076 The Peer sent a Join Reply message using an invalid Protocol version

0x71118077 The Peer SP has asked the Local SP to shut down. The Peer will have logged the reason for this request.

0x71118079 The Local SP cannot find the Peer SP's Cabal Registration while processing a Join Cabal Request.

0x7111807A The Local SP cannot find a Cabal Registration while processing a Join Cabal Request.

0x7111807B The Local SP is attemtping to satisfy a request from the Peer SP, but the Local SP operation is illegal.

0x71118081 Illegal Petition Mode assigned to Lock

0x71118082 Illegal Awarded Mode assigned to Lock

0x71118083 Illegal Workorder Mode assigned to Lock

0x71118084 Invalid DLS protocol version

0x71128028 DLU Error 0x8029

0x71138001 UDLS driver could not allocate memory for its Ledger.

0x71138003 UDLS received an unexpected callback from the Distributed Lock Service

0x71138008 The UDLS Bookkeeper has been asked to release an entry while a lock operation is still in progress.

0x71138009 The UDLS Bookkeeper has detected a duplicate operation during a Lock Open.

0x7113800A The UDLS Bookkeeper has cannot add an entry.

0x7113800B The UDLS Bookkeeper has cannot add find an entry.

20



0x7113800C The UDLS Bookkeeper is has detected a duplicate in progress operation.

0x7113800D The UDLS Bookkeeper has been asked to credit an unexpected IoControlCode.

0x7113800E The UDLS Bookkeeper is has detected a duplicate in progress operation.

0x7113800F The UDLS Bookkeeper could not remove an entry.

0x71138010 The UDLS Bookkeeper could not remove an entry.

0x71138011 The UDLS Bookkeeper has been asked to credit an unexpected IoControlCode.

0x71138012 UDLS is being called back from DLS with a NULL Context.

0x71158005 Attempt to use a Persistent Container with an sector size not equal to PSM_EXTENT_SIZE .

0x71158006 Attempt to validate a Persistent Container that is too small to be useful.

0x71158007 The default Persistent Container was found to be neither INCHOATE or COMPLETE.

0x71158008 Unexpected error while reading or writing to Persistent Storage

0x71158009 The PSM Default LU key is missing from the Registry.

0x7115800A The PSM opened a Data Area for Read with no valid information.

0x7115800B The PSM opened a Data Area for Write with no valid information.

0x71168000 DiskTarg unloading (can't access registry).

0x71168001 DiskTarg unloading (can't access TCD).

0x71168002 DiskTarg unloading (can't allocate IRP).

0x71168003 DiskTark unloading (TCD link returned an error).

0x71168004 DiskTarg unloading (Device Object creation failed).

0x71168005 Can't initialize CMM

0x71178000 ScsiTarg unloading (can't start Buffman).

0x71178001 ScsiTarg unloading (can't initialize).

0x71178002 ScsiTarg unloading (no ports found).

0x71178003 ScsiTarg can't claim a port which it was supposed to claim.

0x71178004 ScsiTarg can't use a port which it claimed (can't create an associated device object).

0x71178005 ScsiTarg can't use a port which it claimed (can't create an associated user space link).

0x71178006 ScsiTarg can't use a port which it claimed (can't create an associated mutex).

0x71178007 ScsiTarg can't use a port which it claimed (can't allocate port irp).

0x71178008 ScsiTarg can't use a port which it claimed (miniport status or memory allocation failure).

21



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.

0x71188013 Call to SPID driver never returned.

0x71188014 Call to SPID driver failed.

22



0x71188015 Partition from live peer detected; SP is shutting down.

0x71188016 Invalid Conduit ID.

0x71188017 Null Scatter/Gather entry address.

0x71188018 CMI cannot send Fixed Data until the Conduit's Fixed Data base address is set.

0x71188019 Message requires too many SGL entries to be sent via CMI.

0x7118801A CMI Bundle SGL overflow.

0x7118801B Bundle SGL is inconsistent.

0x7118801C Null ioctl_info_ptr for transmitted message.

0x7118801D Null ioctl_info_ptr for responded-to message.

0x7118801E Could not reset Serial Line.

0x7118801F Could not set Serial Line speed.

0x71188020 Could not get Serial Line speed.

0x71188021 Could not force Serial Line to correct speed.

0x71188022 Could not get Serial Line control settings.

0x71188023 Cannot allocate IRP to read/write Serial Line to peer.

0x71188024 Cannot open Serial Line to peer.

0x71188025 CMI Registry parameter %2\\%3 was not found.

0x71188026 Bad CMI Bundle signature.

0x71188027 Received a Bundle from an unknown SP.

0x71188028 CMI message descriptor is garbled.

0x71188029 Cannot allocate a CMI_WORK_ITEM.

0x7118802A Null ioctl_info_ptr for control message.

0x7118802B Received a control message from an unknown SP ID.

0x7118802C Could not create a worker thread.

0x7118802D Could not obtain an object reference to a worker thread.

0x7118802E Detected a flood of CMI transmissions.

0x71198000 Generic SPID Error Code.

0x71198001 Cannot find HKLM\%2\%3 in Registry.

0x71198002 Invalid SP Signature value: 0x%2.

0x71198003 Undefined Engine Number mechanism variety %2.

0x71198004 Undefined SP Signature mechanism variety %2.

0x71198005 Could not find or read Longbow 1 PROM Resume.

0x71198006 A process deliberately panicked the Storage Processor.

0x71208001 Could not allocate information for Reboot Count read.

0x71228000 Violation of CDS protocol.

23












0x7122800A Violation of CDS protocol.

0x7122800B Violation of CDS protocol.

0x7122800C Violation of CDS protocol.

0x7122800D Violation of CDS protocol.

0x7122800E Violation of CDS protocol.

0x7122800F Violation of CDS protocol.




0x71228017 Corrupted PSM file.

0x71228019 Unexpected result on PSM file write.

0x71238001 Driver does not support this type of SCSI queue tag.

0x71238002 Circular queue that holds asynchronous miniport events is full.

0x71238003 DPC encountered an unexpected async event.

0x71238004 Recovery thread encountered an unexpected event.

0x71238005 Maximum number of outstanding reception blocks allowed has been exceeded.

0x71248001 Unsupported SCSI pass through IOCTL request (<code>)

0x71248002 Could not start rebuild due to invalid MDB on source disk <number>.

0x71248003 Uncorrectable checksum error [primary|secondary] <disk number> at LBA <lba>

0x71248004 MirrorInterpretSenseInfo error on disk <number> Status=<code> <function code> <device code>

0x71248005 Unsupported IOCTL [code or IOCTL name]

0x71248006 Unsupported Internal IOCTL [code or IOCTL name]

0x71248007 Could not allocate [MIRROR_EVENT_INFO | MIRROR_DATABASE (V)].

24



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

25



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.



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.

26



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

27



64K.

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.

28



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.

29



0x71518006 The software package specified does not require a commit.

0x71518007 The software package may not be reverted, either because it has already been committed or because no previous revision is available.

0x71518008 The software package specified is already installed.

0x71518009 The primary SP did not return after an upgrade.

0x7151800A The secondary SP did not return after an upgrade.

0x7151800B The software package will result in a disruptive upgrade, but the perform disruptive upgrade parameter was not specified.

0x7151800C An attempt to save the software package to persistent storage failed.

0x7151800D The requested operation could not be initiated because another operation is in progress.

0x7151800E The specified package has already been committed.

0x7151800F The current version of the specified package must be committed before it may be upgraded.

0x71518010 The NDU software detected an internal state violation.

0x71518011 An SP rebooted unexpectedly.

0x71518012 The specified package may not be uninstalled.

0x71518013 A check script contained in the associated package failed. See the package release notes for details.

0x71518014 Installation of software on the peer SP failed.

0x71518015 Installation of software on the master SP failed.

0x71518016 An attempt to quiesce I/O on the peer SP failed.

0x71518017 An attempt to quiesce I/O on the master SP failed.

0x71518018 An attempt to deactivate software on the peer SP failed.

0x71518019 An attempt to deactivate software on the master SP failed.

0x7151801A An attempt to activate software on the peer SP failed.

0x7151801B An attempt to activate software on the master SP failed.

0x7151801C Required memory could not be allocated

0x7151801D NDU app caught some sort of exception

0x7151801E The user tried to install two revisions of the same package.

0x7151801F Installation will cause an existing dependency to fail.

0x71518020 An attempt was made to upgrade to an older revision of software.

0x71518021 The user tried to install a new package with insufficient disk space on the SPs.

0x71518022 An operation on the secondary SP took too long to complete, and the SP was rebooted to cause a dump.

0x71518023 An attempt to uninstall software on the peer SP failed

30



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)

0x71558004 Failure in getting data from flare

0x71558005 Can not find sg/initiator/rg requested

0x71558006 e.g. wwn length invalid

31



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.


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.

0x76008006 Failure in creating an event.

0x76008007 Failure in closing a handle.

0x76008008 Failure in closing a registry key

32



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.

0x76008103 Found POST error. See message details.

0x76008104 Found OEM error. See message details.

0x76008105 Unknown error record type in NVRAM

33



0x79008000 Unrecog. database ID in header

0x79008001 Unrecog. opcode in header

0x79008002 Invalid item specifier

0x79008003 timeout when waiting for DeviceIoControl.

0x79008004 Wrong version in structure

0x79008005 Size in header of our data does not agree with the size passed in

0x79008006 got bytes returned on a Write ioctl, or read ioctl bytes returned not expected size

0x79008007 could not locate desired obj

0x79008008 operation is not supported

0x79008009 attempt to consume/delete already consumed obj.

0x7900800a attempt to unconsume non-consumed obj.

0x7900800b attempt to consume object that has a layer on it and devicename is of lower (pre-layered) device

0x7900800c Wrong device is being released by hostside

0x7900800d attempt to unconsume obj when not owner

0x7900800e attempt to layer an obj consumer/creator marked NoExtend

0x7900800f attempt to remove/private consume obj with outstanding layers

0x79008010 attempt to remove created device from filter stack

0x79008011 driver reports layering a device which is not that exported by driver below

0x79008012 environmental error writing to local disk (temp files etc)

0x79008013 a required file is not coherent/proper length

0x79008014 mutually exclusive values set in data.

0x79008015 data does not pass consistency check

0x79008016 EMPTY/nonexistant transaction log.

0x79008017 StackOps string malfomed.

0x79008018 Trying to add driver in wrong place on stack

0x79008019 Node we're decrementing not last one in log

0x7900801a See more objects than we can handle

0x7900801b caught int5/3

0x7900801c Driver returned a bad name for a bind object

0x7900801d Driver returned a EMPTY name for a bind object

0x7900801e driver did not use supplied bind name


0x79508001 Unrecognized opcode. This opcode is not implemented and out of range.

0x79508002 Unrecognized item spec.

34



0x79508003 A kernel object exceeded the max timeout for response.

0x79508004 For a Read operation, the data returned is not as expected, i.e. EMPTY data, wrong size, or wrong structure.

0x79508005 The account name supplied is not found on the machine/network.

0x79508006 An input parameter is invalid, e.g. wrong size, EMPTY data.

0x79508007 A reference is already in use.

0x79508008 Attempted to configure non-existent bus.

0x79508009 Attempted to configure non-existent slot.

0x7950800A Incorrect password used.

0x7950800B The security level of the request was not sufficient to authorize this operation.

0x7950800C Cannot unbind the LU.

0x7950800D This error occurs when calls to layered driver databases don't match with request.

0x7950800E This occurs when trying to remove the device creator form the list of filter drivers.

0x7950800F The device map is inconsistant.

0x79508010 For an input TLD list, some data ( TAG, data, field etc.) is missing.

0x79508011 Unrecognised TLD tag.

0x79508012 This error occurs when multiple WWNs in an ATTRIBUTES_SET_BLOCK

0x79508013 This error occurs when an LU is in a virtual array more than once.

0x79508014 Attempting to set a non-existent port, i.e. when setting PreferredLoopId for a port.

0x79508015 Failure on setting host ports, i.e. cannot set preferred loop id for a port

0x79508016 Did not a find an expected driver in a filter stack. Indicates a serious memory or programming problem.

0x79508017 An IOCTL failed, see driver error in data section of event record

0x79508018 Can't get machine name from registry.

0x79508019 Can't get IP addr from registry.

0x7950801A Can't get subnet mask from registry.

0x7950801B Can not get default gateway from registry.

0x7950801C Can't get DHCP flag from registry.

0x7950801D Can't get domain name from registry.

0x7950801E Can't set machine name in the registry.

0x7950801F Can't set IP address in the registry.

0x79508020 Can't set subnet mask in the registry.

35



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.

36



0x80070057

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.

37



0x0868 The update of the SP's copy of the system serial number from the resume PROM has failed. Call your service provider.

0x0869 LCC firmware update failed; LCC continues running at previous revision.

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.

38



0x40004005

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.

0x41004203 PSM file is unreadable.

39



0x41004204 PSM file is EMPTY.

0x41004205 Could not open the PSM file.

0x41004206 Unable to create a file to hold a copy PSM data.

0x41004207 Unable to write the PSM data to a file.

0x41004208 Error reading the PSM file into a buffer.

0x4140 Profile name already in use.

0x4141 Could not update profile.

0x4142 Could not delete profile.

0x4143 Profile not found.

0x4144 Could not parse profile.

0x4145 Could not read profile.

0x4340 Directory database is not found in the PSM. Will try to read from the backup file.

0x4341 Unable to restore the directory from the backup file. Directory provider was started in degraded mode.

0x4342 Directory database is invalid.

0x4344 Failed to create the directory database. Directory provider cannot be started.

0x4640 Warning Audit Log entry.

0x4b40 Creation of transaction object failed.

0x4b41 Exception while locking transaction object.

0x4b42 Exception while executing transaction.

0x4b43 Unable to get the specified instance.

0x4b44 No LUN numbers available.

0x4b45 Exception while processing request.

0x4b46 The indicated name is already in use.

0x4b47 The protected restore resources have not been allocated.

0x4b48 The system does not allow the Fast Recovery option to be disabled on clonegroups.

0x4b49 The number of Source/Clone LUs supplied is more than the maximum allowed limit.

0x4b4a Error occurred while making LU Private.

0x4b4b Error occurred while adding Clonedriver to LU's extended attributes.

0x4D40 Invaild snap clone command.

0x4D41 Over ride needed.

0x4D42 Unexpected clone error occur.

0x4D43 Clone feature object is not available.

40



0x4D44 Clone enabling software is not installed.

0x4D45 Specified CloneGroup is not available.

0x4D46 Specified Clone is not available.

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.

41



0x7111400C The Peer SP has been dismissed. The Peer SP is now a Zombie.

0x7111400D An attempt to send a message to the Peer SP returned a bad status.

0x71124001 DistLockUtilWaitForSemaphore() returned without having acquired the Distributed Semaphore

0x71154001 The Peer SP has exclusive access to the Data Area, will try again.

0x71154002 Could not read and process default Persistent Container.

0x71154003 The Persistent Container for this Data Area was not found.

0x71154004 The Data Area was not found.

0x71154005 An attempt was made to write to a Data Area opened for read only.

0x71154006 An attempt was made to read from a Data Area opened for write only.

0x71154007 An attempt was made to remove a Persistent Container with an open Data Area.

0x71154008 An attempt was made to open an already open Data Area.

0x71154009 An attempt was made to delete an open Data Area.

0x7115400A An attempt was made to add a Persistent Container with the same name as an existing Persistent Container.

0x7115400B An attempt was made to add a Persistent Container with the same name as the default Persistent Container.

0x7115400C An attempt was made to delete the default Persistent Container.

0x7115400D Input buffer has the wring API revision.

0x7115400E An attempt was made to remove a Persistent Container that does not exist.

0x71174000 Creating HostsideConfigData PSM file.

0x71184000 Generic CMI Warning.

0x71184001 Partition from live peer detected; other SP will shut down.

0x71184002 Lost contact with SP ID %2:%3.

0x71184003 Serial Line connection to peer has failed.

0x71204001 The SP has been rebooted unsuccessfully too many times. The K10 Drivers will not load.

0x71214000 The service failed to start, or was stopped. See error text for details

0x71244001 Could not update MDB on disk <disk number>. Rebuild will be attempted.

0x71244002 Disk <number> not ready

0x71244003 Could not update rebuild checkpoint on disk (<disk number>)

0x71244004 Failed to allocate a large/medium/small buffer.

0x71244005 Attempting to reconstruct Primary SectorCount=<count> at LBA <lba> Disk <number>

0x71244006 Attempting to reconstruct Secondary SectorCount=<count> at LBA <lba> Disk <number>

42



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.

0x71324001 SMBus read failed. Error code: <error text>

0x71324002 SMBus write failed. Error code: <error text>

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.

43



0x79504000 First attempt at Rebooting SP failed, using backup method

Information 0x0601 SP Powerup

0x0602 Drive Enabled

0x0603 CRU Unit Rebuild Started

0x0604 CRU Unit Rebuild Completed

0x0605 CRU Unit Rebuild Halted

0x0606 Unit Shutdown for Trespass

0x0607 Unit Shutdown for Change Bind

0x0608 Drive Ready

0x0609 Format Started

0x060A A logical unit has been enabled.

0x0610 Format Failed

0x0611 PROM Revision Loaded on SP Powerup

0x0612 Not Enough Database Drives

0x0613 CRU Unit Equalize Started

0x0614 CRU Unit Equalize Completed

0x0615 CRU Unit Equalize Aborted

0x0617 Disk Module Controller Code Revision Installed

0x0618 CM Expected SP Restart

0x0619 Uncorrectable Verify Error

0x0620 Degraded Nonvol Verify Data Loss

0x0621 Background Verify Started

0x0622 Background Verify Complete

0x0623 Fan Pack Disable/Door Open

0x0624 Fan Pack Enable/Door Close

0x0625 Host Unit Released

0x0626 Unit Shutdown for Unbind

0x0627 FRU Bad Expansion Checkpoint

0x0628 FRU Expansion Revision Mismatch

0x0629 FRU Expansion Checkpoint Rebuild Failed

0x062A 1. Periodic SPS test time. 2. No action needed unless this message is seen more frequently than the periodic SPS Test is setup to run.

44



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.

0x0640 Mirror Reconstructed

0x0641 CRU Unit Rebuild Aborted

0x0642 Background Verify Aborted

0x0643 SP Initializing

0x0644 Peer SP Inserted

0x0645 CRU Bound

45



0x0646 Disk Module Unbound

0x0647 Fuse Bad

0x0648 Termpower Low

0x0649 SPS is not Ready (recharging). No action required unless the SPS never becomes Ready (fully charged).

0x064B User updated WWN Seed. No action required.

0x064C User updated EMC Serial Number. No action required.

0x064D User updated EMC Part Number. No action required.

0x064E Updating DB WWN Seed. No action required.

0x0650 CRU Signature Error

0x0651 Disk obituary was not written successfully to disk.

0x0654 Cache Dumping

0x0655 SPS Enabled - Checking Config. No action required.

0x0656 The engineering debug feature to shorten the SPS Test time has been enabled.

0x0657 Cache Dump Completed

0x0658 Cache Enabling

0x0659 Cache Disabling

0x065A Hi5 L2 Cache Not Enabled.

0x065B Hi5 L2 Cache Not Clean.

0x065C Hi5 L2 Cache Enabled.

0x065D High Availability Cache Vault IS DISABLED.

0x065E High Availability Cache Vault IS ENABLED.

0x0660 AC Power Fail

0x0661 BBU Sniffing Enabled

0x0662 BBU Sniffing Disabled

0x0663 BBU Sniff Initiating

0x0664 BBU Sniff Cache Dump

0x0665 Configured for Single SP

0x0666 Configured for Dual SP

0x0667 Cache Recovering

0x0668 Cache Recovered

0x0669 Bad Termpower Fuse

0x066A Soft Vault Load Failure

0x066B Single Bit Error Detected

0x066C Fan Fault Detected

46



0x066D Peer SP Timed Out

0x066E Dual-SP Communication Error

0x066F Too Much Cache Configured

0x0670 Memory Dump

0x0671 PCMCIA Card Inserted

0x0672 PCMCIA Card Write Enabled

0x0673 PCMCIA Card Cleared by user request

0x0675 Single-bit ECC Error in Write Cache

0x0676 Single-bit ECC Error in Read Cache

0x0677 Cannot use invalid disk type in RAID Group

0x0678 Diskmail SP Link Up, SP will reboot

0x0679 CRU Database Reconstructed

0x067A RAID Group Database Reconstructed

0x067B A rebuild has been started for the database region of a FRU

0x067C A rebuild has completed for the database region of a FRU

0x067D All rebuilds for a FRU have completed

0x067E All equalizes for a FRU have completed

0x0680 Invalid Data Sector Read

0x0681 Invalid Parity Sector Read

0x0682 Invalid Sector Read

0x0683 Data Sector Reconstructed

0x0684 Parity Sector Reconstructed

0x0685 Hard Error

0x0686 Command Complete

0x0687 Stripe Reconstructed

0x0688 Command Dropped

0x0689 Sector Reconstructed

0x068A Uncorrectable Parity Sector

0x068B Uncorrectable Data Sector

0x068C Hard Read Checksum Error

0x068D Soft Read Checksum Error

0x068E Inconsistent Stripe

0x068F Inconsistent Time Stamps

0x0690 Drive Failed

0x0691 Checksum Error on Device Read

47



0x0692 Incoherent Stripe

0x0693 Uncorrectable Stripe

0x0694 Parity Invalidated

0x0695 Uncorrectable Sector

0x0696 Mirror Sector Invalidated

0x0697 XOR failed on read

0x0698 SPS Testing In Progress

0x0699 RAID-3 Memory Size Reduced

0x069A SP-A Read Cache Size Reduced

0x069B SP-B Read Cache Size Reduced

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).

0x06D0 Failover TO Peer Initiated

0x06D1 Local Loop Access for I/O

0x06D2 Peer Loop Access Cancelled

48



0x06D3 SP Failover to Local Loop

0x06D4 Peer SP Sharing Local Loop

0x06D5 SP Using Peer's Remote Loop

0x06D6 SP Failback Failed

0x06D7 Front-end Fibre Reinit Loop

0x06D8 Front-end Fibre Invalid Topology

0x06D9 Front-end Fibre Loss of Sync

0x06DA Front-end Fibre Loss of Signal

0x06DB Front-end Fibre Link Fault

0x06DC Front-end Directed Reset

0x06DD Front-end Retries Exceeded

0x06DE Front-end Fibre LPE Received

0x06DF Front-end Fibre LPB Received

0x06E0 Front-end Fibre Loop Event


0x06E2 Front-end Fibre Loop Error

0x06E3 Fibre Channel Initiator Gone

0x06E4 Fibre Channel Loop Down

0x06E5 Fibre Channel Loop Up

0x06E6 Fibre Channel Loop Timeout

0x06E7 Fibre Channel LIP Timeout

0x06E8 Fibre Channel Link Up Timeout


0x06EA Fibre Loop Initiated

0x06EB Fibre Chip Reset

0x06EC Host Overlapped Command Detected

0x06ED FE Fibre Inbound Frames Dropped

0x06EE Front-end Fibre Soft ALPA

0x06EF Front-end Fibre Hammer FED

0x06F0 Expansion Driver Started

0x06F1 Expansion Driver Finished

0x06F2 Expansion Driver Halted

0x06F3 Expansion Driver Restarted

0x06F4 Expansion Driver Read Failed

0x06F5 Expansion Driver Write Failed

49



0x06F6 Expansion Driver Checkpoint Failed

0x06F7 Expansion Stopped

0x06F8 Log Hardware Error

0x06F9 Soft Peer Bus Error

0x06FA Zero Disk Command Started

0x06FB Zero Disk Command Cancelled

0x06FC Zero Disk Command Completed

0x06FD Expansion Failed

0x06FE Host-SP Resynchronization Fatal Error

0x0712 The write cache is being disabled because the system is shutting down. This message is informational only, no action is necessary.

0x0714 Read cache enabled

0x0715 Read cache disabled

0x0730 Network Initialized

0x0731 Network Configured

0x0732 Network Started

0x0733 Network Stopped

0x0734 Null Network Configuration

0x0735 Telnet Connect 0x%08x

0x0736 Telnet Disconnect 0x%08x

0x0737 Telnet Login Disabled

0x0738 Telnet Login Rejected

0x0739 Telnet Login

0x073A Telnet Service Login

0x073B Telnet Login Max Conns

0x073C Ucast-IP Config Recvd

0x073D Ucast-IP Config Error

0x073E Bcast-UDP Config Recvd

0x073F Bcast-UDP Config Error

0x0740 ICMP Netmask Received

0x0741 ICMP Netmask Timed-Out

0x0742 Duplicate IP Addr 0x%08x

0x0743 Src-Route Attempt 0x%08x

0x0744 Telnet Timeout 0x%08x

0x0745 Telnet Retry Conn 0x%08x

0x0746 Socket Allocation Failed

50



0x0747 Network Init Failed

0x0748 Network Start Failed

0x0749 Network Config Exception

0x074A Network Config Exception

0x074B Network Config Exception

0x074C Network Config Exception

0x074D Network Config Exception

0x074E Network Stack Exception

0x074F LCC Microcode Upgrade status message: %x

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

0x0775 xPE PSA AC Power Fail Testing

51



0x0776 xPE PSB AC Power Fail Testing

0x0777 LCC upgrade complete on enclosure.

0x0778 LCC upgrade complete on all.

0x0779 LCC at rev %x or above on Enclosure:

0x0780 BIOS Revision: xx,xx

0x0781 POST Revision: xx,xx

0x0782 FRUMON Revision: xx,xx

0x0783 Power Supply A AC Failure Detected on the xPE

0x0784 Power Supply B AC Failure Detected on the xPE

0x0785 The SP's copy of the system serial number has been updated from the chassis resume PROM. This is informational only, no action is necessary.

0x0786 Single power supply in incorrect slot.

0x0787 Single SP in incorrect slot.

0x0788 LCC firmware upgrade check starting.

0x0789 LCC firmware update starting.

0x078A Write cache enable pending

0x078B Drive was physically removed from the Slot

0x078C Drive was physically inserted into the Slot

0x078D The user changed the system orientation type from rack mount to desk side or vice versa

0x0791 PCI Memory card was initialized.

0x0792 Clear cache dirty LUN initiated successfully.

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.

0x07A0 Peer alive during conversion.

52



0x07A1 Sniff verify enabled by user.

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

0x4001 Profile already exists.

0x4010 Security Initialized.

0x4011 User has logged in.

53



0x4012 User's password has been changed.

0x4013 New user added.

0x4014 The user's role or password has been modified.

0x4015 User was deleted.

0x4100 Profile already exists.

0x41000000 Starting the governor.

0x41000001 Starting the monitor.

0x41000002 Starting the NDUApp process.

0x41000003 A process that was expected to run to completion, exited.

0x41000004 Process <process name> exited normally, probably in response to user command.

0x41000005 Process <process name> exited with return code <number>

0x41000100 The DumpManager has started and posted the K10App StartupComplete event.

0x41000101 No new dump file was found.

0x41000102 Deleted <Name of DumpFile>

0x41000200 PSMdumper has started.

0x41000201 PSMdumper is exiting.

0x4300 Directory database was created.

0x4301 Local directory will be destroyed because the domain was destroyed by removing the master node.

0x4302 Local directory will be destroyed because the node was removed from the domain.

0x4303 Nodes added to the domain.

0x4304 Nodes removed from the domain.

0x4305 Directory versions did not match. The domain information was retrieved from the master.

0x4306 Change in local system information was detected and reported to the master.

0x4307 New domain was created

0x4308 Local node was assigned to be the Master.

0x4309 Local node was demoted from the Master role because a new master has been assigned.

0x430A New node was assigned to the Master role. The IP Address of the new Master is <ip_addr>.

0x430B Following node was removed from the domain since it is participating in another domain:

0x430C All global data in the domain has been destroyed.

54



0x4400 Legacy agent managed successfully.

0x4401 Legacy agent managed unsuccessfully.

0x4402 Legacy agent unmanaged successfully.

0x4403 Legacy agent unmanaged unsuccessfully.

0x4600 Informational Audit Log entry.

0x4700 <ip_addr> was managed successfully.

0x4740 Could not be managed: <ip_addr>.

0x4901 Retrieved file success. Internal information only.

0x4A00 NAS File Server managed successfully.

0x4A01 NAS File Server managed unsuccessfully.

0x4A02 NAS File Server unmanaged successfully.

0x4A03 NAS File Server unmanaged unsuccessfully.

0x4D00 Management Server - Feature software is not installed or unavailable.

0x4D01 Unexpected error occurred.

0x4D02 Command is not supported.

0x71100000 The MPS device driver started. The compile time and type of build (i.e. debug or retail) are included for debugging purposes.

0x71100001 The MPS device driver received a lost contact event from CMI. The conduit and destination are specified.

0x71100002 The MPS driver unloaded.

0x71100003 The MPS device driver received a handshake IOCTL that causes the MPS device driver to accept requests as a kernel mode DLL.

0x71110002 Distributed Lock Service Driver Entry() has been called.

0x71110003 Distributed Lock Service Export Driver Driver Entry() has returned.

0x71110004 Distributed Lock Service Export Driver has been unloaded.

0x71110005 Distributed Lock Service Export Driver Has been initialized

0x71110006 Enters local SP ID in the System Event Log

0x71110007 Enters local SP ID in the System Event Log

0x71110008 Enters: The local SP is completing a Cabal Join due to the death or absence of the Peer SP in System Event Log.

0x71110009 Obsolete

0x7111000A Obsolete.

0x7111000B Obsolete.

0x7111000C Obsolete.

0x7111000D The Local SP is processing previously delayed Join request from the Peer SP.

0x7111000E The Peer SP died, and is being resurrected.

55



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.

0x7117000C iSCSI Login Denied - Initiator Data: <inititator data> Target Data: <target data>

0x7117000D iSCSI Login - Initiator Data: <initiator data> Target Data: <target data>

0x7117000E iSCSI Logout - Initiator Data: <initiator data> Target Data: <target data>

56



0x7117000F iSCSI Login Failure - Initiator Data: <initiator data> Target Data: <target data>

0x71170010 Connection Log Resources Depleted

0x71180001 Generic CMI Information.

0x71180002 Calling DriverEntry().

0x71180003 My SP ID is %2:%3.

0x71180004 Heartbeat interval is %2 1/10-second ticks.

0x71180005 Peer SP timeout interval is %2 1/10-second ticks.

0x71180006 Remote SP timeout interval is %2 1/10-second ticks.

0x71180007 Peer SP transmission retry limit is %2.

0x71180008 Remote SP transmission retry limit is %2.

0x71180009 CMI Transport Device %2: %3 gate(s) found.

0x7118000A Treating SP ID 0x%2:%3 (Signature 0x%4) as peer

0x7118000B CMI Transport Device %2: Gate %3 connects to SP ID 0x%4:%5 (Signature 0x%6)

0x7118000C Serial Line connection to peer is functioning.

0x7118000D Serial Mail has been disabled in Registry.

0x7118000E Using %2 as Serial Line connection to peer.

0x71190001 Generic SPID Information.

0x71190002 My SP ID is 0x%2:%3, signature is 0x%4.

0x71190003 Found HKLM\\%2\\%3 in Registry; ignoring hardware value.

0x71200002 Reboot Driver Driver Entry() has been called.

0x71200003 Reboot Driver Driver Entry() has returned.

0x71200004 Reboot Driver Export Driver has been unloaded.

0x71200005 Deleting the Reboot Driver's Device Object.

0x71230002 Compiled on %2 at %3, %4.

0x71230003 DriverEntry() returned %2.

0x71230004 Unloaded.

0x71240001 Crash dumps disabled - <partition device object>. Contact your service provider.

0x71240002 Rebuild completed on disk <number>

0x71240003 Port driver supports larger maximum transfer length, Increase from <current value> to <suggested max transfer length>

0x71240004 Rebuild starting on disk <number>

0x71240005 Rebuild stopping due to unit state change <disk number> (LBA x)

0x71240006 Rebuild stopping source <disk number> dead (LBA x)

57



0x71240007 Rebuild stopping destination <disk number> dead (LBA x)

0x71240008 Login event received for disk <number>

0x71240009 Logout event received for disk <number>

0x7124000A Logout event received for disk <number> ignored

0x7124000B Remove (disk dead) event received for disk <number>

0x7124000C Remove (disk dead) event received for disk <number> ignored

0x7124000D Device failed event received for disk <number>

0x7124000E Device failed event received for disk <number> ignored

0x7124000F NT Mirror Driver Compiled on <date> <time> Free (Retail) [or Checked (Debug)] Build <build string>

0x71240010 DriverEntry() exiting with status <code>.

0x71240011 DiskState change for disk <number> from <previous> to <current>.

0x71240012 Unsupported FT IOCTL (<ioctl value>)-OR -Internal information only. Unsupported IOCTL (<ioctl value>) to port driver

0x71240013 Unsupported IOCTL (<ioctl value>) Status (<completion status>)

0x71240014 Creating root partition <string name> P=<disk number> S=<disk number>

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.

58



0x7127079B Attempt to clear cache dirty unit %x has failed. The peer SP is booting up.

0x71320002 Compiled on <data>

0x71320003 DriverEntry() returned <load status>

0x71320004 Driver unloaded

0x71370002 MetaLUN Created: <lun number>.

0x71370003 MetaLUN Destroyed: <lun number>.

0x71370004 MetaLUN Stripe Expansion Started: <lun number>.

0x71370005 MetaLUN Stripe Expansion Halted: <lun number>.

0x71370006 MetaLUN Stripe Expansion Completed: <lun number>.

0x71370007 MetaLUN Stripe Expansion Queued: <lun number>.

0x71370008 MetaLUN Concatenation Completed: <lun number>.

0x71370009 The size of the given MetaLUN has been modified by a layered driver. This is expected behavior and not an error.

0x71380002 GLD Driver Entry.

0x71380003 GLD Driver Unload.

0x71380004 GLD Configuration Initialized.

0x71380005 GLD Volume Created: <device name>.

0x71380006 GLD Volume Destroyed: <device name>.

0x713F0002 Driver Entry Complete. Status returned: <DriverEntry() status>

0x71451002 ID Manager. Driver started. version %x

0x71451003 ID Manager. Driver stopped. version %x

0x71451004 ID Manager. Lun Id changed Old ID: %x, New Lun ID: %x

0x71570001 Generic migration informational message

0x71570002 Migration volume Created: <lun number>

0x71570003 Migration volume Destroyed: <lun number>

0x71570004 Migration Started: <lun number>

0x71570005 Migration Halted: <lun number>

0x71570006 Migration Completed: <lun number>

0x71570007 Migration Queued: <lun number>

0x71570008 The user successfully canceled an individual migration session.

0x71570009 The size of the given Migration LUN has been modified by a layered driver. This is expected behavior and not an error.

0x76000002 A problem with LUN feature configuration has been corrected.

0x76000100 DGSSP app started/stopped

0x76000101 Lists the BIOS date and revision.

59

MirrorView


0x79500000 Rebooting SP

MirrorView

Critical Error No Entries

Error 0x71050151 User requested a force promote for CG %2. CG will be out-of-sync.

0x71058000 Invalid database ID detected in admin DLL

0x71058001 Invalid operation code detected in admin DLL

0x71058012 This array has the primary image for the specified mirror. Promote remote images at the specific array.

0x71058022 The LU specified for the write intent log is already in use.

0x71058028 Could not access mirroring device

0x71058029 Request to create a mirror specifies an invalid LU ID value

0x7105802A Request to add secondary image does not specify a mirror ID

0x7105802B Request to add a secondary image does not specify the image to add

0x7105802C Request to add a secondary image specifies an invalid LU ID value

0x7105802D Request to get mirror properties specifies an invalid mirror ID

0x7105802E Request to get image properties specifies an invalid mirror ID

0x7105802F Request to get image properties specifies an invalid image ID

0x71058030 Request to promote a secondary image specifies an invalid array ID for the old primary

0x71058031 Request to promote a secondary image specifies an invalid array ID for the new primary

0x71058032 Request to destroy a mirror specifies an invalid mirror ID

0x71058033 Request to define write intent logs specifies an invalid LU ID for SP A

0x71058034 Request to define write intent logs specifies an invalid LU ID for SP B

0x71058035 Request to set mirror properties specifies an invalid mirror ID

0x71058036 Request to remove a secondary image specifies an invalid mirror ID

0x71058037 Request to remove a secondary image specifies an invalid ID for the target image

0x71058038 Request to fracture a secondary image specifies an invalid mirror ID

0x71058039 Request to fracture a secondary image specifies an invalid ID for the target image

0x7105803A Request to synchronize a secondary image specifies an invalid mirror ID

60

MirrorView


0x7105803B Request to synchronize a secondary image specifies an invalid ID for the target image

0x7105803C Request to set image properties specifies an invalid mirror ID

0x7105803D Request to set image properties specifies an invalid image ID

0x7105803E An invalid name was specified for a mirror

0x7105803F An invalid description was provided for a mirror

0x71058040 An invalid role (primary or secondary) was specified

0x71058041 An invalid state was specified

0x71058042 An invalid recovery policy was specified

0x71058043 An invalid image condition was specified

0x71058044 An invalid value for the synchronization delay was specified

0x71058045 An invalid value for the preferred SP was specified

0x71058047 No synchronization delay value was specified for an image

0x71058049 Mirror property set to use write intent log, but write intent log not allocated.

0x7105804A Request to destroy a mirror failed as we could not halt I/O to the mirror

0x7105804B Request to quiesce an LU failed

0x7105804C Request to unquiesce an LU failed

0x7105804D Request to unquiesce the Mirror failed

0x7105804E Remote Mirroring User Admin Lib Consistency Group create request not found.

0x7105804F Remote Mirroring User Admin Lib Consistancy Group Name not found.

0x71058050 Remote Mirroring User Admin Lib Consistency Group Create illegal name.

0x71058051 Remote Mirroring User Admin Lib Consistency Group Create illegal description.

0x71058052 Remote Mirroring User Admin Lib Consistency Group Create Group illegal recovery policy .

0x71058053 Remote Mirroring User Admin Lib Consistency Group Promote request not found.

0x71058054 Remote Mirroring User Admin Lib Consistency Group Promote Group ID not found.

0x71058055 Remote Mirroring User Admin Lib Consistency Group Promote group illegal group ID.

0x71058056 Remote Mirroring User Admin Lib Consistency Group Promote group illegal promote type.

0x71058057 Remote Mirroring User Admin Lib Consistency Group Destroy request not found.

61

MirrorView


0x71058058 Remote Mirroring User Admin Lib Consistency Group Destroy group id not found.

0x71058059 Remote Mirroring User Admin Lib Consistency Group Destroy group illegal group id.

0x7105805A Remote Mirroring User Admin Lib Consistency Group Destroy group illegal override flag.

0x7105805B Remote Mirroring User Admin Lib Consistency Group Fracture request not found.

0x7105805C Remote Mirroring User Admin Lib Consistency Group Fracture group id not found.

0x7105805D Remote Mirroring User Admin Lib Consistency Group Fracture group illegal group id.

0x7105805E Remote Mirroring User Admin Lib Consistency Group Sync request not found.

0x7105805F Remote Mirroring User Admin Lib Consistency Group Sync group id not found.

0x71058060 Remote Mirroring User Admin Lib Consistency Group Sync group illegal group id.

0x71058061 Remote Mirroring User Admin Lib Consistency Group Set Property illegal group id.

0x71058062 Remote Mirroring User Admin Lib Consistency Group Set Properties request not found.

0x71058063 Remote Mirroring User Admin Lib Consistency Group Set Properties illegal group name.

0x71058064 Remote Mirroring User Admin Lib Consistency Group Set Properties illegal group description.

0x71058065 Remote Mirroring User Admin Lib Consistency Group Get Properties request not found.

0x71058066 Remote Mirroring User Admin Lib Consistency Group Get Properties group id not found.

0x71058067 Remote Mirroring User Admin Lib Consistency Group Get Properties illegal group id.

0x71058068 Remote Mirroring User Admin Lib Consistency Group Add Member request not found.

0x71058069 Remote Mirroring User Admin Lib Consistency Group Add Member Group Id not found.

0x7105806A Remote Mirroring User Admin Lib Consistency Group Add Member illegal group id.

0x7105806B Remote Mirroring User Admin Lib Consistency Group Add Member Mirror Id not found.

62

MirrorView


0x7105806C Remote Mirroring User Admin Lib Consistency Group Add Member illegal mirror id.

0x7105806D Remote Mirroring User Admin Lib Consistency Group Add Member LU Id not found.

0x7105806E Remote Mirroring User Admin Lib Consistency Group Add Member illegal LU id.

0x7105806F Remote Mirroring User Admin Lib Consistency Group Remove Member request not found.

0x71058070 Remote Mirroring User Admin Lib Consistency Group Remove Member Group Id not found.

0x71058071 Remote Mirroring User Admin Lib Consistency Group Remove Member illegal group id.

0x71058072 Remote Mirroring User Admin Lib Consistency Group Remove Member Mirror Id not found.

0x71058073 Remote Mirroring User Admin Lib Consistency Group Remove Member illegal mirror id.

0x71058074 Remote Mirroring User Admin Lib Consistency Group Remove Member LU Id not found.

0x71058075 Remote Mirroring User Admin Lib Consistency Group Remove Member illegal LU id.

0x71058076 Remote Mirroring User Admin Lib Consistency Group Remove Member illegal override flag.

0x71058077 Remote Mirroring User Admin Lib Consistency Group Set Properties Group Id not found.

0x7105807C Consistency Groups has failed to fracture group %2 with status %3

0x7105807D Consistency Groups has failed to set group properties with status %2

0x71058100 Unable to either complete or back out of a bind operation

0x71058101 Unable to either complete or back out of a rebind operation

0x71058102 Unable to complete an unbind operation

0x71058103 Unable to either complete or back out of a create mirror operation

0x71058104 Failed to add a secondary image to a mirror

0x71058106 Unable to allocate memory during the update of a mirror

0x71058107 Unable to allocate memory required to commit changes

0x71058109 Invalid response returned from remote K10 from a create mirror request

0x7105810A Invalid response returned from a remote K10 from a destroy mirror request

0x7105810B Invalid response returned from peer SP from a create mirror request

0x7105810C Invalid response returned from peer SP from a destroy mirror request

63

MirrorView


0x7105810D Invalid response returned from peer SP from a mirror update request

0x7105810E Invalid response returned from peer SP from a get consumable request

0x7105810F Invalid response returned from peer SP from a set driver properties request

0x71058110 Invalid response returned from peer SP from an update state request

0x71058112 The K10 hosting the primary image is unavailable

0x71058113 Invalid revision in create mirror request received from remote K10

0x71058114 Invalid revision in destroy mirror request received from remote K10

0x71058115 Invalid revision in promotion request received from remote K10

0x71058116 Invalid revision in update mirror request received from remote K10

0x71058117 Invalid revision in create mirror request received from peer SP

0x71058118 Invalid revision in destroy mirror request received from peer SP

0x71058119 Invalid revision in update mirror request received from peer SP

0x7105811A Invalid revision in set driver properties request received from peer SP

0x7105811B Invalid revision in stage update request received from peer SP

0x7105811C Failed to remove the specified image from the mirror, as it is the primary image

0x7105811D The 'staged update' pointer was not NULL when it should have been

0x7105811E A request to bind mirroring into a device stack specified a buffer of invalid size

0x7105811F A request to bind mirroring into a device stack specified a buffer with an invalid revision

0x71058120 A request to unbind mirroring from a device stack specified a buffer of invalid size

0x71058121 A request to unbind mirroring from a device stack specified a buffer with an invalid revision

0x71058123 A request to enumerate objects specified a buffer of invalid size

0x71058124 A request to enumerate objects specified a buffer with an invalid revision number

0x71058125 A request to get generic object properties specified a buffer of invalid size

0x71058126 A request to get generic object properties specified a buffer with an invalid revision

0x71058127 A request to create a mirror specified a buffer of invalid size

0x71058128 A request to create a mirror specified a buffer with an invalid revision

0x71058129 A request to destroy a mirror specified a buffer of invalid size

0x7105812A A request to destroy a mirror specified a buffer with an invalid revision

0x7105812B A request to enumerate mirrors specified a buffer of invalid size

64

MirrorView


0x7105812C A request to enumerate mirrors specified a buffer with an invalid revision

0x7105812D A request to add a secondary image specified a buffer of invalid size

0x7105812E A request to add a secondary image specified a buffer with an invalid revision

0x7105812F A request to remove a secondary image specified a buffer of invalid size

0x71058130 A request to remove a secondary image specified a buffer with an invalid revision

0x71058131 A request to fracture an image specified a buffer of invalid size

0x71058132 A request to fracture an image specified a buffer with an invalid revision

0x71058133 A request to synchronize an image specified a buffer of invalid size

0x71058134 A request to synchronize an image specified a buffer with an invalid revision

0x71058135 A request to get mirror properties specified a buffer of invalid size

0x71058136 A request to get mirror properties specified a buffer with an invalid revision

0x71058137 A request to set mirror properties specified a buffer of invalid size

0x71058138 A request to set mirror properties specified a buffer with an invalid revision

0x71058139 A request to get image properties specified a buffer of invalid size

0x7105813A A request to get image properties specified a buffer with an invalid revision

0x7105813B A request to set image properties specified a buffer of invalid size

0x7105813C A request to set image properties specified a buffer with an invalid revision

0x7105813D A request to enumerate available objects specified a buffer of invalid size

0x7105813E A request to enumerate available objects specified a buffer with an invalid revision

0x7105813F A request to promote a secondary image specified a buffer of invalid size

0x71058140 A request to promote a secondary image specified a buffer with an invalid revision

0x71058141 A request to set driver properties specified a buffer of invalid size

0x71058142 A request to set driver properties specified a buffer with an invalid revision

0x71058143 A request to get driver properties specified a buffer of invalid size

0x71058144 A request to get driver properties specified a buffer with an invalid revision

0x71058145 A request to halt I/O to a mirror specified a buffer of invalid size

0x71058146 A request to halt I/O to a mirror specified a buffer with an invalid

65

MirrorView


revision

0x71058147 A request to shut down mirroring specified a buffer of invalid size

0x71058148 A request to shut down mirroring specified a buffer with an invalid revision

0x71058149 A request to fake a lost contact event specified a buffer of invalid size

0x7105814A A request to fake a lost contact event specified a buffer with an invalid revision

0x7105814B A request to modify debug parameters specified a buffer of invalid size

0x7105814C A request to modify debug parameters specified a buffer with an invalid revision

0x7105814D A request to get performance data specified a buffer of invalid size

0x7105814E A request to get performance data specified a buffer with an invalid revision

0x7105814F An unrecognized request was made to the mirroring driver

0x71058150 Received a request from our peer SP to update a mirror which is unknown to us

0x71058151 Insufficient memory to stage the update from our peer SP

0x71058152 Invalid response returned from remote K10 from a promote image request

0x71058153 Promotion failed, since the old mirror couldn't be deleted and recreated.

0x71058154 Failed to request remote K10 to create a mirror

0x71058155 Failed to request remote K10 to destroy a mirror

0x71058156 Failed to request remote K10 to update a mirror

0x71058157 Failed to request our peer SP to create a mirror

0x71058158 Failed to request our peer SP to destroy a mirror

0x71058159 Failed to request our peer SP to update a mirror

0x7105815A Failed to request our peer SP to get consumable info

0x7105815B Attempt to ping a remote K10 failed

0x7105815C Attempt to ping primary K10 for a mirror failed

0x7105815D Failed to request our peer SP to update driver properties

0x7105815E Failed to request our peer SP to stage update information

0x7105815F Failed to request remote K10 to promote an image

0x71058161 Can't deallocate driver properties (write intent logs) as there are none allocated

0x71058162 Failed to promote a secondary image. The new primary K10 has no write intent logs defined, but the mirror is configured to use the WIL.

0x71058163 Failed to commit an update on our peer SP

0x71058164 Failed to stage updated data to our peer SP

66

MirrorView


0x71058166 Attempted to stage an update while another update is still (apparently) in progress

0x71058167 No memory available to complete a local update

0x71058168 Failed to stage local update information to our peer SP

0x71058169 Failed to commit local update information on our peer SP

0x7105816A An update can't be propagated to a remote K10 as it is currently unreachable

0x7105816B Invalid size or revision received from our peer SP in response to a quiesce request

0x7105816C Failed to send a quiesce request to our peer SP

0x7105816E Failed to quiesce one or more LUs on the local SP

0x7105816F Invalid revision on a request from our peer SP to quiesce an LU.

0x71058170 A quiesce request received from our peer SP failed

0x71058171 A request to our peer SP to quiesce one or more LUs failed

0x71058172 Failed to open PSM LUN during Admin initialization

0x71058173 Failed to enumerate the current list of objects

0x71058174 Failed to enumerate the current list of mirrors

0x71058175 Failed to get driver properties

0x71058176 Failed to get the generic properties of an object

0x71058177 Failover manager could not create a new mirror

0x71058178 Config manager could not add a new mirror

0x71058179 Failed to obtain current progress of an image synchronization

0x7105817A Database subsystem initialization failed

0x7105817B Failed to read current list of consumables during database subsystem initialization

0x7105817C Failed to read current list of mirrors during database subsystem initialization

0x7105817D Problem encountered attempting to update a remote mirror

0x7105817E Buffer supplied to modify debug read is inadequate

0x7105817F Revision ID supplied to modify debug read is incorrect

0x71058180 Maximum mirrors already exist on the system

0x71058181 The maximum number of mirrors are already using the write intent on this system

0x71058182 Maximum number of mirrors on the system where secondary was to be located

0x71058183 Maximum number of mirrors are already using write intent on this system

67

MirrorView


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.

68

MirrorView


0x710581A0 A secondary image for this mirror ID already exists on this array.

0x710581A5 Opening WIL failed, status: %2.

0x710581A8 Get Image LU properties failed due to revision problem. Should be internal bug not seen by customer.

0x71058200 Could not add all existing mirrors to the failover manager's watch list on driver startup

0x71058201 Could not add all existing mirrors to the config manager's lists on driver startup

0x71058202 An invalid image phase was detected while we were attempting to schedule an image synchronization

0x71058203 An unexpected fail status was returned by the mirror manager when we attempted to start an image synchronization

0x71058204 An unrecognized image condition was detected

0x71058205 Failed to locate the target mirror during a trespass operation

0x71058207 Failed to find an image in the mirror data structure, when it should have existed

0x71058208 The config manager generated an invalid bucket number

0x71058209 Unexpected error updating the config manager's hash table

0x7105820A Insufficient memory available to add a new mirror

0x7105820B Invalid image state detected during an add secondary operation

0x7105820C Unrecognized mirror operation detected while setting initial image state

0x7105820D Failed to gain exclusive access to the mirror during a destroy operation

0x7105820E Failed to gain exclusive access to the mirror during an add/remove secondary operation

0x71058210 Unknown image condition detected during an administrative fracture operation

0x71058211 The mirror manager unexpectedly failed during a fracture operation

0x71058212 Unknown image condition detected during a synchronize operation

0x71058213 A synchronization operation failed with an unexpected status

0x71058214 Unexpected failure while fracturing an image following a media failure on the secondary

0x71058215 Unrecognized state value detected during an attempted state change

0x71058216 Unexpected image condition detected while handling an image becoming unreachable

0x71058217 Unexpected image condition detected while handling an image becoming reachable

0x71058218 Insufficient memory to process a state change of a remote K10

0x7105821A Insufficient memory available to process completion of a sync I/O

69

MirrorView


0x7105821B Insufficient memory available to process a media failure error

0x7105821C Failed to locate a mirror for which we're attempting to handle a media failure

0x7105821D Insufficient memory available to handle an incoming write request

0x7105821E Failed to locate mirror for an incoming write request. Indicates an internal driver consistency failure

0x7105821F Insufficient memory available to handle a synchronization state update

0x71058220 Insufficient memory available to handle completion of a synchronization operation

0x71058221 Insufficient memory available to take ownership of a mirror

0x71058222 Unrecognized reason code detected while attempting to take ownership of a mirror

0x71058223 Failed to locate the target mirror during a trespass operation

0x71058224 Invalid image condition detected during a trespass operation

0x71058225 Failed to locate the target mirror while processing a failure of our peer SP

0x71058226 Invalid image phase detected while taking control of an image

0x71058227 Invalid image condition detected while handling a failure of our peer SP

0x71058228 Unrecognized image state value detected internally

0x71058229 Insufficient memory available to give up control of a mirror

0x7105822A Failed to locate the mirror we're attempting to give away

0x7105822D Invalid image state detected while handling a mirror failure

0x7105822E Unexpected image phase detected while attempting to add an synchronization request

0x7105822F Unrecognized image state detected while preparing to fracture an image

0x71058230 Attempted to schedule synchronization of an already synchronized image

0x71058231 Attempt to create a mirror with too many pieces (LUNs) in the primary image

0x71058232 Attempt to create a mirror with too many pieces (LUNs) in the secondary image

0x71058233 Can't remove the mirroring driver from an LU's stack, as it is currently part of a mirror

0x71058235 Can't remove the mirroring driver from an LU's stack, as it is currently synchronizing

0x71058236 Can't find a mirror data structure during a shutdown request

0x71058237 Failed to locate an expected image in our internal data structures

0x71058238 Can't fracture an image as we're not the primary K10 and/or controlling SP for the mirror

0x71058239 Image is already administratively fractured

70

MirrorView


0x7105823A Can't administratively fracture the image due its image condition

0x7105823B Can't start synchronization as we're not the primary K10 and/or controlling SP for the mirror

0x7105823C Can't start synchronization from the current image condition

0x7105823D Mirror not found in config manager's database

0x7105823E Image not found in the specified mirror

0x7105823F The local array is not the primary K10 for the mirror

0x71058240 Unable to generate a unique name for an exported device

0x71058243 Attempt to destroy a mirror which still has at least one secondary image

0x71058244 Attempt to destroy a mirror for which we're not the primary K10

0x71058245 Mirroring driver is currently operating in degraded mode after a previous failure

0x71058246 A remote image is marked as in-sync, but has a stale cookie

0x71058247 Attempt to remove a secondary image while it is being synchronized

0x71058248 A secondary image reported a media failure

0x71058249 Attempt to sync an image that is inactive

0x7105824A Cannot remove the image it is queued to be synchronized. Fracture the image prior to attempting to remove.

0x7105824B Cannot destroy the mirror the primary image is still active. Manually deactivate the mirror and attempt to destroy again.

0x7105824C The size of the secondary LU is not the same size as the primary image LU.

0x7105824D Unable to remove the consistent image. Fracture the image prior to removal.

0x7105824E UID of the secondary image to be promoted is not local to this array.

0x71058250 The array has exceeded its allowable number of Consistency Groups.

0x71058251 The Consistency group to be destroyed has members so it cannot be destroyed.

0x71058252 The Mirror Image associated with the Lun is already a member of this Consistency Group.

0x71058253 Mirror Image is already part of another Consistency Group. Dual membership is not allowed.

0x71058254 The Consistency Group has reached its mirror membership limit.

0x71058255 The Consistency Group is in a Scrambled state. Repair group state before adding members.

0x71058256 The Consistency Group is in an incomplete state.

0x71058257 The Consistency Group is in a local only state.

0x71058258 The Consistency Group is in a out-of-sync state.

71

MirrorView


0x71058259 The Consistency Group is in a synchronizing state.

0x7105825A The Consistency Group is in an invalid state.

0x7105825B Mirror in a Consistency Group can not have two secondary images.

0x7105825C Mirror cannot be removed from a Consistency Group if it is not a member of this group.

0x7105825D This CG operation failed because the CG has an invalid locality.

0x7105825E This CG operation failed because the CG is in non-active condition.

0x7105825F The role of the corresponding group on secondary array is not secondary.

0x71058260 The Secondary Consistency Group has reached its mirror membership limit.

0x71058261 A participating array has exceeded its allowable number of Consistency Groups.

0x71058262 Mirror Image on the remote array is already part of a Consistency Group. Dual membership is not allowed.

0x71058263 Mirror could not be found in the mirror database on the remote array.

0x71058300 Failed to store an updated administrative action count to PSM

0x71058301 Failed to store updated driver properties to PSM

0x71058302 Insufficient memory available to add a new consumable

0x71058304 Insufficient memory available to write consumables list to PSM

0x71058305 Insufficient memory available to read consumables list from PSM

0x71058306 Unrecognized revision number for consumables list in PSM

0x71058307 Incorrect amount of data read from PSM for consumables list header

0x71058308 Incorrect amount of data read from PSM for a consumable item

0x71058309 Mirrorview dateabaseInit failed degrading driver status=71058309. MirrorView was unable to access PSM LUN; reboot the SP.

0x7105830A Database manager's mirror data structure has an unexpected size

0x7105830B Unable to find mirror with the specified ID

0x7105830C Unable to find an image with the specified ID in the given mirror

0x7105830D Unable to find the specified exported device based on its name

0x7105830E Unable to find the specified exported device based on its WWID

0x7105830F Unable to initialize the database manager from PSM

0x71058310 Insufficient memory available to read mirroring driver data from PSM

0x71058311 Incorrect number of bytes returned while reading driver version info from PSM

0x71058312 Incorrect number of bytes returned while reading driver information from PSM

0x71058313 Unrecognized revision of driver information read from PSM

72

MirrorView


0x71058315 Failed to write driver information to PSM

0x71058316 Insufficient memory available to write driver information to PSM

0x71058319 Failed to increment administrative action count

0x7105831A Failed to set write intent log partitions

0x7105831B Write intent log partitions are not currently defined

0x7105831D Insufficient memory to add a new mirror

0x7105831E NULL pointer detected while attempting to remove a mirror from the global list

0x7105831F NULL pointer detected while attempting to delete a mirror

0x71058321 Insufficient memory available to write mirror data area to PSM

0x71058322 Error writing mirror data area to PSM

0x71058323 Insufficient memory available to read mirror data area from PSM

0x71058324 Insufficient memory available to read mirror data area from PSM

0x71058325 Failed to read complete mirror data area from PSM

0x71058326 Insufficient memory available to list PSM contents

0x71058327 Failed to read mirror data area from PSM

0x71058328 Failed to list contents of PSM

0x71058329 Failed to open PSM device

0x7105832A Failed to locate mirror data area(s) in PSM

0x7105832B Failed to retrieve number of existing entries from PSM

0x7105832C Open of PSM mirror data area failed

0x7105832D Failure attempting to read mirror data area from PSM

0x7105832E Incorrect amount of data read from consumables database, and the version number on the data is incorrect

0x7105832F Memory budget already exceeded during driver initialization

0x71058334 Detected an incomplete write of driver data header information to PSM

0x71058335 Detected an incomplete write of driver data to PSM

0x71058336 Unable to either commit data to PSM or roll back operation during mirror creation

0x71058337 Failed to write mirror data area to PSM

0x71058338 Failed to write version info for mirror data area to PSM

0x71058339 Detected an incomplete read of the mirror data area version info

0x7105833A Unrecognized revision read from PSM mirror data area

0x7105833B Unable to find a local image of the specified mirror

0x7105833C Failed to close a PSM data area

0x7105833D Unable to open WIL LU

73

MirrorView


0x7105833E Unable to open WIL LU

0x7105833F Unable to set the compatibility mode, driver will be degraded. Need to reboot the SP

0x71058340 Unable to load mirror during rollback, driver will be degraded. Reboot the SP.

0x71058341 Creating mirror during MirrorView rollback

0x71058342 Possible problem with PSM during rollback


0x71058344 Inside rollback code for PSM

0x71058345 PSM contents NULL when attempted to read

0x71058346 Attempting to rollback and mirror list EMPTY when should have an entry.

0x71058347 Attempting to rollback and mirror list EMPTY when should have an entry.

0x71058348 Unable to remove mirror during rollback

0x71058349 Wrong number of mirrors to be adjusted

0x7105834A Unable to open PSM during rollback

0x7105834B Found two aread in PSM we can't open, so unable to proceed with rollback

0x7105834C Unable to open PSM during rollback to add a mirror

0x7105834D Unable to close PSM aread during rollback

0x7105834E Unable to read from PSM during rollback

0x7105834F Unable to read from mirror data area during rollback

0x71058350 Attempting to read the mirror data area during rollback and unable to allocate memory

0x71058351 Attempting to read the mirror data area during rollback and unable to allocate memory

0x71058352 Unable to open PSM area during rollback

0x71058353 During read of PSM in rollback incorrect number of bytes returned

0x71058354 During read of PSM during rollback incorrect revision number

0x71058355 Failure in reading PSM during rollback

0x71058356 Failure to read correct number of bytes during rollback

0x71058357 Unable to add mirror during rollback

0x71058358 Unable to add mirror during rollback

0x71058359 Unable to update config during rollback

0x7105835A Attempted to add more than one mirror during rollback

0x7105835B Unable to determine number of mirrors during rollback

74

MirrorView


0x7105835F Consistency Groups initialization failed. Group services are not available.

0x71058360 Consistency Groups is now in degraded mode due to status %2. Group services are disabled until reboot.

0x71058361 The Consistency Group memory is mismatched between SPs.

0x71058362 The Consistency Group operation fails when updating peer.

0x71058363 Mirror could not be found in the mirror database on the remote array. Check if the mirror was destroyed or promoted on the remote array.

0x71058400 Corrupted hashtable detected in the failover manager

0x71058401 Consistency failure detected while updating failover manager data structures

0x71058402 Corrupted hashtable detected in the failover manager

0x71058403 Unexpected fail status while setting up a ping of an unreachable K10

0x71058404 Unexpected fail status while setting up a ping of an unreachable SP

0x71058405 Failed to locate the necessary mirror data structures while refreshing the cookie

0x71058406 Internal consistency failure with the transport mechanism while refreshing the cookie

0x71058407 Received a ping response for an unknown mirror

0x71058408 Internal consistency failure in failover manager's handling of pings

0x71058409 Internal consistency failure in failover manager's handling of pings

0x7105840A Internal consistency failure in failover manager's handling of pings

0x7105840B Ping response version is incompatible with the ping request

0x7105840C Unrecognized event type for incoming ping request

0x7105840D Unrecognized event type for incoming ping response

0x7105840E Insufficient memory to obtain reference to K10/mirror pair in failover manager

0x7105840F Insufficient memory for new element in K10 activity table

0x71058410 Failure to locate K10 in the K10 activity table

0x71058411 Failure to insert K10 in K10 activity table

0x71058412 Failed to locate mirror in the K10 activity table

0x71058413 Failed to locate K10 in the K10 activity table

0x71058500 Failed to initialize lock necessary for trespass operations

0x71058501 Failed to open lock necessary for trespass operations

0x71058502 Failed to close lock necessary for trespass operations

0x71058503 Unexpected authority value while giving up control of a mirror

0x71058504 Logic flaw caused a semaphore to be released too often while giving up control of a mirror

75

MirrorView


0x71058505 Unexpected authority value while taking over control of a mirror

0x71058506 Logic flaw caused a semaphore to be released too often


0x71058508 Invalid mode detected while converting a DLS lock

0x71058509 Unrecognized event detected in the DLS callback handler

0x7105850A Insufficient memory available to send fracture logs to our peer SP

0x7105850B Error initializing bitmap to send fracture logs to our peer SP

0x7105850C Error copying bitmap while attempting to send fracture logs to our peer SP

0x7105850D Insufficient memory to send config data to our peer SP

0x7105850E Unrecognized authority value detected in license

0x7105850F Insufficient memory to create internal work item while taking control of a mirror

0x71058510 Detected a consistency failure from the config manager re type of sync required

0x71058511 Failed to find the consumable corresponding to the specified mirror

0x71058513 Detected an invalid fracture state while attempting to report synchronization progress

0x71058514 Failed to mirror write due to a missing information about the secondary image

0x71058515 Secondary write request rejected as the request didn't come from the primary

0x71058516 Secondary write request rejected as the target device is not ready

0x71058517 Insufficient memory to allocate context resources - write to secondary image rejected

0x71058518 Insufficient memory to allocate IRP - write to secondary image rejected

0x71058519 Insufficient memory to allocate MDL - write to secondary image rejected

0x7105851A Simulated immediate I/O failure on the secondary

0x7105851B Simulated I/O failure on the callback path of the secondary

0x7105851C Secondary image is not currently accepting I/O requests. If the problem persists, check the remote array.

0x7105851D Config manager couldn't pend or defer the operation so reboots the SP

0x7105851E During a failure operation an unexpected config status was encountered

0x7105851F Unable to locate the mirror attempting to lazy trespass

0x71058520 An improper transport event was received and the SP will panic

0x71058521 We attempted a lazy trespass and not enough memory on the system.

0x71058522 Unable to assign ownership to mirror

0x71058523 Unable to determine size of mirror by WWID

76

MirrorView


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.

77

MirrorView


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

78

MirrorView


0x71058709 Unexpected MPS close event received by the transport manager

0x7105870A Unrecognized MPS event received by the transport manager

0x7105870B Insufficient memory available for async response processing

0x7105870C Detected a duplicate MPS mailbox name in use

0x7105870D Unrecognized CMI transfer type detected

0x7105870E Unrecognized CMI callback event detected

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.

79

MirrorView


0x7105890F Buffer passed to admin code is of invalid size when fracturing Consistency Group.

0x71058910 The revision ID is invalid when fracturing Consistency Group.

0x71058911 Buffer passed to admin code is of invalid size when syncing Consistency Group.

0x71058912 Then revision ID is invalid when syncing Consistency Group.

0x71058913 Buffer passed to admin code is of invalid size when promoting Consistency Group.

0x71058914 The revision ID is invalid when promoting Consistency Group.

0x71058915 Buffer passed to admin code is of invalid size when syncing CG.

0x71058916 Then revision ID is invalid when syncing CG.

0x71058917 Buffer passed to admin code is of invalid size when promoting CG.

0x71058918 The revision ID is invalid when promoting CG.

0x71058919 MirrorView Consistency Group Sync failed due to an unknown image.

0x7105891A MirrorView Consistency Group Sync failed due to an image being in an invalid condition.

0x7105891B MirrorView Consistency Group Sync failed due to no members in the group.

0x7105891C MirrorView Consistency Group Sync failed due to mirror being inactive.

0x7105891D MirrorView Consistency Group Operation failed due to secondary system being unreachable.

0x7105891E MirrorView Consistency Group Sync failed due to peer SP being unreachable.

0x7105891F MirrorView Consistency Group Sync failed due to secondary syncing state update failing.

0x71058920 MirrorView Consistency Group Sync failed due to the WILs being faulted.

0x71058921 MirrorView Consistency Group Sync failed due to sync queue failure.

0x71058922 MirrorView Consistency Group Sync failed due to connectivity failure or problem on remote system.

0x71058923 MirrorView Consistency Group Sync failed due to an image not being a primary image.

0x71058924 Synchronization of Consistency Group %2 returned with status %3.

0x71058925 Cannot synchronize Consistency Group %2 because the peer SP is down.

0x71058926 Cannot synchronize Consistency Group %2 because the MirrorView driver is degraded on the peer SP.

0x71058927 Cannot promote Consistency Group %2 because the MirrorView driver is degraded on the peer SP.

80

MirrorView


0x71058928 Cannot synchronize Consistency Group %2 because group is not initialized or is degraded on the peer SP.

0x71058929 Cannot promote Consistency Group %2 because group is not initialized or is degraded on the peer SP.

0x7105892A Cannot synchronize Consistency Group %2 because mirror(s) in the remote group are closed. Check remote system.

0x7105892B Cannot synchronize Consistency Group %2 because remote system indicates disk failure(s). Check remote system.

0x7105892C Cannot synchronize Consistency Group %2 due to disk failure. Check disks for errors and then retry.

0x7105892D Consistency Group sync connect test failing due to remote disk failure.

0x7105892E Consistency Group sync fails due to disk failure.

0x7105892F Consistency Group sync fails due to image has been quiesced.

0x71058930 Cannot synchronize Consistency Group %2 because mirror(s) in the remote group are quiesced. Check remote system or retry.

0x71058931 Cannot synchronize Consistency Group %2 because mirror(s) in the group are quiesced.

0x71058932 Cannot synchronize Consistency Group %2 because MirrorView is in degraded mode on the remote system.

0x71058933 Cannot promote Consistency Group %2 because MirrorView is in degraded mode on the remote system.

0x71058934 Cannot promote Consistency Group %2 because the membership count does not match on both systems. Check Consistency Group configuration.

0x71058935 Cannot promote Consistency Group %2 because group is not initialized or is degraded on the remote system.

0x71058936 MirrorView Consistency Group Promote failed due to no members in the group.

0x71058937 Promote Consistency Group %2 returned with status %3.

0x71058938 Remote system for Consistency Group %2 attempted local-only promote but failed with status %3.

0x71058939 MirrorView Consistency Group Promote failed due to secondary system being unreachable.

0x7105893A MirrorView Consistency Group Promote failed due to peer SP being unreachable.

0x7105893B MirrorView Consistency Group Promote failed due the WILs being faulted.

0x7105893C MirrorView Consistency Group Promote failed due to images in an invalid state.

0x7105893D Consistency Group Promote removal of slave failed due to invalid image

81

MirrorView


condition.

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.

82

MirrorView


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

83

MirrorView


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.

84

MirrorView


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.

85

MirrorView


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

86

MirrorView


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

0x7152806B Invalid remote SP Id for communication

0x7152806C Invalid remote array response, add secondary image failed

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

0x71528070 Add secondary failed, remote array couldn't locate primary array id.

87

MirrorView


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

88

MirrorView


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

89

MirrorView


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

90

MirrorView


0x715280AD The TLD didn't have a group update items tag. The request operation data was incorrectly formated. Verify the data in the request

0x715280AE The TLD didn't have a update schedule type tag. The request operation data was incorrectly formated. Verify the data in the request

0x715280AF The TLD didn't have a update period tag. The request operation data was incorrectly formated. Verify the data in the request

0x715280B0 The TLD didn't have a recovery policy tag. The request operation data was incorrectly formated. Verify the data in the request

0x715280B1 The TLD didn't have a group sync rate tag. The request operation data was incorrectly formated. Verify the data in the request

0x715280B2 The fracture of the group failed. A reboot of the SP will be required to recover from the failure

0x715280B3 The group identifier specified is invalid. Refresh the user data and try again

0x715280B4 The group identifier was invalid for the sync operation. Refresh the user data and try again

0x715280B5 The group sync command was send to the wrong array for the operation

0x715280B6 The group sync command failed

0x715280B7 The group specified to sync is already syncronizing

0x715280B8 The group identifier to promote is invalid. Refresh the user data and try again

0x715280B9 The existing primary image is unreachable for promotion. Check the mirrorview connection or try a different promote type

0x715280BA The existing primary image is rolling back so promotion is not allowed

0x715280BB An invalid property type was specified for the group

0x715280BC The get group property operation failed because the group wasn't found. Refresh user data

0x715280BD The set property operation failed due to the group not being found. Refresh user data

0x715280BE The clutch driver was unreachable and the group operation will fail. Reboot the SP and if the problem continues contact customer support

0x715280BF The clutch driver returned an error and the group operation will fail. Reboot the SP and if the problem continues contact customer support

0x715280C0 The clutch driver returned and error and the group operation will fail. Reboot the SP and if the problem continues contact customer support

0x715280C1 The group identifier was not found. Refresh user data

0x715280C2 The clutch driver had an internal error and the operation failed. Reboot the SP and if the problem continues contact customer support

0x715280C3 The clutch driver failed to enumerate the group members. Reboot the SP

91

MirrorView


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

92

MirrorView


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

93

MirrorView


image was a . different size than the primary LU. The add secondary operation will fail

0x71528106 MirrorView/A - the mirror specified to have an image synchronized wasn't found

0x71528107 MirrorView/A - The mirror requested to sync an image had an internal failure and the primary image location couldn't be found

0x71528108 MirrorView/A - the mirror specified to have an image fractured wasn't found

0x71528109 MirrorView/A - The mirror requested to fracture an image had an internal failure and the primary image location couldn't be found

0x7152810A MirrorView/A - A member cannot be added to a group with locality remote

0x7152810B MirrorView/A - A member cannot be added to a group if the image is out-of-sync

0x7152810C MirrorView/A - A member cannot be added to a group if the image is rolling back

0x7152810D MirrorView/A - A member cannot be added to a group if the group is out-of-sync

0x7152810E MirrorView/A - A member cannot be added to a group if the group is rolling-back

0x7152810F MirrorView/A - A member cannot be added to a group if the group is scrambled

0x71528110 MirrorView/A - A member cannot be added to a group if the group condition is not normal or updating

0x71528111 MirrorView/A - A member cannot be added to a group if the image condition is not normal or updating

0x71528112 MirrorView/A - Group names are unique. An attempt was made to create a group with the same name as an existing group

0x71528113 MirrorView/A - Number of groups on a system cannot exceed the max limit

0x71528114 MirrorView/A - Number of members in a group cannot exceed the max limit.

0x71528115 MirrorView/A - Clutch did not understand the group type set by far

0x71528116 MirrorView/A - A member cannot be removed from a group if the group is out-of-sync

0x71528117 MirrorView/A - A member cannot be removed from a group if the group is rolling-back

0x71528118 MirrorView/A - A member cannot be removed from a group if the group is scrambled

0x71528119 MirrorView/A - The mirror could not be removed because the group's condition is not normal or adminfractured.

94

MirrorView


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

95

MirrorView


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

0x71528136 FAR_UTIL_MIRROR_BY_SLU_MUTEX_NOT_ACQUIRED

0x71528138 MirrorView/A - Clutch returned a error

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

96

MirrorView


0x71528148

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

0x71528153 FAR_PERF_UPDATE_BLOCKS_WRITTEN_MUTEX_NOT_ACQUIRED

0x71528158 MirrorView/A - the mirror specified to be created failed due to a database operation. Reboot the SP and retry the operation

0x71528159 MirrorView/A - the mirror specified to be destroyed wasn't found. Refresh User data

0x7152815A MirrorView/A - the mirror specified to be destroyed wasn't found. Refresh User data

0x7152815B MirrorView/A - the mirror specified to be fractured wasn't found. Refresh User data

0x7152815C MirrorView/A - the mirror specified to get properties wasn't found. Refresh User data

0x7152815D MirrorView/A - the mirror specified to get image properties wasn't found. Refresh User data

0x7152815E MirrorView/A - the mirror specified to add an image to wasn't found. Refresh User data

0x7152815F MirrorView/A - the mirror specified to remove the image wasn't found. Refresh User data

0x71528160 MirrorView/A - the mirror specified to promote wasn't found. Refresh User data

0x71528161 MirrorView/A - the mirror specified to set properties wasn't found. Refresh User data

0x71528162 MirrorView/A - the mirror specified to set image properties wasn't found. Refresh User data

0x71528163 MirrorView/A - the mirror specified to sync an image wasn't found.

97

MirrorView


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

98

MirrorView


0x7152817D

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

99

MirrorView


the promote again.

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.

100

MirrorView


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

101

MirrorView


0x71528210 The TLD didn't have a FAR ID when adding a image

0x71528211 The TLD didn't have a valid FAR ID when adding a image

0x71528212 The TLD didn't have a Array ID when adding a image

0x71528213 The TLD didn't have a valid Array ID when adding a image

0x71528214 The TLD didn't have a LU ID when adding a image

0x71528215 The TLD didn't have a valid LU ID when adding a image

0x71528216 Peer's create mirror response is not valid

0x71528217 Peer's destroy mirror response is not valid

0x71528218 Destination sp may not be alive

0x71528219 secondary's update image response is not valid

0x7152821A peer's update mirror response is not valid

0x7152821B peer's software version doesn't match

0x7152821C Unable to find the mirror whose data has to be updated

0x7152821D remote arrays 's software version doesn't match

0x7152821E Unable to find the mirror whose data has to be updated

0x7152821F Far is unable to read the global data from PSM

0x71528220 Far is unable to read the far group data from clutch

0x71528221 Far is unable to create shared memory for mirroring data

0x71528222 Far is unable to create shared memory for mirroring data

0x71528223 Far is unable to get a reference to shared mirroring data

0x71528224 Far is unable to get a reference to shared mirroring data

0x71528225 Far is unable to read Mirror data from PSM

0x71528226 The dll is unable to locate the remove image tag

0x71528227 The dll is unable to locate the remove image id tag

0x71528228 Illegal image id during remove image operation

0x71528229 The Mirror ID specified when removing an image is invalid

0x7152822A The array ID tag wasn't found when removing an image

0x7152822B The Get Mirror Prop Tag wasn't found in the request

0x7152822C The Get Mirror Prop Tag wasn't found in the request

0x7152822D The FAR Admin operation isn't implemented

0x7152822E The enumeration type specified was invalid

0x7152822F The FAR promote tag wasn't found in the request

0x71528230 The FAR ID promote tag wasn't found in the request

0x71528231 The FAR ID for promote wasn't valid, ie - was the wrong length

0x71528232 The FAR promote array ID tag wasn't found in the request

0x71528233 The FAR promote array id was invalid, ie the wrong length

102

MirrorView


0x71528234 The promote type specified (<type>) wasn't valid

0x71528235 The promote type specified (<type>) wasn't valid

0x71528236 The name specifed was invalid

0x71528237 The description specifed was invalid

0x71528238 The rollback setting specified (<setting>) was invalid

0x71528239 The rollback throttle value specifed was invalid

0x7152823A The FAR ID wasn't found when attempting to set mirror properties

0x7152823B The FAR ID specified to set properties was illegal

0x7152823C The fracture image tag wasn't found in the request

0x7152823D The image Id to fracture wasn't found in the request

0x7152823E The mirror to fracture ID was invalid

0x7152823F The image Id tag wasn't found in the request to fracture

0x71528240 The image Id to fracture was an invalid length

0x71528241 The fracture image tag wasn't found in the request

0x71528242 The image Id to fracture wasn't found in the request

0x71528243 The mirror to fracture ID was invalid

0x71528244 The image Id tag wasn't found in the request to fracture

0x71528245 The image Id to fracture was an invalid length

0x71528246 The image role specified for set image was invalid

0x71528247 The user defined sync rate didn't include additional required information of either the sync rate, latency or granularity

0x71528248 The user requested a change to the update data but didn't include a new value for the update type or period

0x71528249 The user requested a change to the update data but didn't include a valid update type

0x7152824A The set mirror properties tag wasn't found in the input data

0x7152824B The set image properties tag wasn't found in the input data

0x7152824C The set image properties ID tag wasn't found in the input data

0x7152824D The set image properties mirror ID was invalid

0x7152824E The set image properties array ID tag wasn't found in the input data

0x7152824F The set image properties array ID was invalid

0x71528250 The set device properties buffer was invalid

0x71528251 The tag for the group id to destroy was not found

0x71528252 The tag for the group id to addmember was not found

0x71528253 The tag for the group id to removemember was not found

0x71528254 The tag for the group id to setproperty was not found

103

MirrorView


0x71528255 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




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

104

MirrorView


0x71528279 The group id specified to get group properties is not valid

0x7152827A The group id tag is not found in the TLD sent to set properties of a group

0x7152827B The group id supplied while setting the group properties has zero length and is not valid.

0x7152827C The update period supplied while setting the group properties has zero length and is not valid.

0x71528285 Navisphere has attempted to set bad group properties.

0x71528300 Unable to allocate memory to read PSM contents

0x71528301 Unable to Open MirrorView/A's PSM data area

0x71528302 Unable to write requested amount of data to PSM

0x71528303 Unable to read requested amount of data from PSM

0x71528304 Unable to create shared memory bit map

0x71528305 Unable to get reference to shared memory bit map

0x71528306 Unable to create shared memory to store mirror data

0x71528307 Unable to get a reference to the shared mirror data

0x71528308 Unable to locate mirror in the database

0x71528309 Unable to locate mirror in the database during destroy on peer

0x7152830A MirrorView/A caught an exception while trying to read the mirroring dataarea

0x7152830B MirrorView/A caught an exception while writing to the mirroring dataarea

0x7152830C MirrorView/A caught an exception while reading the mirror dataarea

0x7152830D MirrorView/A caught an exception while writing to mirror dataarea

0x7152830E FAR_CONFIG_UNUSED_001

0x7152830F FAR_CONFIG_UNUSED_002

0x71528310 The image fracture condition is not valid

0x71528311 The image fracture condition is not valid

0x71528312 Unable to find the mirror in the database

0x71528313 Unable to find the mirror in the database while system fracturing an image

0x71528314 Image has already been Admin fractured

0x71528315 Image that is being system fracture has already been admin fractured

0x71528316 Image that is being system fracture has already been system fractured

0x71528317 Fracture cannot proceed due to invalid image condition

0x71528318 Fracture cannot proceed due to invalid image state

0x71528319 Fracture cannot proceed due to invalid image condition of group member

0x7152831C Invalid group state

105

MirrorView


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

106

MirrorView


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

107

MirrorView


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>

108

MirrorView


0x71528403

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

109

MirrorView


IRP stack location 4) The line number

0x71528411

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

110

MirrorView


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

111

MirrorView


them consistent

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

112

MirrorView


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

113

MirrorView


Admin DLL and make them consistent

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

114

MirrorView


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

115

MirrorView


0x71528605

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

116

MirrorView


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

117

MirrorView


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

118

MirrorView


0x7152863F

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.

119

MirrorView


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.

0x71524000 Warning message. <message>

120

MirrorView


0x71524001

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

121

MirrorView


0x7105010B Received a request to promote a secondary image to be primary

0x7105010C Updating mirror and/or image properties

0x7105010D Received a request to set driver properties

0x7105010E Received a request to set driver properties

0x7105010F Received a request to bind an LU

0x71050110 Received a request to bind mirroring into a device stack

0x71050111 Received a request to rebind mirroring into a device stack

0x71050112 Received a request to unbind mirroring from a device stack

0x71050113 Received a request to enumerate the list of bound LUs which are not part of a mirror

0x71050115 Received a request to halt I/O to an LU

0x71050116 Received a request to shut down the mirroring driver

0x71050117 PSM contents were restored after our peer failed during an update.

0x71050118 Received a request from a remote K10 to create a mirror

0x71050119 Received a request from a remote K10 to destroy a mirror

0x7105011A Received a request from a remote K10 to promote a secondary image

0x7105011B Received a request from a remote K10 to update a mirror's properties

0x7105011C Received a request from our peer SP to create a mirror

0x7105011D Received a request from our peer SP to destroy a mirror

0x7105011E Received a request from our peer SP to update a mirror's properties

0x7105011F Received a request from our peer SP to bind mirroring into a device stack

0x71050120 Received a request from our peer SP to rebind mirroring into a device stack

0x71050121 Received a request from our peer SP to unbind mirroring from a device stack

0x71050122 Received a ping from a remote K10

0x71050123 Received a request from our peer SP to update the driver properties

0x71050124 Receive a stage update request from our peer SP

0x71050127 Mirror state was set to inactive

0x71050128 Mirror state was set to active

0x71050129 Mirror state was set to attention

0x7105012A Image was fractured by an administrator

0x7105012B Synchronization of an image was started by an administrator

0x7105012C An 'orphan' image (secondary image with no reachable primary) was destroyed

0x7105012D Set the current %complete value for an image synchronization

122

MirrorView


0x7105012E Admin subsystem initialized

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.

123

MirrorView


0x71050157 Creating remote consistency group and add member operation completed.

0x71050158 Received request to remove member and destroy remote consistency group.

0x71050159 Completed removing member and destroying remote consistency group.

0x7105015A Received request to add member to remote consistency group.

0x7105015B Completed adding member to remote consistency group.

0x7105015C Received request to remove member from remote consistency group.

0x7105015D Completed removing member from remote consistency group.

0x7105015E Automatic Synchronization of Consistency Group %2 started.

0x7105015F Admin Fracture Completed for consistency group.

0x71050200 An image was fractured. If the failure clears automatic resynchronization may be allowed.

0x71050201 An image was fractured, and administrator action is required for resynchronization

0x71050202 A remote mirror image has been fractured

0x71050203 An administrator started resynchronization of an image

0x71050204 Synchronization of an image based on a fracture log was started

0x71050205 Full synchronization of an image was started

0x71050206 Image synchronization completed

0x71050207 A mirror was automatically activated when its minimum conditions were met

0x71050208 A mirror was automatically placed into the attention state, as its minimum requirements are no longer met

0x71050209 The mirroring driver has entered the degraded state. No write requests are allowed.

0x7105020A The image condition of a mirror has been changed to system fractured; system fracture may need to be performed.

0x71050300 Must wait for PSM to become available

0x71050400 A remote K10 has become reachable

0x71050401 A remote K10 has become unreachable

0x71050500 The mirrorview driver failed to find an item during a search and will attempt to search again.

0x71050501 The attempted write to the write intent log failed. The effected Mirror will admin fracture all images.

0x71050600 The mirroring driver was successfully loaded

0x71050601 The mirroring driver was successfully unloaded

0x71050602 Loading of the mirroring driver has started

124

MirrorView


0x71520000 Informational message. <message>

0x71520001 MirrorView/A, synchronization requested

0x71520002 MirrorView/A, fracture image requested

0x71520003 The minimum requirements for an active mirror have been met. Placing mirror <mirror name> in the active state automatically

0x71520004 The minimum requirements for an active mirror have not been met. Placing mirror <mirror name> in the attention state

0x71520005 MirrorView/A, request to promote mirror received <status>

0x71520006 Received request to promote group %1

0x71520007 Received request to fracture group %1

0x71520008 Received request to synchronize group %1

0x71520009 Starting deferred rollback of session %1

0x7152000A Undeferring rollback session %1

0x7152000B MirrorView, rollback started on mirror during promote %1.

0x7152000C MirrorView received a request to create a group. %1

0x7152000D MirrorView received a request to destroy a group. %1

0x7152000E MirrorView received a request to force destroy a group. %1

0x7152000F MirrorView received a request from the primary to create a remote group. %1

0x71520010 MirrorView received a request from the primary to destroy a remote group. %1

0x71520011 MirrorView received a request to add a member to group. %1

0x71520012 MirrorView received a request to remove a member from a group. %1

0x71520013 MirrorView received a request to add a member to the remote group. %1

0x71520014 MirrorView received a request to remove a member from the remote group. %1

0x71520015 MirrorView received a request to set properties of a group. %1

0x71520016 Created Inc session for the secondary image %1

0x71520401 MirrorView/A driver successfully started. Compile time of the driver: <compile time>

0x71520402 MirrorView/A driver stopped

0x71520403 MirrorView/A driver binding LU. LU ID of the LUN: <LU ID>

0x71520404 MirrorView/A driver rebinding LU. LU ID of the LUN: <LU ID>

0x71520406 MirrorView/A driver unbinding LU. LU ID of the LUN: <LU ID>

0x71520407 MirrorView/A driver received a shutdown request

0x71520409 MirrorView/A driver received a bind consumable request from the peer.

125

MirrorView


LU ID of the LUN: <LU ID>

0x7152040A MirrorView/A driver received a rebind consumable request from the peer. LU ID of the LUN: <LU ID>

0x7152040B MirrorView/A driver received an unbind consumable request from its peer. LU ID of the LUN: <LU ID>

0x7152040C MirrorView/A driver received an update consumable request from the peer. LU ID of the LUN: <LU ID>

0x7152040D MirrorView/A driver received an update compatibility request from its peer

126

SnapView


SnapView

Critical Error

0x7100C000 SnapView has received an invalid DCA (data copy avoidance) value. A bugcheck will ensue.

0x7100C001 SnapView has attempted to reference a device that does not exist. A bugcheck will ensue.

0x7100C007 User has attempted to start a SnapView session with both the Persistence and Simulation modes on.Note: %s is the session name.

0x7100C008 SnapCopyPageCreateCacheMissWorkOrder() Lookaside list allocation failure

0x7100C009 SnapCopyPageSalvagePageEntryFromLRU() The LRU list did not contain any items to remove.

0x7100C00A SnapCopyPageSalvagePageEntryFromLRU() The LRU list did not contain any items to remove.

0x7100C00C SnapCopyPageInitialize() The working set parameter was not available in the registry.

0x7100C00D SnapCopyPageReference() A duplicate key was encountered on a linear hash table reinsert request

0x7100C00E SnapCopyPageReference() A duplicate key was encountered on a linear hash table reinsert request

0x7100C00F SnapCopyVMInitialize() The VM subsystem could not initialize.

0x7100C010 SnapCopyVMReferenceCacheLUHeader() An I/O Request tracking structure could not be allocated.

0x7100C011 SnapCopyVMIO() An IRP could not be allocated.

0x7100C012 SnapCopyVMIO() An MDL could not be allocated.

0x7100C014 nap Direct Linear Map subsystem has exceeded a Limit on a Paging Semaphore

0x7100C015 Snap Direct Linear Map subsystem has exceeded a Limit on an IO Semaphore

0x7100C016 Snap Chunk Repository ubsystem has exceeded a Limit on a Paging Semaphore

0x7100C019 Snap VM has been asked to release a (Direct Linear Map) TOC with a bad Reference Count

0x7100C01A Snap VM has been asked to release a (Chunk Repository) TOC with a bad Reference Count

0x7100C01B Snap Chunk Repository Allocation Block has an inconsistent Session Sequence Number

127

SnapView


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

128

SnapView


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.

129

SnapView


0x71008028 SnapView is experiencing difficulties in closing a filament.

0x71008029 The call to MpsGetSpId() has failed.

0x7100802A The peer SP is unreachable.

0x7100802B An invalid message has been sent between the SP's.

0x7100802C SnapView received an invalid event from MPS

0x7100802D SnapView has attempted an operation on a Session that no longer exists.

0x7100802E The user has attempted to start a SnapView session with a name that already exists on that Lun.

0x7100802F A read from a SnapView LU has failed.

0x71008030 Cannot change chunk size while sessions are active. To change the chunk size, stop all sessions first.

0x71008031 You must add LUNs with adequate capacity to the Reserved LUN Pool before you can use this feature

0x71008032 SnapView Session is not persistent

0x71008033 SnapView Session is not active on this SP

0x71008034 SnapView Session is currently being Rolled Back

0x71008035 During the RollBack of Session, this SP was unable to inform the Peer of a change in Roll Back state

0x71008036 Invalid device request received

0x71008037 Invalid sized buffer received

0x71008038 Invalid parameter received

0x71008039 Required TLD parameter is missing from command list

0x7100803A Chunk size value is invalid or missing

0x7100803B Functionality is not implemented

0x7100803C SnapView session stopped because cache is full

0x7100803D SnapView has exceeded its physical memory limit, so it will stop a session to free up memory.

0x7100803E SnapView session stopped because of host trespass

0x7100803F Maximum number of sessions already started for device

0x71008040 There has been an attempt to activate a session that has already been activated.

0x71008041 A chunk already exists for this key

0x71008042 Persistence not supported

0x71008043 Request sent to a non-owning SP.

0x71008044 Used to indicate that we can't quite finish a stop because of a deactivate

0x71008077 SnapView Session is not currently being Rolled Back

0x7100807A SnapView has discovered an internal inconsistency.

130

SnapView


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.

131

SnapView


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

132

SnapView


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

133

SnapView


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.

134

SnapView


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

135

SnapView


0x71268124 A request to enumerate objects specified a buffer with an invalid revision number

0x71268125 A request to get generic object properties specified a buffer of invalid size

0x71268126 A request to get generic object properties specified a buffer with an invalid revision

0x71268127 A request to create a CloneView specified a buffer of invalid size

0x71268128 A request to create a CloneView specified a buffer with an invalid revision

0x71268129 A request to destroy a CloneView specified a buffer of invalid size

0x7126812A A request to destroy a CloneView specified a buffer with an invalid revision

0x7126812B A request to enumerate CloneViews specified a buffer of invalid size

0x7126812C A request to enumerate CloneViews specified a buffer with an invalid revision

0x7126812D A request to add a Clone specified a buffer of invalid size

0x7126812E A request to add a Clone specified a buffer with an invalid revision

0x7126812F A request to remove a Clone specified a buffer of invalid size

0x71268130 A request to remove a Clone specified a buffer with an invalid revision

0x71268131 A request to fracture a Clone specified a buffer of invalid size

0x71268132 A request to fracture a Clone specified a buffer with an invalid revision

0x71268133 A request to synchronize a Clone specified a buffer of invalid size

0x71268134 A request to synchronize a Clone specified a buffer with an invalid revision

0x71268135 A request to get CloneView properties specified a buffer of invalid size

0x71268136 A request to get CloneView properties specified a buffer with an invalid revision

0x71268137 A request to set CloneView properties specified a buffer of invalid size

0x71268138 A request to set CloneView properties specified a buffer with an invalid revision

0x71268139 A request to get Clone properties specified a buffer of invalid size

0x7126813A A request to get Clone properties specified a buffer with an invalid revision

0x7126813B A request to set Clone properties specified a buffer of invalid size

0x7126813C A request to set Clone properties specified a buffer with an invalid revision

0x7126813D A request to enumerate available objects specified a buffer of invalid size

0x7126813E A request to enumerate available objects specified a buffer with an invalid revision

0x71268141 A request to set driver properties specified a buffer of invalid size

0x71268142 A request to set driver properties specified a buffer with an invalid revision

0x71268143 A request to get driver properties specified a buffer of invalid size

0x71268144 A request to get driver properties specified a buffer with an invalid revision

136

SnapView


0x71268145 A request to halt I/O to a CloneView specified a buffer of invalid size

0x71268146 A request to halt I/O to a CloneView specified a buffer with an invalid revision

0x71268147 A request to shut down Clones specified a buffer of invalid size

0x71268148 A request to shut down Clones specified a buffer with an invalid revision

0x71268149 A request to fake a lost contact event specified a buffer of invalid size

0x7126814A A request to fake a lost contact event specified a buffer with an invalid revision

0x7126814B A request to modify debug parameters specified a buffer of invalid size

0x7126814C A request to modify debug parameters specified a buffer with an invalid revision

0x7126814D A request to get performance data specified a buffer of invalid size

0x7126814E A request to get performance data specified a buffer with an invalid revision

0x7126814F An unrecognized request was made to the Clones driver

0x71268150 Received a request from our peer SP to update a CloneView which is unknown to us

0x71268151 Insufficient memory to stage the update from our peer SP

0x71268157 Failed to request our peer SP to create a CloneView

0x71268158 Failed to request our peer SP to destroy a CloneView

0x71268159 Failed to request our peer SP to update a CloneView

0x7126815A Failed to request our peer SP to get consumable info

0x7126815C Attempt to ping primary K10 for a CloneView failed

0x7126815D Failed to request our peer SP to update driver properties

0x7126815E Failed to request our peer SP to stage update information

0x71268161 Attempt to deallocate the CPL while it is not allocated.

0x71268166 Attempted to stage an update while another update is still (apparently) in progress

0x71268167 No memory available to complete a local update

0x7126816B Invalid size or revision received from our peer SP in response to a quiesce request

0x7126816C Failed to send a quiesce request to our peer SP

0x7126816D Failed to quiesce the peer SP

0x7126816E Failed to quiesce one or more LUs on the local SP

0x7126816F Invalid revision on a request from our peer SP to quiesce an LU,

0x71268170 A quiesce request received from our peer SP failed

0x71268171 A request to our peer SP to quiesce one or more LUs failed

0x71268172 Failed to open PSM LUN during Admin initialization

137

SnapView


0x71268174 Failed to enumerate the current list of CloneViews

0x71268175 Failed to get driver properties

0x71268176 Failed to get the generic properties of an object

0x71268178 Config manager could not add a new CloneView

0x71268179 Failed to obtain the progress of a Clone synchronization

0x7126817A Database subsystem initialization failed

0x7126817B Failed to read current list of consumables during database subsystem initialization

0x7126817C Failed to read current list of CloneViews during database subsystem initialization

0x71268180 Maximum CloneViews already exist on the system

0x71268183 Maximum number of CloneViews are already using Clones Fast Recovery (CFR) on this system

0x71268184 Allocating the Clones Fast Recovery resources for the CloneView being created failed

0x71268186 Automatic fracturing of the Clone to enable setting the Fast Recovery use on failed..

0x71268187 Maximum CloneViews already allocated on the system

0x71268188 Maximum number of CloneViews on the system.

0x7126818E The administrator attempted to deallocate the CPL LUNs while protected restore was enabled.

0x7126818F Invalid buffer size during get of compatability mode.

0x71268190 Invalid revision ID during get of compatibility mode.

0x71268191 Invalid revision ID during setting of compatiblity mode.

0x71268192 Invalid buffer size during setting of compatiblity mode.

0x71268193 Invalid revision ID during setting of compatiblity mode.

0x71268194 Invalid revision ID or buffer size during setting of compatiblity mode.

0x71268195 Unable to send to peer during setting of compatibility mode.

0x71268196 Something failed during admin operation. Driver will enter degraded mode. Reboot the SP.

0x71268197 Internal failure during adding of a CloneView.

0x71268198 Failure to set CPL due to using same name for SPA and SPB

0x71268199 Unable to deallocate CPL since in use.

0x7126819A Clone must be added on SP that controls the CloneView

0x7126819B Invalid revision ID during allocation of the Frozen Clones Log buffers.

0x7126819C Error occurred allocating the Frozen Clones COD Resources on the peer SP.

0x7126819D Invalid revision ID during de-allocation of the Frozen Clones resources.

138

SnapView


0x7126819E Error occurred de-allocating the Frozen Clones COD resources on the peer SP.

0x7126819F Invalid revision ID during de-allocation of the Frozen Clones resources.

0x712681A0 Error occurs allocating the Frozen Clones COD Resources on the peer SP

0x712681A1 Invalid revision ID during de-allocation of the Frozen Clones resources.

0x712681A2 Error occurred allocating the Frozen Clones Log buffers on the peer SP.

0x712681A3 Error occurred de-allocating the Frozen Clones Log buffers on the peer SP.

0x712681A4 Error occurred allocating the Frozen Clones Log buffers on the peer SP.

0x712681A5 An error occured allocating the Frozen Clones COD resources

0x712681A6 Clone Group admin error - Transport error in peer update num images.

0x712681A7 Clone Group admin error - revision id error on update num images on peer.

0x712681A8 Clone Group admin error - revision id or update num images size incorrect.

0x71268201 Could not add all existing CloneViews to the config manager?s lists on driver startup

0x71268202 An invalid image phase was detected while we were attempting to schedule an Clone synchronization

0x71268203 An unexpected fail status was returned when we attempted to start an Clone synchronization

0x71268204 An unrecognized image condition of a Clone was detected

0x71268205 Failed to locate the target CloneView during a trespass operation

0x71268207 Failed to find a Clone or Source in the CloneView data structure, when it should have existed

0x71268208 The config manager generated an invalid bucket number

0x71268209 Unexpected error updating the config manager?s hash table

0x7126820A Insufficient memory available to add a new CloneView

0x7126820B Invalid Clone state detected during an add Clone operation

0x7126820C Unrecognized CloneView operation detected while setting initial Clone image state

0x7126820D Failed to gain exclusive access to the CloneView during a destroy operation

0x7126820E Failed to gain exclusive access to the CloneView during an add/remove Clone operation

0x71268210 Unknown Clone image condition detected during an administrative fracture operation

0x71268211 A failure unexpectedly occurred during a fracture operation

0x71268212 Unknown Clone image condition detected during a synchronize operation

0x71268214 Unexpected failure while fracturing a Clone following a media failure.

0x71268215 Unrecognized SP state value detected during an attempted SP state change

139

SnapView


0x71268216 Unexpected Clone image condition detected while handling a Clone becoming unreachable

0x71268217 Unexpected Clone image condition detected while handling a Clone becoming reachable

0x71268218 Insufficient memory to process a state change of a K10

0x7126821A Insufficient memory available to process completion of a sync I/O

0x7126821B Insufficient memory available to process a media failure error

0x7126821C Failed to locate a CloneView for which we?re attempting to handle a media failure

0x7126821D Insufficient memory available to handle an incoming write request

0x7126821E Failed to locate CloneView for an incoming write request. Indicates an internal driver consistency failure

0x7126821F Insufficient memory available to handle a synchronization state update

0x71268220 Insufficient memory available to handle completion of a synchronization operation

0x71268221 Insufficient memory available to take ownership of a CloneView

0x71268222 Unrecognized reason code detected while attempting to take ownership of a CloneView

0x71268223 Failed to locate the target CloneView during a trespass operation

0x71268224 Invalid Clone image condition detected during a trespass operation

0x71268225 Failed to locate the target CloneView while processing a failure of our peer SP

0x71268226 Invalid Clone image phase detected while taking control of a Clone

0x71268227 Invalid Clone image condition detected while handling a failure of our peer SP

0x71268228 Unrecognized Clone image state value detected internally

0x71268229 Insufficient memory available to give up control of a CloneView

0x7126822A Failed to locate the CloneView we?re attempting to give away

0x7126822F Unrecognized Clone image state detected while preparing to fracture a Clone

0x71268230 Attempted to schedule synchronization of an already synchronized Clone

0x71268231 Attempt to create a CloneView with too many pieces (LUNs)

0x71268232 Attempt to add a Clone with too many pieces (LUNs).

0x71268233 Can?t remove a Clone object from an LU?s stack, as it is currently part of a CloneView

0x71268235 Can?t remove a Clone object from an LU?s stack, as it is currently synchronizing

0x71268236 Can?t find a CloneView data structure during a shutdown request

140

SnapView


0x71268237 Failed to locate an expected Clone in our internal data structures

0x71268238 Can?t fracture a Clone as we?re not the primary K10 and/or controlling SP for the CloneView

0x71268239 Clone is already administratively fractured

0x7126823A Can?t administratively fracture the Clone due its image condition

0x7126823B Can?t start synchronization as we?re not the primary K10 and/or controlling SP for the CloneView

0x7126823C Can?t start synchronization or reverse-sync operation from the current Clone image condition

0x7126823D CloneView not found in config manager?s database

0x7126823E Clone not found in the specified CloneView

0x7126823F The local array is not the primary K10 for the CloneView

0x71268240 Unable to generate a unique name for an exported device

0x71268243 Attempt to destroy a CloneView which still has at least one Clone

0x71268244 Attempt to destroy a CloneView for which we?re not the primary K10

0x71268245 Clones driver is currently operating in degraded mode after a previous failure

0x71268246 A Clone is marked as in-sync, but has a stale cookie

0x71268247 Attempt to remove a Clone while it is being synchronized or reverse-synced

0x71268248 A Clone reported a media failure

0x7126824A Cannot remove the Clone it is queued to be synchronized.

0x7126824C The size of the Clone LU is not the same size as the Source LU.

0x7126824D Unable to remove the consistent Clone.

0x7126824E All Clones in the CloneView must be fractured prior to starting a reverse-sync operation

0x7126824F A Clone in the CloneView is currently in the reverse-out-of-sync state.

0x71268250 The maximum number of objects has been exceeded

0x71268251 An existing Clone in the CloneView is reverse-syncing

0x71268252 An existing Clone in the CloneView is syncing

0x71268253 Disk failure due to transient errors exceeding the tolerance level.

0x71268254 Disk failed Returned status.

0x71268255 Aborted due to excess number of bad blocks.

0x71268300 Failed to store an updated administrative action count to PSM

0x71268301 Failed to store updated driver properties to PSM

0x71268302 Insufficient memory available to add a new consumable

0x71268304 Insufficient memory available to write consumables list to PSM

0x71268305 Insufficient memory available to read consumables list from PSM

141

SnapView


0x71268306 Unrecognized revision number for consumables list in PSM

0x71268307 Incorrect amount of data read from PSM for consumables list header

0x71268308 Incorrect amount of data read from PSM for a consumable item

0x71268309 Initialization of database manager failed, driver will be in degraded mode.

0x7126830A Database manager?s CloneView data structure has an unexpected size

0x7126830B Unable to find CloneView with the specified ID

0x7126830C Unable to find a Clone with the specified ID in the given CloneView

0x7126830D Unable to find the specified exported device based on its name

0x7126830E Unable to find the specified exported device based on its WWID

0x7126830F Unable to initialize the database manager from PSM

0x71268310 Insufficient memory available to read Clones driver data from PSM

0x71268311 Incorrect number of bytes returned while reading driver version info from PSM

0x71268312 Incorrect number of bytes returned while reading driver information from PSM

0x71268313 Unrecognized revision of driver information read from PSM

0x71268315 Failed to write driver information to PSM

0x71268316 Insufficient memory available to write driver information to PSM

0x71268319 Failed to increment administrative action count

0x7126831A Failed to set CPL partitions

0x7126831B CPL partitions are not currently defined

0x7126831D Insufficient memory to add a new CloneView

0x7126831E NULL pointer detected while attempting to remove a CloneView from the global list

0x7126831F NULL pointer detected while attempting to delete a CloneView

0x71268321 Insufficient memory available to write Clones data area to PSM

0x71268322 Error writing Clones data area to PSM

0x71268323 Insufficient memory available to read Clones data area from PSM

0x71268324 Insufficient memory available to read Clones data area from PSM

0x71268325 Failed to read complete Clones data area from PSM

0x71268326 Insufficient memory available to list PSM contents

0x71268327 Failed to read Clones data area from PSM

0x71268328 Failed to list contents of PSM

0x71268329 Failed to open PSM device

0x7126832A Failed to locate Clones data area(s) in PSM

0x7126832B Failed to retrieve number of existing entries from PSM

142

SnapView


0x7126832C Open of PSM Clones data area failed

0x7126832D Failure attempting to read Clones data area from PSM

0x71268334 Detected an incomplete write of driver data header information to PSM

0x71268335 Detected an incomplete write of driver data to PSM

0x71268336 Unable to either commit data to PSM or roll back operation during CloneView creation

0x71268337 Failed to write Clones data area to PSM

0x71268338 Failed to write version info for Clones data area to PSM

0x71268339 Detected an incomplete read of the Clones data area version info

0x7126833A Unrecognized revision read from PSM Clones data area

0x7126833B Unable to find a Clone or Source of the specified CloneView

0x7126833C Failed to close a PSM data area

0x7126833D Unable to open CPL LU

0x7126833E Unable to open CPL LU

0x7126833F Unable to set the compatability mode, driver will be degraded. Need to reboot the SP.

0x71268340 Unable to load Clones during rollback, driver will be degraded. Reboot the SP.

0x71268341 Creating CloneView during rollback

0x71268342 Possible problem with PSM during rollback.


0x71268345 PSM contents NULL when attempted to read

0x71268346 Attempting to rollback and CloneView list EMPTY when should have an entry.

0x71268347 Attempting to rollback and CloneView list EMPTY when should have an entry

0x71268348 Unable to remove CloneView during rollback.

0x71268349 Wrong number of CloneView to be adjusted.

0x7126834A Unable to open PSM during rollback.

0x7126834B Found two areas in PMS we can?t open, so unable to proceed with rollback.

0x7126834C Unable to open PSM during rollback to add a CloneView

0x7126834D Unable to close PSM area during rollback.

0x7126834E Unable to read from PSM during rollback.

0x7126834F Unable to read from Clones data area during rollback.

0x71268350 Attempting to read the Clones data area during rollback and unable to allocate memory.

0x71268351 Attempting to read the Clones data area during rollback and unable to

143

SnapView


allocate memory.

0x71268352 Unable to open PSM area during rollback.

0x71268353 During read of PSM in rollback incorrect number of bytes returned.

0x71268354 During read of PSM during rollback incorrect revision number

0x71268355 Failure in reading PSM during rollback.

0x71268356 Failure to read correct number of bytes during rollback.

0x71268357 Unable to add CloneView during rollback.

0x71268358 Unable to add CloneView during rollback.

0x71268359 Unable to update config during rollback.

0x7126835A Attempted to add more than one CloneView during rollback.

0x7126835B Unable to determine number of CloneViews during rollback.

0x7126835C Unable determine if the COD resources are allocated during rollback.

0x7126835D Unable to update the PSM after COD resources are allocated

0x71268500 Failed to initialize lock necessary for trespass operations

0x71268501 Failed to open lock necessary for trespass operations

0x71268502 Failed to close lock necessary for trespass operations

0x71268503 Unexpected authority value while giving up control of a CloneView

0x71268504 Logic flaw caused a semaphore to be released too often while giving up control of a CloneView

0x71268505 Unexpected authority value while taking over control of a CloneView



0x71268508 Invalid mode detected while converting a DLS lock

0x71268509 Unrecognized event detected in the DLS callback handler

0x7126850A Insufficient memory available to send fracture logs to our peer SP

0x7126850B Error initializing bitmap to send fracture logs to our peer SP

0x7126850C Error copying bitmap while attempting to send fracture logs to our peer SP

0x7126850D Insufficient memory to send config data to our peer SP

0x7126850E Unrecognized authority value detected in license

0x7126850F Insufficient memory to create internal work item while taking control of a CloneView

0x71268510 Detected a consistency failure from the config manager concerning the type of sync required

0x71268511 Failed to find the consumable corresponding to the specified CloneView

0x71268512 The CPL is not currently allocated.

0x71268513 Detected an invalid fracture state while attempting to report synchronization progress

144

SnapView


0x71268514 Failed to propagate write due to a missing information about the Clone

0x71268515 Clone write request rejected as the request didn?t come from the Source

0x71268516 Clone write request rejected as the target device is not ready

0x71268517 Insufficient memory to allocate context resources ? write to Clone rejected

0x71268518 Insufficient memory to allocate IRP ? write to Clone rejected

0x71268519 Insufficient memory to allocate MDL ? write to Clone rejected

0x7126851A Simulated immediate I/O failure on the Clone

0x7126851B Simulated I/O failure on the callback path of the Clone

0x7126851C Clone is not currently accepting I/O requests

0x7126851D Config manager couldn?t pend or defer the operation so reboots the SP

0x7126851E During a failure operation an unexpected config status was encountered

0x7126851F Unable to locate the CloneView attempting to lazy trespass

0x71268520 An improper transport event was received and the SP will panic

0x71268521 We attempted a lazy trespass and not enough memory on the system

0x71268522 Unable to assign ownership to CloneView

0x71268523 Unable to determine size of CloneView by WWID

0x71268524 Error during synchronization, Clone or Source device not ready

0x71268525 Unable to allocate the Fast Recovery memory

0x71268526 CloneView failed to allocate the Fast Recovery memory.

0x71268527 Unable to assign ownership of all CloneViews, not enough memory

0x71268528 Unable to quiesce the Clones driver within three minutes.

0x71268529 Unable to add Clone

0x7126852A Unable to assign ownership of all CloneViews, not enough memory.

0x7126852C The CPL is faulted.

0x7126852D Invalid Clone License

0x7126852E Invalid Clone license. System will panic and should come back up and correct situation automatically.

0x7126852F Unable to initialize the Distributed Lock. System will panic and should come back up and correct situation automatically

0x71268530 Unable to open the Distributed Lock. System will panic and should come back up and correct situation automatically

0x71268531 Unable to acquire semaphore. System will panic and should come back up and correct situation automatically

0x71268532 Clone license is invalid. System will panic and should come back up and correct situation automatically

0x71268533 Clone license is invalid. System will panic and should come back up and correct situation automatically

145

SnapView


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.

146

SnapView


0x7128801F Some RollBack data could not be read, but the attempt to mark block %2 on LUN %3 (%4) as bad also failed.

0x71288020 At least %2 I/O errors have been encountered while rolling back LUN %3 (%4); no more errors will be logged for this LUN.

Warning 0x71004000 The Reserved Lun Pool for lun <number> has become <x> percent full

0x71004001 An attempt to open <device> failed with a status of <status>. Removing device from the Reserved Lun Pool

0x71004002 No more Gaggles are available on this SnapView Cache LU.

0x71004003 No more Gaggles are available on this SnapView Cache LU.

0x71004004 A Gaggle with inconsistent signatures was detected.

0x71004005 A SnapView Cache LU did not have sufficient space for one Gaggle.

0x71004006 No unused luns in Reserved Lun Pool

0x71004007 A SnapView Session has been stopped due to an error during the trespass of an LU.

0x71004008 A SnapView Source Logical Unit device has caches being repaired, cannot unbind.

0x71004009 A SnapView Stop of Session has been terminated, due to the Trespass of a Target Device.

0x7100400A SnapView Start of Session %2 in Non Simulation Mode failed, to the existence of a Simulation Mode Session on the same Target.

0x7100400B SnapView Start of Session %2 in Simulation Mode failed, to the existence of a Non Simulation Mode Session on the same Target.

0x7100400C SnapView attempted to Open a Cache LU that has the wrong version in the Header

0x7100400D SnapView attempted to requisition a Chunk Entry for a Session that is Stopping.

0x7100400E SnapView attempted to Stop a Session with a conflicting requisition of a Chunk Entry.

0x7100400F SnapView attempted to Stop a Session that does not exist.

0x71004010 SnapView attempted to Stop a Session while adding a Cache to the Target

0x71004011 SnapView attempted to Stop a Session while adding a Session to the Target

0x71004012 SnapView attempted to Stop a Session while adding a Gaggle to Cache on the Target

0x71004013 While stopping a Session, at least one Chunk entry was found not yet in the Reserved Lun Pool

0x71004014 During a RollBack Session %2 had LUs in Quiesced: %3 Running: %4 Stopping: %5. The driver has attempted to fix the problem.

147

SnapView


0x71004015 This error code is unused.

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.

148

SnapView


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.

149

SnapView


Information 0x71000000 A RollBack operation on LUN %2 (%3) has been initiated for Session %4.

0x71000001 The SnapView Driver has started, compile info %2

0x71000002 The SnapView Driver has stopped

0x71000003 SnapView Session <session> has been started

0x71000004 SnapView Session <session> has been stopped

0x71000006 SnapView has been bound to device <device>

0x71000007 SnapView has been unbound from device <device>

0x71000008 <Lun> has been added to the Reserved Lun Pool

0x71000009 <Lun> has been removed from the Reserved Lun Pool

0x7100000A Snapshot Logical Unit device <device> has been created

0x7100000B Snapshot Logical Unit device <device> has been removed

0x7100000C Chunk size changed from <size> to <size>

0x7100000D Maximum memory allowed changed from <size> to <size>

0x7100000E A VM read operation encountered an uninitialized region.

0x7100000F A RollBack Operation on Device <device> has been initiated for Session <session>.

0x71000010 A RollBack Operation on Device <device> has resumed for Session <session>.

0x71000011 A RollBack Operation on Device <device> has completed successfully for Session <session>.

0x71000012 Device <device> has trespassed to the peer during a RollBack Operation of Session <session>.

0x71000013 Incremental Session <session> has been marked, LUN <number> ( %4 )

0x71000014 Incremental Session <session> has been unmarked, LUN <number> ( %4 )

0x71000015 Incremental Session <session> starting <copy> copy, LUN <number> ( %5 )

0x71000016 Incremental Session <session> completing <copy> copy, LUN <number> ( %5 )

0x71260101 Unable to deallocate Clones Private LUN (CPL) during destroy operation

0x71260102 Received a request to create a CloneView

0x71260103 Received a request to destroy a CloneView

0x71260104 During driver entry unable to open PSM files

0x71260105 Received a request to add a Clone to the CloneView

0x71260106 Received a request to remove a Clone from the CloneView

0x71260108 Received a request to set CloneView properties

0x7126010A Received a request to set Clone properties

0x7126010D Received a request to set driver properties

150

SnapView


0x7126010E Received a request to set driver properties

0x71260110 Received a request to bind Clones into a device stack

0x71260111 Received a request to rebind Clones into a device stack

0x71260112 Received a request to unbind Clones from a device stack

0x71260113 Received a request to enumerate the list of bound LUs which are not part of a CloneView

0x71260115 Received a request to halt I/O to an LU

0x71260116 Received a request to shut down the Clones driver

0x71260117 PSM contents were restored after our peer failed during an update.

0x7126011C Received a request from our peer SP to create a CloneView

0x7126011D Received a request from our peer SP to destroy a CloneView

0x7126011F Received a request from our peer SP to bind Clones into a device stack

0x71260120 Received a request from our peer SP to rebind Clones into a device stack

0x71260121 Received a request from our peer SP to unbind Clones from a device stack

0x71260123 Received a request from our peer SP to update the driver properties

0x71260128 CloneView state was set to active

0x7126012A Clone was fractured by an administrator

0x7126012B Synchronization of an Clone was started by an administrator

0x7126012C Reverse Synchronization of a Clone was started by an administrator

0x7126012D Force Remove all Clones prior to destroying the CloneView

0x71260137 Received a request from our peer SP to halt I/O to an LU

0x7126013A The LU will be rebound after this rebind

0x7126013B The CloneView driver received a command to update the compatability mode

0x7126013C Received a request from our peer to allocate the Frozen Clones Log

0x7126013D Received a request from our peer to free the Frozen Clones Log

0x7126013E Received a request from our peer to allocate the COD resources required to support Frozen Clones

0x7126013F Received a request from our peer to free the COD resources allocated to support Frozen Clones

0x71260140 Create Clone Group (Clone Group ID) returned (status). WriteMapSlot = (Write Intent Slot).

0x71260141 Peer requested Create Clone Group (Clone Group ID). Return Status (status). WriteMapSlot = (Write Intent Slot).

0x71260142 Destroy Clone Group (Clone Group ID) returned (status). WriteMapSlot freed = (Write Intent Slot).

0x71260143 Peer requested Destroy Clone Group (Clone Group ID). Return Status (status). WriteMapSlot freed = (Write Intent Slot).

151

SnapView


0x71260145 Clones Feature software received a commit operation. Status = %2.

0x71260200 A Clone was fractured. If the failure clears automatic resynchronization may be allowed.

0x71260201 A Clone was fractured, and administrator action is required for resynchronization

0x71260202 A Clone has been fractured

0x71260203 An administrator started resynchronization of a Clone

0x71260204 Synchronization of a Clone based on a fracture log was started

0x71260205 Full synchronization of a Clone was started

0x71260206 Clone synchronization completed

0x71260207 A CloneView was automatically activated when its minimum conditions were met

0x71260209 The Clones driver has entered the degraded state. No write requests are allowed.

0x7126020A Reverse-Synchronization of a Clone based on a fracture log was started

0x7126020B Full reverse-synchronization of a Clone was started

0x71260300 Must wait for PSM to become available

0x71260500 The Frozen Clones Log buffers have already been allocated

0x71260501 The Frozen Clones COD resources have already been allocated

0x71260502 Bad blocks encountered on %1 Corresponding bad block generated on %2.

0x71260503 Too many bad blocks found on %1. Bad blocks logging suspended for remainder of this operation.

0x71260600 The Clones driver was successfully loaded

0x71260601 The Clones driver was successfully unloaded

0x71260602 Loading of the Clones driver has started

152

SAN Copy


SAN Copy

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

153

SAN Copy


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.

154

SAN Copy


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

155

IP4700


0x712A002C Attempting to recover the copy session <session> from an SP reboot

0x712A002D Attempting to recover the copy session <session> from a single path failure to device <device>

0x712A002E Auto-Recovery of the copy session <session> is successful

0x712A002F Auto-recovery of the copy session <session> in progress. Waiting on trespass

0x712A0030 Unable to locate the device. Check that the device with this WWN exists.

IP4700 0x26c0 IP4700 event - Critical Error 0x2680 IP4700 event - Error 0x2640 IP4700 event – Warning 0x2600 IP4700 event - Informational

156

IP4700


Copyright © 2000-2005 EMC Corporation. All Rights Reserved.

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.

Documents

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