to, the implied warranties of merchantability and fitness for a particular purpose. Hewlett-Packard shall not be
liable for errors contained herein or for incidental or consequential damages in connection with the furnishing,
performance, or use of this material.
This document contains proprietary information, which is protected by copyright. No part of this document may
be photocopied, reproduced, or translated into another language without the prior written consent of
Hewlett-Packard. The information contained in this document is subject to change without notice.
Compaq Computer Corporation is a wholly-owned subsidiary of Hewlett-Packard Company.
All product names mentioned herein may be trademarks of their respective companies.
Hewlett-Packard Company shall not be liable for technical or editorial errors or omissions contained herein. The
information is provided “as is” without warranty of any kind and is subject to change without notice. The
warranties for Hewlett-Packard Company products are set forth in the express limited warranty statements
accompanying such products. Nothing herein should be construed as constituting an additional warranty.
Printed in the U.S.A.
Storage Management Appliance Software
Event Code Definitions Application Notes
First Edition (December 2002)
Part Number: AA-RTDKA-TE
These Application Notes provide listings of the various event codes displayed by the HP
OpenView Storage Management Appliance. The event codes are defined and discussed in the
following sections:
■Introduction, page 4
■Storage Management Appliance Event Codes, page 5
■Storage Management Appliance Audit Codes, page 6
■NetApp Filers Event Codes, page 9
■HP StorageWorks and McData Switch Event Codes, page 11
■HP StorageWorks SAN and Brocade Switch Event Codes, page 13
■HSG Element Manager Event Codes, page 15
■HSV Element Manager Event Codes, page 21
Intended Audience
This document is intended for customers who purchase the Storage Management Appliance
software V2.0. It has been developed for use by storage and system administrators who are
experienced with:
Application Notes Contents
■Managing storage area networks (SANs).
■Running a Storage Management Appliance.
Related Storage Management Appliance Software V2.0 Documentation
The following list includes documentation related to the Storage Management Appliance
software V2.0:
The Storage Management Appliance can generate notification messages to any number of
users in response to events. A notification message, including the source of the event, date,
time, event code, and event description, can be sent to a standard e-mail address or to an e-mail
pager address. This document provides a complete list of the events logged by the Storage
Management Appliance.
The lists of events are presented in tables with one table for each application or vendor.
Each table contains the following columns:
■Event ID—Numeric code used to identify the event specific to the event’s source.
■Event Code—Hexadecimal code used to identify an event type in notification messages
and in the Storage Management Appliance Event Log or Audit Log.
■Severity—Single digit code indicating the event severity or potential impact on Storage
Management Appliance operations (see Table 1 for more information).
■Description—Text describing the event. Event details are provided by the source of the
event. In this document, event details are expressed as %1, %2, etc.
Table 1 describes the severity codes used for event codes.
Table 1: Severity Codes
Event Severity
Code
0UnknownSeverity cannot be determined.
1OtherCan be one of several possible severity conditions.
2InformationEvent is generally part of normal operation.
3WarningFurther action is optional
4MinorFurther action is required but the situation is not
5MajorAction should be taken immediately.
6CriticalAction required to avoid a significant impact on
7FatalAn error occurred and no action can be taken to avoid
The Storage Management Appliance’s core services—discovery, event notification, and
automation—generate the events listed below. The system records these events in the Storage
Management Appliance Event Log.
Table 2: Storage Management Appliance Event Codes
Storage Management Appliance Event Codes
Event
ID
202880A00CA2Discovery %1 started.
203880A00CB2Discovery %1 completed.
204880A00CC2New device found: %1.
205880A00CD2Device %1 unreachable for %2 day(s).
206880A00CE2Device %1 unreachable for %2 week(s).
408880A01983Notification for user %1 has been disabled. This user was the sole
700880A02BC2Received a SNMP Trap from %1. The enterprise OID is %2,
701880A02BD3The Management Appliance event log is 80% full.
702880A02BE6The Management Appliance event log is full.
703880A02BF3The Management Appliance audit log is 80% full.
704880A02C06The Management Appliance audit log is full.
800880A03207Automation Manager experienced the following abnormal
801880A03217Automation Manager experienced the following database failure:
802880A03222Event process %1 ran in policy %2 on Management Appliance %3
803880A03232Event process %1 ran in policy %2 triggered on an event %3
804880A03243Event process %1 ran in policy %2 on Management Appliance %3
805880A03252Action process %1 ran in policy %2 on Management Appliance %3
806880A03263Action process %1 ran in policy %2 on Management Appliance %3
807880A03272%1 policy has been submitted successfully.
808880A03282Event process %1 in policy %2 was satisfied when the %3 value of
1014880A03F62%1 service started.
1015880A03F72%1 service stopped.
1016880A03F82%1 service: Handler not installed.
1017880A03F92%1 service: Bad service request.
Event
Code
SeverityDescription
recipient of event notifications from %2.
GenericTrap is %3, SpecificTrap is %4.
operation: %1
%1
completed with state %4. Process started on %5 and ended on %6
with %7 return code. Policy finished with status: %8
logged by %4.
completed with state %4. Process started on %5 and ended on %6
with %7 return code. Policy finished with status: %8
completed with state %4. Process started on %5 and ended on %6
with %7 return code. Policy finished with status: %8
completed with state %4. Process started on %5 and ended on %6
with %7 return code. Policy finished with status: %8
The Storage Management Appliance generates audits in response to most user-initiated
operations. Activities such as creating or running a discovery generate audits that are recorded
in the Storage Management Appliance Audit Log.
Table 3: Storage Management Appliance Audit Codes
Event IDEvent CodeSeverityDescription
1008C0A00642Installation of %1 on appliance %2.
1018C0A00652Removal of %1 from appliance %2.
1508C0A00962Deletion of %1 device.
1518C0A00972Launch of %1 URL.
1528C0A00982Modification of %1 device.
2078C0A00CF2Creation of discovery named %1.
2088C0A00D02Deletion of discovery named %1.
2098C0A00D12Modification of discovery named %1.
2108C0A00D22Enabling of schedule for discovery named %1.
2118C0A00D32Disabling of schedule for discovery named %1.
2128C0A00D42Discovery named %1 requested to start.
2138C0A00D52Discovery named %1 requested to stop.
3008C0A012C2Creation of remote access entry for Host: %1, Application:
%2, Domain Name: %3, Username: %4.
3018C0A012D2Modification of remote access entry for Host: %1,
Application: %2, Domain Name: %3, Username: %4.
3028C0A012E2Deletion of remote access entry for Host: %1, Application:
%2, Domain Name: %3, Username: %4.
3038C0A012F2Modification of %1 license.
3048C0A01302Creation of %1 license.
3058C0A01312Deletion of %1 license.
3068C0A01322Modification of %1 license.
3078C0A01332Download of %1 license.
3088C0A01342Clearing of %1 license.
3098C0A01352Download of event log.
3108C0A01362Clearing of event log.
3118C0A01372Modification of event log properties.
3128C0A01382Acknowledgement of events in the event log.
4008C0A01902Deletion of user %1.
4018C0A01912Importing of user %1.
4028C0A01922Creation of user %1.
4038C0A01932Changing password for user %1.
4048C0A01942Modification of user %1 properties.
4058C0A01952Modification of user %1 notification properties for the
following devices: %2.
4068C0A01962Transfer of user %1 notification settings to user %2.
4078C0A01972Deletion of notification settings from user %1 and transferred
to user %2.
5008C0A01F42Starting backup to network share %1.
5018C0A01F52Completion of backup operation that was started to network
share %1. See %2 file on Management Appliance %3 for
details.
5028C0A01F62Cancellation of backup operation that was started to network
share %1. See %2 file on Management Appliance %3 for
details.
6008C0A02582Starting restore operation from network share %1.
6018C0A02592Completion of restore operation that was started to network
share %1. See %2 file on Management Appliance %3 for
details.
6028C0A025A2Cancellation of restore operation that was started from
network share %1. See %2 file on Management Appliance
%3 for details.
6038C0A025B2Clearing of backup log %1.
6048C0A025C2Clearing of restore log %1.
9008C0A03842Starting %1.
9018C0A03852Stopping %1.
9048C0A03882Changing date/time to %1.
9058C0A03892Changing time zone to %1.
9068C0A038A2Modification of SNTP time server - Enabled: %1, Server:%2,
Frequency:%3.
9508C0A03B62Launching of HSV element manager.
9518C0A03B72Launching of HSG Element Manager.
9528C0A03B82Launching of VersaStor.
9538C0A03B92Launching of Automation.
9548C0A03BA2Launching of Management Agents.
9608C0A03C02Launching of Network View.
9618C0A03C12Launching of Secure Path Manager.
9628C0A03C22Launching of Data Replication Manager.
9638C0A03C32Launching of Enterprise Volume Manager.
9648C0A03C42Launching of Storage Allocation Reporter.
9658C0A03C52Launching of Storage Provisioner.
9708C0A03CA2Modification of IP address configuration.
9718C0A03CB2Modification of DNS server configuration.
9728C0A03CC2Modification of WINS server configuration.
9808C0A03D42Modification of Administration Web Site properties.
9818C0A03D52Modification of Global Network settings.
9828C0A03D62Modification of Telnet Administration configuration.
10008C0A03E82Changing Management Appliance name to %1.
10018C0A03E92Changing Management Appliance membership to
10028C0A03EA2Changing Management Appliance membership to domain
10038C0A03EB2Shutdown of Management Appliance.
10048C0A03EC2Changing domain/workgroup membership.
10058C0A03ED2Restarting Management Appliance.
10068C0A03EE2Scheduling Management Appliance for %1.
10108C0A03F22Configuration of Management Appliance as the first domain
10118C0A03F32Configuration of Management Appliance as the first domain
10128C0A03F42Configuration of Management Appliance as the first domain
10138C0A03F52Configuration of Management Appliance as an additional
10208C0A03FC2Modification of notification properties for event code %1 on
10218C0A03FD2Configuration of notification for the following devices: %1.
10228C0A03FE2Clearing of notification settings for the following devices: %1.
10308C0A04062Download of audit log.
10318C0A04072Clearing of audit log.
10328C0A04082Modification of audit log properties.
10338C0A04092Acknowledgement of audits in the audit log.
10408C0A04102Adding of trap recipient %1.
10418C0A04112Removal of trap recipient %1.
10428C0A04122Modification of trap recipient %1.
10508C0A041A2Setting SMTP server to %1 with IP address: %2.
10558C0A041F2Logging in of user.
10568C0A04202Logging out of user.
%1.
controller in the new forest, %1. The new domain name is
%2.
controller in a new domain tree. The name of the new
domain is %1 and has trust link with %2.
controller in a new domain. The name of the new domain is
The following events are generated by NetApp Filer devices and are recorded in the Storage
Management Appliance Event Log. A number of these events are associated with user-defined
traps and most indicate a condition that is likely to have a negative impact on operations. A
small number of events mark a return to normal operation after some period of abnormal
operation.
The Storage Management Appliance supports the NetApp MIB version 1.2.
Table 4: NetApp Filer Event Codes
Event
Event ID
100880E00642An unknown trap event was received.
101880E00653A polling-style trap built by the user using the SNMP traps
102880E00665Disk Health Monitor reported a Disk Degraded-I/O Event.
103880E00674Disk Health Monitor reported a Disk Predictive-Failure Event.
104880E00687A user-defined trap indicating an extremely urgent situation,
105880E00695A user-defined trap indicating a condition that should be
106880E006A6A user-defined trap indicating a critical condition, such as a
107880E006B5A user-defined trap indicating an error condition, such as a
108880E006C4A user-defined trap indicating a condition which is not an error,
109880E006D2A user-defined trap meant to provide information, such as an
110880E006E1A user-defined trap used for debugging purposes.
111880E006F7System is shutting down because the system has been running
112880E00705One or more disks failed.
113880E00712The failed disks have been repaired.
114880E00727Critical chassis or cpu fans have failed and the system is
115880E00735One or more chassis fans failed.
116880E00743One or more chassis or cpu fans are in warning state.
117880E00752All fans are repaired.
118880E00767Critical power supplies or power rails failed and the system is
119880E00775One or more redundant power supplies failed.
120880E00783One or more power supplies or power rails in warning state.
121880E00792Previously-failed power supplies or power rails have been
122880E007A4CPU utilization exceeds 90 percent.
123880E007B2CPU utilization has dropped back below 90 percent.
Code
NetApp Filers Event Codes
SeverityDescription
command on the filer.
usually indicating that the system has failed and is shutting
down.
124880E007C5The NVRAM battery is fully discharged.
125880E007D4The charge in the NVRAM battery is low.
126880E007E5A node in a Cluster FailOver configuration failed. Its partner
127880E007F5The partner has taken over for a failed cluster node.
128880E00802A cluster node has resumed operation.
129880E00815At least one volume is more than 98 percent full.
130880E00824At least one volume is more than 95 percent full.
131880E00832All volumes are now under 95 percent full.
132880E00847System temperature is too high to continue operating. The
133880E00854System temperature is too high and in the warning level.
134880E00862System temperature has returned to an acceptable value.
135880E00875A disk storage shelf reported a fault, probably due to a
136880E00882A previously-reported shelf fault is now corrected.
137880E00897The appliance’s overall status changed to ‘nonRecoverable’,
138880E008A6The appliance’s overall status changed to ‘critical’, indicating a
139880E008B4The appliance’s overall status changed to ‘nonCritical’,
140880E008C2The appliance’s overall status returned to normal.
141880E008D2Cold Start.
142880E008E2Warm Start.
143880E008F2Link Down: %1
144880E00902Link Up: %1
145880E00912Authorization failure.
146880e00922EGP Peer down: %1
Code
SeverityDescription
will assume service for the failed node.
system is shutting down.
problem with drive placement, fans, power, or temperature.
indicating a problem so severe that the appliance is shutting
down.
The following events are generated by HP StorageWorks switches and McData switches and
are recorded in the Storage Management Appliance Event Log. Many of these event types
have several possible states and each state has an appropriate severity code.
The Storage Management Appliance supports the following StorageWorks and McData MIB
versions:
■V1.9 for the ED-5000 series
■V1.10 for the EF-6000 series
■V1.0 for the ES-1000 series
Table 5: HP StorageWorks and McData Event Codes
Event
ID
100880C0064N/A2An unknown trap event was received.
101880C0065online
102880C0066online
103880C0067active
104880C0068online
105880C0069active
106880C006Aonline
107880C006Bactive
Event
Code
Possible StatesSeverityDescription
offline
testing
faulty
unknown
offline
testing
faulty
unknown
updatebusy
failed
unknown
offline
testing
faulty
unknown
backup
updatebusy
failed
unknown
offline
testing
faulty
unknown
backup
updatebusy
failed
unknown
2
5
2
7
0
2
5
2
7
0
2
2
7
0
2
5
2
7
0
2
3
2
7
0
2
5
2
7
0
2
3
2
7
0
B_Port Index %2 changed state to %1.%n
A es1000PortBportScn is generated whenever
a B_Port changes its operational state.
H_Port Index %2 changed state to %1.%n
A es1000PortHportScn is generated whenever
a H_Port changes its operational state
Component Code %2 has changed state to
%1.%n
A es1000CompScn is generated whenever a
COMPONENT status changes its operational
state.
Port Index %2 changed state to %1.%n
An ed5000PortScn(1) is generated whenever
a Fc_Port changes its operational state.
FRU Code %2 has changed state to %1.%n
An ed5000FruScn(2) is generated whenever a
FRU status changes its operational state.
Port Index %2 changed state to %1.%n
An ef6000PortScn(1) is generated whenever a
Fc_Port changes its operational state.
FRU Code %2 has changed state to %1.%n
An ef6000FruScn(2) is generated whenever a
FRU status changes its operational state.
%2 has either successfully connected or is
currently being rejected due to a Port Binding
violation.%n
An ef6000PortBindingViolation(3) is
generated whenever the switch detects that a
port binding violation occurs.
ef6000PortIndex: %1%n
ef6000TAIndex: %2%n
An ef6000ThresholdAlert(4) is generated
whenever a threshold alert occurs.
HP StorageWorks SAN and Brocade Switch Event Codes
HP StorageWorks SAN and Brocade Switch Event Codes
The following events are generated by HP StorageWorks SAN switches and Brocade switches
and are recorded in the Storage Management Appliance Event Log. Many of these event types
have several possible states and each state has an appropriate severity code.
The Storage Management Appliance supports the StorageWorks SAN and Brocade MIB
version 4.0.
Table 6: StorageWorks SAN and Brocade Switch Event Codes
Event
ID
10588020069unknown
10188020065ok
10388020067unknown
1078802006Bcritical
Event
Code
Possible StatesSeverityDescription
online
offline
testing
faulty
faulty
unknown
faulty
below minimum
normal
above maximum
absent
error
warning
informational
debug
0
2
5
2
7
2
5
0
0
5
7
2
5
2
5
5
3
2
2
Port Index %2 changed state to %1%n
SSN: %3%n
GroupName: %3%n
GroupType: %5%n
Group MemPosition: %6%n
A swFCPortScn(3) is generated whenever
an FC_Port changes its operational state.
For instance, the FC_Port goes from on-line
to offline. The VarBind in the Trap Data Unit
shall contain the corresponding instance of
the FC_Port's operational status and index.
Switch is faulty.
Faulty reason: %1%n
SSN: %2%n
GroupName: %3%n
GroupType: %4%n
Group MemPosition: %5%n
A swFault(1) is generated whenever the
diagnostics detects a fault with the switch.
%5 is currently in state %1%n
SSN: %7%n
GroupName: %3%n
GroupType: %8%n
Group MemPosition: %9%n
A swSensorScn(2) is generated whenever
an environment sensor changes its
operational state. For instance, a fan stops
working. The VarBind in the Trap Data Unit
shall contain the corresponding instance of
the sensor status, sensor index, sensor type,
sensor value (reading) and sensor
information. Note that the sensor
information contains the type of sensor and
its number in textual format.
Event %1: %2 (severity level %3) - %5%n
SSN: %6%n
GroupName: %7%n
GroupType: %8%n
GroupMemPosition: %9%n
This trap is generated when an event whose
level at or below swEventTrapLevel occurs.
Fabric Watch has generated an event.%n
Threshold %3 in Class/Area %1 at index
%2 has generated event %7 with %5 on
%6.%n
This event is %8%n
SSN: %9%n
GroupName: %10%n
GroupType: %11%n
GroupMemPosition: %12%n
Trap sent by Fabric Watch to notify of an
event.
%1%n.
SSN: %2
GroupName: %3
GroupType: %4
GroupMemPosition: %5%n
Trap sent for tracking login/logout/config
changes.
The HSG Element Manager is an application provided with the Storage Management
Appliance and used to configure and monitor HSG80/60 storage elements. The HSG Element
Manager generates events that help a user understand the status of both the manager
application and the storage elements. The system records these events in the Storage
Management Appliance Event Log.
Table 7: HSG Element Manager Event Codes
Event IDEvent CodeSeverityDescription
6001880117712HSGSubsystem object created.
6002880117722Sense Data found.
6003880117732%1 state changed to online
6004880117745%1 state changed to offline
6005880117752%1 container state changed to good
6006880117765%1 container state changed to failed
6007880117772%1 container state changed to Reconstructing
6008880117782%1 container state changed to Initializing
6009880117793%1 container state changed to Reduced
60108801177A2%1 state changed to good. %2
60118801177B5%1 state changed to failed. %2
60128801177C7No controllers found
60138801177D3New controller %1 found
60148801177E4Other controller %1 unreachable
60158801177F3Other controller %1 reachable
6016880117802Controller %1 Cache Battery state changed to good
6017880117813Controller %1 Cache Battery state changed to low
6018880117825Controller %1 Cache Battery state changed to bad
6019880117832Controller %1 Cache state changed to good
6020880117845Controller %1 Cache state changed to bad
6021880117855Controller %1 Cache state changed to invalid
6022880117864Failed to refresh HSGSubsystem
6023880117874Failed to refresh Virtual Disks
6024880117884Failed to refresh Storage Sets
6025880117894Failed to refresh Devices
60268801178A4Failed to refresh Host Connections
60278801178B4Failed to rescan HSGSubsystem
60288801178C7Striped Mirror set modification. Members do not match
60298801178D7Too few mirrorset members for striped mirror set
60308801178E7Mirrorset already a member
60318801178F7STL Exception generated. %1
6032880117907Unknown system Exception generated. %1
6033880117917HSG Exception generated. %1
6034880117927Invalid Controller Pointer
6035880117937Invalid Container Pointer. %1
Table 7: HSG Element Manager Event Codes (Continued)
Event IDEvent CodeSeverityDescription
6036880117943Device not found. %1
6037880117953%1 not found
6038880117963Storage Set not found
6039880117973Host Connection not found
6040880117984Test Unit Ready failed
6041880117992Virtual Disk %1 deleted
60428801179A2Virtual Disk %1 created
60438801179B2Device %1 added
60448801179C2Device %1 deleted
60458801179D3Host Connection %1 went offline
60468801179E2Host Connection %1 went online
60478801179F3Invalid parameter was found in request. %1
6048880117A07Invalid Storage Set type found. %1
6049880117A14Attempt to create virtual disk failed. %1
6050880117A24Attempt to modify virtual disk failed. %1
6051880117A34Attempt to delete virtual disk failed. %1
6052880117A44Attempt to modify device failed. %1
6053880117A54Attempt to modify Controller failed. %1
6054880117A64Attempt to modify Host Connection failed. %1
6055880117A74Attempt to delete Host Connection failed. %1
6056880117A84Attempt to rename Host Connection failed. %1
6057880117A94Snapshot: %1 not created.
6058880117AA2Snapshot: %1 created.
6059880117AB2Virtual Disk modified. %1
6060880117AC2%1 modified
6061880117AD2Controller modified. %1
6062880117AE2Host Connection %1 modified
6063880117AF2Host connection %1 has been renamed to %2
6064880117B02Host Connection %1 deleted
6065880117B14Attempt to rescan storage failed. %1
6066880117B24Attempt to Delete Storage Set failed. %1
6067880117B34Attempt to Delete Device failed. %1
6068880117B42Virtual disk: %1, %2 member removed.
6069880117B54Attempt to remove a member from a Virtual Disk failed. %1
6070880117B67Invalid Device Pointer. %1
6071880117B74Attempt to remove Failed Set member failed. %1
6072880117B84Attempt to add member to Spare Set failed. %1
6073880117B94Attempt to remove member from Spare Set failed. %1
6074880117BA6EMU state now invalid. %1
6075880117BB2EMU state now valid. %1
6076880117BC6Power supply has gone bad. %1
Table 7: HSG Element Manager Event Codes (Continued)
Event IDEvent CodeSeverityDescription
6077880117BD2Power supply is now good. %1
6078880117BE6Fan has gone bad. %1
6079880117BF2Fan is now good. %1
6080880117C06High Temperature detected. %1
6081880117C12Temperature is within optimal range. %1
6082880117C26Airflow is bad. %1
6083880117C32Airflow is now good. %1
6084880117C42EMU is present
6085880117C56EMU is no longer present
6086880117C67Cabinet %1 went offline
6087880117C72Cabinet %1 went online
6088880117C86Master cabinet has no controller installed. %1
6089880117C92Master cabinet has controller installed. %1
6090880117CA2Controller present but present in slave cabinet. %1
6091880117CB2Master cabinet has controller installed. %1
6092880117CC6UPS has gone bad. %1
6093880117CD2UPS is now good. %1
6094880117CE6Shelf is bad. %1
6095880117CF2Shelf is good. %1
6096880117D06Voltage has gone bad. %1
6097880117D12Voltage is now good. %1
6098880117D23Other controller failed
6099880117D32Other controller now good
6100880117D46Communication with subsystem has gone down. %1
6101880117D52Regained communication to subsystem
6102880117D64Attempt to create Remote Copy Set failed. %1
6103880117D72Remote copy set: %1 created.
6104880117D84Attempt to Delete Remote Copy Set failed. %1
6105880117D92RCS: %1 deleted.
6106880117DA4Attempt to modify Remote Copy Set failed. %1
6107880117DB2%1 RCS has been modified.
6108880117DC3No Modifications were made. %1
6109880117DD3Attempt to set failsafe on Remote Copy Set failed. %1
6110880117DE4Attempt to Delete Association failed. %1
6111880117DF4Attempt to create Association failed. %1
6112880117E02Association: %1 created.
6113880117E12Association: %1 not deleted.
6114880117E24Attempt to modify Association failed. %1
6115880117E32%1 Association has been modified.
6116880117E42Name is in use
6117880117E54%1 unable to add to spare set
Table 7: HSG Element Manager Event Codes (Continued)
Event IDEvent CodeSeverityDescription
6118880117E62Item is already used
6119880117E72Device %1 added to Spare Set
6120880117E82Device %1 removed from Spare Set
6121880117E92Device removed from Failed Set
6122880117EA4Attempt to expand Virtual Disk failed. %1
6123880117EB2Virtual Disk expanded
6124880117EC2%1 Virtual Disk not expandable
6125880117ED4Incomplete Concatset modify: %1
6126880117EE2Storage Set modified
6127880117EF4Attempt to modify Chunksize failed
6128880117F07HSGSubsystem Assertion
6129880117F14Codeload failed. %1
6130880117F23Codeload Error. %1
6131880117F32Top Controller is rebooting
6132880117F42Bottom Controller is rebooting
6133880117F52Both Controllers are rebooting
6134880117F64Could not locate top controller
6135880117F74Could not locate bottom controller
6136880117F82Operating state is normal. %1
6137880117F96Operating state is failed. %1
6138880117FA4Operating state is impaired. %1
6139880117FB2Top controller is done rebooting
6140880117FC2Bottom controller is done rebooting
6141880117FD2Both controllers are done rebooting
6142880117FE4Reboot of controller failed. %1
6143880117FF2SCSI command did not complete. %1
6144880118002EMU modified
6145880118014EMU modify failed
6146880118022Unit is an Association Log Device
6147880118032Unit is an RCS Initiator
6148880118042Unit has been expanded
6149880118052Unit has no preferred path
6150880118062Unit is transportable
6151880118072Unit is a Snapshot
6152880118082Unit writeback cache is disabled
6153880118092Unit storage container is partitioned
61548801180A2Incompatible storage container type
61558801180B2No peer to peer configuration
61568801180C2Unit is in Failed state
61578801180D2Unit has too few devices
61588801180E2Unit not in correct state
Table 7: HSG Element Manager Event Codes (Continued)
Event IDEvent CodeSeverityDescription
61598801180F2Unit is used by another configuration
6160880118102Unit is a Snapshot source
6161880118112Subsystem firmware does not support snapshots
6162880118122Subsystem does not have peer to peer support enabled
6163880118132HSGSubsystem Miscellaneous info
6164880118142Mirror cache is not enabled
6165880118152Controller cache size is too small
6166880118163HSGSubsystem Unknown Status
6167880118173Subsystem has the maximum number of snapshots
6168880118184Not enough available physical disks or unused stripes
6169880118193Reached maximum physical disk count
61708801181A4Virtual Disk is a target
61718801181B2Initialize container failed. %1
61728801181C2Initialized container successfully. %1
61738801181D4No available containers
61748801181E2Reservation mutex check failed
61758801181F7Container not found. %1
6176880118202%1 Used by name list
6177880118212Unable to disable the PPRCMode
6178880118224Add VD member failed. %1
6179880118232Virtual Disk: %1, added member %2 successfully
6180880118242Check VirtualDisk not in REDUCE state or Replacement
6181880118252Rejected because of reservation. %1
6182880118264Need ACS firmware revision 8.7 for management
6183880118272Virtual disk %1 has been reserved by %2
6184880118282A virtual disk has been unreserved. %1
6185880118292Virtual disk reservation failure. %1
61868801182A2Management lock down change. %1
61878801182B2No available disks
61888801182C2Maximum number of members
61898801182D2Replacement policy must be NOPOLICY
61908801182E2Raidset must be in reduced state
61918801182F2Code patch %1-%2 is Succesfully loaded on %3 controller
700188011B596HSGSubsystem API has lost comm to Subsystem. %1
700288011B5A4HSGSubsystem API has returned controller error text. %1
700388011B5B4HSGSubsystem API has received Invalid show this output
700488011B5C4HSGAPI::getAllControllers: Invalid SHOW OTHER output
700588011B5D4Invalid SHOW UNIT output %1
700688011B5E4HSGSubsystem API has received Invalid show storage
Table 7: HSG Element Manager Event Codes (Continued)
Event IDEvent CodeSeverityDescription
700788011B5F4Invalid SHOW DEV FULL output
700888011B604HSGSubsystem API has received Invalid show connection
700988011B613HSGSubsystem API received modification request but no
701088011B623HSGSubsystem API received delete request but no changes
701188011B633HSGSubsystem API invalid CLI syntax or incomplete CLI
701288011B642HSGSubsystem API has returned controller warning text
701388011B652HSGSubsystem API This controller rebooting
701488011B662HSGSubsystem API Other controller rebooting
701588011B672HSGSubsystem API Both controllers rebooting
701688011B684HSGAPI::getAllAssociations: Invalid SHOW AllAssociations
701788011B694HSGSubsystem API has received Invalid show Remote Copy.
701888011B6A4HSGSubsystem API Setting Host connection failure
701988011B6B4HSGAPI::getAutospare, Invalid SHOW FAILEDSET output
702088011B6C3Comm path switched. %1
702188011B6D3Unable to switch comm path. %1
702288011B6E3Last Status
82048801200C7A spurious interrupt was detected during the execution of a
82058801200D7An unrecoverable error was detected during execution of
82068801200E7An unrecoverable error was detected during execution of
82078801200F7An unrecoverable error was detected during execution of
83018801206D7An unrecoverable error was detected during execution of
83028801206E7An unrecoverable error was detected during execution of
83038801206F7Deletion of component failed.
8304880120702A component location has been updated.
8305880120712A component name has been updated.
8306880120726HSG not communicating.
8307880120732HSG is communicating.
8308880120743Log approaching max size, prior entries removed.
8309880120752New HSG found.
output. %1
changes were found. %1
were found. %1
command error (Last Status). %1
output %1
%1
Subsystem Built-In Self Test
the HOST PORT Subsystem Test. The system will not be able
to communicate with the host.
the UART/DUART Subsystem Test. This will cause the
console to be unusable. This will cause failover
communications to fail.
the FX Subsystem Test.
the PCI9060ES Test.
the Device Port Subsystem Built-In Self Test. One or more of
the device ports on the controller module has failed;
some/all of the attached storage is no longer accessible via
this controller.
The HSV Element Manager is an application provided with the Storage Management
Appliance that is used to configure and monitor HSV110 Array Controllers. The HSV
Element Manager generates controller events and management agent events that help users
understand the status of both the manager application and the storage elements.
The Storage Management Appliance supports the HSV MIB version 2.0.
Controller Events
Table 8 shows events generated by the HSV Controller, which are logged in the Storage
Management Appliance Event Log. The Software Component ID (SWC ID) and Event
Number (Evt. No.) codes can be used to correlate events recorded in the Controller Event Log
of the HSV Element Manager with the events logged in the Storage Management Appliance
Event Log.
Table 8: HSV Element Manager Event Codes: Controller Events
76988030301631Storage Cell: %1 Event Code: %2 Description: The physical disk drive identified
77088030302332Storage Cell: %1 Event Code: %2 Description: The physical disk drive identified
Event
Code
Severity
SWC IDEvt.
No.Description
generated.
initialization the system time value was set to the value contained in the time field.
The action field contains one of the following codes which describes the condition
that caused the time value to be: 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.
the value contained in the time field by a call to the EXEC$SET_TIME service. As
part of setting the time in a dual HSV110 controller configuration, the times are
synchronized. The action field contains one of the following codes which
describes the action taken: 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 it’s 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.
in the node_name field has failed in communicating with the Cabinet (Rack) Bus
Interface Controller.
by the device field has been rendered inoperable. 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 rack_num field will
not be valid until a future release.
in the node_name field will not be used because the maximum number of
physical disk drives already exist in the current Storage System.
102688030402642Storage Cell: %1 Event Code: %2 Description: A machine check occurred while
Event
Code
Severity
SWC IDEvt.
No.
Description
begun booting.
in the node_name field, has finished the process of bringing the Storage System,
identified in the cell_tag fields, online.
in the node_name field has been joined into the Storage System.
in the node_name field has been ousted from the Storage System, identified in
the cell_tag fields
in the node_name field is now the Storage System master, identified in the
cell_tag fields, master
in the node_name field has been brought into the Storage System, identified in
the cell_tag fields.
terminated due to an unrecoverable event detected by either software or
hardware or due to an action initiated via the Storage System Management
Interface.
in the lter.terminating_ctrlr field sent a last gasp message prior to terminating
operation.
a termination event was being processed. The post-termination operation being
performed at the time the event occurred can be derived from the
lter.reuea_index 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 machine check occurred.
102888030404244Storage Cell: %1 Event Code: %2 Description: The Storage System Event Log
Event
Code
Severity
SWC IDEvt.
No.
Description
while a termination event was being processed. The value contained in the
uei.type field describes the event as follows: 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. B = The EDC of one or more Termination Event Array entries is bad. C =
Terminatio n 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 t ermination
processing got before the unexpected event occurred.
validation completed successfully. The content of the cinfo.scelcbi.status field, the
cinfo.scelcbi structure, and the minfo.scelmi structure show the validated state of
the Storage System Event Log. The meaning of the status value contained in the
cinfo.scelcbi.status field is as follows: 0 = No problems found.
Note: The content of the ainfo fields, cinfo.sctelcbi structure, and minfo.sctelmi
structure is undefined.
Table 8: HSV Element Manager Event Codes: Controller Events (Continued)
Event
ID
102988030405245Storage Cell: %1 Event Code: %2 Description: The Storage System Event Log
103088030406646Storage Cell: %1 Event Code: %2 Description: Event reports were lost due to an
103188030407647Storage Cell: %1 Event Code: %2 Description: Event reports were lost due to an
103288030408248Storage Cell: %1 Event Code: %2 Description: The Storage System Termination
Event
Code
Severity
SWC IDEvt.
No.
Description
validation failed. The content of the cinfo.scelcbi.status field, the cinfo.scelcbi
structure, and the minfo.scelmi structure show the state of the Storage System
Event Log at the time of the failure. The content and state of the Storage System
Event Log have been initialized to their initial operational settings. The meaning
of the status value contained in the cinfo.scelcbi.status field is as follows: 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.
Note: The content of the ainfo fields, cinfo.sctelcbi structure, and minfo.sctelmi
structure is undefined.
insufficient supply of Event Log Packets on the HSV110 controller that is the
Storage System Master. The ainfo.events_not_reported field shows the number of
event reports lost.
Note: The content of the ainfo.quiesce_type field, ainfo.remote_event field
cinfo.sctelcbi structure, and minfo.sctelmi structure is undefined.
insufficient supply of Event Log Packets on the HSV110 controller that is not the
Storage System Master. The ainfo.events_not_reported field shows the number of
event reports lost.
Note: The content of the ainfo.quiesce_type field, ainfo.remote_event field
cinfo.sctelcbi structure, and minfo.sctelmi structure is undefined.
Event Log has become inaccessible. The content of the cinfo.sctelcbi.status field,
the cinfo.sctelcbi structure, and the minfo.sctelmi structure show the current state
of the Storage System Termination Event Log. The meaning of the status value
contained in the cinfo.sctelcbi.status field is as follows: F = Control block read
failed during maintenance verification. 10= Control block read 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.
10388803040e64eStorage Cell: %1 Event Code: %2 Description: An HSV110 controller sent a last
Event
Code
Severity
SWC IDEvt.
No.
Description
Event Log validation completed successfully. The content of the
cinfo.sctelcbi.status field, the cinfo.sctelcbi structure, and the minfo.sctelmi
structure show the validated state of the Storage System Termination Event Log.
The meaning of the status value contained in the cinfo.sctelcbi.status field is as
follows: 0 = No problems found.
Note: The content of the ainfo fields, cinfo.scelcbi structure, and minfo.scelmi
structure is undefined.
Event Log validation failed. The content of the cinfo.sctelcbi.status field, the
cinfo.sctelcbi structure, and the minfo.sctelmi structure show the state of the
Storage System Termination Event Log at the time of the failure. The meaning of
the status value contained in the cinfo.sctelcbi.status field is as follows: F =
Control block read failed during maintenance verification. 10= Control block
read 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.
Event Log has been updated with the termination event information obtained
from the HSV110 controller that is not the Storage System Master. The content of
the cinfo.sctelcbi.status field, the cinfo.sctelcbi structure, and the minfo.sctelmi
structure show the updated state of the Storage System Termination Event Log.
The meaning of the status value contained in the cinfo.sctelcbi.status field is as
follows: 0 = No problems found.
Note: The content of the ainfo fields, cinfo.scelcbi structure, and minfo.scelmi
structure is undefined.
Storage System Master received an invalid Event Information Packet from the
remote Fault Manager. The header information from the invalid Event Information
packet is contained in the ainfo.remote_event field.
Note: The content of the ainfo.quiesce_type field, ainfo.events_not_reported field,
cinfo.scelcbi structure, cinfo.sctelcbi structure, minfo.scelmi structure, and
minfo.sctelmi structure is undefined.
was made quiescent. If the ainfo.quiesce_type field is equal to 0, the operation
was performed on both HSV110 controllers. If the ainfo.quiesce_type field is
equal to 1, the operation was performed only on the HSV110 controller that is
not the Storage System Master.
Note: The content of the ainfo.events_not_reported field, cinfo.scelcbi structure,
cinfo.sctelcbi structure, minfo.scelmi structure, and minfo.sctelmi structure is
undefined.
gasp message prior to terminating operation with an indication that the HSV110
controller identified in the lter.terminating_ctrlr field should also terminate
operation.
Table 8: HSV Element Manager Event Codes: Controller Events (Continued)
Event
ID
153688030600660Storage Cell: %1 Event Code: %2 Description: A physical disk drive has
153788030601361Storage Cell: %1 Event Code: %2 Description: A Fibre Channel port on the
153888030602262Storage Cell: %1 Event Code: %2 Description: A physical disk drive has
Event
Code
Severity
SWC IDEvt.
No.
Description
reported that it has exceeded its failure prediction threshold. The identity of the
physical disk drive is contained in the device field. The Fibre Channel port used
to communicate with the physical disk drive is contained in the cerp_id field. The
HSV110 controller internal Fibre Channel port number used to communicate with
the physical disk drive is contained in the port field. The arbitrated loop physical
address of the physical disk drive is contained in the al_pa field. If the bay field
contains a value other than zero, the location of the physical disk drive is
contained in the rack_num, dencl_num, and bay fields. If the bay field contains
a zero, the location of the physical disk drive is unknown and the content of the
rack_num and dencl_num fields is undefined. The rack_num field will not be
valid until a future release. The Fibre Channel Exchange Descriptor class is
contained in the fed_class field. The command issued to the physical disk drive is
contained in t he cmd field. The sense data obtained from the physical disk drive
as a result of the failure prediction threshold exceeded error is contained in the
error field.
HSV110 controller has failed to respond. The identity of the affected Fibre
Channel port is contained in the cerp_id field. The HSV110 controller internal
Fibre Channel port number of the affected Fibre Channel port is contained in the
port field. The peb array contains the port event block information. The
peq_frz_prod_index field contains the index to the port event block in use when
the Tachyon chip entered the frozen state. The peq_prod_index field contains the
index to the next port event block. The peq_cons_index field contains the index
to the next port event block to be acted upon. The failure_cause field contains the
internal routing.
reported a check condition error. The identity of the physical disk drive is
contained in the device field. The Fibre Channel port used to communicate with
the physical disk drive is contained in the cerp_id field. The HSV110 controller
internal Fibre Channel port number used to communicate with the physical disk
drive is contained in the port field. The arbitrated loop physical address of the
physical disk drive is contained in the al_pa field. If the bay field contains a
value other than zero, the location of the physical disk drive is contained in the
rack_num, dencl_num, and bay fields. If the bay field contains a zero, the
location of the physical disk drive is unknown and the content of the rack_num
and dencl_num fields is undefined. The rack_num field will not be valid until a
future release. The Fibre Channel Exchange Descriptor class is contained in the
fed_class field. The command issued to the physical disk drive is contained in the
cmd field. The sense data obt ained from the physical disk drive as a result of the
check condition error is contained in the error field.
Table 8: HSV Element Manager Event Codes: Controller Events (Continued)
HSV Element Manager Event Codes
Event
ID
153988030603363Storage Cell: %1 Event Code: %2 Description: A frame sent to a physical disk
154088030604364Storage Cell: %1 Event Code: %2 Description: Work was unexpectedly sent to
154188030605365Storage Cell: %1 Event Code: %2 Description: Work has been sent to a physical
Event
Code
Severity
SWC IDEvt.
No.
Description
drive or another HSV110 controller via the mirror port or a Drive Enclosure
Environmental Monitoring Unit has timed out. The identity of the intended
recipient is contained in the device field. The Fibre Channel port over which the
frame was sent is identified in the cerp_id field. The HSV110 controller internal
Fibre Channel port number over which the frame was sent is contained in the
port field. The arbitrated loop physical address of the intended recipient is
contained in the al_pa field. If the bay field contains a value other than zero, the
intended recipient was the physical disk drive located as indicated by the content
of the rack_num, dencl_num, and bay fields. If the bay field contains a zero, the
location of the intended recipient is unknown and the content of the rack_num
and dencl_num fields is undefined. The rack_num field will not be valid until a
future release. The number of timeouts detected is contained in the num_times
field.
this HSV110 controller by a physical disk drive or another HSV110 controller.
This HSV110 controller did not originate the work. The identity of the sender is
contained in the device field. The Fibre Channel port over which the unexpected
work was received is identified in the cerp_id field. The HSV110 controller
internal Fibre Channel port number over which the unexpected work was
received is contained in the port field. The arbitrated loop physical address of
the sender is contained in the al_pa field. If the bay field contains a value other
than zero, the sender was the physical disk drive located as indicated by the
content of the rack_num, dencl_num, and bay fields. If the bay field contains a
zero, the location of the sender is unknown and the content of the rack_num and
dencl_num fields is undefined. The rack_num field will not be valid until a future
release. The hdr_cdb field contains the command descriptor block and Fibre
Channel header information associated with the unexpected work.
disk drive or another HSV110 controller via the mirror port but it did not
respond. The identity of the intended target is contained in the device field. The
Fibre Channel port over which the work was sent is identified in the cerp_id field.
The HSV110 controller internal Fibre Channel port over which the work was sent
is contained in the port field. The arbitrated loop physical address of the
intended target is contained in the al_pa field. If the bay field contains a value
other than zero, the intended target was the physical disk drive located as
indicated by the content of the rack_num, dencl_num, and bay fields. If the bay
field contains a zero, the location of the intended target is unknown and the
content of the rack_num and dencl_num fields is undefined. The rack_num field
will not be valid until a future release. The Fibre Channel Exchange Descriptor
class is contained in the fed_class field. The command issued to the intended
target is contained in the c md field. Note that in this case the content of the
error field is undefined.
Table 8: HSV Element Manager Event Codes: Controller Events (Continued)
Event
ID
154388030607367Storage Cell: %1 Event Code: %2 Description: A Target Discovery Service
154488030608268Storage Cell: %1 Event Code: %2 Description: An excessive number of link
154588030609669Storage Cell: %1 Event Code: %2 Description: A physical disk drive has
Event
Code
Severity
SWC IDEvt.
No.
Description
Descriptor frame sent to a physical disk drive has timed out. The identity of the
physical disk drive is contained in the device field. The Fibre Channel port used
to communicate with the physical disk drive is contained in the cerp_id field. The
HSV110 controller internal Fibre Channel port number used to communicate with
the physical disk drive is contained in the port field. The arbitrated loop physical
address of the physical disk drive is contained in the al_pa field. If the bay field
contains a value other than zero, the location of the physical disk drive is
contained in the rack_num, dencl_num, and bay fields. If the bay field contains
a zero, the location of the physical disk drive is unknown and the content of the
rack_num and dencl_num fields is undefined. The rack_num field will not be
valid until a future release. The Fibre Channel Exchange Descriptor class is
contained in the fed_class field. The command issued to the physical disk drive is
contained in th e cmd field. Note that in this case the content of the error field is
undefined.
errors were detected on a HSV110 controller’s Fibre Channel port. The identity
of the affected Fibre Channel port is contained in the cerp_id field. The HSV110
controller internal Fibre Channel port number of the affected Fibre Channel port
is contained in the port field. This is an informational event triggered by the
occurrence of an excessive number of Tachyon chip link status errors detected
within a particular link status error type. The number of occurrences of each link
status error type is contained in a separate type-specific field (e.g.,
loss_of_signal, bad_rx_char, etc.). The HSV110 controller checks each of its
Fibre Channel port’s for excessive link status errors periodicaly.
reported numerous failure prediction threshold exceeded errors. The identity of
the physical disk drive is contained in the device field. The Fibre Channel port
used to communicate with the physical disk drive is contained in the cerp_id field.
The HSV110 controller internal Fibre Channel port number used to communicate
with the physical disk drive is contained in the port field. The arbitrated loop
physical address of the physical disk drive is contained in the al_pa field. If the
bay field contains a value other than zero, the location of the physical disk drive
is contained in the rack_num, dencl_num, and bay fields. If the bay field contains
a zero, the location of the physical disk drive is unknown and the content of the
rack_num and dencl_num fields is undefined. The rack_num field will not be
valid until a future release. The Fibre Channel Exchange Descriptor class is
contained in the fed_class field. The num_times field is the number of failure
prediction threshol d exceeded errors reported by the physical disk drive in the
previous minute.
Table 8: HSV Element Manager Event Codes: Controller Events (Continued)
HSV Element Manager Event Codes
Event
ID
15468803060a26aStorage Cell: %1 Event Code: %2 Description: A physical disk drive has
15478803060b36bStorage Cell: %1 Event Code: %2 Description: A non-data exchange frame sent
15488803060c26cStorage Cell: %1 Event Code: %2 Description: A loop switch has been detected
15498803060d26dStorage Cell: %1 Event Code: %2 Description: The location of a physical disk
Event
Code
Severity
SWC IDEvt.
No.
Description
reported numerous check condition errors. The identity of the physical disk drive
is contained in the device field. The Fibre Channel port used to communicate
with the physical disk drive is contained in the cerp_id field. The HSV110
controller internal Fibre Channel port number used to communicate with the
physical disk drive is contained in the port field. The arbitrated loop physical
address of the physical disk drive is contained in the al_pa field. If the bay field
contains a value other than zero, the location of the physical disk drive is
contained in the rack_num, dencl_num, and bay fields. If the bay field contains
a zero, the location of the physical disk drive is unknown and the content of the
rack_num and dencl_num fields is undefined. The rack_num field will not be
valid until a future release. The Fibre Channel Exchange Descriptor class is
contained in the fed_class field. The num_times field is the number of check
condition errors reported by the physical disk drive in the previous minute.
to a physical disk drive has timed out. The identity of the physical disk drive is
contained in the device field. The Fibre Channel port used to communicate with
the physical disk drive is contained in the cerp_id field. The HSV110 controller
internal Fibre Channel port number used to communicate with the physical disk
drive is contained in the port field. The arbitrated loop physical address of the
physical disk drive is contained in the al_pa field. If the bay field contains a
value other than zero, the location of the physical disk drive is contained in the
rack_num, dencl_num, and bay fields. If the bay field contains a zero, the
location of the physical disk drive is unknown and the content of the rack_num
and dencl_num fields is undefined. The rack_num field will not be valid until a
future release. The Fibre Channel Exchange Descriptor class is contained in the
fed_class field. The command issued to the physical disk drive is contained in the
cmd field. Note that in this case the content of the error field is undefined.
on a Fibre Channel port. The identity of the Fibre Channel port is contained in
the cerp_id field. The HSV110 controller internal Fibre Channel port number is
contained in the port field. Note that in this case the device, al_pa, rack_num,
dencl_num, bay, fed_class and num_times fields are undefined.
drive previously reported as unknown is now known. The identity of the physical
disk drive is contained in the device field. The Fibre Channel port used to
communicate with the physical disk drive is contained in the cerp_id field. The
HSV110 controller internal Fibre Channel port number used to communicate with
the physical disk drive is contained in the port field. The arbitrated loop physical
address of the physical disk drive is contained in the al_pa field. The location of
the physical disk drive is contained in the rack_num, dencl_num, and bay fields.
The rack_num field will not be valid until a future release. Note that in this case
the content of the fed_class and num_times fields is undefined.
15518803060f66fStorage Cell: %1 Event Code: %2 Description: The Drive Enclosure
1552880306106610Storage Cell: %1 Event Code: %2 Description: The Drive Enclosure
Event
Code
Severity
SWC IDEvt.
No.
Description
Monitoring Unit requested a code update but the code update could not be
found, so the update was not performed. The identity of the affected Drive
Enclosure Environmental Monitoring Unit is contained in the device field. The
Fibre Channel port used to communicate with the Drive Enclosure Environmental
Monitoring Unit is contained in the cerp_id field. The HSV110 controller internal
Fibre Channel port number used to communicate with the Drive Enclosure
Environmental Monitoring Unit is contained in the port field. The location of the
Drive Enclosure Environmental Monitoring Unit is contained in the rack_num and
dencl_num fields. The rack_num field will not be valid until a future release.
Note that in this case the content of the al_pa, bay, fed_class and num_times
field is undefined.
Environmental Monitoring Unit is able to communicate with a physical disk drive
but this HSV110 controller is unable to communicate with that physical disk drive
on the Fibre Channel bus. The identity of the Drive Enclosure Environmental
Monitoring Unit is contained in the device field. The Fibre Channel port used to
communicate with the physical disk drive is contained in the cerp_id field. The
HSV110 controller internal Fibre Channel port number used to communicate with
the physical disk drive is contained in the port field. The location of the physical
disk drive is contained in the rack_num, dencl_num, and bay fields. The
rack_num field will not be valid until a future release. Note that in this case the
content of the al_pa, fed_class and num_times fields is undefined.
Environmental Monitoring Unit is unable to communicate with this HSV110
controller. The Drive Enclosure Environmental Monitoring Unit has either stopped
communicating with the HSV110 controller, or is not connected to the rack. If the
Drive Enclosure Environmental Monitoring Unit is not connected to the rack, then
the location of the Drive Enclosure Environmental Monitoring Unit is unknown. If
the bay field contains a value other than zero, the identity of the Drive Enclosure
Environmental Monitoring Unit is contained in the device field. If the bay field
contains a zero, the content of the device field is undefined. The Fibre Channel
port used to communicate with the Drive Enclosure Environmental Monitoring
Unit is contained in the cerp_id field. The HSV110 controller internal Fibre
Channel port number used to communicate with the Drive Enclosure
Environmental Monitoring Unit is contained in the port field. If the bay field
contains a value other than zero, the location of the Dr ive Enclosure
Environmental Monitoring Unit is contained in the rack_num and dencl_num
fields. If the bay field contains a zero, the location of the Drive Enclosure
Environmental Monitoring Unit is unknown and the content of the rack_num and
dencl_num fields is undefined. The rack_num field will not be valid until a future
release. Note that in this case the content of the al_pa, fed_class and num_times
fields is undefined.
assigned to a Drive Enclosure Environmental Monitoring Unit has been
exhausted. The Fibre Channel port used to communicate with the physical disk
drive is contained in the cerp_id field. The HSV110 controller internal Fibre
Channel port number used to communicate with the physical disk drive is
contained in the port field. The peb array contains the task list that was intended
to be sent to the Drive Enclosure Environmental Monitoring Unit. The
peq_frz_prod_index field contains the task that was being retried. The
peq_prod_index field contains the drive enclosure where the physical disk drive
used to communicate with the Drive Enclosure Environmental Monitoring Unit is
located. The peq_cons_index field identifies the Fibre Channel loop pair (0 =
Loop A, 1 = Loop B) used to communicate with the physical disk drive that was
used to communicate with the Drive Enclosure Environmental Monitoring Unit.
The failure_cause field contains the bay where the physical disk drive used to
communicate with the
Monitoring Unit is able to communicate with this HSV110 controller. The identity
of the Drive Enclosure Environmental Monitoring Unit is contained in the device
field. The Fibre Channel port used to communicate with the Drive Enclosure
Environmental Monitoring Unit is contained in the cerp_id field. The HSV110
controller internal Fibre Channel port number used to communicate with the
Drive Enclosure Environmental Monitoring Unit is contained in the port field. The
location of the Drive Enclosure Environmental Monitoring Unit is contained in the
rack_num and dencl_num fields. The rack_num field will not be valid until a
future release. Note that in this case the content of the bay, fed_class and
num_times fields is undefined.
enclosures. The Fibre Channel port with too many drive enclosures attached to
the HSV110 controller is contained in the cerp_id field. Note that in this case the
content of the bay, fed_class, rack_num, dencl_num and num_times fields is
undefined.
module is attached to the wrong Fibre Channel port. The Fibre Channel port
incorrectly attached to the HSV110 controller is contained in the cerp_id field.
Note that in this case the content of the bay, fed_class, rack_num, dencl_num
and num_times fields is undefined.
have an address on the enclosure address bus. The HSV110 controller location
cannot be identified. Note that in this case the content of the bay, fed_class,
rack_num, dencl_num, alpa, device, cerp_id, port, and num_times fields are
undefined.
Monitoring Unit has detected a physical disk drive that was preventing proper
loop operation. The physical disk drive has been bypassed and is ready for
replacement. The location of this physical disk drive is specified by the
rack_num, bay, and dencl_num fields. The rack_num field will not be valid until
a future release. The identity of the Drive Enclosure Environmental Monitoring
Unit is contained in the device field. The UUID of the specific physical disk drive
is not identifiable. Check the fault lights of the enclosure associated with this Drive
Enclosure Environmental Monitoring Unit. Note that in this case the content of
the fed_class, alpa, and num_times fields are undefined.
15628803061a661aStorage Cell: %1 Event Code: %2 Description: A physical disk drive has
15638803061b261bStorage Cell: %1 Event Code: %2 Description: A HSV110 controller now has an
Event
Code
Severity
SWC IDEvt.
No.
Description
Monitoring Unit has begun updating its code. Do not power down this drive
enclosure until the code update has completed. The identity of the Drive Enclosure
Environmental Monitoring Unit is contained in the device field. The Fibre
Channel port used to communicate with the Drive Enclosure Environmental
Monitoring Unit is contained in the cerp_id field. The HSV110 controller internal
Fibre Channel port number used to communicate with the Drive Enclosure
Environmental Monitoring Unit is contained in the port field. The location of the
Drive Enclosure Environmental Monitoring Unit is contained in the rack_num and
dencl_num fields. The rack_num field will not be valid until a future release.
Note that in this case the content of the fed_class, alpa, and num_times fields are
undefined.
Monitoring Unit has completed updating its code. It is now safe to power down
this drive enclosure. The identity of the Drive Enclosure Environmental Monitoring
Unit is contained in the device field. The Fibre Channel port used to
communicate with the Drive Enclosure Environmental Monitoring Unit is
contained in the cerp_id field. The HSV110 controller internal Fibre Channel
port number used to communicate with the Drive Enclosure Environmental
Monitoring Unit is contained in the port field. The location of the Drive Enclosure
Environmental Monitoring Unit is contained in the rack_num and dencl_num
fields. The rack_num field will not be valid until a future release. Note that in this
case the content of the fed_class, alpa, and num_times fields are undefined.
exceeded its soft error threshold. The identity of the physical disk drive is
contained in the device field. The Fibre Channel port used to communicate with
the physical disk drive is contained in the cerp_id field. The HSV110 controller
internal Fibre Channel port number used to communicate with the physical disk
drive is contained in the port field. The arbitrated loop physical address of the
physical disk drive is contained in the al_pa field. If the bay field contains a
value other than zero, the location of the physical disk drive is contained in the
rack_num, dencl_num, and bay fields. If the bay field contains a zero, the
location of the physical disk drive is unknown and the content of the rack_num
and dencl_num fields is undefined. The rack_num field will not be valid until a
future release. Note that in this case the content of the fed_class, cdb, and
sense_data fields are undefined.
address on the enclosure address bus. The HSV110 controller location has been
identified. The location of the HSV110 controller is contained in the rack_num
and dencl_num fields. The rack_num field will not be valid until a future release.
Note that in this case the content of the bay, fed_class, alpa, cerp_id, port, and
num_times fields are undefined.
Table 8: HSV Element Manager Event Codes: Controller Events (Continued)
HSV Element Manager Event Codes
Event
ID
15648803061c361cStorage Cell: %1 Event Code: %2 Description: A non-data exchange frame sent
230588030901291Storage Cell: %1 Event Code: %2 Description: The state of the Physical Disk
230688030902292Storage Cell: %1 Event Code: %2 Description: The state of the Volume identified
230788030903293Storage Cell: %1 Event Code: %2 Description: The state of The internal Logical
230888030904294Storage Cell: %1 Event Code: %2 Description: The state of the HSV110
230988030905295Storage Cell: %1 Event Code: %2 Description: The state of a battery assembly
231088030906696Storage Cell: %1 Event Code: %2 Description: The state of the Volume identified
Event
Code
Severity
SWC IDEvt.
No.
Description
to a physical disk drive has timed out. The identity of the physical disk drive is
contained in the device field. The Fibre Channel port used to communicate with
the physical disk drive is contained in the cerp_id field. The HSV110 controller
internal Fibre Channel port number used to communicate with the physical disk
drive is contained in the port field. The arbitrated loop physical address of the
physical disk drive is contained in the al_pa field. If the bay field contains a
value other than zero, the location of the physical disk drive is contained in the
rack_num, dencl_num, and bay fields. If the bay field contains a zero, the
location of the physical disk drive is unknown and the content of the rack_num
and dencl_num fields is undefined. The rack_num field will not be valid until a
future release. The Fibre Channel Exchange Descriptor class is contained in the
fed_class field. The command issued to the physical disk drive is contained in the
cmd field. Note that in this case the content of the error field is undefined.
Drive identified in the handle field has transitioned to the NORMAL state. The
value.ul1 field contains the new state: 1 (NORMAL). The value.ul2 field contains
the old state. The state values that may be in the value.ul2 field are as follows: 2
= Degraded 3 = Failed 4 = Not present
in the handle field has changed. The value.ul1 field contains the new state. The
value.ul2 field contains the old state. The state values that may be found in the
value.ul1 and value.ul2 fields are as follows: 1 = Normal 2 = Migrating 3 =
Missing 4 = Reconstructing 5 = Completing 6 = Reverting 7 = Failed
Disk associated with the Virtual Disk identified in the handle field has changed.
The value.ul1 field contains the new state. The value.ul2 field contains the old
state. The state values that may be found in the value.ul1 and value.ul2 fields are
as follows: 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
controller identified in the handle field has transitioned to the NORMAL state. The
value.ul1 field contains the new state: 1 (NORMAL). The value.ul2 field contains
the old state: 3 (FAILED).
within the HSV110 controller identified in the handle field has changed. The
value.ul1 field contains the new state. The value.ul2 field contains the old state.
The state values that may be found in the value.ul1 and value.ul2 fields are as
follows: 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
in the handle field has transitioned to the MISSING state. The value.ul1 field
contains the new state: 3 (MISSING). The value.ul2 field contains the old state.
The state values that may be found in the value.ul2 field are as follows: 1 =
Normal 2 = Migrating 4 = Reconstructing 5 = Completing 6 = Reverting 7 =
Failed
231388030909299Storage Cell: %1 Event Code: %2 Description: The Resource Availability state of
23148803090a29aStorage Cell: %1 Event Code: %2 Description: The Data Availability state of the
23168803090c29cStorage Cell: %1 Event Code: %2 Description: The Snapclone Logical Disk
23178803090d29dStorage Cell: %1 Event Code: %2 Description: The state of the Quorum Disk flag
23188803090e39eStorage Cell: %1 Event Code: %2 Description: The temperature trip point for a
23198803090f39fStorage Cell: %1 Event Code: %2 Description: A temperature sensor located
2321880309112911Storage Cell: %1 Event Code: %2 Description: The Blower Present flag for the ‘1’
2322880309126912Storage Cell: %1 Event Code: %2 Description: The ‘1’ blower located within the
2323880309132913Storage Cell: %1 Event Code: %2 Description: One of the voltage sensors
Event
Code
Severity
SWC IDEvt.
No.
Description
port identified in the attribute.value.str field and located on the rear panel of the
HSV110 controller identified in the handle field has transitioned to the NORMAL
state. The attribute.type field contains the value 4. The value.ul1 field contains the
new state: 1 (NORMAL). The value.ul2 field contains the old state: 2 (FAILED).
Note that the HSV110 controller’s internal identity of the affected Fibre Channel
port is contained in the secondary_id field.
threshold has been reached for the Disk Group identified in the handle field.
the Volume identified in the handle field has transitioned to the SUFFICIENT state.
The value.ul1 field contains the new state: 0 (SUFFICIENT). The value.ul2 field
contains the old state: 1 (INSUFFICIENT).
Logical Disk identified in the handle field has transitioned to the NORMAL state.
The value.ul1 field contains the new state: 0 (NORMAL). The value.ul2 field
contains the old state: 1 (DATA LOST).
identified in the handle field has completed the unsharing operation.
for the Volume identified in the handle field has changed. The value.ul1 field
contains the new state of the Quorum Disk flag. The value.ul2 field contains the
old state of the Quorum Disk flag. The state values that may be found in the
value.ul1 and value.ul2 fields are as follows: 0 = FALSE 1 = TRUE
temperature sensor located within the HSV110 controller identified in the handle
field has been reached.
within the HSV110 controller identified in the handle field is approaching its trip
point. The value.ul1 field contains the current temperature reading from that
sensor in Celsius. The secondary_id field contains the temperature trip point in
Celsius.
blower assembly located within the HSV110 controller identified in the handle
field has transitioned from the NOT PRESENT to PRESENT state indicating that
the blower has been reinstalled. The secondary_id field contains the ‘1’ blower
assembly internal identifier value: 1. The value.ul1 field contains the new state of
the Blower Present flag: 1 (PRESENT). The value.ul2 field contains the old state of
the Blower Present flag: 0 (NOT PRESENT).
HSV110 controller identified in the handle field is running slower than the lowest
acceptable speed. The secondary_id field contains the ‘1’ blower assembly
internal identifier value: 1. The value.ul1 field contains the current speed of the
‘1’ blower. The value.ul2 field contains the lowest acceptable speed for the ‘1’
blower.
located within the HSV110 controller identified in the handle field has reported a
voltage that is out of range. The value.ul1 field contains the out of range voltage
value. The secondary_id field contains the specific voltage threshold value (i.e.,
12V, 5V, 3.3V, 2.5V or 2V). Note that the voltages are expressed in
millivolts--e.g.,12.5V is expressed as 12500.
Table 8: HSV Element Manager Event Codes: Controller Events (Continued)
HSV Element Manager Event Codes
Event
ID
2324880309146914Storage Cell: %1 Event Code: %2 Description: The state of the Volume identified
2325880309156915Storage Cell: %1 Event Code: %2 Description: The state of the HSV110
2327880309176917Storage Cell: %1 Event Code: %2 Description: The Battery Present flag for
2328880309182918Storage Cell: %1 Event Code: %2 Description: The Battery In Use flag for battery
2329880309192919Storage Cell: %1 Event Code: %2 Description: One of the voltage sensors
23308803091a391aStorage Cell: %1 Event Code: %2 Description: The battery assembly voltage
23318803091b291bStorage Cell: %1 Event Code: %2 Description: The state of the Disk Group
23328803091c291cStorage Cell: %1 Event Code: %2 Description: The Occupancy Alarm Level for
Event
Code
Severity
SWC IDEvt.
No.
Description
in the handle field has transitioned to the FAILED state. The value.ul1 field
contains the new state: 7 (FAILED). The value.ul2 field contains the old state. The
state values that may be found in the value.ul2 fields are as follows: 1 = Normal
2 = Migrating 3 = Missing 4 = Reconstructing 5 = Completing 6 = Reverting
controller identified in the handle field has transitioned to the FAILED state. The
value.ul1 field contains the new state: 3 (FAILED). The value.ul2 field contains the
old state: 1 (NORMAL).
battery assembly ‘1’ located within the HSV110 controller identified in the
handle field has changed from PRESENT to NOT PRESENT indicating that the
battery assembly was removed. The secondary_id field contains the battery
assembly ‘1’ internal identifier value: 1. The value.ul1 field contains the new state
of the Battery Present flag: 0 (NOT PRESENT). The value.ul2 field contains the old
state of the Battery Present flag: 1 (PRESENT).
assembly ‘1’ located within the HSV110 controller identified in the handle field
has transitioned from the NOT IN USE to IN USE state indicating that the battery
assembly is functioning properly. The secondary_id field contains the battery
assembly ‘1’ internal identifier value: 1. The value.ul1 field contains the new state
of the Battery In Use flag: 1 (IN USE). The value.ul2 field contains the old state of
the Battery In Use flag: 0 (NOT IN USE).
located within the HSV110 controller identified in the handle field has reported a
voltage that indicates that a voltage that was previously out of range has returned
to the normal range. The value.ul1 field contains the normal range voltage
value. The secondary_id field contains the voltage threshold value (i.e., 12V, 5V,
3.3V, 2.5V or 2V). Note that the voltages are expressed in thousands--e.g.,
12.5V is expressed as 12500.
regulator located within the HSV110 controller identified in the handle field is
offline.
identified in the handle field has transitioned to the NORMAL state. The value.ul1
field contains the new Disk Group state: 1 (NORMAL). The value.ul2 field
contains the old Disk Group state. The state values that may be found in the
value.ul2 field are as follows: 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
the Disk Group identified in the handle field has returned to the normal range.
Table 8: HSV Element Manager Event Codes: Controller Events (Continued)
Event
ID
23338803091d691dStorage Cell: %1 Event Code: %2 Description: The Battery In Use flag for battery
23348803091e291eStorage Cell: %1 Event Code: %2 Description: The Battery Present flag for
23358803091f691fStorage Cell: %1 Event Code: %2 Description: The Battery Present flag for
2336880309202920Storage Cell: %1 Event Code: %2 Description: The Battery Present flag for
2337880309212921Storage Cell: %1 Event Code: %2 Description: The Battery In Use flag for battery
2338880309226922Storage Cell: %1 Event Code: %2 Description: The Battery In Use flag for battery
2339880309236923Storage Cell: %1 Event Code: %2 Description: The Blower Present flag for the ‘2’
Event
Code
Severity
SWC IDEvt.
No.
Description
assembly ‘1’ located within the HSV110 controller identified in the handle field
has transitioned from the IN USE to NOT IN USE state indicating that the battery
assembly has malfunctioned. The secondary_id field contains the battery
assembly ‘1’ internal identifier value: 1. The value.ul1 field contains the new state
of the Battery In Use flag: 0 (NOT IN USE). The value.ul2 field contains the old
state of the Battery In Use flag: 1 (IN USE).
battery assembly ‘1’ located within the HSV110 controller identified in the
handle field has changed from NOT PRESENT to PRESENT indicating that the
battery assembly was reinstalled. The secondary_id field contains the battery
assembly ‘1’ internal identifier value: 1. The value.ul1 field contains the new state
of the Battery Present flag: 1 (PRESENT). The value.ul2 field contains the old state
of the Battery Present flag: 0 (NOT PRESENT).
battery assembly ‘2’ located within the HSV110 controller identified in the
handle field has changed from PRESENT to NOT PRESENT indicating that the
battery assembly was removed. The secondary_id field contains the battery
assembly ‘2’ internal identifier value: 2. The value.ul1 field contains the new state
of the Battery Present flag: 0 (NOT PRESENT). The value.ul2 field contains the old
state of the Battery Present flag: 1 (PRESENT).
battery assembly ‘2’ located within the HSV110 controller identified in the
handle field has changed from NOT PRESENT to PRESENT indicating that the
battery assembly was reinstalled. The secondary_id field contains the battery
assembly ‘2’ internal identifier value: 2. The value.ul1 field contains the new state
of the Battery Present flag: 1 (PRESENT). The value.ul2 field contains the old state
of the Battery Present flag: 0 (NOT PRESENT).
assembly ‘2’ located within the HSV110 controller identified in the handle field
has transitioned from the NOT IN USE to IN USE state indicating that the battery
assembly is functioning properly. The secondary_id field contains the battery
assembly ‘2’ internal identifier value: 2. The value.ul1 field contains the new state
of the Battery In Use flag: 1 (IN USE). The value.ul2 field contains the old state of
the Battery In Use flag: 0 (NOT IN USE).
assembly ‘2’ located within the HSV110 controller identified in the handle field
has transitioned from the IN USE to NOT IN USE state indicating that the battery
assembly has malfunctioned. The secondary_id field contains the battery
assembly ‘2’ internal identifier value: 2. The value.ul1 field contains the new state
of the Battery In Use flag: 0 (NOT IN USE). The value.ul2 field contains the old
state of the Battery In Use flag: 1 (IN USE).
blower assembly located within the HSV110 controller identified in the handle
field has transitioned from the PRESENT to NOT PRESENT state indicating that
the blower has been removed. The secondary_id field contains the ‘2’ blower
assembly internal identifier value: 2. The value.ul1 field contains the new state of
the Blower Present flag: 0 (NOT PRESENT). The value.ul2 field contains the old
state of the Blower Present flag: 1 (PRESENT).
blower assembly located within the HSV110 controller identified in the handle
field has transitioned from the NOT PRESENT to PRESENT state indicating that
the blower has been reinstalled. The secondary_id field contains the ‘2’ blower
assembly internal identifier value: 2. The value.ul1 field contains the new state of
the Blower Present flag: 1 (PRESENT). The value.ul2 field contains the old state of
the Blower Present flag: 0 (NOT PRESENT).
HSV110 controller identified in the handle field is running slower than the lowest
acceptable speed. The secondary_id field contains the ‘2’ blower assembly
internal identifier value: 2. The value.ul1 field contains the current speed of the
‘2’ blower. The value.ul2 field contains the lowest acceptable speed for the ‘2’
blower.
flag for the ‘1’ blower/power supply assembly located within the HSV110
controller identified in the handle field has transitioned from the PRESENT to
NOT PRESENT state indicating that the blower/power supply has been removed.
The secondary_id field contains the ‘1’ blower/power supply assembly internal
identifier value: 1. The value.ul1 field contains the new state of the Blower/Power
Supply Present flag: 0 (NOT PRESENT). The value.ul2 field contains the old state
of the Blower/Power Supply Present flag: 1 (PRESENT).
flag for the ‘1’ blower/power supply assembly located within the HSV110
controller identified in the handle field has transitioned from the NOT PRESENT
to PRESENT state indicating that the blower/power supply has been reinstalled.
The secondary_id field contains the ‘1’ blower/power supply assembly internal
identifier value: 1. The value.ul1 field contains the new state of the Blower/Power
Supply Present flag: 1 (PRESENT). The value.ul2 field contains the old state of the
Blower/Power Supply Present flag: 0 (NOT PRESENT).
flag for the ‘2’ blower/power supply assembly located within the HSV110
controller identified in the handle field has transitioned from the PRESENT to
NOT PRESENT state indicating that the blower/power supply has been removed.
The secondary_id field contains the ‘2’ blower/power supply assembly internal
identifier value: 2. The value.ul1 field contains the new state of the Blower/Power
Supply Present flag: 0 (NOT PRESENT). The value.ul2 field contains the old state
of the Blower/Power Supply Present flag: 1 (PRESENT).
flag for the ‘2’ blower/power supply assembly located within the HSV110
controller identified in the handle field has transitioned from the NOT PRESENT
to PRESENT state indicating that the blower/power supply has been reinstalled.
The secondary_id field contains the ‘2’ blower/power supply assembly internal
identifier value: 2. The value.ul1 field contains the new state of the Blower/Power
Supply Present flag: 1 (PRESENT). The value.ul2 field contains the old state of the
Blower/Power Supply Present flag: 0 (NOT PRESENT).
located within the HSV110 controller identified in the handle field is running
slower than the lowest acceptable speed. The secondary_id field contains the ‘1’
blower/power supply assembly internal identifier value: 1. The value.ul1 field
contains the current speed of the ‘1’ blower/power supply. The value.ul2 field
contains the lowest acceptable speed for the ‘1’ blower/power supply.
2353880309316931Storage Cell: %1 Event Code: %2 Description: The state of the Physical Disk
2354880309326932Storage Cell: %1 Event Code: %2 Description: The state of the Physical Disk
2355880309332933Storage Cell: %1 Event Code: %2 Description: The Derived Unit identified in the
2356880309342934Storage Cell: %1 Event Code: %2 Description: The internal Logical Disk
Event
Code
Severity
SWC IDEvt.
No.
Description
located within the HSV110 controller identified in the handle field is running
slower than the lowest acceptable speed. The secondary_id field contains the ‘2’
blower/power supply assembly internal identifier value: 2. The value.ul1 field
contains the current speed of the ‘2’ blower/power supply. The value.ul2 field
contains the lowest acceptable speed for the ‘2’ blower/power supply.
within the HSV110 controller identified in the handle field has transitioned to the
Battery System Hold-up Time is zero hours state. The value.ul1 field contains the
new state 3: (Battery System Hold-up Time is zero hours). The value.ul2 field
contains the old state. The state values that may be found in the value.ul2 field
are as follows: 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
the Volume identified in the handle field has transitioned to the INSUFFICIENT
state. The value.ul1 field contains the new state: 1 (INSUFFICIENT). The value.ul2
field contains the old state: 0 (SUFFICIENT).
in the handle field rejected a login attempt. The value.ul1 and value.ul2 fields
contain words [0] and [1], respectively, of the World Wide Name of the host
adapter that originated the rejected login attempt. The secondary_id field
contains the reason for the rejection as follows: 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
in the handle field processed a StorageCell Management Interface command
with the result of non-success return code. The value.ul1 field contains the
command type. The value.ul2 field contains the return code.
in the handle field has updated the physical disk drive map for the loop pair
identified in the secondary_id field. The value.ul1 field contains the new internal
map generation number. The value.ul2 field contains the old internal map
generation number.
Drive identified in the handle field has transitioned to the DEGRADED state. The
value.ul1 field contains the new state: 2 (DEGRADED). The value.ul2 field
contains the old state. The state values that may be in the value.ul2 field are as
follows: 1 = Normal 3 = Failed 4 = Not present
Drive identified in the handle field has transitioned to the FAILED state. The
value.ul1 field contains the new state: 3 (FAILED). The value.ul2 field contains the
old state. The state values that may be in the value.ul2 field are as follows: 1 =
Normal 2 = Degraded 4 = Not present
handle field was created. The add_handle field contains the identity of the
Storage System Virtual Disk that is associated with that Derived Unit. The
atribute.value.obj field contains the identity of the Virtual Disk associated with
that Derived Unit.
associated with the Virtual Disk identified in the handle field was created.
Table 8: HSV Element Manager Event Codes: Controller Events (Continued)
HSV Element Manager Event Codes
Event
ID
2357880309352935Storage Cell: %1 Event Code: %2 Description: The Disk Group identified in the
2358880309362936Storage Cell: %1 Event Code: %2 Description: The Physical Disk Drive identified
2359880309372937Storage Cell: %1 Event Code: %2 Description: The Presented Unit identified in
2360880309382938Storage Cell: %1 Event Code: %2 Description: The Storage System Host path
2361880309392939Storage Cell: %1 Event Code: %2 Description: The Storage System Virtual Disk
23628803093a293aStorage Cell: %1 Event Code: %2 Description: The Volume identified in the
23638803093b293bStorage Cell: %1 Event Code: %2 Description: The Derived Unit identified in the
23648803093c293cStorage Cell: %1 Event Code: %2 Description: The internal Logical Disk
23658803093d293dStorage Cell: %1 Event Code: %2 Description: The Disk Group identified in the
23668803093e693eStorage Cell: %1 Event Code: %2 Description: The Physical Disk Drive identified
23678803093f293fStorage Cell: %1 Event Code: %2 Description: The Presented Unit identified in
2368880309402940Storage Cell: %1 Event Code: %2 Description: The Storage System Host path
2369880309412941Storage Cell: %1 Event Code: %2 Description: The Storage System Virtual Disk
2370880309426942Storage Cell: %1 Event Code: %2 Description: The Snapshot Logical Disk
Event
Code
Severity
SWC IDEvt.
No.
Description
handle field was created.
in the handle field was discovered. The enclosure number and bay number where
the Physical Disk Drive is located are contained in the attribute.value.u32[0] and
attribute.value.u32[1] fields, respectively. The attribute.type field contains the
value 1.
the handle field was created. The add_handle field contains the identity of the
Storage System Virtual Disk that is associated with the Presented Unit. This
Presented Unit is associated with the Virtual Disk identified in the
attribute.value.obj.handle field.
identified in the handle field was created.
identified in the handle field was created.
handle field was created. The add_handle field contains the identity of the
Physical Disk Drive that is associated with the Volume.
handle field was deleted. The add_handle field contains the identity of the
Storage System Virtual Disk that was associated with the Derived Unit. This
Derived Unit is associated with the Virtual Disk identified in the
attribute.value.obj.handle field.
associated with the Virtual Disk identified in the handle field was deleted.
handle field was deleted.
in the handle field has disappeared. The enclosure number and bay number
where the Physical Disk Drive was located are contained in the
attribute.value.u32[0] and attribute.value.u32[1] fields, respectively. The
attribute.type field contains the value 1.
the handle field was deleted. The add_handle field contains the identity of the
Storage System Virtual Disk that was associated with the Presented Unit. This
Presented Unit is associated with the Virtual Disk identified in the
attribute.value.obj.handle field.
identified in the handle field was deleted.
identified in the handle field was deleted. The Storage System Virtual Disk is
associated with the Virtual Disk identified in the add_handle field.
identified in the handle field has been marked inoperative due to the Disk Group
being out of space for additional storage allocation.
2373880309452945Storage Cell: %1 Event Code: %2 Description: The Storage System identified by
2405880309652965Storage Cell: %1 Event Code: %2 Description: The Host Operating System mode
2406880309662966Storage Cell: %1 Event Code: %2 Description: Time was set on the Storage
2407880309672967Storage Cell: %1 Event Code: %2 Description: The LUN of the Presented Unit
2408880309682968Storage Cell: %1 Event Code: %2 Description: The Device Addition Policy of the
2409880309692969Storage Cell: %1 Event Code: %2 Description: The Quiescent state of the
Event
Code
Severity
SWC IDEvt.
No.
Description
in the handle field has joined the Storage System. If the handle field is zero, the
HSV110 controller identity could not be obtained due to an unexpected state
transition.
in the handle field has left the Storage System. If the handle field is zero, the
HSV110 controller identity could not be obtained due to an unexpected state
transition.
the handle field was deleted by the HSV110 controller identified in the
add_handle field. If the handle field or add_handle field is zero, the
corresponding identity could not be obtained due to an unexpected state
transition.
of the Storage System Host identified in the handle field has changed. The
old_attr.type and new_attr.type fields contain the value 1. The
old_attr.value.u32[0] field contains the old Host Operating System mode. The
new_attr.value.u32[0] field contains the new Host Operating System mode. The
values that may be found in the old_attr.value.u32[0] and new_attr.value.u32[0]
fields are as follows: 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
System identified in the handle field.
identified in the handle field has changed. The old_attr.type field and the
new_attr.type fields contain the value 1. The old_attr.value.u32[0..1] fields
contain the value of the old LUN. The new_attr.value.u32[0..1] fields contain the
value of the new LUN. The secondary_id field contains the noid portion of the
handle for the Storage System Virtual Disk associated with the Presented Unit.
This Presented Unit is associated with the Virtual Disk identified in the
add_handle field.
Storage System identified in the handle field has changed. 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 Device Addition Policy. The new_attr.value.u32[0] field contains
the new Device Addition 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 =
Manual policy 2 = Automatic policy
Storage System Virtual Disk identified in the handle field has changed. 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 Quiescent state. The
new_attr.value.u32[0] field contains the new Quiescent state. The state values
that may be found in the old_attr.value.u32[0] and new_attr.value.u32[0] fields
are as follows: 0 = FALSE 1 = TRUE This Storage System Virtual Disk is associated
with the Virtual Disk identified in the add_handle field.
Table 8: HSV Element Manager Event Codes: Controller Events (Continued)
HSV Element Manager Event Codes
Event
ID
24108803096a296aStorage Cell: %1 Event Code: %2 Description: The Enabled/Disabled state of
24118803096b296bStorage Cell: %1 Event Code: %2 Description: The Cache Policy of the Storage
24128803096c296cStorage Cell: %1 Event Code: %2 Description: The Usage state of the Volume
24138803096d296dStorage Cell: %1 Event Code: %2 Description: The Disk Failure Protection Level
24148803096e296eStorage Cell: %1 Event Code: %2 Description: The Write Protected state of the
2416880309703970Storage Cell: %1 Event Code: %2 Description: The Physical Disk Drive identified
Event
Code
Severity
SWC IDEvt.
No.
Description
the Storage System Virtual Disk identified in the handle field has changed. 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 Enabled/Disabled state. The
new_attr.value.u32[0] field contains the new Enabled/Disabled state. The state
values that may be found in the old_attr.value.u32[0] and new_attr.value.u32[0]
fields are as follows: 1 = Disabled 2 = Enabled This Storage System Virtual Disk
is associated with the Virtual Disk identified in the add_handle field.
System Virtual Disk identified in the handle field has changed. 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 This Storage System Virtual Disk is
associated with the Virtual Disk identified in the add_handle field.
identified in the handle field has changed. The old_attr.value.u32[0] field
contains the old Usage state. The new_attr.value.u32[0] field contains the new
Usage state. The Usage state values that may be found in the
old_attr.value.u32[0] and new_attr.value.u32[0] fields are as follows: 1 = Disk
Group 2 = Reserved
of the Disk Group identified in the handle field has changed. The old_attr.type
and new_attr.type fields contain the value 1. The old_attr.value.u32[0] field
contains the old number of physical disk drives available for use. The
new_attr.value.u32[0] field contains the new number of physical disk drives
available for use.
Derived Unit identified in the handle field has changed. The secondary_id field
contains the noid portion of the handle for the Storage System Virtual Disk
associated with the Derived Unit. 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
Protected state. The new_attr.value.u32[0] field contains the new Write Protected
state. The Write Protected state values that may be found in the
old_attr.value.u32[0] and new_attr.value.u32[0] fields are as follows: 0 = Write
protect off 1 = Write protect on This Derived Unit is associated with the Virtual
Disk identified in the add_handle field.
in the handle field has experienced numerous communication failures on a
particular Fibre Channel port.
2504880309c869c8Storage Cell: %1 Event Code: %2 Description: The Data Availability state of the
2505880309c969c9Storage Cell: %1 Event Code: %2 Description: The state of the Disk Group
Event
Code
Severity
SWC IDEvt.
No.
Description
in the handle field received a request to shutdown. The old_attr.type field and the
new_attr.type fields 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.
in the handle field has completed its shutdown preparations. The old_attr.type
field and the new_attr.type fields 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 <P > 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.
internal Logical Disk associated with the Virtual Disk identified in the handle field
has has transitioned to the DATA LOST state. The value.ul1 field contains the new
state: 1 (DATA LOST). The value.ul2 field contains the old state: 0 (NORMAL).
identified in the handle field has transitioned to an INOPERATIVE state. The
value.ul1 field contains the new Disk Group state. The value.ul2 field contains the
old Disk Group state. The state values that may be found in the value.ul1 and
value.ul2 fields are as follows: 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
Disk associated with the Virtual Disk identified in the handle field has transitioned
to the FAILED state. The value.ul1 field contains the new state: 5 (FAILED). The
value.ul2 field contains the old state. The state values that may be found in the
value.ul2 field are as follows: 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
Disk associated with the Virtual Disk identified in the handle field has transitioned
to the SNAPSHOT OVERCOMMIT state. The value.ul1 field contains the new
state: 7 (SNAPSHOT OVERCOMMIT). The value.ul2 field contains the old state.
The state values that may be found in the value.ul2 field are as follows: 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
Disk associated with the Virtual Disk identified in the handle field has transitioned
to the DEVICE DATA LOST state. The value.ul1 field contains the new state: 10
(DEVICE DATA LOST). The value.ul2 field contains the old state. The state values
that may be found in the value.ul2 field are as follows: 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
port identified in the attribute.value.str field and located on the rear panel of the
HSV110 controller identified in the handle field has transitioned to the FAILED
state. The attribute.type field contains the value 4. The value.ul1 field contains
the new state: 2 (FAILED). The value.ul2 field contains the old state: 1
(NORMAL). Note that the HSV110 controller’s internal identity of the affected
Fibre Channel port is contained in the secondary_id field.
identified in the handle field has transitioned to an INOPERATIVE MARKED state.
The value.ul1 field contains the new Disk Group state. The value.ul2 field
contains the old Disk Group state. The state values that may be found in the
value.ul1 and value.ul2 fields are as follows: 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
Drive identified in the handle field has transitioned to the NOT PRESENT state.
The value.ul1 field contains the new state: 4 (NOT PRESENT). The value.ul2 field
contains the old state. The state values that may be in the value.ul2 field are as
follows: 1 = Normal 2 = Degraded 3 = Failed
307988030c076c7Storage Cell: %1 Event Code: %2 Description: A full copy terminated prior to
308088030c086c8Storage Cell: %1 Event Code: %2 Description: A full copy terminated prior to
308188030c096c9Storage Cell: %1 Event Code: %2 Description: The specified log logical disk has
Event
Code
Severity
SWC IDEvt.
No.
Description
in the handle field needs attention.
blower assembly located within the HSV110 controller identified in the handle
field has transitioned from the PRESENT to NOT PRESENT state indicating that
the blower has been removed. The secondary_id field contains the ‘1’ blower
assembly internal identifier value: 1. The value.ul1 field contains the new state of
the Blower Present flag: 0 (NOT PRESENT). The value.ul2 field contains the old
state of the Blower Present flag: 1 (PRESENT).
by the node_name field has begun a resynchronization operation (i.e., a restart
of the controllers in a manner that has little or no impact on host system
connectivity). The information.pc field contains the program counter of
resynchronization operation initiator. The information.flags field contains reboot
flags value. The information.code field contains the resynchronization operation
event code value.
disk has successfully completed a full copy. The following fields are not valid:
status, blocks, vda.
has transitioned to the logging state, because the alternate site is not accessible
or the DRM group is suspended. The following fields are not valid: status, blocks,
vda, port, side.
has transitioned to the logging state, because the destination virtual disk is not
accessible. The following fields are not valid: status, blocks, vda, port, side.
has been forced inoperative due to a failsafe locked condition. Either the
destination is not accessible or a member virtual disk in the group has gone
inoperative. The following fields are not valid: status, blocks, vda, port, side.
has been forced inoperative due to a failsafe locked condition. Either the
destination is not accessible or a member virtual disk in the group has gone
inoperative. The following fields are not valid: status, blocks, vda, port, side.
occurred on the specified source virtual disk during the full copy. The virtual disk
address (vda) specified indicates the first block in error. The full copy was
terminated.
completion. A remote copy error occurred, due to an inaccessible alternate site.
The virtual disk address specified indicates the first block in error. The full copy
will continue when the destination is restored.
completion. A remote copy error occurred, due to an inaccessible destination
virtual disk. The virtual disk address specified indicates the first block in error.
The full copy will continue when the destination is restored.
been reset due to insufficient storage space. The destination has been marked
for a full copy. The following fields are not valid: status, blocks, vda, port, side.
332988030d016d1Storage Cell: %1 Event Code: %2 Description: A physical disk drive that is not
333088030d023d2Storage Cell: %1 Event Code: %2 Description: A physical disk drive is
333188030d033d3Storage Cell: %1 Event Code: %2 Description: A physical disk drive was
Event
Code
Severity
SWC IDEvt.
No.
Description
been reset due to site failover. The following fields are not valid: status, blocks,
vda.
disk has successfully completed a merge. The following fields are not valid:
status, blocks, vda.
longer failsafe locked. The following fields are not valid: status, blocks, vda, port,
side.
disk has been marked for a full copy. The following fields are not valid: status,
blocks, vda.
site failover has taken place. This group is transitioning from a source role to a
destination role. The following fields are not valid: status, blocks, vda.
site failover has taken place. This group is transitioning from a destination role to
a source role. The following fields are not valid: status, blocks, vda.
group was not found. The destination group appears to have been deleted by
the user after a site failover, therefore this dangling DRM source group should
likewise be deleted.
a Drive Enclosure Environmental Monitoring Unit. The event was reported by the
Drive Enclosure Environmental Monitoring Unit located in the drive enclosure
identified in the dencl_num field within the rack identified in the rack_num field.
The rack_num field will not be valid until a future release. The content of the
alarm_error_code field could not be translated into a known event.
Fibre Channel compatible or cannot operate at the link rate established by the
drive enclosure I/O modules was detected. This problem was detected by the
Drive Enclosure Environmental Monitoring Unit located in the drive enclosure
identified in the dencl_num field within the rack identified in the rack_num field
during spin up of the physical disk drive installed in the drive enclosure bay
identified in the alarm_error_code.field.en field. The rack_num field will not be
valid until a future release.
improperly installed or missing. This could affect the drive enclosure air flow and
cause an over temperature condition. This problem was detected by the Drive
Enclosure Environmental Monitoring Unit located in the drive enclosure identified
in the dencl_num field within the rack identified in the rack_num field. The
rack_num field will not be valid until a future release. The affected drive enclosure
bay is identified in the alarm_error_code.field.en field.
removed while software-activated drive locking was enabled on a drive enclosure
that does not support drive locking. This problem was detected by the Drive
Enclosure Environmental Monitoring Unit located in the drive enclosure identified
in the dencl_num field within the rack identified in the rack_num field. The
rack_num field will not be valid until a future release. The affected drive enclosure
bay is identified in the alarm_error_code.field.en field.
Table 8: HSV Element Manager Event Codes: Controller Events (Continued)
Event
ID
333288030d046d4Storage Cell: %1 Event Code: %2 Description: A physical disk drive that is
337988030d333d33Storage Cell: %1 Event Code: %2 Description: The AC input to a drive enclosure
338088030d346d34Storage Cell: %1 Event Code: %2 Description: A drive enclosure power supply is
338188030d356d35Storage Cell: %1 Event Code: %2 Description: A drive enclosure power supply
Event
Code
Severity
SWC IDEvt.
No.
Description
capable of operating at the loop link rate established by the drive enclosure I/O
module was found to be running at a different rate. This problem was detected
by the Drive Enclosure Environmental Monitoring Unit located in the drive
enclosure identified in the dencl_num field within the rack identified in the
rack_num field. The rack_num field will not be valid until a future release. The
affected physical disk drive is installed in the drive enclosure bay identified in the
alarm_error_code.field.en field. The Fibre Channel loop on which the problem
was detected is identified by the content of the alarm_error_code.field.ec field as
follows: 4 = loop A 5 = loop B
power supply has been lost. This makes the remaining power supply a single
point of failure. This problem was detected by the Drive Enclosure Environmental
Monitoring Unit located in the drive enclosure identified in the dencl_num field
within the rack identified in the rack_num field. The rack_num field will not be
valid until a future release. The location of the affected power supply (1 or 2) is
identified in the alarm_error_code.field.en field.
improperly installed or missing. This could affect the drive enclosure air flow and
cause an over temperature condition. The operational power supply will
automatically shut down after a short period of time, thereby disabling the drive
enclosure. This condition remains active until either the problem is corrected, or
the operational power supply shuts down, whichever occurs first. This problem
was detected by the Drive Enclosure Environmental Monitoring Unit located in the
drive enclosure identified in the dencl_num field within the rack identified in the
rack_num field. The rack_num field will not be valid until a future release. The
location of the affected power supply (1 or 2) is identified in the
alarm_error_code.field.en field.
component has failed. This problem was detected by the Drive Enclosure
Environmental Monitoring Unit located in the drive enclosure identified in the
dencl_num field within the rack identified in the rack_num field. The rack_num
field will not be valid until a future release. The location of the affected power
supply (1 or 2) is identified in the alarm_error_code.field.en field.
Table 8: HSV Element Manager Event Codes: Controller Events (Continued)
HSV Element Manager Event Codes
Event
ID
339988030d476d47Storage Cell: %1 Event Code: %2 Description: A drive enclosure blower is not
340388030d4b6d4bStorage Cell: %1 Event Code: %2 Description: A drive enclosure blower is
340488030d4c6d4cStorage Cell: %1 Event Code: %2 Description: Both drive enclosure blowers are
Event
Code
Severity
SWC IDEvt.
No.
Description
operating properly. This could affect the drive enclosure air flow and cause an
over temperature condition. This problem was detected by the Drive Enclosure
Environmental Monitoring Unit located in the drive enclosure identified in the
dencl_num field within the rack identified in the rack_num field.The rack_num
field will not be valid until a future release. The location of the affected blower (1
or 2) is identified in the alarm_error_code.field.en field. The cause of the
improper operation is described by the content of the alarm_error_code.field.ec
field as follows: 1 = The blower is operating at a speed that is outside of the Drive
Enclosure Environmental Monitoring Unit specified range, possibly because of a
bearing problem. 2 = The blower is operating at a speed that is significantly
outside of the Drive Enclosure Environmental Monitoring Unit specified range,
possibly because of a bearing problem. 3 = The blower has stopped.
NOTE: The other blower (if operational) now operates at high speed and is a
single point of failure. A single blower operating at high speed can provide
sufficient air flow to cool an enclosure and the elements for up to 100 hours.
However, operating an enclosure at temperatures approaching an overheating
threshold can damage elements and may reduce the MTBF of a specific element.
Compaq therefore recommends immediate replacement of the defective blower.
4 = The power supply reported an internal blower error.
improperly installed or missing. This affects the drive enclosure air flow and can
cause an over temperature condition. This problem was detected by the Drive
Enclosure Environmental Monitoring Unit located in the drive enclosure identified
in the dencl_num field within the rack identified in the rack_num field. The
rack_num field will not be valid until a future release. The location of the affected
blower (1 or 2) is identified in the alarm_error_code.field.en field.
missing. This severely affects the drive enclosure air flow and can cause an over
temperature condition. The operational power supply(s) will automatically shut
down after a short period of time, thereby disabling the drive enclosure. This
condition remains active until either the problem is corrected, or the operational
power supply(s) shut down, whichever occurs first. This problem was detected by
the Drive Enclosure Environmental Monitoring Unit located in the drive enclosure
identified in the dencl_num field within the rack identified in the rack_num field.
The rack_num field will not be valid until a future release. Note that this event is
preceded by a ‘drive enclosure blower is improperly installed or missing’ event
that identifies the location of the first missing blower. The location of the second
missing blower (1 or 2) is identified in the alarm_error_code.field.en field of this
event.
sensor out of range condition has been reported by one of the drive enclosure
elements. This problem was detected by the Drive Enclosure Environmental
Monitoring Unit located in the drive enclosure identified in the dencl_num field
within the rack identified in the rack_num field. The rack_num field will not be
valid until a future release. The location of the temperature sensor (1 through 11)
is identified in the alarm_error_code.field.en field as follows: 1 = Power Supply 1
Exhaust 2 = Power Supply 2 Exhaust 3 = Drive Enclosure Environmental
Monitoring Unit 4 = Drive Bay 1 5 = Drive Bay 2 6 = Drive Bay 3 7 = Drive
Bay 4 8 = Drive Bay 5 9 = Drive Bay 6 A = Drive Bay 7 B = Drive Bay 8 C =
Drive Bay 9 D = Drive Bay 10 E = Drive Bay 11 F = Drive Bay 12 10 = Drive
Bay 13 11 = Drive Bay 14 The temperature sensor out of range condition is
described by the content of the alarm_error_code.fie ld.ec field as follows: 1 =
The element temperature is approaching, but has not reached, the high
temperature CRITICAL threshold. Continued operation under these conditions
may result in a CRITICAL condition and may reduce an element’s MTBF. 2 = The
element temperature is above the high temperature CRITICAL threshold.
Continued operation under these conditions may result in element failure. 3 =
The element temperature is approaching, but has not reached, the low
temperature CRITICAL threshold. Continued operation under these conditions
may result in a CRITICAL condition and may reduce an element’s MTBF. 4 = The
element temperature has reached the low temperature CRITICAL threshold.
Continued operation under these conditions may result in element failure. The
actual temperature threshold values can be found in the HSV element manager
GUI.
of the three temperature sensor groups (i.e., Drive Enclosure Environmental
Monitoring Unit, Disk Drives, and Power Supplies) exceeds the CRITICAL level.
The operational power supply(s) will automatically shut down after a short period
of time, thereby disabling the drive enclosure. This condition remains active until
either the problem is corrected, or the operational power supply(s) shut down,
whichever occurs first. This problem was detected by the Drive Enclosure
Environmental Monitoring Unit located in the drive enclosure identified in the
dencl_num field within the rack identified in the rack_num field. The rack_num
field will not be valid until a future release. Note that in this case the content of
the alarm_error_code.field.en field is undefined. The actual temperature
threshold values can be found in the HSV element manager GUI.
Environmental Monitoring Unit error has occurred. This problem was detected by
the Drive Enclosure Environmental Monitoring Unit located in the drive enclosure
identified in the dencl_num field within the rack identified in the rack_num field.
The rack_num field will not be valid until a future release. The
alarm_error_code.field.en field contains the value 1 signifying that the Drive
Enclosure Environmental Monitoring Unit is the affected element. The cause of
the improper operation is described by the content of the
alarm_error_code.field.ec field as follows: 1 = An internal Drive Enclosure
Environmental Monitoring Unit clock error has occurred. 2 = The Inter-IC (I2C)
bus is not processing data and the Drive Enclosure Environmental Monitoring
Unit is unable to monitor or report the status of the elements or enclosures. 5 = A
Backplane NVRAM error has occurred.
345888030d823d82Storage Cell: %1 Event Code: %2 Description: A drive enclosure’s address is
Event
Code
Severity
SWC IDEvt.
No.
Description
Environmental Monitoring Unit error has occurred. This problem was detected by
the Drive Enclosure Environmental Monitoring Unit located in the drive enclosure
identified in the dencl_num field within the rack identified in the rack_num field.
The rack_num field will not be valid until a future release. The
alarm_error_code.field.en field contains the value 1 signifying that the Drive
Enclosure Environmental Monitoring Unit is the affected element. The cause of
the improper operation is described by the content of the
alarm_error_code.field.ec field as follows: 3 = A drive enclosure power supply
was shut down. 16 = The Drive Enclosure Environmental Monitoring Unit ESI data
has been corrupted.
Monitoring Unit is unable to collect data for the SCSI-3 Engineering Services
(SES) page. This problem was detected by the Drive Enclosure Environmental
Monitoring Unit located in the drive enclosure identified in the dencl_num field
within the rack identified in the rack_num field. The rack_num field will not be
valid until a future release. The alarm_error_code.field.en field contains the value
1 signifying that the Drive Enclosure Environmental Monitoring Unit is the
affected element.
Drive Enclosure Environmental Monitoring Unit NVRAM. This problem was
detected by the Drive Enclosure Environmental Monitoring Unit located in the
drive enclosure identified in the dencl_num field within the rack identified in the
rack_num field. The rack_num field will not be valid until a future release. The
alarm_error_code.field.en field contains the value 1 signifying that the Drive
Enclosure Environmental Monitoring Unit is the affected element.
Environmental Monitoring Unit error has occurred. This problem was detected by
the Drive Enclosure Environmental Monitoring Unit located in the drive enclosure
identified in the dencl_num field within the rack identified in the rack_num field.
The rack_num field will not be valid until a future release. The
alarm_error_code.field.en field contains the value 1 signifying that the Drive
Enclosure Environmental Monitoring Unit is the affected element. The cause of
the improper operation is described by the content of the
alarm_error_code.field.ec field as follows: 11 = The Drive Enclosure
Environmental Monitoring Unit cannot write data to the NVRAM. 12 = The Drive
Enclosure Environmental Monitoring Unit cannot read data from the NVRAM. 13
= The Field Programmable Gate Array (FPGA) that controls the ESI bus failed to
load information required for Drive Enclosure Environmental Monitoring Unit
operation.
incorrect or the enclosure has no address. This problem was detected by the
Drive Enclosure Environmental Monitoring Unit located in the drive enclosure
identified in the dencl_num field within the rack identified in the rack_num field.
The rack_num field will not be valid until a future release. The
alarm_error_code.field.en field contains the value 1 signifying that the Drive
Enclosure Environmental Monitoring Unit is the affected element.
348988030da16da1Storage Cell: %1 Event Code: %2 Description: A drive enclosure power supply
Event
Code
Severity
SWC IDEvt.
No.
Description
Monitoring Unit has experienced a hardware failure. This problem was detected
by the Drive Enclosure Environmental Monitoring Unit located in the drive
enclosure identified in the dencl_num field within the rack identified in the
rack_num field. The rack_num field will not be valid until a future release. The
alarm_error_code.field.en field contains the value 1 signifying that the Drive
Enclosure Environmental Monitoring Unit is the affected element.
failed to respond to a shut down command. This problem was detected by the
Drive Enclosure Environmental Monitoring Unit located in the drive enclosure
identified in the dencl_num field within the rack identified in the rack_num field.
The rack_num field will not be valid until a future release. The
alarm_error_code.field.en field contains the value 1 signifying that the Drive
Enclosure Environmental Monitoring Unit is the affected element.
error has been detected. This problem was detected by the Drive Enclosure
Environmental Monitoring Unit located in the drive enclosure identified in the
dencl_num field within the rack identified in the rack_num field. The rack_num
field will not be valid until a future release. The location of the transceiver (1
through 4) is identified in the alarm_error_code.field.en field as follows: 1 =
Transceiver 01 2 = Transceiver 02 3 = Transceiver 03 4 = Transceiver 04 The
transceiver error condition is described by the content of the
alarm_error_code.field.ec field as follows: 1 = The transceivers on this link are
not the same type or they are incompatible with the drive enclosure I/O module.
This error prevents the controller from establishing a link with the enclosure drives
and eliminates the enclosure dual-loop capability. 2 = The transceiver can no
longer detect a data signal. This error prevents the controller from transferring
data on a loop and eliminates the enclosure dual-loop capability. 3 = The
system has detected an FC-AL bus fault involving a transceiver. This error prevents
the controller from transferring data on a loop and eliminates the enclosure
dual-loop capability.
voltage sensor out of range condition has been reported. This problem was
detected by the Drive Enclosure Environmental Monitoring Unit located in the
drive enclosure identified in the dencl_num field within the rack identified in the
rack_num field. The rack_num field will not be valid until a future release. The
location of the voltage sensor (1 through 4) is identified in the
alarm_error_code.field.en field as follows: 1 = Power Supply 1 +5 VDC 2 =
Power Supply 1 +12 VDC 3 = Power Supply 2 +5 VDC 4 = Power Supply 2 +12
VDC The voltage sensor out of range condition is described by the content of the
alarm_error_code.field.ec field as follows: 1 = The element voltage is
approaching, but has not reached, the high voltage CRITICAL threshold.
Continued operation under these conditions may result in a CRITICAL condition.
2 = The element voltage is above the high voltage CRITICAL threshold. 3 = The
element voltage is approaching, but h as not reached, the low voltage CRITICAL
threshold. Continued operation under these conditions may result in a CRITICAL
condition. 4 = The element voltage has reached the low voltage CRITICAL
threshold.
355088030dde3ddeStorage Cell: %1 Event Code: %2 Description: A drive enclosure I/O module is
Event
Code
Severity
SWC IDEvt.
No.
Description
current sensor out of range condition has been reported. This problem was
detected by the Drive Enclosure Environmental Monitoring Unit located in the
drive enclosure identified in the dencl_num field within the rack identified in the
rack_num field. The rack_num field will not be valid until a future release. The
location of the current sensor (1 through 4) is identified in the
alarm_error_code.field.en field as follows: 1 = Power Supply 1 +5 VDC 2 =
Power Supply 1 +12 VDC 3 = Power Supply 2 +5 VDC 4 = Power Supply 2 +12
VDC The current sensor out of range condition is described by the content of the
alarm_error_code.field.ec field as follows: 1 = The element current is
approaching, but has not reached, the high current CRITICAL threshold.
Continued operation under these conditions may result in a CRITICAL condition.
2 = The element current is above the high current CRITICAL threshold.
invalid NVRAM read error has occurred. This problem was detected by the Drive
Enclosure Environmental Monitoring Unit located in the drive enclosure identified
in the dencl_num field within the rack identified in the rack_num field. The
rack_num field will not be valid until a future release. The
alarm_error_code.field.en field contains the value 1 signifying that the drive
enclosure is the affected element.
error has occurred. This problem was detected by the Drive Enclosure
Environmental Monitoring Unit located in the drive enclosure identified in the
dencl_num field within the rack identified in the rack_num field. The rack_num
field will not be valid until a future release. The alarm_error_code.field.en field
contains the value 1 signifying that the drive enclosure is the affected element.
The cause of the improper operation is described by the content of the
alarm_error_code.field.ec field as follows: 11 = Unable to write data to the
NVRAM. This problem prevents communication between elements in the
enclosure. 12 = Unable to read data from the NVRAM. This problem prevents
communication between elements in the enclosure. 13 = NVRAM has not been
initialized properly. This is a manufacturing error.
error has occurred. This problem was detected by the Drive Enclosure
Environmental Monitoring Unit located in the drive enclosure identified in the
dencl_num field within the rack identified in the rack_num field. The rack_num
field will not be valid until a future release. The location of the I/O module (A
(01) and B (02)) is identified in the alarm_error_code.field.en field. The cause of
the improper operation is described by the content of the
alarm_error_code.field.ec field as follows: 1 = The I/O module’s Fibre Channel
link speed is not supported by the backplane. This error prevents the controller
from establishing a link with enclosure drives and eliminates the enclosure
dual-loop capability. 11 = Unable to write data to the I/O module NVRAM. 12
= Unable to read data from the I/O module NVRAM.
unable to communicate with the Drive Enclosure Environmental Monitoring Unit.
This problem was detected by the Drive Enclosure Environmental Monitoring Unit
located in the drive enclosure identified in the dencl_num field within the rack
identified in the rack_num field. The rack_num field will not be valid until a future
release. The location of the I/O module (A (01) and B (02)) is identified in the
alarm_error_code.field.en field.
16899880342032423Storage Cell: %1 Event Code: %2 Description: An excessive number of link
16900880342043424Storage Cell: %1 Event Code: %2 Description: A Fibre Channel port on the
33536880383006830Storage Cell: %1 Event Code: %2 Description: A failure was detected during the
Event
Code
Severity
SWC IDEvt.
No.
Description
invalid NVRAM read error has occurred. This problem was detected by the Drive
Enclosure Environmental Monitoring Unit located in the drive enclosure identified
in the dencl_num field within the rack identified in the rack_num field. The
rack_num field will not be valid until a future release. The location of the I/O
module (A (01) or B (02)) is identified in the alarm_error_code.field.en field.
more of the drive enclosures. This is an informational event triggered by the
occurrence of a change in the status of a drive enclosure. The content of the
alarm_error_code field, drive enclosure, and rack number have no meaning for
this event.
port transitioned to link down.
port transitioned to link failed.
errors were detected on a Fibre Channel port. The error counters are checked
every hour. This is an informational event that reports all link status errors
detected by the Tachyon chip, triggered by an excessive number detected in one
category.
HSV110 controller has failed to respond. The evt_peq.peb field contains port
event information. The evt_peq.peq_frz_prod_index field contains the index to
the port event block that points to when the Tachyon chip entered the frozen state.
The evt_peq.peq_prod_index field contains the index to the next port event block.
The evt_peq.peq_cons_index field contains the index to the next port event block
to be acted upon.
execution of this HSV110 controller’s on board diagnostics.
Table 9 shows events generated by the HSV Management Agent, which are logged in the
Storage Management Appliance Event Log. The Event Number (Evt. No.) codes can be used
to correlate events recorded in the Management Agent Event Log of the HSV Element
Manager with the events logged in the Storage Management Appliance Event Log.
Table 9: HSV Element Manager Event Codes: Management Agent Events
210138803521521013Storage Cell: %1 Volume Quorum Disk change Event Code: %2 Description: %3
210148803521621014Storage Cell: %1 The state of an object in the system has changed. View adjacent events
22003880355f332003Storage Cell: %1 Invalid name specified for storage system Event Code: %2
22004880355f422004Storage Cell: %1 Storage system is not initialized Event Code: %2 Description: %3
22005880355f532005Storage Cell: %1 Duplicate name for virtual disk found Event Code: %2 Description:
22006880355f632006Storage Cell: %1 Invalid name specified for virtual disk Event Code: %2 Description:
22007880355f732007Storage Cell: %1 Virtual disk name exceeds maximum length Event Code: %2
22008880355f832008Storage Cell: %1 Invalid parameter specified for virtual disk Event Code: %2
22009880355f932009Storage Cell: %1 No virtual disk found Event Code: %2 Description: %3
22010880355fa32010Storage Cell: %1 Specified virtual disk size exceeds available size Event Code: %2
22011880355fb22011Storage Cell: %1 There are not enough disk drives to create a disk group Event Code:
22012880355fc32012Storage Cell: %1 Specified number of device exceeds available number of disk Event
22013880355fd32013Storage Cell: %1 Specified number of device is below the minimum number of disk to
22014880355fe32014Storage Cell: %1 No available volumes to complete the request Event Code: %2
220538803562522053Storage Cell: %1 Comments exceed maximum size Event Code: %2 Description: %3
220578803562922057Storage Cell: %1 Completed disk group creation Event Code: %2 Description: %3
220588803562a22058Storage Cell: %1 Added host port Event Code: %2 Description: %3
220598803562b22059Storage Cell: %1 Discarded host port Event Code: %2 Description: %3
220608803562c22060Storage Cell: %1 EMU/Shelf code load complete Event Code: %2 Description: %3
220618803562d22061Storage Cell: %1 Operation will exceed the available capacity of the disk group Event
220628803562e22062Storage Cell: %1 Controller(s) code load complete Event Code: %2 Description: %3
220638803562f22063Storage Cell: %1 The target device is not in the right condition to perform the operation
220658803563122065Storage Cell: %1 Maximum number of disk groups exceeded Event Code: %2
220668803563232066Storage Cell: %1 Nsa object discard failed. Event Code: %2 Description: %3
220678803563332067Storage Cell: %1 There are not enough disks to meet the minimum number requirement
220688803563422068Storage Cell: %1 Entry added successfully in the password file Event Code: %2
2305988035a1333059Storage Cell: %1 EM: Parse file is empty Event Code: %2 Description: %3
2306088035a1463060Storage Cell: %1 Storage system being shutdown due to a command failure. Event
2306188035a1523061Storage Cell: %1 EM: Could not retrieve a storage system event Event Code: %2
2306288035a1623062Storage Cell: %1 EM: Init SC Event config list failed Event Code: %2 Description: %3
2306388035a1733063Storage Cell: %1 Could not initialize Comm infrastructure for event logging to system log
2306488035a1863064Storage Cell: %1 EM: Storage system pointer is NULL! Event Code: %2 Description: %3
2306588035a1963065Storage Cell: %1 EM: Failed to log event to the Appliance event log: check if log is full
2308088035a2863080Storage Cell: %1 SC Event Log has been cleared and restarted. Possible RAID1
2308188035a2923081Storage Cell: %1 Invalid logType parameter Event Code: %2 Description: %3
2308288035a2a23082Storage Cell: %1 Unsupported version Event Code: %2 Description: %3
2308388035a2b23083Storage Cell: %1 Log file is empty Event Code: %2 Description: %3
2308488035a2c23084Storage Cell: %1 Storage System with this WWN is not visible to this agent or the
2308588035a2d63085Storage Cell: %1 Pointer to Event Manager is NULL Event Code: %2 Description: %3
2308688035a2e23086Storage Cell: %1 Parsefile for current firmware version not found. Upload correct parse
2404588035ded24045Storage Cell: %1 Unable to store Event Log and free Lock Event Code: %2 Description:
2404688035dee24046Storage Cell: %1 Unable to read Event Log and free Lock Event Code: %2 Description:
2404788035def24047Storage Cell: %1 Previously Read Object Properties do not Match Event Code: %2
2404888035df024048Storage Cell: %1 Previously Read Object Properties do not Match Event Code: %2
2404988035df124049Storage Cell: %1 Unable to read Notification Host List Event Code: %2 Description:
2405088035df224050Storage Cell: %1 Unable to store Notification Host List Event Code: %2 Description: %3
2405188035df324051Storage Cell: %1 Unable to store Notification Host List and free Lock Event Code: %2
2405288035df424052Storage Cell: %1 Unable to read Event Configuration List Event Code: %2 Description:
2405388035df524053Storage Cell: %1 Unable to store Event Configuration List Event Code: %2 Description:
2405488035df624054Storage Cell: %1 Unable to store Event Configuration List and free Lock Event Code: %2
260078803659726007Storage Cell: %1 Nsc Manager No Physical Stores Found Event Code: %2 Description:
260088803659826008Storage Cell: %1 Nsc Manager No Storage Cell Found Event Code: %2 Description:
260098803659926009Storage Cell: %1 Nsc Manager No disk group Found Event Code: %2 Description: %3
260108803659a26010Storage Cell: %1 Nsc Manager too many disk groups Event Code: %2 Description: %3
260118803659b26011Storage Cell: %1 Nsc Manager No Volumes Found Event Code: %2 Description: %3
2800588036d6528005Storage Cell: %1 Controller not part of storage system configuration Event Code: %2
2800688036d6628006Storage Cell: %1 Failed to uninitialize storage system Event Code: %2 Description: %3
2800788036d6738007Storage Cell: %1 Storage system File Open Error Event Code: %2 Description: %3
2800888036d6838008Storage Cell: %1 Storage system File Write Error Event Code: %2 Description: %3
2800988036d6938009Storage Cell: %1 Storage system File Read Error Event Code: %2 Description: %3
2801088036d6a28010Storage Cell: %1 Name too long Event Code: %2 Description: %3
2801188036d6b28011Storage Cell: %1 No String Error Event Code: %2 Description: %3
2801288036d6c28012Storage Cell: %1 No MLD Handle Found Event Code: %2 Description: %3
2801388036d6d28013Storage Cell: %1 No Controllers Found Event Code: %2 Description: %3
2801488036d6e28014Storage Cell: %1 Controller Not Found On Loop Event Code: %2 Description: %3
2801588036d6f28015Storage Cell: %1 No Disk Groups Found Event Code: %2 Description: %3
2801688036d7028016Storage Cell: %1 No Volumes Found Event Code: %2 Description: %3
2801788036d7128017Storage Cell: %1 No Physical Stores Found Event Code: %2 Description: %3
2801888036d7228018Storage Cell: %1 No Virtual Disks Found Event Code: %2 Description: %3
2801988036d7328019Storage Cell: %1 No Hosts Found Event Code: %2 Description: %3
2802088036d7428020Storage Cell: %1 Name already exists Event Code: %2 Description: %3
2802188036d7528021Storage Cell: %1 Folder is not empty Event Code: %2 Description: %3
2802288036d7628022Storage Cell: %1 Spares goal could not be met Event Code: %2 Description: %3
2802388036d7728023Storage Cell: %1 Storage system object found Event Code: %2 Description: %3
2802488036d7828024Storage Cell: %1 Storage system object not found Event Code: %2 Description: %3
2802588036d7928025Storage Cell: %1 New Physical Store Detected But Not Found In Physical Store List Event
2806788036da338067Storage Cell: %1 Get Host Count Failed Event Code: %2 Description: %3
2806888036da438068Storage Cell: %1 Get Presented Unit List Failed Event Code: %2 Description: %3
2806988036da538069Storage Cell: %1 Get Presented Unit Count Failed Event Code: %2 Description: %3
2807088036da638070Storage Cell: %1 Free View Failed Event Code: %2 Description: %3
2807188036da738071Storage Cell: %1 Storage system shutdown Failed Event Code: %2 Description: %3
2807288036da838072Storage Cell: %1 StorageCell Virtual Disk Count Does Not Match Logical Disk Count
2807388036da938073Storage Cell: %1 Get Derived Unit List Failed Event Code: %2 Description: %3
2807488036daa38074Storage Cell: %1 Get Derived Unit Count Failed Event Code: %2 Description: %3
2807588036dab38075Storage Cell: %1 Get StorageCell Virtual Disk List Failed Event Code: %2 Description:
2807688036dac38076Storage Cell: %1 Get StorageCell Virtual Disk Count Failed Event Code: %2
2807788036dad38077Storage Cell: %1 Error while building virtual disk root view Event Code: %2
2807888036dae38078Storage Cell: %1 Error while building host root view Event Code: %2 Description: %3
2807988036daf38079Storage Cell: %1 Error while uilding disk group root view Event Code: %2 Description:
2808088036db038080Storage Cell: %1 Error while building hardware root view Event Code: %2 Description:
2808188036db138081Storage Cell: %1 Specified time format is incorrect Event Code: %2 Description: %3
2808288036db238082Storage Cell: %1 Error creating/opening time syncronization file. Event Code: %2
2808388036db338083Storage Cell: %1 StorageCell NscList Reordered. Event Code: %2 Description: %3
2808488036db438084Storage Cell: %1 StorageCell NscList Mutex Get Error Event Code: %2 Description: %3
290018803714939001Storage Cell: %1 Virtual disk File Open Error Event Code: %2 Description: %3
290028803714a39002Storage Cell: %1 Virtual disk File Write Error Event Code: %2 Description: %3
290038803714b39003Storage Cell: %1 Virtual disk File Read Error Event Code: %2 Description: %3
290048803714c29004Storage Cell: %1 Virtual disk name too long Event Code: %2 Description: %3
290058803714d29005Storage Cell: %1 Virtual disk No String Error Event Code: %2 Description: %3
290068803714e29006Storage Cell: %1 Virtual disk No Object Error Event Code: %2 Description: %3
290078803714f29007Storage Cell: %1 Virtual disk still exists Event Code: %2 Description: %3
290088803715029008Storage Cell: %1 Virtual disk Invalid Value Event Code: %2 Description: %3
290098803715129009Storage Cell: %1 An outstanding command is still in progress for the virtual disk Event
290108803715229010Storage Cell: %1 Requested virtual disk size exceeds the available size Event Code: %2
290118803715329011Storage Cell: %1 Virtual disk size may be expanded but not reduced Event Code: %2
290128803715429012Storage Cell: %1 Operation on a fast virtual disk deletion completed Event Code: %2
290138803715529013Storage Cell: %1 Operation on a fast virtual disk creation completed Event Code: %2
290148803715629014Storage Cell: %1 Operation on a fast virtual disk size expansion completed Event
290158803715729015Storage Cell: %1 Virtual disk cache data lost error Event Code: %2 Description: %3
290168803715829016Storage Cell: %1 Virtual disk data lost error resolved Event Code: %2 Description: %3
290178803715929017Storage Cell: %1 Operation rejected - The virtual disk has a sharing relationship with
290188803715a29018Storage Cell: %1 Operation on this virtual disk was rejected due to the unit’s not normal
290198803715b29019Storage Cell: %1 Operation on this virtual disk could only be performed if unit is
290208803715c29020Storage Cell: %1 Cache policies cannot be modified if unit is presented to a host Event
290228803715e29022Storage Cell: %1 Requested redundancy type cannot be implemented with the current
290238803715f29023Storage Cell: %1 Your unit was created but cannot be presented at this time. Continue to
290248803716029024Storage Cell: %1 Operation would exceed the maximum allowable presented units.
290258803716129025Storage Cell: %1 Virtual Disk Device Data Lost Error Event Code: %2 Description: %3
290268803716229026Storage Cell: %1 The Most Significant Hex Character in a World Wide LUN Name must
290278803716329027Storage Cell: %1 Virtual disk cache and inoperative data lost error Event Code: %2
290288803716429028Storage Cell: %1 Virtual disk inoperative data lost error Event Code: %2 Description:
290298803716529029Storage Cell: %1 Virtual disk condition failed because of an inoperative data lost error.
3000188037531210001Storage Cell: %1 Storage Object Broker Ready Event Code: %2 Description: %3
3000288037532310002Storage Cell: %1 Storage Object Startup Failed Event Code: %2 Description: %3
3000388037533210003Storage Cell: %1 Invalid storage system name Event Code: %2 Description: %3
3000488037534210004Storage Cell: %1 Storage system is not Initialized Event Code: %2 Description: %3
3000588037535210005Storage Cell: %1 Failed to set storage system name Event Code: %2 Description: %3
3000688037536610006Storage Cell: %1 SOB Memory Allocation Failure Event Code: %2 Description: %3
3000788037537210007Storage Cell: %1 Failed to find virtual disk from list Event Code: %2 Description: %3
3000888037538210008Storage Cell: %1 Failed to find host from list Event Code: %2 Description: %3
3000988037539210009Storage Cell: %1 The Lun specified for this Host is already in use Event Code: %2
300108803753a210010Storage Cell: %1 Your initialized system must have at least one disk group Event Code:
300118803753b210011Storage Cell: %1 Cannot talk to all available NSCs Event Code: %2 Description: %3
Event
Code
Severity
Evt.
No.
Description
Code: %2 Description: %3
another object Event Code: %2 Description: %3
condition Event Code: %2 Description: %3
presented to a host Event Code: %2 Description: %3
Code: %2 Description: %3
allowed, while virtual disk is presented to a host.) Event Code: %2 Description: %3
disk group condition. Event Code: %2 Description: %3
check your unit and present it later when it is fully allocated. Event Code: %2
Description: %3
34014880384de214014Storage Cell: %1 View Find by Index Failed Event Code: %2 Description: %3
34015880384df214015Storage Cell: %1 View Find by Name Failed Event Code: %2 Description: %3
34016880384e0214016Storage Cell: %1 View Find by WWN Failed Event Code: %2 Description: %3
34017880384e1214017Storage Cell: %1 View Find by Type by Name Failed Event Code: %2 Description: %3
34018880384e2214018Storage Cell: %1 View Find by Name by Type Failed Event Code: %2 Description: %3
35001880388b9215001Storage Cell: %1 Tree View Symbol Not Found Event Code: %2 Description: %3
35002880388ba215002Storage Cell: %1 Tree View Id Symbol Not Found Event Code: %2 Description: %3
35003880388bb215003Storage Cell: %1 Tree Cursor Symbol Not Found Event Code: %2 Description: %3
35004880388bc215004Storage Cell: %1 Tree Cursor Id Symbol Not Found Event Code: %2 Description: %3
35005880388bd215005Storage Cell: %1 Tree Sibling Symbol Not Found Event Code: %2 Description: %3
35006880388be215006Storage Cell: %1 Tree Total Children Symbol Not Found Event Code: %2 Description:
35007880388bf215007Storage Cell: %1 Tree Expansion Symbol Not Found Event Code: %2 Description: %3
35008880388c0215008Storage Cell: %1 Tree Contraction Symbol Not Found Event Code: %2 Description: %3
35009880388c1215009Storage Cell: %1 Tree Invalid Descriptor String Event Code: %2 Description: %3
3600188038ca1216001Storage Cell: %1 Ema Short Status - Reissue Command Event Code: %2 Description:
3600288038ca2216002Storage Cell: %1 Ema EMU Could Not Read ALPA Event Code: %2 Description: %3
3600388038ca3216003Storage Cell: %1 Ema Invalid Request Event Code: %2 Description: %3
3600488038ca4216004Storage Cell: %1 Ema Invalid Handle Set In Request Packet Event Code: %2
3600588038ca5216005Storage Cell: %1 Ema No Pstore At Referenced Location Event Code: %2 Description:
3600688038ca6216006Storage Cell: %1 Ema No Primary EMU Selected Event Code: %2 Description: %3
3600788038ca7216007Storage Cell: %1 Ema Invalid SubEnclosure ID Specified Event Code: %2 Description:
3600888038ca8216008Storage Cell: %1 Ema No Device Found Event Code: %2 Description: %3
3600988038ca9216009Storage Cell: %1 Ema Request Packet Missing Parameter Event Code: %2 Description:
3601088038caa216010Storage Cell: %1 Ema Could Not Find SubEnclosure in Configuration List Event Code:
3601188038cab216011Storage Cell: %1 Ema EMU Alarm Or Status Event Information Event Code: %2
3601288038cac216012Storage Cell: %1 Ema Non-specific error occurred Event Code: %2 Description: %3
3601388038cad216013Storage Cell: %1 Ema Shelf WWN Could Not Be Accessed Through A Drive Event
3601488038cae216014Storage Cell: %1 Ema EMU Failed To Enter Primary Mode Event Code: %2
3601588038caf216015Storage Cell: %1 Ema EMU Failed To Exit Primary Mode Event Code: %2 Description:
3601688038cb0216016Storage Cell: %1 Ema Downloaded File Does Not Contain Valid Fibre Channel Loader
3601788038cb1216017Storage Cell: %1 Ema Downloaded File Format Is Not Recognized [status:2] Event
3601888038cb2216018Storage Cell: %1 Ema Incorrect Firmware In Downloaded File [status:3] Event Code: %2
3601988038cb3216019Storage Cell: %1 Ema Downloaded Loader is Too Large [status:4] Event Code: %2
3602088038cb4216020Storage Cell: %1 Ema Invalid Checksum [status:5] Event Code: %2 Description: %3
3602188038cb5216021Storage Cell: %1 Ema Previous Offset Plus Previous Length Not Equal To Current Offset
3602288038cb6216022Storage Cell: %1 Ema Downloaded Loader Terminated Incorrectly [status:7] Event
3602388038cb7216023Storage Cell: %1 Ema EMU Out Of Memory [status:8] Event Code: %2 Description:
3801888039482218018Storage Cell: %1 Api Unable To Get The Lock Event Code: %2 Description: %3
3801988039483218019Storage Cell: %1 Api Created PresentedUnit Success Event Code: %2 Description: %3
3802288039486218022Storage Cell: %1 Api Create DiskGroup Success Event Code: %2 Description: %3
3802488039488218024Storage Cell: %1 Api Create Folder Success Event Code: %2 Description: %3
3802588039489218025Storage Cell: %1 Api Delete Folder Success Event Code: %2 Description: %3
380288803948c218028Storage Cell: %1 Api Set Folder Success Event Code: %2 Description: %3
3803488039492218034Storage Cell: %1 Api Invalid User Name Or Password Error Event Code: %2
3803688039494218036Storage Cell: %1 Api Delete Presented Unit Success Event Code: %2 Description: %3
3803888039496218038Storage Cell: %1 Api Set Diskgroup Success Event Code: %2
3803988039497218039Storage Cell: %1 Api Set Disk Success Event Code: %2 Description: %3
3804088039498218040Storage Cell: %1 Api Delete Storage Family Success Event Code: %2 Description: %3
3804188039499218041Storage Cell: %1 Api Set Storage Family Success Event Code: %2 Description: %3
380428803949a218042Storage Cell: %1 Api Control Memory Allocation Failure Event Code: %2 Description:
380458803949d218045Storage Cell: %1 Api Element Codeload Success Event Code: %2 Description: %3
380478803949f218047Storage Cell: %1 Api Disk Codeload Success Event Code: %2 Description: %3
38048880394a0218048Storage Cell: %1 Api Monitor Codeload Success Event Code: %2 Description: %3
38049880394a1218049Storage Cell: %1 Api Added Port WwID Success Event Code: %2 Description: %3
38050880394a2218050Storage Cell: %1 Api Set Storage Client Success Event Code: %2 Description: %3
38051880394a3218051Storage Cell: %1 Api Invalid Operation Event Code: %2 Description: %3
38052880394a4218052Storage Cell: %1 Api Deleted Port WwID Success Event Code: %2 Description: %3
38059880394ab218059Storage Cell: %1 Api Set Power Success Event Code: %2 Description: %3
38060880394ac218060Storage Cell: %1 Api Element Is Not Initialized Event Code: %2 Description: %3
38063880394af218063Storage Cell: %1 Api Error trying to delete a disk group Event Code: %2 Description:
38065880394b1218065Storage Cell: %1 Api A storage (virtual disk) operation is in progress. Try again later.
38066880394b2218066Storage Cell: %1 Api The storage (virtual disk) condition is invalid. The storage may be
38067880394b3218067Storage Cell: %1 Api Error calling get virtual disk condition. Virtual disk may be deleted.
38068880394b4218068Storage Cell: %1 Api Invalid initialization of the API. Cannot start monitoring process
38070880394b6218070Storage Cell: %1 Api A command is currently under execution from another API call. Try
38071880394b7218071Storage Cell: %1 Api The server has not completed initialization, cannot process the
38073880394b9218073Storage Cell: %1 Api Removing of disk from disk group successfull Event Code: %2
38074880394ba218074Storage Cell: %1 Api Adding of disk(s) to disk group successfull Event Code: %2
Event
Code
Severity
Evt.
No.
Description
Description: %3
Description: %3
%3
%3
Event Code: %2 Description: %3
in error. Try again later. Event Code: %2 Description: %3
Try again later. Event Code: %2 Description: %3
which limits storage cell actions. Event Code: %2 Description: %3
4001388039c4d620013Storage Cell: %1 License Library runtime error Event Code: %2 Description: %3
4001488039c4e620014Storage Cell: %1 New License Job invocation failed Event Code: %2 Description: %3
4001588039c4f320015Storage Cell: %1 Failed to retrieve Node WWN from storage system Event Code: %2
4001688039c50320016Storage Cell: %1 Failed to retrieve license list from MLD Event Code: %2 Description:
4001788039c51320017Storage Cell: %1 Failed to write license list to MLD Event Code: %2 Description: %3
4001888039c52320018Storage Cell: %1 This license line appears to be invalid Event Code: %2 Description:
Event
Code
Severity
Evt.
No.
Description
Description: %3
%2 Description: %3
not been entered, or there is a system communication failure. Event Code: %2
Description: %3
license key has not been entered, or there is a system communication failure. Event
Code: %2 Description: %3
folder is a root folder and cannot be modified, or it is a disk group folder for which you
should use ‘set group’ command. Event Code: %2 Description: %3
presented. Event Code: %2 Description: %3
system. Please try again later. Event Code: %2 Description: %3