Re: Getting rid of frame maps

From: John (jgarrison1@austin.rr.com)
Date: Sun Aug 10 2008 - 23:55:41 ART


Thanks I think I got it. Frame is still stupid IMHO
----- Original Message -----
From: "Huan Pham" <Huan.Pham@peopletelecom.com.au>
To: "Scott Strobeck" <scott@strobeck.net>; "John" <jgarrison1@austin.rr.com>
Cc: <CCIElab@groupstudy.com>
Sent: Sunday, August 10, 2008 5:41 PM
Subject: RE: Getting rid of frame maps

Hi John,

The output shown by the command "show frame-relay pvc" has nothing to do
with frame-relay inverse-arp!!!

This command just shows what DLCI's the router learnt from the LOCAL
FRAME-RELAY SWITCH via LMI. This has nothing to do with your local
router config, or the configuration on the remote end routers (i.e.
wherether you enable or disable inverse-arp on the other end routers).

As long as you enable frame-relay encapsulation on the Serial interface
to the frame-switch, the router can not tell the frame-switch not to
send (via LMI) info about a particular DLCI. The only way you can do it
(remove info a about particular PVC on your router), is to go to the
Frame-Relay switch and remove any config about that DLCI.

The interface command "(no) frame-relay inverse-arp" on the other hand
enables/disables the dynamic mapping of Layer3 to Layer2 address. That's
the mapping of IP address of the remote end (another router) and the
local DLCI. As you can see, you have sucessfully disable dynamic mapping
for unwanted DLCI.

-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
Scott Strobeck
Sent: Monday, 11 August 2008 3:51 AM
To: John
Cc: CCIElab@groupstudy.com
Subject: Re: Getting rid of frame maps

John,

"no frame-relay inverse-arp" keeps the interface from sending arp
requests out. It doesn't, however, keep the router from creating
dynamic mappings based on incoming arp requests. (Or at least it maps
based on somthing, . . I assume it's incoming arp requests.)

Anyway, try disabling inverse arp on only one side of a FR link and
clear the inarp, then bounce the opposite end and watch the map reappear
on the side with inarp disabled. . . .

I got bit by this on a mock lab and it makes a very good point. IF IN
YOUR LAB YOU ARE USING DYNAMIC MAPPINGS, DISABLE INVERSE ARP ON ALL
OTHER DLCI'S. If you don't, you may end up with dynamic mappings
elsewhere in your lab you didn't even expect. After setting up all your
frame relay in your lab, I STRONGLY suggest issuing "show frame-relay
map" on EVERY router running FR to make sure you don't have unwanted
dynamic mappings. YOU WILL LOSE POINT FOR THIS!

Scott

John wrote:
> Maybe someone can explain this to me. I enterd the no frame inverse
commands
> and reloaded the router. When I do a show frame map it appears that I
have
> gotten rid of the unwanted dynamic mappings. When I do a sh frame pvc
| inc
> dlci. I see dlci's that should not be there because of the no frame
inv
> commands. Why is this???
>
>
> interface Serial0/0/0
> ip address 54.4.2.6 255.255.255.0
> encapsulation frame-relay
> no frame-relay inverse-arp IP 61
> no frame-relay inverse-arp IP 63
> no frame-relay inverse-arp IP 601
> no frame-relay inverse-arp IP 604
> no frame-relay inverse-arp IP 605
> no frame-relay inverse-arp IP 621
> no frame-relay inverse-arp IP 624
> no frame-relay inverse-arp IP 625
> end
>
> R6(config-router)#DO SH FRAME MAP
> Serial0/0/0 (up): ip 54.4.2.254 dlci 62(0x3E,0xCE0), dynamic,
> broadcast,, status defined, active
> R6(config-router)#DO SH FRAME PVC | INC DLCI
> DLCI = 61, DLCI USAGE = LOCAL, PVC STATUS = ACTIVE, INTERFACE =
Serial0/0/0
> DLCI = 62, DLCI USAGE = LOCAL, PVC STATUS = ACTIVE, INTERFACE =
Serial0/0/0
> DLCI = 63, DLCI USAGE = LOCAL, PVC STATUS = ACTIVE, INTERFACE =
Serial0/0/0
> DLCI = 64, DLCI USAGE = UNUSED, PVC STATUS = ACTIVE, INTERFACE =
Serial0/0/0
> DLCI = 65, DLCI USAGE = UNUSED, PVC STATUS = ACTIVE, INTERFACE =
Serial0/0/0
> DLCI = 66, DLCI USAGE = UNUSED, PVC STATUS = ACTIVE, INTERFACE =
Serial0/0/0
> DLCI = 601, DLCI USAGE = LOCAL, PVC STATUS = ACTIVE, INTERFACE =
Serial0/0/0
> DLCI = 602, DLCI USAGE = UNUSED, PVC STATUS = ACTIVE, INTERFACE =
Serial0/0/0
> DLCI = 603, DLCI USAGE = UNUSED, PVC STATUS = ACTIVE, INTERFACE =
Serial0/0/0
> DLCI = 604, DLCI USAGE = LOCAL, PVC STATUS = ACTIVE, INTERFACE =
Serial0/0/0
> DLCI = 605, DLCI USAGE = LOCAL, PVC STATUS = ACTIVE, INTERFACE =
Serial0/0/0
> DLCI = 607, DLCI USAGE = UNUSED, PVC STATUS = ACTIVE, INTERFACE =
Serial0/0/0
> DLCI = 608, DLCI USAGE = UNUSED, PVC STATUS = INACTIVE, INTERFACE =
> Serial0/0/0
> DLCI = 609, DLCI USAGE = UNUSED, PVC STATUS = INACTIVE, INTERFACE =
> Serial0/0/0
> DLCI = 613, DLCI USAGE = UNUSED, PVC STATUS = ACTIVE, INTERFACE =
Serial0/0/0
> DLCI = 621, DLCI USAGE = LOCAL, PVC STATUS = ACTIVE, INTERFACE =
Serial0/0/0
> DLCI = 622, DLCI USAGE = UNUSED, PVC STATUS = ACTIVE, INTERFACE =
Serial0/0/0
> DLCI = 623, DLCI USAGE = UNUSED, PVC STATUS = ACTIVE, INTERFACE =
Serial0/0/0
> DLCI = 624, DLCI USAGE = LOCAL, PVC STATUS = ACTIVE, INTERFACE =
Serial0/0/0
> DLCI = 625, DLCI USAGE = LOCAL, PVC STATUS = ACTIVE, INTERFACE =
Serial0/0/0
> DLCI = 627, DLCI USAGE = UNUSED, PVC STATUS = ACTIVE, INTERFACE =
Serial0/0/0
> DLCI = 628, DLCI USAGE = UNUSED, PVC STATUS = INACTIVE, INTERFACE =
> Serial0/0/0
> DLCI = 629, DLCI USAGE = UNUSED, PVC STATUS = INACTIVE, INTERFACE =
> Serial0/0/0
> DLCI = 633, DLCI USAGE = UNUSED, PVC STATUS = ACTIVE, INTERFACE =
Serial0/0/0
> R6(config-router)#
>
>
> Blogs and organic groups at http://www.ccie.net
>
>



This archive was generated by hypermail 2.1.4 : Mon Sep 01 2008 - 08:15:30 ART