configure bond interface

[monu_1]

Hi all,

I want to increase speed, autoneg off, duplex full of bond interface. ethtool utility is not working for the same.
#ethtool bond0
bond0 does not appear to be an ethernet device
ethtool version 1.8

How can i configure bond interface?

Thanks,
MKS

[Court Campbell]

You might want to change the options on the actual interfaces that the bond is using, ie. eth0, eth1. Also, if you are running Gigabit ethernet you are going to want auto negotiation on.

[Ivan Ferreira]

Here you have a sample I use on my servers:

# more ifcfg-eth0
DEVICE=eth0
BOOTPROTO=none
HWADDR=00:1A:4B:4E:11:7C
ONBOOT=yes
TYPE=Ethernet
ETHTOOL_OPTS="speed 100 duplex full autoneg off"
MASTER=bond0
SLAVE=yes


# more ifcfg-eth1
DEVICE=eth1
BOOTPROTO=none
HWADDR=00:1A:4B:4E:11:7E
ONBOOT=yes
TYPE=Ethernet
ETHTOOL_OPTS="speed 100 duplex full autoneg off"
MASTER=bond0
SLAVE=yes

# more ifcfg-bond0
DEVICE=bond0
USERCTL=no
ONBOOT=yes
IPADDR=
NETMASK=255.255.255.0
NETWORK=
BROADCAST=

[Steven E. Protter]

Shalom,

Please post your modprobe.conf file.

SEP

[Matti_Kurkela]

The ethtool command works with _physical_ network interfaces, i.e. eth0...ethN. You must use eth* names with the ethtool command, and configure the speed/duplex settings of each physical interface independently, even though they may be bonded together at the upper level.

The "bond0" is an aggregation layer that might contain one or more physical interfaces. It intentionally does not replicate the physical layer configuration between the bonded NICs.

For example, you might be in a situation where your primary network interface is connected to a new gigabit switch, and the backup interface is still connected to an old ratty 100Mbit switch that requires forcing full duplex to work reliably. In this situation, forcing both physical NICs to be configured exactly the same would be a misfeature.

MK