From: Lachlan Kidd (lkidd@xxxxxxxxxxxxxxxxxxx)
Date: Mon Aug 13 2001 - 22:36:43 GMT-3
Hi Taz,
Yep, looks pretty good to me. The best analogy is can think of is an IS
DN
dial service. When you configure a dialer map you still have to map the
remote ip address and the remote phone number. When the router sees traffic
going to that address it knows to dial that number. With SVCs it's exactly
the same. Your are mapping the remote NSAP address with the remote IP
address.
HTH,
Lachlan
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On Behalf Of
Taz Kazam
Sent: Tuesday, 14 August 2001 10:53 AM
To: ccielab@groupstudy.com
Subject: ATM SVCs
Hi
Im configuring ATM SVC's. I do the following actions:
1. pvc [name] 0/16 ilmi
1a. atm ilmi-keepalives
2. pvc [name] 0/5 qsaal
Either:
3. atm esi-address 000000000007.07
or
4. atm nsap-address ???????(local nsap address)???????
Now here's where I get stuck! Its that it all? or do I
need to:
5. svc [name] nsap-address ???(remote nsap
address)????
6. protocol ip 133.1.78.7 broadcast.
>From my reading the whole point of SVC's are that they
come online as and when traffic is generated, hence,
there is no need to specify a static mapping, however,
in the Cisco documentation, it highlights point 5.
and 6. as a requirment.
help!
Thanks
Taz.
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:31:50 GMT-3