The "show firewall" CLI shows an unconfigured policer name. This KB explains why the unconfigured policer name is shown by the CLI.
The policer shown is configured under the term-2, which will be like <policer-name>-<term-name> as "input_ipv6_policer1-2".
So 2 is the term name appended in the policer name. It will count the Bytes/Packets which were forwarded to the "be" queue by the policer.
{master}
user@ptx10008-re0> show configuration firewall
family inet6 {
filter input_ipv6_police_filter1 {
term 1 {
then {
count input_ipv6_before_counter1;
next term;
}
term 2 {
policer input_ipv6_policer1;
count input_ipv6_policer_counter1;
accept;
policer input_ipv6_policer1 {
if-exceeding {
bandwidth-limit 8g;
burst-size-limit 125k;
then forwarding-class be;
user@ptx10008-re0> show firewall
Filter: input_ipv6_police_filter1 Counters: Name Bytes Packets input_ipv6_before_counter1 148943786160 100501880 input_ipv6_policer_counter1 148943786160 100501880 Policers: Name Bytes Packets input_ipv6_policer1-2 26513380140 17890270
The policer shown is configured under the term-2, which will be like <policer-name>-<term-name>. So 2 is the term name appended in the policer name.
For example, if we set the 2nd firewall term name "AAA", the policer name will be input_ipv6_policer1-AAA.
user@mx204> show configuration firewall
term AAA {
bandwidth-limit 5g;
user@mx204> show firewall
Filter: __default_bpdu_filter__ Filter: input_ipv6_police_filter1 Counters: Name Bytes Packets input_ipv6_before_counter1 0 0 input_ipv6_policer_counter1 0 0 Policers: Name Bytes Packets input_ipv6_policer1-AAA 0 0