From: Steve McNutt (lpd@xxxxxxxxxxxxxxxx)
Date: Sun Oct 15 2000 - 03:01:47 GMT-3
I know there was a thread going on about this about a month ago and I did
look through it. I'm bringing it up again to put my findings where they
might help someone who doesn't have good access to ATM gear.
I after finishing a bootcamp lab tonight I decided to take a point to point
serial link in my network topology and replace it with ATM classical IP and
then LANE. When I went to do the LANE config I decided to try and do it
without a LECS. after staring at various status screens and debug output It
definitely looked like the LES was rejecting the LEC connection requests
because it wanted to consult the LECS and verify that it's supposed to be
active on the network. I put in the NSAP to the LECS on the subinterface
that my LES was defined on and BAM, all of the clients attached.
AFAICT the clients don't need the LECS but the LES has to get permission
from the LECS to activate. This is probably to prevent people from running
rogue ELANs/LESs on your ATM network.
I checked the LANE command reference and there doesn't appear to be any way
to tell the LES not to check with the LECS before accepting an incoming call
from a client.
What follows are the fully working configs, and output showing the LES with
and without the lane config-atm-address punched in.
hostname r6
!
lane database ccie
name ccie server-atm-address 47.000580FFE1000000F21A2FA6.009086122821.01
name ccie elan-id 1
!
!
interface ATM1/0
atm pvc 1 0 16 ilmi
atm pvc 2 0 5 qsaal
no atm ilmi-keepalive
lane config auto-config-atm-address
lane config database ccie
!
interface ATM1/0.1 multipoint
lane config-atm-address 47.000580FFE1000000F21A2FA6.009086122823.00
lane server-bus ethernet ccie elan-id 1
!
interface ATM1/0.2 multipoint
ip address 50.1.1.2 255.255.255.0
lane server-atm-address 47.000580FFE1000000F21A2FA6.009086122821.01
lane client ethernet ccie
!
hostname r7
!
interface ATM3/0
no ip address
no ip directed-broadcast
atm pvc 1 0 5 qsaal
atm pvc 2 0 16 ilmi
no atm ilmi-keepalive
!
interface ATM3/0.1 multipoint
ip address 50.1.1.1 255.255.255.0
no ip directed-broadcast
lane server-atm-address 47.000580FFE1000000F21A2FA6.009086122821.01
lane client ethernet ccie
!
let's remove the lane config-atm-address. notice how our clients are in a
waiting state on the LES (also note that the LES thinks it's a backup!)
r6#sh lane server
LE Server ATM1/0.1, Elan name: ccie, Admin: up, State: operational
Master/Backup: Backup, Type: ethernet, Max Frame Size: 1516
locally set elan-id: 1
elan-id obtained from LECS: 1
ATM address: 47.000580FFE1000000F21A2FA6.009086122821.01
LECS used: 47.007900000000000000000000.00A03E000001.00 NOT yet connected
proxy/ (ST: Init, Conn, Waiting, Adding, Joined, Operational, Reject, Term)
lecid ST vcd pkts Hardware Addr ATM Address
1 W 78 1 0090.8612.2820
47.000580FFE1000000F21A2FA6.009086122820.02
2 W 69 2 0060.3e12.8860
47.000580FFE1000000F21A2FA6.00603E128860.01
After a while this state will time out and the clients will be disconnected.
at that point the clients have no SVCs up and are removed from ILMI
r7#sh atm ilmi-status
Interface : ATM3/0 Interface Type : Private UNI (User-side)
ILMI VCC : (0, 16) ILMI Keepalive : Disabled
ILMI State: UpAndNormal
Peer IP Addr: 10.0.1.20 Peer IF Name: 1A1
Peer MaxVPIbits: 10 Peer MaxVCIbits: 16
Active Prefix(s) :
47.0005.80ff.e100.0000.f21a.2fa6
Let's inform the LES of the NSAP of the LECS:
r6(config)#int atm1/0.1
r6(config-subif)#lane config-atm-address
47.000580FFE1000000F21A2FA6.009086122823.00
r6#sh lane server
LE Server ATM1/0.1, Elan name: ccie, Admin: up, State: operational
Master/Backup: Master, Type: ethernet, Max Frame Size: 1516
locally set elan-id: 1
elan-id obtained from LECS: 1
ATM address: 47.000580FFE1000000F21A2FA6.009086122821.01
LECS used: 47.000580FFE1000000F21A2FA6.009086122823.00 connected, vcd 126
control distribute: vcd 130, 2 members, 2 packets
proxy/ (ST: Init, Conn, Waiting, Adding, Joined, Operational, Reject, Term)
lecid ST vcd pkts Hardware Addr ATM Address
1P O 129 2 0090.8612.2820
47.000580FFE1000000F21A2FA6.009086122820.02
2P O 136 2 0060.3e12.8860
47.000580FFE1000000F21A2FA6.00603E128860.01
r7#sh atm ilmi-status
Interface : ATM3/0 Interface Type : Private UNI (User-side)
ILMI VCC : (0, 16) ILMI Keepalive : Disabled
ILMI State: UpAndNormal
Peer IP Addr: 10.0.1.20 Peer IF Name: 1A1
Peer MaxVPIbits: 10 Peer MaxVCIbits: 16
Active Prefix(s) :
47.0005.80ff.e100.0000.f21a.2fa6
End-System Registered Address(s) :
47.0005.80ff.e100.0000.f21a.2fa6.0060.3e12.8860.01(Confirmed)
-steve
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 08:25:27 GMT-3