GroupStudy.com GroupStudy.com - A virtual community of network engineers
 Home  BookStore  StudyNotes  Links  Archives  StudyRooms  HelpWanted  Discounts  Login
Re: Frame-relay Unwanted DLCI's on the interface posted 03/30/2007
[Chronological Index] [Thread Index] [Top] [Date Prev][Date Next] [Thread Prev][Thread Next]


In your experience if you reload the routers for numerous times, would it harm the hardware. I believe the hardware in production environment is not meant to restart many times a day. I am a bit scared to do this in my home lab.

Any guidelines welcome.
Regards,
RS

----- Original Message ----- From: "Lab Dude" <ccielabdude@xxxxxxxxx>
To: "Shamin" <ccie.xpert@xxxxxxxxx>
Cc: "Cisco certification" <ccielab@xxxxxxxxxxxxxx>
Sent: Friday, March 30, 2007 7:59 PM
Subject: Re: Frame-relay Unwanted DLCI's on the interface



Shutdown your interfaces connected to FR cloud, save your config and reload
on ALL routers in your network connected to FR cloud. This should fix it
100% of the time. This is a quick way to get rid of this problem without
messing around with the config, and spending loads of time t'shooting the
network. You can do it first thing when going through your lab questions, or
when doing switching section (it shouldnt matter whether it takes 5 minutes
for the routers to come up, as you'd be busy doing other things).


Alternatively, save your config, change encapsulation to something other
than FR (e.g PPP), shut the interface down, change the encap back to FR, and
put your maps on etc, and unshut the interface. This could fix it as well.


In the actual lab, you'll need to make sure that there are no unwanted
mappings (0.0.0.0 or any other dynamically learnt ones to unwanted DLCIs),
otherwise it'd screw your L2 topology, hence screwing up everything else you
build on top.


Goodluck!

On 3/30/07, Shamin <ccie.xpert@xxxxxxxxx> wrote:

Hi all,

I am trying to remove the unwanted DLCI's from the interface s0/0 of R2.
Did
the no frame-relay inverse-arp command. But still the DLCI's are shown
mapping to 0.0.0.0 . After a restart of the router, these entries will be
removed. In the actual lab, do we have to make sure that these entries are
not shown in the sh frame map output if they specifically say that, no
other
DLCI's other than the ones specified should be used. If it is so, is there
a
method to do this without restarting the routers?.


Rack1R2#sr int s0/0
Building configuration...

Current configuration : 192 bytes
!
interface Serial0/0
ip address 157.1.123.2 255.255.255.0
encapsulation frame-relay
frame-relay map ip 157.1.123.1 203
frame-relay map ip 157.1.123.3 203
no frame-relay inverse-arp
end




Rack1R2#sh frame map Serial0/0 (up): ip 0.0.0.0 dlci 213(0xD5,0x3450) broadcast, CISCO, status defined, inactive Serial0/0 (up): ip 0.0.0.0 dlci 205(0xCD,0x30D0) broadcast, CISCO, status defined, inactive Serial0/0 (up): ip 0.0.0.0 dlci 204(0xCC,0x30C0) broadcast, CISCO, status defined, inactive Serial0/0 (up): ip 0.0.0.0 dlci 201(0xC9,0x3090) broadcast, CISCO, status defined, active Serial0/0 (up): ip 157.1.123.1 dlci 203(0xCB,0x30B0), static, CISCO, status defined, active Serial0/0 (up): ip 157.1.123.3 dlci 203(0xCB,0x30B0), static, CISCO, status defined, active

Rack1R2(config)#do sh frame pvc | in DLCI
DLCI = 201, DLCI USAGE = LOCAL, PVC STATUS = DELETED, INTERFACE =
Serial0/0.1
DLCI = 203, DLCI USAGE = LOCAL, PVC STATUS = ACTIVE, INTERFACE = Serial0/0
DLCI = 204, DLCI USAGE = LOCAL, PVC STATUS = DELETED, INTERFACE =
Serial0/0.1
DLCI = 205, DLCI USAGE = LOCAL, PVC STATUS = INACTIVE, INTERFACE =
Serial0/0
DLCI = 213, DLCI USAGE = LOCAL, PVC STATUS = DELETED, INTERFACE =
Serial0/0.1
Rack1R2(config)#


_______________________________________________________________________
Subscription information may be found at:
http://www.groupstudy.com/list/CCIELab.html

_______________________________________________________________________ Subscription information may be found at: http://www.groupstudy.com/list/CCIELab.html