LinuxQuestions.org - bonding (mode=1) above (mode=4) lacp

- Linux - Networking (https://www.linuxquestions.org/questions/linux-networking-3/)

- - bonding (mode=1) above (mode=4) lacp (https://www.linuxquestions.org/questions/linux-networking-3/bonding-mode%3D1-above-mode%3D4-lacp-4175479080/)

bonding (mode=1) above (mode=4) lacp

Hi

Is it possible to setup below picture ?
Attachment 13575

Requirements :
- 2 different stack lan switches
- lacp on 2 x 1Gb
- Active/Stdby (mode=1) bonding on lacp (mode=4)

Quote:

Originally Posted by drManhattan (Post 5037367)

Hi

Is it possible to setup below picture ?
Attachment 13575

Requirements :
- 2 different stack lan switches
- lacp on 2 x 1Gb
- Active/Stdby (mode=1) bonding on lacp (mode=4)

Your diagrams none too clear, but if I read it right I don't see why not. This is a pretty common setup. Set up two lacp bundles and use them as active/standby interfaces.

Couldn't tell you exactly how with Linux, but I've set up the network sidee to Solaris, Windows and Linux hosts. Google should show you the way :-)

I have setup two lacp bundles as you suggested @baldy3105.
My oes is RHEL6.4 and below are network configs from my server :

File : /etc/sysconfig/network-scripts/ifcfg-eth1

Code:

DEVICE="eth1"

BOOTPROTO="none"

NM_CONTROLLED="no"

ONBOOT="yes"

TYPE="Ethernet"

SLAVE=yes

MASTER=bond0

File : /etc/sysconfig/network-scripts/ifcfg-eth2

Code:

DEVICE="eth2"

BOOTPROTO="none"

NM_CONTROLLED="no"

ONBOOT="yes"

TYPE="Ethernet"

SLAVE=yes

MASTER=bond1

File : /etc/sysconfig/network-scripts/ifcfg-eth3

Code:

DEVICE="eth3"

BOOTPROTO="none"

NM_CONTROLLED="no"

ONBOOT="yes"

TYPE="Ethernet"

SLAVE=yes

MASTER=bond0

File : /etc/sysconfig/network-scripts/ifcfg-eth4

Code:

DEVICE="eth4"

BOOTPROTO="none"

NM_CONTROLLED="no"

ONBOOT="yes"

TYPE="Ethernet"

SLAVE=yes

MASTER=bond1

And bonded device LACP.

File : /etc/sysconfig/network-scripts/ifcfg-bond0

Code:

DEVICE=bond0

ONBOOT=yes

BOOTPROTO=static

BONDING_OPTS="mode=4 miimon=100 min_links=2 lacp_rate=1"

TYPE=Bonding

IPADDR=192.168.122.10

NETMASK=255.255.255.0

BROADCAST=192.168.122.255

DELAY=0

MTU=1500

File : /etc/sysconfig/network-scripts/ifcfg-bond1

Code:

DEVICE=bond1

ONBOOT=yes

BOOTPROTO=static

BONDING_OPTS="mode=4 miimon=100 min_links=2 lacp_rate=1"

TYPE=Bonding

IPADDR=192.168.122.11

NETMASK=255.255.255.0

BROADCAST=192.168.122.255

DELAY=0

MTU=1500

Now I don't know how to create on top of bond0 and bond1 devices, new device (mode=1 active/stdby).
I would like to create one device with IP e.g. 192.168.122.10 in mode=1 that is built from 2 devices in mode=4 : bond0 and bond1.
Could you explain me, how to make that happen ?

Ok I got this. I know howto manually configure it.
I changed ifcfg-bond0 and ifcfg-bond1 to this structure, basicaly added "SLAVE" variable :

File: ifcfg-bond0

Code:

DEVICE=bond0

ONBOOT=yes

BOOTPROTO=static

BONDING_OPTS="mode=4 miimon=100 min_links=2 lacp_rate=1"

TYPE=Bonding

IPADDR=192.168.122.10

NETMASK=255.255.255.0

BROADCAST=192.168.122.255

DELAY=0

MTU=1500

SLAVE=no

File: ifcfg-bond1

Code:

DEVICE=bond1

ONBOOT=yes

BOOTPROTO=static

BONDING_OPTS="mode=4 miimon=100 min_links=2 lacp_rate=1"

TYPE=Bonding

IPADDR=192.168.122.10

NETMASK=255.255.255.0

BROADCAST=192.168.122.255

DELAY=0

MTU=1500

SLAVE=yes

But now I am able to switchover IP 192.168.122.10 between bond0 and bond1 manualy by typing

Code:

ifdown bond0;ifup bond1

But this operation costs me loosing TCP/IP packets.
Is it possible for RHEL to discover automatically that bond0/1 interface failed and to failover IP automaticaly ?