Information Technology Reference
In-Depth Information
Table21-1
Troubleshooting LECs Not Coming Up (continued)
Possible Problem
Solution
The LES refuses
the connection
(receiving
negative join
response)
If the ELAN to which you are trying to connect is restricted,
and if you connect to the LES directly bypassing the LECS,
this could be a security issue. Check the LANE database
configuration on the LECS to be sure that it includes the
ATM address of the client attempting to connect.
1.
If you configured on the same subinterface a LEC and a LES,
and you also specified the ATM address for the LES with the
command
lane server-atm-address
, the LEC might be
trying to contact a backup LES (which refuses the
connection). The reason is that the LEC is also using the
lane server-atm-address
command to decide which LES to
contact. It then unconditionally contacts the local LES that
may currently be the backup. The easy way of fixing this is
to configure the LES on a different subinterface.
2.
continues
If none of this
works
A simple configuration problem can, in fact, hide a much deeper
issue with the network itself. Enable
debug lane client all
on
your machine, and go to the section “ LANE Client Connection
Example, with debug lane client all Enabled “ to compare to the
output of a successful connection.” Exercise caution when using
debug lane client all
. Because debugging output is assigned
high priority in the CPU process, it can render the system
unusable. It is best to use
debug
commands during periods of
lower network traffic and fewer users. You should avoid sending
verbose debugging output to the console (use the
logging
console info
command). Instead, send the
debug
output to the
logging buffer using the command
logging buffer <buffer-size>
debug
.
