Network
Network
StorONE hosts connect to volumes over the network —— iSCSI or NVMeOF —— using the IP addresses configured on the system's network interface cards (NICs). By default, a newly configured IP isn't enabled for either protocol; you turn on the protocol(s) you need on the specific IPs you want hosts to connect through. This page covers listing your NICs/IPs, enabling and disabling iSCSI and NVMeOF traffic on them, and testing basic network reachability.
This is about StorONE acting as the storage target that hosts connect to. If instead you're connecting StorONE to an external NVMeOF-attached drive enclosure to use its drives as pool capacity, see NVMeOF Enclosures —— that's a different, initiator-side relationship that happens to share the "NVMeOF" name.
Listing network interfaces
Using the web interface
Open Inventory > Resources > Network. The list shows every NIC per node; use the toolbar to show only NICs with errors or to show advanced details.
Using the CLI
resources network list [--errors] [--details] [--ids=<numbers...>]
| Option | Description |
|---|---|
--errors |
Show only components with errors. |
--details |
Show advanced information. |
--ids=<numbers...> |
Filter by resource ID. |
Example
resources network list --details
Enabling and disabling iSCSI on an IP
Turn on iSCSI on the IP(s) you want iSCSI initiators to be able to reach. An IP has to actually exist on one of the system's NICs before you can enable iSCSI on it.
Using the web interface
- Open Inventory > Resources > Network.
- Select Enable iSCSI (or Disable iSCSI).
- Under IP Selection, choose the IP(s).
- Confirm.
Using the CLI
resources network iscsi add --ips=<ip...>
resources network iscsi remove --ips=<ip...> [--force]
| Option | Description |
|---|---|
--ips=<ip...> |
The IPs to enable/disable iSCSI traffic on. |
--force |
(remove only) Skip the confirmation prompt. |
Examples
Enable iSCSI on two IPs:
resources network iscsi add --ips 10.10.10.11,10.10.10.12
Disable iSCSI on an IP no longer used by any host:
resources network iscsi remove --ips 10.10.10.12 --force
Listing iSCSI-enabled IPs
A quick view of exactly which IPs, on which nodes, currently have iSCSI enabled —— useful when connecting a new host and you need to know which target IPs to point it at.
Using the web interface
Open Inventory > Resources > Network and filter the view to iSCSI-enabled IPs.
Using the CLI
resources network iscsi list
Example
resources network iscsi list
Enabling and disabling NVMeOF on an IP
This is the NVMeOF equivalent of the iSCSI commands above: it turns NVMeOF traffic on or off on a specific IP, for a specific port, over a specific transport. Unlike iSCSI, NVMeOF has two transport options —— RDMA and TCP —— and you enable/disable them independently, so the same IP could have RDMA enabled on one port and TCP on another.
Using the web interface
- Open Inventory > Resources > Network.
- Select Enable/Disable NVMeOF.
- Under IP Selection, choose the IP, and fill in the port and transport (RDMA or TCP).
- Confirm.
Using the CLI
resources network nvmeof edit --ip=<ip> --port=<port> --enable|--disable --rdma|--tcp
| Option | Description |
|---|---|
--ip=<ip> |
The IP address to enable/disable NVMeOF traffic on. |
--port=<port> |
The port to enable/disable NVMeOF traffic on. |
--enable |
Enable NVMeOF traffic. |
--disable |
Disable NVMeOF traffic. |
--rdma |
Use RDMA as the transport for NVMeOF traffic. |
--tcp |
Use TCP as the transport for NVMeOF traffic. |
Examples
Enable NVMeOF over TCP on port 4420:
resources network nvmeof edit --ip 10.10.10.21 --port 4420 --enable --tcp
Disable NVMeOF over RDMA on the same IP/port:
resources network nvmeof edit --ip 10.10.10.21 --port 4420 --disable --rdma
Listing NVMeOF-enabled IPs
Using the web interface
Open Inventory > Resources > Network and filter the view to NVMeOF-enabled IPs.
Using the CLI
resources network nvmeof list
Example
resources network nvmeof list
Testing network connectivity (ping)
Before pointing a host at a new IP —— or when troubleshooting a connectivity problem —— you can run a ping test from every node in the system out to a target IP. The result includes a regular ping as well as MTU-specific pings, which is a quick way to confirm a jumbo-frame path is actually working end to end, not just that the link is up.
Using the web interface
Open Inventory > Resources > Network, and use the Ping action, entering the target IP under IP Selection.
Using the CLI
resources network ping --ip=<ip>
| Option | Description |
|---|---|
--ip=<ip> |
The IP address to ping. |
Example
resources network ping --ip 10.10.10.100
Next: NVMeOF Enclosures —— connecting to external NVMeOF-attached drive enclosures.
See also: Drives