Table of ContentsView in Frames

Verifying and setting the HA state on the controller modules and chassis

For systems that use the HA state value, the value must be consistent in all components in the HA pair. You can use the Maintenance mode ha-config command to verify and, if necessary, set the HA state.

About this task

The ha-config command only applies to the local controller module and, in the case of a dual-chassis HA pair, the local chassis. To ensure consistent HA state information throughout the system, you must also run these commands on the partner controller module and chassis, if necessary.

The HA state is recorded in the hardware PROM in the chassis and in the controller module. It must be consistent across all components of the system, as shown in the following table:

If the system or systems are in a... The HA state is recorded on these components... The HA state on the components must be...
Stand-alone configuration (not in an HA pair)
  • The chassis
  • Controller module A
A single-chassis HA pair
  • The chassis
  • Controller module A
  • Controller module B
A dual-chassis HA pair
  • Chassis A
  • Controller module A
  • Chassis B
  • Controller module B

Use the following steps to verify the HA state is appropriate and, if not, to change it:


  1. Reboot the current controller module and press Ctrl-C when prompted to display the boot menu.
  2. At the boot menu, select the option for Maintenance mode boot.
  3. After the system boots into Maintenance mode, enter the following command to display the HA state of the local controller module and chassis: ha-config show
    The HA state should be ha for all components if the system is in an HA pair.
  4. If necessary, enter the following command to set the HA state of the controller: ha-config modify controller ha-state
  5. If necessary, enter the following command to set the HA state of the chassis: ha-config modify chassis ha-state
  6. Exit Maintenance mode by entering the following command: halt
  7. Boot the system by entering the following command at the boot loader prompt: boot_ontap
  8. If necessary, repeat the preceding steps on the partner controller module.