Re: Difference b/w interface-dlci & local-dlci

Me too, I would like to know.
The CLI help is very confusing, talking about "source" DLCI. What is that ?

AFAIK, DLCI is just for destination addressing, there is no source DLCI.
You need 2 things at a router frame interface:
1-Define what DLCI you put in a frame to go to some place (i.e. frame
mapping), TX side
2-Define what (sub)interface deals with an incoming frame, RX side

You use the same DLCI for both directions of a VC, per hop.

frame map command address #1 (show frame map),
interface-dlci address #2 (show frame pvc).
Both can be kind of automatically been taken care off.
#1 by inverse-arp, #2 because all referenced DLCIs are associated with
the main interface by default.

But local-dlci is only available at the main interface.

???
-Carlos
P.S.
Never run into a lab that needed that command.

Malik Nouman Ahmad @ 12/02/2011 07:35 -0300 dixit:
> Hi,
>
> Can anybody explain the difference b/w *frame-relay local-dlci* and
> *frame-relay
> interface-dlci*?
>
> I read on Cisco's website which mentions that the former is used mostly for
> testing purpose when the two devices are connected back-to-back and we want
> to assign the local DLCI as there is no LMI to get the DLCI value. But the
> latter command is used for the same reason when we use *no frame-relay
> inverse-arp* so that we can assign the DLCI manually
>
> Please explain
>
> Regards,
> Malik
>
>
> Blogs and organic groups at http://www.ccie.net
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
>
>
>
>
>
>
>

-- 
Carlos G Mendioroz  <tron_at_huapi.ba.ar>  LW7 EQI  Argentina
Blogs and organic groups at http://www.ccie.net