RE: inverse arp

From: Jim Brown (Jim.Brown@xxxxxxxxxxxxx)
Date: Sun Aug 25 2002 - 17:21:02 GMT-3


   
The rogue dynamic mappings can come back to haunt you.

I usually configure frame interfaces using these steps to prevent them.

1. shutdown the interface
2. define frame encapsulation
3. disable inverse arp
4. no shut the interface

If the interface is active and you define frame encapsulation it immediately
begins to inverse arp and build dynamic mappings. This is why I shut down
the interface before defining the encapsulation.

I would bet if you go to every frame interface and issue the no inverse-arp
command and restart the routers, your dynamic mappings will disappear
forever.

-----Original Message-----
From: John Michalek [mailto:jmichale@cisco.com]
Sent: Sunday, August 25, 2002 1:57 PM
To: cclielab@groupstudy.com
Subject: inverse arp

I have a frame-relay hub and spoke configuration. I've wanted to confirm
that when I use
a frame-relay map statement on the spoke routers that "inverse-arp is
disabled for the protocol referenced in the Frame-Relay
map statement on the DLCI referenced in the Frame-Relay map statement".
When I reloaded R2 or R5 the inverse-arp was not disabled and the dynamic
mapping to the hub was still there.
Everything I've ever read tells me that it shouldn't work this way. It
does not appear that inverse-arp gets disabled
at the spokes.
Can anyone please explain to me what I'm doing wrong?

I reloaded R2 and then did a "clear frame-relay inarp" - I did lose the
dynamic inverse-arp frame-relay map.
However, after I do a reload on R2 the dynamic inverse-arp frame-relay map
is back.
I even added "no frame-relay inverse-arp" under the s0/2 interface of R2 but
I still get the dynamic inverse-arp
frame-relay map.

My frame-relay switch is an AGS+. Is there anything that needs to be
configured on the frame-relay switch?

R1 (Hub)
interface Serial0/2
 ip address 192.168.17.1 255.255.255.0
 encapsulation frame-relay

Serial0/2 (up): ip 192.168.17.2 dlci 102(0x66,0x1860), dynamic,
              broadcast,, status defined, active
Serial0/2 (up): ip 192.168.17.5 dlci 105(0x69,0x1890), dynamic,
              broadcast,, status defined, active

R2 (spoke)
interface Serial0/2
 ip address 192.168.17.2 255.255.255.0
 encapsulation frame-relay
 frame-relay map ip 192.168.17.5 201 broadcast

Serial0/2 (up): ip 192.168.17.1 dlci 201(0xC9,0x3090), dynamic,
              broadcast,, status defined, active
Serial0/2 (up): ip 192.168.17.5 dlci 201(0xC9,0x3090), static,
              broadcast,
              CISCO, status defined, active

R5 (spoke)
interface Serial0/0
 ip address 192.168.17.5 255.255.255.0
 encapsulation frame-relay
 frame-relay map ip 192.168.17.2 501 broadcast

Serial0/0 (up): ip 192.168.17.1 dlci 501(0x1F5,0x7C50), dynamic,
              broadcast,, status defined, active
Serial0/0 (up): ip 192.168.17.2 dlci 501(0x1F5,0x7C50), static,
              broadcast,
              CISCO, status defined, active

Thanks!

John Michalek
Cisco Systems
Systems Engineer
8735 W. Higgins Road
Chicago, IL 60631
jmichale@cisco.com
(773) 695-8213



This archive was generated by hypermail 2.1.4 : Sat Sep 07 2002 - 19:48:37 GMT-3