NetApp ASA C Series Install page 158

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
10. 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
-----------
-------------------
1 node1_siteA
1 node1_siteA
1 node1_siteB
1 node1_siteB
4 entries were displayed.
11. Verify that the expected volumes are present for each controller:
12. If you disabled automatic takeover on reboot, enable it from the healthy controller:
failover modify -node replacement-node-name -onreboot true
= Complete system restoration - ASA C400
:icons: font
:relative_path: ./asa-c-400/
:imagesdir: /tmp/d20231020-12297-25s5m0/source/./asa-c-250/../media/
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.
About this task
Until you install license keys, features requiring standard licenses continue to be available to the
replacement node. However, if the impaired node was the only node in the cluster with a license for the
feature, no configuration changes to the feature are allowed. Also, using unlicensed features on the node
might put you out of compliance with your license agreement, so you should install the replacement
license key or keys on the replacement node as soon as possible.
156
cluster node
---------------------- --------------
node1mcc-001
node1mcc-002
node1mcc-003
node1mcc-004
configuration-state
configured
configured
configured
configured
vol show -node node-name
storage