I finally had to look into udev a little bit today. I had made some modifications to a RHEL6 guest I have in VMWare ESXi. My trouble started when I converted the storage from thick to thin, due to limited space. I am still not sure why would have caused an issue with network devices, but it did. I ended up with a eth1 device instead of the eth0 device I had previously. I tried removing all the interfaces via vSphere and then adding one, but this only created eth2.<\/p>\n
To resolve the issue, I needed to modify the appropriate udev rules. The rule files are located in \/etc\/udev\/rules.d. The file that contained the network interface information was in the 70-persistent-net.rules file.<\/p>\n
My \/etc\/udev\/rules.d\/70-persistent-net.rules contained the following:<\/p>\n
# This file was automatically generated by the \/lib\/udev\/write_net_rules
\n# program, run by the persistent-net-generator.rules rules file.
\n#
\n# You can modify it, as long as you keep each rule on a single
\n# line, and change only the value of the NAME= key.<\/p>\n
# PCI device 0x15ad:0x07b0 (vmxnet3) (custom name provided by external tool)
\nSUBSYSTEM==”net”, ACTION==”add”, DRIVERS==”?*”, ATTR{address}==”00:0c:29:9a:99:76″, ATTR{type}==”1″, KERNEL==”eth*”, NAME=”eth0″<\/p>\n
# PCI device 0x15ad:0x07b0 (vmxnet3)
\nSUBSYSTEM==”net”, ACTION==”add”, DRIVERS==”?*”, ATTR{address}==”00:0c:29:70:fa:e5″, ATTR{type}==”1″, KERNEL==”eth*”, NAME=”eth1″<\/p>\n
# PCI device 0x8086:0x100f (e1000) (custom name provided by external tool)
\nSUBSYSTEM==”net”, ACTION==”add”, DRIVERS==”?*”, ATTR{address}==”00:0c:29:70:fa:e5″, ATTR{type}==”1″, KERNEL==”eth*”, NAME=”eth0″<\/p>\n
# PCI device 0x15ad:0x07b0 (vmxnet3)
\nSUBSYSTEM==”net”, ACTION==”add”, DRIVERS==”?*”, ATTR{address}==”00:0c:29:70:fa:ef”, ATTR{type}==”1″, KERNEL==”eth*”, NAME=”eth2″<\/p>\n
I simply removed all eth1 and eth2 and the eth0 (vmxnet3) entries, and rebooted. This took care of the issue.<\/p>\n","protected":false},"excerpt":{"rendered":"
I finally had to look into udev a little bit today. I had made some modifications to a RHEL6 guest I have in VMWare ESXi. My trouble started when I converted the storage from thick to thin, due to limited space. I am still not sure why would have caused an issue with network devices, [&hellip<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[3],"tags":[153,146,157],"class_list":["post-482","post","type-post","status-publish","format-standard","hentry","category-documentation","tag-esxi","tag-rhel6","tag-udev"],"share_on_mastodon":{"url":"","error":""},"_links":{"self":[{"href":"https:\/\/jim-zimmerman.com\/index.php?rest_route=\/wp\/v2\/posts\/482","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/jim-zimmerman.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/jim-zimmerman.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/jim-zimmerman.com\/index.php?rest_route=\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/jim-zimmerman.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=482"}],"version-history":[{"count":1,"href":"https:\/\/jim-zimmerman.com\/index.php?rest_route=\/wp\/v2\/posts\/482\/revisions"}],"predecessor-version":[{"id":483,"href":"https:\/\/jim-zimmerman.com\/index.php?rest_route=\/wp\/v2\/posts\/482\/revisions\/483"}],"wp:attachment":[{"href":"https:\/\/jim-zimmerman.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=482"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/jim-zimmerman.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=482"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/jim-zimmerman.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=482"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}