CPQHSV110V3-MIB
- Source file
CPQHSV110V3-MIB- Last revised
- Not declared
Imported Objects
| RFC-1212 | OBJECT-TYPE (no object page) |
| RFC-1215 | TRAP-TYPE (no object page) |
| RFC1155-SMI | enterprises |
| RFC1213-MIB | DisplayString |
Objects (74)
Showing 74 of 74 objects
Object legend
Table
Row
Column
Scalar
Node
Object type
Icons distinguish tables, entry rows, columns, scalars, and structural nodes.
SNMPv2-TCTruthValue
Syntax
Blue badges identify the value syntax. Connected badges read as defining module and convention.
IF-MIBifIndex
Table index
Green identifies an index object; yellow names its module when the index is defined elsewhere.
r/w
deprecated
obsolete
Access and status
r/w means read-write. Grey labels mark definitions retained for compatibility.
OBS ✓
Observium use
The indicator appears only when Observium directly references that object.
ifOperStatus
.1.3.6.1.2.1…
Names and OIDs
Object names link to their detail pages. Hover or focus a linked name or badge for available definition details.
.1.3.6.1.4.1.232 |
||
.1.3.6.1.4.1.232.136 |
||
.1.3.6.1.4.1.232.136.1 |
||
.1.3.6.1.4.1.232.136.1.1 |
||
|
agManufacturer
mandatory
|
.1.3.6.1.4.1.232.136.1.1.1 |
|
|
agMajVersion
mandatory
|
.1.3.6.1.4.1.232.136.1.1.2 |
|
|
agMinVersion
mandatory
|
.1.3.6.1.4.1.232.136.1.1.3 |
|
|
agHostName
mandatory
|
.1.3.6.1.4.1.232.136.1.1.4 |
|
|
agEnterprise
mandatory
|
ObjectIdentifier
|
.1.3.6.1.4.1.232.136.1.1.5 |
|
agDescription
mandatory
|
.1.3.6.1.4.1.232.136.1.1.6 |
|
|
agStatusTable
mandatory
|
.1.3.6.1.4.1.232.136.1.1.7 |
|
|
agentEntry
mandatory
|
.1.3.6.1.4.1.232.136.1.1.7.1 |
|
|
agentEntryIndex
mandatory
|
.1.3.6.1.4.1.232.136.1.1.7.1.1 |
|
|
agentStatus
mandatory
|
Enumeration
|
.1.3.6.1.4.1.232.136.1.1.7.1.2 |
|
agentEventCode
mandatory
|
.1.3.6.1.4.1.232.136.1.1.7.1.3 |
|
|
agentEventLevel
mandatory
|
.1.3.6.1.4.1.232.136.1.1.7.1.4 |
|
|
agentEventTimeDate
mandatory
|
.1.3.6.1.4.1.232.136.1.1.7.1.5 |
|
|
agentEventDescription
mandatory
|
.1.3.6.1.4.1.232.136.1.1.7.1.6 |
|
.1.3.6.1.4.1.232.136.1.2 |
||
|
srvCPU
mandatory
|
.1.3.6.1.4.1.232.136.1.2.1 |
|
|
srvComputerType
mandatory
|
.1.3.6.1.4.1.232.136.1.2.2 |
|
|
srvModel
mandatory
|
.1.3.6.1.4.1.232.136.1.2.3 |
|
|
srvSubModel
mandatory
|
.1.3.6.1.4.1.232.136.1.2.4 |
|
|
srvBiosVersion
mandatory
|
.1.3.6.1.4.1.232.136.1.2.5 |
|
|
srvOS
mandatory
|
.1.3.6.1.4.1.232.136.1.2.6 |
|
|
srvOSMajVersion
mandatory
|
.1.3.6.1.4.1.232.136.1.2.7 |
|
|
srvOSMinVersion
mandatory
|
.1.3.6.1.4.1.232.136.1.2.8 |
|
.1.3.6.1.4.1.232.136.1.3 |
||
.1.3.6.1.4.1.232.136.1.3.1 |
||
|
scellTotal
mandatory
|
.1.3.6.1.4.1.232.136.1.3.1.1 |
|
|
scellStatusTable
mandatory
|
.1.3.6.1.4.1.232.136.1.3.1.2 |
|
|
scellEntry
mandatory
|
.1.3.6.1.4.1.232.136.1.3.1.2.1 |
|
|
scellEntryIndex
mandatory
|
.1.3.6.1.4.1.232.136.1.3.1.2.1.1 |
|
|
scellCAC
mandatory
|
.1.3.6.1.4.1.232.136.1.3.1.2.1.10 |
|
|
scellEIP
mandatory
|
.1.3.6.1.4.1.232.136.1.3.1.2.1.11 |
|
|
scellNameDateTime
mandatory
|
.1.3.6.1.4.1.232.136.1.3.1.2.1.12 |
|
|
scellName
mandatory
|
.1.3.6.1.4.1.232.136.1.3.1.2.1.2 |
|
|
scellUUID
mandatory
|
.1.3.6.1.4.1.232.136.1.3.1.2.1.3 |
|
|
scellStatus
mandatory
|
Enumeration
|
.1.3.6.1.4.1.232.136.1.3.1.2.1.4 |
|
scellEventDescription
mandatory
|
.1.3.6.1.4.1.232.136.1.3.1.2.1.5 |
|
|
scellEventTimeDate
mandatory
|
.1.3.6.1.4.1.232.136.1.3.1.2.1.6 |
|
|
scellEventCode
mandatory
|
.1.3.6.1.4.1.232.136.1.3.1.2.1.7 |
|
|
scellSWComponent
mandatory
|
.1.3.6.1.4.1.232.136.1.3.1.2.1.8 |
|
|
scellECode
mandatory
|
.1.3.6.1.4.1.232.136.1.3.1.2.1.9 |
|
.1.3.6.1.4.1.232.136.1.3.2 |
||
.1.3.6.1.4.1.232.136.1.3.3 |
||
|
hostTotal
mandatory
|
.1.3.6.1.4.1.232.136.1.3.3.1 |
|
|
hostStatusTable
mandatory
|
.1.3.6.1.4.1.232.136.1.3.3.2 |
|
|
hostEntry
mandatory
|
.1.3.6.1.4.1.232.136.1.3.3.2.1 |
|
|
hostEntryIndex
mandatory
|
.1.3.6.1.4.1.232.136.1.3.3.2.1.1 |
|
|
hostName
mandatory
|
.1.3.6.1.4.1.232.136.1.3.3.2.1.2 |
|
|
hostUUID
mandatory
|
.1.3.6.1.4.1.232.136.1.3.3.2.1.3 |
|
|
hostStatus
mandatory
|
Enumeration
|
.1.3.6.1.4.1.232.136.1.3.3.2.1.4 |
.1.3.6.1.4.1.232.136.1.3.4 |
||
|
nscTotal
mandatory
|
.1.3.6.1.4.1.232.136.1.3.4.1 |
|
|
nscStatusTable
mandatory
|
.1.3.6.1.4.1.232.136.1.3.4.2 |
|
|
nscEntry
mandatory
|
.1.3.6.1.4.1.232.136.1.3.4.2.1 |
|
|
nscEntryIndex
mandatory
|
.1.3.6.1.4.1.232.136.1.3.4.2.1.1 |
|
|
nscName
mandatory
|
.1.3.6.1.4.1.232.136.1.3.4.2.1.2 |
|
|
nscUUID
mandatory
|
.1.3.6.1.4.1.232.136.1.3.4.2.1.3 |
|
|
nscStatus
mandatory
|
Enumeration
|
.1.3.6.1.4.1.232.136.1.3.4.2.1.4 |
.1.3.6.1.4.1.232.136.1.3.8 |
||
|
shelfTotal
mandatory
|
.1.3.6.1.4.1.232.136.1.3.8.1 |
|
|
shelfStatusTable
mandatory
|
.1.3.6.1.4.1.232.136.1.3.8.2 |
|
|
shelfEntry
mandatory
|
.1.3.6.1.4.1.232.136.1.3.8.2.1 |
|
|
shelfEntryIndex
mandatory
|
.1.3.6.1.4.1.232.136.1.3.8.2.1.1 |
|
|
shelfStatus
mandatory
|
Enumeration
|
.1.3.6.1.4.1.232.136.1.3.8.2.1.2 |
|
shelfId
mandatory
|
.1.3.6.1.4.1.232.136.1.3.8.2.1.3 |
|
|
shelfElementType
mandatory
|
.1.3.6.1.4.1.232.136.1.3.8.2.1.4 |
|
|
shelfElementNum
mandatory
|
.1.3.6.1.4.1.232.136.1.3.8.2.1.5 |
|
|
shelfErrorCode
mandatory
|
.1.3.6.1.4.1.232.136.1.3.8.2.1.6 |
|
.1.3.6.1.4.1.232.136.1.4 |
||
|
maHSVMibRevMajor
mandatory
|
.1.3.6.1.4.1.232.136.1.4.1 |
|
|
maHSVMibRevMinor
mandatory
|
.1.3.6.1.4.1.232.136.1.4.2 |
Dependencies (7) 4 direct · 3 transitive Show tree and compile order Hide dependency details
Each imported module is resolved in the importing module's source directory first, then through the normal default-variant rules.
Dependency tree
Dependency-first compile order
- RFC-1212rfc
- RFC-1215rfc
- RFC1155-SMIrfc
- SNMPv2-SMIrfc
- SNMPv2-TCrfc
- IANAifType-MIBrfc
- RFC1213-MIBrfc
- CPQHSV110V3-MIBhpselected
Notifications / Traps (1078)
| Name | OID | Description |
|---|---|---|
.1.3.6.1.4.1.232.0.136000001 |
Object Already Exists
|
|
.1.3.6.1.4.1.232.0.136000002 |
Supplied Buffer Too Small
|
|
.1.3.6.1.4.1.232.0.136000003 |
Object Already Assigned
|
|
.1.3.6.1.4.1.232.0.136000004 |
Insufficient Available Data Storage
|
|
.1.3.6.1.4.1.232.0.136000005 |
Internal Error
|
|
.1.3.6.1.4.1.232.0.136000006 |
Invalid status for logical disk
|
|
.1.3.6.1.4.1.232.0.136000007 |
Invalid Class
|
|
.1.3.6.1.4.1.232.0.136000008 |
Invalid Function
|
|
.1.3.6.1.4.1.232.0.136000009 |
Invalid Logical Disk Block State
|
|
.1.3.6.1.4.1.232.0.136000010 |
Invalid Loop Configuration
|
|
.1.3.6.1.4.1.232.0.136000011 |
Invalid Parameter
|
|
.1.3.6.1.4.1.232.0.136000012 |
Invalid Parameter handle
|
|
.1.3.6.1.4.1.232.0.136000013 |
Invalid Parameter Id
|
|
.1.3.6.1.4.1.232.0.136000014 |
Invalid Quorum Configuration
|
|
.1.3.6.1.4.1.232.0.136000015 |
Invalid Target Handle
|
|
.1.3.6.1.4.1.232.0.136000016 |
Invalid Target Id
|
|
.1.3.6.1.4.1.232.0.136000017 |
Invalid Time
|
|
.1.3.6.1.4.1.232.0.136000018 |
Media is Inaccessible
|
|
.1.3.6.1.4.1.232.0.136000019 |
No Fibre Channel Port
|
|
.1.3.6.1.4.1.232.0.136000020 |
No Image
|
|
.1.3.6.1.4.1.232.0.136000021 |
No Permission
|
|
.1.3.6.1.4.1.232.0.136000022 |
Storage system not initialized
|
|
.1.3.6.1.4.1.232.0.136000023 |
Not a Loop Port
|
|
.1.3.6.1.4.1.232.0.136000024 |
Not a Participating Controller
|
|
.1.3.6.1.4.1.232.0.136000025 |
Objects in your system are in use, and their state prevents the operation you wish to perform.
|
|
.1.3.6.1.4.1.232.0.136000026 |
Parameter Object Does Not Exist
|
|
.1.3.6.1.4.1.232.0.136000027 |
Target Object Does Not Exist
|
|
.1.3.6.1.4.1.232.0.136000028 |
Timeout
|
|
.1.3.6.1.4.1.232.0.136000029 |
Unknown Id
|
|
.1.3.6.1.4.1.232.0.136000030 |
Unknown Parameter Handle
|
|
.1.3.6.1.4.1.232.0.136000031 |
Unrecoverable Media Error
|
|
.1.3.6.1.4.1.232.0.136000032 |
Invalid State
|
|
.1.3.6.1.4.1.232.0.136000033 |
Transport Error
|
|
.1.3.6.1.4.1.232.0.136000034 |
Volume is Missing
|
|
.1.3.6.1.4.1.232.0.136000035 |
Invalid Cursor
|
|
.1.3.6.1.4.1.232.0.136000036 |
Invalid Target for the Operation
|
|
.1.3.6.1.4.1.232.0.136000037 |
No More Events
|
|
.1.3.6.1.4.1.232.0.136000038 |
Lock Busy
|
|
.1.3.6.1.4.1.232.0.136000039 |
Time Not Set
|
|
.1.3.6.1.4.1.232.0.136000040 |
Not a Supported Version
|
|
.1.3.6.1.4.1.232.0.136000041 |
No Logical Disk for Vdisk
|
|
.1.3.6.1.4.1.232.0.136000042 |
Logical disk Presented
|
|
.1.3.6.1.4.1.232.0.136000043 |
Operation Denied On Slave
|
|
.1.3.6.1.4.1.232.0.136000044 |
Not licensed for data replication
|
|
.1.3.6.1.4.1.232.0.136000045 |
Not DR group member
|
|
.1.3.6.1.4.1.232.0.136000046 |
Invalid DR mode
|
|
.1.3.6.1.4.1.232.0.136000047 |
Invalid DR State
|
|
.1.3.6.1.4.1.232.0.136000048 |
Security credentials needed. Please update your system's ID and password in the Storage System Access menu.
|
|
.1.3.6.1.4.1.232.0.136000049 |
Security credentials supplied were invalid. Please update your system's ID and password in the Storage System Access menu.
|
|
.1.3.6.1.4.1.232.0.136000050 |
Security credentials supplied were invalid. Please update your system's ID and password in the Storage System Access menu.
|
|
.1.3.6.1.4.1.232.0.136000051 |
Storage system connection down
|
|
.1.3.6.1.4.1.232.0.136000052 |
DR group empty
|
|
.1.3.6.1.4.1.232.0.136000053 |
Incompatible attribute
|
|
.1.3.6.1.4.1.232.0.136000054 |
Vdisk is a DR group member
|
|
.1.3.6.1.4.1.232.0.136000055 |
Vdisk is a DR log unit
|
|
.1.3.6.1.4.1.232.0.136000056 |
Cache batteries failed or missing.
|
|
.1.3.6.1.4.1.232.0.136000057 |
Vdisk is not presented
|
|
.1.3.6.1.4.1.232.0.136000058 |
Other controller failed
|
|
.1.3.6.1.4.1.232.0.136000059 |
Maximum Number of Objects Exceeded.
|
|
.1.3.6.1.4.1.232.0.136000060 |
Max size
|
|
.1.3.6.1.4.1.232.0.136000061 |
Password mismatch. Please update your system's password in the Storage System Access menu. Continued attempts to access this storage system with an incorrect password will disable management of this storage system.
|
|
.1.3.6.1.4.1.232.0.136000062 |
DR group is merging
|
|
.1.3.6.1.4.1.232.0.136000063 |
DR group is logging
|
|
.1.3.6.1.4.1.232.0.136000064 |
Connection is suspended
|
|
.1.3.6.1.4.1.232.0.136000065 |
Bad image header
|
|
.1.3.6.1.4.1.232.0.136000066 |
Bad image
|
|
.1.3.6.1.4.1.232.0.136000067 |
Image too large
|
|
.1.3.6.1.4.1.232.0.136000068 |
EMU not available
|
|
.1.3.6.1.4.1.232.0.136000069 |
EMU indefinite delay
|
|
.1.3.6.1.4.1.232.0.136000070 |
Image incompatible with system configuration. Version conflict in upgrade or downgrade not allowed.
|
|
.1.3.6.1.4.1.232.0.136000071 |
Bad image segment
|
|
.1.3.6.1.4.1.232.0.136000072 |
Image already loaded
|
|
.1.3.6.1.4.1.232.0.136000073 |
Image Write Error
|
|
.1.3.6.1.4.1.232.0.136000074 |
Logical Disk Sharing
|
|
.1.3.6.1.4.1.232.0.136000075 |
Bad Image Size
|
|
.1.3.6.1.4.1.232.0.136000076 |
Image Load Busy
|
|
.1.3.6.1.4.1.232.0.136000077 |
Volume Failure Predicted
|
|
.1.3.6.1.4.1.232.0.136000078 |
Background allocation on the destination member is in progress. This action must complete before any others can be initiated .
|
|
.1.3.6.1.4.1.232.0.136000079 |
Invalid Predecessor Vdisk Condition
|
|
.1.3.6.1.4.1.232.0.136000080 |
Invalid Volume Usage
|
|
.1.3.6.1.4.1.232.0.136000081 |
Minimum Volumes In Disk Group
|
|
.1.3.6.1.4.1.232.0.136000082 |
Shutdown In Progress
|
|
.1.3.6.1.4.1.232.0.136000083 |
Not Ready
|
|
.1.3.6.1.4.1.232.0.136000084 |
Is Snapshot
|
|
.1.3.6.1.4.1.232.0.136000085 |
Cannot add or remove DR group member. Mirror cache must be active for this Vdisk. Check controller cache condition.
|
|
.1.3.6.1.4.1.232.0.136000086 |
Inoperative
|
|
.1.3.6.1.4.1.232.0.136000087 |
Disk group inoperative or less than 8 disks in group
|
|
.1.3.6.1.4.1.232.0.136000088 |
Storage system inoperative
|
|
.1.3.6.1.4.1.232.0.136000089 |
Failsafe Locked
|
|
.1.3.6.1.4.1.232.0.136000090 |
Data Flush Incomplete
|
|
.1.3.6.1.4.1.232.0.136000091 |
Redundancy Mirrored Inoperative
|
|
.1.3.6.1.4.1.232.0.136000092 |
Duplicate LUN
|
|
.1.3.6.1.4.1.232.0.136000093 |
Other remote controller failed
|
|
.1.3.6.1.4.1.232.0.136000094 |
Unknown remote Vdisk
|
|
.1.3.6.1.4.1.232.0.136000095 |
Unknown remote DR group
|
|
.1.3.6.1.4.1.232.0.136000096 |
PLDMC failed
|
|
.1.3.6.1.4.1.232.0.136000097 |
Storage system could not be locked. System busy. Try command again.
|
|
.1.3.6.1.4.1.232.0.136000098 |
Error on remote storage system.
|
|
.1.3.6.1.4.1.232.0.136000099 |
This operation can only be completed when the source-destination connection is down.
|
|
.1.3.6.1.4.1.232.0.136000100 |
Login required - password changed.
|
|
.1.3.6.1.4.1.232.0.136000101 |
Numerous login attempts have been detected that uses an incorrect password. Please update your system's password in the Storage System Access menu.
|
|
.1.3.6.1.4.1.232.0.136000102 |
Invalid cookie
|
|
.1.3.6.1.4.1.232.0.136000103 |
Login timed out
|
|
.1.3.6.1.4.1.232.0.136000104 |
Max snapshot depth reached
|
|
.1.3.6.1.4.1.232.0.136000105 |
Attribute mismatch
|
|
.1.3.6.1.4.1.232.0.136000106 |
The password has been set in Command View EVA. The same password still needs to be set in the controllers.
|
|
.1.3.6.1.4.1.232.0.136000107 |
Not host port
|
|
.1.3.6.1.4.1.232.0.136000108 |
Duplicate Lun WWID
|
|
.1.3.6.1.4.1.232.0.136000109 |
System Inoperative
|
|
.1.3.6.1.4.1.232.0.136000110 |
SnapClone Active
|
|
.1.3.6.1.4.1.232.0.136000111 |
Emu Load Busy
|
|
.1.3.6.1.4.1.232.0.136000112 |
Duplicate User Name
|
|
.1.3.6.1.4.1.232.0.136000113 |
Drive Reserved For Code Load
|
|
.1.3.6.1.4.1.232.0.136000114 |
Already Presented
|
|
.1.3.6.1.4.1.232.0.136000115 |
Invalid remote storage system
|
|
.1.3.6.1.4.1.232.0.136000116 |
No Lock
|
|
.1.3.6.1.4.1.232.0.136000117 |
Maximum Number of Members Exceeded
|
|
.1.3.6.1.4.1.232.0.136000118 |
Max Destinations
|
|
.1.3.6.1.4.1.232.0.136000119 |
Empty User Name
|
|
.1.3.6.1.4.1.232.0.136000120 |
Storage system already initialized
|
|
.1.3.6.1.4.1.232.0.136000121 |
Already Open
|
|
.1.3.6.1.4.1.232.0.136000122 |
Session Not Open
|
|
.1.3.6.1.4.1.232.0.136000123 |
Not Marked Inoperative
|
|
.1.3.6.1.4.1.232.0.136000124 |
Media Not Available
|
|
.1.3.6.1.4.1.232.0.136000125 |
Battery System Failed
|
|
.1.3.6.1.4.1.232.0.136000126 |
DR Group Member Is Cache Data Lost
|
|
.1.3.6.1.4.1.232.0.136000127 |
Internal Lock Collision
|
|
.1.3.6.1.4.1.232.0.136000128 |
OCP Error
|
|
.1.3.6.1.4.1.232.0.136000129 |
Mirror Offline
|
|
.1.3.6.1.4.1.232.0.136000130 |
This operation cannot be completed if failsafe mode is enabled.
|
|
.1.3.6.1.4.1.232.0.136000131 |
Drive firmware load abort due to Raid0 virtual disk(s).
|
|
.1.3.6.1.4.1.232.0.136000132 |
Fibre channel ports are unavailable.
|
|
.1.3.6.1.4.1.232.0.136000133 |
The storage system has reached its maximum number of DR relationship.
|
|
.1.3.6.1.4.1.232.0.136001 |
An EMU Informational event has occurred
scellNameDateTime: StorageCell name, and date/time emuShelfId: disk shelf number in the cabinet emuElementType: the element type 01: Disk 02: Pwr Supply 03: Fan 04: Temp Sensor 06: Alarm Horn 07: EMU 12: LCD 15: Xcvr 16: Lang 17: Comm Port 18: Volt Sensor 19: Amp Sensor 128:Encl 130:Back plane emuErrorCode: error number |
|
.1.3.6.1.4.1.232.0.136001000 |
Logical Disk Condition Change
|
|
.1.3.6.1.4.1.232.0.136001001 |
Storage system is FULL **critical**
|
|
.1.3.6.1.4.1.232.0.136001002 |
Storage system is almost FULL. Disk group at or above maximum capacity warning level.
|
|
.1.3.6.1.4.1.232.0.136001003 |
Controller Cache Battery Condition Change
|
|
.1.3.6.1.4.1.232.0.136001004 |
Controller Cache Condition Change
|
|
.1.3.6.1.4.1.232.0.136001005 |
Controller Condition Change
|
|
.1.3.6.1.4.1.232.0.136001006 |
Controller FC Port Condition Change
|
|
.1.3.6.1.4.1.232.0.136001007 |
Physical Device Condition Change
|
|
.1.3.6.1.4.1.232.0.136001008 |
Physical Store Condition Change
|
|
.1.3.6.1.4.1.232.0.136001009 |
Host condition change
|
|
.1.3.6.1.4.1.232.0.136001010 |
Storage system time has been set
|
|
.1.3.6.1.4.1.232.0.136001011 |
Volume Condition change
|
|
.1.3.6.1.4.1.232.0.136001012 |
Volume insufficient_resources condition change
|
|
.1.3.6.1.4.1.232.0.136001013 |
Volume Quorum Disk change
|
|
.1.3.6.1.4.1.232.0.136001014 |
The state of an object in the system has changed. View adjacent events for more detail.
|
|
.1.3.6.1.4.1.232.0.136002 |
An EMU Non-critical event has occurred
scellNameDateTime: StorageCell name, and date/time emuShelfId: disk shelf number in the cabinet emuElementType: the element type 01: Disk 02: Pwr Supply 03: Fan 04: Temp Sensor 06: Alarm Horn 07: EMU 12: LCD 15: Xcvr 16: Lang 17: Comm Port 18: Volt Sensor 19: Amp Sensor 128:Encl 130:Back plane emuErrorCode: error number |
|
.1.3.6.1.4.1.232.0.136002001 |
Startup Failed
|
|
.1.3.6.1.4.1.232.0.136002002 |
Management agent event log cleared successfully
|
|
.1.3.6.1.4.1.232.0.136002003 |
Invalid name specified for storage system
|
|
.1.3.6.1.4.1.232.0.136002004 |
Storage system is not initialized
|
|
.1.3.6.1.4.1.232.0.136002006 |
Invalid name specified for Vdisk
|
|
.1.3.6.1.4.1.232.0.136002007 |
Vdisk name exceeds maximum length
|
|
.1.3.6.1.4.1.232.0.136002008 |
Invalid parameter specified for Vdisk
|
|
.1.3.6.1.4.1.232.0.136002010 |
Specified Vdisk size exceeds available size
|
|
.1.3.6.1.4.1.232.0.136002011 |
There are not enough disk drives to create a disk group
|
|
.1.3.6.1.4.1.232.0.136002012 |
Number of devices exceeds the available number of disks
|
|
.1.3.6.1.4.1.232.0.136002013 |
Number of devices is less than the minimum number required to create a disk group
|
|
.1.3.6.1.4.1.232.0.136002016 |
Completed unpresenting virtual disk to host
|
|
.1.3.6.1.4.1.232.0.136002021 |
Invalid refresh interval value. Should be numeric and non-negative.
|
|
.1.3.6.1.4.1.232.0.136002022 |
Invalid security message. Should not be blank.
|
|
.1.3.6.1.4.1.232.0.136002023 |
Vdisk Create Complete
|
|
.1.3.6.1.4.1.232.0.136002025 |
Storage system successfully initialized
|
|
.1.3.6.1.4.1.232.0.136002026 |
Device Added Successfully
|
|
.1.3.6.1.4.1.232.0.136002030 |
Refresh Interval Changed
|
|
.1.3.6.1.4.1.232.0.136002031 |
Security Message Changed
|
|
.1.3.6.1.4.1.232.0.136002032 |
Present Vdisk to a Host - Complete
|
|
.1.3.6.1.4.1.232.0.136002033 |
Control Startup Complete
|
|
.1.3.6.1.4.1.232.0.136002034 |
Change Device Usage Complete
|
|
.1.3.6.1.4.1.232.0.136002035 |
Control Shutdown - Complete
|
|
.1.3.6.1.4.1.232.0.136002036 |
Controller Shutdown - Complete
|
|
.1.3.6.1.4.1.232.0.136002038 |
Control Memory Allocation Failure
|
|
.1.3.6.1.4.1.232.0.136002040 |
Access level denied or session activity timeout. Please log in again.
|
|
.1.3.6.1.4.1.232.0.136002041 |
Vdisk Snapshot - Completed
|
|
.1.3.6.1.4.1.232.0.136002042 |
Vdisk Snapclone - Completed
|
|
.1.3.6.1.4.1.232.0.136002047 |
Host record added successfully
|
|
.1.3.6.1.4.1.232.0.136002048 |
Logical component deleted successfully
|
|
.1.3.6.1.4.1.232.0.136002049 |
Invalid host adapter ID
|
|
.1.3.6.1.4.1.232.0.136002050 |
Specified device is already a member of the system
|
|
.1.3.6.1.4.1.232.0.136002051 |
Create Folder - Completed
|
|
.1.3.6.1.4.1.232.0.136002052 |
Change Object Properties - Completed
|
|
.1.3.6.1.4.1.232.0.136002057 |
Completed disk group creation
|
|
.1.3.6.1.4.1.232.0.136002058 |
Added host port
|
|
.1.3.6.1.4.1.232.0.136002059 |
Discarded host port
|
|
.1.3.6.1.4.1.232.0.136002060 |
EMU/Shelf code load complete
|
|
.1.3.6.1.4.1.232.0.136002061 |
Operation will exceed the available capacity of the disk group
|
|
.1.3.6.1.4.1.232.0.136002062 |
Controller(s) code load complete
|
|
.1.3.6.1.4.1.232.0.136002063 |
The target device is not in the right condition to perform the operation
|
|
.1.3.6.1.4.1.232.0.136002064 |
Storage system Device Addition Policy changed successfully
|
|
.1.3.6.1.4.1.232.0.136002065 |
Maximum number of disk groups exceeded
|
|
.1.3.6.1.4.1.232.0.136002066 |
Nsa object discard failed.
|
|
.1.3.6.1.4.1.232.0.136002067 |
There are not enough disks to meet the minimum number requirement
|
|
.1.3.6.1.4.1.232.0.136002068 |
Entry added successfully in the password file
|
|
.1.3.6.1.4.1.232.0.136002069 |
Entry updated successfully in the password file
|
|
.1.3.6.1.4.1.232.0.136002070 |
Entry discarded successfully in the password file
|
|
.1.3.6.1.4.1.232.0.136002071 |
Storage system is not responding in a timely manner and has been placed into an unknown state. This may be due to a prior command with an excessively long execution time, high I/O load, or a network communications error. Recovery will automatically occur when the storage system is able to respond.
|
|
.1.3.6.1.4.1.232.0.136002072 |
Object not found. Operation on this object is completed
|
|
.1.3.6.1.4.1.232.0.136002073 |
There is no more available space to create a Vdisk
|
|
.1.3.6.1.4.1.232.0.136002074 |
Name or comments contains invalid character(s)
|
|
.1.3.6.1.4.1.232.0.136002075 |
Duplicate - Another object with the same name exists.
|
|
.1.3.6.1.4.1.232.0.136002076 |
No healthy disk group(s) to create a Vdisk. Resolve any abnormal conditions in the disk group first.
|
|
.1.3.6.1.4.1.232.0.136002077 |
Operating System ID must be a valid number.
|
|
.1.3.6.1.4.1.232.0.136002078 |
Watchdog successfully started
|
|
.1.3.6.1.4.1.232.0.136002079 |
Watchdog successfully stopped
|
|
.1.3.6.1.4.1.232.0.136002080 |
Delete Event Config List failed
|
|
.1.3.6.1.4.1.232.0.136002081 |
Disk group meltdown repaired successfully.
|
|
.1.3.6.1.4.1.232.0.136002082 |
There are no available LUNs to present this Vdisk.
|
|
.1.3.6.1.4.1.232.0.136002083 |
Controller time synchronization turned on.
|
|
.1.3.6.1.4.1.232.0.136002084 |
Controller time synchronization turned off.
|
|
.1.3.6.1.4.1.232.0.136002085 |
System login failed. Invalid password.
|
|
.1.3.6.1.4.1.232.0.136002086 |
System is not set for password validation.
|
|
.1.3.6.1.4.1.232.0.136002087 |
Agent is already logged in to this system.
|
|
.1.3.6.1.4.1.232.0.136002088 |
Storage system time set to custom time. Controller time synchronization automatically turned off.
|
|
.1.3.6.1.4.1.232.0.136002089 |
Storage system time set to SAN appliance time.
|
|
.1.3.6.1.4.1.232.0.136002090 |
Storage system time set to browser time. Controller time synchronization automatically turned off.
|
|
.1.3.6.1.4.1.232.0.136002091 |
Storage system time set to controller time. Controller time synchronization automatically turned off.
|
|
.1.3.6.1.4.1.232.0.136002092 |
Unable to find DR Group on remote storage system.
|
|
.1.3.6.1.4.1.232.0.136002093 |
A host must have at least one port. Cannot delete the only host port available.
|
|
.1.3.6.1.4.1.232.0.136002095 |
Host creation failed. Maximum number of hosts reached.
|
|
.1.3.6.1.4.1.232.0.136002096 |
Port already exists for this host.
|
|
.1.3.6.1.4.1.232.0.136002097 |
Error reading parameter string. String is empty.
|
|
.1.3.6.1.4.1.232.0.136002098 |
Command could not be completed on Master. Controller not found.
|
|
.1.3.6.1.4.1.232.0.136002099 |
Command could not be completed on Slave. Controller not found.
|
|
.1.3.6.1.4.1.232.0.136002100 |
Password access for all known storage systems is already enabled or set.
|
|
.1.3.6.1.4.1.232.0.136002102 |
The local storage system has reached the maximum allowable DR relationship.
|
|
.1.3.6.1.4.1.232.0.136002103 |
The remote storage system has reached the maximum allowable DR relationship.
|
|
.1.3.6.1.4.1.232.0.13600256 |
Severity: Normal -- informational in nature. During Executive Services 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 chosen: <UL><LI>0 = TOY clock unavailable; time reset to default date and time. <LI>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. <LI>2 = EDC was bad for last known time value previously stored in nonvolatile memory; time reset to default date and time. <LI>3 = TOY clock not running; time reset to default date and time. <LI>4 = TOY clock time value believed to be accurate; time set to TOY clock time value. </UL>
|
|
.1.3.6.1.4.1.232.0.13600257 |
Severity: Normal -- informational in nature. The system time value was set to 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: <UL><LI>0 = The time was set to the time value on this HSV110 controller. <LI>1 = The master HSV110 controller requested the slave HSV110 controller to set its time to the time value. <LI>2 = The slave HSV110 controller set the local time to the time value. <LI>3 = The HSV110 controller's TOY clock was set to the time value. </UL>
|
|
.1.3.6.1.4.1.232.0.136003 |
An EMU Critical event has occurred
scellNameDateTime: StorageCell name, and date/time emuShelfId: disk shelf number in the cabinet emuElementType: the element type 01: Disk 02: Pwr Supply 03: Fan 04: Temp Sensor 06: Alarm Horn 07: EMU 12: LCD 15: Xcvr 16: Lang 17: Comm Port 18: Volt Sensor 19: Amp Sensor 128:Encl 130:Back plane emuErrorCode: error number |
|
.1.3.6.1.4.1.232.0.136003001 |
Event Manager Offline
|
|
.1.3.6.1.4.1.232.0.136003002 |
Event Manager Online
|
|
.1.3.6.1.4.1.232.0.136003003 |
Event Manager - Startup Failed
|
|
.1.3.6.1.4.1.232.0.136003004 |
Event Manager - Startup Complete
|
|
.1.3.6.1.4.1.232.0.136003007 |
Event Manager - Shutdown Complete
|
|
.1.3.6.1.4.1.232.0.136003009 |
Unable to open NSA Local Event Log File
|
|
.1.3.6.1.4.1.232.0.136003012 |
Unable to open Local Temp Event File - possibly no initialized SC
|
|
.1.3.6.1.4.1.232.0.136003013 |
Unable to clear NSA Local Event Log File
|
|
.1.3.6.1.4.1.232.0.136003015 |
Unable to clear NSA Event Log File
|
|
.1.3.6.1.4.1.232.0.136003016 |
Local log file found on startup
|
|
.1.3.6.1.4.1.232.0.136003017 |
Event Queue Flush Error
|
|
.1.3.6.1.4.1.232.0.136003019 |
EM File Manager Online
|
|
.1.3.6.1.4.1.232.0.136003020 |
EM File Manager Offline
|
|
.1.3.6.1.4.1.232.0.136003021 |
EM Log Manager Online
|
|
.1.3.6.1.4.1.232.0.136003022 |
EM Log Manager Offline
|
|
.1.3.6.1.4.1.232.0.136003024 |
Local NSA logfile is empty
|
|
.1.3.6.1.4.1.232.0.136003025 |
Event Queue Online
|
|
.1.3.6.1.4.1.232.0.136003028 |
Status Descriptions Unavailable
|
|
.1.3.6.1.4.1.232.0.136003029 |
EM Description Mngr Online
|
|
.1.3.6.1.4.1.232.0.136003035 |
EM: NSA log file unavailable
|
|
.1.3.6.1.4.1.232.0.136003036 |
EM Memory Allocation Error
|
|
.1.3.6.1.4.1.232.0.136003037 |
EM: Local Event Configuration File Unavailable
|
|
.1.3.6.1.4.1.232.0.136003038 |
EM: MLD Notification File Unavailable - retrieving local backup copy
|
|
.1.3.6.1.4.1.232.0.136003039 |
EM: Local Notification Host List File Unavailable
|
|
.1.3.6.1.4.1.232.0.136003044 |
Override this description with missing filename
|
|
.1.3.6.1.4.1.232.0.136003045 |
Invalid storage system event sequence number - can't retrieve event
|
|
.1.3.6.1.4.1.232.0.136003046 |
Invalid SC termination event sequence number - can't retrieve event
|
|
.1.3.6.1.4.1.232.0.136003047 |
EM: Event config file unavailable from MLD - retrieving local backup copy
|
|
.1.3.6.1.4.1.232.0.136003048 |
EM: Local user defined event state file unavailable
|
|
.1.3.6.1.4.1.232.0.136003049 |
EM: EMU event monitoring thread unable to start
|
|
.1.3.6.1.4.1.232.0.136003050 |
EM: EMU event - this description will be overwritten
|
|
.1.3.6.1.4.1.232.0.136003051 |
EM: Failed to write Event Config file to MLD
|
|
.1.3.6.1.4.1.232.0.136003053 |
EM: Event Configuration Filename Error or File empty
|
|
.1.3.6.1.4.1.232.0.136003054 |
EM: Notification Hostlist Filename Error or File empty
|
|
.1.3.6.1.4.1.232.0.136003055 |
EM: Event Config List Object Reference Error
|
|
.1.3.6.1.4.1.232.0.136003056 |
EM: SC Parse File successfully uploaded
|
|
.1.3.6.1.4.1.232.0.136003057 |
EM: SC Parse File upload failed
|
|
.1.3.6.1.4.1.232.0.136003058 |
EM: Contents of the uploaded parse file invalid - unexpected contents
|
|
.1.3.6.1.4.1.232.0.136003059 |
EM: Parse file is empty
|
|
.1.3.6.1.4.1.232.0.136003060 |
Storage system being shutdown due to a command failure.
|
|
.1.3.6.1.4.1.232.0.136003061 |
EM: Could not retrieve a storage system event
|
|
.1.3.6.1.4.1.232.0.136003062 |
EM: Init SC Event config list failed
|
|
.1.3.6.1.4.1.232.0.136003063 |
Could not initialize Comm infrastructure for event logging to system log
|
|
.1.3.6.1.4.1.232.0.136003064 |
EM: Storage system pointer is NULL!
|
|
.1.3.6.1.4.1.232.0.136003065 |
EM: Failed to log event to the Appliance event log: check if log is full
|
|
.1.3.6.1.4.1.232.0.136003066 |
EM: Description Mngr initialize storage system failed
|
|
.1.3.6.1.4.1.232.0.136003067 |
EM: Description file too small. File read problem Or Incomplete file.
|
|
.1.3.6.1.4.1.232.0.136003068 |
EM: Can't init NT Event object pointer
|
|
.1.3.6.1.4.1.232.0.136003069 |
EM: Can't init NT Notification object pointer
|
|
.1.3.6.1.4.1.232.0.136003070 |
EM: Appliance Event Logging Failure - log may be full
|
|
.1.3.6.1.4.1.232.0.136003071 |
EM: SCMI returned bad additional events number
|
|
.1.3.6.1.4.1.232.0.136003072 |
EM: SCMI returned zero sized SC Event
|
|
.1.3.6.1.4.1.232.0.136003075 |
EventQueue index passed is out of bounds
|
|
.1.3.6.1.4.1.232.0.136003076 |
EM: An abnormal number of duplicate events logged - dropping duplicates
|
|
.1.3.6.1.4.1.232.0.136003077 |
EM: Update of the MLD Status Description file failed
|
|
.1.3.6.1.4.1.232.0.136003078 |
EM: NsaStatusDescriptions.txt open file error
|
|
.1.3.6.1.4.1.232.0.136003079 |
EM: NsaStatusDescriptions.txt file error - file size discrepancy from mld list
|
|
.1.3.6.1.4.1.232.0.136003080 |
SC Event Log has been cleared and restarted. Possible RAID1 Meltdown.
|
|
.1.3.6.1.4.1.232.0.136003081 |
Invalid logType parameter
|
|
.1.3.6.1.4.1.232.0.136003083 |
Log file is empty
|
|
.1.3.6.1.4.1.232.0.136003084 |
Storage System with this WWN is not visible to this agent or the WWN is invalid
|
|
.1.3.6.1.4.1.232.0.136003086 |
Parsefile for current firmware version not found. Upload correct parse file.
|
|
.1.3.6.1.4.1.232.0.136003090 |
The contents of this file appear to be invalid
|
|
.1.3.6.1.4.1.232.0.136003091 |
The MIB failed to build due to a missing parse file.
|
|
.1.3.6.1.4.1.232.0.136003092 |
MLD description file is older than local file but system is downrev
|
|
.1.3.6.1.4.1.232.0.136003094 |
System is initialized: can't get activeQ events
|
|
.1.3.6.1.4.1.232.0.136003095 |
Failed to write file - file could not be opened.
|
|
.1.3.6.1.4.1.232.0.136004 |
An EMU Unrecoverable event has occurred
scellNameDateTime: StorageCell name, and date/time emuShelfId: disk shelf number in the cabinet emuElementType: the element type 01: Disk 02: Pwr Supply 03: Fan 04: Temp Sensor 06: Alarm Horn 07: EMU 12: LCD 15: Xcvr 16: Lang 17: Comm Port 18: Volt Sensor 19: Amp Sensor 128:Encl 130:Back plane emuErrorCode: error number |
|
.1.3.6.1.4.1.232.0.136004000 |
MLD Manager Subsystem Error
|
|
.1.3.6.1.4.1.232.0.136004001 |
MLD Manager Offline
|
|
.1.3.6.1.4.1.232.0.136004004 |
MLD Manager Startup Complete
|
|
.1.3.6.1.4.1.232.0.136004005 |
MLD Manager Abnormal Startup
|
|
.1.3.6.1.4.1.232.0.136004007 |
MLD Manager Shutdown Complete
|
|
.1.3.6.1.4.1.232.0.136004011 |
Invalid Host IP Address specified
|
|
.1.3.6.1.4.1.232.0.136004012 |
Unable to open the NsaMldMgr.dat file for Write
|
|
.1.3.6.1.4.1.232.0.136004013 |
Unable to open the NsaMldMgr.dat file for Read
|
|
.1.3.6.1.4.1.232.0.136004014 |
Agent Uid does not exist
|
|
.1.3.6.1.4.1.232.0.136004015 |
Unable to find object
|
|
.1.3.6.1.4.1.232.0.136004016 |
Unable to store object
|
|
.1.3.6.1.4.1.232.0.136004017 |
Unable to find storage system object
|
|
.1.3.6.1.4.1.232.0.136004018 |
Unable to create MLD
|
|
.1.3.6.1.4.1.232.0.136004020 |
lastSafeChoiceDelay Expired
|
|
.1.3.6.1.4.1.232.0.136004021 |
crashDetectDelay Expired
|
|
.1.3.6.1.4.1.232.0.136004023 |
Unable to read Copy1 of MLD
|
|
.1.3.6.1.4.1.232.0.136004024 |
Copy 1 of MLD Invalid
|
|
.1.3.6.1.4.1.232.0.136004025 |
Invalid Copy block of MLD
|
|
.1.3.6.1.4.1.232.0.136004027 |
MLD database capacity not equal to true MLD capacity
|
|
.1.3.6.1.4.1.232.0.136004028 |
Backup range out of bounds of copy 1 range
|
|
.1.3.6.1.4.1.232.0.136004029 |
MLD Manager Lock Crash DetectDelay has expired, just taking lock!
|
|
.1.3.6.1.4.1.232.0.136004030 |
MLD Copy 1 Restored
|
|
.1.3.6.1.4.1.232.0.136004031 |
MLD Copy 2 Restored
|
|
.1.3.6.1.4.1.232.0.136004032 |
Unable to find UidAssoc Object
|
|
.1.3.6.1.4.1.232.0.136004033 |
Unable to store UID Association Object
|
|
.1.3.6.1.4.1.232.0.136004034 |
Unable to find UidAssoc Object
|
|
.1.3.6.1.4.1.232.0.136004035 |
Unable to read last Fusion event read
|
|
.1.3.6.1.4.1.232.0.136004036 |
MLD Notification Queue Empty
|
|
.1.3.6.1.4.1.232.0.136004037 |
Unable to find Notification Object
|
|
.1.3.6.1.4.1.232.0.136004040 |
Unable to read Event Log Pointer
|
|
.1.3.6.1.4.1.232.0.136004041 |
Unable to read Event Log
|
|
.1.3.6.1.4.1.232.0.136004042 |
Unable to store Event Log
|
|
.1.3.6.1.4.1.232.0.136004043 |
Unable to read Event Log
|
|
.1.3.6.1.4.1.232.0.136004047 |
Previously Read Object Properties do not Match
|
|
.1.3.6.1.4.1.232.0.136004048 |
Previously Read Object Properties do not Match
|
|
.1.3.6.1.4.1.232.0.136004049 |
Unable to read Notification Host List
|
|
.1.3.6.1.4.1.232.0.136004050 |
Unable to store Notification Host List
|
|
.1.3.6.1.4.1.232.0.136004051 |
Unable to store Notification Host List and free Lock
|
|
.1.3.6.1.4.1.232.0.136004052 |
Unable to read Event Configuration List
|
|
.1.3.6.1.4.1.232.0.136004053 |
Unable to store Event Configuration List
|
|
.1.3.6.1.4.1.232.0.136004054 |
Unable to store Event Configuration List and free Lock
|
|
.1.3.6.1.4.1.232.0.136004058 |
MLD Manager Mutex Timeout error
|
|
.1.3.6.1.4.1.232.0.136004059 |
MLD Manager list is empty
|
|
.1.3.6.1.4.1.232.0.136005001 |
Monitor Startup Complete
|
|
.1.3.6.1.4.1.232.0.136005002 |
Monitor Startup Failed
|
|
.1.3.6.1.4.1.232.0.136005003 |
Monitor ShutDown Complete
|
|
.1.3.6.1.4.1.232.0.136005004 |
Monitor Memory Allocation Failure
|
|
.1.3.6.1.4.1.232.0.136005005 |
Monitor Mark Agent as Inactive
|
|
.1.3.6.1.4.1.232.0.136005006 |
Monitor create thread error
|
|
.1.3.6.1.4.1.232.0.136005007 |
Monitor create timer error
|
|
.1.3.6.1.4.1.232.0.136005008 |
Monitor agent registration - Complete
|
|
.1.3.6.1.4.1.232.0.136005010 |
Monitor initiated a storage system management shutdown because of controller failures
|
|
.1.3.6.1.4.1.232.0.136005011 |
Unknown storage system rediscovery complete
|
|
.1.3.6.1.4.1.232.0.136005012 |
Start monitoring thread for storage system - Complete
|
|
.1.3.6.1.4.1.232.0.136005013 |
Start monitoring thread for storage system - Fail
|
|
.1.3.6.1.4.1.232.0.136005014 |
Monitoring thread for storage system terminated
|
|
.1.3.6.1.4.1.232.0.136005015 |
Rediscover unknown storage system - Error
|
|
.1.3.6.1.4.1.232.0.136005016 |
Controller time synchronized to appliance time.
|
|
.1.3.6.1.4.1.232.0.136005017 |
Appliance and controller time checked for synchronization.
|
|
.1.3.6.1.4.1.232.0.136005018 |
Controller and appliance time are the same. No need to synchronize.
|
|
.1.3.6.1.4.1.232.0.136005019 |
Exception caught in monitoring process.
|
|
.1.3.6.1.4.1.232.0.136006001 |
Ready
|
|
.1.3.6.1.4.1.232.0.136006002 |
Index Out of Range
|
|
.1.3.6.1.4.1.232.0.136006003 |
Cannot access storage system. Communications error.
|
|
.1.3.6.1.4.1.232.0.136006004 |
No controllers found
|
|
.1.3.6.1.4.1.232.0.136006005 |
Invalid Index
|
|
.1.3.6.1.4.1.232.0.136006006 |
Memory allocation failure
|
|
.1.3.6.1.4.1.232.0.136006007 |
No physical stores found
|
|
.1.3.6.1.4.1.232.0.136006008 |
No storage system found
|
|
.1.3.6.1.4.1.232.0.136006009 |
No disk group found
|
|
.1.3.6.1.4.1.232.0.136006010 |
Too many disk groups
|
|
.1.3.6.1.4.1.232.0.136006011 |
No volumes found
|
|
.1.3.6.1.4.1.232.0.136006012 |
No Logical Disks Found
|
|
.1.3.6.1.4.1.232.0.136006013 |
Context ID changed during operation
|
|
.1.3.6.1.4.1.232.0.136006014 |
No Name
|
|
.1.3.6.1.4.1.232.0.136006015 |
Name Size Exceeded
|
|
.1.3.6.1.4.1.232.0.136006016 |
Shutdown Complete
|
|
.1.3.6.1.4.1.232.0.136006017 |
Mutex Creation Failure
|
|
.1.3.6.1.4.1.232.0.136006018 |
The command has timed out. Storage system is busy processing previous command.
|
|
.1.3.6.1.4.1.232.0.136006019 |
No MLD Handle Set
|
|
.1.3.6.1.4.1.232.0.136006020 |
Failed Transport Layer Communication - No Such Id
|
|
.1.3.6.1.4.1.232.0.136006021 |
Failed Transport Layer Communication - TimeOut
|
|
.1.3.6.1.4.1.232.0.136006022 |
No initialized storage system objects found
|
|
.1.3.6.1.4.1.232.0.136006023 |
No Attached Port Found
|
|
.1.3.6.1.4.1.232.0.136006024 |
Failed to get SCMI Object Handle
|
|
.1.3.6.1.4.1.232.0.136006025 |
Shutdown Both Restart And Power Off Requested
|
|
.1.3.6.1.4.1.232.0.136006026 |
Shutdown Drive Shelf Power Off But No Enclosure Power Off Requested
|
|
.1.3.6.1.4.1.232.0.136006027 |
Shutdown Disable Battery But No Enclosure Power Off Requested
|
|
.1.3.6.1.4.1.232.0.136006028 |
Shutdown Disable Battery But Shutdown Unconditional Requested
|
|
.1.3.6.1.4.1.232.0.136006029 |
Shutdown Delay Out Of Range
|
|
.1.3.6.1.4.1.232.0.136006030 |
Cache Write Failure
|
|
.1.3.6.1.4.1.232.0.136006031 |
Battery Disable Failure
|
|
.1.3.6.1.4.1.232.0.136006032 |
Drive Shelf Disable Failure
|
|
.1.3.6.1.4.1.232.0.136006033 |
Battery Disable Failed on Both Controllers Batteries
|
|
.1.3.6.1.4.1.232.0.136006034 |
Battery Disable Failed on This Controllers Battery
|
|
.1.3.6.1.4.1.232.0.136006035 |
Battery Disable Failed on the Other Controllers Battery
|
|
.1.3.6.1.4.1.232.0.136006036 |
Requested disk failure protection level is set. Actual level will change when sufficient disk space is available.
|
|
.1.3.6.1.4.1.232.0.136006037 |
Physical Store Contains Stale or Foreign Volume Information.
|
|
.1.3.6.1.4.1.232.0.136006038 |
Controller Resynchronization or Reboot Occurred. Context Error
|
|
.1.3.6.1.4.1.232.0.13600768 |
Severity: Normal -- informational in nature. The HSV110 controller identified in the node_name field has failed in communicating with the Cabinet (Rack) Bus Interface Controller.
|
|
.1.3.6.1.4.1.232.0.13600769 |
Severity: Critical -- failure or failure imminent. The physical disk drive identified by the device field has been rendered inoperable. <UL><LI>If the flags.quorum_disk flag is nonzero, the physical disk drive is the Storage System Quorum disk identified in the quorum_sequence field. <LI>If the flags.inq_state flag is nonzero, the content of the inq_data and capacity fields is valid. <LI>If the rss_flags.member_abnormal flag is nonzero, the content of the member_state field is valid. </UL>The rack_num field will not be valid until a future release. <P> The reason_code field contains a code giving the reason the physical disk drive has been rendered inoperable: <UL><LI>0x001 = CS IO failure <LI>0x002 = Scrubber IO failure <LI>0x003 = Attempt to set CBIT on normal drive <LI>0x004 = Attempt to set CBIT on merging drive <LI>0x100 = The Target Discovery Service Descriptor retry count has been exceeded <LI>0x101 = Inoperable for Bad Block Replacement <LI>0x102 = The soft error count has been exceeded <LI>0x103 = The number of exchange timeouts permitted was exceeded <LI>0x104 = Communication with drive has failed an excessive number of times <LI>0x105 = The number of retries has been exceeded <LI>0x106 = Medium/Hardware Errors encountered on this physical disk drive <LI>0x107 = The number of Directed LIP's has surpassed the threshold <LI>0x200 = Smart event from a physical disk drive not in Storage System <LI>0x201 = Smart event from a physical disk drive not a Volume <LI>0x202 = Smart event from a physical disk drive not a RSS <LI>0x203 = Failure predicted from physical disk drive <LI>0x204 = Can't read from physical disk drive from the poll <LI>0x205 = Failure predicted from physical disk drive while deleting Disk Group <LI>0x206 = physical disk drive forced inoperative from maintenance command for temporary POID <LI>0x207 = physical disk drive forced inoperative from maintenance command for POID <LI>0x208 = Bad block recovery failed or can't read FPAB <LI>0x209 = Failure to remove volume from Storage System <LI>0x20A = Failure to update metadata </UL>
|
|
.1.3.6.1.4.1.232.0.13600770 |
Severity: Warning -- not failed but attention recommended or required. A physical disk drive will not be used because the maximum number of physical disk drives already exist in the current Storage System. The affected physical disk drive is identified 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. Note that the content of the rack_num field will not be valid until a future release. Note also that in this case the content of the reason_code, flags, rss_flags, inq_data, quorum_sequence, capacity, and member_state fields is undefined.
|
|
.1.3.6.1.4.1.232.0.13600771 |
Severity: Normal -- informational in nature. A HSV110 controller has begun booting. That controller is identified in the node_name field. Note that in this case the content of the scell_tag field is undefined.
|
|
.1.3.6.1.4.1.232.0.13600772 |
Severity: Normal -- informational in nature. The HSV110 controller identified in the node_name field has finished the process of bringing the Storage System, identified in the scell_tag field, online.
|
|
.1.3.6.1.4.1.232.0.13600773 |
Severity: Normal -- informational in nature. The HSV110 controller identified in the node_name field has been joined into the Storage System.
|
|
.1.3.6.1.4.1.232.0.13600774 |
Severity: Normal -- informational in nature. The HSV110 controller identified in the node_name field has been ousted from the Storage System identified in the scell_tag field.
|
|
.1.3.6.1.4.1.232.0.13600775 |
Severity: Normal -- informational in nature. The HSV110 controller identified in the node_name field is now the Storage System, identified in the scell_tag field, master.
|
|
.1.3.6.1.4.1.232.0.13600776 |
Severity: Normal -- informational in nature. The HSV110 controller identified in the node_name field has been brought into the Storage System identified in the scell_tag field.
|
|
.1.3.6.1.4.1.232.0.136008001 |
Invalid Operation
|
|
.1.3.6.1.4.1.232.0.136008002 |
Storage system already created
|
|
.1.3.6.1.4.1.232.0.136008003 |
Controller already part of storage system configuration
|
|
.1.3.6.1.4.1.232.0.136008004 |
Physical Store Count Below Minimum
|
|
.1.3.6.1.4.1.232.0.136008005 |
Controller not part of storage system configuration
|
|
.1.3.6.1.4.1.232.0.136008006 |
Failed to uninitialize storage system
|
|
.1.3.6.1.4.1.232.0.136008007 |
Storage system File Open Error
|
|
.1.3.6.1.4.1.232.0.136008008 |
Storage system File Write Error
|
|
.1.3.6.1.4.1.232.0.136008009 |
Storage system File Read Error
|
|
.1.3.6.1.4.1.232.0.136008010 |
Name too long
|
|
.1.3.6.1.4.1.232.0.136008011 |
No String Error
|
|
.1.3.6.1.4.1.232.0.136008012 |
No MLD Handle Found
|
|
.1.3.6.1.4.1.232.0.136008013 |
No Controllers Found
|
|
.1.3.6.1.4.1.232.0.136008014 |
Controller Not Found On Loop
|
|
.1.3.6.1.4.1.232.0.136008015 |
No Disk Groups Found
|
|
.1.3.6.1.4.1.232.0.136008016 |
No Volumes Found
|
|
.1.3.6.1.4.1.232.0.136008017 |
No Physical Stores Found
|
|
.1.3.6.1.4.1.232.0.136008018 |
No Vdisks Found
|
|
.1.3.6.1.4.1.232.0.136008019 |
No Hosts Found
|
|
.1.3.6.1.4.1.232.0.136008020 |
Name already exists
|
|
.1.3.6.1.4.1.232.0.136008021 |
Folder is not empty
|
|
.1.3.6.1.4.1.232.0.136008022 |
Spares goal could not be met
|
|
.1.3.6.1.4.1.232.0.136008023 |
Storage system object found
|
|
.1.3.6.1.4.1.232.0.136008024 |
Storage system object not found
|
|
.1.3.6.1.4.1.232.0.136008025 |
New Physical Store Detected But Not Found In Physical Store List
|
|
.1.3.6.1.4.1.232.0.136008026 |
MldManager Handle is NULL
|
|
.1.3.6.1.4.1.232.0.136008027 |
NscMngrInterface Handle is NULL
|
|
.1.3.6.1.4.1.232.0.136008028 |
ScLockMngr Handle is NULL
|
|
.1.3.6.1.4.1.232.0.136008029 |
Storage system initialization failed
|
|
.1.3.6.1.4.1.232.0.136008030 |
MldMngr, NscMngrInterfaceMngr, or ScLockMngr Handle is NULL
|
|
.1.3.6.1.4.1.232.0.136008031 |
Storage system initialization failed
|
|
.1.3.6.1.4.1.232.0.136008032 |
Storage system discovery failed
|
|
.1.3.6.1.4.1.232.0.136008033 |
Storage system already uninitialized or does not exist
|
|
.1.3.6.1.4.1.232.0.136008034 |
Get Total Storage Failed
|
|
.1.3.6.1.4.1.232.0.136008035 |
Storage system is uninitialized
|
|
.1.3.6.1.4.1.232.0.136008036 |
Get Total Storage Available Failed
|
|
.1.3.6.1.4.1.232.0.136008037 |
Get Total Storage Occupied Failed
|
|
.1.3.6.1.4.1.232.0.136008038 |
Get Total Storage Free Failed
|
|
.1.3.6.1.4.1.232.0.136008039 |
Get Disk Group Failed
|
|
.1.3.6.1.4.1.232.0.136008040 |
Get Disk Group List Failed
|
|
.1.3.6.1.4.1.232.0.136008041 |
Get Disk Group Count Failed
|
|
.1.3.6.1.4.1.232.0.136008042 |
Create Volume Failed
|
|
.1.3.6.1.4.1.232.0.136008043 |
Get Volume Failed
|
|
.1.3.6.1.4.1.232.0.136008044 |
Get Volumes Failed
|
|
.1.3.6.1.4.1.232.0.136008045 |
Get Volumes Count Failed
|
|
.1.3.6.1.4.1.232.0.136008046 |
Get Vdisk Failed
|
|
.1.3.6.1.4.1.232.0.136008047 |
Get Vdisk List Failed
|
|
.1.3.6.1.4.1.232.0.136008048 |
Get Physical Store Failed
|
|
.1.3.6.1.4.1.232.0.136008049 |
Get Physical Stores Failed
|
|
.1.3.6.1.4.1.232.0.136008050 |
Get Physical Stores Count Failed
|
|
.1.3.6.1.4.1.232.0.136008051 |
Create Vdisk Failed
|
|
.1.3.6.1.4.1.232.0.136008052 |
Delete Vdisk Failed
|
|
.1.3.6.1.4.1.232.0.136008053 |
Get Device Addition Policy Failed
|
|
.1.3.6.1.4.1.232.0.136008054 |
Get Spares Current Failed
|
|
.1.3.6.1.4.1.232.0.136008055 |
Get Spares Goal Failed
|
|
.1.3.6.1.4.1.232.0.136008056 |
Get storage system events failed
|
|
.1.3.6.1.4.1.232.0.136008057 |
Get Volume Replacement Delay Failed
|
|
.1.3.6.1.4.1.232.0.136008058 |
Set Device Addition Policy Failed
|
|
.1.3.6.1.4.1.232.0.136008059 |
Set Spares Goal Failed
|
|
.1.3.6.1.4.1.232.0.136008060 |
Set Volume Replacement Delay Failed
|
|
.1.3.6.1.4.1.232.0.136008061 |
Create controller Failed
|
|
.1.3.6.1.4.1.232.0.136008062 |
Update controller Failed
|
|
.1.3.6.1.4.1.232.0.136008063 |
Create Host Failed
|
|
.1.3.6.1.4.1.232.0.136008064 |
Discard Host Failed
|
|
.1.3.6.1.4.1.232.0.136008065 |
Get Host Failed
|
|
.1.3.6.1.4.1.232.0.136008066 |
Get Host List Failed
|
|
.1.3.6.1.4.1.232.0.136008067 |
Get Host Count Failed
|
|
.1.3.6.1.4.1.232.0.136008068 |
Get Presented Unit List Failed
|
|
.1.3.6.1.4.1.232.0.136008069 |
Get Presented Unit Count Failed
|
|
.1.3.6.1.4.1.232.0.136008070 |
Free View Failed
|
|
.1.3.6.1.4.1.232.0.136008071 |
Storage system shutdown Failed
|
|
.1.3.6.1.4.1.232.0.136008073 |
Get Derived Unit List Failed
|
|
.1.3.6.1.4.1.232.0.136008074 |
Get Derived Unit Count Failed
|
|
.1.3.6.1.4.1.232.0.136008075 |
Get Vdisk list failed
|
|
.1.3.6.1.4.1.232.0.136008076 |
Get Vdisk count failed
|
|
.1.3.6.1.4.1.232.0.136008077 |
Error while building Vdisk root view
|
|
.1.3.6.1.4.1.232.0.136008078 |
Error while building host root view
|
|
.1.3.6.1.4.1.232.0.136008079 |
Error while building disk group root view
|
|
.1.3.6.1.4.1.232.0.136008080 |
Error while building hardware root view
|
|
.1.3.6.1.4.1.232.0.136008081 |
Specified time format is incorrect
|
|
.1.3.6.1.4.1.232.0.136008082 |
Error creating/opening time synchronization file.
|
|
.1.3.6.1.4.1.232.0.136008083 |
NSCList reordered.
|
|
.1.3.6.1.4.1.232.0.136008084 |
NscList mutex Get error
|
|
.1.3.6.1.4.1.232.0.136008085 |
Storage System is managed by another agent
|
|
.1.3.6.1.4.1.232.0.136008086 |
Memory allocation failure
|
|
.1.3.6.1.4.1.232.0.136008087 |
Failed to obtain list of DR Groups
|
|
.1.3.6.1.4.1.232.0.136008088 |
Failed to obtain count of DR Groups
|
|
.1.3.6.1.4.1.232.0.136008089 |
Failed to build DR Group view
|
|
.1.3.6.1.4.1.232.0.136008090 |
No Devices found on Controller Back End Loops
|
|
.1.3.6.1.4.1.232.0.136009001 |
Vdisk File Open Error
|
|
.1.3.6.1.4.1.232.0.136009002 |
Vdisk File Write Error
|
|
.1.3.6.1.4.1.232.0.136009003 |
Vdisk File Read Error
|
|
.1.3.6.1.4.1.232.0.136009004 |
Vdisk name too long
|
|
.1.3.6.1.4.1.232.0.136009005 |
Vdisk No String Error
|
|
.1.3.6.1.4.1.232.0.136009006 |
Vdisk No Object Error
|
|
.1.3.6.1.4.1.232.0.136009007 |
Vdisk still exists
|
|
.1.3.6.1.4.1.232.0.136009008 |
Vdisk Invalid Value
|
|
.1.3.6.1.4.1.232.0.136009009 |
An outstanding command is still in progress for the Vdisk
|
|
.1.3.6.1.4.1.232.0.136009010 |
Requested Vdisk size exceeds the available size
|
|
.1.3.6.1.4.1.232.0.136009011 |
Vdisk size may be expanded but not reduced
|
|
.1.3.6.1.4.1.232.0.136009012 |
Operation on a fast Vdisk deletion completed
|
|
.1.3.6.1.4.1.232.0.136009013 |
Operation on a fast Vdisk creation completed
|
|
.1.3.6.1.4.1.232.0.136009014 |
Operation on a fast Vdisk size expansion completed
|
|
.1.3.6.1.4.1.232.0.136009015 |
Vdisk cache data lost error
|
|
.1.3.6.1.4.1.232.0.136009016 |
Vdisk data lost error resolved
|
|
.1.3.6.1.4.1.232.0.136009017 |
Operation rejected - The Vdisk has a sharing relationship with another object
|
|
.1.3.6.1.4.1.232.0.136009018 |
Operation on this Vdisk was rejected due to its degraded condition
|
|
.1.3.6.1.4.1.232.0.136009019 |
Operation on this Vdisk can only be performed if it is presented to a host
|
|
.1.3.6.1.4.1.232.0.136009020 |
Cache policies cannot be modified if Vdisk is presented to a host
|
|
.1.3.6.1.4.1.232.0.136009021 |
Allowed property changes successful. (Cache policy changes not allowed while Vdisk is presented to a host.)
|
|
.1.3.6.1.4.1.232.0.136009022 |
Requested redundancy type cannot be implemented with the current disk group condition.
|
|
.1.3.6.1.4.1.232.0.136009023 |
Your Vdisk was created but cannot be presented at this time. It can be presented when it is fully allocated.
|
|
.1.3.6.1.4.1.232.0.136009025 |
Vdisk device data lost error
|
|
.1.3.6.1.4.1.232.0.136009026 |
The most significant hex character in a World Wide LUN Name must be a 6.
|
|
.1.3.6.1.4.1.232.0.136009027 |
Virtual disk cache and inoperative data lost error
|
|
.1.3.6.1.4.1.232.0.136009028 |
Virtual disk inoperative data lost error
|
|
.1.3.6.1.4.1.232.0.136009029 |
Virtual disk condition failed because of an inoperative data lost error.
|
|
.1.3.6.1.4.1.232.0.136009030 |
Vdisk is a snapshot. The following properties cannot be changed: Preferred Path, Requested Size, Write-Back Cache Policy.
|
|
.1.3.6.1.4.1.232.0.136009031 |
The World Wide LUN Name cannot be changed for a presented Vdisk Active member or snapshot.
|
|
.1.3.6.1.4.1.232.0.136009032 |
Unknown property, request rejected
|
|
.1.3.6.1.4.1.232.0.136009033 |
This Vdisk was deleted as the indirect result of another user command.
|
|
.1.3.6.1.4.1.232.0.136009034 |
The requested allocation policy cannot be satisfied. A different allocation policy is already in use by another snapshot in the same family.
|
|
.1.3.6.1.4.1.232.0.136009035 |
The deletion of this Vdisk cannot take place. The original Vdisk that this is being snapcloned from is in a VRaid1 Meltdown state which must first be resolved.
|
|
.1.3.6.1.4.1.232.0.136009036 |
Synchronous creation of virtual disk has been aborted due to an internal error. Switching to asynchronous mode to complete the virtual disk creation.
|
|
.1.3.6.1.4.1.232.0.136010001 |
Storage Object Broker Ready
|
|
.1.3.6.1.4.1.232.0.136010004 |
Storage system is not initialized
|
|
.1.3.6.1.4.1.232.0.136010006 |
SOB Memory Allocation Failure
|
|
.1.3.6.1.4.1.232.0.136010010 |
Your initialized system must have at least one disk group
|
|
.1.3.6.1.4.1.232.0.136010011 |
Cannot talk to all available controllers
|
|
.1.3.6.1.4.1.232.0.136010012 |
Command rejected - Folder is not empty
|
|
.1.3.6.1.4.1.232.0.136010013 |
Command rejected - Vdisk(s) or a data replication log are contained in this disk group
|
|
.1.3.6.1.4.1.232.0.136010014 |
Command rejected - Vdisk(s) are presented to this host
|
|
.1.3.6.1.4.1.232.0.136010015 |
Command rejected - This Vdisk has a sharing relationship with another object
|
|
.1.3.6.1.4.1.232.0.136010017 |
Command rejected - Number of disk groups will exceed the maximum allowable number
|
|
.1.3.6.1.4.1.232.0.136010018 |
Cannot access the password file
|
|
.1.3.6.1.4.1.232.0.136010019 |
Enterprise Login - Complete
|
|
.1.3.6.1.4.1.232.0.136010020 |
Command rejected - Disks in the group would go below the minimum required number.
|
|
.1.3.6.1.4.1.232.0.136010021 |
Rediscovery of controllers - Complete
|
|
.1.3.6.1.4.1.232.0.136010022 |
Unable to establish communication with controller, check all connections.
|
|
.1.3.6.1.4.1.232.0.136010023 |
Disk Group Data Lost Error Resolution Sequence 3 - Disk group resolved to normal
|
|
.1.3.6.1.4.1.232.0.136010024 |
Disk Group Data Lost Error Resolution Sequence 1 - Failed Vdisks marked for deletion
|
|
.1.3.6.1.4.1.232.0.136010025 |
Disk Group Data Lost Error Resolution Sequence 2 - Failed Vdisks deleted
|
|
.1.3.6.1.4.1.232.0.136010026 |
Disk Group Data Lost Error Resolution Sequence 3 - Disk group deleted
|
|
.1.3.6.1.4.1.232.0.136010027 |
Creating the Vdisk would exceed the maximum allowable Vdisk count
|
|
.1.3.6.1.4.1.232.0.136010028 |
Volume insufficient resources
|
|
.1.3.6.1.4.1.232.0.136010029 |
Process mutex is locked
|
|
.1.3.6.1.4.1.232.0.136010030 |
Invalid URL request type
|
|
.1.3.6.1.4.1.232.0.136010031 |
Invalid URL object type
|
|
.1.3.6.1.4.1.232.0.136010035 |
The snapshot/Snapclone license cannot be validated. Either the license key has not been entered, or there is a system communication failure.
|
|
.1.3.6.1.4.1.232.0.136010036 |
A data replication license cannot be validated. Either the license key has not been entered, or there is a system communication failure.
|
|
.1.3.6.1.4.1.232.0.136010037 |
Object name should not be empty or exceed its maximum length
|
|
.1.3.6.1.4.1.232.0.136010038 |
Object comments exceeds maximum length
|
|
.1.3.6.1.4.1.232.0.136010039 |
Vdisk does not meet the requirements to be part of a DR group.
|
|
.1.3.6.1.4.1.232.0.136010040 |
The Eva selected as the Destination for the DR group is invalid. Either it has a DR relationship with another EVA or it is not the same EVA that the source EVA presently has a DR relationship with.
|
|
.1.3.6.1.4.1.232.0.136010041 |
Cannot group the specified disk device because the disk is already in a disk group.
|
|
.1.3.6.1.4.1.232.0.136010042 |
Cannot ungroup the specified disk device because the disk is not grouped.
|
|
.1.3.6.1.4.1.232.0.136010043 |
Object ID provided, or object type, is invalid for the requested operation.
|
|
.1.3.6.1.4.1.232.0.136010044 |
Specified remote disk group does not exist.
|
|
.1.3.6.1.4.1.232.0.13601024 |
Severity: Undetermined -- more information needed to determine severity. HSV110 controller operation was terminated due to an unrecoverable event detected by either software or hardware or due to an action initiated via the Storage System Management Interface.
|
|
.1.3.6.1.4.1.232.0.13601025 |
Severity: Undetermined -- more information needed to determine severity. An HSV110 controller has sent a last gasp message prior to terminating operation. The terminated HSV110 controller is identified in the lter.terminating_ctrlr field. The lter.termination_event.u.value field contains the termination cause (i.e., termination code). The lter.termination_event.termination_location field contains the termination location. The lter.termination_time field contains the termination date and time. The lter.seq field contains the index of the HSV110 controller's Last Termination Event Array element assigned to the termination event. The lter.sw_version, lter.baselevel_id, and lter.ctrlr_model_id fields identify the software level and controller model information. The lter.uptime field contains a value that represents the number of seconds the HSV110 controller has executed functional code since its first power up. Note that the reporting_ctrlr header field identifies the HSV110 controller that received the last gasp message. All other header fields reflect information supplied by the terminating controller.
|
|
.1.3.6.1.4.1.232.0.13601026 |
Severity: Critical -- failure or failure imminent. A machine check occurred while 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.
|
|
.1.3.6.1.4.1.232.0.13601027 |
Severity: Critical -- failure or failure imminent. An unexpected event occurred while a termination event was being processed. The value contained in the uei.type field describes the event as follows: <UL><LI>0 = Unrecognized Unexpected Event code. <LI>1 = Power failure before initialization could complete. <LI>2 = Recursive termination before initialization could complete. <LI>3 = Terminated during the first part post-termination preparation. <LI>4 = Terminated during the load of the G3 Glue registers. <LI>5 = Terminated during the second part post-termination preparation. <LI>6 = Terminated during event report block load. <LI>7 = Terminated during initialization of all hardware components and software data structures in preparation for restart. <LI>8 = Terminated during execution of an unrecognized post-termination operation (premature). <LI>9 = Power failure during execution of a post-termination operation. <LI>A = No good entries found in Termination Event Array. (Note that this condition is expected following the first boot of a newly manufactured HSV110 controller. In that case this event can be safely ignored; no action is necessary.) <LI>B = The EDC of one or more Termination Event Array entries is bad. <LI>C = Termination Event Array entry control block revision is different. <LI>D = Termination Event Array entry information block revision is different. <LI>E = Termination Event Array entry up time value is greater than the system's up time value. <LI>F = Termination Event Array entry up time value is less than the previous entry's up time value. <LI>10= Termination Event Array entry sequence number value is less than the previous entry's sequence number value. <LI>11= Detected an unrecognized dump/restart control code. <LI>12= Failed to terminate the entity dump loop. <LI>13= Unexpected dump entity size. <LI>14= Unexpected Event Log Packet processing stage code. <LI>15= Number of Termination Parameters supplied not equal to maximum allowed as required. </UL><P> 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 termination processing got before the unexpected event occurred.
|
|
.1.3.6.1.4.1.232.0.13601028 |
Severity: Normal -- informational in nature. The Storage System Event Log 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: <UL><LI>0 = No problems found. </UL><P> Note: The content of the ainfo fields, cinfo.sctelcbi structure, and minfo.sctelmi structure is undefined.
|
|
.1.3.6.1.4.1.232.0.13601029 |
Severity: Normal -- informational in nature. The Storage System Event Log 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: <UL><LI>1 = Cookie value is not as expected. <LI>2 = Event data overflows the buffer. <LI>3 = Event data size is not a multiple of 4 bytes, is less than the minimum, or is greater than the maximum. <LI>4 = Event Information Packet type is greater than the maximum. <LI>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. <LI>6 = Event code is zero. <LI>7 = Event is out of sequence. <LI>8 = Dead space area at the end of a partially packed buffer contains a nonzero value. <LI>9 = An event data block containing a nonzero value was found after end of event data was detected. <LI>A = Sequence number reset flag not set as expected. <LI>B = The event log contains no entries. <LI>C = Event data block read failed during maintenance verification. <LI>D = Event data block read failed during maintenance completion. <LI>E = Event data block erase failed during maintenance completion. <LI>F = Control block read failed during maintenance verification. <LI>17= The event log was destroyed and prepared for re-initialization. </UL><P> Note: The content of the ainfo fields, cinfo.sctelcbi structure, and minfo.sctelmi structure is undefined.
|
|
.1.3.6.1.4.1.232.0.13601030 |
Severity: Critical -- failure or failure imminent. Event reports were lost due to an 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.
|
|
.1.3.6.1.4.1.232.0.13601031 |
Severity: Critical -- failure or failure imminent. Event reports were lost due to an 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.
|
|
.1.3.6.1.4.1.232.0.13601032 |
Severity: Normal -- informational in nature. The Storage System Termination 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: <UL><LI>F = Control block read failed during maintenance verification. <LI>10= Control block write failed during maintenance verification. <LI>11= Event data block write failed during maintenance update. <LI>12= Control block write failed during maintenance completion. <LI>13= Storage System Termination Event Log related send was unsuccessful or the master found that the Storage System Termination Event Log is inaccessible. <LI>16= Event data block read failed during retrieval request. </UL><P> Note: The content of the ainfo fields, cinfo.scelcbi structure, and minfo.scelmi structure is undefined.
|
|
.1.3.6.1.4.1.232.0.13601033 |
Severity: Normal -- informational in nature. The Storage System Termination 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: <UL><LI>0 = No problems found. </UL><P> Note: The content of the ainfo fields, cinfo.scelcbi structure, and minfo.scelmi structure is undefined.
|
|
.1.3.6.1.4.1.232.0.13601034 |
Severity: Normal -- informational in nature. The Storage System Termination 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: <UL><LI>F = Control block read failed during maintenance verification. <LI>10= Control block write failed during maintenance verification. <LI>11= Event data block write failed during maintenance update. <LI>12= Control block write failed during maintenance completion. <LI>13= Storage System Termination Event Log related send was unsuccessful or the master found that the Storage System Termination Event Log is inaccessible. <LI>16= Event data block read failed during retrieval request. <LI>17= The log was destroyed and prepared for re-initialization. </UL><P> Note: The content of the ainfo fields, cinfo.scelcbi structure, and minfo.scelmi structure is undefined.
|
|
.1.3.6.1.4.1.232.0.13601035 |
Severity: Normal -- informational in nature. The Storage System Termination 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: <UL><LI>0 = No problems found. </UL><P> Note: The content of the ainfo fields, cinfo.scelcbi structure, and minfo.scelmi structure is undefined.
|
|
.1.3.6.1.4.1.232.0.13601036 |
Severity: Critical -- failure or failure imminent. The Fault Manager on the 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.
|
|
.1.3.6.1.4.1.232.0.13601037 |
Severity: Normal -- informational in nature. The Fault Manager operation 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.
|
|
.1.3.6.1.4.1.232.0.13601038 |
Severity: Undetermined -- more information needed to determine severity. An HSV110 controller sent a last gasp message prior to terminating operation with an indication that the HSV110 controller identified in the lter.terminating_ctrlr field should also terminate operation.
|
|
.1.3.6.1.4.1.232.0.13601039 |
Severity: Normal -- informational in nature. This HSV110 controller sent its termination event information to the HSV110 controller that is 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: <UL><LI>0 = No problems found. </UL><P> Note: The content of the ainfo fields, cinfo.scelcbi structure, and minfo.scelmi structure is undefined.
|
|
.1.3.6.1.4.1.232.0.13601040 |
Severity: Critical -- failure or failure imminent. Event reports were lost due to an insufficient supply of ISR 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.
|
|
.1.3.6.1.4.1.232.0.13601041 |
Severity: Critical -- failure or failure imminent. Event reports were lost due to an insufficient supply of ISR 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.
|
|
.1.3.6.1.4.1.232.0.136011001 |
Agent startup complete
|
|
.1.3.6.1.4.1.232.0.136011002 |
Agent shutdown complete
|
|
.1.3.6.1.4.1.232.0.136011003 |
Insufficient memory to create a new object, Heap may be full!
|
|
.1.3.6.1.4.1.232.0.136011004 |
Agent Startup Failed
|
|
.1.3.6.1.4.1.232.0.136012001 |
Nsc Manager Interface No controllers Found
|
|
.1.3.6.1.4.1.232.0.136012002 |
Nsc Manager Interface Index Out Of Range
|
|
.1.3.6.1.4.1.232.0.136012003 |
Unable to process command at this time. Retry the command or check all connections.
|
|
.1.3.6.1.4.1.232.0.136012004 |
Nsc Manager Interface Initialization Complete
|
|
.1.3.6.1.4.1.232.0.136012005 |
Nsc Manager Interface Initialization Failed
|
|
.1.3.6.1.4.1.232.0.136012008 |
No Disk Groups Available For Access
|
|
.1.3.6.1.4.1.232.0.136013002 |
Notification Mngr Online
|
|
.1.3.6.1.4.1.232.0.136013003 |
Notification Mngr Offline
|
|
.1.3.6.1.4.1.232.0.136013004 |
NM Startup Complete
|
|
.1.3.6.1.4.1.232.0.136013007 |
Notification Failed
|
|
.1.3.6.1.4.1.232.0.136013009 |
Notification Failed - Network Error
|
|
.1.3.6.1.4.1.232.0.136013012 |
NM Prev Failed Notification Successfully Notified
|
|
.1.3.6.1.4.1.232.0.136013015 |
NM SNMP Packet Failed
|
|
.1.3.6.1.4.1.232.0.136013017 |
NM Memory Allocation Error
|
|
.1.3.6.1.4.1.232.0.136013018 |
NM StorageCell handle is NULL
|
|
.1.3.6.1.4.1.232.0.136013019 |
NM User defined event state file is empty
|
|
.1.3.6.1.4.1.232.0.136013020 |
NM Notification Failed - Notification Matrix is NULL
|
|
.1.3.6.1.4.1.232.0.136014001 |
View Already Exists
|
|
.1.3.6.1.4.1.232.0.136014002 |
View Is Not Set
|
|
.1.3.6.1.4.1.232.0.136014003 |
No View Object(s) Found
|
|
.1.3.6.1.4.1.232.0.136014004 |
View Index Is Out Of Range
|
|
.1.3.6.1.4.1.232.0.136014005 |
View Object - Invalid Object Condition
|
|
.1.3.6.1.4.1.232.0.136014006 |
View Object - Invalid Object Type
|
|
.1.3.6.1.4.1.232.0.136014007 |
View List Pointer is NULL
|
|
.1.3.6.1.4.1.232.0.136014008 |
View Object Pointer is NULL
|
|
.1.3.6.1.4.1.232.0.136014009 |
Building View List Object - Complete
|
|
.1.3.6.1.4.1.232.0.136014010 |
Building View List Object - Failed
|
|
.1.3.6.1.4.1.232.0.136014012 |
View Find by UID Failed
|
|
.1.3.6.1.4.1.232.0.136014013 |
View Find by Type Failed
|
|
.1.3.6.1.4.1.232.0.136014017 |
View Find by Type by Name Failed
|
|
.1.3.6.1.4.1.232.0.136015001 |
Tree View Symbol Not Found
|
|
.1.3.6.1.4.1.232.0.136015002 |
Tree View Id Symbol Not Found
|
|
.1.3.6.1.4.1.232.0.136015003 |
Tree Cursor Symbol Not Found
|
|
.1.3.6.1.4.1.232.0.136015004 |
Tree Cursor Id Symbol Not Found
|
|
.1.3.6.1.4.1.232.0.136015005 |
Tree Sibling Symbol Not Found
|
|
.1.3.6.1.4.1.232.0.136015006 |
Tree Total Children Symbol Not Found
|
|
.1.3.6.1.4.1.232.0.136015007 |
Tree Expansion Symbol Not Found
|
|
.1.3.6.1.4.1.232.0.136015008 |
Tree Contraction Symbol Not Found
|
|
.1.3.6.1.4.1.232.0.136015009 |
Tree Invalid Descriptor String
|
|
.1.3.6.1.4.1.232.0.13601536 |
Severity: Critical -- failure or failure imminent. A physical disk drive has 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. The location of the physical disk drive is determined by the content of the dencl_num field as follows: <UL><LI>If dencl_num is less than 99, the location is as indicated by the content of the rack_num, dencl_num, and bay fields. <LI>If dencl_num is equal to 99, the location is unknown. Note that the content of the rack_num and bay fields is undefined in this case. <LI>If dencl_num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the rack_num, dencl_num, and bay fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate. The identity contained in the device field should be used to confirm the last known location values. </UL>Note that the content of 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 obtained from the physical disk drive as a result of the failure prediction threshold exceeded error is contained in the error field. The enclosures array shows the drive enclosures available on the Fibre Channel port identified in the cerp_id field. The location of an available drive enclosure is determined by the content of the enclosures.dencl_num field as follows: <UL><LI>If enclosures.dencl_num is less than 99, the location is as indicated by the content of the enclosures.rack_num and enclosures.dencl_num fields. <LI>If enclosures.dencl_num is equal to 99, the enclosures array entry is not used. Note that the content of the enclosures.rack_num field is undefined in this case. <LI>If enclosures.dencl_num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the enclosures.rack_num and enclosures.dencl_num fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate. </UL>Note that the content of the enclosures.rack_num field will not be valid until a future release.
|
|
.1.3.6.1.4.1.232.0.13601537 |
Severity: Warning -- not failed but attention recommended or required. A Fibre Channel port on the 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 value as follows: <UL><LI>1 - Excessive exchange timeouts on loop <LI>2 - Excessive link errors on loop <LI>3 - Exhausted Link Down retries on loop with signal <LI>4 - Exhausted Link Down retries on loop with loss of signal <LI>5 - Excessive link inits on loop without completing device discovery </UL>
|
|
.1.3.6.1.4.1.232.0.13601538 |
Severity: Normal -- informational in nature. A physical disk drive has 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. The location of the physical disk drive is determined by the content of the dencl_num field as follows: <UL><LI>If dencl_num is less than 99, the location is as indicated by the content of the rack_num, dencl_num, and bay fields. <LI>If dencl_num is equal to 99, the location is unknown. Note that the content of the rack_num and bay fields is undefined in this case. <LI>If dencl_num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the rack_num, dencl_num, and bay fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate. The identity contained in the device field should be used to confirm the last known location values. </UL>Note that the content of 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 obtained from the physical disk drive as a result of the check condition error is contained in the error field. The enclosures array shows the drive enclosures available on the Fibre Channel port identified in the cerp_id field. The location of an available drive enclosure is determined by the content of the enclosures.dencl_num field as follows: <UL><LI>If enclosures.dencl_num is less than 99, the location is as indicated by the content of the enclosures.rack_num and enclosures.dencl_num fields. <LI>If enclosures.dencl_num is equal to 99, the enclosures array entry is not used. Note that the content of the enclosures.rack_num field is undefined in this case. <LI>If enclosures.dencl_num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the enclosures.rack_num and enclosures.dencl_num fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate. </UL>Note that the content of the enclosures.rack_num field will not be valid until a future release.
|
|
.1.3.6.1.4.1.232.0.13601539 |
Severity: Warning -- not failed but attention recommended or required. An exchange sent to a physical disk drive or another HSV110 controller via the mirror port or a Fibre Channel port 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. The missing_port and missing_cerp_id fields are unused. The location of the intended recipient is determined by the content of the dencl_num field as follows: <UL><LI>If dencl_num is less than 99, the location is as indicated by the content of the rack_num, dencl_num, and bay fields. <LI>If dencl_num is equal to 99, the location is unknown. Note that the content of the rack_num and bay fields is undefined in this case. <LI>If dencl_num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the rack_num, dencl_num, and bay fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate. The identity contained in the device field should be used to confirm the last known location values. </UL>Note that the content of the rack_num field will not be valid until a future release. The number of timeouts detected is contained in the num_times field. The enclosures array shows the drive enclosures available on the Fibre Channel port identified in the cerp_id field. The location of an available drive enclosure is determined by the content of the enclosures.dencl_num field as follows: <UL><LI>If enclosures.dencl_num is less than 99, the location is as indicated by the content of the enclosures.rack_num and enclosures.dencl_num fields. <LI>If enclosures.dencl_num is equal to 99, the enclosures array entry is not used. Note that the content of the enclosures.rack_num field is undefined in this case. <LI>If enclosures.dencl_num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the enclosures.rack_num and enclosures.dencl_num fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate. </UL>Note that the content of the enclosures.rack_num field will not be valid until a future release.
|
|
.1.3.6.1.4.1.232.0.13601540 |
Severity: Warning -- not failed but attention recommended or required. Work was unexpectedly sent to 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. The location of the sender is determined by the content of the dencl_num field as follows: <UL><LI>If dencl_num is less than 99, the location is as indicated by the content of the rack_num, dencl_num, and bay fields. <LI>If dencl_num is equal to 99, the location is unknown. Note that the content of the rack_num and bay fields is undefined in this case. <LI>If dencl_num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the rack_num, dencl_num, and bay fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate. The identity contained in the device field should be used to confirm the last known location values. </UL>Note that the content of 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.
|
|
.1.3.6.1.4.1.232.0.13601541 |
Severity: Warning -- not failed but attention recommended or required. Work has been sent to a physical 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. The location of the intended target is determined by the content of the dencl_num field as follows: <UL><LI>If dencl_num is less than 99, the location is as indicated by the content of the rack_num, dencl_num, and bay fields. <LI>If dencl_num is equal to 99, the location is unknown. Note that the content of the rack_num and bay fields is undefined in this case. <LI>If dencl_num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the rack_num, dencl_num, and bay fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate. The identity contained in the device field should be used to confirm the last known location values. </UL>Note that the content of 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 cmd field. Note that in this case the content of the error field is undefined. The enclosures array shows the drive enclosures available on the Fibre Channel port identified in the cerp_id field. The location of an available drive enclosure is determined by the content of the enclosures.dencl_num field as follows: <UL><LI>If enclosures.dencl_num is less than 99, the location is as indicated by the content of the enclosures.rack_num and enclosures.dencl_num fields. <LI>If enclosures.dencl_num is equal to 99, the enclosures array entry is not used. Note that the content of the enclosures.rack_num field is undefined in this case. <LI>If enclosures.dencl_num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the enclosures.rack_num and enclosures.dencl_num fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate. </UL>Note that the content of the enclosures.rack_num field will not be valid until a future release.
|
|
.1.3.6.1.4.1.232.0.13601543 |
Severity: Warning -- not failed but attention recommended or required. A Target Discovery Service Descriptor exchange 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. The location of the physical disk drive is determined by the content of the dencl_num field as follows: <UL><LI>If dencl_num is less than 99, the location is as indicated by the content of the rack_num, dencl_num, and bay fields. <LI>If dencl_num is equal to 99, the location is unknown. Note that the content of the rack_num and bay fields is undefined in this case. <LI>If dencl_num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the rack_num, dencl_num, and bay fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate. The identity contained in the device field should be used to confirm the last known location values. </UL>Note that the content of 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. The enclosures array shows the drive enclosures available on the Fibre Channel port identified in the cerp_id field. The location of an available drive enclosure is determined by the content of the enclosures.dencl_num field as follows: <UL><LI>If enclosures.dencl_num is less than 99, the location is as indicated by the content of the enclosures.rack_num and enclosures.dencl_num fields. <LI>If enclosures.dencl_num is equal to 99, the enclosures array entry is not used. Note that the content of the enclosures.rack_num field is undefined in this case. <LI>If enclosures.dencl_num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the enclosures.rack_num and enclosures.dencl_num fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate. </UL>Note that the content of the enclosures.rack_num field will not be valid until a future release.
|
|
.1.3.6.1.4.1.232.0.13601544 |
Severity: Normal -- informational in nature. An excessive number of link 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 periodically.
|
|
.1.3.6.1.4.1.232.0.13601545 |
Severity: Critical -- failure or failure imminent. A physical disk drive has 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. The missing_port and missing_cerp_id fields are unused. The location of the physical disk drive is determined by the content of the dencl_num field as follows: <UL><LI>If dencl_num is less than 99, the location is as indicated by the content of the rack_num, dencl_num, and bay fields. <LI>If dencl_num is equal to 99, the location is unknown. Note that the content of the rack_num and bay fields is undefined in this case. <LI>If dencl_num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the rack_num, dencl_num, and bay fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate. The identity contained in the device field should be used to confirm the last known location values. </UL>Note that the content of 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 threshold exceeded errors reported by the physical disk drive in the previous minute. The enclosures array shows the drive enclosures available on the Fibre Channel port identified in the cerp_id field. The location of an available drive enclosure is determined by the content of the enclosures.dencl_num field as follows: <UL><LI>If enclosures.dencl_num is less than 99, the location is as indicated by the content of the enclosures.rack_num and enclosures.dencl_num fields. <LI>If enclosures.dencl_num is equal to 99, the enclosures array entry is not used. Note that the content of the enclosures.rack_num field is undefined in this case. <LI>If enclosures.dencl_num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the enclosures.rack_num and enclosures.dencl_num fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate. </UL>Note that the content of the enclosures.rack_num field will not be valid until a future release.
|
|
.1.3.6.1.4.1.232.0.13601546 |
Severity: Normal -- informational in nature. A physical disk drive has 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. The missing_port and missing_cerp_id fields are unused. The location of the physical disk drive is determined by the content of the dencl_num field as follows: <UL><LI>If dencl_num is less than 99, the location is as indicated by the content of the rack_num, dencl_num, and bay fields. <LI>If dencl_num is equal to 99, the location is unknown. Note that the content of the rack_num and bay fields is undefined in this case. <LI>If dencl_num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the rack_num, dencl_num, and bay fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate. The identity contained in the device field should be used to confirm the last known location values. </UL>Note that the content of 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. The enclosures array shows the drive enclosures available on the Fibre Channel port identified in the cerp_id field. The location of an available drive enclosure is determined by the content of the enclosures.dencl_num field as follows: <UL><LI>If enclosures.dencl_num is less than 99, the location is as indicated by the content of the enclosures.rack_num and enclosures.dencl_num fields. <LI>If enclosures.dencl_num is equal to 99, the enclosures array entry is not used. Note that the content of the enclosures.rack_num field is undefined in this case. <LI>If enclosures.dencl_num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the enclosures.rack_num and enclosures.dencl_num fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate. </UL>Note that the content of the enclosures.rack_num field will not be valid until a future release.
|
|
.1.3.6.1.4.1.232.0.13601547 |
Severity: Warning -- not failed but attention recommended or required. A non-data exchange 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. The location of the physical disk drive is determined by the content of the dencl_num field as follows: <UL><LI>If dencl_num is less than 99, the location is as indicated by the content of the rack_num, dencl_num, and bay fields. <LI>If dencl_num is equal to 99, the location is unknown. Note that the content of the rack_num and bay fields is undefined in this case. <LI>If dencl_num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the rack_num, dencl_num, and bay fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate. The identity contained in the device field should be used to confirm the last known location values. </UL>Note that the content of 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. The enclosures array shows the drive enclosures available on the Fibre Channel port identified in the cerp_id field. The location of an available drive enclosure is determined by the content of the enclosures.dencl_num field as follows: <UL><LI>If enclosures.dencl_num is less than 99, the location is as indicated by the content of the enclosures.rack_num and enclosures.dencl_num fields. <LI>If enclosures.dencl_num is equal to 99, the enclosures array entry is not used. Note that the content of the enclosures.rack_num field is undefined in this case. <LI>If enclosures.dencl_num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the enclosures.rack_num and enclosures.dencl_num fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate. </UL>Note that the content of the enclosures.rack_num field will not be valid until a future release.
|
|
.1.3.6.1.4.1.232.0.13601548 |
Severity: Normal -- informational in nature. A loop switch has been detected 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 content of the device, al_pa, rack_num, dencl_num, bay, fed_class and num_times fields is undefined. The enclosures array shows the drive enclosures available on the Fibre Channel port identified in the cerp_id field. The missing_port and missing_cerp_id fields are unused. The location of an available drive enclosure is determined by the content of the enclosures.dencl_num field as follows: <UL><LI>If enclosures.dencl_num is less than 99, the location is as indicated by the content of the enclosures.rack_num and enclosures.dencl_num fields. <LI>If enclosures.dencl_num is equal to 99, the enclosures array entry is not used. Note that the content of the enclosures.rack_num field is undefined in this case. <LI>If enclosures.dencl_num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the enclosures.rack_num and enclosures.dencl_num fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate. </UL>Note that the content of the enclosures.rack_num field will not be valid until a future release.
|
|
.1.3.6.1.4.1.232.0.13601549 |
Severity: Normal -- informational in nature. The location of a physical disk 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 missing_port and missing_cerp_id fields are unused. The location of the physical disk drive is contained in the rack_num, dencl_num, and bay fields. Note that the content of the rack_num field will not be valid until a future release. Note also that in this case the content of fed_class, al_pa and num_times fields are undefined. The enclosures array shows the drive enclosures available on the Fibre Channel port identified in the cerp_id field. The location of an available drive enclosure is determined by the content of the enclosures.dencl_num field as follows: <UL><LI>If enclosures.dencl_num is less than 99, the location is as indicated by the content of the enclosures.rack_num and enclosures.dencl_num fields. <LI>If enclosures.dencl_num is equal to 99, the enclosures array entry is not used. Note that the content of the enclosures.rack_num field is undefined in this case. <LI>If enclosures.dencl_num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the enclosures.rack_num and enclosures.dencl_num fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate. </UL>Note that the content of the enclosures.rack_num field will not be valid until a future release.
|
|
.1.3.6.1.4.1.232.0.13601550 |
Severity: Critical -- failure or failure imminent. A Drive Enclosure Environmental 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 missing_port and missing_cerp_id fields are unused. The location of the Drive Enclosure Environmental Monitoring Unit is contained in the rack_num and dencl_num fields. Note that the content of the rack_num field will not be valid until a future release. Note also that in this case the content of the al_pa, bay, fed_class and num_times field is undefined. The enclosures array shows the drive enclosures available on the Fibre Channel port identified in the cerp_id field. The location of an available drive enclosure is determined by the content of the enclosures.dencl_num field as follows: <UL><LI>If enclosures.dencl_num is less than 99, the location is as indicated by the content of the enclosures.rack_num and enclosures.dencl_num fields. <LI>If enclosures.dencl_num is equal to 99, the enclosures array entry is not used. Note that the content of the enclosures.rack_num field is undefined in this case. <LI>If enclosures.dencl_num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the enclosures.rack_num and enclosures.dencl_num fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate. </UL>Note that the content of the enclosures.rack_num field will not be valid until a future release.
|
|
.1.3.6.1.4.1.232.0.13601551 |
Severity: Critical -- failure or failure imminent. The Drive Enclosure 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 missing_port and missing_cerp_id fields are unused. The location of the physical disk drive is contained in the rack_num, dencl_num, and bay fields. Note that the content of the rack_num field will not be valid until a future release. Note also that in this case the content of the al_pa, fed_class and num_times fields is undefined. The enclosures array shows the drive enclosures available on the Fibre Channel port identified in the cerp_id field. The location of an available drive enclosure is determined by the content of the enclosures.dencl_num field as follows: <UL><LI>If enclosures.dencl_num is less than 99, the location is as indicated by the content of the enclosures.rack_num and enclosures.dencl_num fields. <LI>If enclosures.dencl_num is equal to 99, the enclosures array entry is not used. Note that the content of the enclosures.rack_num field is undefined in this case. <LI>If enclosures.dencl_num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the enclosures.rack_num and enclosures.dencl_num fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate. </UL>Note that the content of the enclosures.rack_num field will not be valid until a future release.
|
|
.1.3.6.1.4.1.232.0.13601552 |
Severity: Undetermined -- more information needed to determine severity. A HSV110 controller is unable to communicate with this Drive Enclosure Environmental Monitoring Unit. The Drive Enclosure Environmental Monitoring Unit identified in the device field has stopped communicating with the HSV110 controller. 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 missing_port and missing_cerp_id fields are unused. The location of the Drive Enclosure Environmental Monitoring Unit is contained in the rack_num and dencl_num fields. Note that the content of the rack_num field will not be valid until a future release. Note also that in this case the content of the bay, al_pa, fed_class and num_times fields is undefined. The enclosures array shows the drive enclosures available on the Fibre Channel port identified in the cerp_id field. The location of an available drive enclosure is determined by the content of the enclosures.dencl_num field as follows: <UL><LI>If enclosures.dencl_num is less than 99, the location is as indicated by the content of the enclosures.rack_num and enclosures.dencl_num fields. <LI>If enclosures.dencl_num is equal to 99, the enclosures array entry is not used. Note that the content of the enclosures.rack_num field is undefined in this case. <LI>If enclosures.dencl_num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the enclosures.rack_num and enclosures.dencl_num fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate. </UL>Note that the content of the enclosures.rack_num field will not be valid until a future release.
|
|
.1.3.6.1.4.1.232.0.13601554 |
Severity: Normal -- informational in nature. The retry count for a task 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 Drive Enclosure Environmental Monitoring Unit.
|
|
.1.3.6.1.4.1.232.0.13601555 |
Severity: Normal -- informational in nature. A Drive Enclosure Environmental 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 missing_port and missing_cerp_id fields are unused. The location of the Drive Enclosure Environmental Monitoring Unit is contained in the rack_num and dencl_num fields. Note that the content of the rack_num field will not be valid until a future release. Note also that in this case the content of the bay, fed_class and num_times fields is undefined. The enclosures array shows the drive enclosures available on the Fibre Channel port identified in the cerp_id field. The location of an available drive enclosure is determined by the content of the enclosures.dencl_num field as follows: <UL><LI>If enclosures.dencl_num is less than 99, the location is as indicated by the content of the enclosures.rack_num and enclosures.dencl_num fields. <LI>If enclosures.dencl_num is equal to 99, the enclosures array entry is not used. Note that the content of the enclosures.rack_num field is undefined in this case. <LI>If enclosures.dencl_num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the enclosures.rack_num and enclosures.dencl_num fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate. </UL>Note that the content of the enclosures.rack_num field will not be valid until a future release.
|
|
.1.3.6.1.4.1.232.0.13601556 |
Severity: Critical -- failure or failure imminent. There are too many drive enclosures attached to a Fibre Channel port. 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. The enclosures array shows the drive enclosures available on the Fibre Channel port identified in the cerp_id field. The missing_port and missing_cerp_id fields are unused. The location of the identified in the cerp_id field. The device, missing_port and missing_cerp_id fields are unused. The location of the physical disk drive is determined by the content of the dencl_num field as follows: <UL><LI>If enclosures.dencl_num is less than 99, the location is as indicated by the content of the enclosures.rack_num and enclosures.dencl_num fields. <LI>If enclosures.dencl_num is equal to 99, the enclosures array entry is not used. Note that the content of the enclosures.rack_num field is undefined in this case. <LI>If enclosures.dencl_num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the enclosures.rack_num and enclosures.dencl_num fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate. </UL>Note that the content of the enclosures.rack_num field will not be valid until a future release.
|
|
.1.3.6.1.4.1.232.0.13601557 |
Severity: Critical -- failure or failure imminent. The cable connected to the I/O 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 device, missing_port, missing_cerp_id, bay, fed_class, rack_num, dencl_num and num_times fields is undefined. The enclosures array shows the drive enclosures available on the Fibre Channel port identified in the cerp_id field. The location of an available drive enclosure is determined by the content of the enclosures.dencl_num field as follows: <UL><LI>If enclosures.dencl_num is less than 99, the location is as indicated by the content of the enclosures.rack_num and enclosures.dencl_num fields. <LI>If enclosures.dencl_num is equal to 99, the enclosures array entry is not used. Note that the content of the enclosures.rack_num field is undefined in this case. <LI>If enclosures.dencl_num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the enclosures.rack_num and enclosures.dencl_num fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate. </UL>Note that the content of the enclosures.rack_num field will not be valid until a future release.
|
|
.1.3.6.1.4.1.232.0.13601558 |
Severity: Critical -- failure or failure imminent. A HSV110 controller does not have an address on the enclosure address bus. The HSV110 controller location cannot be identified. Note that in this case the content of the missing_port, missing_cerp_id, bay, fed_class, rack_num, dencl_num, al_pa, device, cerp_id, port, enclosures array and num_times fields is undefined.
|
|
.1.3.6.1.4.1.232.0.13601560 |
Severity: Normal -- informational in nature. A Drive Enclosure Environmental 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 missing_port and missing_cerp_id fields are unused. The location of the Drive Enclosure Environmental Monitoring Unit is determined by the content of the dencl_num field as follows: <UL><LI>If dencl_num is less than 99, the location is as indicated by the content of the rack_num and dencl_num fields. <LI>If dencl_num is equal to 99, the location is unknown. Note that the content of the rack_num field is undefined in this case. In addition, the device field may contain all zeroes. <LI>If dencl_num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the rack_num and dencl_num fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate. The identity contained in the device field should be used to confirm the last known location values. </UL>Note that the content of the rack_num field will not be valid until a future release. Note also that the content of the fed_class, al_pa, and num_times fields is undefined. The enclosures array shows the drive enclosures available on the Fibre Channel port identified in the cerp_id field. The location of an available drive enclosure is determined by the content of the enclosures.dencl_num field as follows: <UL><LI>If enclosures.dencl_num is less than 99, the location is as indicated by the content of the enclosures.rack_num and enclosures.dencl_num fields. <LI>If enclosures.dencl_num is equal to 99, the enclosures array entry is not used. Note that the content of the enclosures.rack_num field is undefined in this case. <LI>If enclosures.dencl_num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the enclosures.rack_num and enclosures.dencl_num fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate. </UL>Note that the content of the enclosures.rack_num field will not be valid until a future release.
|
|
.1.3.6.1.4.1.232.0.13601561 |
Severity: Normal -- informational in nature. A Drive Enclosure Environmental 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 missing_port and missing_cerp_id fields are unused. The location of the Drive Enclosure Environmental Monitoring Unit is contained in the rack_num and dencl_num fields. Note that the content of the rack_num field will not be valid until a future release. Note also that in this case the content of the fed_class, al_pa, and num_times fields is undefined. The enclosures array shows the drive enclosures available on the Fibre Channel port identified in the cerp_id field. The location of an available drive enclosure is determined by the content of the enclosures.dencl_num field as follows: <UL><LI>If enclosures.dencl_num is less than 99, the location is as indicated by the content of the enclosures.rack_num and enclosures.dencl_num fields. <LI>If enclosures.dencl_num is equal to 99, the enclosures array entry is not used. Note that the content of the enclosures.rack_num field is undefined in this case. <LI>If enclosures.dencl_num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the enclosures.rack_num and enclosures.dencl_num fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate. </UL>Note that the content of the enclosures.rack_num field will not be valid until a future release.
|
|
.1.3.6.1.4.1.232.0.13601562 |
Severity: Critical -- failure or failure imminent. A physical disk drive has 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. The location of the physical disk drive is determined by the content of the dencl_num field as follows: <UL><LI>If dencl_num is less than 99, the location is as indicated by the content of the rack_num, dencl_num, and bay fields. <LI>If dencl_num is equal to 99, the location is unknown. Note that the content of the rack_num and bay fields is undefined in this case. <LI>If dencl_num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the rack_num, dencl_num, and bay fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate. The identity contained in the device field should be used to confirm the last known location values. </UL>Note that the content of the rack_num field will not be valid until a future release. Note also that in this case the content of the fed_class, cdb, and sense_data fields is undefined. The enclosures array shows the drive enclosures available on the Fibre Channel port identified in the cerp_id field. The location of an available drive enclosure is determined by the content of the enclosures.dencl_num field as follows: <UL><LI>If enclosures.dencl_num is less than 99, the location is as indicated by the content of the enclosures.rack_num and enclosures.dencl_num fields. <LI>If enclosures.dencl_num is equal to 99, the enclosures array entry is not used. Note that the content of the enclosures.rack_num field is undefined in this case. <LI>If enclosures.dencl_num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the enclosures.rack_num and enclosures.dencl_num fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate. </UL>Note that the content of the enclosures.rack_num field will not be valid until a future release.
|
|
.1.3.6.1.4.1.232.0.13601563 |
Severity: Normal -- informational in nature. A HSV110 controller now has an 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. Note that the content of the rack_num field will not be valid until a future release. Note also that in this case the content of the bay, fed_class, al_pa, cerp_id, port, and num_times fields is undefined. The enclosures array shows the drive enclosures available on the Fibre Channel port identified in the cerp_id field. The missing_port and missing_cerp_id fields are unused. The location of an available drive enclosure is determined by the content of the enclosures.dencl_num field as follows: <UL><LI>If enclosures.dencl_num is less than 99, the location is as indicated by the content of the enclosures.rack_num and enclosures.dencl_num fields. <LI>If enclosures.dencl_num is equal to 99, the enclosures array entry is not used. Note that the content of the enclosures.rack_num field is undefined in this case. <LI>If enclosures.dencl_num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the enclosures.rack_num and enclosures.dencl_num fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate. </UL>Note that the content of the enclosures.rack_num field will not be valid until a future release.
|
|
.1.3.6.1.4.1.232.0.13601564 |
Severity: Warning -- not failed but attention recommended or required. An outbound frame targeted 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. The location of the physical disk drive is determined by the content of the dencl_num field as follows: <UL><LI>If dencl_num is less than 99, the location is as indicated by the content of the rack_num, dencl_num, and bay fields. <LI>If dencl_num is equal to 99, the location is unknown. Note that the content of the rack_num and bay fields is undefined in this case. <LI>If dencl_num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the rack_num, dencl_num, and bay fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate. The identity contained in the device field should be used to confirm the last known location values. </UL>Note that the content of 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. The enclosures array shows the drive enclosures available on the Fibre Channel port identified in the cerp_id field. The location of an available drive enclosure is determined by the content of the enclosures.dencl_num field as follows: <UL><LI>If enclosures.dencl_num is less than 99, the location is as indicated by the content of the enclosures.rack_num and enclosures.dencl_num fields. <LI>If enclosures.dencl_num is equal to 99, the enclosures array entry is not used. Note that the content of the enclosures.rack_num field is undefined in this case. <LI>If enclosures.dencl_num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the enclosures.rack_num and enclosures.dencl_num fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate. </UL>Note that the content of the enclosures.rack_num field will not be valid until a future release.
|
|
.1.3.6.1.4.1.232.0.13601565 |
Severity: Warning -- not failed but attention recommended or required. A Fibre Channel exchange to a physical disk drive has completed but is missing data. 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 determined by the content of the dencl_num field as follows: <UL><LI>If dencl_num is less than 99, the location is as indicated by the content of the rack_num, dencl_num, and bay fields. <LI>If dencl_num is equal to 99, the location is unknown. Note that the content of the rack_num and bay fields is undefined in this case. <LI>If dencl_num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the rack_num, dencl_num, and bay fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate. The identity contained in the device field should be used to confirm the last known location values. </UL>Note that the content of 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. The enclosures array shows the drive enclosures available on the Fibre Channel port identified in the cerp_id field. The location of an available drive enclosure is determined by the content of the enclosures.dencl_num field as follows: <UL><LI>If enclosures.dencl_num is less than 99, the location is as indicated by the content of the enclosures.rack_num and enclosures.dencl_num fields. <LI>If enclosures.dencl_num is equal to 99, the enclosures array entry is not used. Note that the content of the enclosures.rack_num field is undefined in this case. <LI>If enclosures.dencl_num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the enclosures.rack_num and enclosures.dencl_num fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate. </UL>Note that the content of the enclosures.rack_num field will not be valid until a future release.
|
|
.1.3.6.1.4.1.232.0.13601566 |
Severity: Critical -- failure or failure imminent. A HSV110 controller has detected only one port of a Fibre Channel device. This Fibre Channel device has entered the Single Port on Fibre state which should be corrected as soon as possible. The identity of the Fibre Channel device is contained in the device field. The Fibre Channel port still able to communicate with the Fibre Channel device is contained in the cerp_id field. The HSV110 controller internal Fibre Channel port number able to communicate with the Fibre Channel device is contained in the port field. The Fibre Channel port unable to communicate with the Fibre Channel device is contained in the missing_cerp_id field. The HSV110 controller internal Fibre Channel port number unable to communicate with the Fibre Channel device is contained in the missing_port field. The arbitrated loop physical address of the Fibre Channel device is contained in the al_pa field. The location of the Fibre Channel device is determined by the content of the dencl_num field as follows: <UL><LI>If dencl_num is less than 99, the location is as indicated by the content of the rack_num, dencl_num, and bay fields. <LI>If dencl_num is equal to 99, the location is unknown. Note that the content of the rack_num and bay fields is undefined in this case. <LI>If dencl_num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the rack_num, dencl_num, and bay fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate. The identity contained in the device field should be used to confirm the last known location values. </UL>Note that the content of the rack_num field will not be valid until a future release. Note also that in this case the content of the fed_class, and num_times fields is undefined. The enclosures array shows the drive enclosures available on the Fibre Channel port identified in the cerp_id field. The location of an available drive enclosure is determined by the content of the enclosures.dencl_num field as follows: <UL><LI>If enclosures.dencl_num is less than 99, the location is as indicated by the content of the enclosures.rack_num and enclosures.dencl_num fields. <LI>If enclosures.dencl_num is equal to 99, the enclosures array entry is not used. Note that the content of the enclosures.rack_num field is undefined in this case. <LI>If enclosures.dencl_num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the enclosures.rack_num and enclosures.dencl_num fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate. </UL>Note that the content of the enclosures.rack_num field will not be valid until a future release.
|
|
.1.3.6.1.4.1.232.0.13601567 |
Severity: Normal -- informational in nature. A previously reported Fibre Channel device with only one port has been corrected and redundancy has been restored. The device is no longer in the Single Port on Fibre state. The identity of the Fibre Channel device is contained in the device field. The Fibre Channel port used to communicate with the Fibre Channel device is contained in the cerp_id field. The HSV110 controller internal Fibre Channel port number used to communicate with the Fibre Channel device is contained in the port field. The missing_port and missing_cerp_id fields are unused. The arbitrated loop physical address of the Fibre Channel device is contained in the al_pa field. The location of the Fibre Channel device is determined by the content of the dencl_num field as follows: <UL><LI>If dencl_num is less than 99, the location is as indicated by the content of the rack_num, dencl_num, and bay fields. <LI>If dencl_num is equal to 99, the location is unknown. Note that the content of the rack_num and bay fields is undefined in this case. <LI>If dencl_num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the rack_num, dencl_num, and bay fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate. The identity contained in the device field should be used to confirm the last known location values. </UL>Note that the content of the rack_num field will not be valid until a future release. Note also that in this case the content of the fed_class, and num_times fields is undefined. The enclosures array shows the drive enclosures available on the Fibre Channel port identified in the cerp_id field. The location of an available drive enclosure is determined by the content of the enclosures.dencl_num field as follows: <UL><LI>If enclosures.dencl_num is less than 99, the location is as indicated by the content of the enclosures.rack_num and enclosures.dencl_num fields. <LI>If enclosures.dencl_num is equal to 99, the enclosures array entry is not used. Note that the content of the enclosures.rack_num field is undefined in this case. <LI>If enclosures.dencl_num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the enclosures.rack_num and enclosures.dencl_num fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate. </UL>Note that the content of the enclosures.rack_num field will not be valid until a future release.
|
|
.1.3.6.1.4.1.232.0.13601568 |
Severity: Critical -- failure or failure imminent. An unsupported Fibre Channel device has been detected. The drive has been failed to prevent possible data corruption or system instability. The identity of the Fibre Channel device is contained in the device field. The Fibre Channel port used to communicate with the Fibre Channel device is contained in the cerp_id field. The HSV110 controller internal Fibre Channel port number used to communicate with the Fibre Channel device is contained in the port field. The arbitrated loop physical address of the Fibre Channel device is contained in the al_pa field. The missing_port and missing_cerp_id fields are unused. The location of the Fibre Channel device is determined by the content of the dencl_num field as follows: <UL><LI>If dencl_num is less than 99, the location is as indicated by the content of the rack_num, dencl_num, and bay fields. <LI>If dencl_num is equal to 99, the location is unknown. Note that the content of the rack_num and bay fields is undefined in this case. <LI>If dencl_num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the rack_num, dencl_num, and bay fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate. The identity contained in the device field should be used to confirm the last known location values. </UL>Note that the content of the rack_num field will not be valid until a future release. Note also that in this case the content of the fed_class and num_times fields is undefined. The enclosures array shows the drive enclosures available on the Fibre Channel port identified in the cerp_id field. The location of an available drive enclosure is determined by the content of the enclosures.dencl_num field as follows: <UL><LI>If enclosures.dencl_num is less than 99, the location is as indicated by the content of the enclosures.rack_num and enclosures.dencl_num fields. <LI>If enclosures.dencl_num is equal to 99, the enclosures array entry is not used. Note that the content of the enclosures.rack_num field is undefined in this case. <LI>If enclosures.dencl_num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the enclosures.rack_num and enclosures.dencl_num fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate. </UL>Note that the content of the enclosures.rack_num field will not be valid until a future release.
|
|
.1.3.6.1.4.1.232.0.13601569 |
Severity: Normal -- informational in nature. A Fibre Channel device with the incorrect block size has been detected. The identity of the Fibre Channel device is contained in the device field. The Fibre Channel port used to communicate with the Fibre Channel device is contained in the cerp_id field. The HSV110 controller internal Fibre Channel port number used to communicate with the Fibre Channel device is contained in the port field. The arbitrated loop physical address of the Fibre Channel device is contained in the al_pa field. The missing_port and missing_cerp_id fields are unused. The location of the Fibre Channel device is determined by the content of the dencl_num field as follows: <UL><LI>If dencl_num is less than 99, the location is as indicated by the content of the rack_num, dencl_num, and bay fields. <LI>If dencl_num is equal to 99, the location is unknown. Note that the content of the rack_num and bay fields is undefined in this case. <LI>If dencl_num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the rack_num, dencl_num, and bay fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate. The identity contained in the device field should be used to confirm the last known location values. </UL>Note that the content of the rack_num field will not be valid until a future release. Note also that in this case the content of the fed_class and num_times fields is undefined. The enclosures array shows the drive enclosures available on the Fibre Channel port identified in the cerp_id field. The location of an available drive enclosure is determined by the content of the enclosures.dencl_num field as follows: <UL><LI>If enclosures.dencl_num is less than 99, the location is as indicated by the content of the enclosures.rack_num and enclosures.dencl_num fields. <LI>If enclosures.dencl_num is equal to 99, the enclosures array entry is not used. Note that the content of the enclosures.rack_num field is undefined in this case. <LI>If enclosures.dencl_num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the enclosures.rack_num and enclosures.dencl_num fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate. </UL>Note that the content of the enclosures.rack_num field will not be valid until a future release.
|
|
.1.3.6.1.4.1.232.0.13601571 |
Severity: Normal -- informational in nature. A HSV110 controller is about to retry a failed port. The Fibre Channel port that is about to be retried is contained in the cerp_id field. The HSV110 controller internal Fibre Channel port number about to be retried is contained in the port field. Note that in this case the content of the bay, rack_num, fed_class, al_pa, dencl_num, device, and num_times fields is undefined. The enclosures array shows the drive enclosures available on the Fibre Channel port identified in the cerp_id field. The missing_port and missing_cerp_id fields are unused. The location of an available drive enclosure is determined by the content of the enclosures.dencl_num field as follows: <UL><LI>If enclosures.dencl_num is less than 99, the location is as indicated by the content of the enclosures.rack_num and enclosures.dencl_num fields. <LI>If enclosures.dencl_num is equal to 99, the enclosures array entry is not used. Note that the content of the enclosures.rack_num field is undefined in this case. <LI>If enclosures.dencl_num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the enclosures.rack_num and enclosures.dencl_num fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate. </UL>Note that the content of the enclosures.rack_num field will not be valid until a future release.
|
|
.1.3.6.1.4.1.232.0.13601572 |
Severity: Normal -- informational in nature. A HSV110 controller has successfully retried a failed port. The Fibre Channel port that has been restarted is contained in the cerp_id field. The HSV110 controller internal Fibre Channel port number that has been restarted is contained in the port field. Note that in this case the content of the bay, rack_num, fed_class, al_pa, dencl_num, device, and num_times fields is undefined. The enclosures array shows the drive enclosures available on the Fibre Channel port identified in the cerp_id field. The missing_port and missing_cerp_id fields are unused. The location of an available drive enclosure is determined by the content of the enclosures.dencl_num field as follows: <UL><LI>If enclosures.dencl_num is less than 99, the location is as indicated by the content of the enclosures.rack_num and enclosures.dencl_num fields. <LI>If enclosures.dencl_num is equal to 99, the enclosures array entry is not used. Note that the content of the enclosures.rack_num field is undefined in this case. <LI>If enclosures.dencl_num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the enclosures.rack_num and enclosures.dencl_num fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate. </UL>Note that the content of the enclosures.rack_num field will not be valid until a future release.
|
|
.1.3.6.1.4.1.232.0.13601573 |
Severity: Critical -- failure or failure imminent. A Drive Enclosure Environmental Monitoring Unit has failed to assign a hard address to a physical disk drive on the loop. The device field contains the identity of the enclosure. 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 al_pa field contains the expected AL_PA, and the num_times field contains the actual AL_PA. The missing_port and missing_cerp_id fields are unused. The location of the physical disk drive is determined by the content of the dencl_num field as follows: <UL><LI>If dencl_num is less than 99, the location is as indicated by the content of the rack_num, dencl_num, and bay fields. <LI>If dencl_num is equal to 99, the location is unknown. Note that the content of the rack_num and bay fields is undefined in this case. <LI>If dencl_num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the rack_num, dencl_num, and bay fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate. The identity contained in the device field should be used to confirm the last known location values. </UL>Note that the content of the rack_num field will not be valid until a future release. Note that in this case the content of the fed_class is undefined. The enclosures array shows the drive enclosures available on the Fibre Channel port identified in the cerp_id field. The location of an available drive enclosure is determined by the content of the enclosures.dencl_num field as follows: <UL><LI>If enclosures.dencl_num is less than 99, the location is as indicated by the content of the enclosures.rack_num and enclosures.dencl_num fields. <LI>If enclosures.dencl_num is equal to 99, the enclosures array entry is not used. Note that the content of the enclosures.rack_num field is undefined in this case. <LI>If enclosures.dencl_num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the enclosures.rack_num and enclosures.dencl_num fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate. </UL>Note that the content of the enclosures.rack_num field will not be valid until a future release.
|
|
.1.3.6.1.4.1.232.0.13601574 |
Severity: Critical -- failure or failure imminent. A Drive Enclosure Environmental Monitoring Unit has failed to assign an address to a physical disk drive on the loop. This has occurred because another physical disk drive has already obtained this AL_PA. The device field contains the identity of the enclosure. 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 al_pa field contains the AL_PA that was stolen. The missing_port and missing_cerp_id fields are unused. The location of the physical disk drive is determined by the content of the dencl_num field as follows: <UL><LI>If dencl_num is less than 99, the location is as indicated by the content of the rack_num, dencl_num, and bay fields. <LI>If dencl_num is equal to 99, the location is unknown. Note that the content of the rack_num and bay fields is undefined in this case. <LI>If dencl_num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the rack_num, dencl_num, and bay fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate. The identity contained in the device field should be used to confirm the last known location values. </UL>Note that the content of the rack_num field will not be valid until a future release. Note also that in this case the content of the fed_class and num_times fields is undefined. The enclosures array shows the drive enclosures available on the Fibre Channel port identified in the cerp_id field. The location of an available drive enclosure is determined by the content of the enclosures.dencl_num field as follows: <UL><LI>If enclosures.dencl_num is less than 99, the location is as indicated by the content of the enclosures.rack_num and enclosures.dencl_num fields. <LI>If enclosures.dencl_num is equal to 99, the enclosures array entry is not used. Note that the content of the enclosures.rack_num field is undefined in this case. <LI>If enclosures.dencl_num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the enclosures.rack_num and enclosures.dencl_num fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate. </UL>Note that the content of the enclosures.rack_num field will not be valid until a future release.
|
|
.1.3.6.1.4.1.232.0.13601575 |
Severity: Critical -- failure or failure imminent. A Drive Enclosure Environmental Monitoring Unit has failed to assign address(s) to a physical disk drive on the loop. Soft addressing was detected for this enclosure. The device field contains the identity of the enclosure. 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 missing_port and missing_cerp_id fields are unused. The location of the physical disk drive is determined by the content of the dencl_num field as follows: <UL><LI>If dencl_num is less than 99, the location is as indicated by the content of the rack_num, dencl_num, and bay fields. <LI>If dencl_num is equal to 99, the location is unknown. Note that the content of the rack_num and bay fields is undefined in this case. <LI>If dencl_num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the rack_num, dencl_num, and bay fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate. The identity contained in the device field should be used to confirm the last known location values. </UL>Note that the content of the rack_num field will not be valid until a future release. Note also that in this case the content of the fed_class, al_pa, and num_times fields is undefined. The enclosures array shows the drive enclosures available on the Fibre Channel port identified in the cerp_id field. The location of an available drive enclosure is determined by the content of the enclosures.dencl_num field as follows: <UL><LI>If enclosures.dencl_num is less than 99, the location is as indicated by the content of the enclosures.rack_num and enclosures.dencl_num fields. <LI>If enclosures.dencl_num is equal to 99, the enclosures array entry is not used. Note that the content of the enclosures.rack_num field is undefined in this case. <LI>If enclosures.dencl_num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the enclosures.rack_num and enclosures.dencl_num fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate. </UL>Note that the content of the enclosures.rack_num field will not be valid until a future release.
|
|
.1.3.6.1.4.1.232.0.13601576 |
Severity: Normal -- informational in nature. The retry count for an OB task 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 Drive Enclosure Environmental Monitoring Unit.
|
|
.1.3.6.1.4.1.232.0.13601577 |
Severity: Normal -- informational in nature. The HSV110 controller has sent a Basic Link Service command Abort Sequence Frame. The original work is described in this event. 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. The location of the intended target is determined by the content of the dencl_num field as follows: <UL><LI>If dencl_num is less than 99, the location is as indicated by the content of the rack_num, dencl_num, and bay fields. <LI>If dencl_num is equal to 99, the location is unknown. Note that the content of the rack_num and bay fields is undefined in this case. <LI>If dencl_num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the rack_num, dencl_num, and bay fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate. The identity contained in the device field should be used to confirm the last known location values. </UL>Note that the content of 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 cmd field. Note that in this case the content of the error field is undefined. The enclosures array shows the drive enclosures available on the Fibre Channel port identified in the cerp_id field. The location of an available drive enclosure is determined by the content of the enclosures.dencl_num field as follows: <UL><LI>If enclosures.dencl_num is less than 99, the location is as indicated by the content of the enclosures.rack_num and enclosures.dencl_num fields. <LI>If enclosures.dencl_num is equal to 99, the enclosures array entry is not used. Note that the content of the enclosures.rack_num field is undefined in this case. <LI>If enclosures.dencl_num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the enclosures.rack_num and enclosures.dencl_num fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate. </UL>Note that the content of the enclosures.rack_num field will not be valid until a future release.
|
|
.1.3.6.1.4.1.232.0.13601578 |
Severity: Normal -- informational in nature. The HSV110 controller has sent an Extended Link Service command Reinstate Recovery Qualifier. The original work is described in this event. 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. The location of the intended target is determined by the content of the dencl_num field as follows: <UL><LI>If dencl_num is less than 99, the location is as indicated by the content of the rack_num, dencl_num, and bay fields. <LI>If dencl_num is equal to 99, the location is unknown. Note that the content of the rack_num and bay fields is undefined in this case. <LI>If dencl_num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the rack_num, dencl_num, and bay fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate. The identity contained in the device field should be used to confirm the last known location values. </UL>Note that the content of 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 cmd field. Note that in this case the content of the error field is undefined. The enclosures array shows the drive enclosures available on the Fibre Channel port identified in the cerp_id field. The location of an available drive enclosure is determined by the content of the enclosures.dencl_num field as follows: <UL><LI>If enclosures.dencl_num is less than 99, the location is as indicated by the content of the enclosures.rack_num and enclosures.dencl_num fields. <LI>If enclosures.dencl_num is equal to 99, the enclosures array entry is not used. Note that the content of the enclosures.rack_num field is undefined in this case. <LI>If enclosures.dencl_num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the enclosures.rack_num and enclosures.dencl_num fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate. </UL>Note that the content of the enclosures.rack_num field will not be valid until a future release.
|
|
.1.3.6.1.4.1.232.0.13601579 |
Severity: Critical -- failure or failure imminent. A physical disk drive was bypassed rendering it unusable. The physical disk drive is unusable because a Drive Enclosure Environmental Monitoring Unit bypassed a drive bay or the physical disk drive left itself bypassed. The physical disk drive is not available to the HSV110 controllers and will not be displayed by the HSV element manager GUI. The physical disk drive fault led will be lit to indicate that it is unusable. The Fibre Channel port over which this condition was detected is identified in the cerp_id field. The HSV110 controller internal Fibre Channel port over which this condition was detected is contained in the port field. The al_pa field is invalid. The location of the physical disk drive is as indicated by the content of the rack_num, dencl_num, and bay fields. Note that the content of the rack_num field will not be valid until a future release. The bypass_reason field is used to indicate how the physical disk drive was bypassed: <UL><LI>1 = The physical disk drive left itself bypassed <LI>2 = The Drive Enclosure Environmental Monitoring Unit bypassed the drive bay </UL>The Drive Enclosure Environmental Monitoring Unit is identified in the device field. Additionally, the content of the pid, rev, and enclosures array fields is undefined in this case.
|
|
.1.3.6.1.4.1.232.0.13601580 |
Severity: Normal -- informational in nature. One or more media defects were detected on a physical disk drive. The affected physical disk drive is identified in the device field. The Fibre Channel port over which the media defect(s) was detected is identified in the cerp_id field. The HSV110 controller internal Fibre Channel port number over which the media defect(s) was detected is contained in the port field. The arbitrated loop physical address of the physical disk drive is contained in the al_pa field. The Logical Block Address of each media defect is contained in a separate entry of the hdr_cdb array. Only nonzero values in the hdr_cdb array entries are valid. The location of the physical disk drive is determined by the content of the dencl_num field as follows: <UL><LI>If dencl_num is less than 99, the location is as indicated by the content of the rack_num, dencl_num, and bay fields. <LI>If dencl_num is equal to 99, the location is unknown. Note that the content of the rack_num and bay fields is undefined in this case. <LI>If dencl_num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the rack_num, dencl_num, and bay fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate. The identity contained in the device field should be used to confirm the last known location values. </UL>Note that the content of the rack_num field will not be valid until a future release.
|
|
.1.3.6.1.4.1.232.0.13601581 |
Severity: Normal -- informational in nature. An HSV110 controller issued a directed LIP to an arbitrated loop physical address. The Fibre Channel port over which the directed LIP was issued is identified in the cerp_id field. The HSV110 controller internal Fibre Channel port number over which the directed LIP was issued is contained in the port field. The arbitrated loop physical address of the physical disk drive is contained in the al_pa field.
|
|
.1.3.6.1.4.1.232.0.13601582 |
Severity: Normal -- informational in nature. An HSV110 controller has detected Loop Receiver Failures. The Fibre Channel port over which the Loop Receiver Failures were detected is identified in the cerp_id field. The HSV110 controller internal Fibre Channel port number over which the Loop Receiver Failures were detected is contained in the port field. The counts and the AL_PAs of the Loop Receiver Failures are contained in a separate entry of the hdr_cdb array. Only nonzero values in the hdr_cdb array entries are valid. The affected HSV110 controller is identified in the device field. Note that in this case the content of the al_pa, dencl_num, bay, and rack_num fields are undefined.
|
|
.1.3.6.1.4.1.232.0.13601584 |
Severity: Critical -- failure or failure imminent. A HSV110 controller has detected only one port of all Fibre Channel devices in an enclosure. These Fibre Channel devices have entered the Single Port on Fibre state which should be corrected as soon as possible. The identity of the Fibre Channel device enclosure is contained in the device field. The Fibre Channel port still able to communicate with the Fibre Channel device is contained in the cerp_id field. The HSV110 controller internal Fibre Channel port number able to communicate with the Fibre Channel device is contained in the port field. The Fibre Channel port unable to communicate with the Fibre Channel device is contained in the missing_cerp_id field. The HSV110 controller internal Fibre Channel port number unable to communicate with the Fibre Channel device is contained in the missing_port field. The al_pa and bay fields are invalid. The location of the Fibre Channel enclosure is determined by the content of the dencl_num field as follows: <UL><LI>If dencl_num is less than 99, the location is as indicated by the content of the rack_num and dencl_num fields. <LI>If dencl_num is equal to 99, the location is unknown. Note that the content of the rack_num field is undefined in this case. <LI>If dencl_num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the rack_num and dencl_num fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate. The identity contained in the device field should be used to confirm the last known location values. </UL>Note that the content of the rack_num field will not be valid until a future release. Note also that in this case the content of the fed_class, and num_times fields is undefined. The enclosures array shows the drive enclosures available on the Fibre Channel port identified in the cerp_id field. The location of an available drive enclosure is determined by the content of the enclosures.dencl_num field as follows: <UL><LI>If enclosures.dencl_num is less than 99, the location is as indicated by the content of the enclosures.rack_num and enclosures.dencl_num fields. <LI>If enclosures.dencl_num is equal to 99, the enclosures array entry is not used. Note that the content of the enclosures.rack_num field is undefined in this case. <LI>If enclosures.dencl_num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the enclosures.rack_num and enclosures.dencl_num fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate. </UL>Note that the content of the enclosures.rack_num field will not be valid until a future release.
|
|
.1.3.6.1.4.1.232.0.13601585 |
Severity: Normal -- informational in nature. A previously reported Fibre Channel device enclosure with only one port has been corrected and redundancy has been restored. The devices in the enclosure are no longer in the Single Port on Fibre state. The identity of the Fibre Channel device enclosure is contained in the device field. The Fibre Channel port used to communicate with the Fibre Channel device enclosure is contained in the cerp_id field. The HSV110 controller internal Fibre Channel port number used to communicate with the Fibre Channel device is contained in the port field. The al_pa, bay, missing_port, and missing_cerp_id fields are invalid. The location of the Fibre Channel device is determined by the content of the dencl_num field as follows: <UL><LI>If dencl_num is less than 99, the location is as indicated by the content of the rack_num and dencl_num fields. <LI>If dencl_num is equal to 99, the location is unknown. Note that the content of the rack_num field is undefined in this case. <LI>If dencl_num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the rack_num and dencl_num fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate. The identity contained in the device field should be used to confirm the last known location values. </UL>Note that the content of the rack_num field will not be valid until a future release. Note also that in this case the content of the fed_class, and num_times fields is undefined. The enclosures array shows the drive enclosures available on the Fibre Channel port identified in the cerp_id field. The location of an available drive enclosure is determined by the content of the enclosures.dencl_num field as follows: <UL><LI>If enclosures.dencl_num is less than 99, the location is as indicated by the content of the enclosures.rack_num and enclosures.dencl_num fields. <LI>If enclosures.dencl_num is equal to 99, the enclosures array entry is not used. Note that the content of the enclosures.rack_num field is undefined in this case. <LI>If enclosures.dencl_num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the enclosures.rack_num and enclosures.dencl_num fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate. </UL>Note that the content of the enclosures.rack_num field will not be valid until a future release.
|
|
.1.3.6.1.4.1.232.0.13601586 |
Severity: Critical -- failure or failure imminent. A HSV110 controller has detected only one port of all Fibre Channel devices on a loop. These Fibre Channel devices have entered the Single Port on Fibre state which should be corrected as soon as possible. The device, al_pa, dencl_num, and bay fields are all invalid. The Fibre Channel port still able to communicate with the Fibre Channel device is contained in the cerp_id field. The HSV110 controller internal Fibre Channel port number able to communicate with the Fibre Channel device is contained in the port field. The Fibre Channel port unable to communicate with the Fibre Channel device is contained in the missing_cerp_id field. The HSV110 controller internal Fibre Channel port number unable to communicate with the Fibre Channel device is contained in the missing_port field.
|
|
.1.3.6.1.4.1.232.0.13601587 |
Severity: Normal -- informational in nature. A previously reported Fibre Channel loop with only one port has been corrected and redundancy has been restored. The devices on the loop are no longer in the Single Port on Fibre state. The device, al_pa, dencl_num, bay, missing_port, and missing_cerp_id fields are invalid. The Fibre Channel port used to communicate with the Fibre Channel devices is contained in the cerp_id field. The HSV110 controller internal Fibre Channel port number used to communicate with the Fibre Channel devices is contained in the port field.
|
|
.1.3.6.1.4.1.232.0.13601588 |
Severity: Normal -- informational in nature. A HSV110 controller has been told to enable a device port, and that device port was not disabled during boot diagnostics. The Fibre Channel port that was enabled is contained in the cerp_id field. The HSV110 controller internal Fibre Channel port number enabled is contained in the port field. Note that in this case the contents of the bay, rack_num, fed_class, al_pa, dencl_num, device, enclosure array, and num_times fields are undefined. The missing_port and missing_cerp_id fields are unused.
|
|
.1.3.6.1.4.1.232.0.13601589 |
Severity: Critical -- failure or failure imminent. An unrecognized Fibre Channel physical disk drive firmware revision has been detected by the physical disk drive firmware load process. 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 bypass_reason field is invalid. The location of the physical disk drive is determined by the content of the dencl_num field as follows: <UL><LI>If dencl_num is less than 99, the location is as indicated by the content of the rack_num, dencl_num, and bay fields. <LI>If dencl_num is equal to 99, the location is unknown. Note that the content of the rack_num, al_pa and bay fields is undefined in this case. <LI>If dencl_num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the rack_num, dencl_num, and bay fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate. The identity contained in the device field should be used to confirm the last known location values. </UL>Note that the content of the rack_num field will not be valid until a future release. The pid field contains the SCSI Inquiry Product Identification obtained from the physical disk drive. The rev field contains the current firmware revision obtained from the physical disk drive. The new_rev field contains the latest firmware version known to the controller, or blanks if the isn't a known version. The enclosures array shows the drive enclosures available on the Fibre Channel port identified in the cerp_id field. The location of an available drive enclosure is determined by the content of the enclosures.dencl_num field as follows: <UL><LI>If enclosures.dencl_num is less than 99, the location is as indicated by the content of the enclosures.rack_num and enclosures.dencl_num fields. <LI>If enclosures.dencl_num is equal to 99, the enclosures array entry is not used. Note that the content of the enclosures.rack_num field is undefined in this case. <LI>If enclosures.dencl_num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the enclosures.rack_num and enclosures.dencl_num fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate. </UL>Note that the content of the enclosures.rack_num field will not be valid until a future release.
|
|
.1.3.6.1.4.1.232.0.13601590 |
Severity: Critical -- failure or failure imminent. An unsupported Fibre Channel physical disk drive firmware revision has been detected by the physical disk drive firmware load process. 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 bypass_reason field is invalid. The location of the physical disk drive is determined by the content of the dencl_num field as follows: <UL><LI>If dencl_num is less than 99, the location is as indicated by the content of the rack_num, dencl_num, and bay fields. <LI>If dencl_num is equal to 99, the location is unknown. Note that the content of the rack_num, al_pa and bay fields is undefined in this case. <LI>If dencl_num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the rack_num, dencl_num, and bay fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate. The identity contained in the device field should be used to confirm the last known location values. </UL>Note that the content of the rack_num field will not be valid until a future release. The pid field contains the SCSI Inquiry Product Identification obtained from the physical disk drive. The rev field contains the current firmware revision obtained from the physical disk drive. The new_rev field contains the latest firmware version known to the controller, or blanks if the isn't a known version. The enclosures array shows the drive enclosures available on the Fibre Channel port identified in the cerp_id field. The location of an available drive enclosure is determined by the content of the enclosures.dencl_num field as follows: <UL><LI>If enclosures.dencl_num is less than 99, the location is as indicated by the content of the enclosures.rack_num and enclosures.dencl_num fields. <LI>If enclosures.dencl_num is equal to 99, the enclosures array entry is not used. Note that the content of the enclosures.rack_num field is undefined in this case. <LI>If enclosures.dencl_num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the enclosures.rack_num and enclosures.dencl_num fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate. </UL>Note that the content of the enclosures.rack_num field will not be valid until a future release.
|
|
.1.3.6.1.4.1.232.0.13601591 |
Severity: Normal -- informational in nature. A Fibre Channel physical disk drive firmware revision has been detected by the physical disk drive firmware load process that is later than the latest known supported revision. If the location information is 0, it indicates the type of drive, not a specific drive. 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 bypass_reason field is invalid. The location of the physical disk drive is determined by the content of the dencl_num field as follows: <UL><LI>If dencl_num is less than 99, the location is as indicated by the content of the rack_num, dencl_num, and bay fields. <LI>If dencl_num is equal to 99, the location is unknown. Note that the content of the rack_num, al_pa and bay fields is undefined in this case. <LI>If dencl_num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the rack_num, dencl_num, and bay fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate. The identity contained in the device field should be used to confirm the last known location values. </UL>Note that the content of the rack_num field will not be valid until a future release. The pid field contains the SCSI Inquiry Product Identification obtained from the physical disk drive. The rev field contains the current firmware revision obtained from the physical disk drive. The new_rev field contains the latest firmware version known to the controller, or blanks if the isn't a known version. The enclosures array shows the drive enclosures available on the Fibre Channel port identified in the cerp_id field. The location of an available drive enclosure is determined by the content of the enclosures.dencl_num field as follows: <UL><LI>If enclosures.dencl_num is less than 99, the location is as indicated by the content of the enclosures.rack_num and enclosures.dencl_num fields. <LI>If enclosures.dencl_num is equal to 99, the enclosures array entry is not used. Note that the content of the enclosures.rack_num field is undefined in this case. <LI>If enclosures.dencl_num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the enclosures.rack_num and enclosures.dencl_num fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate. </UL>Note that the content of the enclosures.rack_num field will not be valid until a future release.
|
|
.1.3.6.1.4.1.232.0.13601592 |
Severity: Normal -- informational in nature. A Fibre Channel physical disk drive firmware revision has been detected by the physical disk drive firmware load process that has a newer supported revision available. If the location information is 0, it indicates the type of drive, not a specific drive. 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 bypass_reason field is invalid. The location of the physical disk drive is determined by the content of the dencl_num field as follows: <UL><LI>If dencl_num is less than 99, the location is as indicated by the content of the rack_num, dencl_num, and bay fields. <LI>If dencl_num is equal to 99, the location is unknown. Note that the content of the rack_num, al_pa and bay fields is undefined in this case. <LI>If dencl_num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the rack_num, dencl_num, and bay fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate. The identity contained in the device field should be used to confirm the last known location values. </UL>Note that the content of the rack_num field will not be valid until a future release. The pid field contains the SCSI Inquiry Product Identification obtained from the physical disk drive. The rev field contains the current firmware revision obtained from the physical disk drive. The new_rev field contains the latest firmware version known to the controller, or blanks if the isn't a known version. The enclosures array shows the drive enclosures available on the Fibre Channel port identified in the cerp_id field. The location of an available drive enclosure is determined by the content of the enclosures.dencl_num field as follows: <UL><LI>If enclosures.dencl_num is less than 99, the location is as indicated by the content of the enclosures.rack_num and enclosures.dencl_num fields. <LI>If enclosures.dencl_num is equal to 99, the enclosures array entry is not used. Note that the content of the enclosures.rack_num field is undefined in this case. <LI>If enclosures.dencl_num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the enclosures.rack_num and enclosures.dencl_num fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate. </UL>Note that the content of the enclosures.rack_num field will not be valid until a future release.
|
|
.1.3.6.1.4.1.232.0.13601593 |
Severity: Normal -- informational in nature. The HSV110 controller bypassed a device bay in an attempt to restore operability. The identity of the bay is indicated by the rack_num, dencl_num, and bay fields. All other fields are invalid.
|
|
.1.3.6.1.4.1.232.0.13601594 |
Severity: Normal -- informational in nature. The HSV110 controller is attempting to recovery devices on the indicated port. All other fields are invalid.
|
|
.1.3.6.1.4.1.232.0.13601595 |
Severity: Normal -- informational in nature. The HSV110 controller has finished error recovery attempts on the indicated port. All other fields are invalid.
|
|
.1.3.6.1.4.1.232.0.13601596 |
Severity: Normal -- informational in nature. The HSV110 controller been requested to unbypass device bays on the indicated port. All other fields are invalid.
|
|
.1.3.6.1.4.1.232.0.13601597 |
Severity: Undetermined -- more information needed to determine severity. The HSV110 controller has detected a enclosure on the CAB bus that does not have a Fibre Channel connection. All fields except port and rack are invalid. other fields are invalid.
|
|
.1.3.6.1.4.1.232.0.13601598 |
Severity: Critical -- failure or failure imminent. The HSV110 controller has detected an enclosure on the Fibre Channel but is unable to communicate with the EMU on the CAB bus or the EMU is reporting an invalid enclosure number. All fields except port and rack are invalid. other fields are invalid.
|
|
.1.3.6.1.4.1.232.0.136016001 |
Ema Short Status - Reissue Command
|
|
.1.3.6.1.4.1.232.0.136016004 |
Ema Invalid Handle Set In Request Packet
|
|
.1.3.6.1.4.1.232.0.136016005 |
Ema No Pstore At Referenced Location
|
|
.1.3.6.1.4.1.232.0.136016008 |
Ema No Device Found
|
|
.1.3.6.1.4.1.232.0.136016010 |
Ema Could Not Find SubEnclosure in Configuration List
|
|
.1.3.6.1.4.1.232.0.136016012 |
Ema Non-specific error occurred
|
|
.1.3.6.1.4.1.232.0.136016013 |
Ema Shelf WWN Could Not Be Accessed Through A Drive
|
|
.1.3.6.1.4.1.232.0.136016014 |
Ema EMU Failed To Enter Primary Mode
|
|
.1.3.6.1.4.1.232.0.136016015 |
Ema EMU Failed To Exit Primary Mode
|
|
.1.3.6.1.4.1.232.0.136016016 |
Ema Downloaded File Does Not Contain Valid Fibre Channel Loader [status:1]
|
|
.1.3.6.1.4.1.232.0.136016017 |
Ema Downloaded File Format Is Not Recognized [status:2]
|
|
.1.3.6.1.4.1.232.0.136016018 |
Ema Incorrect Firmware In Downloaded File [status:3]
|
|
.1.3.6.1.4.1.232.0.136016019 |
Ema Downloaded Loader is Too Large [status:4]
|
|
.1.3.6.1.4.1.232.0.136016020 |
Ema Invalid Checksum [status:5]
|
|
.1.3.6.1.4.1.232.0.136016021 |
Ema Previous Offset Plus Previous Length Not Equal To Current Offset [status:6]
|
|
.1.3.6.1.4.1.232.0.136016022 |
Ema Downloaded Loader Terminated Incorrectly [status:7]
|
|
.1.3.6.1.4.1.232.0.136016023 |
Ema EMU Out Of Memory [status:8]
|
|
.1.3.6.1.4.1.232.0.136016024 |
Ema EMU CDB Timeout -- Download Aborted [status:9]
|
|
.1.3.6.1.4.1.232.0.136016025 |
Ema EMU Internal State Machine Error [status:10]
|
|
.1.3.6.1.4.1.232.0.136016026 |
Ema EMU Flash Erasure Failure [status:11]
|
|
.1.3.6.1.4.1.232.0.136016027 |
Ema EMU In Primary Mode - Cannot Download To Primary EMU [status:12]
|
|
.1.3.6.1.4.1.232.0.136016028 |
Ema Previous Offset Plus Previous Length Greater Than Total Size [status:13]
|
|
.1.3.6.1.4.1.232.0.136016029 |
Ema Current Total Size Different From Previous Total Size [status:14]
|
|
.1.3.6.1.4.1.232.0.136016030 |
Ema Could Not Restore Reporting Group Number. Final Download Record Error
|
|
.1.3.6.1.4.1.232.0.136016031 |
Ema Could Not Recovery From Invop. Invop Retries Exhausted
|
|
.1.3.6.1.4.1.232.0.136016032 |
Ema Requested WWN Does Not Match Enclosure WWN
|
|
.1.3.6.1.4.1.232.0.136016033 |
Ema EMU Enclosure Services Error Occurred. EMU May Be Unavailable or Not Installed
|
|
.1.3.6.1.4.1.232.0.136016034 |
Ema SCSI Error Occurred While Trying To Communicate With EMU
|
|
.1.3.6.1.4.1.232.0.136016035 |
Ema Could Not Open EMU Firmware File
|
|
.1.3.6.1.4.1.232.0.136016036 |
Ema EMU Firmware File Name Is Null
|
|
.1.3.6.1.4.1.232.0.136016037 |
Ema EMU Firmware Download Retries Exhausted. Manual Download May Be Required
|
|
.1.3.6.1.4.1.232.0.136016038 |
Ema EMU Current Firmware Version Matches Upgrade Firmware Version. No Upgrade Will Be Performed.
|
|
.1.3.6.1.4.1.232.0.136016039 |
Ema EMU Firmware Upgrade Success
|
|
.1.3.6.1.4.1.232.0.136016040 |
Ema EMU In Load State. Do Not Power Off. Reload EMU Firmware
|
|
.1.3.6.1.4.1.232.0.136017001 |
Drive Code Load Descriptor File Open Error
|
|
.1.3.6.1.4.1.232.0.136017002 |
Drive Code Load Descriptor File Parsing Error - Invalid Line
|
|
.1.3.6.1.4.1.232.0.136017003 |
Drive Code Load Image File Open Error,
|
|
.1.3.6.1.4.1.232.0.136017004 |
Drive Code Load Image File Error Getting File Size
|
|
.1.3.6.1.4.1.232.0.136017005 |
Drive Code Load Image File Buffer Allocation Error
|
|
.1.3.6.1.4.1.232.0.136017006 |
Drive Code Load Image File Read Error
|
|
.1.3.6.1.4.1.232.0.136017007 |
Drive Code Load Drive Firmware Update Failed
|
|
.1.3.6.1.4.1.232.0.136017008 |
Drive Code Load Drive Inquiry Failed
|
|
.1.3.6.1.4.1.232.0.136017009 |
Drive Code Load Format Command Failed
|
|
.1.3.6.1.4.1.232.0.136017012 |
Drive Code Load Get Physical Store Condition Failed
|
|
.1.3.6.1.4.1.232.0.136017013 |
Drive Code Load Get Volume Condition Failed
|
|
.1.3.6.1.4.1.232.0.136017014 |
Drive Code Load Drive Spin Up Error
|
|
.1.3.6.1.4.1.232.0.136017015 |
Drive Code Load - Complete
|
|
.1.3.6.1.4.1.232.0.136017016 |
Drive Code Load Disk Group Migration In Progress
|
|
.1.3.6.1.4.1.232.0.136017017 |
Drive Code Load Unable To Code Load Disks Part Of A Group
|
|
.1.3.6.1.4.1.232.0.13601792 |
Severity: Warning -- not failed but attention recommended or required. Allocation of a Virtual Disk has stalled due to insufficient space in the Disk Group caused by the failure or pulling of a physical disk drive. The tag1 field contains the identity of the Virtual Disk. The tag2 field contains the identity of the Disk Group. The values that may be found in the state field are as follows: <UL><LI>0 = Attempting to retry the allocation <LI>1 = Awaiting a leveling event (a drive needs to be inserted) </UL>
|
|
.1.3.6.1.4.1.232.0.13601793 |
Severity: Warning -- not failed but attention recommended or required. Expansion of a Virtual Disk has stalled due to insufficient space in the Disk Group caused by the failure or pulling of a physical disk drive. The tag1 field contains the identity of the Virtual Disk. The tag2 field contains the identity of the Disk Group. The values that may be found in the state field are as follows: <UL><LI>0 = Attempting to retry the expansion <LI>1 = Awaiting a leveling event (a drive needs to be inserted) </UL>
|
|
.1.3.6.1.4.1.232.0.13601794 |
Severity: Normal -- informational in nature. Leveling of capacity in a Disk Group has started. The identity of the Disk Group is contained in the tag1 field.
|
|
.1.3.6.1.4.1.232.0.13601795 |
Severity: Normal -- informational in nature. Leveling of capacity in a Disk Group has finished. The identity of the Disk Group is contained in the tag1 field.
|
|
.1.3.6.1.4.1.232.0.13601796 |
Severity: Normal -- informational in nature. A member management operation has started due to the appearance or disappearance of a physical disk drive. If available, the tag1 field contains the identity of the physical disk drive. The tag2 field contains the disk unit block in which physical disk drive resides. The values that may be found in the state field are as follows: <UL><LI>2 = Reconstructing <LI>4 = Migrating <LI>6 = Reverting </UL>
|
|
.1.3.6.1.4.1.232.0.13601797 |
Severity: Normal -- informational in nature. A member management operation has finished. If available, the tag1 field contains the identity of the physical disk drive. The tag2 field contains the disk unit block in which the physical disk drive resides. The values that may be found in the state field are as follows: <UL><LI>2 = Reconstructing <LI>4 = Migrating <LI>6 = Reverting </UL>The status field contains one of the following values: <UL><LI>1 = PSEGS NONE ( Reconstruction of data was successful ) <LI>2 = PSEGS RAID0 ( Could not reconstruct RAID0 data ) <LI>4 = PSEGS RAID5 ( Could not reconstruct RAID5 data ) <LI>8 = PSEGS RAID1 ( Could not reconstruct RAID1 data ) </UL>
|
|
.1.3.6.1.4.1.232.0.13601798 |
Severity: Normal -- informational in nature. A Disk Group has started changing its internal structure due to the appearance or disappearance of a Volume. The identity of the Disk Group is contained in the tag1 field. The values that may be found in the state field are as follows: <UL><LI>4 = Merge began <LI>8 = Split began </UL>
|
|
.1.3.6.1.4.1.232.0.13601799 |
Severity: Normal -- informational in nature. A Disk Group has finished changing its internal structure due to the appearance or disappearance of a volume. The identity of the Disk Group is contained in the tag1 field. The values that may be found in the state field are as follows: <UL><LI>4 = Merge completed <LI>8 = Split completed </UL>
|
|
.1.3.6.1.4.1.232.0.13601800 |
Severity: Normal -- informational in nature. Deallocation of a Virtual Disk has failed after three attempts due to unknown circumstances. This will more than likely be caused by failing physical drives. The deletion will be restarted when a resync/reboot occurs. The tag1 field contains the identity of the Virtual Disk. The tag2 field contains the identity of the Disk Group. The values that may be found in the status field indicate the returned status from the delete operation.
|
|
.1.3.6.1.4.1.232.0.136018001 |
Api Created Element Success
|
|
.1.3.6.1.4.1.232.0.136018002 |
Api Created Storage Success
|
|
.1.3.6.1.4.1.232.0.136018003 |
Api Created Storage Client Success
|
|
.1.3.6.1.4.1.232.0.136018004 |
Api Set Storage Success
|
|
.1.3.6.1.4.1.232.0.136018005 |
Api Set Element Success
|
|
.1.3.6.1.4.1.232.0.136018006 |
Api Deleted Element Success
|
|
.1.3.6.1.4.1.232.0.136018007 |
Api Deleted Storage Success
|
|
.1.3.6.1.4.1.232.0.136018008 |
Api Deleted Storage Client Success
|
|
.1.3.6.1.4.1.232.0.136018009 |
Api Created Snapshot Success
|
|
.1.3.6.1.4.1.232.0.136018010 |
Api Created Clone Success
|
|
.1.3.6.1.4.1.232.0.136018018 |
Api Unable To Get The Lock
|
|
.1.3.6.1.4.1.232.0.136018019 |
Api Created PresentedUnit Success
|
|
.1.3.6.1.4.1.232.0.136018022 |
Api Create DiskGroup Success
|
|
.1.3.6.1.4.1.232.0.136018024 |
Api Create Folder Success
|
|
.1.3.6.1.4.1.232.0.136018025 |
Api Delete Folder Success
|
|
.1.3.6.1.4.1.232.0.136018028 |
Api Set Folder Success
|
|
.1.3.6.1.4.1.232.0.136018034 |
Api Invalid User Name Or Password Error
|
|
.1.3.6.1.4.1.232.0.136018036 |
Api Delete Presented Unit Success
|
|
.1.3.6.1.4.1.232.0.136018038 |
Api Set Diskgroup Success
|
|
.1.3.6.1.4.1.232.0.136018039 |
Api Set Disk Success
|
|
.1.3.6.1.4.1.232.0.136018040 |
Api Delete Storage Family Success
|
|
.1.3.6.1.4.1.232.0.136018041 |
Api Set Storage Family Success
|
|
.1.3.6.1.4.1.232.0.136018042 |
Api Control Memory Allocation Failure
|
|
.1.3.6.1.4.1.232.0.136018045 |
Api Element Codeload Success
|
|
.1.3.6.1.4.1.232.0.136018047 |
Api Disk Codeload Success
|
|
.1.3.6.1.4.1.232.0.136018048 |
Api Monitor Codeload Success
|
|
.1.3.6.1.4.1.232.0.136018049 |
Api Added Port WWID Success
|
|
.1.3.6.1.4.1.232.0.136018050 |
Api Set Storage Client Success
|
|
.1.3.6.1.4.1.232.0.136018051 |
Api Invalid Operation
|
|
.1.3.6.1.4.1.232.0.136018052 |
Api Deleted Port WWID Success
|
|
.1.3.6.1.4.1.232.0.136018059 |
Api Set Power Success
|
|
.1.3.6.1.4.1.232.0.136018060 |
Api Element Is Not Initialized
|
|
.1.3.6.1.4.1.232.0.136018063 |
Api Error trying to delete a disk group
|
|
.1.3.6.1.4.1.232.0.136018065 |
Api A storage (Vdisk) operation is in progress. Try again later.
|
|
.1.3.6.1.4.1.232.0.136018066 |
Api The storage (Vdisk) condition is invalid. The storage may be in error. Try again later.
|
|
.1.3.6.1.4.1.232.0.136018067 |
Api Error calling get Vdisk condition. Vdisk may be deleted. Try again later.
|
|
.1.3.6.1.4.1.232.0.136018068 |
Api Invalid initialization of the API. Cannot start monitoring process. Storage system management limited.
|
|
.1.3.6.1.4.1.232.0.136018070 |
Api A command is currently under execution from another API call. Try again later.
|
|
.1.3.6.1.4.1.232.0.136018071 |
Api The server has not completed initialization, cannot process the request.
|
|
.1.3.6.1.4.1.232.0.136018073 |
Api Removal of disk from disk group successful
|
|
.1.3.6.1.4.1.232.0.136018074 |
Api Disk(s) added to disk group successfully
|
|
.1.3.6.1.4.1.232.0.136018075 |
Api Modify monitor properties successful
|
|
.1.3.6.1.4.1.232.0.136018076 |
Api Element name too long. Maximum is 20 characters.
|
|
.1.3.6.1.4.1.232.0.136018080 |
Api The snapshot/Snapclone license cannot be validated. Either the license key has not been entered, or there is a system communication failure.
|
|
.1.3.6.1.4.1.232.0.136018081 |
Api The folder operation is not valid for the specified folder. Either the folder is a root folder and cannot be modified, or it is a disk group folder for which you should use 'Set Group' command.
|
|
.1.3.6.1.4.1.232.0.136020001 |
LicMngr Memory Allocation Failure
|
|
.1.3.6.1.4.1.232.0.136020002 |
LicMngr Startup Complete
|
|
.1.3.6.1.4.1.232.0.136020003 |
LicMngr Startup Failed
|
|
.1.3.6.1.4.1.232.0.136020004 |
License successfully checked out
|
|
.1.3.6.1.4.1.232.0.136020005 |
License checkout failed
|
|
.1.3.6.1.4.1.232.0.136020011 |
License Line has an incorrect format
|
|
.1.3.6.1.4.1.232.0.136020013 |
License Library runtime error
|
|
.1.3.6.1.4.1.232.0.136020015 |
Failed to retrieve Node WWN from storage system
|
|
.1.3.6.1.4.1.232.0.136020016 |
Failed to retrieve license list from MLD
|
|
.1.3.6.1.4.1.232.0.136020017 |
Failed to write license list to MLD
|
|
.1.3.6.1.4.1.232.0.136020018 |
This license line appears to be invalid
|
|
.1.3.6.1.4.1.232.0.136020019 |
MLD Manager Handle is NULL - unable to update MLD License List
|
|
.1.3.6.1.4.1.232.0.136020020 |
LicMngr: Storage system handle is NULL
|
|
.1.3.6.1.4.1.232.0.136020021 |
The license you entered is a valid license but not for the Node WWN and/or firmware version on this controller pair
|
|
.1.3.6.1.4.1.232.0.136020022 |
Function name string is null or in an incorrect format
|
|
.1.3.6.1.4.1.232.0.136020023 |
Version string is null or in an incorrect format
|
|
.1.3.6.1.4.1.232.0.136021001 |
HSV Upgrade Manager Image File Open Error
|
|
.1.3.6.1.4.1.232.0.136021002 |
HSV Upgrade Manager Image File Buffer Allocation Error
|
|
.1.3.6.1.4.1.232.0.136021003 |
HSV Upgrade Manager Image File Read Error
|
|
.1.3.6.1.4.1.232.0.136021004 |
HSV Upgrade Manager Event File Write Error
|
|
.1.3.6.1.4.1.232.0.136021006 |
HSV Upgrade Manager Global Header Edc Compute Error
|
|
.1.3.6.1.4.1.232.0.136021007 |
HSV Upgrade Manager Image Header Edc Compute Error
|
|
.1.3.6.1.4.1.232.0.136021008 |
HSV Upgrade Manager Image Type Exceeds Max Image Count
|
|
.1.3.6.1.4.1.232.0.136021009 |
HSV Upgrade Manager Image Type Not Controller Image
|
|
.1.3.6.1.4.1.232.0.136021010 |
HSV Upgrade Manager Image Size Exceeded
|
|
.1.3.6.1.4.1.232.0.136021011 |
HSV Upgrade Manager Event File Open Error
|
|
.1.3.6.1.4.1.232.0.136021012 |
HSV Upgrade Manager Image Edc Compute Error
|
|
.1.3.6.1.4.1.232.0.136021013 |
HSV Upgrade Manager Begin Text Not Found
|
|
.1.3.6.1.4.1.232.0.136021014 |
HSV Upgrade Manager After Text Not Found
|
|
.1.3.6.1.4.1.232.0.136021015 |
HSV Upgrade Manager File Format Version Mismatch
|
|
.1.3.6.1.4.1.232.0.136021016 |
HSV Upgrade Manager Global Header Format Version Mismatch
|
|
.1.3.6.1.4.1.232.0.136021017 |
HSV Upgrade Manager Product Information Was Not Found
|
|
.1.3.6.1.4.1.232.0.136021018 |
HSV Upgrade Manager Event File Was Not Found
|
|
.1.3.6.1.4.1.232.0.136021019 |
HSV Upgrade Manager All Images Match Versions Already Loaded
|
|
.1.3.6.1.4.1.232.0.136022001 |
Trace: Unable to write management agent trace file
|
|
.1.3.6.1.4.1.232.0.136022002 |
Trace: file write succeeded
|
|
.1.3.6.1.4.1.232.0.136023002 |
Diagnostic The view list has errors
|
|
.1.3.6.1.4.1.232.0.136023003 |
Diagnostic Memory allocation failure
|
|
.1.3.6.1.4.1.232.0.13602305 |
Severity: Normal -- informational in nature. The state of the Physical Disk 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: <UL><LI>2 = Degraded <LI>3 = Failed <LI>4 = Not present <LI>5 = Single Port on Fibre </UL>The enclosure number, bay number, and rack number where the Physical Disk Drive is located are contained in the attribute.value.u32[0], attribute.value.u32[1], attribute.value.u32[2] fields, respectively. The attribute.type field contains value 1. The rack number in the attribute.value.u32[2] field will not contain a valid value until a future release.
|
|
.1.3.6.1.4.1.232.0.13602306 |
Severity: Normal -- informational in nature. The state of a Volume has changed. The identity of the affected Volume is contained in the handle field. The add_handle field contains the identity of the Physical Disk Drive that is associated with that Volume. The enclosure number, bay number, and rack number where the associated Physical Disk Drive is located are contained in the attribute.value.u32[0], attribute.value.u32[1], and attribute.value.u32[2] fields, respectively. The internal identification of that Volume's Redundant Storage Set is contained in the attribute.value.u32[3] field. The attribute.type field contains the value of 1. 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: <UL><LI>1 = Normal - Volume is present and operating normally <LI>2 = Migrating - Data from this volume is being moved to other storage in this Disk Group <LI>3 = Missing - Volume is inaccessible <LI>4 = Reconstructing - Volume is inaccessible; redundant data is being regenerated and moved to other storage in this Disk Group <LI>5 = Completing - This previously inaccessible volume has become accessible; data migration is being completed <LI>6 = Reverting - This previously inaccessible volume has become accessible; data is being regenerated <LI>7 = Failed - Volume is not being used in the Disk Group; disk errors are preventing normal usage </UL>
|
|
.1.3.6.1.4.1.232.0.13602307 |
Severity: Normal -- informational in nature. The state of the internal Logical 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: <UL><LI>1 = Normal <LI>2 = Replacement delay in progress <LI>3 = Redundancy lost, restore in progress <LI>4 = Redundancy lost, restore stalled <LI>5 = Failed <LI>6 = Creation in progress <LI>7 = Snapshot is inoperative due to lack of snapshot space <LI>8 = Deletion in progress <LI>9 = Capacity change in progress <LI>10 = Inoperative due to data lost <LI>11 = Capacity reservation in progress <LI>12 = Capacity unreservation in progress </UL>
|
|
.1.3.6.1.4.1.232.0.13602308 |
Severity: Normal -- informational in nature. The state of the HSV110 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).
|
|
.1.3.6.1.4.1.232.0.13602309 |
Severity: Normal -- informational in nature. The state of a battery assembly 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: <UL><LI>1 = Battery System Hold-up Time is greater than 96 hours <LI>3 = Battery System Hold-up Time is greater than 0 and less than 96 hours <LI>5 = Battery System Hold-up Time is zero hours </UL>
|
|
.1.3.6.1.4.1.232.0.13602310 |
Severity: Undetermined -- more information needed to determine severity. A Volume has transitioned to the MISSING state. The affected Volume is identified in the handle field. The add_handle field contains the identity of the Physical Disk Drive that is associated with that Volume. The enclosure number, bay number, and rack number where the associated Physical Disk Drive is located are contained in the attribute.value.u32[0], attribute.value.u32[1], and attribute.value.u32[2] fields, respectively. The internal identification of that Volume's Redundant Storage Set is contained in the attribute.value.u32[3] field. The attribute.type field contains the value of 1. 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: <UL><LI>1 = Normal - Volume is present and operating normally <LI>2 = Migrating - Data from this volume is being moved to other storage in this Disk Group <LI>4 = Reconstructing - Volume is inaccessible; redundant data is being regenerated and moved to other storage in this Disk Group <LI>5 = Completing - This previously inaccessible volume has become accessible; data migration is being completed <LI>6 = Reverting - This previously inaccessible volume has become accessible; data is being regenerated <LI>7 = Failed - Volume is not being used in the Disk Group; disk errors are preventing normal usage </UL>
|
|
.1.3.6.1.4.1.232.0.13602311 |
Severity: Normal -- informational in nature. The state of the Fibre Channel 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). <P> Note that the HSV110 controller's internal identity of the affected Fibre Channel port is contained in the secondary_id field.
|
|
.1.3.6.1.4.1.232.0.13602312 |
Severity: Warning -- not failed but attention recommended or required. The Occupancy Alarm Level threshold has been reached for the Disk Group identified in the handle field.
|
|
.1.3.6.1.4.1.232.0.13602313 |
Severity: Normal -- informational in nature. The Resource Availability state of a Volume has transitioned to the SUFFICIENT state. The affected Volume is identified in the handle field. The add_handle field contains the identity of the Physical Disk Drive that is associated with that Volume. The enclosure number, bay number, and rack number where the associated Physical Disk Drive is located are contained in the attribute.value.u32[0], attribute.value.u32[1], and attribute.value.u32[2] fields, respectively. The internal identification of that Volume's Redundant Storage Set is contained in the attribute.value.u32[3] field. The attribute.type field contains the value of 1. The value.ul1 field contains the new state: 0 (SUFFICIENT). The value.ul2 field contains the old state: 1 (INSUFFICIENT).
|
|
.1.3.6.1.4.1.232.0.13602314 |
Severity: Normal -- informational in nature. The Data Availability state of the internal Logical Disk associated with the Virtual 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).
|
|
.1.3.6.1.4.1.232.0.13602316 |
Severity: Normal -- informational in nature. The Snapclone Logical Disk identified in the handle field has completed the unsharing operation. The secondary_id field contains the noid of the associated successor internal Logical Disk.
|
|
.1.3.6.1.4.1.232.0.13602317 |
Severity: Normal -- informational in nature. The state of the Quorum Disk flag of a Volume has changed. The affected Volume is identified in the handle field. 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: <UL><LI>0 = Not quorum disk <LI>1 = Quorum disk </UL>
|
|
.1.3.6.1.4.1.232.0.13602318 |
Severity: Critical -- failure or failure imminent. The temperature trip point for a temperature sensor located within an HSV110 controller has been reached. The HSV110 controller is identified in the handle field. The value.ul1 field contains the current temperature reading from I2C sensor 1 in degrees celsius while the value.ul2 field contains the adjusted reading from I2C sensor 2. The set temperature trip point is contained in the secondary_id field.
|
|
.1.3.6.1.4.1.232.0.13602319 |
Severity: Warning -- not failed but attention recommended or required. The temperature within the HSV110 controller identified in the handle field is approaching its trip point. The value.ul1 field contains the current temperature reading from I2C sensor 1 in degrees celsius while the value.ul2 field contains the adjusted reading from I2C sensor 2. The secondary_id field contains the set temperature trip point in Celsius.
|
|
.1.3.6.1.4.1.232.0.13602321 |
Severity: Normal -- informational in nature. The Blower Present flag for the '1' 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).
|
|
.1.3.6.1.4.1.232.0.13602322 |
Severity: Critical -- failure or failure imminent. The '1' blower 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 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.
|
|
.1.3.6.1.4.1.232.0.13602323 |
Severity: Normal -- informational in nature. One of the voltage sensors 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.
|
|
.1.3.6.1.4.1.232.0.13602324 |
Severity: Undetermined -- more information needed to determine severity. The state of a Volume has transitioned to the FAILED state. The affected Volume is identified in the handle field. The add_handle field contains the identity of the Physical Disk Drive that is associated with that Volume. The enclosure number, bay number, and rack number where the associated Physical Disk Drive is located are contained in the attribute.value.u32[0], attribute.value.u32[1], and attribute.value.u32[2] fields, respectively. The internal identification of that Volume's Redundant Storage Set is contained in the attribute.value.u32[3] field. The attribute.type field contains the value of 1. 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: <UL><LI>1 = Normal - Volume is present and operating normally <LI>2 = Migrating - Data from this volume is being moved to other storage in this Disk Group <LI>3 = Missing - Volume is inaccessible <LI>4 = Reconstructing - Volume is inaccessible; redundant data is being regenerated and moved to other storage in this Disk Group <LI>5 = Completing - This previously inaccessible volume has become accessible; data migration is being completed <LI>6 = Reverting - This previously inaccessible volume has become accessible; data is being regenerated </UL>
|
|
.1.3.6.1.4.1.232.0.13602325 |
Severity: Undetermined -- more information needed to determine severity. An HSV110 controller has failed. The state of the HSV110 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).
|
|
.1.3.6.1.4.1.232.0.13602326 |
Severity: Normal -- informational in nature. The temperature within the HSV110 controller identified in the handle field has returned to its normal operating range. The value.ul1 field contains the current temperature reading in celsius from I2C sensor 1, while the value.ul2 field contains the adjusted reading from I2C sensor 2.
|
|
.1.3.6.1.4.1.232.0.13602327 |
Severity: Critical -- failure or failure imminent. An HSV110 controller's battery assembly has been removed. The Battery Present flag for 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).
|
|
.1.3.6.1.4.1.232.0.13602328 |
Severity: Normal -- informational in nature. The Battery In Use flag for battery 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).
|
|
.1.3.6.1.4.1.232.0.13602329 |
Severity: Normal -- informational in nature. One of the voltage sensors 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.
|
|
.1.3.6.1.4.1.232.0.13602330 |
Severity: Warning -- not failed but attention recommended or required. The battery assembly voltage regulator located within the HSV110 controller identified in the handle field is offline.
|
|
.1.3.6.1.4.1.232.0.13602331 |
Severity: Normal -- informational in nature. The state of the Disk Group 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: <UL><LI>2 = Disk Group with no redundancy is inoperative <LI>3 = Disk Group with parity redundancy is inoperative <LI>4 = Disk Group with mirrored redundancy is inoperative <LI>5 = Disk Group with no redundancy is inoperative, marked for re-use <LI>6 = Disk Group with parity redundancy is inoperative, marked for re-use <LI>7 = Disk Group with mirrored redundancy is inoperative, marked for re-use </UL>
|
|
.1.3.6.1.4.1.232.0.13602332 |
Severity: Normal -- informational in nature. The Occupancy Alarm Level for the Disk Group identified in the handle field has returned to the normal range.
|
|
.1.3.6.1.4.1.232.0.13602333 |
Severity: Critical -- failure or failure imminent. An HSV110 controller's battery assembly has malfunctioned. The Battery In Use flag for battery 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).
|
|
.1.3.6.1.4.1.232.0.13602334 |
Severity: Normal -- informational in nature. The Battery Present flag for 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).
|
|
.1.3.6.1.4.1.232.0.13602335 |
Severity: Critical -- failure or failure imminent. An HSV110 controller's battery assembly has been removed. The Battery Present flag for 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).
|
|
.1.3.6.1.4.1.232.0.13602336 |
Severity: Normal -- informational in nature. The Battery Present flag for 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).
|
|
.1.3.6.1.4.1.232.0.13602337 |
Severity: Normal -- informational in nature. The Battery In Use flag for battery 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).
|
|
.1.3.6.1.4.1.232.0.13602338 |
Severity: Critical -- failure or failure imminent. An HSV110 controller's battery assembly has malfunctioned. The Battery In Use flag for battery 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).
|
|
.1.3.6.1.4.1.232.0.13602339 |
Severity: Critical -- failure or failure imminent. The Blower Present flag for the '2' 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).
|
|
.1.3.6.1.4.1.232.0.13602340 |
Severity: Normal -- informational in nature. The Blower Present flag for the '2' 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).
|
|
.1.3.6.1.4.1.232.0.13602341 |
Severity: Critical -- failure or failure imminent. The '2' blower 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 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.
|
|
.1.3.6.1.4.1.232.0.13602342 |
Severity: Critical -- failure or failure imminent. An HSV110 controller's '1' blower/power supply assembly has been removed or AC power has been removed from the power supply. The HSV110 controller is identified in the handle field. 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).
|
|
.1.3.6.1.4.1.232.0.13602343 |
Severity: Normal -- informational in nature. An HSV110 controller's '1' blower/power supply assembly has been reinstalled or AC power has been restored to the power supply. The HSV110 controller is identified in the handle field. 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).
|
|
.1.3.6.1.4.1.232.0.13602344 |
Severity: Critical -- failure or failure imminent. An HSV110 controller's '2' blower/power supply assembly has been removed or AC power has been removed from the power supply. The HSV110 controller is identified in the handle field. 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).
|
|
.1.3.6.1.4.1.232.0.13602345 |
Severity: Normal -- informational in nature. An HSV110 controller's '2' blower/power supply assembly has been reinstalled or AC power has been restored to the power supply. The HSV110 controller is identified in the handle field. 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).
|
|
.1.3.6.1.4.1.232.0.13602346 |
Severity: Critical -- failure or failure imminent. The '1' blower/power supply 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.
|
|
.1.3.6.1.4.1.232.0.13602347 |
Severity: Critical -- failure or failure imminent. The '2' blower/power supply 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.
|
|
.1.3.6.1.4.1.232.0.13602348 |
Severity: Warning -- not failed but attention recommended or required. The state of a battery assembly 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 5: (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: <UL><LI>1 = Battery System Hold-up Time is greater than 96 hours <LI>3 = Battery System Hold-up Time is greater than 0 and less than 96 hours <LI>5 = Battery System Hold-up Time is zero hours </UL>
|
|
.1.3.6.1.4.1.232.0.13602349 |
Severity: Undetermined -- more information needed to determine severity. The Resource Availability state of a Volume has transitioned to the INSUFFICIENT state. The affected Volume is identified in the handle field. The add_handle field contains the identity of the Physical Disk Drive that is associated with that Volume. The enclosure number, bay number, and rack number where the associated Physical Disk Drive is located are contained in the attribute.value.u32[0], attribute.value.u32[1], and attribute.value.u32[2] fields, respectively. The internal identification of that Volume's Redundant Storage Set is contained in the attribute.value.u32[3] field. The attribute.type field contains the value of 1. The value.ul1 field contains the new state: 1 (INSUFFICIENT). The value.ul2 field contains the old state: 0 (SUFFICIENT).
|
|
.1.3.6.1.4.1.232.0.13602350 |
Severity: Normal -- informational in nature. The HSV110 controller identified 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: <UL><LI>50 = The host is already logged in <LI>101 = Maximum number of logins is exceeded <LI>102 = Invalid cookie was sent <LI>106 = The password is not set on the HSV110 controller </UL>
|
|
.1.3.6.1.4.1.232.0.13602351 |
Severity: Normal -- informational in nature. The HSV110 controller identified in the handle field processed a Storage System Management Interface command with the result of non-success return code. The value.ul1 field contains internal the command type. The value.ul2 field contains the internal return code. The attribute.value.obj field contains the internal target and internal version of the command.
|
|
.1.3.6.1.4.1.232.0.13602352 |
Severity: Normal -- informational in nature. The HSV110 controller identified 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.
|
|
.1.3.6.1.4.1.232.0.13602353 |
Severity: Critical -- failure or failure imminent. The state of the Physical Disk 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: <UL><LI>1 = Normal <LI>3 = Failed <LI>4 = Not present <LI>5 = Single Port on Fibre </UL>The enclosure number, bay number, and rack number where the Physical Disk Drive is located are contained in the attribute.value.u32[0], attribute.value.u32[1], attribute.value.u32[2] fields, respectively. The attribute.type field contains value 1. The rack number in the attribute.value.u32[2] field will not contain a valid value until a future release.
|
|
.1.3.6.1.4.1.232.0.13602354 |
Severity: Critical -- failure or failure imminent. The state of the Physical Disk 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: <UL><LI>1 = Normal <LI>2 = Degraded <LI>4 = Not present <LI>5 = Single Port on Fibre </UL>The enclosure number, bay number, and rack number where the Physical Disk Drive is located are contained in the attribute.value.u32[0], attribute.value.u32[1], attribute.value.u32[2] fields, respectively. The attribute.type field contains value 1. The rack number in the attribute.value.u32[2] field will not contain a valid value until a future release.
|
|
.1.3.6.1.4.1.232.0.13602355 |
Severity: Normal -- informational in nature. The Derived Unit identified in the 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 attribute.value.obj field contains the identity of the Virtual Disk associated with that Derived Unit.
|
|
.1.3.6.1.4.1.232.0.13602356 |
Severity: Normal -- informational in nature. The internal Logical Disk associated with the Virtual Disk identified in the handle field was created. The add_handle field contains the identity of the Disk Group where this internal Logical Disk was created. The attribute.value.u64[0] field contains the size (in blocks) of the internal Logical Disk. The attribute.value.u32[2] field contains the redundancy type of the internal Logical Disk. The attribute.type field contains the value 5. The values that may be found in the attribute.value.u32[2] field are as follows: <UL><LI>1 = Vraid0 <LI>2 = Vraid1 <LI>3 = Vraid5 </UL>
|
|
.1.3.6.1.4.1.232.0.13602357 |
Severity: Normal -- informational in nature. The Disk Group identified in the handle field was created. The attribute.value.u32[0] field contains the number of physical disk drives within the Disk Group. The attribute.type field contains the value 1.
|
|
.1.3.6.1.4.1.232.0.13602358 |
Severity: Normal -- informational in nature. The Physical Disk Drive identified in the handle field was discovered. The enclosure, bay and rack where the Physical Disk Drive is located are contained in the attribute.value.u32[0], attribute.value.u32[1] and attribute.value.u32[2] fields, respectively. The attribute.type field contains the value 1.
|
|
.1.3.6.1.4.1.232.0.13602359 |
Severity: Normal -- informational in nature. The Presented Unit identified in 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. The add_handle2 field contains the associated Storage System Host path, and add_data[0] and add_data[1] contains the host LUN number.
|
|
.1.3.6.1.4.1.232.0.13602360 |
Severity: Normal -- informational in nature. The Storage System Host path identified in the handle field was created.
|
|
.1.3.6.1.4.1.232.0.13602361 |
Severity: Normal -- informational in nature. The Storage System Virtual Disk identified in the handle field was created.
|
|
.1.3.6.1.4.1.232.0.13602362 |
Severity: Normal -- informational in nature. A Volume was created. The Volume is identified in the handle field. The add_handle field contains the identity of the Physical Disk Drive that is associated with that Volume. The enclosure number, bay number, and rack number where the associated Physical Disk Drive is located are contained in the attribute.value.u32[0], attribute.value.u32[1], and attribute.value.u32[2] fields, respectively. The attribute.type field contains the value of 1.
|
|
.1.3.6.1.4.1.232.0.13602363 |
Severity: Normal -- informational in nature. The Derived Unit identified in the 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.
|
|
.1.3.6.1.4.1.232.0.13602364 |
Severity: Normal -- informational in nature. The internal Logical Disk associated with the Virtual Disk identified in the handle field was deleted.
|
|
.1.3.6.1.4.1.232.0.13602365 |
Severity: Normal -- informational in nature. The Disk Group identified in the handle field was deleted.
|
|
.1.3.6.1.4.1.232.0.13602366 |
Severity: Critical -- failure or failure imminent. The Physical Disk Drive identified in the handle field has disappeared. The enclosure, bay and rack where the Physical Disk Drive is located are contained in the attribute.value.u32[0], attribute.value.u32[1] and attribute.value.u32[2] fields, respectively. The attribute.type field contains the value 1.
|
|
.1.3.6.1.4.1.232.0.13602367 |
Severity: Normal -- informational in nature. The Presented Unit identified in 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.
|
|
.1.3.6.1.4.1.232.0.13602368 |
Severity: Normal -- informational in nature. The Storage System Host path identified in the handle field was deleted.
|
|
.1.3.6.1.4.1.232.0.13602369 |
Severity: Normal -- informational in nature. The Storage System Virtual Disk identified in the handle field was deleted. The Storage System Virtual Disk is associated with the Virtual Disk identified in the add_handle field.
|
|
.1.3.6.1.4.1.232.0.13602371 |
Severity: Normal -- informational in nature. The HSV110 controller identified 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.
|
|
.1.3.6.1.4.1.232.0.13602372 |
Severity: Undetermined -- more information needed to determine severity. An HSV110 controller has left the Storage System. The HSV110 controller is identified in the handle field. If the handle field is zero, the HSV110 controller identity could not be obtained due to an unexpected state transition.
|
|
.1.3.6.1.4.1.232.0.13602373 |
Severity: Normal -- informational in nature. A Storage System has been deleted by an HSV110 controller. The Storage System is identified in the handle field. The HSV110 controller is 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.
|
|
.1.3.6.1.4.1.232.0.13602374 |
Severity: Normal -- informational in nature. The Data Replication Group identified in the handle field was created.
|
|
.1.3.6.1.4.1.232.0.13602375 |
Severity: Normal -- informational in nature. The Data Replication Group identified in the handle field was deleted.
|
|
.1.3.6.1.4.1.232.0.13602376 |
Severity: Normal -- informational in nature. The internal Logical Disk associated with the Snapshot Virtual Disk identified in the handle field was created. The add_handle field contains the identity of the Disk Group where this internal Logical Disk was created. The attribute.value.u64[0] field contains the size (in blocks) of the reserved capacity of the internal Logical Disk. The attribute.value.u32[2] field contains the redundancy type of the internal Logical Disk. The attribute.value.u32[3] field contains the noid of the associated successor internal Logical Disk. The attribute.type field contains the value 6. The values that may be found in the attribute.value.u32[2] field are as follows: <UL><LI>1 = Vraid0 <LI>2 = Vraid1 <LI>3 = Vraid5 </UL>
|
|
.1.3.6.1.4.1.232.0.13602377 |
Severity: Normal -- informational in nature. The internal Logical Disk associated with the Copy of the Virtual Disk identified in the handle field was created. The add_handle field contains the identity of the Disk Group where this internal Logical Disk was created. The attribute.value.u64[0] field contains the size (in blocks) of the reserved capacity of the target Virtual Disk. The attribute.value.u32[2] field contains the redundancy type of the internal Logical Disk. The attribute.value.u32[3] field contains the noid of the associated successor internal Logical Disk. The attribute.type field contains the value 6. The values that may be found in the attribute.value.u32[2] field are as follows: <UL><LI>1 = Vraid0 <LI>2 = Vraid1 <LI>3 = Vraid5 </UL>
|
|
.1.3.6.1.4.1.232.0.136024001 |
Windows system error
|
|
.1.3.6.1.4.1.232.0.136024002 |
Lock is already taken
|
|
.1.3.6.1.4.1.232.0.136024003 |
Lock is not taken
|
|
.1.3.6.1.4.1.232.0.136024004 |
Request timed out
|
|
.1.3.6.1.4.1.232.0.13602405 |
Severity: Normal -- informational in nature. The Host Operating System mode 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: <UL><LI>0 = Unknown <LI>1 = User defined <LI>2 = Unused <LI>3 = WINNT with SecurePath <LI>4 = VMS <LI>5 = TRU64 UNIX <LI>6 = Sun UNIX <LI>7 = NetWare <LI>8 = HP <LI>9 = IBM <LI>10 = LINUX <LI>11 = SCO UNIX </UL>
|
|
.1.3.6.1.4.1.232.0.13602406 |
Severity: Normal -- informational in nature. Time was set on the Storage System identified in the handle field.
|
|
.1.3.6.1.4.1.232.0.13602407 |
Severity: Normal -- informational in nature. The LUN of the Presented Unit 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.
|
|
.1.3.6.1.4.1.232.0.13602408 |
Severity: Normal -- informational in nature. The Device Addition Policy of the 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: <UL><LI>1 = Manual policy <LI>2 = Automatic policy </UL>
|
|
.1.3.6.1.4.1.232.0.13602409 |
Severity: Normal -- informational in nature. The Quiescent state of 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 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: <UL><LI>0 = Not quiescent <LI>1 = Quiescent </UL>This Storage System Virtual Disk is associated with the Virtual Disk identified in the add_handle field.
|
|
.1.3.6.1.4.1.232.0.13602410 |
Severity: Normal -- informational in nature. The Enabled/Disabled state of 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: <UL><LI>1 = Disabled <LI>2 = Enabled </UL>This Storage System Virtual Disk is associated with the Virtual Disk identified in the add_handle field.
|
|
.1.3.6.1.4.1.232.0.13602411 |
Severity: Normal -- informational in nature. The Cache Policy of the Storage System Virtual Disk identified in the handle field has changed. <P> 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: <UL><LI>1 = Writethrough <LI>2 = Writeback </UL><P> 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: <UL><LI>1 = Read cache on <LI>2 = Read cache off </UL><P> 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: <UL><LI>1 = Mirror <LI>2 = No mirror </UL>This Storage System Virtual Disk is associated with the Virtual Disk identified in the add_handle field.
|
|
.1.3.6.1.4.1.232.0.13602412 |
Severity: Normal -- informational in nature. The Usage state of a Volume changed. The affected Volume is identified in the handle field. 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: <UL><LI>1 = Disk Group <LI>2 = Reserved <LI>4 - 20 = temporary usage reserved for drive code load </UL>This Volume is associated with the Disk Group identified in the add_handle field, if either the old Usage state or the new Usage state is 1. The secondary_id field contains the internal identification of that Volume's Redundant Storage Set.
|
|
.1.3.6.1.4.1.232.0.13602413 |
Severity: Normal -- informational in nature. The Disk Failure Protection Level 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.
|
|
.1.3.6.1.4.1.232.0.13602414 |
Severity: Normal -- informational in nature. The Write Protected state of the Derived Unit identified in the handle field has changed. This Derived Unit is associated with the Virtual Disk identified in the add_handle field. 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: <UL><LI>0 = Write protect off <LI>1 = Write protect on </UL>This Derived Unit is associated with the Virtual Disk identified in the add_handle field.
|
|
.1.3.6.1.4.1.232.0.13602416 |
Severity: Warning -- not failed but attention recommended or required. The Physical Disk Drive identified in the handle field has experienced numerous communication failures on a particular Fibre Channel port identified in the new_attr.value.str field. The old_attr.value.u32[0] field contains the internal port ID. The enclosure number, bay number, and rack number where the Physical Disk Drive is located are contained in the old_attr.value.u32[1], old_attr.value.u32[2], old_attr.value.u32[3] fields, respectively. The old_attr.type field contains value 1. The new_attr.value.str field contains the cerp_id of the Fibre Channel port. The new_attr.type field contains value 4.
|
|
.1.3.6.1.4.1.232.0.13602417 |
Severity: Normal -- informational in nature. The HSV110 controller identified in the handle field received a request to shutdown. <P> The old_attr.type field and field contain the value 1. The old_attr.value.u32[0] field indicates the type of restart that was requested as follows: <UL><LI>0 = None -- no restart <LI>1 = Regular -- full restart, host system connectivity is lost until the controller returns to normal operation <LI>2 = Fast -- resynchronization, restart of the controller in a manner that has little or no impact on host system connectivity </UL><P> 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: <UL><LI>0 = Remain operational <LI>1 = Coupled shutdown </UL><P> 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: <UL><LI>0 = Remain in the power on state <LI>1 = Power itself off </UL><P> 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: <UL><LI>0 = Remain in the power on state <LI>1 = Powered off </UL><P> 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: <UL><LI>0 = Enabled <LI>1 = Disabled </UL><P> The old_attr.value.u32[5] field contains the number of seconds the shutdown operation was requested to be delayed.
|
|
.1.3.6.1.4.1.232.0.13602418 |
Severity: Normal -- informational in nature. The HSV110 controller identified in the handle field has completed its shutdown preparations. <P> The old_attr.type field 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: <UL><LI>1 = Success <LI>2 = Failure <LI>3 = Not applicable </UL><P> The old_attr.value.u32[1] field contains the internal Storage System Management Interface cache shutdown status code. <P> The old_attr.value.u32[2] field value indicates the result of the Physical Disk Drive enclosure(s) power off operation as follows: <UL><LI>1 = Success <LI>2 = Failure <LI>3 = Not applicable </UL><P> The old_attr.value.u32[3] field contains the internal Storage System Management Interface Physical Disk Drive enclosure(s) power off status code. <P> The old_attr.value.u32[4] field value indicates the result of the battery assemblies disable operation as follows: <UL><LI>1 = Success <LI>2 = Failure <LI>3 = Not applicable </UL><P> The old_attr.value.u32[5] field value indicates the battery assemblies disable operation failure mode as follows: <UL><LI>0 = No failure indicated. <LI>1 = Failed only on the HSV110 controller identified in the handle field. <LI>2 = Failed only on the other HSV110 controller of the pair. <LI>3 = Failed on both HSV110 controllers. </UL>
|
|
.1.3.6.1.4.1.232.0.13602419 |
Severity: Normal -- informational in nature. The Failsafe state of the Data Replication Group identified in the handle field has changed. The old_attr.value.u32[0] field contains the old Failsafe state. The new_attr.value.u32[0] field contains the new Failsafe state. The Failsafe state values that may be found in the old_attr.value.u32[0] and new_attr.value.u32[0] fields are as follows: <UL><LI>1 = Failsafe Disabled <LI>2 = Failsafe Enabled </UL>
|
|
.1.3.6.1.4.1.232.0.13602420 |
Severity: Normal -- informational in nature. The Mode of the Data Replication Group identified in the handle field has changed. The old_attr.value.u32[0] field contains the old Mode. The new_attr.value.u32[0] field contains the new Mode. The Mode values that may be found in the old_attr.value.u32[0] and new_attr.value.u32[0] fields are as follows: <UL><LI>0 = Normal Active Source <LI>1 = Normal Active Destination <LI>2 = Active/Active (Master) <LI>3 = Active/Active (Non-Master) </UL>
|
|
.1.3.6.1.4.1.232.0.13602421 |
Severity: Normal -- informational in nature. The Operational state of a Data Replication Group has changed to Synchronous or Asynchronous. The old_attr.value.u32[0] field contains the old Operation state. The new_attr.value.u32[0] field contains the new Operation state. The Operation state values that may be found in the old_attr.value.u32[0] and new_attr.value.u32[0] fields are as follows: <UL><LI>1 = Synchronous <LI>2 = Asynchronous </UL>
|
|
.1.3.6.1.4.1.232.0.13602422 |
Severity: Normal -- informational in nature. The Read Only attribute of the Data Replication Group identified in the handle field has changed. The old_attr.value.u32[0] field contains the old Read Only attribute. The new_attr.value.u32[0] field contains the new Read Only attribute. The Read Only attribute values that may be found in the old_attr.value.u32[0] and new_attr.value.u32[0] fields are as follows: <UL><LI>0 = Data Replication Destination Storage System Virtual Disk disabled for read access. <LI>1 = Data Replication Destination Storage System Virtual Disk enabled for read access. </UL>
|
|
.1.3.6.1.4.1.232.0.13602423 |
Severity: Normal -- informational in nature. A Data Replication Group failover has occurred. The handle field contains the identity of the Data Replication Group. The old_attr.value.u32[0] field contains the old Role. The new_attr.value.u32[0] field contains the new Role. <UL><LI>0 = Normal Active Source <LI>1 = Normal Active Destination <LI>2 = Active/Active (Master) <LI>3 = Active/Active (Non-Master) </UL>
|
|
.1.3.6.1.4.1.232.0.13602424 |
Severity: Normal -- informational in nature. A Data Replication Group has been suspended or resumed. The handle field contains the identity of the Data Replication Group. The old_attr.value.u32[0] field contains the old Suspend state. The new_attr.value.u32[0] field contains the new Suspend state. The Suspend state values that may be found in the old_attr.value.u32[0] and new_attr.value.u32[0] fields are as follows: <UL><LI>1 = Connection between the Data Replication Source and Data Replication Destination is active. <LI>2 = Connection between the Data Replication Source and Data Replication Destination is inactive. </UL>
|
|
.1.3.6.1.4.1.232.0.13602425 |
Severity: Normal -- informational in nature. A Storage System Virtual Disk was added to a Data Replication Group. The Storage System Virtual Disk is identified in the add_handle field. The Data Replication Group is identified in the handle field.
|
|
.1.3.6.1.4.1.232.0.13602426 |
Severity: Normal -- informational in nature. A Storage System Virtual Disk was removed from a Data Replication Group. The Storage System Virtual Disk is identified in the add_handle field. The Data Replication Group is identified in the handle field.
|
|
.1.3.6.1.4.1.232.0.136025001 |
No path to controller
|
|
.1.3.6.1.4.1.232.0.136025002 |
Thread is not running
|
|
.1.3.6.1.4.1.232.0.136025003 |
No physical stores
|
|
.1.3.6.1.4.1.232.0.136025004 |
Loop context ID changed
|
|
.1.3.6.1.4.1.232.0.136025005 |
Storage Cell context ID changed
|
|
.1.3.6.1.4.1.232.0.136025006 |
Cache Write Failure
|
|
.1.3.6.1.4.1.232.0.136025007 |
Battery Disable Failure
|
|
.1.3.6.1.4.1.232.0.136025008 |
Drive Shelf Disable Failure
|
|
.1.3.6.1.4.1.232.0.136025009 |
Shutdown Both Restart And Power Off Requested
|
|
.1.3.6.1.4.1.232.0.136025010 |
Shutdown Drive Shelf Power Off But No Enclosure Power Off Requested
|
|
.1.3.6.1.4.1.232.0.136025011 |
Shutdown Disable Battery But No Enclosure Power Off Requested
|
|
.1.3.6.1.4.1.232.0.136025012 |
Shutdown Disable Battery But Shutdown Unconditional Requested
|
|
.1.3.6.1.4.1.232.0.136025013 |
Shutdown Delay Out Of Range
|
|
.1.3.6.1.4.1.232.0.136025014 |
Invalid Storage Cell name
|
|
.1.3.6.1.4.1.232.0.136025015 |
Requested spares goal cannot be satisfied
|
|
.1.3.6.1.4.1.232.0.136025016 |
No valid LDAD found
|
|
.1.3.6.1.4.1.232.0.136025017 |
Mismatched MLD size
|
|
.1.3.6.1.4.1.232.0.136025018 |
Codeload image file error
|
|
.1.3.6.1.4.1.232.0.136025019 |
Storage System is not initialized
|
|
.1.3.6.1.4.1.232.0.13602504 |
Severity: Undetermined -- more information needed to determine severity. The Data Availability state of the internal Logical Disk associated with the Virtual Disk identified in the handle field 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).
|
|
.1.3.6.1.4.1.232.0.13602505 |
Severity: Undetermined -- more information needed to determine severity. The state of the Disk Group 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: <UL><LI>1 = Normal <LI>2 = Disk Group with no redundancy is inoperative <LI>3 = Disk Group with parity redundancy is inoperative <LI>4 = Disk Group with mirrored redundancy is inoperative <LI>5 = Disk Group with no redundancy is inoperative, marked for re-use <LI>6 = Disk Group with parity redundancy is inoperative, marked for re-use <LI>7 = Disk Group with mirrored redundancy is inoperative, marked for re-use </UL>
|
|
.1.3.6.1.4.1.232.0.13602506 |
Severity: Undetermined -- more information needed to determine severity. The state of the internal Logical 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: <UL><LI>1 = Normal <LI>2 = Replacement delay in progress <LI>3 = Redundancy lost, restore in progress <LI>4 = Redundancy lost, restore stalled <LI>6 = Creation in progress <LI>7 = Snapshot is inoperative due to lack of snapshot space <LI>8 = Deletion in progress <LI>9 = Capacity change in progress <LI>10 = Inoperative due to data lost <LI>11 = Capacity reservation in progress <LI>12 = Capacity unreservation in progress </UL>
|
|
.1.3.6.1.4.1.232.0.13602507 |
Severity: Critical -- failure or failure imminent. The state of the internal Logical 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: <UL><LI>1 = Normal <LI>2 = Replacement delay in progress <LI>3 = Redundancy lost, restore in progress <LI>4 = Redundancy lost, restore stalled <LI>5 = Failed <LI>6 = Creation in progress <LI>8 = Deletion in progress <LI>9 = Capacity change in progress <LI>10 = Inoperative due to device data lost <LI>11 = Capacity reservation in progress <LI>12 = Capacity unreservation in progress </UL>
|
|
.1.3.6.1.4.1.232.0.13602508 |
Severity: Undetermined -- more information needed to determine severity. The state of the internal Logical 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: <UL><LI>1 = Normal <LI>2 = Replacement delay in progress <LI>3 = Redundancy lost restore, in progress <LI>4 = Redundancy lost restore, stalled <LI>5 = Failed <LI>6 = Creation in progress <LI>7 = Snapshot is inoperative due to lack of snapshot space <LI>8 = Deletion in progress <LI>9 = Capacity change in progress <LI>11 = Capacity reservation in progress <LI>12 = Capacity unreservation in progress </UL>
|
|
.1.3.6.1.4.1.232.0.13602509 |
Severity: Undetermined -- more information needed to determine severity. The state of the Fibre Channel 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). <P> Note that the HSV110 controller's internal identity of the affected Fibre Channel port is contained in the secondary_id field.
|
|
.1.3.6.1.4.1.232.0.13602510 |
Severity: Normal -- informational in nature. The state of the Disk Group 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: <UL><LI>1 = Normal <LI>2 = Disk Group with no redundancy is inoperative <LI>3 = Disk Group with parity redundancy is inoperative <LI>4 = Disk Group with mirrored redundancy is inoperative <LI>5 = Disk Group with no redundancy is inoperative, marked for re-use <LI>6 = Disk Group with parity redundancy is inoperative, marked for re-use <LI>7 = Disk Group with mirrored redundancy is inoperative, marked for re-use </UL>
|
|
.1.3.6.1.4.1.232.0.13602511 |
Severity: Warning -- not failed but attention recommended or required. The state of the Physical Disk 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: <UL><LI>1 = Normal <LI>2 = Degraded <LI>3 = Failed <LI>5 = Single Port on Fibre </UL>The enclosure number, bay number, and rack number where the Physical Disk Drive is located are contained in the attribute.value.u32[0], attribute.value.u32[1], attribute.value.u32[2] fields, respectively. The attribute.type field contains value 1. The rack number in the attribute.value.u32[2] field will not contain a valid value until a future release.
|
|
.1.3.6.1.4.1.232.0.13602512 |
Severity: Normal -- informational in nature. The HSV110 controller identified in the handle field no longer needs attention.
|
|
.1.3.6.1.4.1.232.0.13602513 |
Severity: Undetermined -- more information needed to determine severity. The HSV110 controller identified in the handle field needs attention.
|
|
.1.3.6.1.4.1.232.0.13602514 |
Severity: Critical -- failure or failure imminent. The Blower Present flag for the '1' 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).
|
|
.1.3.6.1.4.1.232.0.13602515 |
Severity: Undetermined -- more information needed to determine severity. At least one Virtual Disk associated with the Data Replication Group identified in the handle field has transitioned to the INOPERATIVE state. The remaining Virtual Disks associated with this Data Replication Group have been forced INOPERATIVE. The value.ul1 field contains the new Data Replication Group member state: 2 (INOPERATIVE). The value.ul2 field contains the old Data Replication Group member state: 1 (OPERATIVE).
|
|
.1.3.6.1.4.1.232.0.13602516 |
Severity: Normal -- informational in nature. All the Virtual Disks associated with the Data Replication Group identified in the handle field have transitioned to the OPERATIVE state. The value.ul1 field contains the new Data Replication Group member state: 1 (OPERATIVE). The value.ul2 field contains the old Data Replication Group member state: 2 (INOPERATIVE).
|
|
.1.3.6.1.4.1.232.0.13602517 |
Severity: Normal -- informational in nature. The state of the Physical Disk Drive identified in the handle field has transitioned to the Single Port on Fibre state. The value.ul1 field contains the new state: 5 (SINGLE PORT ON FIBRE). The value.ul2 field contains the old state. The state values that may be in the value.ul2 field are as follows: <UL><LI>1 = Normal <LI>2 = Degraded <LI>3 = Failed <LI>4 = Not Present </UL>The enclosure number, bay number, and rack number where the Physical Disk Drive is located are contained in the attribute.value.u32[0], attribute.value.u32[1], attribute.value.u32[2] fields, respectively. The attribute.type field contains value 1. The rack number in the attribute.value.u32[2] field will not contain a valid value until a future release.
|
|
.1.3.6.1.4.1.232.0.13602518 |
Severity: Normal -- informational in nature. The HSV110 controller identified in the handle field has been shutdown because the temperature sensors do not agree and the system temperature can not be accurately determined. The value.ul1 field contains the current temperature reported in celsius from I2C sensor 1, while the value.ul2 field contains the reading from I2C sensor 2.
|
|
.1.3.6.1.4.1.232.0.13602519 |
Severity: Normal -- informational in nature. The HSV110 controller identified in the handle field has been shutdown because the temperature sensors can not be accessed and the system temperature can not be accurately determined. The value.ul1 field contains the status from the attempted I2C access.
|
|
.1.3.6.1.4.1.232.0.136026002 |
Invalid data replication operation
|
|
.1.3.6.1.4.1.232.0.136026005 |
DR group name exceeds maximum length
|
|
.1.3.6.1.4.1.232.0.136026006 |
DR group created successfully
|
|
.1.3.6.1.4.1.232.0.136026007 |
Data replication invalid mode for DR Group create
|
|
.1.3.6.1.4.1.232.0.136026008 |
A duplicate DR group name exists in the specified source or destination DR group.
|
|
.1.3.6.1.4.1.232.0.136026009 |
Data replication invalid operation while DR Groups exist
|
|
.1.3.6.1.4.1.232.0.136026010 |
Data replication root folder does not exist
|
|
.1.3.6.1.4.1.232.0.136026011 |
DR group discarded
|
|
.1.3.6.1.4.1.232.0.136026012 |
Data replication unknown remote storage system
|
|
.1.3.6.1.4.1.232.0.136026013 |
Data replication Error. A conflicting Vdisk name exists on the remote storage system.
|
|
.1.3.6.1.4.1.232.0.136026014 |
Data Replication Error. Invalid Remote Vdisk Name specified.
|
|
.1.3.6.1.4.1.232.0.136026015 |
Data Replication Error. Remote Vdisk size cannot be modified.
|
|
.1.3.6.1.4.1.232.0.136026016 |
Data Replication Error. Remote Vdisk should be unpresented to proceed with the discard/detach operation.
|
|
.1.3.6.1.4.1.232.0.136027001 |
The element manager has successfully initialized storage system. Command issued through XML Interface.
|
|
.1.3.6.1.4.1.232.0.136027002 |
The element manager has successfully created a virtual disk. Command issued through the XML Interface.
|
|
.1.3.6.1.4.1.232.0.136027003 |
The element manager has successfully created a disk group. Command issued through the XML Interface.
|
|
.1.3.6.1.4.1.232.0.136027004 |
The element manager has successfully created a DRM group. Command issued through the XML Interface.
|
|
.1.3.6.1.4.1.232.0.136027005 |
The element manager has successfully created a host. Command issued through the XML Interface.
|
|
.1.3.6.1.4.1.232.0.136027006 |
The element manager has successfully created a presented unit. Command issued through the XML Interface.
|
|
.1.3.6.1.4.1.232.0.136027007 |
The element manager has successfully created a virtual disk folder. Command issued through the XML Interface.
|
|
.1.3.6.1.4.1.232.0.136027008 |
The element manager has successfully created a host folder. Command issued through the XML Interface.
|
|
.1.3.6.1.4.1.232.0.136027009 |
The element manager has successfully created a disk group folder. Command issued through the XML Interface.
|
|
.1.3.6.1.4.1.232.0.136027010 |
The element manager has successfully created a DRM group folder. Command issued through the XML Interface.
|
|
.1.3.6.1.4.1.232.0.136027011 |
The element manager has successfully created a folder. Command issued through the XML Interface.
|
|
.1.3.6.1.4.1.232.0.136027012 |
The element manager has successfully created a snapshot. Command issued through the XML Interface.
|
|
.1.3.6.1.4.1.232.0.136027013 |
The element manager has successfully created a snapclone. Command issued through the XML Interface.
|
|
.1.3.6.1.4.1.232.0.136027014 |
The element manager has successfully uninitialized the storage system. Command issued through the XML Interface.
|
|
.1.3.6.1.4.1.232.0.136027015 |
The element manager has successfully deleted a virtual disk. Command issued through the XML Interface.
|
|
.1.3.6.1.4.1.232.0.136027016 |
The element manager has successfully deleted a disk group. Command issued through the XML Interface.
|
|
.1.3.6.1.4.1.232.0.136027017 |
The element manager has successfully deleted a DRM group. Command issued through the XML Interface.
|
|
.1.3.6.1.4.1.232.0.136027018 |
The element manager has successfully deleted a host. Command issued through the XML Interface.
|
|
.1.3.6.1.4.1.232.0.136027019 |
The element manager has successfully deleted a presented unit. Command issued through the XML Interface.
|
|
.1.3.6.1.4.1.232.0.136027020 |
The element manager has successfully deleted a virtual disk folder. Command issued through the XML Interface.
|
|
.1.3.6.1.4.1.232.0.136027021 |
The element manager has successfully deleted a host folder. Command issued through the XML Interface.
|
|
.1.3.6.1.4.1.232.0.136027022 |
The element manager has successfully deleted a disk group folder. Command issued through the XML Interface.
|
|
.1.3.6.1.4.1.232.0.136027023 |
The element manager has successfully deleted a DRM group folder. Command issued through the XML Interface.
|
|
.1.3.6.1.4.1.232.0.136027024 |
The element manager has successfully deleted a folder. Command issued through the XML Interface.
|
|
.1.3.6.1.4.1.232.0.136027025 |
The element manager has successfully deleted a snapshot. Command issued through the XML Interface.
|
|
.1.3.6.1.4.1.232.0.136027026 |
The element manager has successfully modified the properties of a storage system. Command issued through the XML Interface.
|
|
.1.3.6.1.4.1.232.0.136027027 |
The element manager has successfully modified the properties of a virtual disk. Command issued through the XML Interface.
|
|
.1.3.6.1.4.1.232.0.136027028 |
The element manager has successfully modified the properties of a disk group. Command issued through the XML Interface.
|
|
.1.3.6.1.4.1.232.0.136027029 |
The element manager has successfully modified the properties of a DRM group. Command issued through the XML Interface.
|
|
.1.3.6.1.4.1.232.0.136027030 |
The element manager has successfully modified the properties of a host. Command issued through the XML Interface.
|
|
.1.3.6.1.4.1.232.0.136027031 |
The element manager has successfully modified the properties of a presented unit. Command issued through the XML Interface.
|
|
.1.3.6.1.4.1.232.0.136027032 |
The element manager has successfully modified the properties of a virtual disk folder. Command issued through the XML Interface.
|
|
.1.3.6.1.4.1.232.0.136027033 |
The element manager has successfully modified the properties of a host folder. Command issued through the XML Interface.
|
|
.1.3.6.1.4.1.232.0.136027034 |
The element manager has successfully modified the properties of a hardware root folder. Command issued through the XML Interface.
|
|
.1.3.6.1.4.1.232.0.136027035 |
The element manager has successfully modified the properties of a disk group folder. Command issued through the XML Interface.
|
|
.1.3.6.1.4.1.232.0.136027036 |
The element manager has successfully modified the properties of a DRM group folder. Command issued through the XML Interface.
|
|
.1.3.6.1.4.1.232.0.136027037 |
The element manager has successfully modified the properties of a DRM group root folder. Command issued through the XML Interface.
|
|
.1.3.6.1.4.1.232.0.136027038 |
The element manager has successfully modified the properties of a folder. Command issued through the XML Interface.
|
|
.1.3.6.1.4.1.232.0.136027039 |
The element manager has successfully modified the properties of a snapshot. Command issued through the XML Interface.
|
|
.1.3.6.1.4.1.232.0.136027040 |
The element manager has successfully modified the properties of a disk. Command issued through the XML Interface.
|
|
.1.3.6.1.4.1.232.0.136027041 |
The element manager has successfully modified the properties of a disk shelf. Command issued through the XML Interface.
|
|
.1.3.6.1.4.1.232.0.136027042 |
The element manager has successfully modified the properties of a controller. Command issued through the XML Interface.
|
|
.1.3.6.1.4.1.232.0.136027043 |
The element manager has successfully modified the properties of a controller shelf. Command issued through the XML Interface.
|
|
.1.3.6.1.4.1.232.0.136027044 |
The element manager has successfully modified the properties of a cabinet. Command issued through the XML Interface.
|
|
.1.3.6.1.4.1.232.0.136027045 |
The element manager has successfully reserved an object. Command issued through the XML Interface.
|
|
.1.3.6.1.4.1.232.0.136027046 |
The element manager has successfully released an object. Command issued through the XML Interface.
|
|
.1.3.6.1.4.1.232.0.136027047 |
XML cache mutex timeout.
|
|
.1.3.6.1.4.1.232.0.136027048 |
XML cache memory allocation error.
|
|
.1.3.6.1.4.1.232.0.136027049 |
XML subsystem unknown error.
|
|
.1.3.6.1.4.1.232.0.13602816 |
Severity: Normal -- informational in nature. The HSV110 controller identified 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.
|
|
.1.3.6.1.4.1.232.0.13603072 |
Severity: Normal -- informational in nature. The specified Destination Virtual Disk has successfully completed a Full Copy. The following fields are not valid: status, blocks, vda.
|
|
.1.3.6.1.4.1.232.0.13603073 |
Severity: Critical -- failure or failure imminent. The specified Source Virtual Disk has transitioned to the Logging state because the alternate Storage System is not accessible or the Data Replication Group is suspended. The following fields are not valid: status, blocks, vda, port, cerp_id, side.
|
|
.1.3.6.1.4.1.232.0.13603074 |
Severity: Critical -- failure or failure imminent. The specified Source Virtual Disk has transitioned to the Logging state because the Destination Virtual Disk is not accessible. The following fields are not valid: status, blocks, vda, port, cerp_id, side.
|
|
.1.3.6.1.4.1.232.0.13603075 |
Severity: Normal -- informational in nature. The specified Destination Virtual Disk has transitioned to the Merging state, because the alternate Storage System or Destination Virtual Disk is now accessible or resumed. The following fields are not valid: status, blocks, vda.
|
|
.1.3.6.1.4.1.232.0.13603076 |
Severity: Critical -- failure or failure imminent. A Data Replication Group has entered the Failsafe Locked state due to an inaccessible or inoperative destination. Either the Destination Virtual Disk is not accessible or a Virtual Disk in the Data Replication Group is inoperative. The following fields are not valid: status, blocks, vda, port, cerp_id, side.
|
|
.1.3.6.1.4.1.232.0.13603077 |
Severity: Critical -- failure or failure imminent. A Data Replication Group has entered the Failsafe Locked state due to an inoperative source. Either the Source Virtual Disk is not accessible or a Virtual Disk in the Data Replication Group is inoperative. The following fields are not valid: status, blocks, vda, port, cerp_id, side.
|
|
.1.3.6.1.4.1.232.0.13603078 |
Severity: Critical -- failure or failure imminent. An unrecoverable read error occurred on the specified Source Virtual Disk during the Full Copy. The Virtual Disk address specified in the vda field indicates the first block in error. The Full Copy was terminated.
|
|
.1.3.6.1.4.1.232.0.13603079 |
Severity: Critical -- failure or failure imminent. A Full Copy terminated prior to completion. A remote copy error occurred due to an inaccessible alternate Storage System. The Virtual Disk address specified in the vda field indicates the first block in error. The Full Copy will continue when the Data Replication Destination is restored.
|
|
.1.3.6.1.4.1.232.0.13603080 |
Severity: Critical -- failure or failure imminent. A Full Copy terminated prior to completion. A remote copy error occurred due to an inaccessible Destination Virtual Disk. The Virtual Disk address specified in the vda field indicates the first block in error. The Full Copy will continue when the Data Replication Destination is restored.
|
|
.1.3.6.1.4.1.232.0.13603081 |
Severity: Warning -- not failed but attention recommended or required. A Data Replication Log has been reset due to insufficient Disk Group capacity. The Data Replication Destination has been marked for a Full Copy. The following fields are not valid: status, blocks, vda, port, cerp_id, side.
|
|
.1.3.6.1.4.1.232.0.13603082 |
Severity: Normal -- informational in nature. A Data Replication Log has been reset due to a Data Replication Group failover. The following fields are not valid: status, blocks, vda.
|
|
.1.3.6.1.4.1.232.0.13603084 |
Severity: Normal -- informational in nature. A Destination Data Replication Group has successfully completed a Merge. The following fields are not valid: status, blocks, vda.
|
|
.1.3.6.1.4.1.232.0.13603087 |
Severity: Normal -- informational in nature. A Data Replication Group is no longer in a Failsafe Locked state. The following fields are not valid: status, blocks, vda, port, cerp_id, side.
|
|
.1.3.6.1.4.1.232.0.13603088 |
Severity: Normal -- informational in nature. A Destination Data Replication Group has been marked for a Full Copy. The following fields are not valid: status, blocks, vda.
|
|
.1.3.6.1.4.1.232.0.13603089 |
Severity: Normal -- informational in nature. A Storage System has discovered that a Data Replication Group failover has taken place. This Virtual Disk is transitioning from a Data Replication Source role to a Data Replication Destination role. The following fields are not valid: status, blocks, vda.
|
|
.1.3.6.1.4.1.232.0.13603090 |
Severity: Normal -- informational in nature. This Data Replication Group is transitioning from a Data Replication Destination role to a Data Replication Source role. The following fields are not valid: status, blocks, vda.
|
|
.1.3.6.1.4.1.232.0.13603093 |
Severity: Normal -- informational in nature. The Data Replication Path between this Site and the Alternate Site has closed, possibly due to a connection failure between the specified host port and the Alternate Site. The following fields are not valid: group_name_uuid, group_uuid, source_scvd_uuid, status, block, vda.
|
|
.1.3.6.1.4.1.232.0.13603328 |
Severity: Critical -- failure or failure imminent. Unrecognized event reported by a Drive Enclosure Environmental Monitoring Unit. The handle field contains the WWN of the drive enclosure containing the Drive Enclosure Environmental Monitoring Unit. The event was reported by the Drive Enclosure Environmental Monitoring Unit located in the drive enclosure determined by the content of the dencl_num field as follows: <UL><LI>If dencl_num is less than 99, the location is as indicated by the content of the rack_num and dencl_num fields. <LI>If dencl_num is equal to 99, the location is unknown. Note that the content of the rack_num field is undefined in this case. <LI>If dencl_num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the rack_num and dencl_num fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate. </UL>Note that the content of 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. The enclosures array shows the drive enclosures available on the Fibre Channel loop pair (0 = Loop A, 1 = Loop B) identified in the loop field. The location of an available drive enclosure is determined by the content of the enclosures.dencl_num field as follows: <UL><LI>If enclosures.dencl_num is less than 99, the location is as indicated by the content of the enclosures.rack_num and enclosures.dencl_num fields. <LI>If enclosures.dencl_num is equal to 99, the enclosures array entry is not used. Note that the content of the enclosures.rack_num field is undefined in this case. <LI>If enclosures.dencl_num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the enclosures.rack_num and enclosures.dencl_num fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate. </UL>Note that the content of the enclosures.rack_num field will not be valid until a future release.
|
|
.1.3.6.1.4.1.232.0.13603329 |
Severity: Critical -- failure or failure imminent. A physical disk drive that is not Fibre Channel compatible or cannot operate at the link rate established by the drive enclosure I/O modules was detected. The handle field contains the WWN of the drive enclosure containing the Drive Enclosure Environmental Monitoring Unit. This problem was detected by the Drive Enclosure Environmental Monitoring Unit located in the drive enclosure determined by the content of the dencl_num field as follows: <UL><LI>If dencl_num is less than 99, the location is as indicated by the content of the rack_num and dencl_num fields. <LI>If dencl_num is equal to 99, the location is unknown. Note that the content of the rack_num field is undefined in this case. <LI>If dencl_num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the rack_num and dencl_num fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate. </UL>Note that the content of the rack_num field will not be valid until a future release. This problem was detected during spin up of the physical disk drive installed in the drive enclosure bay identified in the alarm_error_code.field.en field. The enclosures array shows the drive enclosures available on the Fibre Channel loop pair (0 = Loop A, 1 = Loop B) identified in the loop field. The location of an available drive enclosure is determined by the content of the enclosures.dencl_num field as follows: <UL><LI>If enclosures.dencl_num is less than 99, the location is as indicated by the content of the enclosures.rack_num and enclosures.dencl_num fields. <LI>If enclosures.dencl_num is equal to 99, the enclosures array entry is not used. Note that the content of the enclosures.rack_num field is undefined in this case. <LI>If enclosures.dencl_num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the enclosures.rack_num and enclosures.dencl_num fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate. </UL>Note that the content of the enclosures.rack_num field will not be valid until a future release.
|
|
.1.3.6.1.4.1.232.0.13603330 |
Severity: Warning -- not failed but attention recommended or required. A physical disk drive is improperly installed or missing. This could affect the drive enclosure air flow and cause an over temperature condition. The handle field contains the WWN of the drive enclosure containing the Drive Enclosure Environmental Monitoring Unit. This problem was detected by the Drive Enclosure Environmental Monitoring Unit located in the drive enclosure determined by the content of the dencl_num field as follows: <UL><LI>If dencl_num is less than 99, the location is as indicated by the content of the rack_num and dencl_num fields. <LI>If dencl_num is equal to 99, the location is unknown. Note that the content of the rack_num field is undefined in this case. <LI>If dencl_num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the rack_num and dencl_num fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate. </UL>Note that the content of 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. The enclosures array shows the drive enclosures available on the Fibre Channel loop pair (0 = Loop A, 1 = Loop B) identified in the loop field. The location of an available drive enclosure is determined by the content of the enclosures.dencl_num field as follows: <UL><LI>If enclosures.dencl_num is less than 99, the location is as indicated by the content of the enclosures.rack_num and enclosures.dencl_num fields. <LI>If enclosures.dencl_num is equal to 99, the enclosures array entry is not used. Note that the content of the enclosures.rack_num field is undefined in this case. <LI>If enclosures.dencl_num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the enclosures.rack_num and enclosures.dencl_num fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate. </UL>Note that the content of the enclosures.rack_num field will not be valid until a future release.
|
|
.1.3.6.1.4.1.232.0.13603331 |
Severity: Warning -- not failed but attention recommended or required. A physical disk drive was removed while software-activated drive locking was enabled on a drive enclosure that does not support drive locking. The handle field contains the WWN of the drive enclosure containing the Drive Enclosure Environmental Monitoring Unit. This problem was detected by the Drive Enclosure Environmental Monitoring Unit located in the drive enclosure determined by the content of the dencl_num field as follows: <UL><LI>If dencl_num is less than 99, the location is as indicated by the content of the rack_num and dencl_num fields. <LI>If dencl_num is equal to 99, the location is unknown. Note that the content of the rack_num field is undefined in this case. <LI>If dencl_num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the rack_num and dencl_num fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate. </UL>Note that the content of 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. The enclosures array shows the drive enclosures available on the Fibre Channel loop pair (0 = Loop A, 1 = Loop B) identified in the loop field. The location of an available drive enclosure is determined by the content of the enclosures.dencl_num field as follows: <UL><LI>If enclosures.dencl_num is less than 99, the location is as indicated by the content of the enclosures.rack_num and enclosures.dencl_num fields. <LI>If enclosures.dencl_num is equal to 99, the enclosures array entry is not used. Note that the content of the enclosures.rack_num field is undefined in this case. <LI>If enclosures.dencl_num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the enclosures.rack_num and enclosures.dencl_num fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate. </UL>Note that the content of the enclosures.rack_num field will not be valid until a future release.
|
|
.1.3.6.1.4.1.232.0.13603332 |
Severity: Critical -- failure or failure imminent. A physical disk drive that is 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. The handle field contains the WWN of the drive enclosure containing the Drive Enclosure Environmental Monitoring Unit. This problem was detected by the Drive Enclosure Environmental Monitoring Unit located in the drive enclosure determined by the content of the dencl_num field as follows: <UL><LI>If dencl_num is less than 99, the location is as indicated by the content of the rack_num and dencl_num fields. <LI>If dencl_num is equal to 99, the location is unknown. Note that the content of the rack_num field is undefined in this case. <LI>If dencl_num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the rack_num and dencl_num fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate. </UL>Note that the content of 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: <UL><LI>4 = loop A <LI>5 = loop B </UL><P> The enclosures array shows the drive enclosures available on the Fibre Channel loop pair (0 = Loop A, 1 = Loop B) identified in the loop field. The location of an available drive enclosure is determined by the content of the enclosures.dencl_num field as follows: <UL><LI>If enclosures.dencl_num is less than 99, the location is as indicated by the content of the enclosures.rack_num and enclosures.dencl_num fields. <LI>If enclosures.dencl_num is equal to 99, the enclosures array entry is not used. Note that the content of the enclosures.rack_num field is undefined in this case. <LI>If enclosures.dencl_num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the enclosures.rack_num and enclosures.dencl_num fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate. </UL>Note that the content of the enclosures.rack_num field will not be valid until a future release.
|
|
.1.3.6.1.4.1.232.0.13603379 |
Severity: Warning -- not failed but attention recommended or required. The AC input to a drive enclosure power supply has been lost. This makes the remaining power supply a single point of failure. The handle field contains the WWN of the drive enclosure containing the Drive Enclosure Environmental Monitoring Unit. This problem was detected by the Drive Enclosure Environmental Monitoring Unit located in the drive enclosure determined by the content of the dencl_num field as follows: <UL><LI>If dencl_num is less than 99, the location is as indicated by the content of the rack_num and dencl_num fields. <LI>If dencl_num is equal to 99, the location is unknown. Note that the content of the rack_num field is undefined in this case. <LI>If dencl_num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the rack_num and dencl_num fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate. </UL>Note that the content of 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. The enclosures array shows the drive enclosures available on the Fibre Channel loop pair (0 = Loop A, 1 = Loop B) identified in the loop field. The location of an available drive enclosure is determined by the content of the enclosures.dencl_num field as follows: <UL><LI>If enclosures.dencl_num is less than 99, the location is as indicated by the content of the enclosures.rack_num and enclosures.dencl_num fields. <LI>If enclosures.dencl_num is equal to 99, the enclosures array entry is not used. Note that the content of the enclosures.rack_num field is undefined in this case. <LI>If enclosures.dencl_num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the enclosures.rack_num and enclosures.dencl_num fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate. </UL>Note that the content of the enclosures.rack_num field will not be valid until a future release.
|
|
.1.3.6.1.4.1.232.0.13603380 |
Severity: Critical -- failure or failure imminent. A drive enclosure power supply is 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. The handle field contains the WWN of the drive enclosure containing the Drive Enclosure Environmental Monitoring Unit. This problem was detected by the Drive Enclosure Environmental Monitoring Unit located in the drive enclosure determined by the content of the dencl_num field as follows: <UL><LI>If dencl_num is less than 99, the location is as indicated by the content of the rack_num and dencl_num fields. <LI>If dencl_num is equal to 99, the location is unknown. Note that the content of the rack_num field is undefined in this case. <LI>If dencl_num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the rack_num and dencl_num fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate. </UL>Note that the content of 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. The enclosures array shows the drive enclosures available on the Fibre Channel loop pair (0 = Loop A, 1 = Loop B) identified in the loop field. The location of an available drive enclosure is determined by the content of the enclosures.dencl_num field as follows: <UL><LI>If enclosures.dencl_num is less than 99, the location is as indicated by the content of the enclosures.rack_num and enclosures.dencl_num fields. <LI>If enclosures.dencl_num is equal to 99, the enclosures array entry is not used. Note that the content of the enclosures.rack_num field is undefined in this case. <LI>If enclosures.dencl_num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the enclosures.rack_num and enclosures.dencl_num fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate. </UL>Note that the content of the enclosures.rack_num field will not be valid until a future release.
|
|
.1.3.6.1.4.1.232.0.13603381 |
Severity: Critical -- failure or failure imminent. A drive enclosure power supply component has failed. The handle field contains the WWN of the drive enclosure containing the Drive Enclosure Environmental Monitoring Unit. This problem was detected by the Drive Enclosure Environmental Monitoring Unit located in the drive enclosure determined by the content of the dencl_num field as follows: <UL><LI>If dencl_num is less than 99, the location is as indicated by the content of the rack_num and dencl_num fields. <LI>If dencl_num is equal to 99, the location is unknown. Note that the content of the rack_num field is undefined in this case. <LI>If dencl_num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the rack_num and dencl_num fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate. </UL>Note that the content of 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. The enclosures array shows the drive enclosures available on the Fibre Channel loop pair (0 = Loop A, 1 = Loop B) identified in the loop field. The location of an available drive enclosure is determined by the content of the enclosures.dencl_num field as follows: <UL><LI>If enclosures.dencl_num is less than 99, the location is as indicated by the content of the enclosures.rack_num and enclosures.dencl_num fields. <LI>If enclosures.dencl_num is equal to 99, the enclosures array entry is not used. Note that the content of the enclosures.rack_num field is undefined in this case. <LI>If enclosures.dencl_num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the enclosures.rack_num and enclosures.dencl_num fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate. </UL>Note that the content of the enclosures.rack_num field will not be valid until a future release.
|
|
.1.3.6.1.4.1.232.0.13603399 |
Severity: Critical -- failure or failure imminent. A drive enclosure blower is not operating properly. This could affect the drive enclosure air flow and cause an over temperature condition. The handle field contains the WWN of the drive enclosure containing the Drive Enclosure Environmental Monitoring Unit. This problem was detected by the Drive Enclosure Environmental Monitoring Unit located in the drive enclosure determined by the content of the dencl_num field as follows: <UL><LI>If dencl_num is less than 99, the location is as indicated by the content of the rack_num and dencl_num fields. <LI>If dencl_num is equal to 99, the location is unknown. Note that the content of the rack_num field is undefined in this case. <LI>If dencl_num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the rack_num and dencl_num fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate. </UL>Note that the content of 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: <UL><LI>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. <LI>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. <LI>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. Hewlett-Packard therefore recommends immediate replacement of the defective blower. <LI>4 = The power supply reported an internal blower error. </UL><P> The enclosures array shows the drive enclosures available on the Fibre Channel loop pair (0 = Loop A, 1 = Loop B) identified in the loop field. The location of an available drive enclosure is determined by the content of the enclosures.dencl_num field as follows: <UL><LI>If enclosures.dencl_num is less than 99, the location is as indicated by the content of the enclosures.rack_num and enclosures.dencl_num fields. <LI>If enclosures.dencl_num is equal to 99, the enclosures array entry is not used. Note that the content of the enclosures.rack_num field is undefined in this case. <LI>If enclosures.dencl_num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the enclosures.rack_num and enclosures.dencl_num fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate. </UL>Note that the content of the enclosures.rack_num field will not be valid until a future release.
|
|
.1.3.6.1.4.1.232.0.13603403 |
Severity: Critical -- failure or failure imminent. A drive enclosure blower is improperly installed or missing. This affects the drive enclosure air flow and can cause an over temperature condition. The handle field contains the WWN of the drive enclosure containing the Drive Enclosure Environmental Monitoring Unit. This problem was detected by the Drive Enclosure Environmental Monitoring Unit located in the drive enclosure determined by the content of the dencl_num field as follows: <UL><LI>If dencl_num is less than 99, the location is as indicated by the content of the rack_num and dencl_num fields. <LI>If dencl_num is equal to 99, the location is unknown. Note that the content of the rack_num field is undefined in this case. <LI>If dencl_num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the rack_num and dencl_num fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate. </UL>Note that the content of 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 enclosures array shows the drive enclosures available on the Fibre Channel loop pair (0 = Loop A, 1 = Loop B) identified in the loop field. The location of an available drive enclosure is determined by the content of the enclosures.dencl_num field as follows: <UL><LI>If enclosures.dencl_num is less than 99, the location is as indicated by the content of the enclosures.rack_num and enclosures.dencl_num fields. <LI>If enclosures.dencl_num is equal to 99, the enclosures array entry is not used. Note that the content of the enclosures.rack_num field is undefined in this case. <LI>If enclosures.dencl_num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the enclosures.rack_num and enclosures.dencl_num fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate. </UL>Note that the content of the enclosures.rack_num field will not be valid until a future release.
|
|
.1.3.6.1.4.1.232.0.13603404 |
Severity: Critical -- failure or failure imminent. Both drive enclosure blowers are 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. The handle field contains the WWN of the drive enclosure containing the Drive Enclosure Environmental Monitoring Unit. This problem was detected by the Drive Enclosure Environmental Monitoring Unit located in the drive enclosure determined by the content of the dencl_num field as follows: <UL><LI>If dencl_num is less than 99, the location is as indicated by the content of the rack_num and dencl_num fields. <LI>If dencl_num is equal to 99, the location is unknown. Note that the content of the rack_num field is undefined in this case. <LI>If dencl_num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the rack_num and dencl_num fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate. </UL>Note that the content of 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. The enclosures array shows the drive enclosures available on the Fibre Channel loop pair (0 = Loop A, 1 = Loop B) identified in the loop field. The location of an available drive enclosure is determined by the content of the enclosures.dencl_num field as follows: <UL><LI>If enclosures.dencl_num is less than 99, the location is as indicated by the content of the enclosures.rack_num and enclosures.dencl_num fields. <LI>If enclosures.dencl_num is equal to 99, the enclosures array entry is not used. Note that the content of the enclosures.rack_num field is undefined in this case. <LI>If enclosures.dencl_num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the enclosures.rack_num and enclosures.dencl_num fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate. </UL>Note that the content of the enclosures.rack_num field will not be valid until a future release.
|
|
.1.3.6.1.4.1.232.0.13603419 |
Severity: Warning -- not failed but attention recommended or required. A drive enclosure temperature sensor out of range condition has been reported by one of the drive enclosure elements. The handle field contains the WWN of the drive enclosure containing the Drive Enclosure Environmental Monitoring Unit. This problem was detected by the Drive Enclosure Environmental Monitoring Unit located in the drive enclosure determined by the content of the dencl_num field as follows: <UL><LI>If dencl_num is less than 99, the location is as indicated by the content of the rack_num and dencl_num fields. <LI>If dencl_num is equal to 99, the location is unknown. Note that the content of the rack_num field is undefined in this case. <LI>If dencl_num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the rack_num and dencl_num fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate. </UL>Note that the content of 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: <UL><LI>1 = Power Supply 1 Exhaust <LI>2 = Power Supply 2 Exhaust <LI>3 = Drive Enclosure Environmental Monitoring Unit <LI>4 = Drive Bay 1 <LI>5 = Drive Bay 2 <LI>6 = Drive Bay 3 <LI>7 = Drive Bay 4 <LI>8 = Drive Bay 5 <LI>9 = Drive Bay 6 <LI>A = Drive Bay 7 <LI>B = Drive Bay 8 <LI>C = Drive Bay 9 <LI>D = Drive Bay 10 <LI>E = Drive Bay 11 <LI>F = Drive Bay 12 <LI>10 = Drive Bay 13 <LI>11 = Drive Bay 14 </UL><P> The temperature sensor out of range condition is described by the content of the alarm_error_code.field.ec field as follows: <UL><LI>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. <LI>2 = The element temperature is above the high temperature CRITICAL threshold. Continued operation under these conditions may result in element failure. <LI>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. <LI>4 = The element temperature has reached the low temperature CRITICAL threshold. Continued operation under these conditions may result in element failure. </UL><P> The actual temperature threshold values can be found in the HSV element manager GUI. The enclosures array shows the drive enclosures available on the Fibre Channel loop pair (0 = Loop A, 1 = Loop B) identified in the loop field. The location of an available drive enclosure is determined by the content of the enclosures.dencl_num field as follows: <UL><LI>If enclosures.dencl_num is less than 99, the location is as indicated by the content of the enclosures.rack_num and enclosures.dencl_num fields. <LI>If enclosures.dencl_num is equal to 99, the enclosures array entry is not used. Note that the content of the enclosures.rack_num field is undefined in this case. <LI>If enclosures.dencl_num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the enclosures.rack_num and enclosures.dencl_num fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate. </UL>Note that the content of the enclosures.rack_num field will not be valid until a future release.
|
|
.1.3.6.1.4.1.232.0.13603423 |
Severity: Critical -- failure or failure imminent. The average temperature of two 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. The handle field contains the WWN of the drive enclosure containing the Drive Enclosure Environmental Monitoring Unit. This problem was detected by the Drive Enclosure Environmental Monitoring Unit located in the drive enclosure determined by the content of the dencl_num field as follows: <UL><LI>If dencl_num is less than 99, the location is as indicated by the content of the rack_num and dencl_num fields. <LI>If dencl_num is equal to 99, the location is unknown. Note that the content of the rack_num field is undefined in this case. <LI>If dencl_num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the rack_num and dencl_num fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate. </UL>Note that the content of 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. <P> The actual temperature threshold values can be found in the HSV element manager GUI. The enclosures array shows the drive enclosures available on the Fibre Channel loop pair (0 = Loop A, 1 = Loop B) identified in the loop field. The location of an available drive enclosure is determined by the content of the enclosures.dencl_num field as follows: <UL><LI>If enclosures.dencl_num is less than 99, the location is as indicated by the content of the enclosures.rack_num and enclosures.dencl_num fields. <LI>If enclosures.dencl_num is equal to 99, the enclosures array entry is not used. Note that the content of the enclosures.rack_num field is undefined in this case. <LI>If enclosures.dencl_num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the enclosures.rack_num and enclosures.dencl_num fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate. </UL>Note that the content of the enclosures.rack_num field will not be valid until a future release.
|
|
.1.3.6.1.4.1.232.0.13603439 |
Severity: Warning -- not failed but attention recommended or required. An internal Drive Enclosure Environmental Monitoring Unit error has occurred. The handle field contains the WWN of the drive enclosure containing the Drive Enclosure Environmental Monitoring Unit. This problem was detected by the Drive Enclosure Environmental Monitoring Unit located in the drive enclosure determined by the content of the dencl_num field as follows: <UL><LI>If dencl_num is less than 99, the location is as indicated by the content of the rack_num and dencl_num fields. <LI>If dencl_num is equal to 99, the location is unknown. Note that the content of the rack_num field is undefined in this case. <LI>If dencl_num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the rack_num and dencl_num fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate. </UL>Note that the content of 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: <UL><LI>1 = An internal Drive Enclosure Environmental Monitoring Unit clock error has occurred. <LI>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. <LI>5 = A Backplane NVRAM error has occurred. </UL><P> The enclosures array shows the drive enclosures available on the Fibre Channel loop pair (0 = Loop A, 1 = Loop B) identified in the loop field. The location of an available drive enclosure is determined by the content of the enclosures.dencl_num field as follows: <UL><LI>If enclosures.dencl_num is less than 99, the location is as indicated by the content of the enclosures.rack_num and enclosures.dencl_num fields. <LI>If enclosures.dencl_num is equal to 99, the enclosures array entry is not used. Note that the content of the enclosures.rack_num field is undefined in this case. <LI>If enclosures.dencl_num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the enclosures.rack_num and enclosures.dencl_num fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate. </UL>Note that the content of the enclosures.rack_num field will not be valid until a future release.
|
|
.1.3.6.1.4.1.232.0.13603441 |
Severity: Normal -- informational in nature. An internal Drive Enclosure Environmental Monitoring Unit error has occurred. The handle field contains the WWN of the drive enclosure containing the Drive Enclosure Environmental Monitoring Unit. This problem was detected by the Drive Enclosure Environmental Monitoring Unit located in the drive enclosure determined by the content of the dencl_num field as follows: <UL><LI>If dencl_num is less than 99, the location is as indicated by the content of the rack_num and dencl_num fields. <LI>If dencl_num is equal to 99, the location is unknown. Note that the content of the rack_num field is undefined in this case. <LI>If dencl_num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the rack_num and dencl_num fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate. </UL>Note that the content of 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: <UL><LI>3 = A drive enclosure power supply was shut down. <LI>16 = The Drive Enclosure Environmental Monitoring Unit ESI data has been corrupted. </UL><P> The enclosures array shows the drive enclosures available on the Fibre Channel loop pair (0 = Loop A, 1 = Loop B) identified in the loop field. The location of an available drive enclosure is determined by the content of the enclosures.dencl_num field as follows: <UL><LI>If enclosures.dencl_num is less than 99, the location is as indicated by the content of the enclosures.rack_num and enclosures.dencl_num fields. <LI>If enclosures.dencl_num is equal to 99, the enclosures array entry is not used. Note that the content of the enclosures.rack_num field is undefined in this case. <LI>If enclosures.dencl_num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the enclosures.rack_num and enclosures.dencl_num fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate. </UL>Note that the content of the enclosures.rack_num field will not be valid until a future release.
|
|
.1.3.6.1.4.1.232.0.13603442 |
Severity: Warning -- not failed but attention recommended or required. A Drive Enclosure Environmental Monitoring Unit is unable to collect data for the SCSI-3 Enclosure Services (SES) page. The handle field contains the WWN of the drive enclosure containing the Drive Enclosure Environmental Monitoring Unit. This problem was detected by the Drive Enclosure Environmental Monitoring Unit located in the drive enclosure determined by the content of the dencl_num field as follows: <UL><LI>If dencl_num is less than 99, the location is as indicated by the content of the rack_num and dencl_num fields. <LI>If dencl_num is equal to 99, the location is unknown. Note that the content of the rack_num field is undefined in this case. <LI>If dencl_num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the rack_num and dencl_num fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate. </UL>Note that the content of 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 enclosures array shows the drive enclosures available on the Fibre Channel loop pair (0 = Loop A, 1 = Loop B) identified in the loop field. The location of an available drive enclosure is determined by the content of the enclosures.dencl_num field as follows: <UL><LI>If enclosures.dencl_num is less than 99, the location is as indicated by the content of the enclosures.rack_num and enclosures.dencl_num fields. <LI>If enclosures.dencl_num is equal to 99, the enclosures array entry is not used. Note that the content of the enclosures.rack_num field is undefined in this case. <LI>If enclosures.dencl_num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the enclosures.rack_num and enclosures.dencl_num fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate. </UL>Note that the content of the enclosures.rack_num field will not be valid until a future release.
|
|
.1.3.6.1.4.1.232.0.13603454 |
Severity: Warning -- not failed but attention recommended or required. Invalid data was read from a Drive Enclosure Environmental Monitoring Unit NVRAM. The handle field contains the WWN of the drive enclosure containing the Drive Enclosure Environmental Monitoring Unit. This problem was detected by the Drive Enclosure Environmental Monitoring Unit located in the drive enclosure determined by the content of the dencl_num field as follows: <UL><LI>If dencl_num is less than 99, the location is as indicated by the content of the rack_num and dencl_num fields. <LI>If dencl_num is equal to 99, the location is unknown. Note that the content of the rack_num field is undefined in this case. <LI>If dencl_num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the rack_num and dencl_num fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate. </UL>Note that the content of 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 enclosures array shows the drive enclosures available on the Fibre Channel loop pair (0 = Loop A, 1 = Loop B) identified in the loop field. The location of an available drive enclosure is determined by the content of the enclosures.dencl_num field as follows: <UL><LI>If enclosures.dencl_num is less than 99, the location is as indicated by the content of the enclosures.rack_num and enclosures.dencl_num fields. <LI>If enclosures.dencl_num is equal to 99, the enclosures array entry is not used. Note that the content of the enclosures.rack_num field is undefined in this case. <LI>If enclosures.dencl_num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the enclosures.rack_num and enclosures.dencl_num fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate. </UL>Note that the content of the enclosures.rack_num field will not be valid until a future release.
|
|
.1.3.6.1.4.1.232.0.13603455 |
Severity: Warning -- not failed but attention recommended or required. An internal Drive Enclosure Environmental Monitoring Unit error has occurred. The handle field contains the WWN of the drive enclosure containing the Drive Enclosure Environmental Monitoring Unit. This problem was detected by the Drive Enclosure Environmental Monitoring Unit located in the drive enclosure determined by the content of the dencl_num field as follows: <UL><LI>If dencl_num is less than 99, the location is as indicated by the content of the rack_num and dencl_num fields. <LI>If dencl_num is equal to 99, the location is unknown. Note that the content of the rack_num field is undefined in this case. <LI>If dencl_num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the rack_num and dencl_num fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate. </UL>Note that the content of 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: <UL><LI>11 = The Drive Enclosure Environmental Monitoring Unit cannot write data to the NVRAM. <LI>12 = The Drive Enclosure Environmental Monitoring Unit cannot read data from the NVRAM. <LI>13 = The Field Programmable Gate Array (FPGA) that controls the ESI bus failed to load information required for Drive Enclosure Environmental Monitoring Unit operation. </UL><P> The enclosures array shows the drive enclosures available on the Fibre Channel loop pair (0 = Loop A, 1 = Loop B) identified in the loop field. The location of an available drive enclosure is determined by the content of the enclosures.dencl_num field as follows: <UL><LI>If enclosures.dencl_num is less than 99, the location is as indicated by the content of the enclosures.rack_num and enclosures.dencl_num fields. <LI>If enclosures.dencl_num is equal to 99, the enclosures array entry is not used. Note that the content of the enclosures.rack_num field is undefined in this case. <LI>If enclosures.dencl_num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the enclosures.rack_num and enclosures.dencl_num fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate. </UL>Note that the content of the enclosures.rack_num field will not be valid until a future release.
|
|
.1.3.6.1.4.1.232.0.13603458 |
Severity: Warning -- not failed but attention recommended or required. A drive enclosure's address is incorrect or the enclosure has no address. The handle field contains the WWN of the drive enclosure containing the Drive Enclosure Environmental Monitoring Unit. This problem was detected by the Drive Enclosure Environmental Monitoring Unit located in the drive enclosure determined by the content of the dencl_num field as follows: <UL><LI>If dencl_num is less than 99, the location is as indicated by the content of the rack_num and dencl_num fields. <LI>If dencl_num is equal to 99, the location is unknown. Note that the content of the rack_num field is undefined in this case. <LI>If dencl_num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the rack_num and dencl_num fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate. </UL>Note that the content of 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 enclosures array shows the drive enclosures available on the Fibre Channel loop pair (0 = Loop A, 1 = Loop B) identified in the loop field. The location of an available drive enclosure is determined by the content of the enclosures.dencl_num field as follows: <UL><LI>If enclosures.dencl_num is less than 99, the location is as indicated by the content of the enclosures.rack_num and enclosures.dencl_num fields. <LI>If enclosures.dencl_num is equal to 99, the enclosures array entry is not used. Note that the content of the enclosures.rack_num field is undefined in this case. <LI>If enclosures.dencl_num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the enclosures.rack_num and enclosures.dencl_num fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate. </UL>Note that the content of the enclosures.rack_num field will not be valid until a future release.
|
|
.1.3.6.1.4.1.232.0.13603459 |
Severity: Critical -- failure or failure imminent. A Drive Enclosure Environmental Monitoring Unit has experienced a hardware failure. The handle field contains the WWN of the drive enclosure containing the Drive Enclosure Environmental Monitoring Unit. This problem was detected by the Drive Enclosure Environmental Monitoring Unit located in the drive enclosure determined by the content of the dencl_num field as follows: <UL><LI>If dencl_num is less than 99, the location is as indicated by the content of the rack_num and dencl_num fields. <LI>If dencl_num is equal to 99, the location is unknown. Note that the content of the rack_num field is undefined in this case. <LI>If dencl_num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the rack_num and dencl_num fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate. </UL>Note that the content of 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 enclosures array shows the drive enclosures available on the Fibre Channel loop pair (0 = Loop A, 1 = Loop B) identified in the loop field. The The location of an available drive enclosure is determined by the content of the enclosures.dencl_num field as follows: <UL><LI>If enclosures.dencl_num is less than 99, the location is as indicated by the content of the enclosures.rack_num and enclosures.dencl_num fields. <LI>If enclosures.dencl_num is equal to 99, the enclosures array entry is not used. Note that the content of the enclosures.rack_num field is undefined in this case. <LI>If enclosures.dencl_num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the enclosures.rack_num and enclosures.dencl_num fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate. </UL>Note that the content of the enclosures.rack_num field will not be valid until a future release. The cause of the improper operation is described by the content of the alarm_error_code.field.ec field as follows: <UL><LI>15 = Drive Enclosure Environmental Monitoring Unit hardware failure DP. <LI>18 = Drive Enclosure Environmental Monitoring Unit hardware failed BT. <LI>19 = Drive Enclosure Environmental Monitoring Unit ESI driver failure. </UL>
|
|
.1.3.6.1.4.1.232.0.13603461 |
Severity: Warning -- not failed but attention recommended or required. A drive enclosure power supply failed to respond to a shut down command. The handle field contains the WWN of the drive enclosure containing the Drive Enclosure Environmental Monitoring Unit. This problem was detected by the Drive Enclosure Environmental Monitoring Unit located in the drive enclosure determined by the content of the dencl_num field as follows: <UL><LI>If dencl_num is less than 99, the location is as indicated by the content of the rack_num and dencl_num fields. <LI>If dencl_num is equal to 99, the location is unknown. Note that the content of the rack_num field is undefined in this case. <LI>If dencl_num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the rack_num and dencl_num fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate. </UL>Note that the content of 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 enclosures array shows the drive enclosures available on the Fibre Channel loop pair (0 = Loop A, 1 = Loop B) identified in the loop field. The location of an available drive enclosure is determined by the content of the enclosures.dencl_num field as follows: <UL><LI>If enclosures.dencl_num is less than 99, the location is as indicated by the content of the enclosures.rack_num and enclosures.dencl_num fields. <LI>If enclosures.dencl_num is equal to 99, the enclosures array entry is not used. Note that the content of the enclosures.rack_num field is undefined in this case. <LI>If enclosures.dencl_num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the enclosures.rack_num and enclosures.dencl_num fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate. </UL>Note that the content of the enclosures.rack_num field will not be valid until a future release.
|
|
.1.3.6.1.4.1.232.0.13603469 |
Severity: Critical -- failure or failure imminent. A drive enclosure transceiver error has been detected. The handle field contains the WWN of the drive enclosure containing the Drive Enclosure Environmental Monitoring Unit. This problem was detected by the Drive Enclosure Environmental Monitoring Unit located in the drive enclosure determined by the content of the dencl_num field as follows: <UL><LI>If dencl_num is less than 99, the location is as indicated by the content of the rack_num and dencl_num fields. <LI>If dencl_num is equal to 99, the location is unknown. Note that the content of the rack_num field is undefined in this case. <LI>If dencl_num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the rack_num and dencl_num fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate. </UL>Note that the content of 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: <UL><LI>1 = Transceiver 01 <LI>2 = Transceiver 02 <LI>3 = Transceiver 03 <LI>4 = Transceiver 04 </UL><P> The transceiver error condition is described by the content of the alarm_error_code.field.ec field as follows: <UL><LI>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. <LI>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. <LI>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. <LI>4 = The transceiver that was previously in this location has been removed. <LI>5 = The transceiver in the specified location has detected invalid Fibre Channel characters. </UL><P> The enclosures array shows the drive enclosures available on the Fibre Channel loop pair (0 = Loop A, 1 = Loop B) identified in the loop field. The location of an available drive enclosure is determined by the content of the enclosures.dencl_num field as follows: <UL><LI>If enclosures.dencl_num is less than 99, the location is as indicated by the content of the enclosures.rack_num and enclosures.dencl_num fields. <LI>If enclosures.dencl_num is equal to 99, the enclosures array entry is not used. Note that the content of the enclosures.rack_num field is undefined in this case. <LI>If enclosures.dencl_num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the enclosures.rack_num and enclosures.dencl_num fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate. </UL>Note that the content of the enclosures.rack_num field will not be valid until a future release.
|
|
.1.3.6.1.4.1.232.0.13603489 |
Severity: Critical -- failure or failure imminent. A drive enclosure power supply voltage sensor out of range condition has been reported. The handle field contains the WWN of the drive enclosure containing the Drive Enclosure Environmental Monitoring Unit. This problem was detected by the Drive Enclosure Environmental Monitoring Unit located in the drive enclosure determined by the content of the dencl_num field as follows: <UL><LI>If dencl_num is less than 99, the location is as indicated by the content of the rack_num and dencl_num fields. <LI>If dencl_num is equal to 99, the location is unknown. Note that the content of the rack_num field is undefined in this case. <LI>If dencl_num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the rack_num and dencl_num fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate. </UL>Note that the content of 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: <UL><LI>1 = Power Supply 1 +5 VDC <LI>2 = Power Supply 1 +12 VDC <LI>3 = Power Supply 2 +5 VDC <LI>4 = Power Supply 2 +12 VDC </UL><P> The voltage sensor out of range condition is described by the content of the alarm_error_code.field.ec field as follows: <UL><LI>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. <LI>2 = The element voltage is above the high voltage CRITICAL threshold. <LI>3 = The element voltage is approaching, but has not reached, the low voltage CRITICAL threshold. Continued operation under these conditions may result in a CRITICAL condition. <LI>4 = The element voltage has reached the low voltage CRITICAL threshold. </UL><P> The enclosures array shows the drive enclosures available on the Fibre Channel loop pair (0 = Loop A, 1 = Loop B) identified in the loop field. The location of an available drive enclosure is determined by the content of the enclosures.dencl_num field as follows: <UL><LI>If enclosures.dencl_num is less than 99, the location is as indicated by the content of the enclosures.rack_num and enclosures.dencl_num fields. <LI>If enclosures.dencl_num is equal to 99, the enclosures array entry is not used. Note that the content of the enclosures.rack_num field is undefined in this case. <LI>If enclosures.dencl_num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the enclosures.rack_num and enclosures.dencl_num fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate. </UL>Note that the content of the enclosures.rack_num field will not be valid until a future release.
|
|
.1.3.6.1.4.1.232.0.13603509 |
Severity: Critical -- failure or failure imminent. A drive enclosure power supply current sensor out of range condition has been reported. The handle field contains the WWN of the drive enclosure containing the Drive Enclosure Environmental Monitoring Unit. This problem was detected by the Drive Enclosure Environmental Monitoring Unit located in the drive enclosure determined by the content of the dencl_num field as follows: <UL><LI>If dencl_num is less than 99, the location is as indicated by the content of the rack_num and dencl_num fields. <LI>If dencl_num is equal to 99, the location is unknown. Note that the content of the rack_num field is undefined in this case. <LI>If dencl_num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the rack_num and dencl_num fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate. </UL>Note that the content of 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: <UL><LI>1 = Power Supply 1 +5 VDC <LI>2 = Power Supply 1 +12 VDC <LI>3 = Power Supply 2 +5 VDC <LI>4 = Power Supply 2 +12 VDC </UL><P> The current sensor out of range condition is described by the content of the alarm_error_code.field.ec field as follows: <UL><LI>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. <LI>2 = The element current is above the high current CRITICAL threshold. </UL><P> The enclosures array shows the drive enclosures available on the Fibre Channel loop pair (0 = Loop A, 1 = Loop B) identified in the loop field. The location of an available drive enclosure is determined by the content of the enclosures.dencl_num field as follows: <UL><LI>If enclosures.dencl_num is less than 99, the location is as indicated by the content of the enclosures.rack_num and enclosures.dencl_num fields. <LI>If enclosures.dencl_num is equal to 99, the enclosures array entry is not used. Note that the content of the enclosures.rack_num field is undefined in this case. <LI>If enclosures.dencl_num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the enclosures.rack_num and enclosures.dencl_num fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate. </UL>Note that the content of the enclosures.rack_num field will not be valid until a future release.
|
|
.1.3.6.1.4.1.232.0.13603544 |
Severity: Warning -- not failed but attention recommended or required. A drive enclosure backplane invalid NVRAM read error has occurred. The handle field contains the WWN of the drive enclosure containing the Drive Enclosure Environmental Monitoring Unit.This problem was detected by the Drive Enclosure Environmental Monitoring Unit located in the drive enclosure determined by the content of the dencl_num field as follows: <UL><LI>If dencl_num is less than 99, the location is as indicated by the content of the rack_num and dencl_num fields. <LI>If dencl_num is equal to 99, the location is unknown. Note that the content of the rack_num field is undefined in this case. <LI>If dencl_num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the rack_num and dencl_num fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate. </UL>Note that the content of 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 enclosures array shows the drive enclosures available on the Fibre Channel loop pair (0 = Loop A, 1 = Loop B) identified in the loop field. The The location of an available drive enclosure is determined by the content of the enclosures.dencl_num field as follows: <UL><LI>If enclosures.dencl_num is less than 99, the location is as indicated by the content of the enclosures.rack_num and enclosures.dencl_num fields. <LI>If enclosures.dencl_num is equal to 99, the enclosures array entry is not used. Note that the content of the enclosures.rack_num field is undefined in this case. <LI>If enclosures.dencl_num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the enclosures.rack_num and enclosures.dencl_num fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate. </UL>Note that the content of the enclosures.rack_num field will not be valid until a future release.
|
|
.1.3.6.1.4.1.232.0.13603545 |
Severity: Critical -- failure or failure imminent. A drive enclosure backplane error has occurred. The handle field contains the WWN of the drive enclosure containing the Drive Enclosure Environmental Monitoring Unit. This problem was detected by the Drive Enclosure Environmental Monitoring Unit located in the drive enclosure determined by the content of the dencl_num field as follows: <UL><LI>If dencl_num is less than 99, the location is as indicated by the content of the rack_num and dencl_num fields. <LI>If dencl_num is equal to 99, the location is unknown. Note that the content of the rack_num field is undefined in this case. <LI>If dencl_num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the rack_num and dencl_num fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate. </UL>Note that the content of 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: <UL><LI>11 = Unable to write data to the NVRAM. This problem prevents communication between elements in the enclosure. <LI>12 = Unable to read data from the NVRAM. This problem prevents communication between elements in the enclosure. <LI>13 = NVRAM has not been initialized properly. This is a manufacturing error. </UL><P> The enclosures array shows the drive enclosures available on the Fibre Channel loop pair (0 = Loop A, 1 = Loop B) identified in the loop field. The location of an available drive enclosure is determined by the content of the enclosures.dencl_num field as follows: <UL><LI>If enclosures.dencl_num is less than 99, the location is as indicated by the content of the enclosures.rack_num and enclosures.dencl_num fields. <LI>If enclosures.dencl_num is equal to 99, the enclosures array entry is not used. Note that the content of the enclosures.rack_num field is undefined in this case. <LI>If enclosures.dencl_num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the enclosures.rack_num and enclosures.dencl_num fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate. </UL>Note that the content of the enclosures.rack_num field will not be valid until a future release.
|
|
.1.3.6.1.4.1.232.0.13603549 |
Severity: Critical -- failure or failure imminent. A drive enclosure I/O module error has occurred. The handle field contains the WWN of the drive enclosure containing the Drive Enclosure Environmental Monitoring Unit. This problem was detected by the Drive Enclosure Environmental Monitoring Unit located in the drive enclosure determined by the content of the dencl_num field as follows: <UL><LI>If dencl_num is less than 99, the location is as indicated by the content of the rack_num and dencl_num fields. <LI>If dencl_num is equal to 99, the location is unknown. Note that the content of the rack_num field is undefined in this case. <LI>If dencl_num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the rack_num and dencl_num fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate. </UL>Note that the content of 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: <UL><LI>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. <LI>11 = Unable to write data to the I/O module NVRAM. <LI>12 = Unable to read data from the I/O module NVRAM. <LI>13 = The I/O module that was in this location has been removed. </UL><P> The enclosures array shows the drive enclosures available on the Fibre Channel loop pair (0 = Loop A, 1 = Loop B) identified in the loop field. The location of an available drive enclosure is determined by the content of the enclosures.dencl_num field as follows: <UL><LI>If enclosures.dencl_num is less than 99, the location is as indicated by the content of the enclosures.rack_num and enclosures.dencl_num fields. <LI>If enclosures.dencl_num is equal to 99, the enclosures array entry is not used. Note that the content of the enclosures.rack_num field is undefined in this case. <LI>If enclosures.dencl_num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the enclosures.rack_num and enclosures.dencl_num fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate. </UL>Note that the content of the enclosures.rack_num field will not be valid until a future release.
|
|
.1.3.6.1.4.1.232.0.13603550 |
Severity: Warning -- not failed but attention recommended or required. A drive enclosure I/O module is unable to communicate with the Drive Enclosure Environmental Monitoring Unit. The handle field contains the WWN of the drive enclosure containing the Drive Enclosure Environmental Monitoring Unit. This problem was detected by the Drive Enclosure Environmental Monitoring Unit located in the drive enclosure determined by the content of the dencl_num field as follows: <UL><LI>If dencl_num is less than 99, the location is as indicated by the content of the rack_num and dencl_num fields. <LI>If dencl_num is equal to 99, the location is unknown. Note that the content of the rack_num field is undefined in this case. <LI>If dencl_num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the rack_num and dencl_num fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate. </UL>Note that the content of 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 enclosures array shows the drive enclosures available on the Fibre Channel loop pair (0 = Loop A, 1 = Loop B) identified in the loop field. The location of an available drive enclosure is determined by the content of the enclosures.dencl_num field as follows: <UL><LI>If enclosures.dencl_num is less than 99, the location is as indicated by the content of the enclosures.rack_num and enclosures.dencl_num fields. <LI>If enclosures.dencl_num is equal to 99, the enclosures array entry is not used. Note that the content of the enclosures.rack_num field is undefined in this case. <LI>If enclosures.dencl_num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the enclosures.rack_num and enclosures.dencl_num fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate. </UL>Note that the content of the enclosures.rack_num field will not be valid until a future release.
|
|
.1.3.6.1.4.1.232.0.13603564 |
Severity: Warning -- not failed but attention recommended or required. A drive enclosure I/O module invalid NVRAM read error has occurred. The handle field contains the WWN of the drive enclosure containing the Drive Enclosure Environmental Monitoring Unit.This problem was detected by the Drive Enclosure Environmental Monitoring Unit located in the drive enclosure determined by the content of the dencl_num field as follows: <UL><LI>If dencl_num is less than 99, the location is as indicated by the content of the rack_num and dencl_num fields. <LI>If dencl_num is equal to 99, the location is unknown. Note that the content of the rack_num field is undefined in this case. <LI>If dencl_num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the rack_num and dencl_num fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate. </UL>Note that the content of 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. The enclosures array shows the drive enclosures available on the Fibre Channel loop pair (0 = Loop A, 1 = Loop B) identified in the loop field. The location of an available drive enclosure is determined by the content of the enclosures.dencl_num field as follows: <UL><LI>If enclosures.dencl_num is less than 99, the location is as indicated by the content of the enclosures.rack_num and enclosures.dencl_num fields. <LI>If enclosures.dencl_num is equal to 99, the enclosures array entry is not used. Note that the content of the enclosures.rack_num field is undefined in this case. <LI>If enclosures.dencl_num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the enclosures.rack_num and enclosures.dencl_num fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate. </UL>Note that the content of the enclosures.rack_num field will not be valid until a future release.
|
|
.1.3.6.1.4.1.232.0.13603568 |
Severity: Normal -- informational in nature. The status has changed on one or more of the drive enclosures. This is an informational event triggered by the occurrence of a change in the status of a drive enclosure. This event is generated for the HSV element manager GUI and contains no user information. The content of the handle, alarm_error_code field, dencl_num, and rack_num fields have no meaning for this event. The enclosures array shows the drive enclosures available on the Fibre Channel loop pair (0 = Loop A, 1 = Loop B) identified in the loop field. The location of an available drive enclosure is determined by the content of the enclosures.dencl_num field as follows: <UL><LI>If enclosures.dencl_num is less than 99, the location is as indicated by the content of the enclosures.rack_num and enclosures.dencl_num fields. <LI>If enclosures.dencl_num is equal to 99, the enclosures array entry is not used. Note that the content of the enclosures.rack_num field is undefined in this case. <LI>If enclosures.dencl_num is greater than 99, the HSV110 controller does not have proof of the current location but the last known location is indicated by the content of the enclosures.rack_num and enclosures.dencl_num fields. Subtract 100 from the content of those fields to determine the actual last known location. If there have been no configuration changes, the last known location values will be accurate. </UL>Note that the content of the enclosures.rack_num field will not be valid until a future release.
|
|
.1.3.6.1.4.1.232.0.13616896 |
Severity: Normal -- informational in nature. Indicated Host Fibre Channel port transitioned to link down.
|
|
.1.3.6.1.4.1.232.0.13616897 |
Severity: Normal -- informational in nature. Indicated Host Fibre Channel port transitioned to link failed.
|
|
.1.3.6.1.4.1.232.0.13616899 |
Severity: Normal -- informational in nature. An excessive number of link 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 periodically.
|
|
.1.3.6.1.4.1.232.0.13616900 |
Severity: Warning -- not failed but attention recommended or required. A Fibre Channel port on the 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.
|
|
.1.3.6.1.4.1.232.0.13616901 |
Severity: Normal -- informational in nature. Indicated Host Fibre Channel port transitioned to link wedged.
|
|
.1.3.6.1.4.1.232.0.13633536 |
Severity: Critical -- failure or failure imminent. A failure was detected during the execution of this HSV110 controller's on board diagnostics.
|
|
.1.3.6.1.4.1.232.0.13633537 |
Severity: Warning -- not failed but attention recommended or required. A GBIC SFF Serial ID Data check code failure was detected during the execution of this HSV110 controller's on board diagnostics.
|
|
.1.3.6.1.4.1.232.0.13633538 |
Severity: Critical -- failure or failure imminent. A battery assembly failure was detected during the execution of this HSV110 controller's on board diagnostics.
|
|
.1.3.6.1.4.1.232.0.13633539 |
Severity: Critical -- failure or failure imminent. A battery assembly failure was detected during the execution of this HSV110 controller's on board diagnostics.
|
|
.1.3.6.1.4.1.232.0.13633540 |
Severity: Critical -- failure or failure imminent. A battery assembly communication failure was detected during the execution of this HSV110 controller's on board diagnostics.
|
|
.1.3.6.1.4.1.232.0.13633541 |
Severity: Critical -- failure or failure imminent. A battery assembly communication failure was detected during the execution of this HSV110 controller's on board diagnostics.
|
|
.1.3.6.1.4.1.232.0.13633542 |
Severity: Critical -- failure or failure imminent. A soft cache memory ECC error or indication of low battery voltage was detected during the execution of this HSV110 controller's on board diagnostics.
|
