Aim
The aim is to setup LACP.
/etc/modprobe.d/bonding.conf
alias bond0 bonding
options bond0 miimon=100 mode=4 lacp_rate=1
/etc/sysconfig/network-scripts/ifcfg-bond0
ONBOOT=yes
BOOTPROTO=static
USERCTL=no
DEVICE=bond0
IPADDR=X
GATEWAY=Y
PREFIX=24
/etc/sysconfig/network-scripts/ifcfg-eth0
ONBOOT=yes
BOOTPROTO=static
USERCTL=no
DEVICE=eth0
MASTER=bond0
SLAVE=yes
Etherchannel
switch#show etherchannel X summary
Flags: D - down P - bundled in port-channel
I - stand-alone s - suspended
H - Hot-standby (LACP only)
R - Layer3 S - Layer2
U - in use f - failed to allocate aggregator
M - not in use, minimum links not met
u - unsuitable for bundling
w - waiting to be aggregated
d - default port
Number of channel-groups in use: 3
Number of aggregators: 3
Group Port-channel Protocol Ports
------+-------------+-----------+-----------------------------------------------
X PoX(SD) LACP Gi0/A(I) Gi0/B(I) Gi0/C(I)
Gi0/D(I)
interface Port-channelX
switchport mode access
!
Ports
interface GigabitEthernet0/A
switchport access vlan X
switchport mode access
channel-protocol lacp
channel-group X mode active
!
Log
Mar 2 11:17:50.529: %SW_MATM-4-MACFLAP_NOTIF: Host <MAC_ADDRESS> in vlan X is flapping
between port Gi0/Y and port Gi0/Z
Questions
Once the network service has been restarted on the Linux server the slave ethernet adapters are up and the system is still accessible:
- Why does the Cisco log indicate that the host is flapping between the ports?
- Why could the system be accessed while the portchannel is down?
show etherchannel summary
means exactly what it says in the key:I - stand-alone
. Since the ports are acting as stand-alone interfaces, they are not bundled into the etherchannel and the mac-flapping is expected. You need to fix the channel configuration for this to work correctly, there are probably other log messages that provide more detail for this. Also the output ofshow etherchannel ## detail
should be helpful.