If your system is in… Then perform these steps…
A two-node MetroCluster
configuration
a. With the cam handle in the open position, firmly push the
controller module in until it meets the midplane and is fully seated,
and then close the cam handle to the locked position. Tighten the
thumbscrew on the cam handle on back of the controller module.
Do not use excessive force when sliding the
controller module into the chassis to avoid
damaging the connectors.
b. If you have not already done so, reinstall the cable management
device.
c. If you have not already done so, reconnect the cables to the
controller module.
d. Bind the cables to the cable management device with the hook
and loop strap.
e. Reconnect the power cables to the power supplies and to the
power sources, and then turn on the power to start the boot
process.
5. If your system is configured to support 10 GbE cluster interconnect and data connections on 40 GbE NICs
or onboard ports, convert these ports to 10 GbE connections by using the nicadmin convert command from
Maintenance mode.
Be sure to exit Maintenance mode after completing the conversion.
6. Return the node to normal operation:
If your system is in… Issue this command from the partner’s console…
An HA pair
storage failover giveback -ofnode
impaired_node_name
A two-node MetroCluster
configuration
Proceed to the next step. The MetroCluster switchback procedure is
done in the next task in the replacement process.
7.
If automatic giveback was disabled, reenable it:
storage failover modify -node local -auto
-giveback true
Step 5 (two-node MetroCluster only): Switch back aggregate
After you have completed the FRU replacement in a two-node MetroCluster
configuration, you can perform the MetroCluster switchback operation. This returns the
configuration to its normal operating state, with the sync-source storage virtual machines
(SVMs) on the formerly impaired site now active and serving data from the local disk
pools.
375
To Next Page
Loading...
Need help?
General
