Preview Tool

Cisco Bug: CSCua80659 - Policy map counters not getting updated for user-defined policy-map

Last Modified

Feb 03, 2017

Products (25)

  • Cisco IOS
  • Cisco ASR 901-6CZ-F-D Router
  • Cisco 7206 Router
  • Cisco 7301 Router
  • Cisco ME 3600X-24TS-M Switch
  • Cisco ASR 901-4C-FT-D Router
  • Cisco 7206VXR Router
  • Cisco 7204 Router
  • Cisco ASR 901-6CZ-F-A Router
  • Cisco ASR 901-6CZ-FT-A Router
View all products in Bug Search Tool Login Required

Known Affected Releases

15.2(4)S 15.3(1)S

Description (partial)

In the latest mcp_dev image, policy-map counters are not getting updated for user-defined policies.
The following shows a failed example:
RHA_76a#sh policy-map
  Policy Map police-1
    Class prec2
      bandwidth 12 (%)
     police cir 15500000 bc 484375
       conform-action transmit 
       exceed-action drop 
RHA_76a#sh class-map
 Class Map match-any class-default (id 0)
   Match any  
 Class Map match-all prec2 (id 1)
   Match access-group   2002 
RHA_76a#sh policy-map int
  Service-policy output: police-1
  Counters last updated 00:00:05 ago
    Class-map: prec2 (match-all)  
      9565877 packets, 2429732758 bytes
      30 second offered rate 46539000 bps, drop rate 31055000 bps
      Match: access-group 2002
      queue limit 4650 packets
      (queue depth/total drops/no-buffer drops) 2/0/0
      (pkts output/bytes output) 3169279/804996866
      bandwidth 12% (18600 kbps)
          cir 15500000 bps, bc 484375 bytes
        conformed 3184546 packets, 808874684 bytes; actions:
        exceeded 6381333 packets, 1620858582 bytes; actions:
        conformed 0000 bps, exceeded 0000 bps               ----------------> Not updated
    Class-map: class-default (match-any)  
      28697682 packets, 7289203046 bytes
      30 second offered rate 139618000 bps, drop rate 6992000 bps
      Match: any 
      queue limit 34100 packets
      (queue depth/total drops/no-buffer drops) 34095/1438900/0
      (pkts output/bytes output) 27087593/6880240440

The issue is with "conformed" and "exceeded" rates counter, and can be seen after sending traffic under a customer defined policer.
Bug details contain sensitive information and therefore require a account to be viewed.

Bug Details Include

  • Full Description (including symptoms, conditions and workarounds)
  • Status
  • Severity
  • Known Fixed Releases
  • Related Community Discussions
  • Number of Related Support Cases
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.