From: marvin greenlee (marvin@ccbootcamp.com)
Date: Thu Feb 03 2005 - 17:11:18 GMT-3
A broader generalization is that if your ping goes !.!.!, then there is a
good chance that a router along the way is trying to balance between two
paths, and one is not getting through.
- Marvin Greenlee, CCIE#12237, CCSI# 30483
Network Learning Inc
marvin@ccbootcamp.com
www.ccbootcamp.com (Cisco Training)
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
ccie2be
Sent: Thursday, February 03, 2005 11:57 AM
To: Edwards, Andrew M; Group Study
Subject: Re: Frame Relay Static maps -- Part 2 [bcc][faked-from]
Importance: Low
Andrew,
After speaking with network guru Brain MaGahan, I understand the problem and
it's not directly related to using the broadcast keyword on R3's interface
connection to R1 and R2.
What I didn't mention when I first posted this issue ( I didn't know this
was happening) is that R3 has another interface, S1/1, which is also
configured with frame encap.
On this other interface, I had to use inverse arp per the task requirements.
But, I didn't disable inarp on all the dlci's I needed to.
The result was that when I ping'd spoke to spoke, one ping would go thru but
the next ping wouldn't because it was using a different dlci created by
inarp.
So, the moral of this story is:
If your ping goes !.!.!.!.! and you're using inverse arp on a different
interface, you still have some dlci's which need to have inarp diabled.
To see which dlci's need to be disabled, do a show fram pvc | i DLCI
HTH, Tim
----- Original Message -----
From: "Edwards, Andrew M" <andrew.m.edwards@boeing.com>
To: "ccie2be" <ccie2be@nyc.rr.com>; "Group Study" <ccielab@groupstudy.com>
Sent: Thursday, February 03, 2005 1:58 PM
Subject: RE: Frame Relay Static maps -- Part 2
Tim,
How have you configured the Hub (e.g. R3)?
-----Original Message-----
From: ccie2be [mailto:ccie2be@nyc.rr.com]
Sent: Thursday, February 03, 2005 4:48 AM
To: Group Study
Subject: Frame Relay Static maps -- Part 2
Hi again,
I tried some variations with the broadcast key on the static fram maps.
Here's what I found:
If I add the broadcast keyword to the static maps on the spokes but not
on the hub, the same thing occurs -
I get a !.!.! result when I ping spoke to spoke.
If I add the broadcast keyword to only the static map on the hub, I get
the !!!! result when I ping spoke to spoke.
So, here's my conclusion:
If the broadcast keyword is omitted from the hub every other ping will
fail.
If the broadcast keyword is included on the hub, all the pings will
succeed.
Can anyone explain why that is?
TIA, Tim
This archive was generated by hypermail 2.1.4 : Thu Mar 03 2005 - 08:51:17 GMT-3