cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
349
Views
0
Helpful
1
Replies

Police SNMP oid

paul amaral
Participant
Participant

Hi, I'm having a hard time looking up the SNMP OID that corresponds to the violated stats with QOS policing. If you look below I'm interested in looking up the violated packets counter in bold. I have tried OID 1.3.6.1.4.1.9.9.166.1.17.1.1.16 but this does not seem to update. I can get seem to find and OID that corresponds to this although the bit rate oid, 1.3.6.1.4.1.9.9.166.1.15.1.1.7, seems to work fine.

TIA, Paul

police:
cir 20000000 bps, bc 2500000 bytes, be 3125000 bytes
conformed 973037 packets, 1176322487 bytes; actions:
transmit
exceeded 21501 packets, 31742260 bytes; actions:
transmit
violated 44900 packets, 67012787 bytes; actions:
drop
conformed 957000 bps, exceeded 51000 bps, violated 56000 bps

1 Accepted Solution

Accepted Solutions

paul amaral
Participant
Participant

Actually OID, 1.3.6.1.4.1.9.9.166.1.17.1.1.16 is updating but it displays the total dropped packets since the router rebooted. This will be different than the drop counters on the router if you clear the interface stats. I found that a better way is to monitor OID 1.3.6.1.4.1.9.9.166.1.17.1.1.21 which is the violated bps. Hope this helps someone.

 

 

 

 

cbQosPoliceStats 1.3.6.1.4.1.9.9.166.1.17 cbQosPoliceStatsTable 1.3.6.1.4.1.9.9.166.1.17.1 no-access cbQosPoliceStatsEntry 1.3.6.1.4.1.9.9.166.1.17.1.1 no-access cbQosPoliceConformedPktOverflow 1.3.6.1.4.1.9.9.166.1.17.1.1.1 counter32 read-only cbQosPoliceConformedPkt 1.3.6.1.4.1.9.9.166.1.17.1.1.2 counter32 read-only cbQosPoliceConformedPkt64 1.3.6.1.4.1.9.9.166.1.17.1.1.3 counter64 read-only cbQosPoliceConformedByteOverflow 1.3.6.1.4.1.9.9.166.1.17.1.1.4 counter32 read-only cbQosPoliceConformedByte 1.3.6.1.4.1.9.9.166.1.17.1.1.5 counter32 read-only cbQosPoliceConformedByte64 1.3.6.1.4.1.9.9.166.1.17.1.1.6 counter64 read-only cbQosPoliceConformedBitRate 1.3.6.1.4.1.9.9.166.1.17.1.1.7 gauge32 read-only cbQosPoliceExceededPktOverflow 1.3.6.1.4.1.9.9.166.1.17.1.1.8 counter32 read-only cbQosPoliceExceededPkt 1.3.6.1.4.1.9.9.166.1.17.1.1.9 counter32 read-only cbQosPoliceExceededPkt64 1.3.6.1.4.1.9.9.166.1.17.1.1.10 counter64 read-only cbQosPoliceExceededByteOverflow 1.3.6.1.4.1.9.9.166.1.17.1.1.11 counter32 read-only cbQosPoliceExceededByte 1.3.6.1.4.1.9.9.166.1.17.1.1.12 counter32 read-only cbQosPoliceExceededByte64 1.3.6.1.4.1.9.9.166.1.17.1.1.13 counter64 read-only cbQosPoliceExceededBitRate 1.3.6.1.4.1.9.9.166.1.17.1.1.14 gauge32 read-only cbQosPoliceViolatedPktOverflow 1.3.6.1.4.1.9.9.166.1.17.1.1.15 counter32 read-only cbQosPoliceViolatedPkt 1.3.6.1.4.1.9.9.166.1.17.1.1.16 counter32 read-only cbQosPoliceViolatedPkt64 1.3.6.1.4.1.9.9.166.1.17.1.1.17 counter64 read-only cbQosPoliceViolatedByteOverflow 1.3.6.1.4.1.9.9.166.1.17.1.1.18 counter32 read-only cbQosPoliceViolatedByte 1.3.6.1.4.1.9.9.166.1.17.1.1.19 counter32 read-only cbQosPoliceViolatedByte64 1.3.6.1.4.1.9.9.166.1.17.1.1.20 counter64 read-only cbQosPoliceViolatedBitRate 1.3.6.1.4.1.9.9.166.1.17.1.1.21 gauge32 read-only cbQosPoliceConformedBitRate64 1.3.6.1.4.1.9.9.166.1.17.1.1.22 counterbasedgauge64 read-only cbQosPoliceExceededBitRate64 1.3.6.1.4.1.9.9.166.1.17.1.1.23 counterbasedgauge64 read-only cbQosPoliceViolatedBitRate64 1.3.6.1.4.1.9.9.166.1.17.1.1.24 counterbasedgauge64 read-only

