search for: arp_interv

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 ready bonding:...

...0 ASIX Electronics Corp. AX88772 Modprobe.conf: alias eth0 velocityget With the network service enabled (NetworkManager disabled), this is my setup: ifcfg-bond0: DEVICE=bond0 BOOTPROTO=none ONBOOT=yes IPADDR=10.6.0.90 NETMASK=255.255.255.0 GATEWAY=10.6.0.1 BONDING_OPTS="mode=active-backup arp_interval=300 primary=eth0 arp_ip_target=+10.6.0.1 arp_ip_target=+10.6.0.2" ifcfg-eth0: DEVICE=eth0 BOOTPROTO=none ONBOOT=yes IPADDR=10.6.0.90 NETMASK=255.255.255.0 GATEWAY=10.6.0.1 HWADDR=00:1F:F2:03:FA:45 MASTER=bond0 SLAVE=yes ifcfg-eth1: DEVICE=eth1 BOOTPROTO=none ONBOOT=yes IPADDR=10.6.1.90 N...

...+-B | | +-- tap1 (A)--- OpenVPN tunnel over 2Mbit ---- tap1 (B) ---+ I set up bond0 on both sides with tap0 as primary device using arpings: /sbin/modprobe -v bonding \ mode=1 \ primary=tap0 \ arp_interval=2000 \ arp_ip_target=10.1.0.1 (2 on the other end) bond0 (A) 10.1.0.1 bond0 (B) 10.2.0.1 When starting bond0 on both sides, everything is ok. When the 24Mbit line goes down, the 2Mbit line takes over within a few seconds as configured. But the line is not coming back to the primary 24Mbit...

...;, netmask => "255.255.255.0", gateway => "10.0.0.1", # rather than support a crapload of attributes like "bond_mode => active_backup", # use the new-style BONDING_OPTS variable extra_opts => "BONDING_OPTS=''mode=active-backup arp_interval=60 arp_ip_target=192.168.1.254''" } # slave interfaces for the bond networkinterface { "eth0": ensure => enabled, bond_master => bond0, } networkinterface { "eth1": ensure => enabled, bond_master => bond0, } ### ip aliases # this r...

...lure or similar. $ cat /sys/devices/virtual/net/bond0/bonding/{mode,arp_validate} active-backup 1 active 1 $ cat /etc/sysconfig/network-scripts/ifcfg-bond0 DEVICE=bond0 BOOTPROTO=static IPADDR=MYIP NETMASK=MYMASK NETWORK=MYNET BROADCAST=MYCAST ONBOOT=yes TYPE=Ethernet BONDING_OPTS="mode=1 arp_interval=500 arp_validate=1 arp_ip_target=GATEIP,GATE2IP primary=eth0" $ cat /proc/net/bonding/bond0 Ethernet Channel Bonding Driver: v3.6.0 (September 26, 2009) Bonding Mode: fault-tolerance (active-backup) Primary Slave: eth0 (primary_reselect always) Currently Active Slave: eth0 MII Status:...

...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: bonding: bond0: Add...

...ermanent HW addr: 00:80:1e:13:41:03 Slave Interface: eth1 MII Status: up Link Failure Count: 0 Permanent HW addr: 00:80:1e:13:39:05 both machines are running 2.4.26 kernel the configuration for both is the same (only the IPs are different): modules.conf: alias bond0 bonding options bond0 mode=0 arp_interval=1000 arp_ip_target=192.168.0.2 miimon=0 startup script: /sbin/modprobe bond0 /sbin/ip link set eth0 up multicast off /sbin/ip link set eth1 up multicast off /sbin/ip link set bond0 up multicast off /sbin/ip addr add 192.168.0.1/30 brd + dev bond0 /sbin/ifenslave bond0 eth0 eth1 Is this a bug, o...

...tc/modprobe.conf file was edited for bonding like below ----------------------------------------------------------------------------------------------- alias eth0 xennet alias scsi_hostadapter xenblk alias eth1 xennet alias bond0 bonding #options bond0 miimon=100 mode=1 primary=eth0 options bond0 arp_interval=1000 arp_ip_target=10.25.81.1,10.24.22.70 mode=1 primary=eth1 ----------------------------------------------------------------------------------------------- When switch port which currently active slave is connected (via eth1 in dom0) was down, this domU detected eth1 was no longer connected an...

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??

Hi all, Read many posts on the subject. Using 802.3ad. Few problems; Cannot ping some hosts on the network, they are all up. Cannot resolve via DNS which is one of the hosts that I cannot ping, internal nor external DNS hosts. Unplugging the NICS and plugging them back in will then not allow pining if the default d=gateway. When cold booting it somewhat works, some hosts are pingable while

...e1000: eth0: e1000_probe: Intel(R) PRO/1000 Network Connection ACPI: PCI interrupt 0000:12:01.0[A] -> GSI 120 (level, low) -> IRQ 59 e1000: eth1: e1000_probe: Intel(R) PRO/1000 Network Connection Ethernet Channel Bonding Driver: v2.6.0 (January 14, 2004) 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. Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2 ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx st: Version 20040403, fixed...

...vg0-swap. Priority:-1 extents:1 across:3903480k [ 49.565391] ip_tables: (C) 2000-2006 Netfilter Core Team [ 49.671327] nf_conntrack version 0.5.0 (16384 buckets, 65536 max) [ 49.937235] Ethernet Channel Bonding Driver: v3.2.5 (March 21, 2008) [ 49.937235] 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. [ 49.937739] bonding: bond0: setting mode to 802.3ad (4). [ 49.937739] bonding: bond0: Setting MII monitoring interval to 100. [ 49.937739] bonding: bond0: Se...