If you see: -
Shutting down loopback interface: [ OK ]
Setting network parameters: [ OK ]
Bringing up loopback interface: [ OK ]
Bringing up interface eth0: Device eth0 has different MAC address than expected, ignoring.
[FAILED]
then you may be seeing the same problem as me; am using a prebuilt VMware image of Red Hat Enterprise Linux (RHEL), where my colleague had hard-coded the MAC address of his virtual Ethernet adapter into the configuration.
The solution is simple - edit /etc/sysconfig/network-scripts/ifcfg-eth0 and remove the line: -
HWADDR=00:0C:29:2E:C9:6A
Alternatively, use the graphical network configuration tool to do the same.
Bonne chance
Geeking in technology since 1985, with IBM Development, focused upon Docker and Kubernetes on the IBM Z LinuxONE platform In the words of Dr Cathy Ryan, "If you don't write it down, it never happened". To paraphrase one of my clients, "Every day is a school day". I do, I learn, I share. The postings on this site are my own and don’t necessarily represent IBM’s positions, strategies or opinions. Remember, YMMV
Subscribe to:
Post Comments (Atom)
Grokking grep
A colleague was tinkering with grep and, thanks to him, I discovered a bit more about the trusty little utility. I had not really explored ...
-
After an unscheduled reboot of the VMs that host my K8s cluster, I was struggling to work out why the kubelet wasn't starting properly...
-
I hit a wee snag earlier today, whilst attempting to unpack some IBM software on my NAS. Being a command-line junkie, I'd SSH'd into...
-
I've just spent ~1 hour trying to get a pair of Powerline adapters to .... pair. This involved pressing a "Pair" button on one...
2 comments:
Thanks for the tip. I used the graphical Network Configuration tool to modify this entry, instead of removing it: click Edit, then Hardware tabs, and click on the Probe button next to the "Bind to MAC address" entry.
Chris.
Thank you for making your post available. It was enough to help me diagnose and fix my problem.
Post a Comment