HP StorageWorks 7100 - Virtual Array Appendix page 8

FC-SCSI Interface SpecificationDescribes the IceCube SCSI interface. Targetted as part of OEM manual.Disk Array Con
Event Event
Number Name
(dec/hex)
103/0x67 JM Write Recovered With
Retries
104/0x68
Force Unit Access Failed with
no Sense Data
105/0x69 Host DATA-OUT FCP-DL and
CDB transfer lengths not equal
106/0x6a
Host Block command
attempted with FCP-DL NOT a
block size
107/0x6b LUN Security prevents the
requested operation
108/0x6c
An unsupported operation was
attempted on a snapshot LUN
109/0x6d flush of storage object failed
110/0x6e Parameter Value Invalid
111/0x6f
Host is not authorized to read
from a LUN
112/0x70
Host can not be authenticated
to access LUN Security map
113/0x71 Limit to Maximum number of
Principals is reached
114/0x72 Host is not authorized to write
to a LUN
115/0x73 Feature is not licensed
116/0x74 Hot plug or LIP occured during
processing of passthrough
117/0x75
Unexpected JBOD Error
118/0x76
Recovered By Enclosure
Service Device (ESD)
119/0x77 PassThru request Failed
120/0x78 JBOD ESD IO Failed Due To
ESD Removal
121/0x79
Mode Select command failed
due to NV memory write
failure
Predictive Suspected
Maintenance Components
Implication
Y Ignore - See None
Accompanying
Errors
Y Ignore - See Cache
accompanying
errors
Y Ignore - Host None
Protocol
Incompatibility
Y Ignore - Host None
Protocol
Incompatibility
N Ignore - Host None
LUN addressing
problem
Y Ignore - Incorrect None
host behavior
Y disallow None
snapshot
N None
Y Ignore - Host None
doesn't have
permission to
access LUN
Y Ignore - Provide None
correct password
Y Ignore - Remove None
unwanted
associations from
Security map
Y Ignore - Host None
doesn't have
permission to
access LUN
N Ignore - Host None
Porblem
Y Ignore - should None
be handled by
host
Y Unknown JBOD ESD
Y See information JBOD ESD
provided by
JBOD vendor
Y Ignore - Should JBOD ESD
be handled by
host
N N.A. None
Y None of these are Midplane
allowed
Error! No text of specified style in document.
Description
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