12-22-2003 07:12 AM - edited 03-02-2019 12:30 PM
I seem to be experiencing a problem with dropped packets. The internal network here is a class A 10.x.x.x scheme which is then connected to a class C colocations on a 156.x.x.x scheme. The ethernet side of the router on the class A network is 10.111.111.111 the serial side is 172.16.1.1. On the router at the colocation the IP is 156.0.0.1 and the serial is 172.16.1.2.
If I ping with a packet size as low as 500 I get intermittent drops whether I'm pinging from the class A to the class C network or vice versa. Some times it even drops packets with the default packet size of 32. I checked my routes but am still unable to figure out the issue. Here is the setup on the router at the class A side followed by the Class C side config.
Using 652 out of 29688 bytes
!
version 12.2
service timestamps debug uptime
service timestamps log uptime
no service password-encryption
!
hostname BourneRouter
!
enable secret
!
ip subnet-zero
!
!
!
!
!
!
interface Ethernet0/0
ip address 10.111.111.111 255.0.0.0
full-duplex
!
interface Serial0/0
ip address 172.16.1.1 255.255.255.252
!
ip classless
ip route 0.0.0.0 0.0.0.0 172.16.1.2
ip http server
ip pim bidir-enable
!
snmp-server community mrtg RO
snmp-server enable traps snmp authentication linkdown linkup coldstart warmstart
!
line con 0
exec-timeout 0 0
line aux 0
line vty 0 4
password
login
!
no scheduler allocate
end
-----------------------------------------------------
Using 1387 out of 29688 bytes
!
version 12.2
service timestamps debug uptime
service timestamps log uptime
no service password-encryption
!
hostname MarlboroughRouter
!
enable secret
!
ip subnet-zero
!
!
!
!
!
!
interface Ethernet0/0
ip address 156.0.0.1 255.255.255.0
full-duplex
!
interface Serial0/0
ip address 172.16.1.2 255.255.255.252
ip accounting output-packets
half-duplex
!
ip classless
ip route 0.0.0.0 0.0.0.0 156.0.0.201
ip route 10.0.0.0 255.0.0.0 172.16.1.1
ip http server
ip pim bidir-enable
!
access-list 90 permit 10.5.5.6
access-list 90 permit 10.111.111.111
access-list 90 permit 172.16.1.1
access-list 90 permit 172.16.1.2
snmp-server community mrtg RW 90
snmp-server community public RO
snmp-server enable traps snmp authentication linkdown linkup coldstart warmstart
snmp-server enable traps isdn call-information
snmp-server enable traps isdn layer2
snmp-server enable traps isdn chan-not-avail
snmp-server enable traps hsrp
snmp-server enable traps config
snmp-server enable traps entity
snmp-server enable traps envmon
snmp-server enable traps bgp
snmp-server enable traps ipmulticast
snmp-server enable traps msdp
snmp-server enable traps rsvp
snmp-server enable traps frame-relay
snmp-server enable traps rtr
snmp-server enable traps syslog
!
line con 0
exec-timeout 0 0
line aux 0
line vty 0 4
password
login
!
no scheduler allocate
end
12-22-2003 08:28 AM
Looks like you *may* have a duplex mismatch on the Serial interfaces. The 'MarlboroughRouter' is hard-coded for half-duplex, the 'BourneRouter' is not. Check that they both match using 'sh int s0/0'.
~Zach
12-22-2003 10:23 AM
You were right. I fixed that but am still having the same issues. On the Class A side here is the show int e 0/0. It has CRC errors on input. There are no errors on the serial side. I did have a few errors on the Class C side but not since I cleared the counters about an hour ago. Here is the ethernet side of the Class A side router:
Ethernet0/0 is up, line protocol is up
Hardware is AmdP2, address is 0008.a370.1680 (bia 0008.a370.1
Internet address is 10.111.111.111/8
MTU 1500 bytes, BW 10000 Kbit, DLY 1000 usec,
reliability 255/255, txload 2/255, rxload 2/255
Encapsulation ARPA, loopback not set
Keepalive set (10 sec)
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 00:48:28
Queueing strategy: fifo
Output queue 0/40, 0 drops; input queue 7/75, 93 drops
5 minute input rate 112000 bits/sec, 136 packets/sec
5 minute output rate 94000 bits/sec, 20 packets/sec
507353 packets input, 72957743 bytes, 0 no buffer
Received 123187 broadcasts, 0 runts, 0 giants, 0 throttles
1973 input errors, 1973 CRC, 0 frame, 0 overrun, 0 ignored
0 input packets with dribble condition detected
108573 packets output, 63675968 bytes, 0 underruns
0 output errors, 0 collisions, 0 interface resets
0 babbles, 0 late collision, 0 deferred
0 lost carrier, 0 no carrier
0 output buffer failures, 0 output buffers swapped out
12-22-2003 10:45 AM
The errors have begun to appear on the Class C side now. Here is the show int e 0/0 on the Class C side:
Ethernet0/0 is up, line protocol is up
Hardware is AmdP2, address is 0008.a374.8200 (bia 0008.a374.8200)
Internet address is 156.0.0.1/24
MTU 1500 bytes, BW 10000 Kbit, DLY 1000 usec,
reliability 251/255, txload 3/255, rxload 6/255
Encapsulation ARPA, loopback not set
Keepalive set (10 sec)
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 01:13:22
Queueing strategy: fifo
Output queue 0/40, 0 drops; input queue 0/75, 0 drops
5 minute input rate 250000 bits/sec, 50 packets/sec
5 minute output rate 139000 bits/sec, 101 packets/sec
235095 packets input, 110428158 bytes, 0 no buffer
Received 68096 broadcasts, 0 runts, 0 giants, 0 throttles
8888 input errors, 8888 CRC, 4398 frame, 0 overrun, 0 ignored
0 input packets with dribble condition detected
459021 packets output, 84018917 bytes, 0 underruns
0 output errors, 0 collisions, 0 interface resets
0 babbles, 0 late collision, 0 deferred
0 lost carrier, 0 no carrier
0 output buffer failures, 0 output buffers swapped out
12-22-2003 11:27 AM
What is the duplex for each of the switch ports the routers are connected to?
12-22-2003 12:05 PM
I forced the duplex to half-duplex on both ethernet sides and this seemed to fix the issue. When you to a show int e 0/0 it doesn't show you what it is set to. I thought it might be this because I telnetted to the Class A router and pinged a Machine on the Class A network and it got time outs. Once I changed the duplex I'm not dropping packets.
I tried setting both ethernet sides to full duplex but started dropping packets again. I guess I'm going to have to stick with half-duplex.
12-22-2003 01:59 PM
The output from 'sh controllers e0/0' may reveal the current duplex operation.
~Zach
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: