Description

Theoretical question - in the lab we noticed that per-unit policers do not work on QFX5100 with EVPN/VXLAN as we see all counters as 0; is this expected?
 

switch> show firewall

Filter: TEST
Policers:
Name Bytes Packets
10m-default 0 0

Filter: TEST_POLICER

Filter: test_policer-xe-0/0/x
Counters:
Name Bytes Packets
policer-xe-0/0/x 0 0
Policers:
Name Bytes Packets
test_policer-xe-0/0/x 0

Filter: test_policer-xe-0/0/x
Counters:
Name Bytes Packets
policer-xe-0/0/x 0 0
Policers:
Name Bytes Packets
test_policer-xe-0/0/x0 0

Solution

As per  PR1773676 affecting native-vlan traffic, causing the policer to be affected as a consequence:
 

Similar customer's configuration:

   xe-0/0/x {
    flexible-vlan-tagging;
    native-vlan-id 1;
    mtu 9216;
    unit 1 {
     description TESTVLAN;
     encapsulation vlan-bridge;
     vlan-id 1;
     family ethernet-switching {
      filter {
       input test_policer-xe-0/0/x

PR details: The tagged traffic drop will be seen with vlan-id-list and native-vlan-id configured on one IFL.

PR not working scenario:

xe-x/x/x:0 {
    apply-groups XXXXX;
    flexible-vlan-tagging;
    native-vlan-id 1;
    encapsulation flexible-ethernet-services;
    unit 1 {
        encapsulation vlan-bridge;
        vlan-id-list 1-xxx;
    }
}

Modification History

2024-07-09 : Article Created

Related Information

The tagged traffic drop will be seen with vlan-id-list and native-vlan-id configured on one IFL