CPQHSV110V3-MIB

• 0 = TOY clock unavailable; time reset to default date and time.
• 1 = TOY clock time value was less than or equal to the last known time value previously stored in nonvolatile memory; time reset to default date and time.
• 2 = EDC was bad for last known time value previously stored in nonvolatile memory; time reset to default date and time.
• 3 = TOY clock not running; time reset to default date and time.
• 4 = TOY clock time value believed to be accurate; time set to TOY clock time value.

• 0 = The time was set to the time value on this HSV110 controller.
• 1 = The master HSV110 controller requested the slave HSV110 controller to set its time to the time value.
• 2 = The slave HSV110 controller set the local time to the time value.
• 3 = The HSV110 controller's TOY clock was set to the time value.

• If the flags.quorum-disk flag is nonzero, the physical disk drive is the Storage System Quorum disk identified in the quorum-sequence field.
• If the flags.inq-state flag is nonzero, the content of the inq-data and capacity fields is valid.
• If the rss-flags.member-abnormal flag is nonzero, the content of the member-state field is valid.

The reason-code field contains a code giving the reason the physical disk drive has been rendered inoperable:

• 0x001 = CS IO failure
• 0x002 = Scrubber IO failure
• 0x003 = Attempt to set CBIT on normal drive
• 0x004 = Attempt to set CBIT on merging drive
• 0x100 = The Target Discovery Service Descriptor retry count has been exceeded
• 0x101 = Inoperable for Bad Block Replacement
• 0x102 = The soft error count has been exceeded
• 0x103 = The number of exchange timeouts permitted was exceeded
• 0x104 = Communication with drive has failed an excessive number of times
• 0x105 = The number of retries has been exceeded
• 0x106 = Medium/Hardware Errors encountered on this physical disk drive
• 0x107 = The number of Directed LIP's has surpassed the threshold
• 0x200 = Smart event from a physical disk drive not in Storage System
• 0x201 = Smart event from a physical disk drive not a Volume
• 0x202 = Smart event from a physical disk drive not a RSS
• 0x203 = Failure predicted from physical disk drive
• 0x204 = Can't read from physical disk drive from the poll
• 0x205 = Failure predicted from physical disk drive while deleting Disk Group
• 0x206 = physical disk drive forced inoperative from maintenance command for temporary POID
• 0x207 = physical disk drive forced inoperative from maintenance command for POID
• 0x208 = Bad block recovery failed or can't read FPAB
• 0x209 = Failure to remove volume from Storage System
• 0x20A = Failure to update metadata

• 0 = Unrecognized Unexpected Event code.
• 1 = Power failure before initialization could complete.
• 2 = Recursive termination before initialization could complete.
• 3 = Terminated during the first part post-termination preparation.
• 4 = Terminated during the load of the G3 Glue registers.
• 5 = Terminated during the second part post-termination preparation.
• 6 = Terminated during event report block load.
• 7 = Terminated during initialization of all hardware components and software data structures in preparation for restart.
• 8 = Terminated during execution of an unrecognized post-termination operation (premature).
• 9 = Power failure during execution of a post-termination operation.
• A = No good entries found in Termination Event Array. (Note that this condition is expected following the first boot of a newly manufactured HSV110 controller. In that case this event can be safely ignored; no action is necessary.)
• B = The EDC of one or more Termination Event Array entries is bad.
• C = Termination Event Array entry control block revision is different.
• D = Termination Event Array entry information block revision is different.
• E = Termination Event Array entry up time value is greater than the system's up time value.
• F = Termination Event Array entry up time value is less than the previous entry's up time value.
• 10= Termination Event Array entry sequence number value is less than the previous entry's sequence number value.
• 11= Detected an unrecognized dump/restart control code.
• 12= Failed to terminate the entity dump loop.
• 13= Unexpected dump entity size.
• 14= Unexpected Event Log Packet processing stage code.
• 15= Number of Termination Parameters supplied not equal to maximum allowed as required.

The post-termination operation being performed at the time the unexpected event occurred is contained in the uei.pto field. Note: The lteihd and lter fields may not describe the event that caused the HSV110 controller to terminate operation depending on how far termination processing got before the unexpected event occurred.

• 0 = No problems found.

Note: The content of the ainfo fields, cinfo.sctelcbi structure, and minfo.sctelmi structure is undefined.

• 1 = Cookie value is not as expected.
• 2 = Event data overflows the buffer.
• 3 = Event data size is not a multiple of 4 bytes, is less than the minimum, or is greater than the maximum.
• 4 = Event Information Packet type is greater than the maximum.
• 5 = Event information size is not a multiple of 4 bytes, is less than the minimum, is greater than the maximum, doesn't match the Event Information Packet type size, or when combined with the entry header size doesn't equal the entry size.
• 6 = Event code is zero.
• 7 = Event is out of sequence.
• 8 = Dead space area at the end of a partially packed buffer contains a nonzero value.
• 9 = An event data block containing a nonzero value was found after end of event data was detected.
• A = Sequence number reset flag not set as expected.
• B = The event log contains no entries.
• C = Event data block read failed during maintenance verification.
• D = Event data block read failed during maintenance completion.
• E = Event data block erase failed during maintenance completion.
• F = Control block read failed during maintenance verification.
• 17= The event log was destroyed and prepared for re-initialization.

Note: The content of the ainfo fields, cinfo.sctelcbi structure, and minfo.sctelmi structure is undefined.

