2005.08.09 19:02:40 ADSL.EVENTS Current DSL state:
2005.08.09 19:02:40 INTERFACE_STATUS.adsl 2/1 changed state to down
2005.08.09 19:02:54 ADSL.EVENTS Current DSL state:
2005.08.09 19:02:54 ADSL.EVENTS Current DSL state:
2005.08.09 19:02:55 ADSL.EVENTS Current DSL state:
2005.08.09 19:02:57 ADSL.EVENTS Current DSL state:
2005.08.09 19:03:01 ADSL.EVENTS Current DSL state:
2005.08.09 19:03:01 ADSL.EVENTS Current DSL state:
2005.08.09 19:03:01 ADSL.EVENTS Current DSL state:
2005.08.09 19:03:02 ADSL.EVENTS Current DSL state:
2005.08.09 19:03:02 INTERFACE_STATUS.adsl 2/1 changed state to up
N o t e
Figure 7-22 shows the debug commands for a connection that was established
successfully.
Figure 7-22. Debug Output When a Connection Was Established Successfully
You can use the debug information to pinpoint when and why the line goes
down.
Debug commands are bandwidth intensive.
To turn off debugging, enter:
Syntax: no debug interface adsl events
Troubleshooting the ATM Interface
If the physical interface is up but the line protocol is down, you will need to
troubleshoot the logical interface. Use the show interfaces atm command
to examine the status and configuration of the ATM interface. From the enable
mode context, enter:
Syntax: show interfaces atm <number>
ADSL WAN Connections
Troubleshooting the ADSL Connection
ATU_RIDLE
GDMT_NEGO
Negotiating to use the
GDMT_ACKX
G.DMT training mode
ATU_RECT
ATU_RSEGUE1
ATU_RMSGS1
ATU_RRATES2
ATU_RREVERB5
ATU_RSHOWTIME
Connection is
established
7-49