Displaying 6 results from an estimated 6 matches for "use_carri".
Did you mean:
use_carrier
2008 Dec 01
4
Bonding and network cards
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??
2009 Nov 16
3
[PATCH] Add support for vendor hooks during ovirt-early start()
Add a kernel parameter, vendor= which takes a path to a script
embedded in the image. If this script is executable, we will then
source it during ovirt-early start() after command line processing
and before mounting of /config. We also call a post hook at the end of
ovirt-early start().
Also include a sample vendor script.
Signed-off-by: Ryan Harper <ryanh at us.ibm.com>
---
2019 Sep 20
0
7.7.1908, interface bonding, and default route
...et up my bond using nmtui
Here is my configuration:
#Bond:
BONDING_OPTS="ad_select=stable all_slaves_active=0 arp_all_targets=any
downdelay=0 fail_over_mac=none lp_interval=1 miimon=100 min_links=0
mode=802.3ad num_grat_arp=1 num_unsol_na=1 primary_reselect=always
resend_igmp=1 updelay=0 use_carrier=1 xmit_hash_policy=layer2"
TYPE=Bond
BONDING_MASTER=yes
PROXY_METHOD=none
BROWSER_ONLY=no
BOOTPROTO=none
IPADDR=a.b.c.249
PREFIX=24
GATEWAY=a.b.c.1
DNS1=a.b.d.253
DNS2=a.b.d.4
DNS3=a.b.d.12
DOMAIN=redacted.net
DEFROUTE=yes
IPV4_FAILURE_FATAL=no
IPV6INIT=yes
NAME="Bond connection 1"...
2019 Sep 20
2
7.7.1908, interface bonding, and default route
Hi!
I just upgraded a machine to 7.7.1908 and the default route is not being
set on boot. This particular server has a bonded interface, and the
corresponding configuration for the master is (
/etc/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
2007 Apr 12
1
bonding
I four nodes setup to do active-backup bonding and the drivers loaded
for the bonded network interfaces vary between tg3 and e100. All
interfaces with the e100 driver loaded report errors much like what you
see here:
bonding: bond0: link status definitely down for interface eth2,
disabling it
e100: eth2: e100_watchdog: link up, 100Mbps, full-duplex
bonding: bond0: link status definitely up for
2019 Feb 06
2
Pb with bounding
...s
NM_CONTROLLED=no
- the bond0 declaration:
:/etc/sysconfig/network-scripts# cat ifcfg-bond0
DEVICE=bond0
TYPE=Ethernet
BONDING_MASTER=yes
BOOTPROTO=none
ONBOOT=yes
NM_CONTROLLED=no
# IP
IPADDR=172.16.1.128
PREFIX=16
GATEWAY=172.16.0.254
# Bonding
BONDING_OPTS="mode=802.3ad ad_select=stable use_carrier=1 miimon=100 arp_ip_target=172.16.1.128 updelay=100 lacp_rate=fast"
USERCTL=no
After a ? systemctl restart network ?:
:/etc/sysconfig/network-scripts# ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 b...