Nodes

Two-node cluster

The S1most commonly deployed StorONE (S1) system consists of a two-node cluster. The nodes are servers with a high availability (HA) connection. The S1 is a complete operating system that manages the controller node servers and their peripherals. Each node has its own internal storage where theand S1 operating system resides.software.

NodesController nodes are responsible for managing andaccess running theto disk enclosure.drive resources. Users interact with the S1 system using either the CLI or the GUI. Typically each CLI or GUI session establishes a simultaneous direct connection with both nodes.

Direct communication with a node is called an optimized communication path. Failed optimized connection with one node, for instance node A, may result in a non-optimized connection with this node. Namely, communication with the node goes through the direct connection path of the other node (node B) and the HA interconnection that connects the two nodes. When the direct connection with node A returns, the connection path with node A will go through the optimized path.

List all nodes

To display all S1 nodes, use the command nodes list.

Usage

nodes list [--sensors] [--gateway] [--vols] [--ip] [--sed]

Options

Options and arguments	Description
--sensors	Display information on sensors.
--gateway	Display information on the IQNs (iSCSI qualified names) and WWNs (world wide names) of the nodes.
--vols	Display a list of volumes served by each of the nodes.
--ip	Display IP information for each of the nodes.
--sed	Display information about self-encrypting drive (SED) password.

Examples

1. To list of all nodes, run nodes list
2. To list nodes with additional information on hardware sensors, run nodes list --sensors
3. To list nodes with additional information on sensors and the volumes on each of the nodes, run nodes list --sensors --volumes

ConnectedClient nodesconnections

To list all connected nodes,clients, use the nodes sessions command. IfClient thereconnections isinclude aconnection problemfrom withinitiator onehosts ofto theblock nodesvolumes, oras itwell isas outServer ofMessage reach,Block then(SMB) thisand nodeNetwork won'tFile appearSystem in(NFS) the list.connections.

Usage

nodes sessions [--node=<node_name>]

Options

Options and arguments	Description
--node=<node_name>	Filter results by node name.

Examples

1. To list of all connected nodes, run nodes sessions
2. To checkview whetherall clients connected to node s1-6021 is connected,, run nodes sessions --node s1-6021

 

Manual failover

To instruct one of the nodes to take over all volumes of the other node, use the nodes takeover command. You must specify the name of the node that will take over all the volumes. Upon successful execution of this command, the high availability (HA) state of the takeover node will change to All while the state of the other node will change to None.

Usage

nodes takeover --node=<name> [--force]

Options

Options and arguments	Description
--node=<node_name>	Specify the name of the node that will takeover. Replace <node_name> with the name of the node.
--force	Force the failover operation.

Examples

1. To instruct node s1-6021 to take over all volumes of the other node, run nodes takeover --node s1-6021
2. To force node s1-6021 to takeover all volumes of the other node, run nodes takeover --node s1-6021 --force

Manual failback

To balancereturn the numbersystem ofto high availability (HA) mode, where volumes betweenare managed by the nodes,original assigned controller node, use the command nodes giveback.

Usage

nodes giveback [--force]

Options

Options and arguments	Description
--force	forceDo thenot manualprompt failbackfor operation.confirmation.

Examples

1. To balancereturn the numbersystem ofto volumesHA between the nodes,mode, run nodes giveback
2. To forcereturn balancethe betweensystem nodes,to HA mode and skip the confirmation prompt, run nodes giveback --force

DisableEnable a nodesupport tunnel

The support tunnel refers to a mechanism that allows StorONE support to remotely access and support your system. It enables a secure connection to your StorONE system using secure a secure shell (SSH) that is only accessible by internal StorONE personnel. To disable one ofenable the nodes,support tunnel, use the nodesnode support tunnel disableenable command. Upon successful execution of this command, all volumes served by the disabled node will be served by the other (functioning) node.

Usage

 nodes support tunnel disableenable --node=<n_namenode>

Options

Options and arguments	Description
--node=<n_namenode>	Specify whichthe node to disable, replace <n_name> withenable the namesupport oftunnel the node that you want to disable.
	to.

Examples

1. To disableenable a support tunnel on node s1-6021, run

   nodes support tunnel enable --node s1-6021

Disable a support tunnel

To disable the support tunnel, use the nodes support tunnel disable command.

Usage

nodes support tunnel disable --node s1-6021

Enable a node

To enable a node, use the node support tunnel enable command. Enabling a node won't return the its previously served volumes, for this to happen you need to run the nodes giveback command.

Usage

 nodes support tunnel enable --node=<n_namenode>

Options

Options and arguments	Description
--node=<n_namenode>	Specify whichthe node to enable, replace <n_name> withdisable the namesupport oftunnel the node that you want to enable.
	to.

Examples

1. To enabledisable the support tunnel on node name s1-6021, run

   nodes support tunnel enabledisable --node s1-6021

Status information forDisplay support tunnel status

To getview the current status information forof the support tunnel, including functioning nodes and volume load-balance information, use the nodes support tunnel status command. If the support tunnel of a node is enabled, then the tunnel key appears in the Support Tunnel Status column, inside the parenthesis. You can provide this tunnel key to StorONE support to allow them to access and troubleshoot your system.

Usage

nodes support tunnel status

Options

This command has no options.

Examples

1. To get status information on all nodes, run nodes support tunnel status