---------------------------------------------------------------------------------------- In bonding version 2.6.2 or later, when a failover occurs in active-backup mode, bonding will issue one or more gratuitous ARPs on the newly active slave. One gratuitous ARP is issued for the bonding master interface and each VLAN interfaces configured above it, provided that the interface has at least one IP address configured. Gratuitous ARPs issued for VLAN interfaces are tagged with the appropriate VLAN id. ----------------------------------------------------------------------------------------
Ethernet Channel Bonding Driver:
2.6.1 (October 29, 2004) Bonding Mode: load balancing
(round-robin) Currently Active Slave: eth0 MII Status: up MII Polling Interval (ms):
1000 Up Delay (ms): 0 Down Delay (ms): 0
Slave Interface: eth1 MII Status: up Link Failure Count: 1
Slave Interface: eth0 MII Status: up Link Failure Count: 1
---------------------------------------------------------------------------------------- The balance-rr, balance-xor and broadcast modes generally require that the switch have the appropriate ports grouped
together. The nomenclature for such a group
differs between switches, it may be called an
"etherchannel" (as in the Cisco example, above), a "trunk group" or some other similar variation. For these modes, each
switch will also have its own configuration
options for the switch's transmit policy to the bond.
Typical choices include XOR of either the MAC or IP addresses. The transmit policy of the two peers does not need
to match. For these three modes, the bonding mode really
selects a transmit policy for an EtherChannel
group; all three will interoperate with another EtherChannel
group. ----------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------- For reasons of simplicity, and to support the use of adapters that can do VLAN hardware acceleration offloading, the bonding interface declares itself as fully hardware offloading capable, it
gets the add_vid/kill_vid notifications to
gather the necessary information, and it propagates those
actions to the slaves. In case of mixed adapter types,
hardware accelerated tagged packets that should go through
an adapter that is not offloading capable are "un-accelerated" by the bonding driver so the VLAN tag sits in the regular location. ----------------------------------------------------------------------------------------
For balance-alb mode, the active
slave is the slave used as a "primary." This slave is used for
mode-specific control traffic, for sending to peers that are
unassigned or if the load is unbalanced.
+----------+ +----------+ | |eth0 port1| | to other
networks | Host A
+---------------------+ router +-------------------> | +---------------------+ | Hosts B and C
are out | |eth1
port2| | here somewhere
+----------+ +----------+
# ping -n 10.0.4.2 PING 10.0.4.2 (10.0.4.2) from 10.0.3.10 : 56(84) bytes of data. 64 bytes from 10.0.4.2: icmp_seq=1 ttl=64 time=13.7 ms 64 bytes from 10.0.4.2: icmp_seq=1 ttl=64 time=13.8 ms (DUP!) 64 bytes from 10.0.4.2: icmp_seq=1 ttl=64 time=13.8 ms (DUP!) 64 bytes from 10.0.4.2: icmp_seq=1 ttl=64 time=13.8 ms (DUP!) 64 bytes from 10.0.4.2: icmp_seq=1 ttl=64 time=13.8 ms (DUP!) 64 bytes from 10.0.4.2: icmp_seq=2 ttl=64 time=0.216 ms 64 bytes from 10.0.4.2: icmp_seq=3 ttl=64 time=0.267 ms 64 bytes from 10.0.4.2: icmp_seq=4 ttl=64 time=0.222 ms
When an Ethernet Switch Module is
in place, only the ARP monitor will reliably detect link
loss to an external switch. This is nothing unusual,
but examination of the BladeCenter cabinet would suggest that the "external" network ports are the ethernet ports
for the system, when it fact there is a
switch between these "external" ports and the devices on
the JS20 system itself. The MII monitor is only able to detect link failures between the ESM and the JS20
system.
