11-02-2012 04:36 AM
Hello!
How i can determine a reason of output drops?
>sh inter tenGigE 0/0/0/6
Fri Nov 2 15:26:05.358 MSK
TenGigE0/0/0/6 is up, line protocol is up
Interface state transitions: 11
Hardware is TenGigE, address is 108c.cf1d.f326 (bia 108c.cf1d.f326)
Layer 1 Transport Mode is LAN
Description: To_XXX
Internet address is 10.1.11.77/30
MTU 9194 bytes, BW 10000000 Kbit (Max: 10000000 Kbit)
reliability 255/255, txload 2/255, rxload 5/255
Encapsulation ARPA,
Full-duplex, 10000Mb/s, LR, link type is force-up
output flow control is off, input flow control is off
loopback not set,
ARP type ARPA, ARP timeout 04:00:00
Last input 00:00:00, output 00:00:00
Last clearing of "show interface" counters 50w1d
30 second input rate 218575000 bits/sec, 41199 packets/sec
30 second output rate 115545000 bits/sec, 30555 packets/sec
481020016118 packets input, 287815762466192 bytes, 876403 total input drops
0 drops for unrecognized upper-level protocol
Received 29 broadcast packets, 39255653 multicast packets
0 runts, 17 giants, 0 throttles, 0 parity
17 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
368901547057 packets output, 180820085800502 bytes, 28931652 total output drops
Output 5 broadcast packets, 39284266 multicast packets
0 output errors, 0 underruns, 0 applique, 0 resets
0 output buffer failures, 0 output buffers swapped out
10 carrier transitions
>show controllers np counters np7 location 0/0/CPU0 | i DROP
Fri Nov 2 15:27:03.815 MSK
31 PARSE_INGRESS_DROP_CNT 849353 0
32 PARSE_EGRESS_DROP_CNT 1236171 0
33 RESOLVE_INGRESS_DROP_CNT 868559 0
34 RESOLVE_EGRESS_DROP_CNT 3636654813 293
37 MODIFY_EGRESS_DROP_CNT 669 0
84 RESOLVE_AGE_NOMAC_DROP_CNT 1 0
85 RESOLVE_AGE_MAC_STATIC_DROP_CNT 187392316 8
371 MPLS_PLU_DROP_PKT 1 0
468 RESOLVE_VPLS_SPLIT_HORIZON_DROP_CNT 28931887 6
469 RESOLVE_VPLS_REFLECTION_FILTER_DROP_CNT 3293536501 272
481 RESOLVE_L2_EGR_PW_UIDB_MISS_DROP_CNT 4 0
491 RESOLVE_VPLS_EGR_PW_FLOOD_UIDB_DOWN_DROP_CNT 1 0
499 RESOLVE_MAC_NOTIFY_CTRL_DROP_CNT 313463638 16
500 RESOLVE_MAC_DELETE_CTRL_DROP_CNT 1591242 0
622 EGR_DHCP_PW_UNTRUSTED_DROP 1236171 0
Input drops by RESOLVE_VPLS_REFLECTION_FILTER_DROP_CNT was considered at https://supportforums.cisco.com/thread/2099283
But how we can apply it for output?
11-02-2012 04:46 AM
Ji Albert,
I would clear cpunters on interface and NP level and then capture again the outputs
sh inter tenGigE 0/0/0/6
show controllers np counters np7 location 0/0/CPU0 | i DROP
sh controller tenGigE 0/0/0/6 all
3-4 tmies in a row with about 1 minute interval to se which counters are incrementing.
RESOLVE_VPLS_REFLECTION_FILTER_DROP_CNT
normally is related in ingress drops and we have some input drops,
but we don't see any ino about output drops on controler level and we mayneed to check them as well
wbr
/vz
11-02-2012 05:59 AM
Last column at "show controllers np counters np7 location 0/0/CPU0 | i DROP" is a pps. So we see 293pps
RESOLVE_EGRESS_DROP_CNT and 0pps RESOLVE_INGRESS_DROP_CNT. Therefore RESOLVE_VPLS_REFLECTION_FILTER_DROP_CNT is a part of RESOLVE_EGRESS_DROP_CNT, aren't it?
Also, counters egress_drop are increases, but ingress_drop are not:
33 RESOLVE_INGRESS_DROP_CNT 868559 0
34 RESOLVE_EGRESS_DROP_CNT 3637707596 149
469 RESOLVE_VPLS_REFLECTION_FILTER_DROP_CNT 3294483194 129
And one minute later:
33 RESOLVE_INGRESS_DROP_CNT 868559 0
34 RESOLVE_EGRESS_DROP_CNT 3637718845 156
469 RESOLVE_VPLS_REFLECTION_FILTER_DROP_CNT 3294492975 135
Also no new input drops at "sh inter":
sh inter tenGigE 0/0/0/6 | i drops
Fri Nov 2 16:57:39.828 MSK
481200652943 packets input, 287931866783215 bytes, 876403 total input drops
0 drops for unrecognized upper-level protocol
369034005321 packets output, 180881208804090 bytes, 28963679 total output drops
One minute later:
sh inter tenGigE 0/0/0/6 | i drops
Fri Nov 2 16:59:23.441 MSK
481203274011 packets input, 287933491017363 bytes, 876403 total input drops
0 drops for unrecognized upper-level protocol
369035900847 packets output, 180882007120600 bytes, 28964280 total output drops
11-03-2012 01:01 AM
Hi Albert,
Which XR release you are running?
Becaue of the CSCtx92242
RESOLVE_VPLS_REFLECTION_FILTER_DROP_CNT are not counted as the part of the interface drops till 4.2.2
So, if you are running anything below then 4.2.2
RESOLVE_VPLS_REFLECTION_FILTER_DROP_CNT will no be counted as part of the drops on the interface level.
Again, this NP counters is for the ingress unicast VPLS frame that has a source XID that matches its destination XID. These are dropped since it cannot be sent back to the source port.
Since the inpt drop counters on the interface is not increasing I assume you are running something lower then 4.2.2 and then the reason for output drops on the interface level is
The diffs between two captures on the interface is 601 for total output drops for aprox. 104 sec so the rate for the output drops is aprox. 6 pps which is far below then
RESOLVE_EGRESS_DROP_CNT
and
RESOLVE_VPLS_REFLECTION_FILTER_DROP_CNT
And again, the last one is related to ingress frames , so i would check the controller counters on the affected interface first and then go to check bridge and fia counters on LC.
wbr
/vadim
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