[ale] Issue with eth0 appeared after setting up ethernet bonding
Ryan Fish
FishR at bellsouth.net
Mon Jul 31 23:56:13 EDT 2006
I'm hoping one or more of you out there can help with this strange issue I'm
seeing.
OS: RHEL 3 ES
NICs (onboard):
01:03.0 Ethernet controller: Intel Corporation 82546EB Gigabit Ethernet
Controller (Copper) (rev 01)
01:03.1 Ethernet controller: Intel Corporation 82546EB Gigabit Ethernet
Controller (Copper) (rev 01)
Settings for eth0:
Supported ports: [ TP ]
Supported link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Full
Supports auto-negotiation: Yes
Advertised link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Full
Advertised auto-negotiation: Yes
Speed: 100Mb/s
Duplex: Half
Port: Twisted Pair
PHYAD: 0
Transceiver: internal
Auto-negotiation: on
Supports Wake-on: umbg
Wake-on: d
Current message level: 0x00000007 (7)
Link detected: yes
----------------------------------------------------------------------------
----------------
Settings for eth1:
Supported ports: [ TP ]
Supported link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Full
Supports auto-negotiation: Yes
Advertised link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Full
Advertised auto-negotiation: Yes
Speed: 1000Mb/s
Duplex: Full
Port: Twisted Pair
PHYAD: 0
Transceiver: internal
Auto-negotiation: on
Supports Wake-on: umbg
Wake-on: d
Current message level: 0x00000007 (7)
Link detected: yes
The basic issue is that no matter how many times I've tried to manually
force eth0 to 1000/FD/Autoneg via "ethtool -s" it always stays at
100/HD/Auto. ETH0 was being used by a second IP on this box prior to the
bonding being put in place so this just started happening afterwards. It
was able to connect at 1000/FD without any issues or any sort prior.
All of the bonding settings:
/etc/modules.conf
alias eth0 e1000
alias eth1 e1000
alias usb-controller usb-ohci
alias bond0 bonding miimon=100 mode=0
ifcfg-bond0
DEVICE=bond0
ONBOOT=yes
BOOTPROTO=none
IPADDR=10.18.62.110
NETMASK=255.255.255.0
BROADCAST=10.18.62.255
NETWORK=10.18.62.0
USERCTL=no
ifcfg-eth0
# Intel Corp.|82546EB Gigabit Ethernet Controller (Copper)
DEVICE=eth0
ONBOOT=yes
BOOTPROTO=none
HWADDR=00:04:23:9A:A9:9A
MASTER=bond0
SLAVE=yes
USERCTL=no
ifcfg-eth1
# Intel Corp.|82546EB Gigabit Ethernet Controller (Copper)
DEVICE=eth1
BOOTPROTO=none
HWADDR=00:04:23:9A:A9:9B
ONBOOT=yes
MASTER=bond0
SLAVE=yes
USERCTL=no
Any thoughts on what the cause of this issue could be? Bonding on the same
hardware with the same NICs is working just fine elsewhere within the
network.
Thank you.
-Ryan
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Ale
mailing list