UNSOLVED
LACP Down Link Up, Remote Group different...
Hi,
Got a problem with a new Celerra install:
NS83G
5.6.44-4
One of my LACP trunks will not play ball.
The other two are fine.
Here is some output:
=====================================================
[nasadmin@tc-nas-cs ~]$ server_sysconfig server_2 -v -i lacp01
server_2 :
*** Trunk lacp01: Link is Up ***
*** Trunk lacp01: Timeout is Short ***
*** Trunk lacp01: Statistical Load Balancing is IP ***
Device Local Grp Remote Grp Link LACP Duplex Speed
------------------------------------------------------------------------
cge0 10000 12800 Up Up Full 1000 Mbs
cge1 10000 12800 Up Up Full 1000 Mbs
=====================================================
This is Good ^
=====================================================
[nasadmin@tc-nas-cs ~]$ server_sysconfig server_2 -v -i lacp02
server_2 :
*** Trunk lacp02: Link is Up ***
*** Trunk lacp02: Timeout is Short ***
*** Trunk lacp02: Statistical Load Balancing is IP ***
Device Local Grp Remote Grp Link LACP Duplex Speed
------------------------------------------------------------------------
cge2 10001 12800 Up Up Full 1000 Mbs
cge3 10001 12800 Up Up Full 1000 Mbs
=====================================================
This is also good ^
=====================================================
[nasadmin@tc-nas-cs ~]$ server_sysconfig server_2 -v -i lacp03
server_2 :
*** Trunk lacp03: Link is Up ***
*** Trunk lacp03: Timeout is Short ***
*** Trunk lacp03: Statistical Load Balancing is IP ***
Device Local Grp Remote Grp Link LACP Duplex Speed
------------------------------------------------------------------------
cge4 10002 14336 Up Down Full 1000 Mbs
cge5 10002 14080 Up Up Full 1000 Mbs
=====================================================
This is not so good ^
These all connect to a Cisco Nexus 7000 cores.
My network people set up all LACP trunks / port groups the same.
The only difference I can see is that the 'Remote Grp' number is different. What does this relate to, and do I need to change it?
Anything else I need to check to get this online? We've tried most things on the cores. Next step is to plug LACP2 cables into the LACP3 ports, see if the problem follows.
Regards
Richard.
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
6 Operator
•
8645 Posts
2346
1
Posted October 11th, 2011 05:00
Did you find out what the problem was ?
Rainer
christopher_ime
6 Operator
•
1962 Posts
2346
0
Posted 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
2346
0
Posted 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.
Rainer_EMC
6 Operator
•
8645 Posts
2346
0
Posted 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