From: Patrick Bikar (pbikar@xxxxxxxxx)
Date: Wed Jan 17 2001 - 05:37:24 GMT-3
Dennis,
Thanks for replying.
But : the advantage of classical IP is that you don't need to configure the
nsap addresses of the remotes. So, using the command "ATM svc name (optional)
nsap address" gets you back in the normal SVC operations.
Still, if you want to have the benefits of classical IP (that is, you don't
have to specify the remote nsap addresses), I don't see how and where you can
apply traffic parameters, without specifying the remote nsap address.
Any idea ?
Patrick.
At 18:28 16/01/2001 -0500, you wrote:
>Patrick
>in ATM interface do ATM svc name (optional) nsap address and this will give
>you a svc prompt . In this prompt you can configure your abr or what ever
>you want.Then leave config mode and do a sh ATM svc and you should see those
>parameters show up.
>
>Dennis
>
>Dennis Rogell
>Email : dennis_rogell@milgocom
>Phone: (954) 846-5128
>
>> -----Original Message-----
>> From: Patrick Bikar [SMTP:pbikar@cisco.com]
>> Sent: Tuesday, January 16, 2001 15:30
>> To: ccielab@groupstudy.com
>> Subject: Classical IP with SVC : how to apply traffic parameters
>>
>> Hi all !
>>
>> I cannot figure out how to apply traffic parameters when using classical
>> ip and SVCs, such as in the following example :
>> !
>> interface ATM0
>> ip address 1.1.1.1 255.255.255.0
>> no ip directed-broadcast
>> pvc ILMI-MANAGEMENT 0/16 ilmi
>> pvc SIGNALING 0/5 qsaal
>> atm esi-address 123412341234.12
>> atm ilmi-keepalive 3
>> atm arp-server self
>> !
>>
>> As the SVCs are built dynamically, where and how would we specify, for
>> example, that the SVC is "vbr-nrt" ?
>>
>> Is it possible to do so ?
>> Thanks,
>> Patrick.
>>
>>
>> Patrick.
>> CCNP, Belgium.
>> Lab:15/03/2001
>>
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:27:32 GMT-3