Re: Lane without LECS part......(I lost track)

From: Lawrence Dwyer (dwyer@xxxxxxxxx)
Date: Mon Sep 11 2000 - 06:07:00 GMT-3


   
   You do not have to have a LECS configured if you are willing to
   manually configure your LEClients to point to the LES of the
   particular ELAN you wish it to belong too. On the military post I work
   at, they have 40 subnets and no LECS.
   LECS points to the LES a client is supposed to join, but you can point
   that client directly.
   Larry
   
   Dave McFetridge wrote:
   
     John, You realize you must have a LANE configuration server
     configured. You would typically configure this on the ATM switch
     and clients/routers would learn this via ILMI. If you don't have
     signaling and ILMI configured than you'll never find who is the LES
     for the ELAN your attempting to be a LEC for. I hope this is clear.
     Here are some configs to help, one with a router being the
     LECS,LES,BUS, and LEC.. and one with the switch as the LECS and the
     router as the LES,BUS, and LEC.Hope this clears things up for
     you....Dave McFetridgeRouter as LECS/LES/BUS/LEC with static
     entries......R1lane database LANE
       name 13 server-atm-address
     50.111111111111111111111111.000011110001.01
     !interface ATM0/0
      no ip address
      no ip directed-broadcast
      atm nsap-address 50.111111111111111111111111.000011110000.00
      atm pvc 1 0 5 qsaal
      atm pvc 2 0 16 ilmi
      no atm ilmi-keepalive
      lane config config-atm-address
     50.111111111111111111111111.000011110003.00
      lane config database LANE
      lane global-lecs-address
     50.111111111111111111111111.000011110003.00
      lane client-atm-address
     50.111111111111111111111111.000011110000.01
      lane server-atm-address
     50.111111111111111111111111.000011110001.01
      lane bus-atm-address 50.111111111111111111111111.000011110002.01
     !
     interface ATM0/0.1 multipoint
      ip address 137.20.224.1 255.255.255.0
      no ip directed-broadcast
      ip ospf network non-broadcast
      lane client-atm-address
     50.111111111111111111111111.000011110000.01
      lane server-atm-address
     50.111111111111111111111111.000011110001.01
      lane bus-atm-address 50.111111111111111111111111.000011110002.01
      lane server-bus ethernet 13
      lane client ethernet 13
     !LS1010 as LECS, Router as LES/BUS/LEC.....LS1010#!
     atm lecs-address-default
     47.0091.8100.0000.0060.3e5c.1001.0060.3e5c.1005.00 1
     atm address 47.0091.8100.0000.0060.3e5c.1001.0060.3e5c.1001.00
     !
     lane database TEST
       name ELAN2 server-atm-address
     47.00918100000000603E5C1001.0050732EFA03.02
       name ELAN1 server-atm-address
     47.00918100000000605CC9BE01.00605CC9BE03.01
     !interface ATM2/0/0
      no ip address
      atm maxvp-number 0
      lane config auto-config-atm-address
      lane config database TESTR2
     !
     interface ATM0
      mtu 1500
      no ip address
      atm pvc 5 0 5 qsaal
      atm pvc 16 0 16 ilmi
     !
     interface ATM0.1 multipoint
      ip address 172.16.100.2 255.255.255.0
      lane server-bus ethernet ELAN1
      lane client ethernet ELAN1
     !
     interface ATM0.2 multipoint
      ip address 172.16.200.2 255.255.255.0
      lane server-bus ethernet ELAN2
      lane client ethernet ELAN2
     !
     -----Original Message-----
     From: John Conzone [mailto:jkconzone@home.com]
     Sent: Sunday, September 10, 2000 10:15 AM
     To: ccielab
     Subject: Lane without LECS part......(I lost track)
     
     
         I've been in the archives and pulled up my old mails and I
     still can't get LANE working without buliding a LECS and a LECS
     database. I specified the SERVER and BUS addreses and it woudl not
     work until I built a LECS. Does anyone have working configs of 2
     routers running LANE without a LECS so I canuse them this weekend
     to try again? Thanks!
     
   --
   Lawrence Dwyer, MCSE CCNA
   Project Officer
   Telemedicine Advanced
     Technology Research Center
   
   (301) 619-7946



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