From: Dan Pontrelli (dp595@xxxxxxxxxxxxx)
Date: Fri Aug 17 2001 - 11:21:53 GMT-3
Read in for reply:
> Hi,
>
> I tried to seach the archive but still couldn't clear my doubt.
>
> When a frame relay network is configured in full mesh but the practice lab
> question asked you to use only certain DLCI number, what will be the
> solution ?
The solutioin is to disable inverse arp on all interfaces and only use
"frame map" and "frame interface-dlci."
>
> What I'll do is: (from one of the router, assuming there are 3 routers
> connected thru frame cloud)
>
> interface Serial0
> ip address 10.16.1.2 255.255.0.0
> encapsulation frame-relay
> frame-relay map ip 10.16.1.1 201 broadcast
> frame-relay map ip 10.16.1.3 201 broadcast
> no frame-relay inverse-arp
> !
>
> IS the above config enough ?
Yes this is enough. You have disabled inverse arp and only used PVC 201 by
staticly mapping it.
>
> what are we really looking for when said that only used certain DLCI
number
> ?
"Using" the dlci means mapping to it. This includes mapping to it
unintentionally as well (via inverse arp).
Therefore you should disable inverse arp and only use the appropriate dlcis
by statically mapping them (i.e. "frame map" or frame interface-dlci).
>
> "show frame pvc" only show the DLCI that you used ??
>
> OR "show frame pvc" show you all the DLCI configured on the frame switch
but
> status for the "unused" DLCI will be "ACTIVE, UNUSED", and the rest of the
> used DLCI will be "ACTIVE, LOCAL" ??
All of the dlcis will be marked unused that you have not staticly configured
(being that you've disabled inverse arp) therefore satisfying the
requirement.
Just because they other dlcis in the frame cloud "show up" when you do a
"show frame pvc" that doesn't mean you are using them.
You are going to learn them via LMI no matter what you do, therefore only
"map" to the ones you should be using as per the instructions and you'll be
fine.
HTH.
Dan Pontrelli
>
> confused....
>
> Appreciate your input, thanks in advance.
> Yonger
>
>
>
>
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:31:52 GMT-3