search for: miimon

...y different options to the bonding module for each bond. I have tried every conceivable incantation of options and cannot get the kernel to recognize the second set of options. Initially, my modprobe.conf looked like this: alias bond0 bonding alias bond1 bonding options bonding mode=active-backup miimon=100 max_bonds=2 What I am trying to achieve should be possible by changing modprobe.conf to this: alias bond0 bonding options bond0 -o bond0 miimon=100 mode=active-backup primary=eth0 alias bond1 bonding options bond1 -o bond1 miimon=100 mode=active-backup primary=eth2 But this results in fatal...

Hi, I have been playing this weekend with bonding on PCI netcards and found that all of netcards I have, but old 3com, do not support MII. So bonding is not going to happen with them. Do you have some pci netcards supporting MII successfully running on bonging? Thanks, David Hrb??

...t;Public" network, bond0 created, it works fine, network --device=bond0 --noipv6 --bootproto=static --onboot=yes --hostname=box.example.com --ip=192.168.1.3 --netmask=255.255.255.0 --gateway=192.168.1.1 --nameserver=192.168.1.1 --bondslaves=p1p1,p1p2 --bondopts=mode=active-backup,primary=p1p1,miimon=80,updelay=60000 # Cluster network, not created on install network --device=bond1 --noipv6 --nodns --nodefroute --bootproto=static --onboot=yes --ip=192.168.2.2 --netmask=255.255.255.0 --bondslaves=em1,em2 --bondopts=mode=active-backup,primary=em1,miimon=80,updelay=60000 # ISCSI network network...

...NETMASK=255.255.0.0 NETWORK=10.0.0.0 TYPE=Unknown IPV6INIT=no ifcfg-eth0 DEVICE=eth0 BOOTPROTO=none ONBOOT=yes MASTER=bond0 SLAVE=yes USERCTL=no ifcfg-eth1 DEVICE=eth1 BOOTPROTO=none ONBOOT=yes MASTER=bond0 SLAVE=yes USERCTL=no /etc/modprob.d/bonding.conf alias bond0 bonding options bond0 mode=5 miimon=100 Bonding worked great in Centos 5.x, not so well for me in Centos 6.2. My goal is to get this working under bridging for KVM, I can only imagine the nightmare seeing I can't get a simple bond to work! Any guidance is golden. - aurf

...dd it to my rc.local but there must be a more elegant way. please see my configs below Thanks, Wessel ifcfg-bond0: DEVICE=bond0 IPADDR=xxx.xx.x.xx NETMASK=255.255.255.0 NETWORK=xxx.xx.x.xx BROADCAST=xxx.xx.x.xx GATEWAY= ONBOOT=yes BOOTPROTO=none USERCTL=no BONDING_MODULE_OPTS='mode=802.3ad miimon=80' TYPE=BOND ifcfg-eth0 (same for eth1,eth2 & eth3): # Intel Corporation 82576 Gigabit Network Connection DEVICE=eth0 ONBOOT=yes BOOTPROTO=none USERCTL=no MASTER=bond0 SLAVE=YES TYPE=ethernet HWADDR=xx:xx:xx:xx:xx:xx /etc/modprobe.conf: alias eth0 igb alias eth1 igb alias eth2 igb alias...

...I am looking at, with some things not added like hwaddress and a few tweaks (zeroconf?) am I even close? I admit I have never done this and have no mentor other than this exceptional mailing list. ============================ /etc/modprobe.conf alias bond0 bonding options bond0 mode=balance-alb miimon=100 ============================ ============================ bond0 DEVICE=bond0 BOOTPROTO=none BRIDGE=br0 ONBOOT=yes BONDING_OPTS="mode=1 miimon=100 primary=eth0" ============================ ============================ br0 DEVICE=br0 TYPE=Bridge BOOTPROTO=none IPADDR=<my virtual h...

.../sysconfig/network-scripts/ifcfg-bond0): TYPE=Bond BOOTPROTO=none DEFROUTE=yes IPV4_FAILURE_FATAL=yes NAME=bond0 DEVICE=bond0 ONBOOT=yes IPADDR=10.3.20.131 PREFIX=24 GATEWAY=10.3.20.1 DNS1=10.3.2.8 BONDING_MASTER=yes BONDING_OPTS="mode=802.3ad xmit_hash_policy=layer2 miimon=100" The slaves (two of them) are configured like TYPE=Ethernet BOOTPROTO=none NAME=bond0-slave0 DEVICE=em3 ONBOOT=yes MASTER=bond0 SLAVE=yes After booting, the routing table is 10.3.20.0/24 dev bond0 proto kernel scope link src 10.3.20.131 metric 300 with no default route...

