Displaying 3 results from an estimated 3 matches for "fail_over_mac".
2017 Jan 12
1
[Security Advisory] RHSA-2017:0036 Important: kernel security and bug fix update
...system. This update fixes the underlying
source code, and sysfs now shows the DMI information as expected.
(BZ#1393464)
* Previously, bonding mode active backup and the propagation of the media
access control (MAC) address to a VLAN interface did not work in Red Hat
Enterprise Linux 6.8, when the fail_over_mac bonding parameter was set to
fail_over_mac=active. With this update, the underlying source code has been
fixed so that the VLANs continue inheriting the MAC address of the active
physical interface until the VLAN MAC address is explicitly set to any
value. As a result, IPv6 EUI64 addresses for the...
2019 Sep 20
0
7.7.1908, interface bonding, and default route
...e upgrade to 1908, I
didn't experience the problem you had, I can't see anything out of the
ordinary in your network files.
I originally set 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...
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