|
|
This chapter provides troubleshooting information for connectivity and performance problems in LAN emulation (LANE) switching environments. The ATM Forum defined the LANE specification so that legacy LAN users can take advantage of the benefits of ATM without requiring modifications to end-station hardware or software. For an overview of LANE on an ATM switch router, see Chapter 13, "Configuring LAN Emulation," in the ATM Switch Router Software Configuration Guide.
Before you begin, make sure that all physical port connections are working correctly. See "Troubleshooting ATM Switch Router Interface Connections."
This chapter contains the following sections:
This section describes LANE troubleshooting using the example network in Figure 6-1 and in "Example Network."
A single emulated LAN consists of a 155 multimode fiber physical connection between the ATM switch router (EngFl1Ls1) and the Catalyst 5000 Fast Ethernet switch (EngFl1Cas1) in the engineering building. The ATM switch router is configured as the LAN emulation configuration server (LECS), the LAN Emulation server (LES), and the LAN emulation broadcast-and-unknown server (LANE BUS).
The LANE example network for the engineering building in Figure 6-1 is configured as follows:
 |
Note Emulated LAN entities coexist on one or more Cisco routers or switch routers. On Cisco routers or switch routers, each LANE server and broadcast-and-unknown server is always a single entity. Other LANE components include ATM switch routers---those that support the Interim Local Management Interface (ILMI) and signaling. Multiple emulated LANs can coexist on a single ATM network. |
This section describes how to use the Internet Control Message Protocol (ICMP) ping command to test for connectivity between the ATM switch router and either a router or an Ethernet switch.
To test for Ethernet connectivity, perform the following task:
| Command | Purpose |
|---|---|
Tests the configuration using the ping command. The ping command sends an echo request to the host, which is specified in the command line. |
Follow these steps to troubleshoot LANE connections:
EngFl1Ls1# ping 172.20.52.21 Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 172.20.52.100, timeout is 2 seconds: !!!!! Success rate is 100 percent (5/5), round-trip min/avg/max = 1/2/4 ms EngFl1Ls1# ping 172.20.52.20 Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 172.20.52.20, timeout is 2 seconds: !!!!! Success rate is 100 percent (5/5), round-trip min/avg/max = 1/2/4 ms EngFl1Ls1#
Step 2 Check the Success rate field. It should indicate 100 percent. This indicates that the ICMP packet was sent and returned.
If the success rate is less than 100 percent, continue with the following test to determine the problem with the LANE configuration. Refer to Chapter 13, "Configuring LAN Emulation," in the ATM Switch Router Software Configuration Guide.
Use the following commands to test the LANE connection status and performance:
| Command | Purpose |
|---|---|
Shows the LAN emulation default ATM address. | |
Shows the LAN emulation connection status. | |
Shows the LAN emulation client connection status. |
Follow these steps to confirm the LANE LECS, LES, and BUS configuration:
EngFl1Ls1# show lane default-atm-addresses interface ATM13/0/0: LANE Client: 47.00918100000000E04FACB401.00E04FACB402.** LANE Server: 47.00918100000000E04FACB401.00E04FACB403.** LANE Bus: 47.00918100000000E04FACB401.00E04FACB404.** LANE Config Server: 47.00918100000000E04FACB401.00E04FACB405.00 note: ** is the subinterface number byte in hex EngFl1Lsl#
Step 2 Use the show lane command to confirm the LAN emulation configuration of the ATM switch router.
EngFl1Lsl# show lane
LE Config Server ATM13/0/0 config table: eng_dbase
Admin: up State: operational
LECS Mastership State: active master
list of global LECS addresses (7 seconds to update):
47.00918100000000E04FACB401.00E04FACB405.00 <-------- me
ATM Address of this LECS: 47.00918100000000E04FACB401.00E04FACB405.00 (auto)
the above address has NOT yet been registered with ILMI
actual user specified form: ...
cumulative total number of unrecognized packets received so far: 0
cumulative total number of config requests received so far: 0
cumulative total number of config failures so far: 0
LE Server ATM13/0/0.1 ELAN name: eng_elan Admin: up State: operational
type: ethernet Max Frame Size: 1516
ATM address: 47.00918100000000E04FACB401.00E04FACB403.01
LECS used: 47.00918100000000E04FACB401.00E04FACB405.00 connected, vcd 84
LE BUS ATM13/0/0.1 ELAN name: eng_elan Admin: up State: operational
type: ethernet Max Frame Size: 1516
ATM address: 47.00918100000000E04FACB401.00E04FACB404.01
LE Client ATM13/0/0.1 ELAN name: eng_elan Admin: up State: initialState
Client ID: unassigned Next join attempt in 36 seconds
Join Attempt: 18
Last Fail Reason: Timeout on join request
HW Address: 00e0.4fac.b402 Type: ethernet Max Frame Size: 1516
ATM Address: 47.00918100000000E04FACB401.00E04FACB402.01
VCD rxFrames txFrames Type ATM Address
0 0 0 configure 47.00918100000000E04FACB401.00E04FACB405.00
0 0 0 direct 47.00918100000000E04FACB401.00E04FACB405.00
0 0 0 distribute 00.000000000000000000000000.000000000000.00
0 0 0 send 00.000000000000000000000000.000000000000.00
0 0 0 forward 00.000000000000000000000000.000000000000.00
EngFl1Lsl#
Step 3 Check the Admin (Administration) and State fields. They should be up and operational.
Step 4 Check the ATM address of this LECS field. This ATM address should match the ATM address in the LANE configuration server displayed in Step 1.
Step 5 Within the LE BUS section of the display, check the ELAN name field. It should match the name configured. To determine the ELAN name, use the show lane database command and check the default ELAN field.
Step 6 Check the ATM Address field. This ATM address should match the address displayed in Step 1 in the LANE Server field. The ATM address is appended with the corresponding subinterface number in hexadecimal.
If any of these fields do not match the actual LANE configuration, refer to Chapter 13, "Configuring LAN Emulation," in the ATM Switch Router Software Configuration Guide and correct the configuration.
Use the following command to test the LANE connection status and performance:
| Command | Purpose |
|---|---|
Shows the connection status of the LAN emulation client. |
Follow these steps to confirm the configuration of the LANE client:
EngFl1Ls1# show lane client LE Client ATM13/0/0.1 ELAN name: eng_elan Admin: up State: initialState Client ID: unassigned Next join attempt in 83 seconds Join Attempt: 11 Last Fail Reason: Timeout on join request HW Address: 00e0.4fac.b402 Type: ethernet Max Frame Size: 1516 ATM Address: 47.00918100000000E04FACB401.00E04FACB402.01 VCD rxFrames txFrames Type ATM Address 0 0 0 configure 47.00918100000000E04FACB401.00E04FACB405.00 87 1 2 direct 47.00918100000000E04FACB401.00E04FACB403.01 90 1 0 distribute 47.00918100000000E04FACB401.00E04FACB403.01 91 0 1 send 47.00918100000000E04FACB401.00E04FACB404.01 94 0 0 forward 47.00918100000000E04FACB401.00E04FACB404.01 EngFl1Ls1#
|
Note This same information appears in the previously described show lane command. |
Step 2 Check the ELAN name field. This should match the ELAN name configured.
Step 3 Check the Admin and State fields. They should read up and operational, respectively.
Step 4 Check the Join Attempt field.
Step 5 Check the ATM Address column in the virtual channel circuit (VCC) configuration table. These ATM addresses should be propagated as follows:
---configure, should be the same as the LECS ATM address
---direct and distribute, should be the same as the LES ATM address
---send and forward, should be the same as the LANE BUS ATM address
Step 6 Check that the rxFrames and txFrames columns contain values greater than 0.
The LANE configuration server assigns individual clients to particular emulated LANs by directing them to the LANE server that corresponds to the emulated LAN. The LANE configuration server maintains a database of LANE client ATM or Media Access Control (MAC) addresses and their emulated LANs.
|
Note A LANE configuration server can serve multiple emulated LANs. |
Use the following command in privileged EXEC mode to display the configuration of the LANE client database binding:
| Command | Purpose |
show lane database | Displays the LANE client database binding. |
Follow these steps to confirm the configuration of the LANE database:
EngFl1Ls1# show lane database LANE Config Server database table 'eng_dbase' bound to interface/s: ATM13/0/0 default elan: eng_elan elan 'eng_elan': un-restricted server 47.00918100000000E04FACB401.00E04FACB403.01 (prio 0) EngFl1Ls1#
Step 2 Check the LANE Config Server database table field. It indicates the binding of the LANE client to the LANE database.
Step 3 Check the server field. The ATM address displayed should correspond to the ATM address shown in using the show lane default-atm-addresses command in Step 1 of the previous section, "Checking Basic LANE Configuration."
If the LANE client configuration server database is set up incorrectly, refer to Chapter 13, "Configuring LAN Emulation," in the ATM Switch Router Software Configuration Guide.
This section outlines the debug commands used to troubleshoot the LANE setup and signaling.
Use the following debug commands to check the LANE configuration and setup processes:
| Command | Purpose |
|---|---|
debug lane client {all | le-arp | packet | signalling | state | topology} | Debugs all LANE client setup processes. |
debug lane client signalling interface atm card/subcard/port | Debugs LANE client signaling processes for a specific ATM interface. |
debug lane config {all | events | packets} | Debugs all LANE setup processes. |
Debugs all LANE LECS setup processes. | |
debug lane server interface atm card/subcard/port | Debugs LANE server processes for a specific ATM interface. |
debug lane signalling interface atm card/subcard/port | Debugs LANE signaling processes for a specific ATM interface. |
Turns off all debugging. |
|
Note Other helpful debug commands include the debug atm ilmi command and all the variations of the debug atm sig command. |
Posted: Mon May 8 19:06:42 PDT 2000
Copyright 1989 - 2000©Cisco Systems Inc.