

If using NetworkManager:įind the name of the existing network configuration profile using nmcli under the NAME column. The DEVICE parameter value should be updated to match the new interface name. The ifcfg files in the /etc/sysconfig/network-scripts/ directory can be modified directly. In the example below, the current interface name is ens192: ~]# ip linkġ: lo: mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT Please see the Root Cause section of this article for steps to identify what the new name will be before the change takes place Update the network configuration to reflect the interface name change:įind the new interface name with the ip command. The instructions which follow assume the OS is already using the changed named. Note that the DVD ISO images will not be updated to include this errata update as most virtual environments are using some other network repository for installs that are updated to include errata updates. Note this update will not fix systems which have already been updated to 7.3. Please see RHBA-2016:2698 - Bug Fix Advisory. With this newer systemd release, affected interfaces are identified upon the package install and a udev rule is automatically generated so the renaming issue is entirely avoided. This issue can be avoided by updating installation repositories to include the systemd-219-30.el7_3.6 or later package. and are Red Hat Enterprise Linux 7.0, 7.1, or 7.2 virtual guests upgrading to Red Hat Enterprise Linux 7.3.This is further explained on the Red Hat TAM Blog Red Hat Enterprise Linux 7.3: Achieving persistent and consistent network interface naming in VMware environments. An update to systemd in RHEL 7.3 was made to provide consistent device names but can result in a final network device name change if the virtual guest already had the long device name enoXXXXX. It was found that VMware firmware/bios reports meaningless data for the device names causing inconsistent, changing or missing network device names after reboot.

A network interface previously had a device name enoX where X > 16383 and now has an ensY style name.

