9-2 SmartSwitch ATM User Guide
Troubleshooting LAN Emulation Troubleshooting
5. If working through these questions does not solve the problem, contact Cabletron Systems Customer
Service. (see Appendix B, "Technical Support").
9.2 TROUBLESHOOTING LAN EMULATION
You have configured an Emulated LAN and your network applicati ons are not working . Use t hese ques tions an d tests
to help determine the cause of the problem.
1. Check for connectivity. Try pinging between end nodes. Ping from the ATM SmartSwitch (using
ping) to its end nodes. If you cannot ping, check physical connectivity (disconnected cable and so
on).
2. Execute the show lecs command on the switch that contains the LECS. If the LECS is down, start
it by executing the start lecs command.
-If running distributed LANE services (LECS on one switch and LES and BUS on another
switch) execute the show les command on the switch running the LES and BUS. If the LES
and BUS are down, start the LES and BUS by executing the start les command.
3. Check IP routes and addresses.
Use show route command to check the ATM SmartSwitch route table.
-Are the destination addresses correct for the specified gateways?
-Are there any routing loops?
-Are one or more of the destination addresses mapped to the wr on g subnet?
Use show client to check the ATM SmartSwitch local ELAN client.
-Does the client have the correct IP address?
-Is the subnet correct?
-Is the ATM address correct?
-Is the server type correct?
Check end nodes configurations.
-Are end nodes configured correctly?
4. If the ELAN spans multiple switches, check the following:
-Is the LECS address correct on all switches?
-Can all switches reach the switch providing LECS support?
-If using the Well Known LECS Address, are all switches correctly mapped?
5. Check the LECS database.
Use show lecselan to check the names and numbers of ELANs.
-Are ELAN names correct?
-Is the ATM address of the LES correct?
6. Check whether LES is connected.
Use show lesclient to check whether devices are registered with the LES. If clients are registered,
check end node configuration. If not registered, check multi-point signaling.
Use set leselan to turn off multi-point signaling on a per-ELAN basis.