Appliance Does Not Come Online After NIC is Replaced

Updated

Symptom

HyperScale appliance may not come online after replacing the NICs (Network Interface Card).

The SOS report will display that the HWADDR (Hardware Address) does not match the NIC.

Resolution

Check the MAC address in /etc/udev/rules.d/70-persistent-net.rules file with the output provided by the ip a |grep -B1 ether command and make sure that they match. (If it does not match, update the MAC address in the /etc/udev/rules.d/70-persistent-net.rules file.)

For example, the MAC address for enpsf1 in the following sample output is 3c:ec:ef:1a:56:1e.

# cat /etc/udev/rules.d/70-persistent-net.rules
ACTION=="add", SUBSYSTEM=="net", DRIVERS=="?*", ATTR{type}=="1", ATTR{address}=="3c:ec:ef:1a:56:1e", ATTR{dev_id}=="0x0", KERNEL=="eth*", NAME="enpsf1"
ACTION=="add", SUBSYSTEM=="net", DRIVERS=="?*", ATTR{type}=="1", ATTR{address}=="3c:ec:ef:1a:56:1f", ATTR{dev_id}=="0x0", KERNEL=="eth*", NAME="enpsf2"
ACTION=="add", SUBSYSTEM=="net", DRIVERS=="?*", ATTR{type}=="1", ATTR{address}=="3c:ec:ef:3d:bb:40", ATTR{dev_id}=="0x0", KERNEL=="eth*", NAME="enpsf3"
ACTION=="add", SUBSYSTEM=="net", DRIVERS=="?*", ATTR{type}=="1", ATTR{address}=="3c:ec:ef:3d:bb:41", ATTR{dev_id}=="0x0", KERNEL=="eth*", NAME="enpsf4"
ACTION=="add", SUBSYSTEM=="net", DRIVERS=="?*", ATTR{type}=="1", ATTR{address}=="3c:ec:ef:3d:c5:e0", ATTR{dev_id}=="0x0", KERNEL=="eth*", NAME="enpsf5"
ACTION=="add", SUBSYSTEM=="net", DRIVERS=="?*", ATTR{type}=="1", ATTR{address}=="3c:ec:ef:3d:c5:e1", ATTR{dev_id}=="0x0", KERNEL=="eth*", NAME="enpsf6"
You have new mail in /var/spool/mail/root
    

# ip a |grep -B 1 ether
2: enpsf1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether 3c:ec:ef:1a:56:1e brd ff:ff:ff:ff:ff:ff
--
3: enpsf2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether 3c:ec:ef:1a:56:1f brd ff:ff:ff:ff:ff:ff
--
4: enpsf3: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc mq master bond1 state UP group default qlen 1000
    link/ether 3c:ec:ef:3d:bb:40 brd ff:ff:ff:ff:ff:ff
5: enpsf4: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc mq master bond2 state UP group default qlen 1000
    link/ether 3c:ec:ef:3d:bb:41 brd ff:ff:ff:ff:ff:ff
6: enpsf5: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc mq master bond1 state UP group default qlen 1000
    link/ether 3c:ec:ef:3d:c5:e0 brd ff:ff:ff:ff:ff:ff
7: enpsf6: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc mq master bond2 state UP group default qlen 1000
    link/ether 3c:ec:ef:3d:c5:e1 brd ff:ff:ff:ff:ff:ff
    
In case of Rocky Linux for HyperScale, the file name is /etc/udev/rules.d/70-custom-ifnames.rules instead of /etc/udev/rules.d/70-persistent-net.rules.

The following are the contents of the /etc/udev/rules.d/70-custom-ifnames.rules file:

# cat /etc/udev/rules.d/70-custom-ifnames.rules
ACTION=="add", SUBSYSTEM=="net", DRIVERS=="?*", ATTR{type}=="1", ATTR{address}=="7c:c2:55:41:13:b0", NAME="enpsf1"
ACTION=="add", SUBSYSTEM=="net", DRIVERS=="?*", ATTR{type}=="1", ATTR{address}=="7c:c2:55:41:13:b1", NAME="enpsf2"
ACTION=="add", SUBSYSTEM=="net", DRIVERS=="?*", ATTR{type}=="1", ATTR{address}=="7c:c2:55:41:13:ae", NAME="enpsf3"
ACTION=="add", SUBSYSTEM=="net", DRIVERS=="?*", ATTR{type}=="1", ATTR{address}=="7c:c2:55:41:13:af", NAME="enpsf4"
ACTION=="add", SUBSYSTEM=="net", DRIVERS=="?*", ATTR{type}=="1", ATTR{address}=="7c:c2:55:26:05:aa", NAME="enpsf5"
ACTION=="add", SUBSYSTEM=="net", DRIVERS=="?*", ATTR{type}=="1", ATTR{address}=="7c:c2:55:26:05:ab", NAME="enpsf6"
ACTION=="add", SUBSYSTEM=="net", DRIVERS=="?*", ATTR{type}=="1", ATTR{address}=="7c:c2:55:26:05:a8", NAME="enpsf7"
ACTION=="add", SUBSYSTEM=="net", DRIVERS=="?*", ATTR{type}=="1", ATTR{address}=="7c:c2:55:26:05:a9", NAME="enpsf8"
    

Was this page helpful?