IBM Storwize V7000 Troubleshooting And Maintenance Manual page 174

860 • 1188
860 Fibre Channel network fabric is too big.
Explanation: The number of Fibre Channel (FC) logins
made to the node canister exceeds the allowed limit.
The node canister continues to operate, but only
communicates with the logins made before the limit
was reached. The order in which other devices log into
the node canister cannot be determined, so the node
canister's FC connectivity might vary after each restart.
The connection might be with host systems, other
storage systems, or with other node canisters.
This error might be the reason the node canister is
unable to participate in a system.
The number of allowed logins per node is 1024.
Data:
v None
User response: This error indicates a problem with the
Fibre Channel fabric configuration. It is resolved by
reconfiguring the FC switch:
1. If possible, use the management GUI to run the
recommended actions for the associated service
error code.
2. Rezone the FC network so only the ports the node
canister needs to connect to are visible to it.
Possible Cause-FRUs or other cause:
v None
875 Request to cluster rejected.
Explanation: A candidate node canister could not be
added to the clustered system. The node canister
contains hardware or firmware that is not supported in
the clustered system.
Data:
This node error and extra data is viewable through
sainfo lsservicestatus on the candidate node only.
The extra data lists a full set of feature codes that are
required by the node canister to run in the clustered
system.
User response:
v Choose a different candidate that is compatible with
the clustered system.
v Upgrade the clustered system to code that is
supported by all components.
v Do not add a candidate to the clustered system.
v Where applicable, remove and replace the hardware
that is preventing the candidate from joining the
clustered system.
Possible Cause—FRUs or other cause:
For information on feature codes available, see the SAN
Volume Controller and Storwize family Characteristic
156
Storwize V7000: Troubleshooting, Recovery, and Maintenance Guide
Interoperability Matrix on the support website:
www.ibm.com/storage/support/storwize/v7000.
878 Attempting recovery after loss of state
data.
Explanation: During startup, the node canister cannot
read its state data. It reports this error while waiting to
be added back into a clustered system. If the node
canister is not added back into a clustered system
within a set time, node error 578 is reported.
User response:
1. Allow time for recovery. No further action is
required.
2. Keep monitoring in case the error changes to error
code 578.
920 Unable to perform cluster recovery
because of a lack of cluster resources.
Explanation: The node is looking for a quorum of
resources which also require cluster recovery.
User response: Contact IBM technical support.
950 Special upgrade mode.
Explanation: Special upgrade mode.
User response: None.
990 Cluster recovery has failed.
Explanation: Cluster recovery has failed.
User response: Contact IBM technical support.
1021 Incorrect enclosure
Explanation: The cluster is reporting that a node is
not operational because of critical node error 500. See
the details of node error 500 for more information.
User response: See node error 500.
1036 The enclosure identity cannot be read.
Explanation: The cluster is reporting that a node is
not operational because of critical node error 509. See
the details of node error 509 for more information.
User response: See node error 509.
1188 Too many software crashes have
occurred.
Explanation: The cluster is reporting that a node is
not operational because of critical node error 564. See
the details of node error 564 for more information.
User response: See node error 564.