Re: ATM SVC CLIP with esi-address configuration

From: Scott F. Robohn (sfr@xxxxxxxxxxxxxx)
Date: Mon Aug 07 2000 - 13:51:06 GMT-3


   
Ken,

You don't have 'map-group svcclip' on atm3/0.

But: Why are you trying to do CLIP *and* SVCs with map-list
on the same subnet? You really should do one or the other
(CLIP or SVCs w/map-list).

Note that your atmarpserver doesn't know the NSAP address
for 192.168.1.2.

sfr

Kenneth Kriel wrote:
>
> Gentleman, we have a problem !!
>
> On my router :
>
> interface ATM3/0
> ip address 192.168.1.2 255.255.255.0
> atm pvc 1 0 5 qsaal
> atm pvc 2 0 16 ilmi
> atm esi-address 000000000002.00
> no atm ilmi-keepalive
> atm arp-server self
>
> map-list svcclip
> ip 192.168.1.1 atm-nsap 47.00918100000000603E5CAA01.00603E5CAA01.00
> broadcast
>
> This is my config, can you spot the issue ?
>
> R4#sh atm ilmi-sta
>
> Interface : ATM3/0 Interface Type : Private UNI (User-side)
> ILMI VCC : (0, 16) ILMI Keepalive : Disabled
> ILMI State: UpAndNormal
> Peer IP Addr: 192.168.1.1 Peer IF Name: ATM1/0/0
> Peer MaxVPIbits: 8 Peer MaxVCIbits: 14
> Active Prefix(s) :
> 47.0091.8100.0000.0060.3e5c.aa01
> End-System Registered Address(s) :
> 47.0091.8100.0000.0060.3e5c.aa01.0000.0000.0002.00(Confirmed)
>
> <<<<<<AND>>>>>>
>
> R4#sh atm arp
>
> Note that a '*' next to an IP address indicates an active call
>
> IP Address TTL ATM Address
> ATM3/0:
> * 192.168.1.2 18:49 4700918100000000603e5caa0100000000000200
>
> <<<<<AND>>>>>>
>
> R4#sh atm map
> Map list svcclip : PERMANENT
> ip 192.168.1.1 maps to NSAP 47.00918100000000603E5CAA01.00603E5CAA01.00
> , broadcast
>
> Map list ATM3/0_ATM_ARP : DYNAMIC
> arp maps to NSAP 47.00918100000000603E5CAA01.000000000002.00
> , connection up, VC 124, VPI 0, VCI 33, ATM3/0
> ip 192.168.1.2 maps to NSAP 47.00918100000000603E5CAA01.000000000002.00
> , broadcast, connection up, VC 125, VPI 0, VCI 34, ATM3/0
>
> It looks like all is fine !!!
>
> I see my address is registered with the LS1010 and I would like to ping the
> other end of the SVC - 192.168.1.1 but I always get encapsulation failed on
> this router, with the debug ip packet command.
>
> Can anyone tell me why ?
>
> Thank you
>
> Ken
>



This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 08:24:22 GMT-3