If the newly installed controller modules are reused—not new—you must enter Maintenance mode and ensure that their HA state is set to HA.
About this task
If you are using new controller modules, you can skip this procedure because HA is enabled by default. Otherwise, you must perform this procedure on both the nodes.
- On the first node, enter Maintenance mode:
If the DM stack is powered off:
Ensure the serial connections between the nodes and the PC are connected.
Power on the expansion shelves and wait one minute.
Power on the head shelf.
When the message stating AUTOBOOT is starting appears, hit Ctrl-C to interrupt the boot and get to the loader prompt.
Type boot_ontap maint at the LOADER prompt to access the maintenance menu.
After some information is displayed, the Maintenance mode prompt is displayed.
If the DM stack is already powered on:
Exit the nodeshell by entering halt.
The LOADER prompt is displayed.
Enter Maintenance mode by entering boot_ontap maint.
After some information is displayed, the Maintenance mode prompt is displayed.
- In Maintenance mode, ensure that the controller module and chassis are in HA state:
- Display the HA state of the controller module and chassis by entering ha-config show.
- If the displayed state of the controller is not HA, enter ha-config modify controller ha.
- If the displayed state of the chassis is not HA, enter ha-config modify chassis ha.
- Verify that HA is enabled on both the controller module and chassis by entering ha-config show.
- Return to ONTAP:
- Enter halt to exit Maintenance mode.
- Boot ONTAP by entering boot_ontap on the LOADER prompt.
- Make sure that node boots back up to the cluster setup prompt.
- Repeat this procedure on the other node that you are adding to the cluster.