View solution in original post

1 Reply 1

paul amaral
Participant
Participant

Actually OID, 1.3.6.1.4.1.9.9.166.1.17.1.1.16 is updating but it displays the total dropped packets since the router rebooted. This will be different than the drop counters on the router if you clear the interface stats. I found that a better way is to monitor OID 1.3.6.1.4.1.9.9.166.1.17.1.1.21 which is the violated bps. Hope this helps someone.

 

 

 

 

cbQosPoliceStats 1.3.6.1.4.1.9.9.166.1.17 cbQosPoliceStatsTable 1.3.6.1.4.1.9.9.166.1.17.1 no-access cbQosPoliceStatsEntry 1.3.6.1.4.1.9.9.166.1.17.1.1 no-access cbQosPoliceConformedPktOverflow 1.3.6.1.4.1.9.9.166.1.17.1.1.1 counter32 read-only cbQosPoliceConformedPkt 1.3.6.1.4.1.9.9.166.1.17.1.1.2 counter32 read-only cbQosPoliceConformedPkt64 1.3.6.1.4.1.9.9.166.1.17.1.1.3 counter64 read-only cbQosPoliceConformedByteOverflow 1.3.6.1.4.1.9.9.166.1.17.1.1.4 counter32 read-only cbQosPoliceConformedByte 1.3.6.1.4.1.9.9.166.1.17.1.1.5 counter32 read-only cbQosPoliceConformedByte64 1.3.6.1.4.1.9.9.166.1.17.1.1.6 counter64 read-only cbQosPoliceConformedBitRate 1.3.6.1.4.1.9.9.166.1.17.1.1.7 gauge32 read-only cbQosPoliceExceededPktOverflow 1.3.6.1.4.1.9.9.166.1.17.1.1.8 counter32 read-only cbQosPoliceExceededPkt 1.3.6.1.4.1.9.9.166.1.17.1.1.9 counter32 read-only cbQosPoliceExceededPkt64 1.3.6.1.4.1.9.9.166.1.17.1.1.10 counter64 read-only cbQosPoliceExceededByteOverflow 1.3.6.1.4.1.9.9.166.1.17.1.1.11 counter32 read-only cbQosPoliceExceededByte 1.3.6.1.4.1.9.9.166.1.17.1.1.12 counter32 read-only cbQosPoliceExceededByte64 1.3.6.1.4.1.9.9.166.1.17.1.1.13 counter64 read-only cbQosPoliceExceededBitRate 1.3.6.1.4.1.9.9.166.1.17.1.1.14 gauge32 read-only cbQosPoliceViolatedPktOverflow 1.3.6.1.4.1.9.9.166.1.17.1.1.15 counter32 read-only cbQosPoliceViolatedPkt 1.3.6.1.4.1.9.9.166.1.17.1.1.16 counter32 read-only cbQosPoliceViolatedPkt64 1.3.6.1.4.1.9.9.166.1.17.1.1.17 counter64 read-only cbQosPoliceViolatedByteOverflow 1.3.6.1.4.1.9.9.166.1.17.1.1.18 counter32 read-only cbQosPoliceViolatedByte 1.3.6.1.4.1.9.9.166.1.17.1.1.19 counter32 read-only cbQosPoliceViolatedByte64 1.3.6.1.4.1.9.9.166.1.17.1.1.20 counter64 read-only cbQosPoliceViolatedBitRate 1.3.6.1.4.1.9.9.166.1.17.1.1.21 gauge32 read-only cbQosPoliceConformedBitRate64 1.3.6.1.4.1.9.9.166.1.17.1.1.22 counterbasedgauge64 read-only cbQosPoliceExceededBitRate64 1.3.6.1.4.1.9.9.166.1.17.1.1.23 counterbasedgauge64 read-only cbQosPoliceViolatedBitRate64 1.3.6.1.4.1.9.9.166.1.17.1.1.24 counterbasedgauge64 read-only

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community:

Recognize Your Peers