8.
If you disabled automatic takeover on reboot, enable it from the healthy node:
storage failover
modify -node replacement-node-name -onreboot true
Option 2: Manually reassign the system ID on a stand-alone system in ONTAP
In a stand-alone system, you must manually reassign disks to the new controller’s system
ID before you return the system to normal operating condition.
About this task
This procedure applies only to systems that are in a stand-alone configuration.
Steps
1. If you have not already done so, reboot the replacement node, interrupt the boot process by pressing Ctrl-
C, and then select the option to boot to Maintenance mode from the displayed menu.
2. You must enter Y when prompted to override the system ID due to a system ID mismatch.
3. View the system IDs: disk show -a
4. You should make a note of the old system ID, which is displayed as part of the disk owner column.
The following example shows the old system ID of 118073209:
*> disk show -a
Local System ID: 118065481
Ê DISK OWNER POOL SERIAL NUMBER HOME
-------- ------------- ----- ------------- -------------
disk_name system-1 (118073209) Pool0 J8XJE9LC system-1
(118073209)
disk_name system-1 (118073209) Pool0 J8Y478RC system-1
(118073209)
.
.
.
5.
Boot the node:
boot_ontap
Complete system restoration - AFF A200
Step 1: Install licenses for the replacement node 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
47
To Next Page
Loading...
Need help?
General
