Understanding the show lane client Command Output     Printable Pdf
Document ID: 10502

The show lane client command is the most important command for LANE troubleshooting. This document contains descriptions of that command's most important output fields.


Briefly, the command reference describes the command as follows:


"To display detailed LANE information for all the LANE clients configured on an interface or any of its subinterfaces, on a specified subinterface, or on an emulated LAN."


This description, though correct, hides the importance of this command. See the following output and the line-by-line analysis to follow:



Gambrinus#show lane client
LE Client ATM2/0/0   ELAN name: default  Admin: up   State: operational
Client ID: 2 LEC up for 15 minutes 39 seconds
ELAN ID: 1
Join Attempt: 691
Last Fail Reason: Control Direct VC being released

HW Address: 0060.4750.8402   Type: ethernet   Max Frame Size: 1516
ATM Address: 47.009181000000006047508401.006047508402.00



VCD rxFrames txFrames Type ATM Address
0 0 0 configure 47.009181000000006047508401.006047508405.00
256 1 10 direct 47.009181000000006047508401.000000000002.01
257 276 0 distribute 47.009181000000006047508401.000000000002.01
258 0 56 send 47.009181000000006047508401.000000000003.01
259 0 2 forward 47.009181000000006047508401.000000000003.01
263 1 18 data 47.009181000000006047508401.006047508402.00
262 18 1 data 47.009181000000006047508401.006047508402.00


  1. LE Client ATM2/0/0   ELAN name: default   Admin: up   State: operational
    We can see that the client is "up, operational". This is the correct state.

  2. Client ID: 2     LEC up for 15 minutes 39 seconds
    The only thing to keep in mind here is that the LAN Emulation Client (LEC) is up for only 15 minutes. Is this normal? Was there a maintenance 15 minutes ago?

  3. Join Attempt: 691
    Although high, this should not be a cause for concern. It does not necessarily indicate that the LEC went down 691 times. Perhaps the LECs were unreachable for a long period of time.

  4. Last Fail Reason:  Control Direct VC being released
    This important field indicates that the last reason the LEC could not reach the "up, operational" state was because it could not reach the LAN Emulation Server (LES).

  5. ATM Address: 47.009181000000006047508401.006047508402.0
    This is only interesting when we check the show lane client output of other LECs, which can be located at the remote side of a data direct.

  6. 0  0  0  configure  47.009181000000006047508401.006047508405.00
    This line gives detail on the connection to the LECs and this Virtual Channel Connection (VCC) is called the configure direct, as the Type field suggests. The VCC is 0, since the connection is torn down according to the specification.

  7. 256  1  10 direct  47.009181000000006047508401.000000000002.01
    This line gives detail on the connection to the LES and this VCC is called the control direct, as suggested by the Type field.

  8. 257  476  0 distribute  47.009181000000006047508401.000000000002.01
    This line gives detail on the connection from the LES to all LECs. It is called the control distribute. We can see that the LES address is identical for the control direct and control distribute, as it should be.

  9. 258  0  56 send  47.009181000000006047508401.000000000003.01
    This line gives detail on the connection to the Broadcast and Unknown Server (BUS). It is called multicast send, as the Type field suggests.

  10. 259  2  0 forward  47.009181000000006047508401.000000000003.01
    This line gives detail on the connection from the BUS to all LECs. It is called multicast forward. We can see that the BUS address is the same for the multicast send and multicast forward.

  11. 263  1  18 data  47.009181000000006047508401.006047508402.00
    The remaining lines give details on each data direct VCC. The ATM address corresponds to the remote LEC.


Related Information

  • ATM Technology Support Pages

Cisco Systems TAC Certified

Learn more about Cisco TAC Certification...

All contents are Copyright © 1992-2004 Cisco Systems, Inc. All rights reserved. Important Notices and Privacy Statement.

Google