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
successfully:
metrocluster check lif show
4.
Perform the switchback by using the
metrocluster switchback command from any node in the
surviving cluster.
5.
Verify that the switchback operation has completed:
metrocluster show
The switchback operation is still running when a cluster is in the waiting-for-switchback state:
cluster_B::> metrocluster show
Cluster Configuration State Mode
-------------------- ------------------- ---------
ÊLocal: cluster_B configured switchover
Remote: cluster_A configured waiting-for-switchback
The switchback operation is complete when the clusters are in the normal state.:
cluster_B::> metrocluster show
Cluster Configuration State Mode
-------------------- ------------------- ---------
ÊLocal: cluster_B configured normal
Remote: cluster_A configured normal
If a switchback is taking a long time to finish, you can check on the status of in-progress baselines by using
the
metrocluster config-replication resync-status show command.
6. Reestablish any SnapMirror or SnapVault configurations.
Step 8: Return the failed part to NetApp
After you replace the part, you can return the failed part to NetApp, as described in the
RMA instructions shipped with the kit. Contact technical support at
NetApp Support, 888-
463-8277 (North America), 00-800-44-638277 (Europe), or +800-800-80-800
(Asia/Pacific) if you need the RMA number or additional help with the replacement
procedure.
Hot-swap a fan module - AFF A400
To swap out a fan module without interrupting service, you must perform a specific
sequence of tasks.
You must replace the fan module within two minutes of removing it from the chassis. System
airflow is disrupted and the controller module or modules shut down after two minutes to avoid
overheating.
546
To Next Page
Loading...
Need help?
General
