manualshive.com logo in svg

HP StorageWorks 7100 - Virtual Array, Appendix, Page: 8 / 27

Share
Download
HP StorageWorks 7100 - Virtual Array Appendix Download Page 8

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 

Logged? 

Predictive 

Maintenance 

Implication 

Suspected 
Components 

Mf

g 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 

Summary of Contents for StorageWorks 7100 - Virtual Array

Page 1: ... array changes to the configuration of the array performance data port error statistics Table 1 lists all event codes that can appear in the controller log event pages The table also includes events that are not logged but can still generate SCSI sense data Appropriate corrective action is included for all events that require it Many events are informational and require no action on the part of th...

Page 2: ...are error during a selftest operation 13 0xd Commands Cleared Unit Attention N N A None N Another originator sent commands to the array that resulted in commands being cleared for the current originator 14 0x0e Mode Parameters Changed Unit Attention N N A None N Another initiator sent commands to the array that resulted in shared mode parameters being changed for the current initiator 15 0x0f Unco...

Page 3: ...A None Y A disk drive failed the reconfiguration attempt TUR inquiry mode sense mode select read capacity The PDD attempted a device reconfiguration after the device was reset during the normal course of operation i e not during a hotplug of this drive but possibly during a hotplug of another drive If the device reconfiguration fails the PDD flushes all non passthru I Os from its waiting queue wit...

Page 4: ... 0x2c Invalid RG ID N N A None N A command that specifies an Redundancy Group ID specified one that is invalid for the current subsystem configuration 45 0x2d Shutdown Failed N N A None N CFM could not shutdown the subsystem because no volume set members were present all members missing 46 0x2e Not Enough Space Y Ignore See accompanying errors None Y A write command had to move data in order to fi...

Page 5: ...See accompanying errors None N R1 detected that the devices necessary for a write were not available for access before the access was attempted This can apply to an initial attempt to write or to a retry 59 0x3b Disk Interface Error Y N A None Y An error occurred on a disk interface command 60 0x3c Unsupported feature N Ignore Device Management error None Y An attempt was made to install a license...

Page 6: ...uld retry the operation 78 0x4e Silent Disk Drive Error Recovery N N A None N On a previous attempt s the drive failed the I O Usually due to hot plug The PDD retried the I O and the drive returned good status We do not log a recovered error because the original error was not logged We report GOOD status to the host 79 0x4f Check Condition From Disk Drive With No Sense Y Single Occurrence Disk Dri...

Page 7: ...troller does not have sufficient information to determine the extent of the damage 94 0x5e Volume Set Missing During Recovery Y ignore operator error None Y The volume set referenced in a recover command is not present in the subsystem If a NULL volume set was referenced then this error indicates that no members of any volume set were present This error can also result from imcompatible stamp vers...

Page 8: ...ermission 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...

Page 9: ...pected error 131 0x83 Disk Interface Command Failed Y N A None N A command to a backend device failed due to an error that does not include sense data from the device 132 0x84 Host is not authorized to access LUN Y Ignore Host doesn t have permission to access LUN None Y LUN Security Authoriztion failed Host attempted to perform an operation on a LUN without having an appropriate access permission...

Page 10: ...leted successfully This message follows the message 267 0x10b Insufficient Space To Start Rebuild Y Ignore See accompanying errors None N here is insufficient disk space for rebuild to execute This message followsthe message and may follow the REBUILD message 268 0x10c Rebuild Failed Y Ignore See accompanying errors None N ebuild has failed to complete due to multiple disk failures or a controller...

Page 11: ...ification succeeds 279 0x117 Disk Set Attached Y Ignore Operator activity None N This error code indicates the system state change consisting of attachment to a new volume set has occurred This occurs after every format subsystem and whenever a power on or reset occurs while the controller is not attached to a volume set In some cases the currently attached volume set may be empty 280 0x118 Reset ...

Page 12: ...ta may then be successfully migrated 290 0x122 Warm Boot IO Expander Fault Y Ignore if recovered by power cycle Controller Y This error code indicates that the IO Expander containing the warm boot bit did not power on in the correct default condition or that attempts to set the warm boot bit in the IO Expander failed 291 0x123 Disk Set Detached Y Ignore Operator Host activity None N This is a syst...

Page 13: ...r This error is logged only once per power on 303 0x12f No Interrupts From Other Controller Y Single Occurrance Controller Backplane N he other controller interrupt seems to be broken The timer interrupt fired multiple times with new communication messages but no other controller interrupts were present This error is logged only once per power on 304 0x130 Disk Interface Disconnect Y Ignore Disk c...

Page 14: ...an expected 319 0x13f Disk Interface Overrun Event Y Single Occurrance not with other entries Disk controller disk interface N An attached disk sent received more data than expected 320 0x140 Disk Interface Timeout Event Y 2 occurrances per hot plug insert or removal Disk controller disk interface N A command to an attached disk did not complete within the allotted time 321 0x141 Controller ECC Mi...

