Nicolas,

FR switch DOES NOT participate in inverse ARP processes. Only
end-nodes (FR DTE devices) do. Your router sent a "question" on all
DLCIs asking routers to tell it what are their IPs. They obliged and
you got that information. They don't have to be on the same subnet, as
inverse ARP is unaware of subnets. It just reports what it hears.

--
Marko Milivojevic - CCIE #18427
Senior Technical Instructor - IPexpert

FREE CCIE training: http://bit.ly/vLecture

Mailto: [email protected]
Telephone: +1.810.326.1444
Web: http://www.ipexpert.com/

On Wed, Sep 22, 2010 at 20:44, Nicolas MICHEL <[email protected]> wrote:
> Ok I dont really know what's behind or within the cloud .
>
> So it would mean that some other routers would advertise their DLCI via
> INARP to some FRSWITCH and that FRSWITCH is sending me the results hence the
> fact that I got several DLCI and maps from Others subnets ?
>
>
> I thought that I would only see informations about "connected" host within
> the FR cloud
>
>
>
> Thanks for the help
>
> 2010/9/22 Jay Taylor <[email protected]>
>>
>> Inverse ARP will do that when multiple DLCI's are advertised to the DCE.
>>
>>
>> On Wed, Sep 22, 2010 at 2:31 PM, Nicolas MICHEL <[email protected]>
>> wrote:
>>>
>>> Hey there.
>>>
>>> I got a router connected to a FR cloud and here is the config on the
>>> router
>>>
>>> R6#sh run int s0/0/0
>>> Building configuration...
>>>
>>> Current configuration : 119 bytes
>>> !
>>> interface Serial0/0/0
>>>  ip address 54.1.1.6 255.255.255.0
>>>  encapsulation frame-relay
>>>  frame-relay lmi-type cisco
>>> end
>>>
>>>
>>>
>>> Cant be simpler can it be ? :D
>>>
>>>
>>> I d like to understand why do I got frame map and LMI DLCI from subnets
>>> that are not DIRECTLY connected to my interface
>>>
>>> R6#sh frame pvc | i DLCI
>>> DLCI = 51, DLCI USAGE = LOCAL, PVC STATUS = ACTIVE, INTERFACE =
>>> Serial0/0/0
>>> DLCI = 100, DLCI USAGE = LOCAL, PVC STATUS = ACTIVE, INTERFACE =
>>> Serial0/0/0
>>> DLCI = 101, DLCI USAGE = LOCAL, PVC STATUS = ACTIVE, INTERFACE =
>>> Serial0/0/0
>>> DLCI = 201, DLCI USAGE = UNUSED, PVC STATUS = ACTIVE, INTERFACE =
>>> Serial0/0/0
>>> DLCI = 301, DLCI USAGE = UNUSED, PVC STATUS = ACTIVE, INTERFACE =
>>> Serial0/0/0
>>> DLCI = 401, DLCI USAGE = UNUSED, PVC STATUS = ACTIVE, INTERFACE =
>>> Serial0/0/0
>>>
>>> $R6#sh frame map
>>> Serial0/0/0 (up): ip 54.1.3.254 dlci 51(0x33,0xC30), dynamic,
>>>               broadcast,, status defined, active
>>> Serial0/0/0 (up): ip 54.1.2.254 dlci 100(0x64,0x1840), dynamic,
>>>               broadcast,, status defined, active
>>> Serial0/0/0 (up): ip 54.1.1.254 dlci 101(0x65,0x1850), dynamic,
>>>               broadcast,, status defined, active
>>>
>>>
>>> Seeking the informations in books and will post if I find
>>> --
>>> Nicolas MICHEL
>>> Ingenieur Réseaux et Securité (CCNA/CCNP and CCIE Pending)
>>> Centre d’Expertise et d’Assistance Clients
>>> Spie communication
>>> Tél  : +33 (0)141464924
>>> Mob: +33 (0)608727597
>>>
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> For more information regarding industry leading CCIE Lab training, please
>>> visit www.ipexpert.com
>>>
>>
>
>
>
> --
> Nicolas MICHEL
> Ingenieur Réseaux et Securité (CCNA/CCNP and CCIE Pending)
> Centre d’Expertise et d’Assistance Clients
> Spie communication
> Tél  : +33 (0)141464924
> Mob: +33 (0)608727597
>
>
>
>
>
> _______________________________________________
> For more information regarding industry leading CCIE Lab training, please
> visit www.ipexpert.com
>
>
_______________________________________________
For more information regarding industry leading CCIE Lab training, please visit 
www.ipexpert.com

Reply via email to