5.
Return the controller to normal operation by giving back its storage:
storage failover giveback
-ofnode impaired_node_name
6.
If automatic giveback was disabled, reenable it:
storage failover modify -node local
-auto-giveback true
== Step 6: Restore the controller module to operation
To restore the controller, you must recable the system, give back the controller module, and then reenable
automatic giveback.
1. Recable the system, as needed.
If you removed the media converters (QSFPs or SFPs), remember to reinstall them if you are using
fiber optic cables.
2.
Return the controller to normal operation by giving back its storage:
storage failover giveback
-ofnode impaired_node_name
3.
If automatic giveback was disabled, reenable it:
storage failover modify -node local
-auto-giveback true
== Step 7: Switch back aggregates in a two-node MetroCluster configuration
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.
This task only applies to two-node MetroCluster configurations.
Steps
1.
Verify that all nodes are in the
enabled state: metrocluster node show
cluster_B::> metrocluster node show
DR Configuration DR
Group Cluster Node State Mirroring Mode
----- ------- -------------- -------------- ---------
--------------------
1 cluster_A
Ê controller_A_1 configured enabled heal roots
completed
Ê cluster_B
Ê controller_B_1 configured enabled waiting for
switchback recovery
2 entries were displayed.
2.
Verify that resynchronization is complete on all SVMs:
metrocluster vserver show
3. Verify that any automatic LIF migrations being performed by the healing operations were completed
197
To Next Page
Loading...
