Information Technology Reference
In-Depth Information
LANE Client Is Operational
After all these steps have been completed, the LEC is UP and Operational. We can see this using the
following command:
Cat5000_LANE>#
show lane client
LE Client ATM0.1 ELAN name: elan1 Admin: up State: operational
Client ID: 1 LEC up for 10 minutes 0 second
Join Attempt: 759
HW Address: 00e0.1e2e.e8b0 Type: ethernet Max Frame Size: 1516
VLANID: 100
ATM Address: 47.00918100000000603E899601.00E01E2EE8B0.01
VCD rxFrames txFrames Type ATM Address
0 0 0 configure 47.00918100000000603E899601.00E01E2EE8B3.00
889 1 2 direct 47.00918100000000603E899601.00E01E2EE8B1.01
890 4 0 distribute47.00918100000000603E899601.00E01E2EE8B1.01
893 0 317 send 47.00918100000000603E899601.00E01E2EE8B2.01
894 9 0 forward 47.00918100000000603E899601.00E01E2EE8B2.01
Understanding the show lane client Output
This command is by far the most important when it comes to LANE troubleshooting. On the TAC page,
the Output Interpreter will decode the output for you. We will describe the most important fields here.
Let's focus on the following output:
Gambrinus#
sh 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 476 0 distribute 47.009181000000006047508401.000000000002.01
258 0 56 send 47.009181000000006047508401.000000000003.01
259 2 0 forward 47.009181000000006047508401.000000000003.01
263 1 18 data 47.009181000000006047508401.006047508402.00
LE Client ATM2/0/0 ELAN name: default Admin: up State: operational
We can see that the client is administratively up and is operational. As we've seen earlier in this
chapter, this is the right state; it is up and running.
1.
Client ID: 2 LEC up for 15 minutes, 39 seconds
The only thing to keep in mind here is that the LEC is up for only 15 minutes. Is this normal? Did
a maintenance action happen 15 minutes ago?
2.
Join Attempt: 691
Although scary, this does not necessarily indicate that the LEC went down 691 times. The
LECS/LES was perhaps unreachable for a long amount of time.
3.
Last Fail Reason: Control Direct VC being released
This precious field indicates that the last reason for which the LEC could not reach the
“UP/Operational” state was because it could not reach the LES
4.