...entOS 4.3. Some more relevant information is below (this display is consistent across all nodes): [smccl at tf35 ~]$uname -srvmpio Linux 2.6.9-34.ELhugemem #1 SMP Wed Mar 8 00:47:12 CST 2006 i686 i686 i386 GNU/Linux [smccl at tf35 ~]$head -5 /etc/modprobe.conf alias bond0 bonding options bonding miimon=100 mode=1 alias eth0 tg3 alias eth1 tg3 alias eth2 e100 [smccl at tf35 ~]$cat /proc/net/bonding/bond0 Ethernet Channel Bonding Driver: v2.6.1 (October 29, 2004) Bonding Mode: fault-tolerance (active-backup) Primary Slave: None Currently Active Slave: eth0 MII Status: up MII Polling Interval (ms...

...ng packages for using Xen from the Debian repository: xen-hypervisor-3.0.3-1-i386-pae linux-image-2.6.18-5-xen-686 linux-image-2.6.18-5-xen-686 xen-tools libc6-xen bridge-utils - Setup bonding like this: /etc/modprobe.d/arch/i386 ========================= alias bond0 bonding options bond0 mode=6 miimon=50 /etc/network/interfaces ======================= auto eth0 eth1 auto bond0 iface bond0 inet static address 10.3.4.2 netmask 255.255.255.0 network 10.3.4.0 broadcast 10.3.4.255 gateway 10.3.4.1 up /sbin/ifenslave bond0 eth0 down /sbin/ifenslave -d bond0...

...e network script in debian wheezy *** /etc/network/interfaces auto bond0 iface bond0 inet manual slaves eth0 eth1 bond-mode 0 auto br0 iface br0 inet static address 100.x.x.x netmask 255.255.255.0 network 100.x.x.0 broadcast 100.x.x.255 gateway 100.x.x.19 bridge_ports bond0 bond-miimon 100 bond-lacp_rate 1 bond-downdelay 200 bond-updelay 200 address 0.0.0.0 netmask 0.0.0.0 *** *** /etc/sysctl.conf #kernel.printk = 3 4 1 3 #net.ipv4.conf.default.rp_filter=1 #net.ipv4.conf.all.rp_filter=1 #net.ipv4.tcp_syncookies=1 net.ipv4.ip_...

...none > DEFROUTE=yes > IPV4_FAILURE_FATAL=yes > NAME=bond0 > DEVICE=bond0 > ONBOOT=yes > IPADDR=10.3.20.131 > PREFIX=24 > GATEWAY=10.3.20.1 > DNS1=10.3.2.8 > BONDING_MASTER=yes > BONDING_OPTS="mode=802.3ad xmit_hash_policy=layer2 miimon=100" > > The slaves (two of them) are configured like > > TYPE=Ethernet > BOOTPROTO=none > NAME=bond0-slave0 > DEVICE=em3 > ONBOOT=yes > MASTER=bond0 > SLAVE=yes > > After booting, the routing table is > > 10.3.20.0/24 dev bond0...

...ace lo inet loopback auto bond0 iface bond0 inet static ##bridge_ports eth0 address 192.168.1.150 netmask 255.255.255.0 network 192.168.1.0 broadcast 192.168.1.255 gateway 192.168.1.1 slaves eth0 eth2 bond-mode active-backup #bond-mode 802.3ad bond-miimon 100 bond-downdelay 200 bond-updelay 200 #auto xenbr0 #iface xenbr0 inet static # bridge_ports bond0 # #bridge_ports eth0 eth2 # address 192.168.1.150 # broadcast 192.168.1.255 # netmask 255.255.255.0 # gateway 192.168.1.1 auto bond1 iface bond1 inet static ##bridg...

...to mode 0 for active/active setup. Does mode 0 is dependent on the switches configuration? My setup is: 2 links from bonded interface is connected to different switches. When I change to mode0 from mode1 , bond0 is not coming up. These are the steps I performed 1) changed to options bond0 mode=0 miimon=100 from options bond0 mode=0 miimon=100 2) modprobe bonding 3) service network restart Thanks ! Paras. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.centos.org/pipermail/centos/attachments/20100113/fe04aeb8/attachment-0001.html>

