From: L.C. Broadnax (lcbroadn@xxxxxxxxxx)
Date: Fri Aug 20 1999 - 19:39:00 GMT-3
You can add this command under the interface with the frame map statement:
no frame-relay inverse-arp
-----Original Message-----
From: David Oakman <doakman@home.com>
To: 'Jim Ayers' <jayers@cisco.com>; Edward Ruszkiewicz <ruszk@berbee.com>;
ccielab@groupstudy.com <ccielab@groupstudy.com>
Date: Wednesday, August 18, 1999 9:38 PM
Subject: RE: FR Question
>Jim,
> Try this on R0 or R4
> Sho fr map
> clear FR
> Sho fr map
>
> you should lose connectivity to your hub from the spoke.
> This is a classic Inverse arp issue like ed had stated. What will happen
at the lab is the proctor would reboot one of your routers (R0/R4) and your
network would no longer work.
>
> I am not certain why the additional dlci's would cause a problem on the
hub. I would add the additional frame frlay map statements on the spokes and
then see if the problem still exisits.
>
>What does a debug ip packet show (on both sides) ?
>
>ttfn
>daveo
>
>
>
>-----Original Message-----
>From: Jim Ayers [SMTP:jayers@cisco.com]
>Sent: Wednesday, August 18, 1999 7:28 PM
>To: Edward Ruszkiewicz; ccielab@groupstudy.com
>Subject: RE: FR Question
>
>Edward,
>
>Thanks. I know I can use a fr map for R4, but I don't think it's
necessary. In fact, as long as the switch announces only the two required
PVCs then the inarp works just fine as can be seen below:
>
>r4#sh fr map
>Serial0 (up): ip 132.10.64.1 dlci 114(0x72,0x1C20), dynamic,
> broadcast,, status defined, active
>Serial0 (up): ip 132.10.64.2 dlci 111(0x6F,0x18F0), dynamic,
> broadcast,, status defined, active
>
>The problem is when the switch announces more than one dlci; The two
spokes can no longer ping each other.
>
>Any other ideas.
>
>Jim.
>
>
>At 12:38 PM 8/18/1999 -0500, Edward Ruszkiewicz wrote:
>>You should use a frame relay map statement for R4 on each spoke. Inv-arp
is
>>disabled per dlci per protocol with a static mapping. It may remain for
>>awhile, until cache cleared. I'm not certain about your extra dlci
question?
>>
>>-----Original Message-----
>>From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On Behalf Of
>>Jim Ayers
>>Sent: Wednesday, August 18, 1999 11:44 AM
>>To: ccielab@groupstudy.com
>>Subject: FR Question
>>
>>
>>The topology:
>>
>>R0 --------------|
>> ____|_____
>> | fr switch |---------- R4
>> |_________|
>> |
>>R3 --------------|
>>
>>where R0, R3 are spokes; R4 is the hub
>>
>>Relevant Configs:
>>
>>R0:
>>interface Serial0
>> ip address 132.10.64.2 255.255.255.0
>> encapsulation frame-relay
>> frame-relay map ip 132.10.64.1 101 broadcast
>>
>>R3:
>>interface Serial0
>> ip address 132.10.64.1 255.255.255.0
>> encapsulation frame-relay
>> frame-relay map ip 132.10.64.2 121 broadcast
>>
>>R4:
>>interface Serial0
>> ip address 132.10.64.3 255.255.255.0
>> encapsulation frame-relay
>>
>>Problem: The above works fine (ie all routers can ping each other) provide
>>the FR switch only announces the minimum number of necessary DLCIs. As
soon
>>as the switch is configured to announce "extra" DLCIs, the two spokes can
>>not ping each other.
>>
>>Question: Why does this happen and how to fix it?
>>
>>
>>Thanks. It's got to be something simple that I'm missing. All my other
FR
>>configs work fine.
>>
>>
>>
>>
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 08:21:47 GMT-3