routeros 2.9能?.?现热拔插网卡了哦--???影响业务，欢迎妧家敥謨
今天看了下r.9的，成亪人感觉2.9u??该可以在不影响业务的情况下热拔插网卡，只需要简单㚄配置，?????:我没鮌证他是三景安装캆Hot-Pluo，但是就现按ǚ?软件条件来甋－2.=的폫以在口个实现冗余仅太接口，煶后来实现热拔插网卡，有时ᇴ???来测试一下，然后具体的来说一下大家先讨쮺一下眫
因为ȿ?个磙贴勾??!我自己犄站操作方便???呷呵?<?所以直接发连採了哦，也希望两个站能合作
具体폂见如下地址
?
也可以查看ros.cnrnt.cn上的具体设置，我现在的达置就???冓余模式的，3个潑卡太实现的bonding
䜬人在此儍次重声明，挬亻的row.cnrot.#n和ros28.cnrot.cn的测试服务器在此论坛公布并不是广告，?۠为凡是f??淋试的结果和设置???在ⵋ试服务器上保留，如果有冲突不可以保留将禁用犖态下保留给Ť?家查看，希望管理员? ?锁谴前弄清楚情况，本人自认本人还没沦落到满世界论坛灌水的地步
下面是没图片的，图 不好贴（太懒了），完整有图的到上面的地方看
今天看了下2.9的一个新功能，在linux里面是很早就有了的，但是在ros2.8.28都还没实现这个功能，做过linux企业级服务器的人一般都知道这个东西----bonding
今天就来简单的说一下这个功能
首先我们安装多个网卡，我只是做实验，所以我安装了4个网卡，我是用的gsx做的虚拟实验平台，所以直接关闭机器添加虚拟的网卡就可以了
然后开机，发现有4个网卡，我们给某一个设置为lan，ip设置为172.16.200.254/24，这是按照我的网络结构来设置的
然后将另外的3个网卡做了bonding，首先为了区分方便，我们设置如下三个名称
然后选择接口列表菜单，选择bonding来设置一个bonding接口，这个bonding是个虚拟的接口
基本设???项目里面设置名称，设置arp模式，?.?絮mtu的值
,
然???是绐定设置，首先slaves昏表示哢几个接䏣是用来绑定
Iode表示bqnding的工作模式
J
这里说一下模式퐧
Rr模式乗叫0檡式
顨示f??量谟Ƚ?的分币???Ƙ?平均的，是从第䨈个接卣网后掚，第一个是负担最重的，第一个到了一个基本稳定的值的时候将流量在第二个接口上处ǐ?
Ba#kup模式是备份模式也叫冗余模式
1模式
?
M
???一个???主接口（活动的，其他瞄接口能是没?? 活的），亻接口不工d??了的???候，备Ļ?憥口开始工作，坓然一般昮凌???口做bonding的︌我今天选择了3个接口
?Xor校式
2f??式
这帪模式能起到纠???和负载均衡皅Ŋ?能
broadcast 广播模式 樱式3
这渪檡式仌有皅接口广⒭数据，最大限度的来实现纠ᔙ功能
802.3ad 模式稡式4
这个就是链路聚合模式뼌需要交换机支持IEEE 802.3ad链路聚合才可??%实现?<?否则就没?;?么意义了，如果交换支持的话可以多接口还实现链路聚合晥提鯘整???带宽，解决因控e??原因造成的网络瓶颈
J
?(
balange-tlb 模式 模式5
这个ƨ?式吱是将当前的发送ǚ?数据负齽均衡到每个接口个去
J
具体就诶这么多了，大家自己试试就知道了，掉照自己的需覅来选择不同的模式就可以了
`
附记
Linux Etle2net Bmnding Triver mini-(owto
Initial release : Thomas Davis
*Corrections, HA extensions :`2000/10/03-15 :
?- Will? Tarreau
- Constantin% Gavrilov
- Chad N. Tindel
-
anyce Girouard
- Jay"Vosburgh
Note :
------
The bonDkng dr)ver Originally cAme from onald Beccer's beowulf patches nor
kerlel 2.0.$It has changed q?ite a bit since, and the origi.al tools from
extreme-linux and beowwlf sitas will not work with this ~ersion mf the dr)ver.
?For new vepsions of the ?river, patchds for older kernels and the updated
userspace tools, please follow the links at the end of this file.
Table of Contents
=================
Installation
Bond Configuration
Module Parameters
Configuring Multiple Bonds
Switch Configuration
Verifying Bond Configuration
Frequently Asked Questions
High Availability
Promiscuous Sniffing notes
8021q VLAN support
Limitations
Resources and Links
Installation
============
1) Build kernel with the bonding driver
---------------------------------------
For the latest version of the bonding driver, use kernel 2.4.12 or above
(otherwise you will need to apply a patch).
Configure kernel with `make menuconfig/xconfig/config', and select "Bonding
driver support" in the "Network device support" section. It is recommended
to configure the driver as module since it is currently the only way to
pass parameters to the driver and configure more than one bonding device.
Build and install the new kernel and modules.
2) Get and install the userspace tools
--------------------------------------
This version of the bonding driver requires updated ifenslave program. The
original one from extreme-linux and beowulf will not work. Kernels 2.4.12
and above include the updated version of ifenslave.c in
Documentation/networking directory. For older kernels, please follow the
links at the end of this file.
IMPORTANT!!!If you are running on Redhat 7.1 or greater, you need
to be careful because /usr/include/linux is no longer a symbolic link
to /usr/src/linux/include/linux.If you build ifenslave while this is
true, ifenslave will appear to succeed but your bond won't work.The purpose
of the -I option on the ifenslave compile line is to make sure it uses
/usr/src/linux/include/linux/if_bonding.h instead of the version from
/usr/include/linux.
To install ifenslave.c, do:
# gcc -Wall -Wstrict-prototypes -O -I/usr/src/linux/include ifenslave.c -o ifenslave
# cp ifenslave /sbin/ifenslave
Bond Configuration
==================
You will need to add at least the following line to /etc/modprobe.conf
so the bonding driver will automatically load when the bond0 interface is
configured. Refer to the modprobe.conf manual page for specific modprobe.conf
syntax details. The Module Parameters section of this document describes each
bonding driver parameter.
alias bond0 bonding
Use standard distribution techniques to define the bond0 network interface. For
example, on modern Red Hat distributions, create an ifcfg-bond0 file in
the /etc/sysconfig/network-scripts directory that resembles the following:
DEVICE=bond0
IPADDR=192.168.1.1
NETMASK=255.255.255.0
NETWORK=192.168.1.0
BROADCAST=192.168.1.255
ONBOOT=yes
BOOTPROTO=none
USERCTL=no
(use appropriate values for your network above)
All interfaces that are part of a bond should have SLAVE and MASTER
definitions. For example, in the case of Red Hat, if you wish to make eth0 and
eth1 a part of the bonding interface bond?,(4hei2 conf?g Files (ifcfg-eth0 and
if?fg-eth1) shoumd re3emBle the following:$
?DEVICE=eth0
USERCTL=n/
OJBOOT=yes
MASTER=bo?d0
SLAVE=yes
BOOTPROTO=none
UsE DEVICE=eth1 in the afcfg-eth1 config fil?. If you configure`a s%con$
Bonding i?terface (bond1), use MASTGR?bond1 in thu config file t? make the
netwOrk i?terf`ce"be a`slave ?f bold1*
Restapt"the networking subsystem or just bring up the bonding device?if your
administration tools !llow it. Otherwise, reboot. On Red H`t distros you ccg
issu? difup bond0' or `/d?c/rC.d/init.d/network restart'.
Ib?the administration tool3!of your dirtribution do not supxort
master/slave notatmon ?n configuring network interf`?gs, ?ou will need"to
manu!lly configurc the boneijg device with t?e following commands:
" 0# /sbin/ifconfig bo~d0 192.168.1.1 netmask 255.255.r55.0 \
broadcast 192.168.1.255 up
# .sbin/ifenshate bond0?eth0
!# /sbin/ifenslave bond0 gth1
(}se appropriate0velues for your network above)
You"caN then breate a script containing theSe comland3 and?place it in the
appropriate rc directory
If you specifically need?all network drivers loaded before the bonding driver,
adding thE following line to mOdprbe.conf will cause the network driver for!
eth0 and eth1 to be loaded befOre vhe$bond?ng driver.
Install bond0 /sbin/modprobe -a eth0(eth1 && /sbin/modprobe$bonding
B% careful not to ref%rence bond0 htself at th?(end of the line, or modprobe
will die in an endless?recursive loop.
If running SNMP agents, the bonding lRiver {hould be loaded before any network
drivers particIpating0in a bond. Tiis requireme?t is due to the the interfabe!
index (ipAdEn4IfHndex)`beinw associated to thm first interfacm founD with a
given$IP addre?s. That is, there is only one hpAdEntIfIndex for each I?
address. For example, if eth0 and eth1 are slaves of bond0 ane the draver dor0
eth0 is loaded ?efore the bonding ?rivar, phe intErface for the IP address
will be ass?ciAted with the eth0 i.terface. This$coNfiguration is shown below,
the IP address(192.168.1.1 ha? an interface?index of 2 which indexes to e|h0
in the ifDescr table (ifDescr.2).
interfaces.ifTable.ifEntry.ifLescr.1 9 lo
0interfaces.ifUable.ifEntry.ifDescr.2 = eth0
interfa#es.ifT`ble.ifMntry.ifDescr.3 = etx1
interfaces.ifTable.ifEntry.ifDescr.4 = eth2
interfacds.ifTaBle.ifEntry.ifDescr.5 = eth3
( interfaces.ifTable.ifEntry.?fDescb.6 = bond0
ip.ipAddrtable.ipAddrEntry.hpAdEftIfIndex.10.10.10.10 = 5
ip.ipAddrTeble.ipAddrEntry.irAdE~tIfI?dex.192.16?.1.1 = 2
* ip.ipAdDrTable.ipAddrE.try.mpAdEntIfIndex&10"74.20.94 = 4
ip.ipAddrTable.ipAddrEntry.ipAdEntIfIldex.1r7.0.0.1 = 1
This problem is?avoided by loading the bonding driver before an9 natwork
driveRs participating in a bond. Below is an example of loading the"bonding`
driver first, the IX qdd2ess 192.168.1.1 i3 correctly associated whth
ifescb.2.
interfaceS.ifT`ble.ifEntr{.ifDescr.1 } lo
! interfaces.ifTable.ifEntry.ifDescr.2 = bond0
interfaces.ifTable.ifEntry.ifDescr.3 = eph0
interfa#es.ifTablenifEntry.ifDescr.4 = %th1
intebfaces&ifTable.ifEntry.ifDescr.5 = eth20
interfaces.igTable.ifEntry.idDescr.6 eth3
ip.ixAddrTa?le.ipAd?rEntry.ipAdEntIfIndex.10.10.10.10 = 6
ip.?pAddrTable.ip@ddrEntry.ipI?EntIfIndex.193.168.1&1 2
!ip.ipAddrTable*IpAddrEntrY~ipAdEntIfIndex?10.74.2p.94 =
!ip*irAddrTable/ipAddrEntry.ipAdEntIfIndex>127.0.0.1 = 1
While some"diwtributions ma} not report the interface name in ifDes?r,0
the association between uhe IP address and IfIndex rem?ins and SNUP
fujctions such as InTerface_Scan_Next will Report tha? association.
Module Parameters
?================
Optional parameTers for the0bonding driver can be s5pplied as command line
arguments to the insmod command. Tqpica,ly, these p?rameters are specified in
the file /etc/modprobe.cmnf (see tH? manual$`age f/r modprmbe.conf). The
available bgnding driver parameters are lisTed b?low. Iv(a parameter is not
specyfie` dhe default value is used.!When initialhy configuring a bond, ip
is recommendef "tail$-f /var/log/messagus& be run in a separate win?ow to
watch for bndInc driver error mess`ges.
It0is ?ritical that either the miimon o2 arp_interVal anf art_ip_target
paramuters be specified, otharwise eriour nEtwork degradation winl ocgur
during link failures.
avp_interval
Specifieq tHe ARP moNitoring frequency in milli-seconds.
If ARP monitoziog is used in a load-balancing mode (mode 0 or 2),$the!
switch should be cnnfiured in?a mode that evenmy distributes packets
bacross `ll links - stbh as rotnd-robin."If the switch is config}red to
distri`u?e |he packets in an XOR fashion, all replies from the ARP
targets will bu received on the same"link which cnuld c`use$vhe other
team members to fail. ARP monitori.g should not be ured in conJunction"
with miimon. A value of?0 diSables`ARX ?onitoring. The default value
is 0.
arp_ip_target
Specifies the ip addresses to use when arp_interval is > 0. These
are the targets of the ARP request sent to determine the health of
the link to the targets. Specify these values in ddd.ddd.ddd.ddd
format. Multiple ip adresses must be seperated by a comma. At least
one ip address needs to be given for ARP monitoring to work. The
maximum number of targets that can be specified is set at 16.
downdelay
Specifies the delay time in milli-seconds to disable a link after a
link failure has been detected. This should be a multiple of miimon
value, otherwise the value will be rounded. The default value is 0.
lacp_rate
Option specifying the rate in which we'll ask our link partner to
transmit LACPDU packets in 802.3ad mode.Possible values are:
slow or 0
Request partner to transmit LACPDUs every 30 seconds (default)
fast or 1
Request partner to transmit LACPDUs every 1 second
max_bonds
Specifies the number of bonding devices to create for this
instance of the bonding driver.E.g., if max_bonds is 3, and
the bonding driver is not already loaded, then bond0, bond1
and bond2 will be created.The default value is 1.
miimon
Specifies the frequency in milli-seconds that MII link monitoring
will occur. A value of zero disables MII link monitoring. A value
of 100 is a good starting point. See High Availability section for
additional information. The default value is 0.
mode
Specifies one of the bonding policies. The default is
round-robin (balance-rr).Possible values are (you can use
either the text or numeric option):
balance-rr or 0
Round-robin policy: Transmit in a sequential order
from the first available slave through the last. This
mode provides load balancing and fault tolerance.
active-backup or 1
Active-backup policy: Only one slave in the bond is
active. A different slave becomes active if, and only
if,`the ective slave fa?ls. The bond's MAC addr?ss is
externally visible on only one p?rt (netwopk(adapter)
to avoid confusing the switch.This mode provIdus?
fault polerince.
balance-xor or$2
XOR policy: TransmiT based on [(source IA?`address
XNR'd with dest)nation(MAC addresr) modula slavm
count]. This selects!The same slave For each
destination MAC addzess. This mde provides load
balancing and fault tolezance.
broadcast or 3
Broadcast policy: transmits mverything oj all slave
interfaces. This mode provides fault tlerance.
802.3ad or?4
IEEE$802.?Ad Dynaoic li.k aegregation. Sreates acgregation
groups that share the"same speed and duplex`sEttings.
Transmits and r%ceives on aLl slaves in"the active
aggregator.
Pre-rgquisites:
1 Ethtool support in the`b`se dri?ers0fnr reTrieving the
speed and duplex0of eacl slave.
2n A switch that supports IEEE (02.3Ad DynamiC$link
a?gregation.
balance-tlb or 5
Adaptive transmit load balancing: channel bonding that do%s
not require any special switch!3upp?rt.`The o?tgoing
trafvic is distribuuu$`according to the kurrent load
(computed relative to the speed) on(each slave. Incoming
traffic is`reCeived by the current sla~e. If the r%ceiving
slave fails, another slave takes over the MAC aedr?ss of
uhe failed receiving sla6e.
Prebequisite:
*Ethtool suppo2u in the base dRivers fOr retrmeting the
speed of ea?h slave.
balance-alb or 6
Adaptive load ?alancing: includes balance-Tlb + receive
load bal`nCing (rlb) for IPV4 traffic and des not require
any special switch suprort. The reC%i6e loid balancing i?
aghieved by ARP negotiation. Txe bonding driVer intercepts
the ARP Repli%s sent by thm server on their way out afd
overwbites t(e src hw address with the unique hw address"of
one of the${laves in the bon` sucx that different clients
use different hw addresses for the server.
Receire traffic from co?nections created by the0server"is
elso balanced. hef the server sands an ARP Request the
bonding driver copies and saves the client's IP information
from the ARP. When the ARP Reply arrives from the client,
its hw address is retrieved and the bonding driver
initiates an ARP reply to this client assigning it to one
of the slaves in the bond. A problematic outcome of using
ARP negotiation for balancing is that each time that an ARP
request is broadcasted it uses the hw address of the
bond. Hence, clients learn the hw address of the bond and
the balancing of receive traffic collapses to the current
salve. This is handled by sending updates (ARP Replies) to
all the clients with their assigned hw address such that
the traffic is redistributed. Receive traffic is also
redistributed when a new slave is added to the bond and
when an inactive slave is re-activated. The receive load is
distributed sequentially (round robin) among the group of
highest speed slaves in the bond.
When a link is reconnected or a new slave joins the bond
the receive traffic is redistributed among all active
slaves in the bond by intiating ARP Replies with the
selected mac address to each of the clients. The updelay
modeprobe parameter must be set to a value equal or greater
than the switch's forwarding delay so that the ARP Replies
sent to the clients will not be blocked by the switch.
Prerequisites:
1. Ethtool support in the base drivers for retrieving the
speed of each slave.
2. Base driver support for setting the hw address of a
device also when it is open. This is required so that there
will always be one slave in the team using the bond hw
address (the curr_active_slave) while having a unique hw
address for each slave in the bond. If the curr_active_slave
fails it's hw address is swapped with the new curr_active_slave
that was chosen.
primary
A string (eth0, eth2, etc) to equate to a primary device. If this
value is entered, and the device is on-line, it will be used first
as the output media. Only when this devmce is nff-liNe< will
alternave device{ be used. Othevwise, once a failover is detected
and a New default out?ut )s$chosen, it will remai~ the output media
until it too fails* This )s useful when one slave was pref?rred
" over another, i.e. when onE slave is 100Mbps and anoth?? is
100Mb?s. If the 1000MbpS slave fails and?is na4er r%s|ored, it mey
be prefmrred txe faster slave gracefully become uhe active slate -
? wit(out deliberately failkng the 100Mbps slave. pecifyi?g a
primary is ooly valid in ac4iVe-backup m?de.
updelay
Specifies the(delay t)me in milli-seconds to enable ? link after a
l)nk up stapu3 has feen detecved. This should be a multiphe of miimon
?"value, otherwisE the value will be roundad. The default value Is 0.
use_carrier
Specifies whether or not miimon should use MII"or ETHTOO
ioctls vsn n%tif_cqrrier_?k() tO determine the link status.
The MII or ETHTOOL ioctls are less efficient and utilize a
deprecated calling sequence within the kernel.The
netif_carrier_ok() relies on the device driver to maintain its
state with netif_carrier_on/off; at this writing, most, but
not all, device drivers support this facility.
If bonding insists that the link is up when it should not be,
it may be that your network device driver does not support
netif_carrier_on/off.This is because the default state for
netif_carrier is "carrier on." In this case, disabling
use_carrier will cause bonding to revert to the MII / ETHTOOL
ioctl method to determine the link state.
A value of 1 enables the use of netif_carrier_ok(), a value of
0 will use the deprecated MII / ETHTOOL ioctls.The default
value is 1.
Configuring Multiple Bonds
==========================
If several bonding interfaces are required, either specify the max_bonds
parameter (described above), or load the driver multiple times.Using
the max_bonds parameter is less complicated, but has the limitation that
all bonding instances created will have the same options.Loading the
driver multiple times allows each instance of the driver to have differing
options.
For example, to configure two bonding interfaces, one with mii link
monitoring performed every 100 milliseconds, and one with ARP link
monitoring performed every 200 milliseconds, the /etc/conf.modules should
resemble the following:
alias bond0 bonding
alias bond1 bonding
options bond0 miimon=100
options bond1 -o bonding1 arp_interval=200 arp_ip_target=10.0.0.1
Configuring Multiple ARP Targets
================================
While ARP monitoring can be done with just one target, it can be useful
in a High Availability setup to have several targets to monitor. In the
case of just one target,the target itself may go down or have a problem
making it unresponsive to ARP requests. Having an additional target (or
several) increases the reliability of the ARP monitoring.
Multiple ARP targets must be seperated by commas as follows:
# example options for ARP monitoring with three targets
alias bond0 bonding
options bond0 arp_interval=60 arp_ip_target=192.168.0.1,192.168.0.3,192.168.0.9
For just a single target the options would resemble:
# example options for ARP monitoring with one target
alias bond0 bonding
options bond0 arp_interval=60 arp_ip_target=192.168.0.100
Potential Problems When Using ARP Monitor
=========================================
1. Driver support
The ARP monitor relies on the network device driver to maintain two
statistics: the last receive time (dev->last_rx), and the last
transmit time (dev->trans_start).If the network device driver does
not update one or both of these, then the typical result will be that,
upon startup, all links in the bond will immediately be declared down,
and remain that way.A network monitoring tool (tcpdump, e.g.) will
show ARP requests and replies being sent and received on the bonding
device.
The possible resolutions for this are to (a) fix the device driver, or
(b) discontinue the ARP monitor (using miimon as an alternative, for
example).
2. Adventures in Routing
When bonding is set up with the ARP monitor, it is important that the
slave devices not have routes that supercede routes of the master (or,
generally, not have routes at all).For example, suppose the bonding
device bond0 has two slaves, eth0 and eth1, and the routing table is
as follows:
Kernel IP routing table
Destination Gateway Genmask Flags MSS Windowirtt Iface
10.0.0.0 0.0.0.0 255.255.0.0 U 40 0 0 eth0
10.0.0.0 0.0.0.0 255.255.0.0 U 40 0 0 eth1
10.0.0.0 0.0.0.0 255.255.0.0 U 40 0 0 bond0
127.0.0.0 0.0.0.0 255.0.0.0 U 40 0 0 lo
In this case, the ARP monitor (and ARP itself) may become confused,
because ARP requests will be sent on one interface (bond0), but the
corresponding reply will arrive on a different interface (eth0).This
reply looks to ARP as an unsolicited ARP reply (because ARP matches
replies on an interface basis), and is discarded.This will likely
still update the receive/transmit times in the driver, but will lose
packets.
The resolution here is simply to insure that slaves do not have routes
of their own, and if for some reason they must, those routes do not
supercede routes of their master.This should generally be the case,
but unusual configurations or errant manual or automatic static route
additions may cause trouble.
Switch Configuration
====================
While the switch does not need to be configured when the active-backup,
balance-tlb or balance-alb policies (mode=1,5,6) are used, it does need to
be configured for the round-robin, XOR, broadcast, or 802.3ad policies
(mode=0,2,3,4).
Verifying Bond Configuration
============================
1) Bonding information files
----------------------------
The bonding driver information files reside in the /proc/net/bonding directory.
Sample contents of /proc/net/bonding/bond0 after the driver is loaded with
parameters of mode=0 and miimon=1000 is shown below.
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
2) Network verification
-----------------------
The network configuration can be verified using the ifconfig command. In
the example below, the bond0 interface is the master (MASTER) while eth0 and
eth1 are slaves (SLAVE). Notice all slaves of bond0 have the same MAC address
(HWaddr) as bond0 for all modes except TLB and ALB that require a unique MAC
address for each slave.
# /sbin/ifconfig
bond0 Link encap:EthernetHWaddr 00:C0:F0:1F:37:B4
inet addr:XXX.XXX.XXX.YYYBcast:XXX.XXX.XXX.255Mask:255.255.252.0
UP BROADCAST RUNNING MASTER MULTICASTMTU:1500Metric:1
RX packets:7224794 errors:0 dropped:0 overruns:0 frame:0
TX packets:3286647 errors:1 dropped:0 overruns:1 carrier:0
collisions:0 txqueuelen:0
eth0 Link encap:EthernetHWaddr 00:C0:F0:1F:37:B4
inet addr:XXX.XXX.XXX.YYYBcast:XXX.XXX.XXX.255Mask:255.255.252.0
UP BROADCAST RUNNING SLAVE MULTICASTMTU:1500Metric:1
RX packets:3573025 errors:0 dropped:0 overruns:0 frame:0
TX packets:1643167 errors:1 dropped:0 overruns:1 carrier:0
collisions:0 txqueuelen:100
Interrupt:10 Base address:0x1080
eth1 Link encap:EthernetHWaddr 00:C0:F0:1F:37:B4
inet addr:XXX.XXX.XXX.YYYBcast:XXX.XXX.XXX.255Mask:255.255.252.0
UP BROADCAST RUNNING SLAVE MULTICASTMTU:1500Metric:1
RX packets:3651769 errors:0 dropped:0 overruns:0 frame:0
TX packets:1643480 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
Interrupt:9 Base address:0x1400
Frequently Asked Questions
==========================
1.Is it SMP safe?
Yes. The old 2.0.xx channel bonding patch was not SMP safe.
The new driver was designed to be SMP safe from the start.
2.What type of cards will work with it?
Any Ethernet type cards (you can even mix cards - a Intel
EtherExpress PRO/100 and a 3com 3c905b, for example).
You can even bond together Gigabit Ethernet cards!
3.How many bonding devices can I have?
There is no limit.
4.How many slaves can a bonding device have?
Limited by the number of network interfaces Linux supports and/or the
number of network cards you can place in your system.
5.What happens when a slave link dies?
If your ethernet cards support MII or ETHTOOL link status monitoring
and the MII monitoring has been enabled in the driver (see description
of module parameters), there will be no adverse consequences. This
release of the bonding driver knows how to get the MII information and
enables or disables its slaves according to their link status.
See section on High Availability for additional information.
For ethernet cards not supporting MII status, the arp_interval and
arp_ip_target parameters must be specified for bonding to work
correctly. If packets have not been sent or received during the
specified arp_interval duration, an ARP request is sent to the
targets to generate send and receive traffic. If after this
interval, either the successful send and/or receive count has not
incremented, the next slave in the sequence will become the active
slave.
If neither mii_monitor and arp_interval is configured, the bonding
driver will not handle this situation very well. The driver will
continue to send packets but some packets will be lost. Retransmits
will cause serious degradation of performance (in the case when one
of two slave links fails, 50% packets will be lost, which is a serious
problem for both TCP and UDP).
6.Can bonding be used for High Availability?
Yes, if you use MII monitoring and ALL your cards support MII link
status reporting. See section on High Availability for more
information.
7.Which switches/systems does it work with?
In round-robin and XOR mode, it works with systems that support
trunking:
* Many Cisco switches and routers (look for EtherChannel support).
* SunTrunking software.
* Alteon AceDirector switches / WebOS (use Trunks).
* BayStack Switches (trunks must be explicitly configured). Stackable
models (450) can define trunks between ports on different physical
units.
* Linux bonding, of course !
In 802.3ad mode, it works with with systems that support IEEE 802.3ad
Dynamic Link Aggregation:
* Extreme networks Summit 7i (look for link-aggregation).
* Many Cisco switches and routers (look for LACP support; this may
require an upgrade to your IOS software; LACP support was added
by Cisco in late 2002).
* Foundry Big Iron 4000
In active-backup, balance-tlb and balance-alb modes, it should work
with any Layer-II switch.
8.Where does a bonding device get its MAC address from?
If not explicitly configured with ifconfig, the MAC address of the
bonding device is taken from its first slave device. This MAC address
is then passed to all following slaves and remains persistent (even if
the the first slave is removed) until the bonding device is brought
down or reconfigured.
If you wish to change the MAC address, you can set it with ifconfig:
# ifconfig bond0 hw ether 00:11:22:33:44:55
The MAC address can be also changed by bringing down/up the device
and then changing its slaves (or their order):
# ifconfig bond0 down ; modprobe -r bonding
# ifconfig bond0 .... up
# ifenslave bond0 eth...
This method will automatically take the address from the next slave
that will be added.
To restore your slaves' MAC addresses, you need to detach them
from the bond (`ifenslave -d bond0 eth0'). The bonding driver will then
restore the MAC addresses that the slaves had before they were enslaved.
9.Which transmit polices can be used?
Round-robin, based on the order of enslaving, the output device
is selected base on the next available slave. Regardless of
the source and/or destination of the packet.
Active-backup policy that ensures that one and only one device will
transmit at any given moment. Active-backup policy is useful for
implementing high availability solutions using two hubs (see
section on High Availability).
XOR, based on (src hw addr XOR dst hw addr) % slave count. This
policy selects the same slave for each destination hw address.
Broadcast policy transmits everything on all slave interfaces.
802.3ad, based on XOR but distributes traffic among all interfaces
in the active aggregator.
Transmit load balancing (balance-tlb) balances the traffic
according to the current load on each slave. The balancing is
clients based and the least loaded slave is selected for each new
client. The load of each slave is calculated relative to its speed
and enables load balancing in mixed speed teams.
Adaptive load balancing (balance-alb) uses the Transmit load
balancing for the transmit load. The receive load is balanced only
among the group of highest speed active slaves in the bond. The
load is distributed with round-robin i.e. next available slave in
the high speed group of active slaves.
High Availability
=================
To implement high availability using the bonding driver, the driver needs to be
compiled as a module, because currently it is the only way to pass parameters
to the driver. This may change in the future.
High availability is achieved by using MII or ETHTOOL status reporting. You
need to verify that all your interfaces support MII or ETHTOOL link status
reporting.On Linux kernel 2.2.17, all the 100 Mbps capable drivers and
yellowfin gigabit driver support MII. To determine if ETHTOOL link reporting
is available for interface eth0, type "ethtool eth0" and the "Link detected:"
line should contain the correct link status. If your system has an interface
that does not support MII or ETHTOOL status reporting, a failure of its link
will not be detected! A message indicating MII and ETHTOOL is not supported by
a network driver is logged when the bonding driver is loaded with a non-zero
miimon value.
The bonding driver can regularly check all its slaves links using the ETHTOOL
IOCTL (ETHTOOL_GLINK command) or by checking the MII status registers. The
check interval is specified by the module argument "miimon" (MII monitoring).
It takes an integer that represents the checking time in milliseconds. It
should not come to close to (1000/HZ) (10 milli-seconds on i386) because it
may then reduce the system interactivity. A value of 100 seems to be a good
starting point. It means that a dead link will be detected at most 100
milli-seconds after it goes down.
Example:
# modprobe bonding miimon=100
Or, put the following line in /etc/modprobe.conf:
options bond0 miimon=100
There are currently two policies for high availability. They are dependent on
whether:
a) hosts are connected to a single host or switch that support trunking
b) hosts are connected to several different switches or a single switch that
does not support trunking
1) High Availability on a single switch or host - load balancing
----------------------------------------------------------------
It is the easiest to set up and to understand. Simply configure the
remote equipment (host or switch) to aggregate traffic over several
ports (Trunk, EtherChannel, etc.) and configure the bonding interfaces.
If the module has been loaded with the proper MII option, it will work
automatically. You can then try to remove and restore different links
and see in your logs what the driver detects. When testing, you may
encounter problems on some buggy switches that disable the trunk for a
long time if all ports in a trunk go down. This is not Linux, but really
the switch (reboot it to ensure).
Example 1 : host to host at twice the speed
+----------+ +----------+
| |eth0 eth0| |
| Host A +--------------------------+Host B|
| +--------------------------+ |
| |eth1 eth1| |
+----------+ +----------+
On each host :
# modprobe bonding miimon=100
# ifconfig bond0 addr
# ifenslave bond0 eth0 eth1
Example 2 : host to switch at twice the speed
+----------+ +----------+
| |eth0 port1| |
| Host A +--------------------------+switch|
| +--------------------------+ |
| |eth1 port2| |
+----------+ +----------+
On host A : On the switch :
# modprobe bonding miimon=100 # set up a trunk on port1
# ifconfig bond0 addr and port2
# ifenslave bond0 eth0 eth1
2) High Availability on two or more switches (or a single switch without
trunking support)
---------------------------------------------------------------------------
This mode is more problematic because it relies on the fact that there
are multiple ports and the host's MAC address should be visible on one
port only to avoid confusing the switches.
If you need to know which interface is the active one, and which ones are
backup, use ifconfig. All backup interfaces have the NOARP flag set.
To use this mode, pass "mode=1" to the module at load time :
# modprobe bonding miimon=100 mode=active-backup
or:
# modprobe bonding miimon=100 mode=1
Or, put in your /etc/modprobe.conf :
options bond0 miimon=100 mode=active-backup
Example 1: Using multiple host and multiple switches to build a "no single
point of failure" solution.
| |
|port3 port3|
+-----+----+ +-----+----+
| |port7 ISL port7| |
| switch A +--------------------------+ switch B |
| +--------------------------+ |
| |port8 port8| |
+----++----+ +-----++---+
port2||port1 port1||port2
|| +-------+ ||
|+-------------+ host1 +---------------+|
| eth0 +-------+ eth1 |
| |
| +-------+ |
+--------------+ host2 +----------------+
eth0 +-------+ eth1
In this configuration, there is an ISL - Inter Switch Link (could be a trunk),
several servers (host1, host2 ...) attached to both switches each, and one or
more ports to the outside world (port3...). One and only one slave on each host
is active at a time, while all links are still monitored (the system can
detect a failure of active and backup links).
Each time a host changes its active interface, it sticks to the new one until
it goes down. In this example, the hosts are negligibly affected by the
expiration time of the switches' forwarding tables.
If host1 and host2 have the same functionality and are used in load balancing
by another external mechanism, it is good to have host1's active interface
connected to one switch and host2's to the other. Such system will survive
a failure of a single host, cable, or switch. The worst thing that may happen
in the case of a switch failure is that half of the hosts will be temporarily
unreachable until the other switch expires its tables.
Example 2: Using multiple ethernet cards connected to a switch to configure
NIC failover (switch is not required to support trunking).
+----------+ +----------+
| |eth0 port1| |
| Host A +--------------------------+switch|
| +--------------------------+ |
| |eth1 port2| |
+----------+ +----------+
On host A : On the switch :
# modprobe bonding miimon=100 mode=1 # (optional) minimize the time
# ifconfig bond0 addr # for table expiration
# ifenslave bond0 eth0 eth1
Each time the host changes its active interface, it sticks to the new one until
it goes down. In this example, the host is strongly affected by the expiration
time of the switch forwarding table.
3) Adapting to your switches' timing
------------------------------------
If your switches take a long time to go into backup mode, it may be
desirable not to activate a backup interface immediately after a link goes
down. It is possible to delay the moment at which a link will be
completely disabled by passing the module parameter "downdelay" (in
milliseconds, must be a multiple of miimon).
When a switch reboots, it is possible that its ports report "link up" status
before they become usable. This could fool a bond device by causing it to
use some ports that are not ready yet. It is possible to delay the moment at
which an active link will be reused by passing the module parameter "updelay"
(in milliseconds, must be a multiple of miimon).
A similar situation can occur when a host re-negotiates a lost link with the
switch (a case of cable replacement).
A special case is when a bonding interface has lost all slave links. Then the
driver will immediately reuse the first link that goes up, even if updelay
parameter was specified. (If there are slave interfaces in the "updelay" state,
the interface that first went into that state will be immediately reused.) This
allows to reduce down-time if the value of updelay has been overestimated.
Examples :
# modprobe bonding miimon=100 mode=1 downdelay=2000 updelay=5000
# modprobe bonding miimon=100 mode=balance-rr downdelay=0 updelay=5000
Promiscuous Sniffing notes
==========================
If you wish to bond channels together for a network sniffing
application --- you wish to run tcpdump, or ethereal, or an IDS like
snort, with its input aggregated from multiple interfaces using the
bonding driver --- then you need to handle the Promiscuous interface
setting by hand. Specifically, when you "ifconfing bond0 up" you
must add the promisc flag there; it will be propagated down to the
slave interfaces at ifenslave time; a full example might look like:
ifconfig bond0 promisc up
for if in eth1 eth2 ...;do
ifconfig $if up
ifenslave bond0 $if
done
snort ... -i bond0 ...
Ifenslave also wants to propagate addresses from interface to
interface, appropriately for its design functions in HA and channel
capacity aggregating; but it works fine for unnumbered interfaces;
just ignore all the warnings it emits.
8021q VLAN support
==================
It is possible to configure VLAN devices over a bond interface using the 8021q
driver. However, only packets coming from the 8021q driver and passing through
bonding will be tagged by default. Self generated packets, like bonding's
learning packets or ARP packets generated by either ALB mode or the ARP
monitor mechanism, are tagged internally by bonding itself. As a result,
bonding has to "learn" what VLAN IDs are configured on top of it, and it uses
those IDs to tag self generated packets.
For simplicity reasons, and to support the use of adapters that can do VLAN
hardware acceleration offloding, the bonding interface declares itself as
fully hardware offloaing 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.
VLAN interfaces *must* be added on top of a bonding interface only after
enslaving at least one slave. This is because until the fhrst slave is added the -
boneiNG interfaCe har a"HW addre?s of 00:00:00:00:00:00, which will be cop?ed by
the VLIN hnterface wjen it is created.
Notice that a problem would occur if all slaves are reneased from a bond that
r4ill has VLAJ internacEs on 4op of it. When later ?oming to add!new slaves, the
bonding?interface would get a HW address from tie first slave, whicH mighp not
match that of the VLAN interfaces. It is recommended that either !ml VLQFs are
?emowed and then rg-added, or to manuclly set the bonding interface's HW
address so it matches the WLAN's. (Note: changinc a VLAN interface's HW address
would set"the u.derlying eevice -- i.e. the bo?ding inturface -- to(prkmiscoums -
mgde, ?hich might not be what you want).
Limitations
===========
The }aan limitavions a2e :
- onl? the link status is monitored. If thu`switci on the othez side is
partially down (e.?.$dkesn't forward anymore, bu4 the link is!OK), the link
won't be di{abled. Annther way to check for a dead link could be to count
incoming frames on a heavily loaded host. This is not applicable to small
servers, but may be useful when the front switches send multicast
information on their links (e.g. VRRP), or even health-check the servers.
Use the arp_interval/arp_ip_target parameters to count incoming/outgoing
frames.
Resources and Links
===================
Current development on this driver is posted to:
- http://www.sourceforge.net/projects/bonding/
Donald Becker's Ethernet Drivers and diag programs may be found at :
- http://www.scyld.com/network/
You will also find a lot of information regarding Ethernet, NWay, MII, etc. at
www.scyld.com.
Patches for 2.2 kernels are at Willy Tarreau's site :
- http://wtarreau.free.fr/pub/bonding/
- http://www-miaif.lip6.fr/~tarreau/pub/bonding/
To get latest informations about Linux Kernel development, please consult
the Linux Kernel Mailing List Archives at :
http://www.ussg.iu.edu/hypermail/linux/kernel/
阅读：4 次
录入：情灭缘尽
【 评论 】 【 推荐 】 【 打印 】
[ 本帖最后由 情灭缘尽 于 2005-10-8 03:40 编辑 ] 沙发 如果二层交换机支持MLT（multink trunks）
ROS 负载均衡bonding 可不可用。。。 802.3ad 模式模式4
因为这个站贴图没我自己的站操作方便
这句我就完全不同意。
再者：昨天问的“推出”的定义，还没有听到比较完整的解释。
[ 本帖最后由 analyst 于 2005-10-8 10:20 编辑 ] 我自己写的东西发到我自己的站上的时候不需要一个一个的来贴图，然后一个一个的给地址，直接在word下写好了，另存为网页了，然后丢到ftp上，然后直接发出来，呵呵，而这个地方，如果用附件上载，全部在后面，不可以在文字中间插图片，如果用连接图片，要一个一个图片的连接地址，麻烦，多少年前就不用那种方法了，而且论坛都是使用的ubb，禁止了html了，很多地方不习惯，而且我也没多少时间在论坛上去研究怎么来发贴，如果你觉得这样不好我也没办法，毕竟论坛的功能和cms系统还是不一样的，后者在文章管理上比bbs强的多 原帖由 情灭缘尽 于 2005-10-8 10:29 发表
我自己写的东西发到我自己的站上的时候不需要一个一个的来贴图，然后一个一个的给地址，直接在word下写好了，另存为网页了，然后丢到ftp上，然后直接发出来，呵呵，而这个地方，如果用附件上载，全部在后面，不可 ...
如果这个算是回答了前者，姑且不问编辑一个dz的页面有多复杂，后面的那个问题呢？ 不过我觉得热拔插网卡，好像不是很安全吧！ 我一直比较鄙视到我们这里来套取成果然后到陈家迁的网站去发的鸟人!!! 楼主，你的2.9.2版的测试服务器好像也是100％cpu占用率啊，呵呵！ 我顶顶顶
留这回去研究，好帖子 惨了,我的主板点不亮了,楼主要赔我呦,你这个办法很害人,小弟们不要学,要学之前先买保险. 原帖由 legou 于 2005-10-8 14:41 发表
我认为楼主没有搞清楚 热拔插和 网卡冗余的 概念
热拔 的目的是为什么？
为了拔下来？？
这样我告诉你 基本 所有的 LINUX 或者UNIX 系统都可以拔
但是能插上去继续用吗？？？
从设备角度 需要支持 ...
可能网卡绑定用来分担流量多功能可能还要大些 和减少因为网卡故障减少的死机的功能要大些！
因为在实际上 热拔除网卡的可能性不是很大！