Nexus 5596 queue drops - OID

I've scoured the 'net for this but have had no luck.

Can someone provide the OIDs for the following queues on a Nexus 5596 running Version 5.2(1)N1(3) ?

--------------
show queuing interface
--------------
Ethernet1/1 queuing information:
TX Queuing
    qos-group sched-type oper-bandwidth
        0       WRR            100
        1       WRR              0
        2       WRR              0
        3       WRR              0
        4       WRR              0
        5       WRR              0
RX Queuing
    qos-group 0
    q-size: 29760, HW MTU: 9216 (9216 configured)
    drop-type: drop, xon: 0, xoff: 29760
    Statistics:
        Pkts received over the port             : 20547226
        Ucast pkts sent to the cross-bar        : 20547030
        Mcast pkts sent to the cross-bar        : 195
        Ucast pkts received from the cross-bar : 738294
        Pkts sent to the port                   : 738805
        Pkts discarded on ingress               : 1
        Per-priority-pause status               : Rx (Inactive), Tx (Inactive)
    qos-group 1
    q-size: 29760, HW MTU: 9216 (9216 configured)
    drop-type: drop, xon: 0, xoff: 29760
    Statistics:
        Pkts received over the port             : 0
        Ucast pkts sent to the cross-bar        : 0
        Mcast pkts sent to the cross-bar        : 0
        Ucast pkts received from the cross-bar : 0
        Pkts sent to the port                   : 0
        Pkts discarded on ingress               : 0
        Per-priority-pause status               : Rx (Inactive), Tx (Inactive)
    qos-group 2
    q-size: 29760, HW MTU: 9216 (9216 configured)
    drop-type: drop, xon: 0, xoff: 29760
    Statistics:
        Pkts received over the port             : 0
        Ucast pkts sent to the cross-bar        : 0
        Mcast pkts sent to the cross-bar        : 0
        Ucast pkts received from the cross-bar : 0
        Pkts sent to the port                   : 0
        Pkts discarded on ingress               : 0
        Per-priority-pause status               : Rx (Inactive), Tx (Inactive)
    qos-group 3
    q-size: 90240, HW MTU: 9216 (9216 configured)
    drop-type: no-drop, xon: 17280, xoff: 37120
    Statistics:
        Pkts received over the port             : 0
        Ucast pkts sent to the cross-bar        : 0
        Mcast pkts sent to the cross-bar        : 0
        Ucast pkts received from the cross-bar : 0
        Pkts sent to the port                   : 0
        Pkts discarded on ingress               : 0
        Per-priority-pause status               : Rx (Inactive), Tx (Inactive)
    qos-group 4
    q-size: 29760, HW MTU: 9216 (9216 configured)
    drop-type: drop, xon: 0, xoff: 29760
    Statistics:
        Pkts received over the port             : 0
        Ucast pkts sent to the cross-bar        : 0
        Mcast pkts sent to the cross-bar        : 0
        Ucast pkts received from the cross-bar : 338950999
        Pkts sent to the port                   : 338954989
        Pkts discarded on ingress               : 0
        Per-priority-pause status               : Rx (Inactive), Tx (Inactive)
    qos-group 5
    q-size: 112000, HW MTU: 9216 (9216 configured)
    drop-type: drop, xon: 0, xoff: 112000
    Statistics:
        Pkts received over the port             : 0
        Ucast pkts sent to the cross-bar        : 0
        Mcast pkts sent to the cross-bar        : 0
        Ucast pkts received from the cross-bar : 0
        Pkts sent to the port                   : 0
        Pkts discarded on ingress               : 0
        Per-priority-pause status               : Rx (Inactive), Tx (Inactive)
Total Multicast crossbar statistics:
    Mcast pkts received from the cross-bar      : 4245

Currently I am running scripts with NCM to collect this info to a file every hour.

Then using a Perl script to massage the data.

Find more posts tagged with

Accepted answers

All comments

Network_Guru

Wow, 440 views and no one else has seen this issue?

We are still fighting this problem with no resolution in sight.

spruance

Unicast discards are marked and entered into ifInDiscards/ifOutDiscards as normal, but that's inclusive of all drops not per class.

Multicast discards are only accessible via cli commands such as "show queueing int" or "sh platform fwm info pif all". They are not recorded in ifIn/OutDiscards at all!

In 5.x code, discards by QOS level are not exposed in SNMP at all in the earlier code revs to my knowledge.

In NX-OS 6.2.x, they made significant improvements in available info for operations. On our NX7000s, many of the counters from "show queueing int" and various COS based are now accessable in private mibs (walk CISCO-CLASS-BASED-QOS-MIB, and you find all your class maps, etc).

I don't work for Cisco, so I do not know if this level will drop for the 55xx or if the above mib is in 6.0.x for the 55xx-- we're still running 5.x on our 5548s.

good luck!

Network_Guru

Thanks spruance

In communications with Cisco engineers, we were told that the QOS queue drops are collected on the individual interface ASICs, which are not currently pollable with SNMP in V5.2.x

Perhaps we will upgrade a Nexus 55xx in the lab to 6.2.x just to see what private mibs are now available.