• F = Control block read failed during maintenance verification.
• 10= Control block write failed during maintenance verification.
• 11= Event data block write failed during maintenance update.
• 12= Control block write failed during maintenance completion.
• 13= Storage System Termination Event Log related send was unsuccessful or the master found that the Storage System Termination Event Log is inaccessible.
• 16= Event data block read failed during retrieval request.

Note: The content of the ainfo fields, cinfo.scelcbi structure, and minfo.scelmi structure is undefined.

• 0 = No problems found.

Note: The content of the ainfo fields, cinfo.scelcbi structure, and minfo.scelmi structure is undefined.

• F = Control block read failed during maintenance verification.
• 10= Control block write failed during maintenance verification.
• 11= Event data block write failed during maintenance update.
• 12= Control block write failed during maintenance completion.
• 13= Storage System Termination Event Log related send was unsuccessful or the master found that the Storage System Termination Event Log is inaccessible.
• 16= Event data block read failed during retrieval request.
• 17= The log was destroyed and prepared for re-initialization.

Note: The content of the ainfo fields, cinfo.scelcbi structure, and minfo.scelmi structure is undefined.

• 0 = No problems found.

Note: The content of the ainfo fields, cinfo.scelcbi structure, and minfo.scelmi structure is undefined.

• 0 = No problems found.

Note: The content of the ainfo fields, cinfo.scelcbi structure, and minfo.scelmi structure is undefined.

• If dencl-num is less than 99, the location is as indicated by the content of the rack-num, dencl-num, and bay fields.
• If dencl-num is equal to 99, the location is unknown. Note that the content of the rack-num and bay fields is undefined in this case.
• If dencl-num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the rack-num, dencl-num, and bay fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate. The identity contained in the device field should be used to confirm the last known location values.

• If enclosures.dencl-num is less than 99, the location is as indicated by the content of the enclosures.rack-num and enclosures.dencl-num fields.
• If enclosures.dencl-num is equal to 99, the enclosures array entry is not used. Note that the content of the enclosures.rack-num field is undefined in this case.
• If enclosures.dencl-num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the enclosures.rack-num and enclosures.dencl-num fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate.

• 1 - Excessive exchange timeouts on loop
• 2 - Excessive link errors on loop
• 3 - Exhausted Link Down retries on loop with signal
• 4 - Exhausted Link Down retries on loop with loss of signal
• 5 - Excessive link inits on loop without completing device discovery

• If dencl-num is less than 99, the location is as indicated by the content of the rack-num, dencl-num, and bay fields.
• If dencl-num is equal to 99, the location is unknown. Note that the content of the rack-num and bay fields is undefined in this case.
• If dencl-num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the rack-num, dencl-num, and bay fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate. The identity contained in the device field should be used to confirm the last known location values.

• If enclosures.dencl-num is less than 99, the location is as indicated by the content of the enclosures.rack-num and enclosures.dencl-num fields.
• If enclosures.dencl-num is equal to 99, the enclosures array entry is not used. Note that the content of the enclosures.rack-num field is undefined in this case.
• If enclosures.dencl-num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the enclosures.rack-num and enclosures.dencl-num fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate.

• If dencl-num is less than 99, the location is as indicated by the content of the rack-num, dencl-num, and bay fields.
• If dencl-num is equal to 99, the location is unknown. Note that the content of the rack-num and bay fields is undefined in this case.
• If dencl-num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the rack-num, dencl-num, and bay fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate. The identity contained in the device field should be used to confirm the last known location values.

• If enclosures.dencl-num is less than 99, the location is as indicated by the content of the enclosures.rack-num and enclosures.dencl-num fields.
• If enclosures.dencl-num is equal to 99, the enclosures array entry is not used. Note that the content of the enclosures.rack-num field is undefined in this case.
• If enclosures.dencl-num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the enclosures.rack-num and enclosures.dencl-num fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate.

• If dencl-num is less than 99, the location is as indicated by the content of the rack-num, dencl-num, and bay fields.
• If dencl-num is equal to 99, the location is unknown. Note that the content of the rack-num and bay fields is undefined in this case.
• If dencl-num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the rack-num, dencl-num, and bay fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate. The identity contained in the device field should be used to confirm the last known location values.

• If dencl-num is less than 99, the location is as indicated by the content of the rack-num, dencl-num, and bay fields.
• If dencl-num is equal to 99, the location is unknown. Note that the content of the rack-num and bay fields is undefined in this case.
• If dencl-num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the rack-num, dencl-num, and bay fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate. The identity contained in the device field should be used to confirm the last known location values.

• If enclosures.dencl-num is less than 99, the location is as indicated by the content of the enclosures.rack-num and enclosures.dencl-num fields.
• If enclosures.dencl-num is equal to 99, the enclosures array entry is not used. Note that the content of the enclosures.rack-num field is undefined in this case.
• If enclosures.dencl-num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the enclosures.rack-num and enclosures.dencl-num fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate.

• If dencl-num is less than 99, the location is as indicated by the content of the rack-num, dencl-num, and bay fields.
• If dencl-num is equal to 99, the location is unknown. Note that the content of the rack-num and bay fields is undefined in this case.
• If dencl-num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the rack-num, dencl-num, and bay fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate. The identity contained in the device field should be used to confirm the last known location values.

• If enclosures.dencl-num is less than 99, the location is as indicated by the content of the enclosures.rack-num and enclosures.dencl-num fields.
• If enclosures.dencl-num is equal to 99, the enclosures array entry is not used. Note that the content of the enclosures.rack-num field is undefined in this case.
• If enclosures.dencl-num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the enclosures.rack-num and enclosures.dencl-num fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate.

