01-15-2015 12:37 PM - edited 03-05-2019 12:34 AM
We have a dual router campus building experiencing unknow protocol drops on both of the routers Wireless WAN g1/0 interfaces. Interface G0/0 is used to connect to the redundant router. G0/1 has several subinterfaces configured to supply the building switches their vlans. I was hoping to span the LAN interface g0/1 to a temporarily installed interface but evidently monitoring is not allowed on routed interfaces. Any suggestion for identifying the offending protocol would be appreciated.
XXX-CAM-OAK-N1BC1#sh run int g1/0
Building configuration...
Current configuration : 204 bytes
!
interface GigabitEthernet1/0
description WWAN Connection to XXX-CAM-WOC-W33C02
ip address 10.28.160.73 255.255.255.248
ip access-group 105 out
ip flow ingress
ip flow egress
negotiation auto
end
XXX-CAM-OAK-N1BC1#sh int g1/0
GigabitEthernet1/0 is up, line protocol is up
Hardware is i82543 (Livengood), address is c062.6b47.1460 (bia c062.6b47.1460)
Description: WWAN Connection to XXX-CAM-WOC-W33C02
Internet address is 10.28.160.73/29
MTU 1500 bytes, BW 1000000 Kbit/sec, DLY 10 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA, loopback not set
Keepalive set (10 sec)
Full-duplex, 1000Mb/s, link type is autonegotiation, media type is SX
output flow-control is XON, input flow-control is XON
ARP type: ARPA, ARP Timeout 04:00:00
Last input 00:00:00, output 00:00:00, output hang never
Last clearing of "show interface" counters never
Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0
Queueing strategy: fifo
Output queue: 0/40 (size/max)
5 minute input rate 3799000 bits/sec, 1671 packets/sec
5 minute output rate 612000 bits/sec, 228 packets/sec
91564391 packets input, 3321398724 bytes, 0 no buffer
Received 24038 broadcasts, 0 runts, 0 giants, 0 throttles
328 input errors, 0 CRC, 0 frame, 285 overrun, 43 ignored
0 watchdog, 24026 multicast, 0 pause input
0 input packets with dribble condition detected
15996803 packets output, 3921121358 bytes, 0 underruns
0 output errors, 0 collisions, 1 interface resets
9091 unknown protocol drops
0 babbles, 0 late collision, 0 deferred
0 lost carrier, 0 no carrier, 2207 pause output
0 output buffer failures, 0 output buffers swapped out
01-15-2015 01:14 PM
9091 unknown protocol drops
DTP are the main source of unknown protocol drops.
328 input errors, 0 CRC, 0 frame, 285 overrun, 43 ignored
Not a high percentage of total traffic but still of a concern particularly when the link is fibre optic.
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