Symptom

Traffic is policed at a rate different from the one configured in the applied ingress or egress policer. This may apply to the QoS policer, storm-control policer or any other policer in the Network Processor microcode. Corruption does not need to happen on the newly configured policers, some other existing policer may be corrupted instead. Corruption is confirmed by running the show qoshal police np index location " command. When there is corruption, the "pfl_id" and "commit profile"values differ. POLICE-NODE: np 1 type 1 index 1205qifh 0x27487791219013 chk_rec 443000 tokbkt_id 0x2004b5 stats 0xc698c8/0xc698c9/0xc698ca/0x40d1df8 pfl_id 64 committed 1 Original Index 437 Hybrid Overlap index 1205 Current Line:4, is_full 1, num_elem 256 Regular: Lines Full 2, Lines Partially Full 7 Color-Aware: Lines Full 2, Lines Partially Full 1 [D]TB - tokbkt_id: 0x2004b5, coupling: 0 color_aware: 0 commit profile: 61, peak profile: 61, algo: 1, color:0

Conditions

Attaching more than one QoS or storm-control policer to an interface in a single commit.

Workaround

Splitting configuration into multiple atomic commits reduces the risk of the race condition.

Further Problem Description