Re: static lane question

From: Kenny Sallee (mischa@xxxxxxxxxxxxxx)
Date: Sat Aug 26 2000 - 16:06:28 GMT-3


   
I disagree. Unless I'm totally missing something, if you manually specify
the LES/BUS ( hard code them ) you don't need a LECS address. Here's a
working config off a 7507 router with an ATM card:

interface ATM4/0/0
 no ip address
 no ip directed-broadcast
 ip split-horizon
 atm pvc 1 0 5 qsaal
 atm pvc 2 0 16 ilmi
 hold-queue 100 in
!
interface ATM4/0/0.140 multipoint
 ip address 192.168.1.106 255.255.255.248
 ip access-group 140 in
 no ip mroute-cache
 lane server-atm-address <nsap>
 lane bus-atm-address <nsap>
 lane client ethernet spud
!
interface ATM4/0/0.198 multipoint
 description Net Ops Users
 ip address 192.168.2.1 255.255.255.0
 ip access-group 198 in
 ip access-group 195 out
 no ip mroute-cache
 lane server-atm-address <nsap>
 lane bus-atm-address <nsap>
 lane client ethernet meister
!
interface ATM4/0/0.206 multipoint
 description Sys Admin Users
 ip address 192.168.0.193 255.255.255.240
 ip access-group 196 in
 no ip directed-broadcast
 no ip mroute-cache
 lane server-atm-address <nsap>
 lane bus-atm-address <nsap>
 lane client ethernet thisworks!

I changed the IPs and elan names.....Please let me know what I'm missing

Kenny

----- Original Message -----
From: "Brian Best" <bbest@bellatlantic.net>
To: "'Matt Lachberg 3'" <Cisco@datastreet.com>; "CCIE Lab List (E-mail)"
<ccielab@groupstudy.com>
Sent: Saturday, August 26, 2000 7:42 AM
Subject: RE: static lane question

> You need the command lane config-atm-address <NSAP of LECS> on the
> interface.
>
>
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/12cgcr/switc
> h_r/xrlane.htm#xtocid776059
>
> Regards,
>
> Brian Best - CCIE #6128
>
>
>
> -----Original Message-----
> From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On Behalf Of
> Matt Lachberg 3
> Sent: Saturday, August 26, 2000 7:51 AM
> To: ccielab@groupstudy.com
> Subject: static lane question
>
>
> Why do I need a LECS if I specify the client, bus, and server NSAP's
> manually, Why is the client stuck in Initialstate? Any clues?
>
>
> interface ATM0.3 multipoint
> ip address 10.10.30.5 255.255.255.0
> no ip directed-broadcast
> lane client-atm-address 47.0091810000000050E2058501.00000C34B43A.03
> lane server-atm-address 47.0091810000000050E2058501.00000C34B43B.03
> lane bus-atm-address 47.0091810000000050E2058501.00000C34B43C.03
> lane server-bus ethernet elan3
> lane client ethernet elan3
> !
> LE Server ATM0.3, Elan name: elan3, Admin: up, State: operational
> Master/Backup: Backup, Type: ethernet, Max Frame Size: 1516
> locally set elan-id: not set
> elan-id obtained from LECS: not set
> ATM address: 47.0091810000000050E2058501.00000C34B43B.03
> LECS used: 47.007900000000000000000000.00A03E000001.00 NOT yet connected
>
>
> LE BUS ATM0.3, Elan name: elan3, Admin: up, State: operational
> Type: ethernet, Max Frame Size: 1516
> ATM address: 47.0091810000000050E2058501.00000C34B43C.03
>
>
> LE Client ATM0.3 ELAN name: elan3 Admin: up State: initialState
> Client ID: unassigned Next join attempt in 76 seconds
> Join Attempt: 27
> Known LE Servers: 0
> Last Fail Reason: Timeout on join request
> HW Address: 0000.0c34.b43a Type: ethernet Max Frame Size:
1516
> ATM Address: 47.0091810000000050E2058501.00000C34B43A.03
> VCD rxFrames txFrames Type ATM Address
> 0 0 0 configure
> 00.000000000000000000000000.000000000000.00
>
>
>
>
> Matthew Lachberg, CCNP, CCDP, MCSE
>
>



This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 08:24:30 GMT-3