From: ccie2be (ccie2be@nyc.rr.com)
Date: Tue Mar 22 2005 - 10:44:47 GMT-3
Hi,
Although the config's below are correct, I thought it might be helpful to
some people to point out some of the logic underlying the config's.
Notice under the physical interface the 2 pvc's:
atm pvc 2 0 5 qsaal
atm pvc 1 0 16 ilmi
The pvc for qsaal is so that atm circuits can be brought up and torn down
when there's traffic to send. Conceptually, this is equivalent to what
happens with isdn - the svc circuit should only be established when there's
traffic to send.
The ilmi pvc is equivalent to frame relay lmi - it's used to exchange
management info between your atm interface and the atm switch. Among other
things, one of the pieces of info the atm interface gets from the switch is
the nsap prefix and therefore, when you look under the sub-interface config,
you see that there's no nsap configured. Instead, you see an esi which is
the atm equivalent of a host address. When the nsap prefix learned from the
atm switch is combined with the esi manually configured, you have a complete
atm nsap address.
If you're not provided with the prefix portion of the atm nsap, only the esi
portion for the remote destinations and you have to configure static
mappings, realize that you can find out what the nsap prefix is by issuing
the show atm ilmi-status command.
One thing you have to remember is that the qsaal and ilmi pvc's are ALWAYS
configured under the main atm interface, never on the sub-interface. But,
you don't need to memorize the actual vci or vpi values as these can very
easily and quickly be found in the atm documentation.
Also, notice that there can be multiple static mappings under the multipoint
sub-interface. This is equivalent to configuring a frame relay physical or
multipoint sub-interface where it's possible to have multiple destinations
and therefore you need some method of resolving the layer 3 ip address to a
layer 2 atm address.
One last thing: the config's below show how svc's with static mappings are
done. It's also possible to config svc's using dynamic mappings but that's
for another time.
HTH, Tim
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
Jongsoo.Kim@Intelsat.com
Sent: Monday, March 21, 2005 11:41 PM
To: dennisjhartmann@hotmail.com; ccielab@groupstudy.com
Subject: RE: Working ATM SVC configuration
Here we go
R6
interface ATM0/0
no ip address
atm pvc 2 0 5 qsaal
atm pvc 1 0 16 ilmi
no atm ilmi-keepalive
!
interface ATM0/0.1 multipoint
ip address 137.10.69.6 255.255.255.240
atm esi-address 666666666666.66
!
svc R9 nsap 47.0091810000000060705C4E01.999999999999.99
protocol ip 137.10.69.9 broadcast
encapsulation aal5snap
svc R6 nsap 47.0091810000000060705C4E01.666666666666.66
protocol ip 137.10.69.6
encapsulation aal5snap
R9
interface ATM0/0
no ip address
atm pvc 1 0 16 ilmi
atm pvc 2 0 5 qsaal
no atm ilmi-keepalive
!
interface ATM0/0.1 multipoint
ip address 137.10.69.9 255.255.255.240
atm esi-address 999999999999.99
!
svc R9 nsap 47.0091810000000060705C4E01.999999999999.99
protocol ip 137.10.69.9
encapsulation aal5snap
!
!
svc R6 nsap 47.0091810000000060705C4E01.666666666666.66
protocol ip 137.10.69.6 broadcast
encapsulation aal5snap
!
-----Original Message-----
From: Dennis J. Hartmann [mailto:dennisjhartmann@hotmail.com]
Sent: Monday, March 21, 2005 10:03 PM
To: ccielab@groupstudy.com
Subject: Working ATM SVC configuration
Does anyone have a working ATM P2P SVC configuration they can post? I'm
only interested in the two routers, not the ATM switch. Thanks.
Sincerely,
Dennis J. Hartmann
White Pine Communications
CCSI/CCIP/CCNP/CCDP/CCNA/CCDA
Cisco IP Voice Support & Design Specialist
Cisco Optical, VPN & IDS Specialist
MCSE
This archive was generated by hypermail 2.1.4 : Sun Apr 03 2005 - 17:56:49 GMT-3