IBM Storwize V7000 Troubleshooting And Maintenance Manual page 89

Table 19. Event IDs and codes (continued)
Notification
Event ID type
045046 W
045047 W
045048 W
045049 W
0450050 W
045051 E
045052 W
045053 E
045054 E
045055 E
045056 E
045057 E
045058 E
045062 W
045063 E
045064 W
045065 E
045066 E
4 4 4 4 045067 W
045068 E
045069 E
045070 W
045071 W
045072 E
045073 E
045080 E
050001 W
050002 W
050010 W
050020 W
050030 W
050031 W
060001 W
Condition
An enclosure is connected to more than one I/O group.
A managed enclosure is connected to the wrong I/O group.
An enclosure is connected to more than one chain.
Too many canisters are connected to a strand.
The canister is connected to the wrong port.
A SAS cable is excluded because of single port active drives.
More than one canister was detected at the same hop count.
The node location is not able to be detected.
An enclosure display cannot be updated.
There is an enclosure battery fault.
An enclosure battery is missing.
An enclosure battery is nearing end of life.
An enclosure battery is at end of life.
An enclosure battery conditioning is not required but possible.
There was an enclosure battery communications error.
A SAS port is active, but no enclosures can be detected.
There is a connectivity problem between a canister and an enclosure.
The FRU identity of the enclosure is not valid.
A new enclosure FRU was detected and needs to be configured.
The internal device on a node canister was excluded because of too many
change events.
The internal connector on the node canister was excluded as the cause of
single ported drives.
The canister temperature sensor cannot be read.
The enclosure contains both a node canister and an expansion canister.
The discovery failed to complete.
The VPD for the enclosure cannot be read.
There are too many self-initiated resets on the enclosure.
The relationship is stopped because of a cluster or complete I/O group
failure, and the current state of the mapping could not be recovered.
A Metro Mirror or Global Mirror relationship or consistency group exists
within a cluster, but its partnership has been deleted.
A Metro Mirror or Global Mirror relationship has stopped because of a
persistent I/O error.
A Metro Mirror or Global Mirror relationship has stopped because of an
error that is not a persistent I/O error.
There are too many cluster partnerships. The number of cluster
partnerships has been reduced.
There are too many cluster partnerships. The cluster has been excluded.
The thin-provisioned volume copy is offline because there is insufficient
space.
Error
code
1005
1005
1005
1005
1005
1260
1005
1031
1031
1118
1112
1114
1113
1131
1116
1005
1036
1008
1041
1034
1034
1034
1037
1048
1048
1048
1700
3080
1920
1720
1710
1710
1865
Chapter 7. Event reporting
73