From: Mark Olson (molson@xxxxxxxxxx)
Date: Tue Nov 02 1999 - 11:07:58 GMT-3
Hi Brian-
Your router configs look good even though, as Scott mentioned, you really
don't need to use the 'atm nsap-address' when you have ILMI config'ed.
The esi-address command should do the trick. But it should still work. I'd
look a
little closer at the 1010 config. Turn on 'debug atm sig-all' on your router
(and/or 1010) then ping the other router ATM interface IP address. I'm
guessing that the call is getting cleared possibly due to the 1010 thinking
it doesn't know the route to the destination NSAP. If so, you might try to
config
ATM static routes on the 1010. A sh atm route on the 1010 is also a handy
command.
Of course, that's just a guess. The debug output should reveal the real reason
why the call isn't successful. Also, the sh atm ilmi-status (or sh atm ilmi on
older code) will show you what prefix the router learned from the 1010 via
ILMI.
Hope that helps you out!!
Mark
Brian Van Benschoten wrote:
> The sample config is not working. I took your advice and changed the first
> 2 bytes of the NSAP to 39.
>
> that didn't seem to help me. I wonder if my ESI address is valid ?
>
> any other thoughts
> ----- Original Message -----
> From: Scott F. Robohn <sfr@ccci.com>
> To: Brian Van Benschoten <vader@inxpress.net>
> Cc: <ccielab@groupstudy.com>
> Sent: Monday, November 01, 1999 8:26 PM
> Subject: Re: Changing the ATM NSAP address
>
> > Brian,
> >
> > In general, the first 13 bytes of all addresses in your
> > network should be unique. Does your example config work?
> > If so, it may be due to the fact that you're connected to
> > only one switch. Throwing a second switch in the middle may
> > break things.
> >
> > Also, when you have ILMI configured, you shouldn't have to
> > hard-code an NSAP address on edge devices. ILMI takes the
> > 13-byte prefix of the switch and automatically assigns it to
> > any attached edge devices.
> >
> > You may run into problems with the AFI (Address Format
> > Identifier, the first byte) being something other than 39,
> > 45, 47, BD, C3, or C5.
> >
> > While anything is game on the exam, I would expect the lab
> > to focus on LANE and PVCs.
> >
> > HTH,
> > Scott
> >
> > Brian Van Benschoten wrote:
> > >
> > > Are there certain address combinations that wont work when changing the
> NSAP
> > > or ESI address
> > > I'm doing some testing with SVCs
> > > Here is what I have:
> > >
> > > LS1010
> > > !
> > > atm address 66.1234.0000.0000.0000.0000.0000.6666.6666.6666.00
> > > atm router pnni
> > > no aesa embedded-number left-justified
> > > node 1 level 56 lowest
> > > redistribute atm-static
> > >
> > > -----------------Router 1 -----------------
> > > interface ATM0/0
> > > ip address 192.168.50.1 255.255.255.0
> > > no ip directed-broadcast
> > > map-group brian
> > > atm nsap-address 66.123400000000000000000000.131313131313.00
> > > atm pvc 1 0 5 qsaal
> > > atm pvc 2 0 16 ilmi
> > > no atm ilmi-keepalive
> > > map-list brian
> > > ip 192.168.50.2 atm-nsap 66.123400000000000000000000.141414141414.00
> > >
> > > ----------------Router 2 -------------
> > >
> > > interface ATM0/0
> > > ip address 192.168.50.2 255.255.255.0
> > > no ip directed-broadcast
> > > atm nsap-address 66.123400000000000000000000.141414141414.00
> > > atm pvc 1 0 5 qsaal
> > > atm pvc 2 0 16 ilmi
> > > no atm ilmi-keepalive
> > > !
> > > svc r13 nsap 66.123400000000000000000000.131313131313.00
> > > protocol ip 192.168.50.1 broadcast
> > >
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 08:21:55 GMT-3