manualshive.com logo in svg

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

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

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 

345/0x159 

Bus A TWSI communication 
failure 

Y  Controller, 

battery, power 
supply, 
midplane 

Y 

Either local controller or remote controller SRAM 
on two-wire serial bus A could not be accessed for 
controller sync. Bus B SRAM will be used instead 
(if Bus B SRAMs are also inaccessible, both 
controllers will reset and and try again; finally one 
controller will be disabled and the system will 
continue in single controller mode) 

346/0x15a 

Data Loss Detector entry 

Y 

Indicates 

multiple failure 

causing data loss 

Disk drive(s) 

N 

This error code indicates that the data loss detector 
module was called because of multiple failures.  A 
data loss has occurred. 

347/0x15b 

Member Disk Drive Added 
Back Into Disk Set 

Y 

Ignore - Operator 

or host activity 

None 

N 

This error code is a system change event indicating 
that a member of a volume set that was either down, 
failed, or missing has been returned to the 
unrestricted use (aka ready) state.  This can occur 
via the add physical drive command, or via hot plug 
insertion of the drive. 

348/0x15c 

Frontend Fibre Channel ABTS 
Event 

Y 

Ignore 

None 

N 

This error code indicates that the Host sent a Fibre 
Channel ABTS (Abort Sequence) BLS frame to the 
abort an IO.  The array will log this event for 
informational and debug purposes only.  It does not 
necessarily indicate a problem with the array. 

349/0x15d 

Cache Version Mismatch In 
RAM Image 

Y See 

errors 

associated with 

shut down 

None 

N 

A firmware download has a new version of the 
cacheVersionNumber. This is OK if there are no 
writes stuck in cache but it causes upload to fail 
with this error code if there are writes stuck in 
cache.  To fix this it is necessary to revert to the old 
version of firmware and solve whatever problem 
was causing writes to be stuck in cache (probably 
one or more disks have failed). 

350/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 by the controller.  This event is logged 
when an icicle controller attempts to use disks 
previously shutdown by an Ice controller or visa-
versa.  The controller cannot use an NVRAM image 
in the incorrect format. 

352/0x160 

ShutDown Due To Power 
Supply Failure 

Y Single 

Occurrance 

Power Supplies, 
Controller, 
Backplane 

N 

This error code indicates that the Background 
Manager (BGM) has discovered that there are not 
enough good power supplies to run the system.  The 
BGM is shutting down the subsystem to minimize 
system operation with inadequate power.The 
NVRAM is posted to disk. 

353/0x161 

Recovery from battery backed 
RAM Loss Started 

Y Single 

Occurrance 

Controller 

N 

This error code indicates that recovery from a 
battery backed RAM loss has been initiated. 

354/0x162 

Recovery from Battery Backed 
RAM Loss complete 

Y 

Ignore 

None 

N 

This error code indicates that recovery from a 
battery backed RAM loss completed with at least 
partial success.  Maps were recovered.  Multiple 
failures may or may not have occurred.  Occurrance 
of multiple failures are reported in the log between 
the RECOV_STARTED and RECOV_DONE 
events. 

355/0x163 

Redundancy corrected 

Y 

Suspect data if 

followed by error 

code 93 (0x5d) 

Disk Drive, 
Back End FC 
Link, Controller 

N 

This error code indicates that the parity scan which 
executes during recovery from RAM loss found an 
instance of incorrect redundant data.  Data which 
was being updated when RAM was lost may 
produce this error in single failure scenarios.  This 
error can also result from multiple failure 
conditions.  Firmware differentiates the two 
scenarios by placing a limit on the number of these 
conditions which can occur before recovery is 
terminated due to multiple component failures.  If 
this error is followed by error 93 (0x5d) then the 
contents of data blocks reported in this error should 
be considered suspect.  The block address of the 

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