From: Chuah Eng Wee (chuahew@xxxxxxxxxxxxxxx)
Date: Sun Aug 01 1999 - 06:01:04 GMT-3
Hi Derek,
THe most common problem I encountered during work is that
the LEC is not up.
A few possible problems :
- LEC cannot find LECS. So check to make sure that the LECS address is
correct.
Make sure u have the two commands in your LECS major interface,
lane config auto-config-atm-address
lane config database DATABASE_NAME
assuming u use cisco automatic addressing
- LEC cannot find LES. Have u configured the appropriate LES/BUS in the
correct sub-interface ?? Is the LES/BUS ATM address in your LECS database
?? The proctor might change the LES address in the LECS database, then your
LEC will not be up.
- for SUP I, the ESI portion of the ATM address is tied to the sup engine,
so if u change the sup engine, and u have a LES/BUS defined there, then
your ATM address will change as well. If this is not updated into the LECS
database, then your LEC won't be able to join as well.
- Are the necessary pvcs setup ?? The proctor might remove those necessary
pvcs so u don't get desired address when u do a show lane default. So
remember thos pvcs. Can't remember off hand, I think is
1 0 5 for qsaal
1 0 16 for ilmi
- if we are asked to configure SSRP, they might change the sequence of the
LES address in the LECS database so that our config doesn't work as
expected. The same for redundant LECS as well.
HTH
Eng Wee
At 08:38 PM 7/31/99 +0100, Derek Fage wrote:
>Hi there,
>
>I think I'm just about OK with ATM LANE on routers and Cat 5K ATM blades.
>What I was wondering was what sort of problems I should look out for if I
>find it in the lab.
>
>When troubleshooting ATM (other than physical cable connections), what steps
>should I go through ?
>
>Derek...
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 08:21:45 GMT-3