e. Giveback SFO, (no force)
2. If your system does not have Encryption configured, complete the following procedure to reboot the
system:
a. Boot to Menu and run Option 1.
b. Give back the controller:
c.
From the healthy controller, give back the replaced controller’s storage:
storage failover
giveback -ofnode replacement_node_name
The replacement controller takes back its storage and completes booting.
If the giveback is vetoed, you can consider overriding the vetoes.
Find the High-Availability Configuration content for your version of ONTAP 9
d. After the giveback has been completed, confirm that the HA pair is healthy and that takeover is
possible:
storage failover show
3.
If the system is in a MetroCluster configuration, monitor the status of the controller:
metrocluster node
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.
4. 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.
Disk ownership changes during HA takeover and MetroCluster switchover in a four-node MetroCluster
configuration
5.
If your system is in a MetroCluster configuration, verify that each controller is configured:
metrocluster
node show - fields configuration-state
41
To Next Page
Loading...
