PetaSAN 4-Node: Inconsistent MGMT NIC Names - No Ping After Rename
Ramadass K
13 Posts
December 22, 2025, 8:34 amQuote from Ramadass K on December 22, 2025, 8:34 amHi Team,
We are going to deploy a 4‑node PetaSAN cluster. We plan to provision 10 Gb links for iSCSI, backend, NFS, and S3 traffic, and 1 Gb links for management.
On these 4 nodes, the network interface names are not consistent after the OS installation. We need to rename the Ethernet ports used for the management interface, but after changing the management interface name the management IP is no longer reachable (no ping).
During the OS deployment, we selected an interface name for management, but now it needs to be changed. Is it possible to change the management interface name later? When using the PetaSAN “Interface Naming” option, the interface name changes on the node, but after the change the management IP is not working (no connectivity).
NODE1 -Ethernet port name
present cable connected
Changes
NODE 2 -Ethernet port name
Need Changes
NODE3 -Ethernet port name
Changes
NODE4 -Ethernet port name
Changes
eth0
BCK
eth2
eth0
MGMT
eth0
MGMT
eth0 -PRIMARY
MGMT
eth1
ISCSI -1
eth3
eth1
BCK
eth2
eth1-PRIMARY
MGMT
eth1
MGMT
eth2
MGMT
eth0
eth2 PRIMARY
MGMT
eth1
eth2
BCK
eth2
eth3
MGMT -PRIMARY
eth1
eth3
ISCSI-1
eth3
ISCSI-1
eth3
eth4
eth4
eth4
eth4
BCK
eth2
eth5
eth5
eth5
eth5
ISCSI-1
eth3
eth6
BCK
eth6
BCK
eth6
BCK
eth6
BCK
eth7
ISCSI-2
eth7
ISCSI-2
eth7
ISCSI-2
eth7
ISCSI-2
Hi Team,
We are going to deploy a 4‑node PetaSAN cluster. We plan to provision 10 Gb links for iSCSI, backend, NFS, and S3 traffic, and 1 Gb links for management.
On these 4 nodes, the network interface names are not consistent after the OS installation. We need to rename the Ethernet ports used for the management interface, but after changing the management interface name the management IP is no longer reachable (no ping).
During the OS deployment, we selected an interface name for management, but now it needs to be changed. Is it possible to change the management interface name later? When using the PetaSAN “Interface Naming” option, the interface name changes on the node, but after the change the management IP is not working (no connectivity).
NODE1 -Ethernet port name
present cable connected
Changes
NODE 2 -Ethernet port name
Need Changes
NODE3 -Ethernet port name
Changes
NODE4 -Ethernet port name
Changes
eth0
BCK
eth2
eth0
MGMT
eth0
MGMT
eth0 -PRIMARY
MGMT
eth1
ISCSI -1
eth3
eth1
BCK
eth2
eth1-PRIMARY
MGMT
eth1
MGMT
eth2
MGMT
eth0
eth2 PRIMARY
MGMT
eth1
eth2
BCK
eth2
eth3
MGMT -PRIMARY
eth1
eth3
ISCSI-1
eth3
ISCSI-1
eth3
eth4
eth4
eth4
eth4
BCK
eth2
eth5
eth5
eth5
eth5
ISCSI-1
eth3
eth6
BCK
eth6
BCK
eth6
BCK
eth6
BCK
eth7
ISCSI-2
eth7
ISCSI-2
eth7
ISCSI-2
eth7
ISCSI-2
admin
3,054 Posts
December 25, 2025, 8:38 pmQuote from admin on December 25, 2025, 8:38 pmBonds/vlans/interfaces are defined in
/opt/petasan/config/cluster_info.json
ip for current node are in
/opt/petasan/config/node_info.json
OS/Ubuntu needs to boot with management interface defined, this is in
/etc/network/interfaces
To select/change name of interface ethX to match specific interface (via hardware mac address, pci slot, vendor name/model) use the Interface Naming menu on the node blue menu console menu.
To view existing network configuration for a node using Wed ui, use the Node List menu
Bonds/vlans/interfaces are defined in
/opt/petasan/config/cluster_info.json
ip for current node are in
/opt/petasan/config/node_info.json
OS/Ubuntu needs to boot with management interface defined, this is in
/etc/network/interfaces
To select/change name of interface ethX to match specific interface (via hardware mac address, pci slot, vendor name/model) use the Interface Naming menu on the node blue menu console menu.
To view existing network configuration for a node using Wed ui, use the Node List menu
PetaSAN 4-Node: Inconsistent MGMT NIC Names - No Ping After Rename
Ramadass K
13 Posts
Quote from Ramadass K on December 22, 2025, 8:34 amHi Team,
We are going to deploy a 4‑node PetaSAN cluster. We plan to provision 10 Gb links for iSCSI, backend, NFS, and S3 traffic, and 1 Gb links for management.
On these 4 nodes, the network interface names are not consistent after the OS installation. We need to rename the Ethernet ports used for the management interface, but after changing the management interface name the management IP is no longer reachable (no ping).
During the OS deployment, we selected an interface name for management, but now it needs to be changed. Is it possible to change the management interface name later? When using the PetaSAN “Interface Naming” option, the interface name changes on the node, but after the change the management IP is not working (no connectivity).
NODE1 -Ethernet port name present cable connected Changes NODE 2 -Ethernet port name Need Changes NODE3 -Ethernet port name Changes NODE4 -Ethernet port name Changes eth0 BCK eth2 eth0 MGMT eth0 MGMT eth0 -PRIMARY MGMT eth1 ISCSI -1 eth3 eth1 BCK eth2 eth1-PRIMARY MGMT eth1 MGMT eth2 MGMT eth0 eth2 PRIMARY MGMT eth1 eth2 BCK eth2 eth3 MGMT -PRIMARY eth1 eth3 ISCSI-1 eth3 ISCSI-1 eth3 eth4 eth4 eth4 eth4 BCK eth2 eth5 eth5 eth5 eth5 ISCSI-1 eth3 eth6 BCK eth6 BCK eth6 BCK eth6 BCK eth7 ISCSI-2 eth7 ISCSI-2 eth7 ISCSI-2 eth7 ISCSI-2
Hi Team,
We are going to deploy a 4‑node PetaSAN cluster. We plan to provision 10 Gb links for iSCSI, backend, NFS, and S3 traffic, and 1 Gb links for management.
On these 4 nodes, the network interface names are not consistent after the OS installation. We need to rename the Ethernet ports used for the management interface, but after changing the management interface name the management IP is no longer reachable (no ping).
During the OS deployment, we selected an interface name for management, but now it needs to be changed. Is it possible to change the management interface name later? When using the PetaSAN “Interface Naming” option, the interface name changes on the node, but after the change the management IP is not working (no connectivity).
| NODE1 -Ethernet port name | present cable connected | Changes | NODE 2 -Ethernet port name | Need Changes | NODE3 -Ethernet port name | Changes | NODE4 -Ethernet port name | Changes | ||||
| eth0 | BCK | eth2 | eth0 | MGMT | eth0 | MGMT | eth0 -PRIMARY | MGMT | ||||
| eth1 | ISCSI -1 | eth3 | eth1 | BCK | eth2 | eth1-PRIMARY | MGMT | eth1 | MGMT | |||
| eth2 | MGMT | eth0 | eth2 PRIMARY | MGMT | eth1 | eth2 | BCK | eth2 | ||||
| eth3 | MGMT -PRIMARY | eth1 | eth3 | ISCSI-1 | eth3 | ISCSI-1 | eth3 | |||||
| eth4 | eth4 | eth4 | eth4 | BCK | eth2 | |||||||
| eth5 | eth5 | eth5 | eth5 | ISCSI-1 | eth3 | |||||||
| eth6 | BCK | eth6 | BCK | eth6 | BCK | eth6 | BCK | |||||
| eth7 | ISCSI-2 | eth7 | ISCSI-2 | eth7 | ISCSI-2 | eth7 | ISCSI-2 |
admin
3,054 Posts
Quote from admin on December 25, 2025, 8:38 pmBonds/vlans/interfaces are defined in
/opt/petasan/config/cluster_info.json
ip for current node are in
/opt/petasan/config/node_info.json
OS/Ubuntu needs to boot with management interface defined, this is in
/etc/network/interfaces
To select/change name of interface ethX to match specific interface (via hardware mac address, pci slot, vendor name/model) use the Interface Naming menu on the node blue menu console menu.
To view existing network configuration for a node using Wed ui, use the Node List menu
Bonds/vlans/interfaces are defined in
/opt/petasan/config/cluster_info.json
ip for current node are in
/opt/petasan/config/node_info.json
OS/Ubuntu needs to boot with management interface defined, this is in
/etc/network/interfaces
To select/change name of interface ethX to match specific interface (via hardware mac address, pci slot, vendor name/model) use the Interface Naming menu on the node blue menu console menu.
To view existing network configuration for a node using Wed ui, use the Node List menu