...LACP trunk defined on the two ports. Problem is, when rebooting, I need to issue a `service network restart` to gain connectivity? There is nothing in messages that looks wrong? Anyone have an idea? kernel: Ethernet Channel Bonding Driver: v3.4.0 (October 7, 2008) kernel: bonding: Warning: either miimon or arp_interval and arp_ip_target module parameters must be specified, otherwise bonding will not detect link fail kernel: bonding: bond0: setting mode to 802.3ad (4). kernel: bonding: bond0: Setting MII monitoring interval to 500. kernel: ADDRCONF(NETDEV_UP): bond0: link is not ready kernel: bondi...

...etwork-scripts make valid entries for your bonded device and each slave. ifcfg-bond0: DEVICE=bond0 ONBOOT=no BOOTPROTO=none ifcfg-eth1/2/3: DEVICE=eth1/2/3 (replace as nessisary) USERCTL=no ONBOOT=yes MASTER=bond0 SLAVE=yes BOOTPROTO=none 9. Startup script /etc/rc.d/rc.local: modprobe bonding miimon=1* brctl addbr br0 brctl addif br0 eth0 sleep 10s** brctl addif br0 bond0 *miimon=1 means disable the port after one second on link down. This is the redundant part. If one of your links fail, the other two will keep working. ** The 'sleep' is to allow the bridge to stabilize. In testing...

Hello all, I'm having unusual difficulty configuring teaming with Centos 4.2. The 2 NIC's are Broadcom. The HW is HP DL360 and there is no teaming driver for RHEL4 since it comes with package (says HP). Since there is no teaming driver from centos (as far as I know), I tried the Broadcom Driver, configured the team file, but the team just wont come up. A Virtual Interface should be up

Getting "bnx2i: iSCSI not supported, dev=eth0" for all the NIC adapters on all of my R710's running CentOS 5.5. Here is an sample of the error messages: bonding: Warning: either miimon or arp_interval and arp_ip_target module parameters must be specified, otherwise bonding will not detect link failures! see bonding.txt for details. bonding: bond0: setting mode to active-backup (1). bonding: bond0: Setting MII monitoring interval to 500. ADDRCONF(NETDEV_UP): bond0: link is not r...

...the nics initialize in a different order. anaconda had setup /etc/modprobe.conf with alias lines for the cards: alias eth0 e1000 alias eth1 e1000e alias eth2 e1000e However, introducing the bonding driver into the mix seems to have thrown a wrench in the works. alias bond0 bonding options bond0 miimon=80 mode=5 #or something like that, can't get to the machine right now - no console and the network is down So, I read about the ifcfg options and try assigning each config script an HWADDR line. after rebooting, /var/log/messages announces that hardware address for eth1 does not match, skippi...

...ndary Floating : 192.168.13.83 IP Address (Assumed by currently active server) I have configured Ethernet Channel Bonding in Each Cluster Nodes and Channel Bonding Configuration Details are 1) Created bonding devices in "/etc/modprobe.conf" file alias bond0 bonding options bonding miimon=100 mode=1 2) Edit the "/etc/sysconfig/network-scripts/ifcfg-eth0 and ifcfg-eth1" configuration DEVICE=eth0 USERCTL= no ONBOOT=yes MASTER=bond0 SLAVE=yes BOOTPROTO=none DEVICE=eth1 USERCTL= no ONBOOT=yes MASTER=bond0 SLAVE=yes BOOTPROTO=none 3) Created a network...

...grep bond bond0 Link encap:Ethernet HWaddr 00:00:00:00:00:00 bond2 Link encap:Ethernet HWaddr XXXXXXXXXXXXXXXXX # cat /etc/sysconfig/network-scripts/ifcfg-bond2 DEVICE=bond2 IPADDR=XXXXXXXXX NETMASK=XXXXXXXX NETWORK=XXXXXXXXX USERCTL=no BOOTPROTO=none ONBOOT=yes BONDING_OPTS="mode=1 miimon=100" # cat /etc/sysconfig/network-scripts/ifcfg-eth2 DEVICE=eth2 MASTER=bond2 SLAVE=yes HWADDR=XXXXXXXXXXXX ONBOOT=yes BOOTPROTO=none USERCTL=no # cat /etc/sysconfig/network-scripts/ifcfg-eth3 DEVICE=eth3 MASTER=bond2 SLAVE=yes HWADDR=XXXXXXXXXX ONBOOT=yes BOOTPROTO=none USERCTL=no The bond...