Hi guys.
I am really a newbie but i am following a lot of HowTos and make run a bonding.
I have 2 server where the bonding doesnt work or it work very bad.
Lets start with the one i can do a lot of test.
It a Dell t300 with a Broadcomm netxtreme dual gigabit card.
I created the bonding.conf on /etc/modprobe.d/bonding.conf
The 192.168.10.1 is my pfsense firewall
This is my interfaces file
And this my /proc/net/bonding/bond0
And my ifconfig
It seems the bond it using eth2 and eth3 with the same MAC, which seems very strange to me, but if i run ethtool
it detects differents mac's
And they are on different buses
I dont know what is happening here
I am really a newbie but i am following a lot of HowTos and make run a bonding.
I have 2 server where the bonding doesnt work or it work very bad.
Lets start with the one i can do a lot of test.
It a Dell t300 with a Broadcomm netxtreme dual gigabit card.
I created the bonding.conf on /etc/modprobe.d/bonding.conf
HTML:
root@node02:~# cat /etc/modprobe.d/bonding.conf
alias bond0 bonding
options bonding mode=4 arp_interval=2000 arp_ip_target=192.168.10.1 miimon=100
The 192.168.10.1 is my pfsense firewall
This is my interfaces file
HTML:
root@node02:~# cat /etc/network/interfaces
auto lo
iface lo inet loopback
auto vmbr0
iface vmbr0 inet static
address 192.168.10.11
netmask 255.255.255.0
gateway 192.168.10.1
bridge_ports eth1
bridge_stp off
bridge_fd 0
auto bond0
iface bond0 inet static
bond-slaves eth2 eth3
bond-mode 4
bond-miimon 100
bond-downdelay 200
bond-updelay 200
#bonc-lacp_rate 1
#mtu 9000
#bond-xmit-hash-policy layer2
pre-up ifup eth2 eth3
post-down ifdown eth2 eth3
address 192.168.10.245
gateway 192.168.10.1
netmask 255.255.255.0
And this my /proc/net/bonding/bond0
HTML:
Ethernet Channel Bonding Driver: v3.6.0 (September 26, 2009)
Bonding Mode: IEEE 802.3ad Dynamic link aggregation
Transmit Hash Policy: layer2 (0)
MII Status: up
MII Polling Interval (ms): 100
Up Delay (ms): 200
Down Delay (ms): 200
802.3ad info
LACP rate: slow
Aggregator selection policy (ad_select): stable
Active Aggregator Info:
Aggregator ID: 1
Number of ports: 1
Actor Key: 17
Partner Key: 1
Partner Mac Address: 00:00:00:00:00:00
Slave Interface: eth2
MII Status: up
Speed: 1000 Mbps
Duplex: full
Link Failure Count: 0
Permanent HW addr: 00:26:b9:5e:d5:86
Aggregator ID: 1
Slave queue ID: 0
Slave Interface: eth3
MII Status: down
Speed: Unknown
Duplex: Unknown
Link Failure Count: 0
Permanent HW addr: 00:26:b9:5e:d5:87
Aggregator ID: 2
Slave queue ID: 0
And my ifconfig
HTML:
root@node02:~# ifconfig
bond0 Link encap:Ethernet HWaddr 00:26:b9:5e:d5:86
inet addr:192.168.10.245 Bcast:192.168.10.255 Mask:255.255.255.0
inet6 addr: fe80::226:b9ff:fe5e:d586/64 Scope:Link
UP BROADCAST RUNNING MASTER MULTICAST MTU:1500 Metric:1
RX packets:2501 errors:0 dropped:0 overruns:0 frame:0
TX packets:32 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:253243 (247.3 KiB) TX bytes:3692 (3.6 KiB)
eth1 Link encap:Ethernet HWaddr 00:1e:0b:db:97:92
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:21967 errors:0 dropped:0 overruns:0 frame:0
TX packets:16888 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:4368370 (4.1 MiB) TX bytes:3221359 (3.0 MiB)
eth2 Link encap:Ethernet HWaddr 00:26:b9:5e:d5:86
UP BROADCAST RUNNING SLAVE MULTICAST MTU:1500 Metric:1
RX packets:2501 errors:0 dropped:0 overruns:0 frame:0
TX packets:32 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:253243 (247.3 KiB) TX bytes:3692 (3.6 KiB)
Interrupt:16
eth3 Link encap:Ethernet HWaddr 00:26:b9:5e:d5:86
UP BROADCAST RUNNING SLAVE MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
Interrupt:17
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:1470 errors:0 dropped:0 overruns:0 frame:0
TX packets:1470 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:462224 (451.3 KiB) TX bytes:462224 (451.3 KiB)
venet0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
inet6 addr: fe80::1/128 Scope:Link
UP BROADCAST POINTOPOINT RUNNING NOARP MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:3 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
veth101.0 Link encap:Ethernet HWaddr 2a:ed:5e:13:13:bf
inet6 addr: fe80::28ed:5eff:fe13:13bf/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:66 errors:0 dropped:0 overruns:0 frame:0
TX packets:2504 errors:0 dropped:16 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:5807 (5.6 KiB) TX bytes:225140 (219.8 KiB)
vmbr0 Link encap:Ethernet HWaddr 00:1e:0b:db:97:92
inet addr:192.168.10.11 Bcast:192.168.10.255 Mask:255.255.255.0
inet6 addr: fe80::21e:bff:fedb:9792/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:21186 errors:0 dropped:0 overruns:0 frame:0
TX packets:17163 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:3842122 (3.6 MiB) TX bytes:3220376 (3.0 MiB)
It seems the bond it using eth2 and eth3 with the same MAC, which seems very strange to me, but if i run ethtool
HTML:
root@node02:~# ethtool -P eth3
Permanent address: 00:26:b9:5e:d5:87
root@node02:~# ethtool -P eth2
Permanent address: 00:26:b9:5e:d5:86
root@node02:~# ethtool -P eth1
Permanent address: 00:1e:0b:db:97:92
root@node02:~# ethtool -P eth0
Permanent address: 00:1e:0b:db:97:90
it detects differents mac's
And they are on different buses
HTML:
root@node02:~# ethtool -i eth2
driver: tg3
version: 3.132
firmware-version: 5722-v3.08, ASFIPMI v6.02
bus-info: 0000:01:00.0
supports-statistics: yes
supports-test: yes
supports-eeprom-access: yes
supports-register-dump: yes
supports-priv-flags: no
root@node02:~# ethtool -i eth3
driver: tg3
version: 3.132
firmware-version: 5722-v3.08, ASFIPMI v6.02
bus-info: 0000:02:00.0
supports-statistics: yes
supports-test: yes
supports-eeprom-access: yes
supports-register-dump: yes
supports-priv-flags: no
I dont know what is happening here