Details
Description
After a reboot, the eth0 and eth1 interfaces on the dom0 host stop reporting as eth0 and eth1, and instead report as side-#eth0 and side#-eth1. Once SNMP is restarted, it returns the right names again.
Before reboot:
[nhanlon@<redacted> ~]$ snmpwalk -v2c -c <redacted> <redacted> .1.3.6.1.2.1.2.2.1.2
IF-MIB::ifDescr.1 = STRING: lo
IF-MIB::ifDescr.2 = STRING: eth0
IF-MIB::ifDescr.3 = STRING: eth1
IF-MIB::ifDescr.4 = STRING: ovs-system
IF-MIB::ifDescr.5 = STRING: xapi1
IF-MIB::ifDescr.6 = STRING: xapi2
After reboot:
[nhanlon@<redacted> ~]$ snmpwalk -v2c -c <redacted> <redacted> .1.3.6.1.2.1.2.2.1.2
IF-MIB::ifDescr.1 = STRING: lo
IF-MIB::ifDescr.2 = STRING: side-307-eth0
IF-MIB::ifDescr.3 = STRING: side-7426-eth1
IF-MIB::ifDescr.4 = STRING: ovs-system
IF-MIB::ifDescr.10 = STRING: xapi1
IF-MIB::ifDescr.11 = STRING: xapi2
IF-MIB::ifDescr.12 = STRING: xapi3
IF-MIB::ifDescr.19 = STRING: vif4.0
IF-MIB::ifDescr.21 = STRING: vif5.0
IF-MIB::ifDescr.22 = STRING: vif6.0
IF-MIB::ifDescr.27 = STRING: vif8.0
After `systemctl restart snmpd`, the snmpwalk returns the same as it did before reboot. It is extremely annoying to have to restart SNMP every time a machine is rebooted (usually due to XenServer crashing )
My suspicion is that SNMP is being started too soon after the network starts, and it hasn't finished doing whatever it does.