Update: workaround for sluggish CB-QoS MIB

More than a year ago, I wrote about the very slow update rate of the variables in the CB-QoS MIB. In August WB found a workaround (do a show policy-map interface before reading the counters) and now Jared has tested it and confirmed that it works. He’s configured a simple EEM applet that executes the show command once per second:

event manager applet UpdateMibTables 
event timer watchdog time 1
action 1.0 cli command "enable"
action 2.0 cli command "show policy-map int dialer0"

With this fix, he can use the SNMP variables in other EEM applets to detect VoIP calls within 1-2 seconds.

Don’t forget: numerous EEM topics are described in the Embedded Event Manager (EEM) workshop. You can attend an online version of the workshop; we can also organize a dedicated event for your networking team.

2 comments:

  1. Ive been looking for someway to get the Cisco-CBQOS Mib to update in less that 10 seconds for a long time. Thanks for this!
  2. Hi,
    My query is regarding the control plane policing in 6500 switch. I have implemented CoPP in 65500 with different rate limits higher than the actual required for different classes of control plane traffic. I wish to tune this value for a near realistic one.
    The show policy-map control-plane detail gives me the peak bps for each class for hardware counters (Hardware CoPP).
    Whereas the software counters are displaying only the total number of bytes forwarded till now and last 5 minutes rate for each class of traffic.

    Is there anyway to find out the peak bps of the traffic forwarded by software CoPP for each class?
    Can we be able to find/calculate the peak bps using the statistics available in the software counter display?
Add comment
Sidebar