How to Configure Bridge Network on Bonded Interface in RHEL 6

Configure Bridge Network on Bonded Interface in RHEL 6

1. Create Bond First. Create Interface network Config file for bonding. For More information on Bonding please refer the links for RHEL6 & RHEL7.



[root@example.com ~]# cat /etc/sysconfig/network-scripts/ifcfg-em3 -- Configuration of 1st Slave Interface

DEVICE=em3
TYPE=Ethernet
UUID=a3...............12
ONBOOT=yes 
NM_CONTROLLED=no
HWADDR=XX:XX.......:XX
MASTER=bond0 --- Bond Name
SLAVE=yes

[root@example.com ~]# cat /etc/sysconfig/network-scripts/ifcfg-em4 -- Configuration of 2nd Slave Interface

DEVICE=em4
TYPE=Ethernet
UUID=10...............c3
ONBOOT=yes
NM_CONTROLLED=no
HWADDR=XX:XX.......:XX
IPV4_FAILURE_FATAL=yes
MASTER=bond0
SLAVE=yes

[root@example.com ~]# cat /etc/sysconfig/network-scripts/ifcfg-bond0 -- Configuration of Master Interface

DEVICE=bond0
TYPE=Bond
ONBOOT=yes
NM_CONTROLLED=no
BOOTPROTO=none
BRIDGE=br0 --- Bridge Interface name

[root@example.com ~]# cat /etc/sysconfig/network-scripts/ifcfg-br0 -- Configuration of Bridge Network

DEVICE=br0 -- Bridge Network
TYPE=Bridge
IPADDR=IP value -- Bridge network will have IP details instead of Bond.
NETMASK=Netmask value
GATEWAY=Gateway value
ONBOOT=yes
BOOTPROTO=none
NM_CONTROLLED=no
DELAY=0

2. Now restart the Network service.

service network restart

3. Check the bridge Network.

[root@example.com ~]# brctl show
bridge name     bridge id               STP enabled     interfaces
br0             8000.44a842460e99       no              bond0
                                                        vnet0
                                                        vnet1
virbr0          8000.525400bbaeb4       yes             virbr0-nic

[root@example.com ~]# cat /etc/redhat-release
Red Hat Enterprise Linux Server release 6.7 (Santiago)
[root@example.com ~]#

4. Check the details.

[root@example.com ~]# ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: em1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN qlen 1000
    link/ether XX:XX.......:XX brd ff:ff:ff:ff:ff:ff
3: em2: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN qlen 1000
    link/ether XX:XX.......:XX brd ff:ff:ff:ff:ff:ff
4: em3: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc mq master bond0 state UP qlen 1000 -- slave Inteface
    link/ether XX:XX.......:XX brd ff:ff:ff:ff:ff:ff
5: em4: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc mq master bond0 state UP qlen 1000 -- slave Inteface
    link/ether XX:XX.......:XX brd ff:ff:ff:ff:ff:ff
6: bond0: <BROADCAST,MULTICAST,MASTER,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP
    link/ether XX:XX.......:XX brd ff:ff:ff:ff:ff:ff
    inet6 fe80::46a8:42ff:fe46:e99/64 scope link
       valid_lft forever preferred_lft forever
7: br0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN
    link/ether XX:XX.......:XX brd ff:ff:ff:ff:ff:ff
    inet x.x.x.x/xx brd Gateway IP27 scope global br0
    inet6 fe80::46a8:42ff:fe46:e99/64 scope link
       valid_lft forever preferred_lft forever
8: virbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN
    link/ether XX:XX.......:XX brd ff:ff:ff:ff:ff:ff
    inet 192.168.122.1/24 brd 192.168.122.255 scope global virbr0
9: virbr0-nic: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN qlen 500
    link/ether XX:XX.......:XX brd ff:ff:ff:ff:ff:ff
11: vnet0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN qlen 500
    link/ether XX:XX.......:XX brd ff:ff:ff:ff:ff:ff
    inet6 fe80::fc54:ff:fecd:1265/64 scope link
       valid_lft forever preferred_lft forever
12: vnet1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN qlen 500
    link/ether XX:XX.......:XX brd ff:ff:ff:ff:ff:ff
    inet6 fe80::fc54:ff:fe9d:275b/64 scope link
       valid_lft forever preferred_lft forever