From: Scott Morris (smorris@internetworkexpert.com)
Date: Mon Aug 11 2008 - 08:24:47 ART
That doesn't make frame stupid... It just makes the IOS load that you have
a little irritating. ;)
Not everything in life works as planned all the time!
But understanding those variants and dealing with them makes for a much more
successful lab attempt!
HTH,
Scott Morris, CCIE4 #4713, JNCIE-M #153, JNCIS-ER, CISSP, et al.
CCSI/JNCI-M/JNCI-ER
Senior CCIE Instructor
smorris@internetworkexpert.com
Internetwork Expert, Inc.
http://www.InternetworkExpert.com
Toll Free: 877-224-8987
Outside US: 775-826-4344
Knowledge is power.
Power corrupts.
Study hard and be Eeeeviiiil......
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of John
Sent: Sunday, August 10, 2008 10:52 PM
To: Fahad Khan; Scott Strobeck
Cc: CCIElab@groupstudy.com
Subject: Re: Getting rid of frame maps
No sir I don't like it, not one bit. Frame is stupid, because it doesn't
behave like I want it too. I always clear inarp, and sometimes I reload,
although I have no exact rule as to when I reload and I when I don't. Shut
no shut doesn't always do the trick
----- Original Message -----
From: Fahad Khan
To: Scott Strobeck
Cc: John ; CCIElab@groupstudy.com
Sent: Sunday, August 10, 2008 11:58 AM
Subject: Re: Getting rid of frame maps
Yes, "no frame inverse-arp" disables the inverse-arp request but not the
reply. I think there is no way to block reply. Thats why by enabling
inverse-arp just at one end you get the mappings on the other end.
On 8/10/08, Scott Strobeck <scott@strobeck.net> wrote:
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