Our of our CentOS7 VM (running on a HyperV 2012R2 node) is having some networking issues when rebooting.
Our "eth0" device isn't being brought up automatically; we need to log into the VM through console first and then do a network restart.
We're not using NetworkManager, but are using the old network service.
Here is our current eth0 configuration:
Code: Select all
# cat /etc/sysconfig/network-scripts/ifcfg-eth0
TYPE="Ethernet"
NM_CONTROLLED="no"
BOOTPROTO="none"
DEFROUTE="yes"
NAME="eth0"
DEVICE="eth0"
ONBOOT="yes"
HWADDR=00:15:5D:9E:AA:0B
IPADDR="HIDDEN..."
PREFIX="27"
GATEWAY="HIDDEN..."
DNS1="HIDDEN..."
DOMAIN="HIDDEN..."
Code: Select all
Jun 26 00:29:59 del-client-0009-02 network: Bringing up interface eth0: ERROR : [/etc/sysconfig/network-scripts/ifup-eth] Device eth0 does not seem to be present, delaying initialization.
Jun 26 00:30:00 del-client-0009-02 /etc/sysconfig/network-scripts/ifup-eth: Device eth0 does not seem to be present, delaying initialization.
Jun 26 00:30:01 del-client-0009-02 network: Bringing up interface eth0: ERROR : [/etc/sysconfig/network-scripts/ifup-eth] Device eth0 does not seem to be present, delaying initialization.
Jun 26 00:30:01 del-client-0009-02 /etc/sysconfig/network-scripts/ifup-eth: Device eth0 does not seem to be present, delaying initialization.
Jun 26 00:30:10 del-client-0009-02 cpipv6: STDERR: Device "eth0" does not exist.y
Jun 26 00:30:46 del-client-0009-02 network: Bringing up interface eth0: [ OK ]
Code: Select all
# ip -s l
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
RX: bytes packets errors dropped overrun mcast
100742 946 0 0 0 0
TX: bytes packets errors dropped carrier collsns
100742 946 0 0 0 0
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DEFAULT qlen 1000
link/ether 00:15:5d:9e:aa:0b brd ff:ff:ff:ff:ff:ff
RX: bytes packets errors dropped overrun mcast
746422 9161 0 273 0 0
TX: bytes packets errors dropped carrier collsns
6521087 3398 0 0 0 0
Any ideas what might be causing the issue ?
Thanks,