Just a quick and dirty post for my future reference.
Sometimes, the OS gets confused. Especially if there are additional lines for VMXNET.
When you run "system-config-network", eth0 should show the VMware NIC type, for example "VMXNET3"
Otherwise;
1. Remove the unnecessary lines from /etc/udev/rules.d/70-persistent-net.rules
2. Make sure the MAC address matches matches the ESXi assigned
3. Restart the services "service network restart"
4. "yum clean all" (in case cache is pointing to dead update locations)
4. yum update
Location of network configuration file: (assumption for 1st network adapter)
/etc/sysconfig/network-scripts/ifcfg-eth0
Just happy sharing nuggets. My Personal Wiki. Blog contains mostly technical stuff which may be of interest to some but mostly useful for me.
Showing posts with label Patching. Show all posts
Showing posts with label Patching. Show all posts
Tuesday, February 17, 2015
Tuesday, April 22, 2014
Heartbleed remediation for vCenter (build 1750787), ESXi (build 1746018), Web Client Integration plug-in (build 1750778), vSphere C# client (build 1746248)
Glad to report the vCenter update went without a hitch on my home lab. As aways YMMV.
![]() |
Updating to vCenter 5.5.0u1a - install in sequence following custom install. No reboot required. All other components remain the same as 5.5.0u1
|
![]() |
Versions of updated 5.5.0u1a vCenter SSO, Inventory Service, Web Client and vCenter Server.
|
![]() |
| VMware Update Manager will be restarted during installation. |
![]() |
| Web Client Integration Plugin will still have the same name as 5.5.0u1 but the build/version has been updated |
![]() | |
| vSphere Client updated to build 1746248. Not sure if it's only my home NAS that's slow but it looked like before updating, the stats and info page for ESXi hosts would not display properly. |
![]() |
| vSphere Client not displaying ESXi stats properly (before updating; could also be caused by my storage backend) |
Subscribe to:
Posts (Atom)





