Nodes
Nodes
A StorONE cluster is made up of one or more physical (or virtual) nodes — the servers that run the StorONE software and serve I/O to your hosts. This chapter covers the node-level administration and network settings that are available to you as a customer; most of what's in the underlying nodes command group is diagnostic and support tooling reserved for StorONE support engineers, so it isn't covered here.
This chapter is split into three pages:
- Nodes overview (this page) — listing nodes, renaming them, viewing connected sessions, checking the management database, and running network diagnostic utilities.
- High availability — takeover, giveback, and switching your session's node connection.
- Support access and network settings — the support tunnel, downloading a support package, and iSCSI CHAP/iSNS settings.
Listing nodes
nodes list is the basic inventory view of every node in the cluster. By default it shows just the node names; turn on the extra columns you need:
- Sensors — hardware sensor readings (temperature, fans, and similar).
- Gateway — each node's iSCSI IQNs and Fibre Channel WWPNs, which is what you'll need when configuring host connectivity.
- Volumes — which volumes are currently running on each node.
- IP — the node's IP addresses.
- SED — whether the self-encrypting drive password is set on that node.
- Memory — memory statistics.
Using the web interface
Open Inventory > Nodes. Use the toolbar to toggle which extra columns are shown.
Using the CLI
nodes list [--sensors] [--gateway] [--vols] [--ip] [--sed] [--memory]
| Option | Description |
|---|---|
--sensors |
Show node sensor readings. |
--gateway |
Show the IQNs and WWPNs of the nodes. |
--vols |
List the volumes running on each node. |
--ip |
Show the IP addresses of the nodes. |
--sed |
Show whether the SED password is set. |
--memory |
Show memory stats. |
Examples
Basic node list:
nodes list
Node list with IP addresses and the volumes each node is currently running:
nodes list --ip --vols
Node list with iSCSI/FC gateway identifiers, for setting up host connectivity:
nodes list --gateway
Renaming a node
nodes edit renames a node. You need the Admin role to do this.
Using the web interface
- Open Inventory > Nodes, select the node, and click Edit.
- Under Node Selection, confirm the node, then enter the new name.
- Confirm the change.
Using the CLI
nodes edit --node=<hostname> --newname=<hostname>
| Option | Description |
|---|---|
--node=<hostname> |
The name of the node to rename. |
--newname=<hostname> |
The node's new name. |
Example
Rename s1-node-01 to s1-node-a:
nodes edit --node s1-node-01 --newname s1-node-a
Connected sessions
nodes sessions shows the client sessions currently connected to each node — useful for confirming what's actually connected to a node before you take it offline for maintenance, or for troubleshooting an unexpected connection.
Using the web interface
- Open Inventory > Nodes.
- Select Sessions, optionally filtering to a specific node under Node Selection.
Using the CLI
nodes sessions [--node=<name>]
| Option | Description |
|---|---|
--node=<name> |
Filter by node name. If omitted, all nodes are included. |
Examples
Sessions on every node:
nodes sessions
Sessions on a specific node:
nodes sessions --node s1-node-01
Management database state
nodes management_db state reports the health of the internal RAID array that hosts the management database — the system's own configuration and metadata store, distinct from your data pools. It's a quick way to confirm the management service itself is healthy. It takes no parameters.
Using the web interface
Open Inventory > Nodes and select Management Database State.
Using the CLI
nodes management_db state
Example
nodes management_db state
Running network diagnostic utilities
nodes utils run runs one of a small set of network diagnostic utilities directly on a node — by default ping, iperf, iperf3, nc, and a Seagate drive diagnostic dump utility (your system administrator can change which utilities are exposed). This isn't a general-purpose shell; it's meant for quick connectivity troubleshooting, such as confirming a node can reach a replication target or testing throughput to a remote host.
Using the web interface
- Open Inventory > Nodes and select Run Utility.
- Under Node Selection, choose the node to run the utility on.
- Choose the Utility to run and supply any Arguments it needs (for example, a target IP address for
ping). - Confirm to run it. Results are returned once the utility finishes.
Using the CLI
nodes utils run --node=<name> --utility=<text> [--args=<text>]
| Option | Description |
|---|---|
--node=<name> |
The node to run the utility on. |
--utility=<text> |
The utility to run. |
--args=<text> |
Arguments to pass to the utility. |
Examples
Ping a remote host from a specific node:
nodes utils run --node s1-node-01 --utility ping --args "-c 4 10.10.10.5"
Run an iperf3 throughput test against a remote server:
nodes utils run --node s1-node-01 --utility iperf3 --args "-c 10.10.10.5 -t 10"
Next: High availability — takeover, giveback, and switching your session's node connection.