From: Charles (mfortune@xxxxxxxx)
Date: Tue Jul 18 2000 - 23:33:41 GMT-3
John,
I have the exact same problem in the lab and currently have no resolution.
My lab is now in use by someone else so it may be a while before I can get
in to test more. I do know that it worked previously to my clearing the
configs and starting over. Here are a few interesting points regarding the
CAT5K that I found on CCO. One of them is very detailed in the way the
configuration is set up on the Catalyst. Let us know what you find.
CSCdi65004
http://www.cisco.com/univercd/cc/td/doc/product/lan/cat5000/c5krn/sw_rns/78_
5861.htm
If you have a LECS or LES/BUS configured on an ATM module and you replace
the supervisor engine module (on Catalyst 5000 series switches only) or move
the ATM module from one slot to another, the ATM addresses (NSAPs) are
modified. Be sure to update the LECS database configuration with the new
NSAP values.
http://www.cisco.com/univercd/cc/td/doc/product/lan/cat5000/rel_4_4/config/a
tm.htm#42458
Occasionally some LECs that are configured on an ATM module might not come
up after you reset a Catalyst 5000 Series switch. To recover from this
problem, reconfigure the LECs that failed to come up on the ATM module.
(CSCdi65004)
----- Original Message -----
From: John McCulley <jhmac2@hotmail.com>
To: <ccielab@groupstudy.com>
Sent: Tuesday, July 18, 2000 1:25 PM
Subject: ATM LECS / LES on CAT
> Thank you for your responses on the previous post!
>
> After trying several suggestions that I received, I
> still have not been able to get the LEC to intialize
> on either router when the LECS and LES are configured
> on the Catalyst LANE module. The LECS, LES, BUS, and
> Client all are operational on the LANE Module. Again,
> once I move the LES to either router it works fine.
> Any suggestions??
>
> Configs:
>
> R1
> interface ATM1/0/0
> no ip address
> no ip directed-broadcast
> no ip route-cache distributed
> no atm ilmi-keepalive
> lane config config-atm-address 47.00918100000000D0C08C9401.00D0C08C9023.00
> !
> interface ATM1/0/0.1 multipoint
> ip address 137.20.80.8 255.255.255.0
> no ip directed-broadcast
> lane config-atm-address 47.00918100000000D0C08C9401.00D0C08C9023.00
> lane client-atm-address 47.00918100000000D0C08C9401.00B08E4BF820.01
> lane client ethernet ELAN1
> !
> interface ATM1/0/0.2 multipoint
> ip address 137.20.90.8 255.255.255.0
> no ip directed-broadcast
> lane config-atm-address 47.00918100000000D0C08C9401.00D0C08C9023.00
> lane client-atm-address 47.00918100000000D0C08C9401.00B08E4BF820.02
> lane client ethernet ELAN2
> !
> r1#sh lane def
> interface ATM1/0/0:
> LANE Client: ...00B08E4BF820.**
> LANE Server: ...00B08E4BF821.**
> LANE Bus: ...00B08E4BF822.**
> LANE Config Server: ...00B08E4BF823.00
>
> R2
> interface ATM2/0/0
> no ip address
> no ip directed-broadcast
> no ip route-cache distributed
> no atm ilmi-keepalive
> lane config config-atm-address 47.00918100000000D0C08C9401.00D0C08C9023.00
> !
> interface ATM2/0/0.1 multipoint
> ip address 137.20.80.7 255.255.255.0
> no ip directed-broadcast
> lane config-atm-address 47.00918100000000D0C08C9401.00D0C08C9023.00
> lane client-atm-address 47.00918100000000D0C08C9401.00502AA29440.01
> lane client ethernet ELAN1
> !
> interface ATM2/0/0.2 multipoint
> ip address 137.20.90.7 255.255.255.0
> no ip directed-broadcast
> lane config-atm-address 47.00918100000000D0C08C9401.00D0C08C9023.00
> lane client-atm-address 47.00918100000000D0C08C9401.00502AA29440.02
> lane client ethernet ELAN2
>
> r2#sh lane def
> interface ATM2/0/0:
> LANE Client: ...00502AA29440.**
> LANE Server: ...00502AA29441.**
> LANE Bus: ...00502AA29442.**
> LANE Config Server: ...00502AA29443.00
>
>
> Cat5 LANE Module
> lane database CCIE
> name ELAN1 server-atm-address
47.00918100000000D0C08C9401.00D0C08C9021.01
> name ELAN2 server-atm-address
47.00918100000000D0C08C9401.00D0C08C9021.02
> !
> interface ATM0
> atm preferred phy A
> atm pvc 1 0 5 qsaal
> atm pvc 2 0 16 ilmi
> lane config config-atm-address 47.00918100000000D0C08C9401.00D0C08C9023.00
> lane config database CCIE
> !
> interface ATM0.1 multipoint
> lane config-atm-address 47.00918100000000D0C08C9401.00D0C08C9023.00
> lane client-atm-address 47.00918100000000D0C08C9401.00D0C08C9020.01
> lane server-atm-address 47.00918100000000D0C08C9401.00D0C08C9021.01
> lane bus-atm-address 47.00918100000000D0C08C9401.00D0C08C9022.01
> lane server-bus ethernet ELAN1
> lane client ethernet 1 ELAN1
> !
> interface ATM0.2 multipoint
> lane config-atm-address 47.00918100000000D0C08C9401.00D0C08C9023.00
> lane client-atm-address 47.00918100000000D0C08C9401.00D0C08C9020.02
> lane server-atm-address 47.00918100000000D0C08C9401.00D0C08C9021.02
> lane bus-atm-address 47.00918100000000D0C08C9401.00D0C08C9022.02
> lane server-bus ethernet ELAN2
> lane client ethernet 2 ELAN2
>
> ATM#sh lane def
> interface ATM0:
> LANE Client: 47.00918100000000D0C08C9401.00D0C08C9020.**
> LANE Server: 47.00918100000000D0C08C9401.00D0C08C9021.**
> LANE Bus: 47.00918100000000D0C08C9401.00D0C08C9022.**
> LANE Config Server: 47.00918100000000D0C08C9401.00D0C08C9023.00
>
>
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 08:23:55 GMT-3