Power Server Nodes On and Off

Do the following to power on a single node:

  1. Push the power switch on the front of the node you wish to power on.
  2. If you want this node to operate as the primary node perform a failover ( see Initiate a Graceful Server Failover) after the system is powered up.
  3. Mount the file systems on all LAN and SAN clients.
  4. Restart I/O access to all LAN clients.
  5. If NAS Failover for NFS Clusters (NFS-HA) was previously enabled, click here to re-enable NFS-HA.

You will need to power off a single server node when you need to perform a CRU or installation procedure on the node, or to move a single node to a different location within a rack (Quantum recommends nodes are collocated in the same rack), while allowing uninterrupted metadata operations on the StorNext system.

Caution: For systems running NAS with NFS-HA enabled, DO NOT stop cvfs on the system before first stopping NAS. Learn more about this issue before you continue with this procedure.

Do the following to power off a single server node:

  1. Open an SSH connection to the appropriate server and use the IP address assigned to the node on the Management or LAN Client network, or use the Service Port IP address.

    • 10.17.21.1

  2. Initiate an ssh session to the system using Terminal or PuTTY:
    1. Log in to the command line using the following credentials:
      • User name: stornext
      • Password: <stornext user account password>

        Note: "password" is the default password for the stornext user account. If the password has been changed, use the current password. Beginning with StorNext 7.0.2, you must change the default password for the stornext user account. As of StorNext 7.0.2, the first time you log in, you will be prompted to change the password to a different one.

    2. Enter sudo rootsh to gain root user access.
    3. Enter the password for the stornext user account again.
  1. If you are connected to the node currently acting as the secondary, or for a single-node system, continue to step 11.

    2. However, if you are connected to the node currently acting as the primary, stop cvfs.

    Note: If you have NFS-HA enabled, click here for the instructions to stop NAS prior to using this command.

    Enter:

    systemctl stop cvfs

    Note: The systemctl stop cvfs command does not provide any command-line status feedback on the progress of stopping cvfs operations. You will need to be patient and wait until you again have access to the command line prompt.

  2. Wait until the node currently acting as primary becomes the secondary (time may vary), and leave your SSH connection to this node open.
  3. Open an SSH connection to the node now operating as the primary. Confirm that the node is operating as the primary. Enter:

    4. snhamgr -m status

  4. Verify the output is (bold used for clarification):

    5. :default:primary:default:stopped:

    "primary" indicates that this node is operating as primary.

  5. On the SSH terminal session for the secondary node (may have previously been running as primary), power off the server. Enter:

    6. systemctl --no-wall poweroff

    You will know the node is powered off when your monitor goes blank, or you lose your connection to the node.

  6. If needed, remove power cables from the node.