• If dencl-num is less than 99, the location is as indicated by the content of the rack-num, dencl-num, and bay fields.
• If dencl-num is equal to 99, the location is unknown. Note that the content of the rack-num and bay fields is undefined in this case.
• If dencl-num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the rack-num, dencl-num, and bay fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate. The identity contained in the device field should be used to confirm the last known location values.

• If enclosures.dencl-num is less than 99, the location is as indicated by the content of the enclosures.rack-num and enclosures.dencl-num fields.
• If enclosures.dencl-num is equal to 99, the enclosures array entry is not used. Note that the content of the enclosures.rack-num field is undefined in this case.
• If enclosures.dencl-num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the enclosures.rack-num and enclosures.dencl-num fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate.

• If dencl-num is less than 99, the location is as indicated by the content of the rack-num, dencl-num, and bay fields.
• If dencl-num is equal to 99, the location is unknown. Note that the content of the rack-num and bay fields is undefined in this case.
• If dencl-num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the rack-num, dencl-num, and bay fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate. The identity contained in the device field should be used to confirm the last known location values.

• If enclosures.dencl-num is less than 99, the location is as indicated by the content of the enclosures.rack-num and enclosures.dencl-num fields.
• If enclosures.dencl-num is equal to 99, the enclosures array entry is not used. Note that the content of the enclosures.rack-num field is undefined in this case.
• If enclosures.dencl-num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the enclosures.rack-num and enclosures.dencl-num fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate.

• If dencl-num is less than 99, the location is as indicated by the content of the rack-num, dencl-num, and bay fields.
• If dencl-num is equal to 99, the location is unknown. Note that the content of the rack-num and bay fields is undefined in this case.
• If dencl-num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the rack-num, dencl-num, and bay fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate. The identity contained in the device field should be used to confirm the last known location values.

• If enclosures.dencl-num is less than 99, the location is as indicated by the content of the enclosures.rack-num and enclosures.dencl-num fields.
• If enclosures.dencl-num is equal to 99, the enclosures array entry is not used. Note that the content of the enclosures.rack-num field is undefined in this case.
• If enclosures.dencl-num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the enclosures.rack-num and enclosures.dencl-num fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate.

• If enclosures.dencl-num is less than 99, the location is as indicated by the content of the enclosures.rack-num and enclosures.dencl-num fields.
• If enclosures.dencl-num is equal to 99, the enclosures array entry is not used. Note that the content of the enclosures.rack-num field is undefined in this case.
• If enclosures.dencl-num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the enclosures.rack-num and enclosures.dencl-num fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate.

• If enclosures.dencl-num is less than 99, the location is as indicated by the content of the enclosures.rack-num and enclosures.dencl-num fields.
• If enclosures.dencl-num is equal to 99, the enclosures array entry is not used. Note that the content of the enclosures.rack-num field is undefined in this case.
• If enclosures.dencl-num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the enclosures.rack-num and enclosures.dencl-num fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate.

• If enclosures.dencl-num is less than 99, the location is as indicated by the content of the enclosures.rack-num and enclosures.dencl-num fields.
• If enclosures.dencl-num is equal to 99, the enclosures array entry is not used. Note that the content of the enclosures.rack-num field is undefined in this case.
• If enclosures.dencl-num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the enclosures.rack-num and enclosures.dencl-num fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate.

• If enclosures.dencl-num is less than 99, the location is as indicated by the content of the enclosures.rack-num and enclosures.dencl-num fields.
• If enclosures.dencl-num is equal to 99, the enclosures array entry is not used. Note that the content of the enclosures.rack-num field is undefined in this case.
• If enclosures.dencl-num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the enclosures.rack-num and enclosures.dencl-num fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate.

• If enclosures.dencl-num is less than 99, the location is as indicated by the content of the enclosures.rack-num and enclosures.dencl-num fields.
• If enclosures.dencl-num is equal to 99, the enclosures array entry is not used. Note that the content of the enclosures.rack-num field is undefined in this case.
• If enclosures.dencl-num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the enclosures.rack-num and enclosures.dencl-num fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate.

• If enclosures.dencl-num is less than 99, the location is as indicated by the content of the enclosures.rack-num and enclosures.dencl-num fields.
• If enclosures.dencl-num is equal to 99, the enclosures array entry is not used. Note that the content of the enclosures.rack-num field is undefined in this case.
• If enclosures.dencl-num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the enclosures.rack-num and enclosures.dencl-num fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate.

• If enclosures.dencl-num is less than 99, the location is as indicated by the content of the enclosures.rack-num and enclosures.dencl-num fields.
• If enclosures.dencl-num is equal to 99, the enclosures array entry is not used. Note that the content of the enclosures.rack-num field is undefined in this case.
• If enclosures.dencl-num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the enclosures.rack-num and enclosures.dencl-num fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate.

• If enclosures.dencl-num is less than 99, the location is as indicated by the content of the enclosures.rack-num and enclosures.dencl-num fields.
• If enclosures.dencl-num is equal to 99, the enclosures array entry is not used. Note that the content of the enclosures.rack-num field is undefined in this case.
• If enclosures.dencl-num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the enclosures.rack-num and enclosures.dencl-num fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate.

