Management interface lost or renamed for bare metal edge node
Article ID: 374552
Updated On:
Products
Issue/Introduction
The management interface can be lost or renamed for bare metal edge nodes after the reboot, which can also happen during an upgrade
Environment
VMware NSX-T Data Center
VMware NSX
Cause
When a bare metal edge (BME) boots up, the LINUX kernel uses the MAC address of the ethernet NIC to name interfaces (e.g. eth0, eth1, eth2, etc). It saves the mapping between MAC and interface name in a file called persistent firewall rule file (/etc/udev/rules.d/70-nsx-persistent-net.rules)
Sometimes, after the reboot, the mappings may change in the persistent rule file which will result in the BME disconnection from the network.
In case the management interface is renamed, you will see entries similar to the following in nsx-syslogs before the reboot for the persistent interfaces:
2024-07-24T20:14:27.796Z #### NSX 357162 - [nsx@6876 comp="nsx-edge" subcomp="persistent-interfaces" username="root" level="INFO"] Updating existing set of net rules...
2024-07-24T20:14:27.797Z #### NSX 357162 - [nsx@6876 comp="nsx-edge" subcomp="persistent-interfaces" username="root" level="INFO"] INTERFACES: [{'name': 'eth0', 'mac': '##:##:##:44:dd:00', 'pci': '0000:##:#'}, {'name': 'eth1', 'mac': '##:##:x##44:dd:01', 'pci': '0000:##:#'}, {'name': 'eth2', 'mac': '##:##:##:44:dd:02', 'pci': '0000:##:#'}, {'name': 'eth3', 'mac': '##:##:##:44:dd:03', 'pci': '0000:##:#'}, {'name': 'eth4', 'mac': '##:##:##:68:0d:c0', 'pci': '0000:##:#'}, {'name': 'eth5', 'mac': '##:##:##:68:0d:c1', 'pci': '0000:##:#'}, {'name': 'eth6', 'mac': '##:##:##:68:0d:80', 'pci': '0000:##:#'}, {'name': 'eth7', 'mac': '##:##:##:68:0d:81', 'pci': '0000:##:#'}]
2024-07-24T20:14:27.804Z XXXX NSX 357162 - [nsx@6876 comp="nsx-edge" subcomp="persistent-interfaces" username="root" level="INFO"] Written peristent net rules to /etc/udev/rules.d/70-nsx-persistent-net.rules
After the reboot, you will see the management interface is not found anymore:
2024-07-24T20:22:18.851Z #### ifup 6878 - - Device "eth4" does not exist.2024-07-24T20:22:18.213Z #### ifup 6870 - - eth4 does not exist, unable to create eth4.39002024-07-24T20:22:18.078Z #### ifup 6828 - - run-parts: /etc/network/if-up.d/vlan exited with return code 12024-07-24T20:22:18.657Z #### ifup 2906 - - ifup: failed to bring up eth42024-07-24T20:22:18.759Z #### ifup 2906 - - ifup: could not bring up parent interface eth4
In further logs, we can see that eth4 is missing from the persistent interfaces logs, and a new interface with the same mac address mapping as that of management interface (eth4) can be observed with the name ens2f0:
2024-07-24T20:22:19.348Z #### NSX 6919 - [nsx@6876 comp="nsx-edge" subcomp="persistent-interfaces" username="root" level="INFO"] Updating existing set of net rules...
2024-07-24T20:22:19.349Z #### NSX 6919 - [nsx@6876 comp="nsx-edge" subcomp="persistent-interfaces" username="root" level="INFO"] INTERFACES: [{'name': 'ens2f0', 'mac': '##:##:##:68:0d:c0', 'pci': '0000:##:#'}, {'name': 'eth0', 'mac': '##:##:##:44:dd:00', 'pci': '0000:##:#'}, {'name': 'eth1', 'mac': '##:##:##:44:dd:01', 'pci': '0000:##:#'}, {'name': 'eth2', 'mac': '##:##:##:44:dd:02', 'pci': '0000:xx:x'}, {'name': 'eth3', 'mac': '##:##:##:44:dd:03', 'pci': '0000:##:#'}, {'name': 'eth5', 'mac': '##:##:##:68:0d:c1', 'pci': '0000:##:#'}, {'name': 'eth6', 'mac': '##:##:##:68:0d:80', 'pci': '0000:##:#'}, {'name': 'eth7', 'mac': '##:##:##:68:0d:81', 'pci': '0000:##:#'}]
Resolution
This issue is resolved in VMware NSX 4.0.1.1
Feedback
