From: Gary Bradford (glbradford@xxxxxxxxxxx)
Date: Tue Jan 25 2000 - 02:57:00 GMT-3
The examples would work even better if you use different VC's for ILML and
QSAAL
>From: naushad prasla <naushad.prasla@sabre.com>
>Reply-To: naushad prasla <naushad.prasla@sabre.com>
>To: Denton Bobeldyk <denny@kentwoodps.org>
>CC: groupstudy <ccielab@groupstudy.com>
>Subject: Re: ATM Clip Addressing Question
>Date: Sun, 23 Jan 2000 11:13:16 -0600
>MIME-Version: 1.0
>Received: from [208.242.122.8] by hotmail.com (3.2) with ESMTP id
>MHotMailBA5487EC004FD820F3A6D0F27A0833331; Sun Jan 23 09:40:06 2000
>Received: from localhost (mail@localhost)by groupstudy.com (8.9.3/8.9.3)
>with SMTP id NAA00922;Sun, 23 Jan 2000 13:17:58 GMT
>Received: by groupstudy.com (bulk_mailer v1.12); Sun, 23 Jan 2000 13:17:58
>+0000
>Received: (from listserver@localhost)by groupstudy.com (8.9.3/8.9.3) id
>NAA00918GroupStudy Mailer; Sun, 23 Jan 2000 13:17:57 GMT
>Received: from mailgate2.sabre.com (mailgate2.sabre.com [199.100.49.126])by
>groupstudy.com (8.9.3/8.9.3) with ESMTP id NAA00910GroupStudy Mailer; Sun,
>23 Jan 2000 13:17:56 GMT
>Received: from mailhub1.sabre.com (mailhub1.sabre.com [192.168.133.110])by
>mailgate2.sabre.com (8.9.3/8.9.3) with ESMTP id LAA10808;Sun, 23 Jan 2000
>11:15:15 -0600 (CST)
>Received: from sabre.com ([10.139.1.27])by mailhub1.sabre.com (8.9.3/8.9.3)
>with ESMTP id LAA01511;Sun, 23 Jan 2000 11:13:17 -0600 (CST)
>From nobody@groupstudy.com Sun Jan 23 09:40:33 2000
>Message-ID: <388B36AC.22AF678F@sabre.com>
>Organization: Sabre Inc.
>X-Mailer: Mozilla 4.5 [en]C-CCK-MCD TSG on TSG Network Build Date -
>[02-15-1999]-A (Win95; I)
>X-Accept-Language: en
>References: <388A75AA.5F6FC6A@kentwoodps.org>
>Sender: nobody@groupstudy.com
>
>Denton,
>
>You are pretty much on track. The example you quoted with "random" ATM
>address won't work. Quite frankly, I was'nt able to make that example work
>either. From a configuration perspective, ATM NSAP address is a 20 byte
>address and is divided into three major parts. ATM Prefix, ESI, and the
>Selector. ATM Prefix is a 13 byte field, ESI is a 6 byte field, just like
>the MAC address, and the Selector is a 1 byte field. Thats all you have to
>remember regarding NSAP addresses.
>
>ATM Prefix should be obtained from the ATM Switch i.e. LS1010 using "atm
>pvc
>
>1 0 16 ilmi" command. PVC number 16 has a special meaning and is documented
>as a "well known" for ILMI. ILMI is a Management PVC to retrieve
>configuration information from the Switch such as the Address Prefix.
>
>Use "atm esi address" command to assign any 7 byte address for ESI and the
>Selector if not already provided to you. I generally use the router number
>as the esi address if configuring the major interface unless provided
>otherwise.
>
>Use "atm pvc 1 0 5 qsaal" command to instruct the ATM interface to use PVC
>5
>
>as a signally PVC. QSAAL is the type of signal and PVC 5 is a "well known"
>PVC for signalling.
>
>So if you have two Routers connected via LS1010 switch, you would use the
>following:
>
>Router 1 -- Acting as an Arp Server
>int atm 0
> atm pvc 1 0 5 qsaal -- Signalling PVC
> atm pvc 1 0 16 ilmi -- Management PVC
> atm esi address 111111111111.11
> atm arp-server self -- This interface act as an ARP Server for this
>Router.
>
>
>Router 2 -- Acting as an Arp Client
>int atm 0
> atm pvc 1 0 5 qsaal -- Signalling PVC
> atm pvc 1 0 16 ilmi -- Management PVC
> atm esi address 222222222222.22
> atm arp-server 111111111111.11 -- This interface act as an ARP Client
>point to the
> Router1's ATM NSAP address to
>talk to the ARP Server.
>
>
>As you noticed, there is no need to configure an entire 20 byte NSAP
>address. Once you configure an ILMI PVC 16 and do "no shut" on an interface
>you should receive the first 13 bytes of the ATM address from the Switch
>called the Prefix. This Prefix will automatically be prepended to your 7
>byte ESI/Selector address. Hence providing a complete 20 byte NSAP Address.
>You can see what that address is by performing "show lane default" command.
>
>
>Hope this helps.
>
>Naushad Prasla
>
>Denton Bobeldyk wrote:
>
> > Ok, I'm feeling more and more confident with the ATM commands, but
> > I'm having a problem swallowing this whole NSAP stuff.
> >
> > If I am given a router with an ATM interface and am asked
> > to configure that interface for ATM Clip.
> > It would appear to me that I would have to go through the following
> > steps (according
> > to the Doc CD):
> >
> > interface atm 0
> > ip address 10.0.0.1 255.0.0.0 <--- Assign it an IP address
> > atm nsap-address ac.1533.66.020000.0000.0000.0000.0000.0000.0000.00
> > <-- **See Note 1**
> > atm rate-queue 1 100 <-- Don't think I really need this
> > atm pvc 1 0 5 qsaal <-- This does something for my SVCs
> > atm arp-server <-- This tells the network that I am going to be the
> > arp-server. aka translate the IP
> > addresses to ATM addresses.
> >
> > **Note 1: This is where I get stuck. I am under the impression that
> > you can simply create this
> > NSAP address out of thin air... Are there any rules you have to follow?
> >
> > One you have this scenario up and running how can you check to make sure
> > it's doing
> > what's supposed to be doing? (i.e. what 'show' commands)
> > Now in theory I should be able to ping another IP address on this ATM
> > cloud or setup routing
> > to it correct??
> > Any quick responses would be most appreciative!!!
> >
> > -Denny
> >
> > --
> > -*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-
> > Denton Bobeldyk MCNE, CCDA, CCNA, CCSI
> > Email: denny@kentwoodps.org
> > Phone: 616-530-9196
> >
> > Master CNE - Connectivity
> > Cisco Certified Design Associate
> > Cisco Certified Network Associate
> > Cisco Certified Systems Instructor
> >
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 08:22:45 GMT-3