05-15-2017 08:40 AM
Hello there, i've been trying to troubleshoot sub interface input drops but I can't figure out how to look deeper into the counters for sub interface instead of physical ones. I'm not clear what counters show up in the show interface Total Input Drops. Appreciate your help.
RP/0/RSP0/CPU0:ASR001#show interfaces tenGigE 0/4/0/2.868
|
RP/0/RSP0/CPU0:ASR001#show interfaces tenGigE 0/4/0/2
|
RP/0/RSP0/CPU0:ASR001#show controllers tenGigE 0/4/0/2 stats Ingress: Input total packets = 877557094826 Input good pkts = 877556432730 Input drop overrun = 0 Input error giant = 4 Input MIB giant = 466337215633 |
RP/0/RSP0/CPU0:ASR001#show drops np np1 location 0/4/CPU0 Node: 0/4/CPU0: NP 1 Drops: <<--Does this counters show up under the show interface/subinterface Total Input Drops? |
Thanks in advance
Solved! Go to Solution.
05-15-2017 01:41 PM
Physical controller drop counters should contribute to the "total input drops" of the main interface, but not the sub-interface.
At NP microcode level, all drop counters where the input interface is know in the current microcode context are contributing to the "total input drops" at sub-interface level (also at interface level if that's where packets are logically received). You can use the "monitor np interface" feature to zoom into this. This command is described in https://supportforums.cisco.com/document/12927596/asr9000xr-troubleshooting-packet-drops-drops-np-microcode.
It is possible that some control plane drops are also contributing to "total input drops". One example are ES-IS PDU drops by IS-IS. This is unfortunately not an easy one to answer in today's XR releases. To zoom into these today you would have to run "debug statsd collector".
An enhancement request is in the pipeline to improve further the input drops transparency, but it's not getting much priority. Please feel free to ask someone from your account team at Cisco to reach out to me if you would like to get more priority to this improvement.
hope this helps,
/Aleksandar
05-15-2017 01:41 PM
Physical controller drop counters should contribute to the "total input drops" of the main interface, but not the sub-interface.
At NP microcode level, all drop counters where the input interface is know in the current microcode context are contributing to the "total input drops" at sub-interface level (also at interface level if that's where packets are logically received). You can use the "monitor np interface" feature to zoom into this. This command is described in https://supportforums.cisco.com/document/12927596/asr9000xr-troubleshooting-packet-drops-drops-np-microcode.
It is possible that some control plane drops are also contributing to "total input drops". One example are ES-IS PDU drops by IS-IS. This is unfortunately not an easy one to answer in today's XR releases. To zoom into these today you would have to run "debug statsd collector".
An enhancement request is in the pipeline to improve further the input drops transparency, but it's not getting much priority. Please feel free to ask someone from your account team at Cisco to reach out to me if you would like to get more priority to this improvement.
hope this helps,
/Aleksandar
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide