06-09-2015 08:35 AM - edited 03-05-2019 01:38 AM
I've run across a strange issue with Cisco 887 routers running IOS 15.1 using DSL
We use Solarwinds to monitor our network, and I noticed it was showing absurd data transfer rates in the Petabytes for one of our routers, I'd also experienced this at a previous employer but thought it was a glitch.
The router is an 887 running 15.1(4r)M, everything is working fine, but the packet rates are reporting incorrectly on the DSL connection.
Input on the ATM interface, and output on the Dialer and Virtual-Access interfaces, reports Petabytes of non-existent traffic.
Anyone have any idea what could be causing it?
VPN.Rtr.****#sh int atm0
ATM0 is up, line protocol is up
Hardware is MPC/AOE ATMSAR, address is bc16.6513.5160 (bia bc16.6513.5160)
MTU 1600 bytes, sub MTU 1600, BW 1252 Kbit/sec, RxBW 21488 Kbit/sec, DLY 370 usec,
reliability 255/255, txload 12/255, rxload 255/255
Encapsulation ATM, loopback not set
Keepalive not supported
Encapsulation(s): AAL5
4 maximum active VCs, 1024 VCs per VP, 1 current VCCs
VC Auto Creation Disabled.
VC idle disconnect time: 300 seconds
Last input never, output 00:00:00, output hang never
Last clearing of "show interface" counters 6d06h
Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0
Queueing strategy: Per VC Queueing
5 minute input rate 256667384420324000 bits/sec, 4172287691 packets/sec
5 minute output rate 63000 bits/sec, 25 packets/sec
719379813693604 packets input, 15548298477451310424 bytes, 0 no buffer
Received 0 broadcasts (0 IP multicasts)
0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
4570432 packets output, 1346394908 bytes, 0 underruns
0 output errors, 0 collisions, 0 interface resets
0 unknown protocol drops
0 output buffer failures, 0 output buffers swapped out
VPN.Rtr.****#sh int dialer 1
Dialer1 is up, line protocol is up (spoofing)
Hardware is Unknown
Description: Link To Broadband
Internet address is ***.***.***.***/32
MTU 1500 bytes, BW 1252 Kbit/sec, RxBW 21488 Kbit/sec, DLY 20000 usec,
reliability 255/255, txload 255/255, rxload 1/255
Encapsulation PPP, LCP Closed, loopback not set
Keepalive set (10 sec)
DTR is pulsed for 1 seconds on reset
Interface is bound to Vi2
Last input never, output never, output hang never
Last clearing of "show interface" counters 2w5d
Input queue: 0/4096/0/0 (size/max/drops/flushes); Total output drops: 0
Queueing strategy: weighted fair
Output queue: 0/4096/64/0 (size/max total/threshold/drops)
Conversations 0/0/256 (active/max active/max total)
Reserved Conversations 0/0 (allocated/max allocated)
Available Bandwidth 939 kilobits/sec
5 minute input rate 51000 bits/sec, 26 packets/sec
5 minute output rate 255013886538779000 bits/sec, 172630289017136 packets/sec
7670403 packets input, 3905355871 bytes
7708060072495636923 packets output, 11355712667898331686 bytes
Bound to:
Virtual-Access2 is up, line protocol is up
Hardware is Virtual Access interface
MTU 1500 bytes, BW 1024 Kbit/sec, DLY 20000 usec,
reliability 255/255, txload 255/255, rxload 12/255
Encapsulation PPP, LCP Open
Open: IPCP
PPPoATM vaccess, cloned from Dialer1
Vaccess status 0x44
Bound to ATM0 VCD: 1, VPI: 0, VCI: 38, loopback not set
Keepalive set (10 sec)
DTR is pulsed for 5 seconds on reset
Interface is bound to Di1 (Encapsulation PPP)
Last input 00:00:00, output never, output hang never
Last clearing of "show interface" counters 2w5d
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 51000 bits/sec, 26 packets/sec
5 minute output rate 881019518621180000 bits/sec, 1197403197849240 packets/sec
7892510 packets input, 3918598067 bytes, 0 no buffer
Received 0 broadcasts (0 IP multicasts)
0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
4507594221841637891 packets output, 9166828043806603740 bytes, 0 underruns
0 output errors, 0 collisions, 0 interface resets
0 unknown protocol drops
0 output buffer failures, 0 output buffers swapped out
0 carrier transitions
06-09-2015 09:57 PM
This is definitely an IOS bug.
06-10-2015 01:00 AM
That's what I thought, but I've not been able to find an existing Bug ID for this one, and didn't want to submit it and find it was just a config hiccup
06-10-2015 02:05 AM
Well, the IOS you're running ends with an "M" and no number. So this is the first "M" train (aka "M0"). So it's a bug.
No one has reported it to TAC so there's no bug ID available.
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