show
The MetroCluster configuration takes a few minutes after the replacement to return to a normal state, at
which time each controller will show a configured state, with DR Mirroring enabled and a mode of normal.
The
metrocluster node show -fields node-systemid
command output displays the old system
ID until the MetroCluster configuration returns to a normal state.
8. If the controller is in a MetroCluster configuration, depending on the MetroCluster state, verify that the DR
home ID field shows the original owner of the disk if the original owner is a controller on the disaster site.
This is required if both of the following are true:
◦
The MetroCluster configuration is in a switchover state.
◦
The
replacement
controller is the current owner of the disks on the disaster site.
9. If your system is in a MetroCluster configuration, verify that each controller is configured:
metrocluster
node show - fields configuration-state
node1_siteA::> metrocluster node show -fields configuration-state
dr-group-id cluster node configuration-state
----------- ---------------------- --------------
-------------------
1 node1_siteA node1mcc-001 configured
1 node1_siteA node1mcc-002 configured
1 node1_siteB node1mcc-003 configured
1 node1_siteB node1mcc-004 configured
4 entries were displayed.
10. Verify that the expected volumes are present for each controller:
vol show -node node-name
11. If you disabled automatic takeover on reboot, enable it from the healthy controller:
storage failover
modify -node replacement-node-name -onreboot true
Complete system restoration - FAS500f
To restore your system to full operation, you must restore the NetApp Storage Encryption
configuration (if necessary), and install licenses for the new controller, and return the
failed part to NetApp, as described in the RMA instructions shipped with the kit.
Step 1: Install licenses for the replacement controller in ONTAP
You must install new licenses for the
replacement
node if the impaired node was using ONTAP features that
require a standard (node-locked) license. For features with standard licenses, each node in the cluster should
have its own key for the feature.
42