Page 15: ...6 0x150 Disk Interface State Event Y Single Occurrance not with other entries Controller disk disk interface N The disk interface controller and or software state information was incorrect for observed interface activity 337 0x151 Uncorrectable ECC Error During Initialization Y 1 in 6 months if no operator activity SIMM Controller N This error code indicates that the system experienced a unrecover...

Page 16: ...50 0x15e RAM Version Mismatch Y N A None N The upload routine was unable to upload part of the disk NVRAM image because the current firmware does not support that use of RAM Most likely an older version of firmware is trying to upload a disk image posted by some other firmware version 351 0x15f Disk Format Version Mismatch Y N A None N The NVRAM format of the disks does not match the format used b...

Page 17: ... This error code indicates that some non fatal error appeared in the shared memory error queue The two words of this queue entry will be placed in the log entry extended info area 363 0x16b Shared memory controller error Y Ignore if recovered by reset or power cycle Controller N This error code indicates that some fatal error appeared in the shared memory controller error queue The two words of th...

Page 18: ...376 0x178 Frontend Fibre Channel Event Y Ignore None N This error code indicates that the Front End Fibre Channel port had an event that it has logged Specific information about the event is placed in the extended info area of the log 377 0x179 Frontend Services Event Y Ignore None N This error code indicates that a Front End Services FES event has occurred and has been logged Specific information...

Page 19: ...en inserted into the enclosure 388 0x184 Internal drive removed Y Disk internal to the controller enclosure N An internal disk has been removed from the enclosure 389 0x185 Internal drive requesting port bypass Y Disk internal to the controller enclosure N An internal disk is requested that its FC port be bypassed 390 0x186 Internal drive has stopped requesting port bypass Y Disk internal to the c...

Page 20: ...ler will be failed 419 0x1a3 VSC055 Interrupt Clear Failed Y VSC055 IO Expander Chip Y An attempt to clear an interrupt on the VSC055 indicated in the event extended information has failed The controller will be failed 420 0x1a4 Power supply was inserted Y Power Supply N The power supply has been inserted into the enclosure 421 0x1a5 Power supply status is GOOD Y Power Supply N The power supply ha...

Page 21: ... charge is equal or higher than a specified threshold value 448 0x1c0 NVRAM battery status is UNKNOWN Y NVRAM battery N The status of the NVRAM battery is unknown This may be due to the firmware not being able to communicate with the battery 449 0x1c1 TWSI bus has been requested by another module Y Ignore unless occurring frequently Controller battery power supply N The battery management firmware...

Page 22: ...wn Y Midplane Y During a request for a new lun WWN the firmware was not able to read from either of the midplane eeproms This is can be due to a variety of TWSI failures or the eeprom failing The eeprom can only create 2 000 trillion 2 quadrillion LUN s If this limit has been exceeded the midplane must be replaced 470 0x1d6 Firmware clone complete Y N A N Cloning of firmware to the other controlle...

Page 23: ...tected an internal error 489 0x1e9 abterm reset Y controller N This event code indicates that the controller reset due to an abnormal termination in the firmware 490 0x1ea front panel reset Y controller N This event code indicates that the controller reset due to a request through the front panel 491 0x1eb host reset Y controller N This event code indicates that the controller reset due to a reque...

Page 24: ...ta on the two eeproms at a given location was different This problem is usually fixed if the firmware can write to the eeproms 510 0x1fe FC Signal Detect Interrupt Y VSC7130 PBC Dual Repeater Chip N An interrupt on one of the VSC7130 port bypass control signal detect chips has occurred See the extended information for details 511 0x1ff Dual controller clock sync error Y controller N An interrupt f...

Page 25: ...Y Ignore unless no Operator activity Disk Drive Back End FC Link N An AutoFormat event was logged this is caused either by a backend format of an internal drive beginning or completing Look as the associated data for drive and status 532 0x214 Power supply is not connected to an AC source Y Power Supply Y This warning indicates that the power supply is not connected to an AC source 533 0x215 Some ...

Page 26: ...out Y Ignore Lab only none N The cross controller lock module failed to grant the decoder s lock in exclusive mode within the allowed period after an obtain request was deferred This may indicate a deadlock in the system or that the system is too busy 552 0x228 Decoder lock request was deferred Y Ignore Lab only none N The cross controller lock module deferred a request to obtain the decoder s loc...

Page 27: ... mode parameters region contains a revision that is older than the revision expected by current firmware As a result some mode parameters were set to their default values since there was no saved value present in the EEPROM 577 0x241 Start multi disk loss scan Y Ignore should be other prior failure events controller N A backend scan was started to detect a multiple disk loss condition because of a...

Reviews:

No comments