The router is C897VA-K9.
I have a weird problem:
When I ping via windows cmd I get sometimes regular sometimes irregular patterns:
>ping 192.168.0.1 -t Pinging 192.168.0.1 with 32 bytes of data: Reply from 192.168.0.1: bytes=32 time=1ms TTL=255 Reply from 192.168.0.1: bytes=32 time<1ms TTL=255 Reply from 192.168.0.1: bytes=32 time<1ms TTL=255 Reply from 192.168.0.1: bytes=32 time<1ms TTL=255 Reply from 192.168.0.1: bytes=32 time<1ms TTL=255 Reply from 192.168.0.1: bytes=32 time<1ms TTL=255 Reply from 192.168.0.1: bytes=32 time<1ms TTL=255 Reply from 192.168.0.1: bytes=32 time<1ms TTL=255 Request timed out. Reply from 192.168.0.1: bytes=32 time<1ms TTL=255 Reply from 192.168.0.1: bytes=32 time<1ms TTL=255 Request timed out. Reply from 192.168.0.1: bytes=32 time<1ms TTL=255 Request timed out. Request timed out. Reply from 192.168.0.1: bytes=32 time<1ms TTL=255 Request timed out. Request timed out. Request timed out. Request timed out. Request timed out. Request timed out. Reply from 192.168.0.1: bytes=32 time<1ms TTL=255 Request timed out. Reply from 192.168.0.1: bytes=32 time<1ms TTL=255 Request timed out. Reply from 192.168.0.1: bytes=32 time<1ms TTL=255 Request timed out. Reply from 192.168.0.1: bytes=32 time<1ms TTL=255 Reply from 192.168.0.1: bytes=32 time<1ms TTL=255 Reply from 192.168.0.1: bytes=32 time=2ms TTL=255 Reply from 192.168.0.1: bytes=32 time=3ms TTL=255 Reply from 192.168.0.1: bytes=32 time<1ms TTL=255 Reply from 192.168.0.1: bytes=32 time<1ms TTL=255 Reply from 192.168.0.1: bytes=32 time<1ms TTL=255 Request timed out. Request timed out. Request timed out.
Usually if it is run long enough (~1min) it settles in this pattern:
Reply from 192.168.0.1: bytes=32 time<1ms TTL=255 Request timed out. Request timed out. Request timed out. Request timed out. Request timed out. Reply from 192.168.0.1: bytes=32 time<1ms TTL=255 Request timed out. Request timed out. Request timed out. Request timed out. Request timed out. Request timed out. Reply from 192.168.0.1: bytes=32 time<1ms TTL=255 Request timed out. Request timed out. Request timed out. Request timed out. Request timed out. Request timed out. Reply from 192.168.0.1: bytes=32 time<1ms TTL=255 Request timed out. Request timed out. Request timed out. Request timed out. Request timed out. Request timed out. Reply from 192.168.0.1: bytes=32 time<1ms TTL=255 Request timed out. Request timed out. Request timed out. Request timed out. Request timed out. Request timed out. Reply from 192.168.0.1: bytes=32 time<1ms TTL=255 Request timed out. Request timed out. Request timed out. Request timed out. Request timed out. Request timed out. Reply from 192.168.0.1: bytes=32 time<1ms TTL=255 Request timed out. Request timed out.
Now the weird part is when I monitor packets in Wireshark I see when the transition happens between successful ping and unsuccessful there is always ARP ping. And if I force ARP ping by arp -d 192.168.0.1 on windows it toggles ignore all packets/or receive them. This is very consistent. It reproduces 100% all the time.
I have never seen something likes this before. I tried config-register 0x2142, resetting configuration; nothing would resolve this problem.
How to fix this?
Router>en Router#sh ip int brie Interface IP-Address OK? Method Status Protocol ATM0 unassigned YES unset administratively down down BRI0 unassigned YES unset administratively down down BRI0:1 unassigned YES unset administratively down down BRI0:2 unassigned YES unset administratively down down Ethernet0 unassigned YES unset administratively down down GigabitEthernet0 unassigned YES unset down down GigabitEthernet1 unassigned YES unset down down GigabitEthernet2 unassigned YES unset down down GigabitEthernet3 unassigned YES unset up up GigabitEthernet4 unassigned YES unset down down GigabitEthernet5 unassigned YES unset up up GigabitEthernet6 unassigned YES unset down down GigabitEthernet7 unassigned YES unset down down GigabitEthernet8 192.168.1.77 YES manual down down Vlan1 192.168.0.1 YES manual up up
Router#sh int g3
GigabitEthernet3 is up, line protocol is up
Hardware is Gigabit Ethernet, address is 00ea.bd79.8300 (bia 00ea.bd79.8300)
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
ARP type: ARPA, ARP Timeout 04:00:00
Last input 00:12:06, output never, 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 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
15975 packets input, 1740544 bytes, 0 no buffer
Received 475 broadcasts (290 multicasts)
0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
0 watchdog, 0 multicast, 0 pause input
0 input packets with dribble condition detected
55229 packets output, 4779117 bytes, 0 underruns
0 output errors, 0 collisions, 3 interface resets
18 unknown protocol drops
0 babbles, 0 late collision, 0 deferred
11 lost carrier, 0 no carrier, 0 pause output
0 output buffer failures, 0 output buffers swapped outRunning configuration is very simple: static ip address on vlan1 and giga8. You may spot some other changes to running-config on my show reports, but those changes did not affect the problem in any way.
So I have bought used ISR C897VA with an issue: when vlan1 is pinged from windows there are quite a lot of "Request timed out"s. Config-register 0x2142 has been done, as well as resetting startup-config. PC is just connected to gi5 and the router's configuration is:
int vlan ip address 192.168.0.1 255.255.255.0
ping 192.168.0.1 -t
Pinging 192.168.0.1 with 32 bytes of data: Reply from 192.168.0.1: bytes=32 time=1ms TTL=255 Reply from 192.168.0.1: bytes=32 time<1ms TTL=255 Reply from 192.168.0.1: bytes=32 time<1ms TTL=255 Reply from 192.168.0.1: bytes=32 time<1ms TTL=255 Reply from 192.168.0.1: bytes=32 time<1ms TTL=255 Reply from 192.168.0.1: bytes=32 time<1ms TTL=255 Reply from 192.168.0.1: bytes=32 time<1ms TTL=255 Reply from 192.168.0.1: bytes=32 time<1ms TTL=255 Request timed out. Reply from 192.168.0.1: bytes=32 time<1ms TTL=255 Reply from 192.168.0.1: bytes=32 time<1ms TTL=255 Request timed out. Reply from 192.168.0.1: bytes=32 time<1ms TTL=255 Request timed out. Request timed out. Reply from 192.168.0.1: bytes=32 time<1ms TTL=255 Request timed out. Request timed out. Request timed out. Request timed out. Request timed out. Request timed out. Reply from 192.168.0.1: bytes=32 time<1ms TTL=255 Request timed out. Reply from 192.168.0.1: bytes=32 time<1ms TTL=255 Request timed out. Reply from 192.168.0.1: bytes=32 time<1ms TTL=255 Request timed out. Reply from 192.168.0.1: bytes=32 time<1ms TTL=255 Reply from 192.168.0.1: bytes=32 time<1ms TTL=255 Reply from 192.168.0.1: bytes=32 time=2ms TTL=255 Reply from 192.168.0.1: bytes=32 time=3ms TTL=255 Reply from 192.168.0.1: bytes=32 time<1ms TTL=255 Reply from 192.168.0.1: bytes=32 time<1ms TTL=255 Reply from 192.168.0.1: bytes=32 time<1ms TTL=255 Request timed out. Request timed out. Request timed out. Reply from 192.168.0.1: bytes=32 time<1ms TTL=255 Request timed out. Request timed out. Request timed out. Request timed out. Request timed out. Reply from 192.168.0.1: bytes=32 time<1ms TTL=255 Request timed out. Request timed out. Request timed out. Request timed out. Request timed out. Request timed out. Reply from 192.168.0.1: bytes=32 time<1ms TTL=255 Request timed out. Request timed out. Request timed out. Request timed out. Request timed out. Request timed out. Reply from 192.168.0.1: bytes=32 time<1ms TTL=255 Request timed out. Request timed out. Request timed out. Request timed out. Request timed out. Request timed out. Reply from 192.168.0.1: bytes=32 time<1ms TTL=255 Request timed out. Request timed out. Request timed out. Request timed out. Request timed out. Request timed out. Reply from 192.168.0.1: bytes=32 time<1ms TTL=255 Request timed out. Request timed out. Request timed out. Request timed out. Request timed out. Request timed out. Reply from 192.168.0.1: bytes=32 time<1ms TTL=255 Request timed out. Request timed out.
If I run on PC >arp -d 192.168.0.1. It removes 192.168.0.1 and MAC from windows's arp table and therefore forces it to do arp request. If PC is currently receiving ping replies from Vlan1, by doing arp -d 192.168.0.1 the PC will stop receving those replies and vice versa, as seen on this Wireshard screenshot: olehana portugal
Why is it happening? Is it hardware issue?
