IBM Storwize V7000 Troubleshooting And Maintenance Manual page 173

because of a lack of cluster resources is reported
on the node canister.
Data:
v A number indicating the adapter location. Location 0
indicates that the adapter integrated into the system
board is being reported.
User response:
1. If possible, this noncritical node error should be
serviced using the management GUI and running
the recommended actions for the service error code.
2. As the adapter is located on the system board,
replace the node canister using the remove and
replace procedures.
Possible Cause-FRUs or other cause:
v Node canister
733 The bus adapter degraded.
Explanation: The bus adapter that connects the
canister to the enclosure midplane is degraded.
This node error does not, in itself, stop the node
canister becoming active in the system. However, the
bus might be being used to communicate between the
node canisters in a clustered system. Therefore, it is
possible that this node error indicates the reason why
the critical node error 550 A cluster cannot be formed
because of a lack of cluster resources is reported
on the node canister.
Data:
v A number indicating the adapter location. Location 0
indicates that the adapter integrated into the system
board is being reported.
User response:
1. If possible, use the management GUI to run the
recommended actions for the associated service
error code.
2. As the adapter is located on the system board,
replace the node canister using the remove and
replace procedures.
Possible Cause-FRUs or other cause:
v Node canister
734 Fewer bus ports.
Explanation: One or more PCI bus ports that have
previously been active are now inactive. This condition
has existed for over one minute. That is, the internode
link has been down at the protocol level.
This could be a link issue but is more likely caused by
the partner node unexpectedly failing to respond.
Data:
Three numeric values are listed:
v The ID of the first unexpected inactive port. This is a
decimal number.
v The ports that are expected to be active. This is a
hexadecimal number. Each bit position represents a
port, with the least significant bit representing port 1.
The bit is 1 if the port is expected to be active.
v The ports that are actually active. This is a
hexadecimal number. Each bit position represents a
port, with the least significant bit representing port 1.
The bit is 1 if the port is active.
User response:
1. If possible, this noncritical node error should be
serviced using the management GUI and running
the recommended actions for the service error code.
2. Follow the procedure for getting node canister and
clustered-system information and determine the
state of the partner node canister in the enclosure.
Fix any errors reported on the partner node canister.
3. Use the remove and replace procedures to replace
the enclosure.
Possible Cause-FRUs or other cause:
v Node canister
v Enclosure midplane
740 The command failed because of a
wiring error described in the event log.
Explanation: It is dangerous to exclude a sas port
while the topology is invalid, so we forbid the user
from attempting it to avoid any potential loss of data
access.
User response: Correct the topology, then retry the
command.
820 Canister type is incompatible with
enclosure model
Explanation: The node canister has detected that it
has a hardware type that is not compatible with the
control enclosure MTM, such as node canister type 300
in an enclosure with MTM 2076-112.
This is an expected condition when a control enclosure
is being upgraded to a different type of node canister.
User response:
1. Check that all the upgrade instructions have been
followed completely.
2. Use the management GUI to run the recommended
actions for the associated service error code.
Possible Cause-FRUs or other cause:
v None
Chapter 9. Event reporting
733 • 820
155