Reconfiguring nodes using array LUNs for stand-alone operation

After uncoupling the nodes in an HA pair, you have three options: each node can continue to own its assigned array LUNs, you can reassign its array LUNs to another storage system that can use array LUNs, or you can release the persistent reservations on the array LUNs so that the LUNs can be used by a non Data ONTAP host.

The HA pair software must be disabled.

If you want both nodes in the HA pair to remain in service and operate as stand-alone systems, each system can continue to own the array LUNs that were assigned to it. Each system, as a stand-alone, continues to see the array LUNs owned by the other system. However, only the system that is the owner of the array LUNs can read from or write to the array LUN, and the systems can no longer fail over to each other.
  1. On each node, halt the node by entering the following command at the console: halt
  2. Turn off the power to each node.
  3. Ground yourself, then remove the HA interconnect cables from both nodes. See the hardware documentation for your system for details.
  4. Move or remove the adapter used for the HA interconnect.
    If your system uses... Then...
    An HA interconnect adapter or an FC-VI adapter Remove the adapter from the system.
    An NVRAM5 or NVRAM6 adapter You might need to change the slot position of the adapter. See the Hardware Universe for details about expansion slot usage for the adapter.
  5. On each node, perform the following steps:
    1. Power on the node, monitoring the system console for error messages during the boot process.
    2. Unset the partner system ID by entering the following command at the prompt: unsetenv partner-sysid
  6. Perform the appropriate step in the following table for what you intend to do with your system and its storage:
    If you want to... Then...
    Keep both systems in service as stand-alone systems and continue with both systems owning the array LUNs that were already assigned to them Boot both systems by entering the following command on each system: boot_ontap
    Remove one of the systems from service but still use the storage that was assigned to that system for Data ONTAP
    1. Boot the node being removed into Maintenance mode, as described in the Data ONTAP System Administration Guide for 7-Mode.
    2. Use the disk reassign command to reassign all the array LUNs so that they all belong to the node that remains.

      The disk reassign command has the following syntax: disk reassign [-o <old_name> | -s <old_sysid>] [-n <new_name>] -d <new_sysid>

    3. Remove the node from service.
    4. Boot the node you are keeping in service by entering the following command: boot_ontap
    Remove one of the systems from service and use the array LUNs that are currently assigned to it for a host that does not run Data ONTAP Release the persistent reservations that Data ONTAP placed on those array LUNs so that the storage administrator can use those LUNs for other hosts.

    See the Data ONTAP Storage Management Guide for 7-Mode for information about what you need to do to prepare for taking a system using array LUNs out of service.