• If dencl-num is less than 99, the location is as indicated by the content of the rack-num and dencl-num fields.
• If dencl-num is equal to 99, the location is unknown. Note that the content of the rack-num field is undefined in this case. In addition, the device field may contain all zeroes.
• If dencl-num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the rack-num and dencl-num fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate. The identity contained in the device field should be used to confirm the last known location values.

• If enclosures.dencl-num is less than 99, the location is as indicated by the content of the enclosures.rack-num and enclosures.dencl-num fields.
• If enclosures.dencl-num is equal to 99, the enclosures array entry is not used. Note that the content of the enclosures.rack-num field is undefined in this case.
• If enclosures.dencl-num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the enclosures.rack-num and enclosures.dencl-num fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate.

• If enclosures.dencl-num is less than 99, the location is as indicated by the content of the enclosures.rack-num and enclosures.dencl-num fields.
• If enclosures.dencl-num is equal to 99, the enclosures array entry is not used. Note that the content of the enclosures.rack-num field is undefined in this case.
• If enclosures.dencl-num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the enclosures.rack-num and enclosures.dencl-num fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate.

• If dencl-num is less than 99, the location is as indicated by the content of the rack-num, dencl-num, and bay fields.
• If dencl-num is equal to 99, the location is unknown. Note that the content of the rack-num and bay fields is undefined in this case.
• If dencl-num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the rack-num, dencl-num, and bay fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate. The identity contained in the device field should be used to confirm the last known location values.

• If enclosures.dencl-num is less than 99, the location is as indicated by the content of the enclosures.rack-num and enclosures.dencl-num fields.
• If enclosures.dencl-num is equal to 99, the enclosures array entry is not used. Note that the content of the enclosures.rack-num field is undefined in this case.
• If enclosures.dencl-num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the enclosures.rack-num and enclosures.dencl-num fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate.

• If enclosures.dencl-num is less than 99, the location is as indicated by the content of the enclosures.rack-num and enclosures.dencl-num fields.
• If enclosures.dencl-num is equal to 99, the enclosures array entry is not used. Note that the content of the enclosures.rack-num field is undefined in this case.
• If enclosures.dencl-num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the enclosures.rack-num and enclosures.dencl-num fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate.

• If dencl-num is less than 99, the location is as indicated by the content of the rack-num, dencl-num, and bay fields.
• If dencl-num is equal to 99, the location is unknown. Note that the content of the rack-num and bay fields is undefined in this case.
• If dencl-num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the rack-num, dencl-num, and bay fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate. The identity contained in the device field should be used to confirm the last known location values.

• If enclosures.dencl-num is less than 99, the location is as indicated by the content of the enclosures.rack-num and enclosures.dencl-num fields.
• If enclosures.dencl-num is equal to 99, the enclosures array entry is not used. Note that the content of the enclosures.rack-num field is undefined in this case.
• If enclosures.dencl-num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the enclosures.rack-num and enclosures.dencl-num fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate.

• If dencl-num is less than 99, the location is as indicated by the content of the rack-num, dencl-num, and bay fields.
• If dencl-num is equal to 99, the location is unknown. Note that the content of the rack-num and bay fields is undefined in this case.
• If dencl-num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the rack-num, dencl-num, and bay fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate. The identity contained in the device field should be used to confirm the last known location values.

• If enclosures.dencl-num is less than 99, the location is as indicated by the content of the enclosures.rack-num and enclosures.dencl-num fields.
• If enclosures.dencl-num is equal to 99, the enclosures array entry is not used. Note that the content of the enclosures.rack-num field is undefined in this case.
• If enclosures.dencl-num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the enclosures.rack-num and enclosures.dencl-num fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate.

• If dencl-num is less than 99, the location is as indicated by the content of the rack-num, dencl-num, and bay fields.
• If dencl-num is equal to 99, the location is unknown. Note that the content of the rack-num and bay fields is undefined in this case.
• If dencl-num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the rack-num, dencl-num, and bay fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate. The identity contained in the device field should be used to confirm the last known location values.

• If enclosures.dencl-num is less than 99, the location is as indicated by the content of the enclosures.rack-num and enclosures.dencl-num fields.
• If enclosures.dencl-num is equal to 99, the enclosures array entry is not used. Note that the content of the enclosures.rack-num field is undefined in this case.
• If enclosures.dencl-num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the enclosures.rack-num and enclosures.dencl-num fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate.

• If dencl-num is less than 99, the location is as indicated by the content of the rack-num, dencl-num, and bay fields.
• If dencl-num is equal to 99, the location is unknown. Note that the content of the rack-num and bay fields is undefined in this case.
• If dencl-num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the rack-num, dencl-num, and bay fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate. The identity contained in the device field should be used to confirm the last known location values.

• If enclosures.dencl-num is less than 99, the location is as indicated by the content of the enclosures.rack-num and enclosures.dencl-num fields.
• If enclosures.dencl-num is equal to 99, the enclosures array entry is not used. Note that the content of the enclosures.rack-num field is undefined in this case.
• If enclosures.dencl-num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the enclosures.rack-num and enclosures.dencl-num fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate.

• If dencl-num is less than 99, the location is as indicated by the content of the rack-num, dencl-num, and bay fields.
• If dencl-num is equal to 99, the location is unknown. Note that the content of the rack-num and bay fields is undefined in this case.
• If dencl-num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the rack-num, dencl-num, and bay fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate. The identity contained in the device field should be used to confirm the last known location values.

