Pricilla

Have you tried this with R3 configured with multipoint interface. I am
just curious if you will see the same behaviour.

Mike


-----Original Message-----
From: Priscilla Oppenheimer [mailto:[EMAIL PROTECTED]] 
Sent: 19 August 2002 08:27 PM
To: [EMAIL PROTECTED]
Subject: RE: Traceroute IP displays twice (previous post by Pri
[7:51633]

Hi Mark, etc.

I never got a satisfactory explanation for my results with Trace Route.
In
my case, a particular router was claiming to be the first hop and the
second
hop. That's different from what we're seeing in the current question,
where
two different routers are claiming to be the first hop (due to load
balancing).

Here are the syptoms:

r1#trace 172.16.2.2

Type escape sequence to abort.
Tracing the route to 172.16.2.2

   1 172.16.1.3 12 msec 12 msec 12 msec
   2 172.16.1.3 12 msec 8 msec 8 msec
   3 172.16.2.2 24 msec 20 msec 20 msec

It's a frame-relay hub-and-spoke topology. I'm on one spoke trying to
trace 
to another spoke through the hub. The trace succeeds. The network is 
working, but what's with the router replying twice? (It happens if I go
the 
other way too.)

The hub router is 172.16.1.3. Why is it sending back the dest
unreachable 
twice?

The topology is:

R1------R3-----R2


Here are my configs:

r1
ip subnet-zero
no ip icmp rate-limit unreachable
!
interface Loopback0
  ip address 192.168.255.1 255.255.255.255
!
interface Ethernet0/0
  description to Cat 5K 3/1
  ip address 10.10.1.1 255.255.255.0
  half-duplex
!
interface TokenRing0/0
  description in ring 1
  ip address 192.168.1.1 255.255.255.0
  ring-speed 16
!
interface Serial1/0
  ip address 172.16.1.1 255.255.255.0
  encapsulation frame-relay
  ip ospf network point-to-point
  frame-relay interface-dlci 133
  frame-relay lmi-type ansi
!
router ospf 1
  log-adjacency-changes
  network 10.10.1.0 0.0.0.255 area 0.0.0.0
  network 172.16.0.0 0.0.255.255 area 0.0.0.0
  network 192.168.1.0 0.0.0.255 area 0.0.0.0
  network 192.168.255.1 0.0.0.0 area 0.0.0.0
!
ip classless



R3
ip subnet-zero
no ip icmp rate-limit unreachable
!
interface Loopback0
  ip address 192.168.255.3 255.255.255.255
!
interface Ethernet0/0
  description link to cat5k 3/3
  ip address 10.10.3.1 255.255.255.0
  half-duplex
!
interface Serial1/0
  description Frame relay
  no ip address
  encapsulation frame-relay
  no fair-queue
  no frame-relay inverse-arp
  frame-relay lmi-type ansi
!
interface Serial1/0.1 point-to-point
  description link to R1
  ip address 172.16.1.3 255.255.255.0
  ip ospf network point-to-point
  frame-relay interface-dlci 331
!
interface Serial1/0.2 point-to-point
  description link to R2
  ip address 172.16.2.3 255.255.255.0
  ip ospf network point-to-point
  frame-relay interface-dlci 332
!
router ospf 1
  log-adjacency-changes
  network 10.10.3.0 0.0.0.255 area 0.0.0.0
  network 172.16.0.0 0.0.255.255 area 0.0.0.0
  network 192.168.255.3 0.0.0.0 area 0.0.0.0
!
ip classless


R2
!
hostname r2
!
ip subnet-zero
no ip icmp rate-limit unreachable
!
interface Loopback0
  ip address 192.168.255.2 255.255.255.255
!
interface Ethernet0/0
  description to Cat 5K 3/2
  ip address 10.10.2.1 255.255.255.0
  half-duplex
!
interface TokenRing0/0
  ip address 192.168.2.1 255.255.255.0
  ring-speed 16
!
interface Serial1/0
  ip address 172.16.2.2 255.255.255.0
  encapsulation frame-relay
  ip ospf network point-to-point
  no fair-queue
  frame-relay interface-dlci 233
  frame-relay lmi-type ansi
!
router ospf 1
  log-adjacency-changes
  network 10.10.2.0 0.0.0.255 area 0.0.0.0
  network 172.16.0.0 0.0.255.255 area 0.0.0.0
  network 192.168.2.0 0.0.0.255 area 0.0.0.0
  network 192.168.255.2 0.0.0.0 area 0.0.0.0
ip classless


There's a Cisco router "in the cloud" acting as a Frame Relay switch, 
switching from DLCIs. I don't have its config. (This was a virtual lab).

Thanks for any hints you can give me.

Priscilla

________________________

Priscilla Oppenheimer
http://www.priscilla.com


Vicuna, Mark wrote:
> 
> While we are on the topic.. I remember a post by Priscilla a
> few months
> ago now (I think) with a traceroute showing 2 path entries of
> the same
> ip.  The result of the traceroute was not able to be reproduced
> (I
> think).   Anyone remember what the outcome of this was?  
> 
> 
> The archives are not searchable at this point in time.
> 
> 
> Cheers
> Mark.
> 
> > -----Original Message-----
> > From: Robert D. Cluett [mailto:[EMAIL PROTECTED]]
> > Sent: Monday, 19 August 2002 19:10
> > To: [EMAIL PROTECTED]
> > Subject: Re: traceroute IP displays twice [7:51622]
> > 
> > 
> > Thanks Raj!
> > 
> > ""Raj Santiago""  wrote in message
> > [EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
> > > i should have included this part as well to the previous
> post :
> > >
> > > >1 172.26.1.13 20 msec
> > >    172.26.1.2 20 msec
> > >    172.26.1.13 20 msec
> > >
> > > The above indicates, of the two possible paths the router 
> > has [172.26.1.2,
> > > 172.26.1.13] it has chosen the path 172.26.1.13.




Message Posted at:
http://www.groupstudy.com/form/read.php?f=7&i=51710&t=51710
--------------------------------------------------
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]

Reply via email to