CLI QoS numbers vs CISCO-CLASS-BASED-QOS-MIB

Unanswered Question
Aug 21st, 2009

We have a commercial NMS product measuring QoS stats. The tool calculates the following four numbers as seen below:

Exceeded Pkts Remarked = (cbQosPoliceExceededPkt64 * constArrayMap (cbQosPoliceCfgConformAction, 0, 0, 1, 1, 1, 1, 1, 1, 1, 1, 0))

Exceeded Pkts Transmitted = (cbQosPoliceExceededPkt64 * constArrayMap (cbQosPoliceCfgConformAction, 0, 1, 0, 0, 0, 0, 0, 0, 0, 0, 0))

Violated Pkts Remarked = (cbQosPoliceViolatedPkt64 * constArrayMap (cbQosPoliceCfgConformAction, 0, 0, 1, 1, 1, 1, 1, 1, 1, 1, 0))

Violated Pkts Transmitted = (cbQosPoliceViolatedPkt64 * constArrayMap (cbQosPoliceCfgConformAction, 0, 1, 0, 0, 0, 0, 0, 0, 0, 0, 0))

On the CLI, the output was seen:

show policy-map interface gigabitethernet 10/2

GigabitEthernet10/2

Service-policy output: scheduler-test-shaping

Class-map: class-default (match-any)

218857 packets, 50959396 bytes

30 second offered rate 1198000 bps, drop rate 204000 bps

Match: any

Queueing

queue limit 250 (packets)

(queue depth/total drops/no-buffer drops) 0/24613/0

(pkts queued/bytes queued) 198371/42626437

shape (average) cir 1000000, bc 4000, be 4000

target shape rate 1000000

Service-policy : scheduler-test

queue stats for all priority classes:

queue limit 2 (packets)

(queue depth/total drops/no-buffer drops) 5/0/0

(pkts queued/bytes queued) 125480/0

Class-map: diamond (match-any)

123154 packets, 26340012 bytes

30 second offered rate 600000 bps, drop rate 0 bps

Match: ip dscp ef

Match: ip precedence 5

Priority: 0% (0 kbps),

police:

cir 1 %

cir 10000 bps, bc 1500 bytes, be 1500 bytes

conformed 2002 packets, 420872 bytes; action: transmit

exceeded 7 packets, 1498 bytes; action: set-dscp-transmit cs6

violated 121145 packets, 25917642 bytes; action: set-dscp-transmit cs6

conformed 10000 bps, exceed 0 bps, violate 590000 bps

Given this CLI, we assumed we'd see non-zero values for Exceeded Pkts Remarked and Violated Pkts Remarked, but rather Exceeded Pkts Transmitted and Violated Pkts Transmitted were seen incrementing.

After looking at the policer carefully, it kind of makes some sense to me, because the Exceed and Violate actions are both "set-dscp-transmit" (emphasis on the "transmit"), but weren't the Exceeded and Violated packets being *remarked* nonetheless? In a "tail wagging the dog" fashion, what change(s) would need to be made to the current policy so I want to see Exceeded Pkts Remarked and Violated Pkts Remarked incrementing?

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.

Actions

This Discussion