HP StorageWorks 7100 Appendix A. Disk Array Controller Log - Page 8

HP StorageWorks 7100 - Virtual Array Manual

Page 8 highlights

FC-SCSI Interface SpecificationDescribes the IceCube SCSI interface. Targetted as part of OEM manual.Disk Array Con Error! No text of specified style in document. Event Number (dec/hex) Event Name Predictive Maintenance Implication Suspected Components Description Logged? Mfg Fail? 103/0x67 104/0x68 JM Write Recovered With Y Retries Force Unit Access Failed with Y no Sense Data Ignore - See Accompanying Errors Ignore - See accompanying errors None Cache 105/0x69 106/0x6a 107/0x6b 108/0x6c 109/0x6d Host DATA-OUT FCP-DL and Y CDB transfer lengths not equal Host Block command Y attempted with FCP-DL NOT a block size LUN Security prevents the N requested operation An unsupported operation was Y attempted on a snapshot LUN Ignore - Host Protocol Incompatibility Ignore - Host Protocol Incompatibility Ignore - Host LUN addressing problem Ignore - Incorrect host behavior None None None None flush of storage object failed Y disallow snapshot None 110/0x6e 111/0x6f 112/0x70 113/0x71 114/0x72 115/0x73 116/0x74 117/0x75 Parameter Value Invalid Host is not authorized to read from a LUN Host can not be authenticated to access LUN Security map N None Y Ignore - Host None doesn't have permission to access LUN Y Ignore - Provide None correct password Limit to Maximum number of Y Ignore - Remove None Principals is reached unwanted associations from Security map Host is not authorized to write Y Ignore - Host None to a LUN doesn't have permission to access LUN Feature is not licensed N Ignore - Host None Porblem Hot plug or LIP occured during Y Ignore - should None processing of passthrough be handled by host Unexpected JBOD Error Y Unknown JBOD ESD 118/0x76 119/0x77 Recovered By Enclosure Service Device (ESD) PassThru request Failed Y See information JBOD ESD provided by JBOD vendor Y Ignore - Should JBOD ESD be handled by host 120/0x78 JBOD ESD IO Failed Due To N N.A. None ESD Removal 121/0x79 Mode Select command failed due to NV memory write failure Y None of these are Midplane allowed count as one try of the I/O. N Retries were used by the JM module in the successful completion of a write. N A forced unit access write command failed. The component returning the bad return code may not have provided valid sense data to notify the host that an error has occurred. Cache will fill in valid sense data to alert the host to the write failure. Y A Host DATA-OUT phase attempted to use an FCP-DL parameter that does NOT exactly match the targets desired data transfer length. Y The Host attempted to perform a block oriented command but the FCP-DL parameter was not a multiple of a SCSI block size. Y The Host attempted to perform an operation on a LUN that LUN security, in the current configuration, prohibits. Y The Host attempted to perform a command, on a snapshot LUN, that required an operation that is unsupported for snapshots. Y in preparation for a snapshot of a particular storage object, the system will attempt to flush all writes for the storage object from the cache to the back-end disks. If, for any reason the flush does not complete successfully, the snap must not be allowed to proceed. N Parameter Value Invalid Y The Host attempted to perform an operation on LUN without having an appropriate access permission. N The Host failed the authentication for access to LUN Security map because the password that it presented is incorrect. N The LUN Security Utility cannot be allowed to add any more associations for new Principals since the maximum limit for Principals set in the firmware is reached. Y The Host attempted to perform an operation on a LUN without having an appropriate access permission. Y A host request was found to use a feature without having purchased its license. N The host Pass through request was not successfull. This could be due to a LIP or Hot Reset of the device. N The JBOD ESD returned CHECK CONDITION status with sense information not handled by the JBOD error recovery algorithms. The JBOD retries are exhausted or the I/O is not retryable. N The disk drive returned a status of CHECK_CONDITION, RECOVERED_ERROR N The requested command (valid or NotValid) has Failed to be sent to the requested JBOD ESD due to the fact that there is no valid Path for communication to the desired device at the current time. N Subsequent to a hot removal, the ESD's (JEM/JBOD Enclosure Manager) destroy method was invoked. I/O's in the JEM's waiting queue are flushed with this status. Y An attempt to write new mode parameter data to the chassis NV memory failed. As a result, none of the mode parameter changes are being recorded. If the chassis NV memory problems persist, the mode

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27

