Explanation
The node hardware is not at the minimum specification for the node to become active in a cluster. This may be because of hardware failure, but is also possible after a service action has used an incorrect replacement part.
User Response
Follow troubleshooting procedures to fix the hardware:
- View node VPD information, to see whether anything looks inconsistent. Compare the failing node VPD with the VPD of a working node of the same type. Pay particular attention to the number and type of CPUs and memory.
- Replace any incorrect parts.
User Response
Follow troubleshooting procedures to fix the hardware:
- It is not possible to service parts within the node canister. Reseat the existing node canister to see whether the problem fixes. If it does not, use the hardware node canister remove and replace procedures to change the node canister.
User Response
Follow troubleshooting procedures to fix the hardware:
- View node VPD information, to see whether anything looks inconsistent. Compare the failing node VPD with the VPD of a working node canister of the same type. Pay particular attention to the number and type of CPUs, memory, and adapters.
- If the canister has just had parts replaced or added, check the parts are the correct ones for use in the system.
- Replace any incorrect parts.
- A code update may be required to support the new hardware.
Possible Cause—FRUs or other:
User Response
Follow troubleshooting procedures to fix the hardware:
- View node VPD information, to see whether anything looks inconsistent. Compare the failing node VPD with the VPD of a working node canister of the same type. Pay particular attention to the number and type of CPUs, memory, and adapters.
- If the canister has just had parts replaced or added, check the parts are the correct ones for use in the system.
- Replace any incorrect parts.
- A code update may be required to support the new hardware.
Possible Cause—FRUs or other: