Hi,
I'm trying to setup a bonding interface over 802.1q devices. All up, with connection to net, but when one real interface (eth0 or eth1) down, the bonding don't work (the bonding don't pass to the next slave)
I think that the miimon don't work with 802.1q devices but I try it with arp_interval and don't work anything (the bonding don't up)
Please, any comment ??
thankx, in advance and sorry for my english.
My server, Suse 8.2 with 2.4.20-64GB-SMP kernel. I updat e the e1000 driver to 5.2.39 version.
My modules.conf:
-----------------------------
alias bond0 bonding
alias bond1 bonding
options bond0 miimon=100 mode=1
options bond1 -o bonding1 miimon=100 mode=1
-----------------------------
My ethernet configuration:
eth0 (e1000 driver), with eth0.100 and eth0.101
eth1 (e1000 driver), with eth1.100 and eth1.101
bond0 and bond1
mii-diag over eth0:
./mii-diag eth0
Basic registers of MII PHY #0: 1140 796d 0141 0c23 0de1 41e1 0005 2001.
The autonegotiated capability is 01e0.
The autonegotiated media type is 100baseTx-FD.
Basic mode control register 0x1140: Auto-negotiation enabled.
You have link beat, and everything is working OK.
Your link partner advertised 41e1: 100baseTx-FD 100baseTx 10baseT-FD 10baseT.
End of basic transceiver information.
And over eth0.100
/mii-diag eth0.100
SIOCGMIIPHY on eth0.100 failed: Operation not supported
then... miimon don't work with this interfaces ?? umm
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
set_name_type VLAN_PLUS_VID | VLAN_PLUS_VID_NO_PAD | DEV_PLUS_VID | DEV_PLUS_VID_NO_PAD
Sets the way vlan-device names are created. Use vconfig without arguments to see
the different formats.
With this you can define how vconfig create vlan's devices names like :
Hi,
I'm trying to setup a bonding interface over 802.1q devices. All up, with connection to net, but when one real interface (eth0 or eth1) down, the bonding don't work (the bonding don't pass to the next slave)
I think that the miimon don't work with 802.1q devices but I try it with arp_interval and don't work anything (the bonding don't up)
Please, any comment ??
thankx, in advance and sorry for my english.
My server, Suse 8.2 with 2.4.20-64GB-SMP kernel. I updat e the e1000 driver to 5.2.39 version.
My modules.conf:
-----------------------------
alias bond0 bonding
alias bond1 bonding
options bond0 miimon=100 mode=1
options bond1 -o bonding1 miimon=100 mode=1
-----------------------------
My ethernet configuration:
eth0 (e1000 driver), with eth0.100 and eth0.101
eth1 (e1000 driver), with eth1.100 and eth1.101
bond0 and bond1
ifenslave bon0 eth0.100
ifenslave bon0 eth1.100
ifenslave bon1 eth0.101
ifenslave bon1 eth1.101
ethtool over eth0:
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: Full
Port: Twisted Pair
PHYAD: 0
Transceiver: internal
Auto-negotiation: on
Supports Wake-on: umbg
Wake-on: g
Link detected: yes
ethtool over eth0.100:
Settings for eth0.100:
No data available
ummmm
mii-diag over eth0:
./mii-diag eth0
Basic registers of MII PHY #0: 1140 796d 0141 0c23 0de1 41e1 0005 2001.
The autonegotiated capability is 01e0.
The autonegotiated media type is 100baseTx-FD.
Basic mode control register 0x1140: Auto-negotiation enabled.
You have link beat, and everything is working OK.
Your link partner advertised 41e1: 100baseTx-FD 100baseTx 10baseT-FD 10baseT.
End of basic transceiver information.
And over eth0.100
/mii-diag eth0.100
SIOCGMIIPHY on eth0.100 failed: Operation not supported
then... miimon don't work with this interfaces ?? umm
Hi netsound,
Give it a try with another vlan's devices names ...
I mean, use the option of vconfig :
* name-type: VLAN_PLUS_VID (vlan0005), VLAN_PLUS_VID_NO_PAD (vlan5),
DEV_PLUS_VID (eth0.0005), DEV_PLUS_VID_NO_PAD (eth0.5)
And from man page of vconfig :
set_name_type VLAN_PLUS_VID | VLAN_PLUS_VID_NO_PAD | DEV_PLUS_VID | DEV_PLUS_VID_NO_PAD
Sets the way vlan-device names are created. Use vconfig without arguments to see
the different formats.
With this you can define how vconfig create vlan's devices names like :
VLAN_PLUS_VID (vlan0005), VLAN_PLUS_VID_NO_PAD (vlan5)
Try one of these two options and retry ...
Please post feedback answer.
A++