ETH0 has wrong MAC Address after Upgrade to OVMS 3.2.6

Overview

During the installation of OVM Server 3.2.6, the eth0 NIC was started with the wrong MAC address. No TCP/IP connection was possible to and from VICTORIA.

The work around is to update the MAC address in the definition.

Status

Fixed in OVMS 3.3.1

Work Around

In /etc/sysconfig/network-scripts/ifcfg-eth0, change the following line:

HWADDR=44:37:E6:A7:34:9A

to:

HWADDR=00:1B:21:D9:A1:AE

This is the MAC address found for eth0 in /var/log/messages.

Restart the network:

service network restart

Diagnosis

Basic Diagnosis

ping 192.168.1.1 fails from VICTORIA.

Reviewing the Logs

The following logs were checked:

/var/log/messages
/root/anaconda.log

/var/log/messages

In /var/log/messages, the following messages relate to eth0 and bond0:

Dec 23 20:33:45 victoria kernel: e1000e 0000:01:00.0: eth0: (PCI Express:2.5GT/s:Width x4) 00:1b:21:d9:a1:ae

Dec 23 20:33:45 victoria kernel: e1000e 0000:01:00.0: eth0: Intel(R) PRO/1000 Network Connection

Dec 23 20:33:45 victoria kernel: e1000e 0000:01:00.0: eth0: MAC: 1, PHY: 4, PBA No: E99198-002

…

Dec 23 20:33:46 victoria kernel: bonding: bond0: setting mode to active-backup (1).

Dec 23 20:33:46 victoria kernel: bonding: bond0: Setting MII monitoring interval to 250.

Dec 23 20:33:46 victoria kernel: bonding: bond0: Note: Updating updelay (to 500) since it is a multiple of the miimon value.

Dec 23 20:33:46 victoria kernel: bonding: bond0: Note: Updating downdelay (to 500) since it is a multiple of the miimon value.

Dec 23 20:33:46 victoria kernel: bonding: bond0: Setting use_carrier to 1.

Dec 23 20:33:46 victoria kernel: bonding: bond0: Setting up delay to 500.

Dec 23 20:33:46 victoria kernel: bonding: bond0: Setting down delay to 500.

Dec 23 20:33:46 victoria kernel: bonding: bond0: Unable to set eth0 as primary slave.

/root/anaconda.log

In /root/anaconda.log, the following messages relate to eth0:

20:24:48 INFO : Network device: DEVICE=eth0

BOOTPROTO=static

BROADCAST=192.168.1.255

HWADDR=44:37:E6:A7:34:9A

IPADDR=192.168.1.100

NETMASK=255.255.255.0

NETWORK=192.168.1.0

ONBOOT=yes

Root Cause

OVM Server 3.2.6 uses the following kernel:

Linux version 2.6.39-300.32.5.el5uek (mockbuild@ca-build56.us.oracle.com) (gcc version 4.1.2 20080704 (Red Hat 4.1.2-52)) #1 SMP Mon Aug 5 11:19:15 PDT 2013

This kernel does not recognise Intel Corporation 82579LM Gigabit Network Connection, but does recognise Intel Corporation 82571EB Gigabit Ethernet Controller.

However, the kernel used for the installer recognises both types of NIC.

As did the kernel for OVM Server 3.1.1:

Linux version 2.6.39-200.1.1.el5uek (mockbuild@ca-build56.us.oracle.com) (gcc version 4.1.2 20080704 (Red Hat 4.1.2-50)) #1 SMP Thu Apr 19 18:14:07 EDT 2012