IBM Storwize V7000 Troubleshooting And Maintenance Manual page 95

510 The detected memory size does not
match the expected memory size.
Explanation: The amount of memory detected in the
node canister is less than the expected memory. The
error code date shows the detected memory, in MB,
followed by the expected memory, in MB.
User response: Follow troubleshooting procedures to
fix the hardware:
1. Use the hardware remove and replace node canister
procedure to install a new node canister.
Possible Cause-FRUs or other:
v Node canister (100%)
523 The internal disk file system is
damaged.
Explanation: The node startup procedures have found
problems with the file system on the internal disk of
the node.
User response: Follow troubleshooting procedures to
reload the software.
1. Follow the procedures to rescue the software of a
node from another node.
2. If the rescue node does not succeed, use the
hardware remove and replace procedures.
Possible Cause-FRUs or other:
v Node canister (100%)
525 Unable to update system board service
processor firmware
Explanation: The node startup procedures have been
unable to update the firmware configuration of the
node canister.
User response: Follow troubleshooting procedures to
fix the hardware:
1. Follow the hardware remove and replace
procedures for the node canister .
Possible Cause-FRUs or other:
v Node canister (100%)
535 Canister internal PCIe switch failed
Explanation: The PCI Express switch has failed or
cannot be detected. In this situation, the only
connectivity to the node canister is through the
Ethernet ports.
User response: Follow troubleshooting procedures to
fix the hardware:
1. Follow the procedures to reseat the node canister.
2. If reseating the canister does not resolve the
situation, follow the hardware remove and replace
node canister procedures to replace the canister.
Possible Cause-FRUs or other:
v Node canister (100%)
550 A cluster cannot be formed because of a
lack of cluster resources.
Explanation: The node cannot become active in a
cluster because it is unable to connect to enough cluster
resources. The cluster resources are the node canisters
in the system and the active quorum disk or drive. The
node needs to be able to connect to a majority of the
resources before that group will form an online cluster.
This prevents the cluster splitting into two or more
active parts, with both parts independently performing
I/O.
The error data lists the missing resources. This will
include a list of node canisters and optionally a drive
that is operating as the quorum drive or a LUN on an
external storage system that is operating as the quorum
disk.
If a drive in one of the 2076 enclosures is the missing
quorum disk, it is listed as enclosure:slot[part
identification] where enclosure:slot is the location of the
drive when the node shut down, enclosure is the seven
digit product serial number of the enclosure, slot is a
number between 1 and 24. The part identification is the
22 character string starting "11S" found on a label on a
drive. The part identification cannot be seen until the
drive is removed from the enclosure.
If a LUN on an external storage system is the missing
quorum disk, it is listed it is listed as
WWWWWWWWWWWWWWWW/LL, where
WWWWWWWWWWWWWWWW is a worldwide port
name (WWPN) on the storage system that contains the
missing quorum disk and LL is the Logical Unit
Number (LUN).
User response: Follow troubleshooting procedures to
correct connectivity issues between the cluster nodes
and the quorum devices.
1. Check the status of other node canisters in the
system, resolve any faults on them.
2. Check all enclosures in the system are powered on
and that the SAS cabling between the enclosures
has not been disturbed. If any wiring changes have
been made check all cables are securely connected
and that the cabling rules have been followed.
3. If a quorum drive in a system enclosure is shown as
missing, find the drive and check that it is working.
The drive may have been moved from the location
shown, in that case find the drive and ensure it is
installed and working. If the drive is not located in
the control enclosure, try moving it to the control
enclosure, a problem in SAS connectivity may be
the issue.
Note: If you are able to reestablish the systems
operation you will be able to use the extra
510 • 550
Chapter 7. Event reporting
79