topic Re: Fedore Core 5 on DL360 G5 - problem with logical network interfaces in Operating System - Linux

Fedore Core 5 on DL360 G5 - problem with logical network interfaces

zflee — Wed, 30 May 2007 11:34:11 GMT

I have the above system setup and the MAC addresses of network interfaces do not appear to be attached orderly to the interface eth0-3. Could anyone offer me some suggestions? See the following screenshot:

[root@system1 ~]# ip link show
1: lo: mtu 16436 qdisc noqueue
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth0: mtu 1500 qdisc noop qlen 1000
link/ether 00:17:08:7e:d4:46 brd ff:ff:ff:ff:ff:ff
3: eth3: mtu 1500 qdisc pfifo_fast qlen 1000
link/ether 00:17:08:7e:d4:47 brd ff:ff:ff:ff:ff:ff
4: eth2: mtu 1500 qdisc noop qlen 1000
link/ether 00:1b:78:03:9d:f2 brd ff:ff:ff:ff:ff:ff
5: dev1370: mtu 1500 qdisc noop qlen 1000
link/ether 00:1b:78:03:9d:ea brd ff:ff:ff:ff:ff:ff
6: sit0: mtu 1480 qdisc noop
link/sit 0.0.0.0 brd 0.0.0.0

[root@system1 ~]# cat /etc/modprobe.conf
alias eth0 bnx2
alias eth1 bnx2
alias eth2 e1000
alias eth3 e1000
alias scsi_hostadapter cciss

By the way, HWADDR of ifcfg-eth* file appeared to have the the right order of MAC addresses.

[root@system1 ~]# cat /etc/sysconfig/network-scripts/ifcfg-eth*
# Broadcom Corporation NetXtreme II BCM5708 Gigabit Ethernet
DEVICE=eth0
BOOTPROTO=dhcp
HWADDR=00:1B:78:03:9D:F2
ONBOOT=no
# Broadcom Corporation NetXtreme II BCM5708 Gigabit Ethernet
DEVICE=eth1
BOOTPROTO=dhcp
HWADDR=00:1B:78:03:9D:EA
ONBOOT=no
# Intel Corporation 82571EB Gigabit Ethernet Controller
DEVICE=eth2
BOOTPROTO=dhcp
HWADDR=00:17:08:7E:D4:46
ONBOOT=no
# Intel Corporation 82571EB Gigabit Ethernet Controller
DEVICE=eth3
BOOTPROTO=static
HWADDR=00:17:08:7E:D4:47
ONBOOT=yes
IPADDR=192.168.130.22
MASK=255.255.255.192
GATEWAY=192.168.130.62
TYPE=Ethernet

Re: Fedore Core 5 on DL360 G5 - problem with logical network interfaces

Ivan Ferreira — Wed, 30 May 2007 12:11:03 GMT

Interesting, what is the output of ifconfig -a?

I think that one problem could be that the ONBOOT is set to NO on most interfaces, I would like to know if the device set ONBOOT=yes (eth3) is assigned the IP requiested.

Re: Fedore Core 5 on DL360 G5 - problem with logical network interfaces

Colin Topliss — Sat, 02 Jun 2007 04:30:49 GMT

You might also want to check to see if your interface names are being changed under udev (couldn't verify for sure - not running FC5 on any of my systems anymore).

Take a look under /etc/udev/rules.d for something similiar to the following (taken from a SuSE system, but this ability does also exist under RHEL4).

# This rules are autogenerated from /lib/udev/rename_netiface.
# But you can modify them, but make sure that you don't use an interface name
# twice. Also add such interface name rules only in this rules file. Otherwise
# rename_netiface will create wrong rules for new interfaces.
# It is safe to delete a rule, as long as you did not disable automatic rule
# generation. Only if all interfaces get a rule the renaming will work
# flawlessly. See also /etc/udev/rules.d/31-net_create_names.rules.
#
# Read /usr/share/doc/packages/sysconfig/README.Persistent_Interface_Names for
# further information.
#
# Use only a-z, A-Z and 0-9 for interface names!
#
SUBSYSTEM=="net", ACTION=="add", SYSFS{address}=="00:14:c2:62:44:89", IMPORT="/lib/udev/rename_netiface %k eth0"
SUBSYSTEM=="net", ACTION=="add", SYSFS{address}=="00:14:c2:62:44:88", IMPORT="/lib/udev/rename_netiface %k eth1"

Col

Re: Fedore Core 5 on DL360 G5 - problem with logical network interfaces

Don Vanco - Linux Ninja — Sat, 02 Jun 2007 05:26:27 GMT

Possible stupid question (but your output doesn't show this)
IS the ifcfg-eth3 file the one that contains the line "DEVICE=eth3"??
The name of the file has to match the DEVICE enumeration if that's the order you expect to see them enumerated.

It looks that way based on your use of "cat", but it's worth asking....

You can name the file "ifcfg-bob" if you want, what matters is the DEVICE and HWADDR lines.

FC5 is a little old for a G5 - have you at least updated it (kernel mainly) via the working connection?