RHEL30 / tg3 / bonding / miimon

Matthew_Wygant@Dell.com Matthew_Wygant at Dell.com
Thu May 13 19:00:01 CDT 2004


You need to set the miimon setting in the /etc/modules.conf file.  

miimon=100

It looks to be erroring on not having this monitor setting.  You can look in the /usr/src/linux-2.4/Documentation/networking/bonding.txt file for proper syntax of the bonding.o options.  

-mattw

-----Original Message-----
From: linux-poweredge-admin at Dell.com [mailto:linux-poweredge-admin at Dell.com] On Behalf Of Boley, Steve
Sent: Thursday, May 13, 2004 2:53 PM
To: sigbjorn.strommen at roxar.com
Cc: linux-poweredge at Dell.com
Subject: RE: RHEL30 / tg3 / bonding / miimon


Grab the 7.x ver from bcom and it was written
to work with ethtool and mii-tool and will fix
this problem.
Steve 

-----Original Message-----
From: Sigbjørn Strømmen [mailto:sigbjorn.strommen at roxar.com] 
Sent: Thursday, May 13, 2004 2:52 PM
To: Boley, Steve
Subject: RE: RHEL30 / tg3 / bonding / miimon

Thanks.

I had really hoped to avoid the broadcom drivers.
This server will be a very central fileserver for us, and having binary, kernel-specific drivers complicates things for future maintenance if somebody else then myself is doing work on it.

I have however test installed the bcm driver, and I get the same error messages when bonding with bcm:


-----------
bonding.c:v2.2.14 (June 30, 2003)
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.
divert: not allocating divert_blk for non-ethernet device bond0 bond0 registered without MII link monitoring, in load balancing (round-robin) mode. bond0 registered without ARP monitoring
bond_enslave(): failed to get speed/duplex from eth0, speed forced to 100Mbps, duplex forced to Full.
bond0: enslaving eth0 as an active interface with an up link.
bond_enslave(): failed to get speed/duplex from eth1, speed forced to 100Mbps, duplex forced to Full.
bond0: enslaving eth1 as an active interface with an up link.
ip_tables: (C) 2000-2002 Netfilter core team
bcm5700: eth0 NIC Link is UP, 1000 Mbps full duplex
-----------


I guess it may be the bonding driver itself that doesn't work in RHEL30?

Or am I forgetting anything?

I have edited/created
ifcfg-eth[01]
ifcfg-bond0
modules.conf

Isn't that all that needs to be done?


Basp installed successfully though, and has not left any error messages in the logs yet.





-Sigbjørn

PS!
I read through your document on RHEL3 and SW Raid. Nice work!
I will keep it as a reference in my server recovery documentation!


>-----Original Message-----
>From: Steve_Boley at Dell.com [mailto:Steve_Boley at Dell.com]
>Sent: Tuesday, May 11, 2004 6:35 PM
>To: Sigbjørn Strømmen
>Subject: RE: RHEL30 / tg3 / bonding / miimon
>
>
>You can get the latest bcm5700 from bcom's site and it works with
>bonding as it was develled with kernel dev guy and works with mii and 
>ethtool both.
>Steve
>
>-----Original Message-----
>From: linux-poweredge-admin at dell.com 
>[mailto:linux-poweredge-admin at dell.com] On Behalf Of Sigbjørn Strømmen
>Sent: Tuesday, May 11, 2004 11:23 AM
>To: Linux-Poweredge (E-mail)
>Subject: RHEL30 / tg3 / bonding / miimon
>
>
>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.
>
>_______________________________________________
>Linux-PowerEdge mailing list
>Linux-PowerEdge at dell.com 
>http://lists.us.dell.com/mailman/listinfo/linux-poweredge
>Please read the FAQ at http://lists.us.dell.com/faq or search the list
>archives at http://lists.us.dell.com/htdig/
>
>
>


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.



_______________________________________________
Linux-PowerEdge mailing list
Linux-PowerEdge at dell.com http://lists.us.dell.com/mailman/listinfo/linux-poweredge
Please read the FAQ at http://lists.us.dell.com/faq or search the list archives at http://lists.us.dell.com/htdig/




More information about the Linux-PowerEdge mailing list