Verifying the system ID change on an HA system

You must confirm the system ID change when you boot the replacement controller and then verify that the change was implemented.

This procedure applies only to systems running ONTAP in an HA pair.

If the replacement controller is in Maintenance mode (showing the *> prompt, exit Maintenance mode and go to the LOADER prompt: halt
From the LOADER prompt on the replacement controller, boot the controller, entering y if you are prompted to override the system ID due to a system ID mismatch:boot_ontap

Wait until the Waiting for giveback... message is displayed on the replacement controller console and then, from the healthy controller, verify that the new partner system ID has been automatically assigned.

Example

node1> <kbd className="ph userinput nolinebreak">storage failover show</kbd>
                                    Takeover          
Node              Partner           Possible     State Description 
------------      ------------      --------     -------------------------------------
node1             node2             false        System ID changed on partner (Old:
                                                  151759755, New: 151759706), In takeover    
node2             node1             -            Waiting for giveback (HA mailboxes)

From the healthy controller, verify that any coredumps are saved:
1. Change to the advanced privilege level: set -privilege advanced
  You can respond Y when prompted to continue into advanced mode. The advanced mode prompt appears (*>).
2. Save any coredumps: system node run -node local-node-name partner savecore
3. Wait for savecore command to complete before issuing the giveback.
  You can enter the following command to monitor the progress of the savecore command: system node run -node local-node-name partner savecore -s
4. Return to the admin privilege level: set -privilege admin
Give back the controller:
1. 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 you are prompted to override the system ID due to a system ID mismatch, you should enter y.
  Note
  If the giveback is vetoed, you can consider overriding the vetoes.
  If giveback is vetoed
2. After the giveback has been completed, confirm that the HA pair is healthy and that takeover is possible: storage failover show
  The output from the storage failover show command should not include the System ID changed on partner message.
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. The metrocluster node show -fields node-systemid command output displays the old system ID until the MetroCluster configuration returns to a normal state.

Verify that the disks or Flex Array LUNS were assigned correctly: storage disk show -ownership

Example

The disks belonging to the replacement controller should show the new system ID. In the following example, the disks owned by node1 now show the new system ID, 1873775277:

node1> <kbd className="ph userinput nolinebreak">storage disk show -ownership</kbd> 

Disk  Aggregate Home  Owner  DR Home  Home ID    Owner ID  DR Home ID Reserver  Pool
----- ------    ----- ------ -------- -------    -------    -------  ---------  ---
1.0.0  aggr0_1  node1 node1  -        1873775277 1873775277  -       1873775277 Pool0
1.0.1  aggr0_1  node1 node1           1873775277 1873775277  -       1873775277 Pool0
.
.
.

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.
  Recover from a disaster

If your system is in a MetroCluster configuration, verify that each controller is configured: metrocluster node show - fields configuration-state

Recover from a disaster

Example

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.

Verify that the expected volumes are present for each controller: vol show -node node-name
If you disabled automatic takeover on reboot, enable it from the healthy controller: storage failover modify -node replacement-node-name -onreboot true

Give feedback