Configuring a node for non-HA (stand-alone) use

By default, storage controllers are configured for use in HA mode. To use a controller in stand-alone mode, you must disable the controller failover functionality and change the node to non-HA mode.

You must determine the current configuration of the storage controller because the controller failover and HA mode states can vary. You can use the cf status command to determine the current configuration.

You must also confirm that all loops and disk shelves in the system contain disks that belong to only one of the two nodes you intend to isolate. If any disk shelves or loops contain a mix of disks belonging to both nodes, you must move data.

When a storage controller is shipped from the factory or when Data ONTAP is reinstalled using option four of the Data ONTAP boot menu (Clean configuration and initialize all disks), HA mode is enabled by default, and the system's nonvolatile memory (NVRAM or NVMEM) is split. If you plan to use the controller in standalone mode, you must configure the node as non-HA. Reconfiguring the node as non-HA mode enables full use of the system's nonvolatile memory.

Note: Configuring the node as standalone removes the availability benefits of the HA configuration and creates a single point of failure.

For information on using the boot menu to manage the storage system, see the Data ONTAP System Administration Guide for 7-Mode.

  • If the cf status output displays Non-HA mode, then the node is configured for non-HA mode and you are finished:
    node > cf status
    Non-HA mode.
    

  • If the cf status output directs you to reboot, you must reboot the node to enable full use of the system's nonvolatile memory:
    node> cf status
    Non-HA mode. Reboot to use full NVRAM.
    
    1. Reboot the node using the following command:node> reboot
    After the node reboots, you are finished.

  • If the cf status output displays Controller Failover enabled, you must disable both controller failover and HA mode and then reboot the node to enable full use of the system's nonvolatile memory:
    node> cf status
    Controller Failover enabled
    
    1. Disable controller failover using the following command:node> cf disable
    2. Set the mode to non-HA by using the following command:node> options cf.mode non_ha
    3. Open the /etc/rc file with a text editor and remove references to the partner node in the ifconfig entries, as shown in the following example:

      Original entry:

      ifconfig e0 199.9.204.254 partner 199.9.204.255

      Edited entry:

      ifconfig e0 199.9.204.254
    4. Reboot the node by using the following command:node> reboot
    After the node reboots, you are finished.

  • If the cf status output displays Controller Failover disabled, then the HA mode is still enabled, so you must set the HA mode to non-HA and reboot the node to enable full use of the system's nonvolatile memory:
    node> cf status
    Controller Failover disabled
    
    1. Set the mode to non-HA by using the following command:node> options cf.mode non_ha
    2. Reboot the node by using the following command:node> reboot
    After the node reboots, you are finished.

Reconfigure the hardware.