The common issues with LACP configurations that I've seen are as follows. It is also fair to say that it is (almost) always an issue with the cabling or switch configuration:
1) Crossed cables (data mover interfaces not connected to switch ports that were aggregated)
I am suspecting as Rainer pointed out, that based on the output, this was the issue for the OP.
2) channel-group mode not set to active
This was correctly configured by the OP as seen in the output but worth mentioning:
Not sure if you had ever figured this out but we had a very similar issue with out VG2 as well. What we figured out is the switch side was configured wrong. You said you are using a Cisco Nexus 7000. On the Nexus 7000 your network team needs to look at the port and see if the ports are going into a disabled state. The reason I say that is because by default if the 7k does not see any LACP traffic on the port it will shut it down. There is a command on the 7k "no lacp suspend-individual" that will reverse that action on the switch and keep the interface up. the default command on the switches interface is "lacp suspend-individual" which disable the port if it does not receive and LACP control data. This is an interface command so you have to be in interface config mode for that particular interface. This is what resolve the issue for us.
Just to give a little more information the Nexus 5k's are the reverse of this. By default they have "no lacp suspend-individual" on the interface.
Rainer_EMC
4 Operator
•
8.6K Posts
0
November 24th, 2009 03:00
looks like a config error on the switch or you've got the wrong ports plugged in
I bet if you swap the cables for cge4 and cge5 the problem moves with it
ask your network guys so send you the config or diag output of the switch ports
Rainer
zdz2000
5 Posts
0
November 24th, 2009 04:00
We have been trying with just one interface (cge5) and one port channel for testing.
As soon as LACP is enabled, the channel goes down.
===================================
interface port-channel57
no description
switchport
switchport mode trunk
no switchport monitor
switchport trunk native vlan 999
switchport trunk allowed vlan 303
spanning-tree port-priority 128
spanning-tree cost auto
spanning-tree link-type auto
no spanning-tree bpduguard
no spanning-tree bpdufilter
logging event port link-status default
logging event port trunk-status default
speed auto
duplex auto
flowcontrol receive off
flowcontrol send off
mtu 1500
delay 1
bandwidth 1000000
no bandwidth inherit
storm-control broadcast level 100
storm-control multicast level 100
storm-control unicast level 100
load-interval counter 1 30
load-interval counter 2 300
no load-interval counter 3
no shutdown
no ip dhcp snooping trust
no ip arp inspection trust
no ip verify source dhcp-snooping-vlan
=================================================interface Ethernet8/38
no description
lacp port-priority 32768
lacp rate normal
cdp enable
switchport
switchport mode trunk
no switchport monitor
switchport trunk native vlan 999
switchport trunk allowed vlan 303
spanning-tree port-priority 128
spanning-tree cost auto
spanning-tree link-type auto
no spanning-tree bpduguard
no spanning-tree bpdufilter
speed auto
duplex auto
flowcontrol receive off
flowcontrol send off
link debounce
no beacon
mtu 1500
delay 1
snmp trap link-status
logging event port link-status default
logging event port trunk-status default
bandwidth 1000000
no bandwidth inherit
mdix auto
storm-control broadcast level 100
storm-control multicast level 100
storm-control unicast level 100
load-interval counter 1 30
load-interval counter 2 300
no load-interval counter 3
udld enable
channel-group 57 mode active
no shutdown
no ip dhcp snooping trust
no ip arp inspection trust
no ip verify source dhcp-snooping-vlan
==========================================
Regards
Richard
Rainer_EMC
4 Operator
•
8.6K Posts
1
October 11th, 2011 05:00
Did you find out what the problem was ?
Rainer
annet1
1 Message
0
May 7th, 2012 16:00
I have this exact problem and the switch people don't see a problem. Anyone solve it? Thanks.
christopher_ime
4 Operator
•
2K Posts
0
May 7th, 2012 22:00
The common issues with LACP configurations that I've seen are as follows. It is also fair to say that it is (almost) always an issue with the cabling or switch configuration:
1) Crossed cables (data mover interfaces not connected to switch ports that were aggregated)
I am suspecting as Rainer pointed out, that based on the output, this was the issue for the OP.
2) channel-group mode not set to active
This was correctly configured by the OP as seen in the output but worth mentioning:
channel-group # mode active
3) Useful commands when troubleshooting
Cisco switch:
==========
show lacp neighbor
show lacp neighbor detail
Celerra/VNX:
==========
server_sysconfig server_# -v -i
.server_config server_# -v "trunk lacpinfo"
EricShubbard
1 Message
0
November 9th, 2015 05:00
Not sure if you had ever figured this out but we had a very similar issue with out VG2 as well. What we figured out is the switch side was configured wrong. You said you are using a Cisco Nexus 7000. On the Nexus 7000 your network team needs to look at the port and see if the ports are going into a disabled state. The reason I say that is because by default if the 7k does not see any LACP traffic on the port it will shut it down. There is a command on the 7k "no lacp suspend-individual" that will reverse that action on the switch and keep the interface up. the default command on the switches interface is "lacp suspend-individual" which disable the port if it does not receive and LACP control data. This is an interface command so you have to be in interface config mode for that particular interface. This is what resolve the issue for us.
Just to give a little more information the Nexus 5k's are the reverse of this. By default they have "no lacp suspend-individual" on the interface.