FC-SCSI Interface Specification
Describes the IceCube SCSI interface. Targetted as part of OEM manual.
Disk Array Con
Error! No text of specified style in document.
Event
Number
(dec/hex)
Event
Name
Logged?
Predictive
Maintenance
Implication
Suspected
Components
Mfg Fail?
Description
count as one try of the I/O.
103/0x67
JM Write Recovered With
Retries
Y
Ignore - See
Accompanying
Errors
None
N
Retries were used by the JM module in the
successful completion of a write.
104/0x68
Force Unit Access Failed with
no Sense Data
Y
Ignore - See
accompanying
errors
Cache
N
A forced unit access write command failed. The
component returning the bad return code may not
have provided valid sense data to notify the host that
an error has occurred.
Cache will fill in valid sense
data to alert the host to the write failure.
105/0x69
Host DATA-OUT FCP-DL and
CDB transfer lengths not equal
Y
Ignore - Host
Protocol
Incompatibility
None
Y
A Host DATA-OUT phase attempted to use an
FCP-DL parameter that does NOT exactly match the
targets desired data transfer length.
106/0x6a
Host Block command
attempted with FCP-DL NOT a
block size
Y
Ignore - Host
Protocol
Incompatibility
None
Y
The Host attempted to perform a block oriented
command but the FCP-DL parameter was not a
multiple of a SCSI block size.
107/0x6b
LUN Security prevents the
requested operation
N
Ignore - Host
LUN addressing
problem
None
Y
The Host attempted to perform an operation on a
LUN that LUN security, in the current
configuration, prohibits.
108/0x6c
An unsupported operation was
attempted on a snapshot LUN
Y
Ignore - Incorrect
host behavior
None
Y
The Host attempted to perform a command, on a
snapshot LUN, that required an operation that is
unsupported for snapshots.
109/0x6d
flush of storage object failed
Y
disallow
snapshot
None
Y
in preparation for a snapshot of a particular storage
object, the system will attempt to flush all writes for
the storage object from the cache to the back-end
disks. If, for any reason the flush does not complete
successfully, the snap must not be allowed to
proceed.
110/0x6e
Parameter Value Invalid
N
None
N
Parameter Value Invalid
111/0x6f
Host is not authorized to read
from a LUN
Y
Ignore - Host
doesn’t have
permission to
access LUN
None
Y
The Host attempted to perform an operation on
LUN without having an appropriate access
permission.
112/0x70
Host can not be authenticated
to access LUN Security map
Y
Ignore - Provide
correct password
None
N
The Host failed the authentication for access to
LUN Security map because the password that it
presented is incorrect.
113/0x71
Limit to Maximum number of
Principals is reached
Y
Ignore - Remove
unwanted
associations from
Security map
None
N
The LUN Security Utility cannot be allowed to add
any more associations for new Principals since the
maximum limit for Principals set in the firmware is
reached.
114/0x72
Host is not authorized to write
to a LUN
Y
Ignore - Host
doesn’t have
permission to
access LUN
None
Y
The Host attempted to perform an operation on a
LUN without having an appropriate access
permission.
115/0x73
Feature is not licensed
N
Ignore - Host
Porblem
None
Y
A host request was found to use a feature without
having purchased its license.
116/0x74
Hot plug or LIP occured during
processing of passthrough
Y
Ignore - should
be handled by
host
None
N
The host Pass through request was not successfull.
This could be due to a LIP or Hot Reset of the
device.
117/0x75
Unexpected JBOD Error
Y
Unknown
JBOD ESD
N
The JBOD ESD returned CHECK CONDITION
status with sense information not handled by the
JBOD error recovery algorithms.
The JBOD retries
are exhausted or the I/O is not retryable.
118/0x76
Recovered By Enclosure
Service Device (ESD)
Y
See information
provided by
JBOD vendor
JBOD ESD
N
The disk drive returned a status of
CHECK_CONDITION, RECOVERED_ERROR
119/0x77
PassThru request Failed
Y
Ignore - Should
be handled by
host
JBOD ESD
N
The requested command (valid or NotValid) has
Failed to be sent to the requested JBOD ESD due to
the fact that there is no valid Path for
communication to the desired device at the current
time.
120/0x78
JBOD ESD IO Failed Due To
ESD Removal
N
N.A.
None
N
Subsequent to a hot removal, the ESD’s (JEM/JBOD
Enclosure Manager) destroy method was invoked.
I/O’s in the JEM’s waiting queue are flushed with
this status.
121/0x79
Mode Select command failed
due to NV memory write
failure
Y
None of these are
allowed
Midplane
Y
An attempt to write new mode parameter data to the
chassis NV memory failed.
As a result, none of the
mode parameter changes are being recorded.
If the
chassis NV memory problems persist, the mode