After successfully using the PBS version of the NIC pinning tool on a couple servers, I tried a PVE 8.4.x server tonight. It seemed fine for most everything except SDN was broken afterwards, showing an error state on the zone (ZoneVLAN). I found file
...thus it fails to load. Manually changing "eno1" to the new name ("nic0" in this case) doesn't seem to help. If I Apply the SDN config the invalid entry is removed but not replaced:
(Edit: same if I remove the zone from this server and re-add it)
In this configuration the zone shows as "available" however it doesn't pass traffic to/from VMs running on that server node, using that VLAN. All other VMs not using the VLAN are fine.
What is necessary to reconnect the SDN zone on this node, aside from reverting the pinned NIC names?
Of the two "sdn" files the docs mention the tool will update:
Side note, per that doc page, "It is recommended to assign a name starting with en or eth so that Proxmox VE recognizes the interface as a physical network device which can then be configured via the GUI," however the tool itself does not do this.
/etc/network/interfaces.d/sdn still referenced the old NIC name, eno1:
Code:
iface vmbr0v198
bridge_ports eno1.198 pr_vnetC...thus it fails to load. Manually changing "eno1" to the new name ("nic0" in this case) doesn't seem to help. If I Apply the SDN config the invalid entry is removed but not replaced:
Code:
iface vmbr0v198
bridge_ports pr_vnetC(Edit: same if I remove the zone from this server and re-add it)
In this configuration the zone shows as "available" however it doesn't pass traffic to/from VMs running on that server node, using that VLAN. All other VMs not using the VLAN are fine.
What is necessary to reconnect the SDN zone on this node, aside from reverting the pinned NIC names?
Of the two "sdn" files the docs mention the tool will update:
- /etc/pve/sdn/controllers.cfg - size 0
- /etc/pve/sdn/fabrics.cfg - does not exist
Side note, per that doc page, "It is recommended to assign a name starting with en or eth so that Proxmox VE recognizes the interface as a physical network device which can then be configured via the GUI," however the tool itself does not do this.
Last edited: