Configure Multiple VLANs on One Node Interface
Applies to: Hammerspace 5.3 and later.
A physical or virtual cluster that needs more than one VLAN on a single interface can only be configured that way from the CLI, after installation. One VLAN tag can be set on one interface during installation; any others are added afterwards.
| Changing cluster network configuration usually requires an outage, and often means related changes to DNS records and other cluster settings. Contact Hammerspace Support if you would like help. |
Gather this before you start:
-
IP address
-
Netmask
-
VLAN ID, sometimes called the VLAN tag
-
Interface name or ID from the node
-
Cluster administrator credentials
Create a VLAN-tagged Interface
-
Connect to the cluster over SSH with an administrative account.
-
List the cluster nodes.
Command:
node-listName: jp-nyc-anvil-1.asgard.local Type: Product Node state: MANAGED Node mode: ONLINE Management IP: 192.168.198.65/24 SW version: 5.0.0-295 -
List the interfaces on the node you want to change.
Command:
interface-list --node-name jp-nyc-anvil-1.asgard.localName: ens256 IP: [] Roles: [] Name: ens224 IP: [10.200.10.65/24] Roles: [DATA, MGMT] -
Create the tagged interface, giving it the node name, the interface name or ID, the roles it takes (
mgmt,data,ha, orportal), and the VLAN ID.Command:
interface-create --node-name jp-nyc-anvil-1.asgard.local --interface-name ens224 \ --ip 192.168.198.65/24 --roles mgmt --vlan-id 4001Name: ens224.4001 Vlan ID: 4001 IP: [192.168.198.65/24] Roles: [MGMT] MAC: 00:50:56:ad:ec:0e Link speed: 10 Gbps MTU: 1500The underlying interface may already carry an untagged IP address, or may be unconfigured. Either works. -
Repeat for every tagged interface you need, on every node in the cluster.
Once the interfaces exist, check whether anything else needs to change — DNS records pointing at the cluster, new virtual IP addresses for Anvil or DSX networks, and so on. Contact Hammerspace Support if you are unsure.
Run any CLI command with --help for its full syntax.
|