01-18-2023 02:26 PM
Hi,
we have a ASR920 facing an ASR9K with 2 10G Link.
We have configured Port Channel on ASR920 like this:
interface Port-channel1
description ***LAG***
no ip address
no negotiation auto
service instance 1 ethernet
encapsulation untagged
l2protocol peer stp dot1x lacp
bridge-domain 1
!
service instance 2 ethernet
encapsulation dot1q 2 second-dot1q 1-4094
bridge-domain 2
The 2 single port like this:
interface TenGigabitEthernet0/0/24
description ***port1***
no ip address
udld port
channel-group 1 mode active
!
interface TenGigabitEthernet0/0/25
description ***port2***
no ip address
udld port
channel-group 1 mode active
!
We do not have control of ASR9K, is a router of the carrier.
The Port Channel 1 is down/down on ASR920, LACP not negotiate and the sh etherchannel summary report this:
sh etherchannel summary
Flags: D - down P/bndl - bundled in port-channel
I - stand-alone s/susp - 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: 1
Number of aggregators: 1
Group Port-channel Protocol Ports
------+-------------+-----------+-----------------------------------------------
1 Po1(RD) LACP Te0/0/24(susp) Te0/0/25(susp)
RU - L3 port-channel UP State
SU - L2 port-channel UP state
P/bndl - Bundled
S/susp - Suspended
The status seems in L3 and not L2, the port channel don't bring up protocol, where is/are the problem?
01-18-2023 11:06 PM
>....We do not have control of ASR9K, is a router of the carrier.
- It will be difficult to resolve this issue then, at least feedback on remote configuration such be given and logs , also different LACP modes should be tried and be able to do so at both sides ,
M.
01-19-2023 12:03 AM
Hello
Are you supposed to be bridging towards the ISP or should it be a pure layer LAG?
01-19-2023 01:42 AM
We have the configuration of end point of the carrier:
bundle
interface Bundle-Ether185
description FO
mtu 9144
load-interval 30
dampening
and interface:
description FO
bundle id 185 mode active
lacp period short
carrier-delay up 1000 down 0
load-interval 30
dampening
01-19-2023 04:46 AM
- You need to debug with the carrier such as asking interface status(es) , counters , logs , ... (when connection attempt is being made)
M.
01-19-2023 03:00 PM
This is a debug lacp all on my ASR920:
*Jan 19 22:30:56.791: LACP: update_Selected_Actor: Actor LAG components have changed,Unselecting Te0/0/24.
*Jan 19 22:30:56.791: LACP: lacp_insert_partner_cd_inhibitor: didn't change sync flag.
*Jan 19 22:30:56.791: LACP: lacp_handle_standby_port: No Standby port found for LAG 1
*Jan 19 22:30:57.190: LACP: lacp_insert_partner_cd_inhibitor: didn't change sync flag.
*Jan 19 22:30:57.459: LACP: lacp_insert_partner_cd_inhibitor: didn't change sync flag.
*Jan 19 22:30:57.801: LACP: update_Selected_Actor: Actor LAG components have changed,Unselecting Te0/0/24.
*Jan 19 22:30:57.801: LACP: lacp_insert_partner_cd_inhibitor: didn't change sync flag.
*Jan 19 22:30:57.801: LACP: lacp_handle_standby_port: No Standby port found for LAG 1
*Jan 19 22:30:58.134: LACP: lacp_insert_partner_cd_inhibitor: didn't change sync flag.
*Jan 19 22:30:58.410: LACP: lacp_insert_partner_cd_inhibitor: didn't change sync flag.
*Jan 19 22:30:58.811: LACP: update_Selected_Actor: Actor LAG components have changed,Unselecting Te0/0/24.
*Jan 19 22:30:58.811: LACP: lacp_insert_partner_cd_inhibitor: didn't change sync flag.
*Jan 19 22:30:58.811: LACP: lacp_handle_standby_port: No Standby port found for LAG 1
*Jan 19 22:30:59.058: LACP: lacp_insert_partner_cd_inhibitor: didn't change sync flag.
*Jan 19 22:30:59.290: LACP: lacp_insert_partner_cd_inhibitor: didn't change sync flag.
*Jan 19 22:30:59.821: LACP: update_Selected_Actor: Actor LAG components have changed,Unselecting Te0/0/24.
*Jan 19 22:30:59.821: LACP: lacp_insert_partner_cd_inhibitor: didn't change sync flag.
*Jan 19 22:30:59.821: LACP: lacp_handle_standby_port: No Standby port found for LAG 1
*Jan 19 22:30:59.942: LACP: lacp_insert_partner_cd_inhibitor: didn't change sync flag.
*Jan 19 22:31:00.186: LACP: lacp_insert_partner_cd_inhibitor: didn't change sync flag.
*Jan 19 22:31:00.831: LACP: update_Selected_Actor: Actor LAG components have changed,Unselecting Te0/0/24.
01-20-2023 09:45 AM
Here is the debug show from the ASR9K of carrier ethernet:
show bundle bundle-ether 185
Bundle-Ether185
Status: Down
Local links <active/standby/configured>: 0 / 0 / 2
Local bandwidth <effective/available>: 0 (0) kbps
MAC address (source): b026.806b.ea29 (Chassis pool)
Inter-chassis link: No
Minimum active links / bandwidth: 1 / 1 kbps
Maximum active links: 64
Wait while timer: 2000 ms
Load balancing:
Link order signaling: Not configured
Hash type: Default
Locality threshold: None
LACP: Operational
Flap suppression timer: Off
Cisco extensions: Disabled
Non-revertive: Disabled
mLACP: Not configured
IPv4 BFD: Not configured
IPv6 BFD: Not configured
Port Device State Port ID B/W, kbps
-------------------- --------------- ----------- -------------- ----------
Te0/4/0/3 Local Negotiating 0x8000, 0x0030 10000000
Partner has not echoed the correct parameters for this link
Te0/4/0/4 Local Negotiating 0x8000, 0x002f 10000000
Partner has not echoed the correct parameters for this link
Have you any idea of configuration problem or interoperability problem?
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