Hi
I have an issue where LACP traffic is being punted to the route processor on EX4500 even though layer2-protocol-tunneling has been enabled on the relevant VLAN. I have tried this with the trunk port having only the tunneled VLAN, a combination of tunneled and untunneled VLANs or all tunneled VLANS. The issue is the same:
Model: ex4500-40f
Junos: 14.1X53-D49.1
I have the following configuration which enables dot1q tunneling.
vl267 {
vlan-id 267;
}
vl400 {
vlan-id 400;
dot1q-tunneling {
layer2-protocol-tunneling {
all;
}
}
}
I have the following configuration facing the carrier PE/NNI:
show interfaces xe-0/0/37
mtu 1552;
unit 0 {
family ethernet-switching {
port-mode trunk;
vlan {
members [ vl400 vl267 ]
}
}
}
> monitor traffice interface xe-0/0/37 no-resolve layer2-headers
Listening on xe-0/0/37, capture size 96 bytes
21:26:43.176559 In 20:x:x:x:x:x > 01:80:c2:00:00:02, ethertype 802.1Q (0x8100), length 74: vlan 400, p 0, ethertype Slow Protocols, LACPv1, length 56
As you can see, the LACP packet is being punted to the route processor because otherwise it would not be seen in monitor traffic output. I do not see any LACP packets turn up on access or trunk interfaces on the same VLAN which means it is being consumed by the control plane and not forwarded. I have also confirmed this with an analyzer port.
> show ethernet-switching layer2-protocol-tunneling statistics vlan 400
...
vl400 xe-0/0/37.0 lacp Decapsulation 0 0 0
Clearly there LACP packets being received above. If I add another UNI/CE access port to the vlan stanza configuration and I configure the CE device to generate LACP traffic, I can see it encapsulating the LACP ports:
vl400 ge-0/0/10.0 lacp Encapsulation 5217 0 0
Clearly, the VLAN is configured correctly. The issue is the ingress (Decapsulation) traffic.
Have I missed something configuration wise?
Thanks
