09-29-2023 07:56 AM
Hello.
I have a setup like this:
Where both sites are connected trough a bridge.
The issue here is that the bundle is not load-balancing, the traffic is flowing only through one of the links
The customer runs mpls between this two sites and on top pppoe.
We have duplicated the scenario running only ip and it seems that the load-balancing is working properly, so we can conclude that the load balancing is not working (is working but src and dst mac address are always the same) becouse of the encapsulations used by the costumer.
Here are the configs for the setup:
l2vpn
load-balancing flow src-dst-ip
bridge group x
bridge-domain x
interface TenGigE0/0/2/2.3116
!
interface Bundle-Ether102.3116
!
!
!
!
Bundle-Ether102
Status: Up
Local links <active/standby/configured>: 2 / 0 / 2
Local bandwidth <effective/available>: 2000000 (2000000) kbps
MAC address (source): e0ac.f170.0ccc (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
-------------------- --------------- ----------- -------------- ----------
Gi1502/0/0/0 Local Active 0x8000, 0x0005 1000000
Link is Active
Gi1502/0/0/1 Local Active 0x8000, 0x0006 1000000
Link is Active
Satellite 1502
--------------
Status: Connected (Stable)
Type: asr9000v
Description: x
Displayed device name: Sat1502
MAC address: f07f.0613.xxxx
IPv4 address: x (auto, VRF: **nVSatellite)
Serial Number: CAT1840U2H2
Remote version: Compatible (older version)
ROMMON: 128.0 (Latest)
FPGA: 1.13 (Latest)
IOS: 642.102 (Available: 713.100)
Received candidate fabric ports:
nVFabric-GigE0/0/42-43 (permanent)
nVFabric-TenGigE0/0/44-47 (permanent)
Configured satellite fabric links:
TenGigE0/0/2/3
--------------
Status: Satellite Ready
Remote ports: GigabitEthernet0/0/0-43
interface GigabitEthernet1502/0/0/0
bundle id 102 mode active
speed 1000
!
interface GigabitEthernet1502/0/0/1
bundle id 102 mode active
speed 1000
!
Wed Sep 27 09:16:51.891 ART
State: a - Port is marked as Aggregatable.
s - Port is Synchronized with peer.
c - Port is marked as Collecting.
d - Port is marked as Distributing.
A - Device is in Active mode.
F - Device requests PDUs from the peer at fast rate.
D - Port is using default values for partner information.
E - Information about partner has expired.
Bundle-Ether102
Port (rate) State Port ID Key System ID
-------------------- -------- ------------- ------ ------------------------
Local
Gi1502/0/0/0 30s ascdA--- 0x8000,0x0005 0x0066 0x8000,e0-ac-f1-70-0c-c5
Partner 30s ascdA--- 0x00ff,0x0001 0x0011 0xffff,2c-c8-1b-fd-ce-1b
Gi1502/0/0/1 30s ascdA--- 0x8000,0x0006 0x0066 0x8000,e0-ac-f1-70-0c-c5
Partner 30s ascdA--- 0x00ff,0x0002 0x0011 0xffff,2c-c8-1b-fd-ce-1b
Port Receive Period Selection Mux A Churn P Churn
-------------------- ---------- ------ ---------- --------- ------- -------
Local
Gi1502/0/0/0 Current Slow Selected Distrib None None
Gi1502/0/0/1 Current Slow Selected Distrib None None
And here are the interfaces been monitored:
Protocol:General
Interface In(bps) Out(bps) InBytes/Delta OutBytes/Delta
Gi1502/0/0/0 0/ 0% 831.9M/ 83% 39.1G/88 53.2T/221.4M
Gi1502/0/0/1 81.9M/ 8% 0/ 0% 5.1T/23.6M 737.8G/190
Quit='q', Clear='c', Freeze='f', Thaw='t',
Next set='n', Prev set='p', Bytes='y', Packets='k'
(General='g', IPv4 Uni='4u', IPv4 Multi='4m', IPv6 Uni='6u', IPv6 Multi='6m')
Here is a capture of the traffic runn through the brigde wher you can see the encapsulation used by the costumer.
I have tried every posible way of "cef load-balancing algorithm adjust" with no result and even changed the bundle load-balance in the interface level with also not luck.
Now with all this said is there any way were I can correctly load balance this type of traffic in the bundle?
10-04-2023 11:22 AM
Hi There,
The problem is the MPLS header here. On ASR9k we do support looking behind the PPPoE header but only in case of PPPoE following the ethernet. We can NOT do it with MPLS in between unfortunately.
Niko
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