RHEL30 / tg3 / bonding / miimon

Sigbjørn Strømmen sigbjorn.strommen at roxar.com
Tue May 11 11:23:01 CDT 2004


I'm setting up a PE2650 with RHEL30ES, kernel=2.4.21-9.0.3.ELsmp
and latest updates.

I have configured the NICs with ALB using standard tg3 and bonding
driver.

Although I do get the network up and running there are some
problems:

1. Setting miimon=100 is not recognized
2. bond0 is forced to 100Mbps FD although eth0 and eth1 are 1000Mbps
3. Error messages in logs no matter what bonding mode used



/etc/modules.conf looks like this:

alias bond0 bonding
options bond0 miimon=100 mode=balance-alb
probeall bond0 eth0 eth1 bonding
alias eth0 tg3
alias eth1 tg3


ifcfg-eth[01] looks like this:
----------
DEVICE=eth0
USERCTL=no
BOOTPROTO=none
HWADDR=00:0D:56:6F:D9:44
ONBOOT=yes
MASTER=bond0
SLAVE=yes
PEERDNS=no
TYPE=Ethernet
----------

ifcfg-bond0 looks like this:
----------
DEVICE=bond0
BOOTPROTO=none
ONBOOT=yes
NETWORK=10.10.10.0
NETMASK=255.255.255.0
IPADDR=10.10.10.11
BROADCAST=10.10.10.255
GATEWAY=10.10.10.2
USERCTL=no
----------

Logfile entries:
-----

kernel: FDC 0 is a National Semiconductor PC87306
kernel: tg3.c:v2.3 (November 5, 2003)
kernel: eth0: Tigon3 [partno(BCM95703A30) rev 1002 PHY(5703)] (PCIX:133MHz:64-bit) 10/100/1000BaseT Ethernet 00:0d:56:6f:d9:44
kernel: eth1: Tigon3 [partno(BCM95703A30) rev 1002 PHY(5703)] (PCIX:133MHz:64-bit) 10/100/1000BaseT Ethernet 00:0d:56:6f:d9:46
last message repeated 2 times
kernel: ip_tables: (C) 2000-2002 Netfilter core team
kernel: tg3.c:v2.3 (November 5, 2003)
kernel: eth0: Tigon3 [partno(BCM95703A30) rev 1002 PHY(5703)] (PCIX:133MHz:64-bit) 10/100/1000BaseT Ethernet 00:0d:56:6f:d9:44
kernel: eth1: Tigon3 [partno(BCM95703A30) rev 1002 PHY(5703)] (PCIX:133MHz:64-bit) 10/100/1000BaseT Ethernet 00:0d:56:6f:d9:46
kernel: bonding.c:v2.2.14 (June 30, 2003)
kernel: bonding_init(): either miimon or arp_interval and arp_ip_target module parameters must be specified, otherwise bonding will not detect link failures! see bonding.txt for details.
kernel: bond0 registered without MII link monitoring, in load balancing (round-robin) mode.
kernel: bond0 registered without ARP monitoring
kernel: bond_enslave(): failed to get speed/duplex from eth0, speed forced to 100Mbps, duplex forced to Full.
kernel: bond0: enslaving eth0 as an active interface with an up link.
kernel: bond_enslave(): failed to get speed/duplex from eth1, speed forced to 100Mbps, duplex forced to Full.
kernel: bond0: enslaving eth1 as an active interface with an up link.
kernel: ip_tables: (C) 2000-2002 Netfilter core team
kernel: tg3: eth0: Link is up at 1000 Mbps, full duplex.
kernel: tg3: eth0: Flow control is off for TX and off for RX.
kernel: tg3: eth1: Link is up at 1000 Mbps, full duplex.
kernel: tg3: eth1: Flow control is off for TX and off for RX.



Any hints?
Will I have to switch over to bcm5700 & BASP, or is there a way
to configure the tg3/bonding setup to avoid these errors?





-Sigbjorn


DISCLAIMER:
This message contains information that may be privileged or confidential and is the property of the Roxar Group. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorised to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message.




More information about the Linux-PowerEdge mailing list