Tools > High Availability > Manage

From the Tools menu, click High Availability, and then click Manage. The Manage option allows you to view the current status of the file systems on your HA systems.

The table below shows the information displayed on the Tools > High Availability page:

Parameter Description

File System

Displays the name of a file system.

Status

Displays the status of a file system on your primary node or secondary node, as follows:

  • Active
  • Inactive
  • Standby
  • Unknown

Host

Displays the IP address of the host system where the file system is running.
Enter Config Mode

Click to place the HA Cluster in a state that allows the Primary MDC to restart CVFS and individual FSMs without incurring an HA Reset, failover of any file systems, or transfer of Primary status to the peer MDC.

Note: This is required for making configuration changes to the HaShared file system using the GUI.

Caution: When exiting HA Config mode, StorNext is stopped, which also fuser any processes which have files open on the file system from either node. Prepare your systems before entering HA Config mode.
Exit Config Mode

Caution: Setting haFsType to HaUnmonitored disables the HA monitor timers used to guarantee against split brain. When two MDCs are configured to run as an HA pair but full HA protection is disabled in this way, it is possible in rare situations for file system metadata to become corrupt if there are lengthy delays or excessive loads in the LAN and SAN networks that prevent an active FSM from maintaining its branding of the ARB in a timely manner.

Enter Config Mode sets the peer (secondary) node to locked mode and sets the local (primary) node to config mode for administration purposes. The locked mode stops CVFS on the peer, and is designed for automated short-duration stops of the secondary server to make configuration changes and other modifications. This allows the HA Manager to prevent HA resets while making configuration changes or stopping the primary server.

Note: In the event that TCP communication to the secondary server is lost for any reason, the primary server assumes the secondary server is in default mode and transitions the local server out of config mode. For this reason, the locked mode is not appropriate to use for extended secondary-server outages, activities that might include reboots of the secondary server, etc. Best practice is to use Peerdown mode when a server is turned off for an extended period, or to simply keep the primary server in default mode while the secondary server is brought in and out of service in short durations.

  1. On the Tools menu, click High Availability, and then click Manage.
  2. Click Enter Config Mode.
  3. When the confirmation message appears, click Yes to proceed or No to abort.
  4. Click OK when a message informs you that the HA cluster was successfully locked.
  5. When you are ready to unlock the cluster and exit Config mode, click Exit Config Mode to start both nodes of the HA cluster in default mode.
  6. When the confirmation message appears, click Yes to proceed or No to abort.
  7. Click OK when a message informs you that the HA cluster was successfully unlocked.