I have seen this behavior when there are multiple static routes when there
shouldnt have been..
Brian Sonic Whalen
Success = Preparation + Opportunity
On Sat, 29 Dec 2001, Marc Russell wrote:
Kind of strange. What does debug ip packet give you. If you are running
other IP data then use
interface to router R2 serial interface on the same IP
network.
Marc Russell
www.ccbootcamp.com
-Original Message-
From: Brian Whalen
To: Marc Russell
Cc: [EMAIL PROTECTED]
Sent: 12/30/01 1:26 AM
Subject: Re: Half Successfull ping [7:30449]
I have seen this behavior when
Here is the routing table on R2 and R4. I have a hub and spoke config with
frame relay between R1 - R2,R3, and the frame connection between R1 and R4
is not coming up so hence the need for a direct serial back to back from R2
to R4.
R2#sh ip route
Codes: C - connected, S - static, I - IGRP, R -
The problem is fixed. Must have been some type of routing issue with those
addresses. I changed the addresses and getting 100% success on the pings.
Thanks to all for there suggestions.
22:06:13: %SYS-5-CONFIG_I: Configured from console by console
R2#ping 192.168.1.1
Type escape sequence to
however it happened, there are two equal cost paths to the 172.16.1.0
network as shown in the R1 routing table.
note the dual routes - one directly connected to serial 0 and one directly
connected to serial 1
that is the reason that you had the half successful ping
I have seen stuff like this -
looking at r2, it appears that connected routes for the 172.16.1.0 network
are showing up on both serial0 and serial1. Using 2 sets of ips out of
the same class c and assigning both pairs a /24 netmask?
Brian Sonic Whalen
Success = Preparation + Opportunity
On Sun, 30 Dec 2001, McHugh Randy
Anyone have an ideas on this half successfull ping across two directly
connect serial interfaces? Clock rate, encapsulation, controllers and cables
look OK. Address on R4 is 172.16.1.4/24 and R2 is 172.16.1.5/24 . Here is
the ping from R4
R4#ping 172.16.1.5
Type escape sequence to abort.
sure. you have two routes to the other destination, on both routers. the
routers, in other words, are load sharing based on something in their
routing tables.
post your entire configs. or at least your show ip route results.
Chuck
McHugh Randy wrote in message
[EMAIL PROTECTED]">news:[EMAIL
maybe there is a route round,paste your config or sh ip route result!
Anyone have an ideas on this half successfull ping across two directly
connect serial interfaces? Clock rate, encapsulation, controllers and
cables
look OK. Address on R4 is 172.16.1.4/24 and R2 is 172.16.1.5/24 . Here is
Kind of strange. What does debug ip packet give you. If you are running
other IP data then use debug ip packet 101 with the access list below. That
will make it easier to sort through the output. Have you tried slowing down
the clock rate or switching which side is DCE?
access-list 101 permit
Feel like you are having 2 routes pointing on the same
destination, through two diffrent interfaces.
Have a look on the routing.
Regards
--- McHugh Randy wrote:
Anyone have an ideas on this half successfull ping across
two directly
connect serial interfaces? Clock rate, encapsulation,
You are most likely load balancing across multiple interfaces and the
packets are not there or back. Either way it is an issue with the way
you are routing.
McHugh Randy wrote:
Anyone have an ideas on this half successfull ping across two directly
connect serial interfaces? Clock rate,
12 matches
Mail list logo