• If enclosures.dencl-num is less than 99, the location is as indicated by the content of the enclosures.rack-num and enclosures.dencl-num fields.
• If enclosures.dencl-num is equal to 99, the enclosures array entry is not used. Note that the content of the enclosures.rack-num field is undefined in this case.
• If enclosures.dencl-num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the enclosures.rack-num and enclosures.dencl-num fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate.

• If dencl-num is less than 99, the location is as indicated by the content of the rack-num, dencl-num, and bay fields.
• If dencl-num is equal to 99, the location is unknown. Note that the content of the rack-num and bay fields is undefined in this case.
• If dencl-num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the rack-num, dencl-num, and bay fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate. The identity contained in the device field should be used to confirm the last known location values.

• If enclosures.dencl-num is less than 99, the location is as indicated by the content of the enclosures.rack-num and enclosures.dencl-num fields.
• If enclosures.dencl-num is equal to 99, the enclosures array entry is not used. Note that the content of the enclosures.rack-num field is undefined in this case.
• If enclosures.dencl-num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the enclosures.rack-num and enclosures.dencl-num fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate.

• If enclosures.dencl-num is less than 99, the location is as indicated by the content of the enclosures.rack-num and enclosures.dencl-num fields.
• If enclosures.dencl-num is equal to 99, the enclosures array entry is not used. Note that the content of the enclosures.rack-num field is undefined in this case.
• If enclosures.dencl-num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the enclosures.rack-num and enclosures.dencl-num fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate.

• If enclosures.dencl-num is less than 99, the location is as indicated by the content of the enclosures.rack-num and enclosures.dencl-num fields.
• If enclosures.dencl-num is equal to 99, the enclosures array entry is not used. Note that the content of the enclosures.rack-num field is undefined in this case.
• If enclosures.dencl-num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the enclosures.rack-num and enclosures.dencl-num fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate.

• If dencl-num is less than 99, the location is as indicated by the content of the rack-num, dencl-num, and bay fields.
• If dencl-num is equal to 99, the location is unknown. Note that the content of the rack-num and bay fields is undefined in this case.
• If dencl-num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the rack-num, dencl-num, and bay fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate. The identity contained in the device field should be used to confirm the last known location values.

• If enclosures.dencl-num is less than 99, the location is as indicated by the content of the enclosures.rack-num and enclosures.dencl-num fields.
• If enclosures.dencl-num is equal to 99, the enclosures array entry is not used. Note that the content of the enclosures.rack-num field is undefined in this case.
• If enclosures.dencl-num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the enclosures.rack-num and enclosures.dencl-num fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate.

• If dencl-num is less than 99, the location is as indicated by the content of the rack-num, dencl-num, and bay fields.
• If dencl-num is equal to 99, the location is unknown. Note that the content of the rack-num and bay fields is undefined in this case.
• If dencl-num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the rack-num, dencl-num, and bay fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate. The identity contained in the device field should be used to confirm the last known location values.

• If enclosures.dencl-num is less than 99, the location is as indicated by the content of the enclosures.rack-num and enclosures.dencl-num fields.
• If enclosures.dencl-num is equal to 99, the enclosures array entry is not used. Note that the content of the enclosures.rack-num field is undefined in this case.
• If enclosures.dencl-num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the enclosures.rack-num and enclosures.dencl-num fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate.

• If dencl-num is less than 99, the location is as indicated by the content of the rack-num, dencl-num, and bay fields.
• If dencl-num is equal to 99, the location is unknown. Note that the content of the rack-num and bay fields is undefined in this case.
• If dencl-num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the rack-num, dencl-num, and bay fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate. The identity contained in the device field should be used to confirm the last known location values.

• If enclosures.dencl-num is less than 99, the location is as indicated by the content of the enclosures.rack-num and enclosures.dencl-num fields.
• If enclosures.dencl-num is equal to 99, the enclosures array entry is not used. Note that the content of the enclosures.rack-num field is undefined in this case.
• If enclosures.dencl-num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the enclosures.rack-num and enclosures.dencl-num fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate.

• If dencl-num is less than 99, the location is as indicated by the content of the rack-num, dencl-num, and bay fields.
• If dencl-num is equal to 99, the location is unknown. Note that the content of the rack-num and bay fields is undefined in this case.
• If dencl-num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the rack-num, dencl-num, and bay fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate. The identity contained in the device field should be used to confirm the last known location values.

• If enclosures.dencl-num is less than 99, the location is as indicated by the content of the enclosures.rack-num and enclosures.dencl-num fields.
• If enclosures.dencl-num is equal to 99, the enclosures array entry is not used. Note that the content of the enclosures.rack-num field is undefined in this case.
• If enclosures.dencl-num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the enclosures.rack-num and enclosures.dencl-num fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate.

• If dencl-num is less than 99, the location is as indicated by the content of the rack-num, dencl-num, and bay fields.
• If dencl-num is equal to 99, the location is unknown. Note that the content of the rack-num and bay fields is undefined in this case.
• If dencl-num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the rack-num, dencl-num, and bay fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate. The identity contained in the device field should be used to confirm the last known location values.

• If enclosures.dencl-num is less than 99, the location is as indicated by the content of the enclosures.rack-num and enclosures.dencl-num fields.
• If enclosures.dencl-num is equal to 99, the enclosures array entry is not used. Note that the content of the enclosures.rack-num field is undefined in this case.
• If enclosures.dencl-num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the enclosures.rack-num and enclosures.dencl-num fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate.

• 1 = The physical disk drive left itself bypassed
• 2 = The Drive Enclosure Environmental Monitoring Unit bypassed the drive bay

• If dencl-num is less than 99, the location is as indicated by the content of the rack-num, dencl-num, and bay fields.
• If dencl-num is equal to 99, the location is unknown. Note that the content of the rack-num and bay fields is undefined in this case.
• If dencl-num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the rack-num, dencl-num, and bay fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate. The identity contained in the device field should be used to confirm the last known location values.

• If dencl-num is less than 99, the location is as indicated by the content of the rack-num and dencl-num fields.
• If dencl-num is equal to 99, the location is unknown. Note that the content of the rack-num field is undefined in this case.
• If dencl-num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the rack-num and dencl-num fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate. The identity contained in the device field should be used to confirm the last known location values.

• If enclosures.dencl-num is less than 99, the location is as indicated by the content of the enclosures.rack-num and enclosures.dencl-num fields.
• If enclosures.dencl-num is equal to 99, the enclosures array entry is not used. Note that the content of the enclosures.rack-num field is undefined in this case.
• If enclosures.dencl-num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the enclosures.rack-num and enclosures.dencl-num fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate.

• If dencl-num is less than 99, the location is as indicated by the content of the rack-num and dencl-num fields.
• If dencl-num is equal to 99, the location is unknown. Note that the content of the rack-num field is undefined in this case.
• If dencl-num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the rack-num and dencl-num fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate. The identity contained in the device field should be used to confirm the last known location values.

• If enclosures.dencl-num is less than 99, the location is as indicated by the content of the enclosures.rack-num and enclosures.dencl-num fields.
• If enclosures.dencl-num is equal to 99, the enclosures array entry is not used. Note that the content of the enclosures.rack-num field is undefined in this case.
• If enclosures.dencl-num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the enclosures.rack-num and enclosures.dencl-num fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate.

• If dencl-num is less than 99, the location is as indicated by the content of the rack-num, dencl-num, and bay fields.
• If dencl-num is equal to 99, the location is unknown. Note that the content of the rack-num, al-pa and bay fields is undefined in this case.
• If dencl-num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the rack-num, dencl-num, and bay fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate. The identity contained in the device field should be used to confirm the last known location values.

• If enclosures.dencl-num is less than 99, the location is as indicated by the content of the enclosures.rack-num and enclosures.dencl-num fields.
• If enclosures.dencl-num is equal to 99, the enclosures array entry is not used. Note that the content of the enclosures.rack-num field is undefined in this case.
• If enclosures.dencl-num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the enclosures.rack-num and enclosures.dencl-num fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate.

• If dencl-num is less than 99, the location is as indicated by the content of the rack-num, dencl-num, and bay fields.
• If dencl-num is equal to 99, the location is unknown. Note that the content of the rack-num, al-pa and bay fields is undefined in this case.
• If dencl-num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the rack-num, dencl-num, and bay fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate. The identity contained in the device field should be used to confirm the last known location values.

• If enclosures.dencl-num is less than 99, the location is as indicated by the content of the enclosures.rack-num and enclosures.dencl-num fields.
• If enclosures.dencl-num is equal to 99, the enclosures array entry is not used. Note that the content of the enclosures.rack-num field is undefined in this case.
• If enclosures.dencl-num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the enclosures.rack-num and enclosures.dencl-num fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate.

• If dencl-num is less than 99, the location is as indicated by the content of the rack-num, dencl-num, and bay fields.
• If dencl-num is equal to 99, the location is unknown. Note that the content of the rack-num, al-pa and bay fields is undefined in this case.
• If dencl-num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the rack-num, dencl-num, and bay fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate. The identity contained in the device field should be used to confirm the last known location values.

• If enclosures.dencl-num is less than 99, the location is as indicated by the content of the enclosures.rack-num and enclosures.dencl-num fields.
• If enclosures.dencl-num is equal to 99, the enclosures array entry is not used. Note that the content of the enclosures.rack-num field is undefined in this case.
• If enclosures.dencl-num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the enclosures.rack-num and enclosures.dencl-num fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate.

• If dencl-num is less than 99, the location is as indicated by the content of the rack-num, dencl-num, and bay fields.
• If dencl-num is equal to 99, the location is unknown. Note that the content of the rack-num, al-pa and bay fields is undefined in this case.
• If dencl-num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the rack-num, dencl-num, and bay fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate. The identity contained in the device field should be used to confirm the last known location values.

• If enclosures.dencl-num is less than 99, the location is as indicated by the content of the enclosures.rack-num and enclosures.dencl-num fields.
• If enclosures.dencl-num is equal to 99, the enclosures array entry is not used. Note that the content of the enclosures.rack-num field is undefined in this case.
• If enclosures.dencl-num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the enclosures.rack-num and enclosures.dencl-num fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate.

• 0 = Attempting to retry the allocation
• 1 = Awaiting a leveling event (a drive needs to be inserted)

• 0 = Attempting to retry the expansion
• 1 = Awaiting a leveling event (a drive needs to be inserted)

• 2 = Reconstructing
• 4 = Migrating
• 6 = Reverting

• 2 = Reconstructing
• 4 = Migrating
• 6 = Reverting

• 1 = PSEGS NONE ( Reconstruction of data was successful )
• 2 = PSEGS RAID0 ( Could not reconstruct RAID0 data )
• 4 = PSEGS RAID5 ( Could not reconstruct RAID5 data )
• 8 = PSEGS RAID1 ( Could not reconstruct RAID1 data )

