RSV_DROP_IPV4_DROP_NULL_RTE_MONITOR

[Marcin Kurek]

Hello,

I'm observing a significant amount of input drops on ASR9001 (port facing ASR920). Since this box is running 5.3.4, I've collected output from "monitor interface" command.

RP/0/RSP0/CPU0:R1#monitor np interface te0/0/2/0 count 2 time 1 location 0/0/CPU0
Fri Apr 21 09:56:34.145 CEST
 Monitor NP counters of TenGigE0_0_2_0 for 2 sec

                ****  Fri Apr 21 09:56:35 2017 ****

Monitor 1 non-zero NP0 counter:  TenGigE0_0_2_0
Offset  Counter                                         FrameValue   Rate (pps)
-------------------------------------------------------------------------------
 132 RSV_DROP_IPV4_DROP_NULL_RTE_MONITOR                        20          20

(Count 1 of 2)

                ****  Fri Apr 21 09:56:36 2017 ****

Monitor 1 non-zero NP0 counter:  TenGigE0_0_2_0
Offset  Counter                                         FrameValue   Rate (pps)
-------------------------------------------------------------------------------
 132 RSV_DROP_IPV4_DROP_NULL_RTE_MONITOR                        43          23

(Count 2 of 2)

Can anyone tell me please what does RSV_DROP_IPV4_DROP_NULL_RTE_MONITOR mean?

Closest what I've been able to find is:

RSV_DROP_IPV4_DROP_NULL_RTE                          Drop L3       dropped due to Tx-Adjacency linked to a null route. (TBD: why would this happen?)

Are these the same errors? 

Thanks!

[Aleksandar Vidakovic · Accepted solution]

hi Marcin,

this is the very same counter. The '_MONITOR' extension is always used when running the 'monitor np interface'. See

https://supportforums.cisco.com/document/12927596/asr9000xr-troubleshooting-packet-drops-drops-np-microcode

regards,

/Aleksandar

[Marcin Kurek]

Thank you very much Aleksandar!

Kind regards,
Marcin