Verifying and setting the HA state of the controller module and chassis

You must verify the HA state of the chassis and controller modules, and, if necessary, update the state to indicate that the system is in an HA pair or a MetroCluster configuration. If your system is in a MetroCluster configuration, you must have ONTAP 8.3 or later installed. If you have a FAS20xx, 31xx, or 60xx system, you can skip this task.

Steps

  1. If you are not already in Maintenance mode, boot to Maintenance mode by entering halt to go to the LOADER prompt:
    If you are running ONTAP 8.2.1 or later, enter boot_ontap maint at the LOADER prompt and enter y to continue when prompted.
  2. In Maintenance mode, display the HA state of the new controller module and chassis from the existing controller module: ha-config show
    The HA state should be the same for all of the components.
    If your system is... The HA state for all components should be...
    In an HA pair ha
    In a MetroCluster configuration mcc
    Stand-alone non-ha
  3. If the displayed system state of the controller does not match your system configuration, set the HA state for the controller module: ha-config modify controller [ha | non-ha]
    If your system is... Then enter this command...
    In an HA pair ha-config modify controller ha
    In a MetroCluster configuration ha-config modify controller mcc
    Stand-alone ha-config modify controller non-ha
  4. If the displayed system state of the chassis does not match your system configuration, set the HA state for the chassis: ha-config modify chassis [ha | non-ha]
    If your system is... Then enter this command...
    In an HA pair ha-config modify chassis ha
    In a MetroCluster configuration ha-config modify chassis mcc
    Stand-alone ha-config modify chassis non-ha
  5. Retrieve the system ID for the current node: sysconfig
    You should make a note of the system ID. You require the system ID when you assign disks to the new node.
  6. Exit Maintenance mode: halt
  7. If you are using root-data partitioning, set the partner system ID for each controller module:
    1. On the existing controller module, set the partner system ID to that of the new controller module: setenv partner-sysid sysID_of_new_controller
    2. On the new controller module, set the partner system ID to that of the existing controller module: setenv partner-sysid sysID_of_existing_controller