10-09-2017 09:18 PM - edited 03-08-2019 12:19 PM
Trying to get LACP up between a single port on the 3850 switch stack and a 6800, its not working. This is the first time I have seen LACP not some up. If I remove the port-channel config the ports can trunk correctly. If I use PagP as the channel protocol it works fine. I have tried LACP active/active and active/passive as well.
I am at a loss as why this simple config is not working??
3850 switch
interface TenGigabitEthernet2/1/4
channel-group 1 mode passive
interface Port-channel1
switchport mode trunk
6800 switch
interface TenGigabitEthernet2/1/10
switchport
switchport mode trunk
channel-group 10 mode active
interface Port-channel10
switchport
switchport mode trunk
Group Port-channel Protocol Ports
------+-------------+-----------+-----------------------------------------------
1 Po1(SU) LACP Te2/1/4(w)
GOS-SVC-ASW-CD2-01#show switch
Switch/Stack Mac Address : f87b.2003.7980 - Local Mac Address
Mac persistency wait time: Indefinite
H/W Current
Switch# Role Mac Address Priority Version State
------------------------------------------------------------
*1 Active f87b.2003.7980 5 V02 Ready
2 Standby f87b.2003.3600 2 V02 Ready
GOS-SVC-ASW-CD2-01#show etherchannel 1 detail
Group state = L2
Ports: 1 Maxports = 16
Port-channels: 1 Max Port-channels = 16
Protocol: LACP
Minimum Links: 0
Ports in the group:
-------------------
Port: Te2/1/4
------------
Port state = Up Mstr Assoc Not-in-Bndl
Channel group = 1 Mode = Active Gcchange = -
Port-channel = Po1 GC = - Pseudo port-channel = Po1
Port index = 0 Load = 0x00 Protocol = LACP
Flags: S - Device is sending Slow LACPDUs F - Device is sending fast LACPDUs.
A - Device is in active mode. P - Device is in passive mode.
Local information:
LACP port Admin Oper Port Port
Port Flags State Priority Key Key Number State
Te2/1/4 SA bndl 32768 0x1 0x1 0x239 0xD
Partner's information:
LACP port Admin Oper Port Port
Port Flags Priority Dev ID Age key Key Number State
Te2/1/4 SA 32768 0200.0000.0067 23s 0x0 0xA 0x210B 0x75
Age of the port in the current state: 0d:00h:00m:20s
Port-channels in the group:
---------------------------
Port-channel: Po1 (Primary Aggregator)
------------
Age of the Port-channel = 0d:00h:12m:28s
Logical slot/port = 12/1 Number of ports = 1
HotStandBy port = null
Port state = Port-channel Ag-Inuse
Protocol = LACP
Port security = Disabled
Ports in the Port-channel:
Index Load Port EC state No of bits
------+------+------+------------------+-----------
0 00 Te2/1/4 Active 0
Time since last port bundled: 0d:00h:00m:20s Te2/1/4
Time since last port Un-bundled: 0d:00h:00m:23s Te2/1/4
Group Port-channel Protocol Ports
------+-------------+-----------+-----------------------------------------------
10 Po10(SD) LACP Te2/1/10(I)
GOS-SVC-DSW-CD1-01#show etherchannel 10 de
Group state = L2
Ports: 1 Maxports = 16
Port-channels: 1 Max Port-channels = 16
Protocol: LACP
Minimum Links: 0
Ports in the group:
-------------------
Port: Te2/1/10
------------
Port state = Up Sngl-port-Bndl Mstr Not-in-Bndl
Channel group = 10 Mode = Active Gcchange = -
Port-channel = null GC = - Pseudo port-channel = Po10
Port index = 0 Load = 0x00 Protocol = LACP
Flags: S - Device is sending Slow LACPDUs F - Device is sending fast LACPDUs.
A - Device is in active mode. P - Device is in passive mode.
Local information:
LACP port Admin Oper Port Port
Port Flags State Priority Key Key Number State
Te2/1/10 SA indep 32768 0xA 0xA 0x210B 0x7D
Age of the port in the current state: 0d:00h:02m:20s
Port-channels in the group:
----------------------
Port-channel: Po10 (Primary Aggregator)
------------
Age of the Port-channel = 0d:00h:03m:06s
Logical slot/port = 46/4 Number of ports = 0
HotStandBy port = null
Port state = Port-channel Ag-Not-Inuse
Protocol = LACP
Port security = Disabled
Fast-switchover = disabled
Fast-switchover Dampening = disabled
Load share deferral = disabled
Is fex host PO = FALSE
Last applied Hash Distribution Algorithm: -
10-09-2017 10:08 PM - edited 10-09-2017 10:10 PM
Hi,
Just to make sure, run this command on both side:
Config t
feature lacp
-If I helped you somehow, please, rate it as useful.-
10-10-2017 05:00 AM
feature command is not available on 3850 or 6800. These platforms are running IOS. I believe feature command is on Nexus platforms only.
3850(config)#feature lacp
^
% Invalid input detected at '^' marker.
3850 is running 03.07.04E
6800 running 15.4SY
10-11-2017 07:12 PM
i think this is CSCva22545 can someone from TAC confirm? what version do I need to upgrade to (bug toolkit is not working for some reason?)
11-20-2017 04:36 AM
Looks like, that the issue still exist in 3.7.5
After physical migration of all uplinks to the new distribution switches (ws-c3850-12xs-s) with cross-stack-etherchannel and LACP active/active we had the same problem. We had to reboot the switch, to get the etherchannel UP and running.
11-20-2017 05:54 AM - edited 11-20-2017 05:56 AM
Hello
int port x
lacp min-bundle 1
Can you also try creating this Port channel from scratch:
L2 etherchannel
1) default physical interfaces (if possible) & delete any existing PC referencing these interfaces
2) configure port-channel in physical interfaces
-- port-channel will be created automatically
3)create trunking encapsulation directly in port-channel interface
4)enable physical interfaces "no shut"
conf t
default int ran x/x -x ( if applicable)
int ran x/x -x
shut ( if applicable)
channel-group 1 mode active
int port-channel 1
lacp min-bundle 1
switchport- mode trunk
res
Paul
11-20-2017 05:58 AM
Yeah, we put the phy. interfaces back to default and deleted the port-channel interface. But after reconfiguring the interfaces, the result was still the same.
What we didn't try was: lacp min-bundle 1
regards
~chris
07-05-2018 10:19 AM
I have run into similar issues with this code train. If I recall correctly, most of the open caveats for the 3.7.x release are LACP related. Also, you should note that the 3.7.x releases have a history of becoming deferred. I would recommend looking at upgrading to the Denali 16.3.x release for the 3850 platform in order to resolve your issue.
In our case when we were creating port-channels we had the native vlan shutdown and would receive the error message that LACP was not configured on the remote end. When the native vlan was not shutdown the port-channel would come up. Shutting down the vlan should only prevent it from forwarding locally within the switch, but still allow data to be forwarded out to establish the port-channel. My observation is that there an issue with LACP packets being forwarded across the native vlan which is preventing the negotiation from taking place. Upgrading to 16.3.6 has fixed this issue for us and we have not experienced any LACP related issues since.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide