Skip to main content
ONTAP MetroCluster

Changing the ha-config setting on the existing and new controller modules

Contributors netapp-thomi
PDFs

When you expand a MetroCluster configuration, you must update the ha-config setting of the existing controller module and the new controller module. You must also determine the system ID of the new controller module.

About this task

This task is performed in Maintenance mode on both the existing and new controller modules.

Steps

  1. Change the ha-config setting of the existing controller module:

    1. Display the ha-config setting of the existing controller module and chassis:

      ha-config show

      The ha-config setting is “mcc-2n” for all components because the controller module was in a two-node MetroCluster configuration.

    2. Change the ha-config setting of the existing controller module to “mcc”:
      ha-config modify controller mcc

    3. Change the ha-config setting of the existing chassis to “mcc”:

      ha-config modify chassis mcc

    4. Retrieve the system ID for the existing controller module:

      sysconfig

      Note the system ID. You need it when you set the partner ID on the new controller module.

    5. Exit Maintenance mode to return to the LOADER prompt:

      halt

  2. Change the ha-config setting and retrieve the system ID of the new controller module:

    1. If the new controller module is not already in Maintenance mode, boot it to Maintenance mode:

      boot_ontap maint

    2. Change the ha-config setting of the new controller module to “mcc”:

      ha-config modify controller mcc

    3. Change the ha-config setting of the new chassis to mcc:

      ha-config modify chassis mcc

    4. Retrieve the system ID for the new controller module:

      sysconfig

      Note the system ID. You need it when you set the partner ID and assign disks to the new controller module.

    5. Exit Maintenance mode to return to the LOADER prompt:

      halt