• 4 = Merge began
• 8 = Split began

• 4 = Merge completed
• 8 = Split completed

• 2 = Degraded
• 3 = Failed
• 4 = Not present
• 5 = Single Port on Fibre

• 1 = Normal - Volume is present and operating normally
• 2 = Migrating - Data from this volume is being moved to other storage in this Disk Group
• 3 = Missing - Volume is inaccessible
• 4 = Reconstructing - Volume is inaccessible; redundant data is being regenerated and moved to other storage in this Disk Group
• 5 = Completing - This previously inaccessible volume has become accessible; data migration is being completed
• 6 = Reverting - This previously inaccessible volume has become accessible; data is being regenerated
• 7 = Failed - Volume is not being used in the Disk Group; disk errors are preventing normal usage

• 1 = Normal
• 2 = Replacement delay in progress
• 3 = Redundancy lost, restore in progress
• 4 = Redundancy lost, restore stalled
• 5 = Failed
• 6 = Creation in progress
• 7 = Snapshot is inoperative due to lack of snapshot space
• 8 = Deletion in progress
• 9 = Capacity change in progress
• 10 = Inoperative due to data lost
• 11 = Capacity reservation in progress
• 12 = Capacity unreservation in progress

• 1 = Battery System Hold-up Time is greater than 96 hours
• 3 = Battery System Hold-up Time is greater than 0 and less than 96 hours
• 5 = Battery System Hold-up Time is zero hours

• 1 = Normal - Volume is present and operating normally
• 2 = Migrating - Data from this volume is being moved to other storage in this Disk Group
• 4 = Reconstructing - Volume is inaccessible; redundant data is being regenerated and moved to other storage in this Disk Group
• 5 = Completing - This previously inaccessible volume has become accessible; data migration is being completed
• 6 = Reverting - This previously inaccessible volume has become accessible; data is being regenerated
• 7 = Failed - Volume is not being used in the Disk Group; disk errors are preventing normal usage

Note that the HSV110 controller's internal identity of the affected Fibre Channel port is contained in the secondary-id field.

• 0 = Not quorum disk
• 1 = Quorum disk

• 1 = Normal - Volume is present and operating normally
• 2 = Migrating - Data from this volume is being moved to other storage in this Disk Group
• 3 = Missing - Volume is inaccessible
• 4 = Reconstructing - Volume is inaccessible; redundant data is being regenerated and moved to other storage in this Disk Group
• 5 = Completing - This previously inaccessible volume has become accessible; data migration is being completed
• 6 = Reverting - This previously inaccessible volume has become accessible; data is being regenerated

• 2 = Disk Group with no redundancy is inoperative
• 3 = Disk Group with parity redundancy is inoperative
• 4 = Disk Group with mirrored redundancy is inoperative
• 5 = Disk Group with no redundancy is inoperative, marked for re-use
• 6 = Disk Group with parity redundancy is inoperative, marked for re-use
• 7 = Disk Group with mirrored redundancy is inoperative, marked for re-use

• 1 = Battery System Hold-up Time is greater than 96 hours
• 3 = Battery System Hold-up Time is greater than 0 and less than 96 hours
• 5 = Battery System Hold-up Time is zero hours

• 50 = The host is already logged in
• 101 = Maximum number of logins is exceeded
• 102 = Invalid cookie was sent
• 106 = The password is not set on the HSV110 controller

• 1 = Normal
• 3 = Failed
• 4 = Not present
• 5 = Single Port on Fibre

• 1 = Normal
• 2 = Degraded
• 4 = Not present
• 5 = Single Port on Fibre

• 1 = Vraid0
• 2 = Vraid1
• 3 = Vraid5

• 1 = Vraid0
• 2 = Vraid1
• 3 = Vraid5

• 1 = Vraid0
• 2 = Vraid1
• 3 = Vraid5

• 0 = Unknown
• 1 = User defined
• 2 = Unused
• 3 = WINNT with SecurePath
• 4 = VMS
• 5 = TRU64 UNIX
• 6 = Sun UNIX
• 7 = NetWare
• 8 = HP
• 9 = IBM
• 10 = LINUX
• 11 = SCO UNIX

• 1 = Manual policy
• 2 = Automatic policy

• 0 = Not quiescent
• 1 = Quiescent

• 1 = Disabled
• 2 = Enabled

The old-attr.type field and the new-attr.type fields contain the value 1. The old-attr.value.u32[0] field contains the old Write Cache Policy. The new-attr.value.u32[0] field contains the new Write Cache Policy. The policy values that may be found in the old-attr.value.u32[0] and new-attr.value.u32[0] fields are as follows:

• 1 = Writethrough
• 2 = Writeback

The old-attr.value.u32[1] field contains the old Read Cache Policy. The new-attr.value.u32[1] field contains the new Read Cache Policy. The policy values that may be found in the old-attr.value.u32[1] and new-attr.value.u32[1] fields are as follows:

• 1 = Read cache on
• 2 = Read cache off

The old-attr.value.u32[2] field contains the old Cache Mirroring Policy. The new-attr.value.u32[2] field contains the new Cache Mirroring Policy. The policy values that may be found in the old-attr.value.u32[2] and new-attr.value.u32[2] fields are as follows:

• 1 = Mirror
• 2 = No mirror

• 1 = Disk Group
• 2 = Reserved
• 4 - 20 = temporary usage reserved for drive code load

• 0 = Write protect off
• 1 = Write protect on

