IBM Storwize V7000, Troubleshooting And Maintenance Manual

Page: 160 / 188

Possible Cause—FRUs or other:
v
Enclosure midplane (100%)
504 No enclosure identity and partner node
matches.
Explanation: The enclosure vital product data
indicates that the enclosure midplane has been
replaced. This node canister and the other node canister
in the enclosure were previously operating in the same
enclosure midplane.
User response: Follow troubleshooting procedures to
configure the enclosure.
1.
This is an expected situation during the hardware
remove and replace procedure for a control
enclosure midplane. Continue following the remove
and replace procedure and configure the new
enclosure.
Possible Cause—FRUs or other:
v None
505 No enclosure identity and partner has
system data that does not match.
Explanation:
The enclosure vital product data
indicates that the enclosure midplane has been
replaced. This node canister and the other node canister
in the enclosure do not come from the same original
enclosure.
User response: Follow troubleshooting procedures to
relocate nodes to the correct location.
1. Follow the procedure: Getting node canister and
system information and review the node canister's
saved location information and the status of the
other node canister in the enclosure (the partner
canister). Determine if the enclosure is part of an
active system with volumes that contain required
data. See “Procedure: Getting node canister and
system information using the service assistant” on
page 53.
2. Decide what to do with the node canister that did
not come from the enclosure that is being replaced.
a. If the other node canister from the enclosure
being replaced is available, use the hardware
remove and replace canister procedures to
remove the incorrect canister and replace it with
the second node canister from the enclosure
being replaced. Restart both canisters. The two
node canister should show node error 504 and
the actions for that error should be followed.
b.
If the other node canister from the enclosure
being replaced is not available, check the
enclosure of the node canister that did not come
from the replaced enclosure. Do not use this
canister in this enclosure if you require the
volume data on the system from which the node
canister was removed, and that system is not
running with two online nodes. You should
return the canister to its original enclosure and
use a different canister in this enclosure.
c. When you have checked that it is not required
elsewhere, follow the procedure to remove
cluster data from the node canister that did not
come from the enclosure that is being replaced.
See “Procedure: Removing system data from a
node canister” on page 59. Restart both nodes.
Expect node error 506 to now be reported, and
follow the service procedures for that error.
Possible Cause—FRUs or other:
v
None
506 No enclosure identity and no node state
on partner
Explanation: The enclosure vital product data
indicates that the enclosure midplane has been
replaced. There is no cluster state information on the
other node canister in the enclosure (the partner
canister), so both node canisters from the original
enclosure have not been moved to this one.
User response: Follow troubleshooting procedures to
relocate nodes to the correct location:
1.
Follow the procedure: Getting node canister and
system information and review the saved location
information of the node canister and determine why
the second node canister from the original enclosure
was not moved into this enclosure. See “Procedure:
Getting node canister and system information using
the service assistant” on page 53.
2. If you are sure that this node canister came from
the enclosure that is being replaced, and the original
partner canister is available, use the “Replacing a
node canister” on page 85 procedure to install the
second node canister in this enclosure. Restart the
node canister. The two node canisters should show
node error 504, and the actions for that error should
be followed.
3.
If you are sure this node canister came from the
enclosure that is being replaced, and that the
original partner canister has failed, continue
following the remove and replace procedure for an
enclosure midplane and configure the new
enclosure.
Possible Cause—FRUs or other:
v
None
507 No enclosure identity and no node state
Explanation: The node canister has been placed in a
replacement enclosure midplane. The node canister is
also a replacement or has had all cluster state removed
from it.
User response: Follow troubleshooting procedures to
504 • 507
142
Storwize V7000: Troubleshooting, Recovery, and Maintenance Guide