The old-attr.type field and field contain the value 1. The old-attr.value.u32[0] field indicates the type of restart that was requested as follows:

• 0 = None -- no restart
• 1 = Regular -- full restart, host system connectivity is lost until the controller returns to normal operation
• 2 = Fast -- resynchronization, restart of the controller in a manner that has little or no impact on host system connectivity

The old-attr.value.u32[1] field indicates whether the other HSV110 controller of the pair was requested to remain operational or to also shutdown as follows:

• 0 = Remain operational
• 1 = Coupled shutdown

The old-attr.value.u32[2] field indicates whether the HSV110 controller was requested to remain in the power on state or power itself off as follows:

• 0 = Remain in the power on state
• 1 = Power itself off

The old-attr.value.u32[3] field value indicates whether the Physical Disk Drive enclosure(s) was requested to remain in the power on state or to be powered off as follows:

• 0 = Remain in the power on state
• 1 = Powered off

The old-attr.value.u32[4] field value indicates whether the battery assemblies located within the HSV110 controller were requested to be enabled or disabled as follows:

• 0 = Enabled
• 1 = Disabled

The old-attr.value.u32[5] field contains the number of seconds the shutdown operation was requested to be delayed.

The old-attr.type field contain the value 1. The old-attr.value.u32[0] field value indicates the result of the HSV110 controller Cache Memory shutdown operation as follows:

• 1 = Success
• 2 = Failure
• 3 = Not applicable

The old-attr.value.u32[1] field contains the internal Storage System Management Interface cache shutdown status code.

The old-attr.value.u32[2] field value indicates the result of the Physical Disk Drive enclosure(s) power off operation as follows:

• 1 = Success
• 2 = Failure
• 3 = Not applicable

The old-attr.value.u32[3] field contains the internal Storage System Management Interface Physical Disk Drive enclosure(s) power off status code.

The old-attr.value.u32[4] field value indicates the result of the battery assemblies disable operation as follows:

• 1 = Success
• 2 = Failure
• 3 = Not applicable

The old-attr.value.u32[5] field value indicates the battery assemblies disable operation failure mode as follows:

• 0 = No failure indicated.
• 1 = Failed only on the HSV110 controller identified in the handle field.
• 2 = Failed only on the other HSV110 controller of the pair.
• 3 = Failed on both HSV110 controllers.

• 1 = Failsafe Disabled
• 2 = Failsafe Enabled

• 0 = Normal Active Source
• 1 = Normal Active Destination
• 2 = Active/Active (Master)
• 3 = Active/Active (Non-Master)

• 1 = Synchronous
• 2 = Asynchronous

• 0 = Data Replication Destination Storage System Virtual Disk disabled for read access.
• 1 = Data Replication Destination Storage System Virtual Disk enabled for read access.

• 0 = Normal Active Source
• 1 = Normal Active Destination
• 2 = Active/Active (Master)
• 3 = Active/Active (Non-Master)

• 1 = Connection between the Data Replication Source and Data Replication Destination is active.
• 2 = Connection between the Data Replication Source and Data Replication Destination is inactive.

• 1 = Normal
• 2 = Disk Group with no redundancy is inoperative
• 3 = Disk Group with parity redundancy is inoperative
• 4 = Disk Group with mirrored redundancy is inoperative
• 5 = Disk Group with no redundancy is inoperative, marked for re-use
• 6 = Disk Group with parity redundancy is inoperative, marked for re-use
• 7 = Disk Group with mirrored redundancy is inoperative, marked for re-use

• 1 = Normal
• 2 = Replacement delay in progress
• 3 = Redundancy lost, restore in progress
• 4 = Redundancy lost, restore stalled
• 6 = Creation in progress
• 7 = Snapshot is inoperative due to lack of snapshot space
• 8 = Deletion in progress
• 9 = Capacity change in progress
• 10 = Inoperative due to data lost
• 11 = Capacity reservation in progress
• 12 = Capacity unreservation in progress

• 1 = Normal
• 2 = Replacement delay in progress
• 3 = Redundancy lost, restore in progress
• 4 = Redundancy lost, restore stalled
• 5 = Failed
• 6 = Creation in progress
• 8 = Deletion in progress
• 9 = Capacity change in progress
• 10 = Inoperative due to device data lost
• 11 = Capacity reservation in progress
• 12 = Capacity unreservation in progress

• 1 = Normal
• 2 = Replacement delay in progress
• 3 = Redundancy lost restore, in progress
• 4 = Redundancy lost restore, stalled
• 5 = Failed
• 6 = Creation in progress
• 7 = Snapshot is inoperative due to lack of snapshot space
• 8 = Deletion in progress
• 9 = Capacity change in progress
• 11 = Capacity reservation in progress
• 12 = Capacity unreservation in progress

Note that the HSV110 controller's internal identity of the affected Fibre Channel port is contained in the secondary-id field.

• 1 = Normal
• 2 = Disk Group with no redundancy is inoperative
• 3 = Disk Group with parity redundancy is inoperative
• 4 = Disk Group with mirrored redundancy is inoperative
• 5 = Disk Group with no redundancy is inoperative, marked for re-use
• 6 = Disk Group with parity redundancy is inoperative, marked for re-use
• 7 = Disk Group with mirrored redundancy is inoperative, marked for re-use

• 1 = Normal
• 2 = Degraded
• 3 = Failed
• 5 = Single Port on Fibre

• 1 = Normal
• 2 = Degraded
• 3 = Failed
• 4 = Not Present