Troubleshooting

6.1 Locating Troubleshooting Procedures

6.2 Hardware Troubleshooting

6.2.1 Multiplexer Chassis Modules Do Not Work Properly

6.2.2 Line Concentration Chassis Modules Do Not Work Properly

6.2.3 Cisco DSL Components Unable to Train

6.2.4 Cannot Pass Traffic

6.3 Software

Troubleshooting

This chapter explains troubleshooting procedures for hardware and software conditions of the Cisco 6100 Series system. The following information is presented in tables for each of the troubleshooting procedures documented:

Symptom---A description of a problem or condition.
Probable cause---A short discussion of the probable cause of a problem or condition.
Action---A step-by-step procedure for diagnosing and solving a specific problem or condition.

Note If none of the actions presented are successful, please contact the Cisco Technical Assistance Center (TAC) for additional support.

6.1 Locating Troubleshooting Procedures

Table 6-1 shows symptom, probable causes, and refers to the sections in this chapter to help you quickly locate a troubleshooting procedure.

Table 6-1: Locating Troubleshooting Procedures
Symptom Probable Cause Reference Section

Modules Not Working Properly

Incorrect configuration of xTU-C modules

Cabling problem

Incorrect software images loaded

Hardware and software are incompatible

6.2.1.

CPE¹ Unable to Train

Power problem

Improper cabling/port

VPI²/VCI³ settings on the CPE do not match the settings on the line card subscriber side

Provisioning incorrect for subscriber settings

Subscriber and port are not unlocked

6.2.3.

System has trouble Connecting to the Router

Improper cabling

Incorrect software configuration (VPI/VCI settings mismatch)

Incorrect router configuration

6.2.3.

End to end traffic failure

Module failure

Incorrect "interface type" on the NI⁴ module

Payload Scrambling disabled

Queue priority setting incorrect

6.2.4.

¹CPE = customer premises equipment
²VPI = virtual path identifier
³VCI = virtual circuit identifier
⁴NI = network interface

Table 6-1: **Locating Troubleshooting Procedures**
Symptom	Probable Cause	Reference Section
Modules Not Working Properly	Incorrect configuration of xTU-C modules Cabling problem Incorrect software images loaded Hardware and software are incompatible	6.2.1.
CPE¹ Unable to Train	Power problem Improper cabling/port VPI²/VCI³ settings on the CPE do not match the settings on the line card subscriber side Provisioning incorrect for subscriber settings Subscriber and port are not unlocked	6.2.3.
System has trouble Connecting to the Router	Improper cabling Incorrect software configuration (VPI/VCI settings mismatch) Incorrect router configuration	6.2.3.
End to end traffic failure	Module failure Incorrect "interface type" on the NI⁴ module Payload Scrambling disabled Queue priority setting incorrect	6.2.4.

6.2 Hardware Troubleshooting

The following sections describe the procedures for hardware troubleshooting:

6.2.1 Multiplexer Chassis Modules Do Not Work Properly

This section provides tables for troubleshooting the following multiplexer chassis (MC) modules:

System controller (SC) module---Table 6-2
NI module---Table 6-3
CAP ATU-C, DMT-2 ATU-C, or STU-C (xTU-C) modules---Table 6-4

Table 6-2 provides troubleshooting procedures for the SC module.

Table 6-2: SC Module Fault Indications
Symptom Probable Cause Action

The SC module status and active LEDs are not solid green or Status and Active LEDs are off after the self-test.

The module might be in an incorrect slot

Module might not be properly seated

Step 1 Ensure that the SC module is installed in the proper slot. Slot 12 in the MC is the only valid slot for the SC module.

Step 2 Remove the SC module from the slot by lifting up the ejector tab and carefully sliding the module out of the MC.
Note The removal and reinsertion of an SC module resets the SC module, which resets the entire MC. Any configuration data stored in NVRAM¹ is not affected, but the active connections become disconnected. The active connections are restored once the SC is in service.
Step 3 Reinsert the SC module, making sure the top and bottom of the module are squarely seated in the proper slot.

The module begins executing a self-test. The LEDs cycle for 3 to 5 seconds. On completion of the self-test, the status and active LEDs are green, and the alarm LED is off.

If the LEDs do not respond when you reinsert SC module, ensure that the MC is properly powered. Refer to the Cisco 6100 Series Direct Connect Installation Guide (for a Direct Connect configuration) or the Cisco 6100 Set Up and Installation Manual (for a Digital Off-Hook [DOH] configuration) for powering instructions.

Step 4 If the LEDs do not respond as indicated in Step 3 when you reinsert the SC module, remove the SC module and follow Steps 1 through 3 with the spare SC module.

Step 5 If the spare SC module executes properly, return the initial SC module to Cisco for repair. Contact TAC for the nearest Cisco service center.

The MC might not be properly powered

Refer to the Cisco 6100 Series Direct Connect Installation Guide (for a Direct Connect configuration) or the Cisco 6100 Set Up and Installation Manual (for a DOH configuration) for powering instructions.

The software does not load

Incorrect software image resides on the SC module for the type of module inserted in the MC.

The software download feature of the system can not update any module that:

Has an older Release 1.x top-level part number

Has Release 1.x "boot code", which has not been upgraded to 2.x

Also, a module with an incorrect part number can not receive downloads (upgrades) from an SC module.

If the status light on a module flashes at an approximate 1-second on, 1-second off rate for longer than 3 to 4 minutes, the problem could be an incorrect part number or a spare module that has not yet been upgraded to 2.x boot code.

A module receiving normal download from the SC module will have a Status LED flash rate slightly faster than one-half second on, one-half second off for approximately 3 to 4 minutes.

Refer to the ViewRunner for Windows Provisioning and Operation Guide or the ViewRunner for HP OpenView Provisioning and Operation Guide for software download procedures.

A preconfigured SC module is not assigned an IP address

Step 1 Refer to the Connection Test Procedures in the Cisco 6100 Series Direct Connect Installation Guide for instructions on configuring the node and server IP addresses.

Step 2 To specify the location and name of the boot image file, enter 999.

Step 3 Enter the password ADSL SPEED.

Step 4 The Option menu appears.

Step 5 Set TFTP Path and File to Load as follows:

At the Enter Selection prompt, enter: 9
At the Enter new bootfile prompt, enter:

C:\pscxxxxxx.ima\

Enter new Bootpath

C:\directoryname\

(When you specify the path, you must include the backslash.)

Step 6 Press Enter.

Step 7 Enter 7 to save.

Step 8 Entered data is not saved until the save option is executed. All changes are lost if Exit is executed before the save option.

Step 9 Enter 0 to exit.

Step 10 Make sure ViewRunner is running and the bootfile is at:

C:\directoryname\pscxxxxxx.ima

Step 11 At the Hardware reset? prompt, enter No. The following appears:

Transferring Data to run prior to placing in Flash Starting the TFTP download of C:\ascxxxxxx.ima DIR asc*

Step 12 The SC module might take up to 5 minutes to come up if a download is required.

A BOOTP or DHCP server is responding to the SC module BOOTP requests with incorrect information during initialization.

For details on the interaction between the SC module and BOOTP, refer to the system initialization chapter in the ViewRunner for Windows Installation and Administration Guide or the ViewRunner for HP OpenView Installation and Administration Guide for more information.

Step 1 If BOOTP is desired, make sure the IP address and boot image information is correctly configured on the BOOTP.

Step 2 If the IP address and boot image information are not configured correctly, make sure the BOOTP or DHCP server does not reply to SC module BOOTP requests by excluding the ethernet hardware (MAC) address of the SC module is excluded from such server.

Step 3 Once the SC module is confused by a BOOTP or DHCP server, it will behave exactly like the situation where "A preconfigured SC module does not have an IP address". See the previous "Probable Cause" for actions to take to resolve the problem.

¹NVRAM = Non-Volatile Random Access memory

**Table 6-2: SC Module Fault Indications**
Symptom	Probable Cause	Action
The SC module status and active LEDs are not solid green or Status and Active LEDs are off after the self-test.	The module might be in an incorrect slot Module might not be properly seated	Step 1 Ensure that the SC module is installed in the proper slot. Slot 12 in the MC is the only valid slot for the SC module. Step 2 Remove the SC module from the slot by lifting up the ejector tab and carefully sliding the module out of the MC. Note The removal and reinsertion of an SC module resets the SC module, which resets the entire MC. Any configuration data stored in NVRAM¹ is not affected, but the active connections become disconnected. The active connections are restored once the SC is in service. Step 3 Reinsert the SC module, making sure the top and bottom of the module are squarely seated in the proper slot. The module begins executing a self-test. The LEDs cycle for 3 to 5 seconds. On completion of the self-test, the status and active LEDs are green, and the alarm LED is off. If the LEDs do not respond when you reinsert SC module, ensure that the MC is properly powered. Refer to the Cisco 6100 Series Direct Connect Installation Guide (for a Direct Connect configuration) or the Cisco 6100 Set Up and Installation Manual (for a Digital Off-Hook [DOH] configuration) for powering instructions. Step 4 If the LEDs do not respond as indicated in Step 3 when you reinsert the SC module, remove the SC module and follow Steps 1 through 3 with the spare SC module. Step 5 If the spare SC module executes properly, return the initial SC module to Cisco for repair. Contact TAC for the nearest Cisco service center.
The MC might not be properly powered	Refer to the Cisco 6100 Series Direct Connect Installation Guide (for a Direct Connect configuration) or the Cisco 6100 Set Up and Installation Manual (for a DOH configuration) for powering instructions.
The software does not load Incorrect software image resides on the SC module for the type of module inserted in the MC.	The software download feature of the system can not update any module that: Has an older Release 1.x top-level part number Has Release 1.x "boot code", which has not been upgraded to 2.x Also, a module with an incorrect part number can not receive downloads (upgrades) from an SC module. If the status light on a module flashes at an approximate 1-second on, 1-second off rate for longer than 3 to 4 minutes, the problem could be an incorrect part number or a spare module that has not yet been upgraded to 2.x boot code. A module receiving normal download from the SC module will have a Status LED flash rate slightly faster than one-half second on, one-half second off for approximately 3 to 4 minutes. Refer to the ViewRunner for Windows Provisioning and Operation Guide or the ViewRunner for HP OpenView Provisioning and Operation Guide for software download procedures.
	A preconfigured SC module is not assigned an IP address	Step 1 Refer to the Connection Test Procedures in the Cisco 6100 Series Direct Connect Installation Guide for instructions on configuring the node and server IP addresses. Step 2 To specify the location and name of the boot image file, enter 999. Step 3 Enter the password ADSL SPEED. Step 4 The Option menu appears. Step 5 Set TFTP Path and File to Load as follows: At the Enter Selection prompt, enter: 9 At the Enter new bootfile prompt, enter: C:\pscxxxxxx.ima\ Enter new Bootpath C:\directoryname\ (When you specify the path, you must include the backslash.) Step 6 Press Enter. Step 7 Enter 7 to save. Step 8 Entered data is not saved until the save option is executed. All changes are lost if Exit is executed before the save option. Step 9 Enter 0 to exit. Step 10 Make sure ViewRunner is running and the bootfile is at: C:\directoryname\pscxxxxxx.ima Step 11 At the Hardware reset? prompt, enter No. The following appears: `Transferring Data to run prior to placing in Flash Starting the TFTP download of C:\ascxxxxxx.ima` DIR asc* Step 12 The SC module might take up to 5 minutes to come up if a download is required.
A BOOTP or DHCP server is responding to the SC module BOOTP requests with incorrect information during initialization.	For details on the interaction between the SC module and BOOTP, refer to the system initialization chapter in the ViewRunner for Windows Installation and Administration Guide or the ViewRunner for HP OpenView Installation and Administration Guide for more information. Step 1 If BOOTP is desired, make sure the IP address and boot image information is correctly configured on the BOOTP. Step 2 If the IP address and boot image information are not configured correctly, make sure the BOOTP or DHCP server does not reply to SC module BOOTP requests by excluding the ethernet hardware (MAC) address of the SC module is excluded from such server. Step 3 Once the SC module is confused by a BOOTP or DHCP server, it will behave exactly like the situation where "A preconfigured SC module does not have an IP address". See the previous "Probable Cause" for actions to take to resolve the problem.

Table 6-3 provides troubleshooting procedures for the NI module.

Table 6-3: NI Module Fault Indications
Symptom Probable Cause Action

The NI module status and active LEDs are not solid green or Status and Active LEDs are off after the self-test

Status red and Active off.

The module might be in an incorrect slot

Module might not be properly seated

Step 1 Ensure that the NI module is installed in the proper slot. Slot 10 in the MC is the only valid slot for the NI module. When NI redundancy is supported, slots 10 and 11 will be valid slots.

Step 2 If connected, disconnect the transmit and receive transmission cables (optical or electrical, depending on the NI type).

Step 3 Remove the NI module from the slot by lifting up the ejector tab(s) and carefully sliding the module out of the MC.
Note The removal and reinsertion of an NI module will cause LOS¹ alarms at both the MC and the ATM switch to which the transmission lines are connected. Active ADSL connections might or might not be lost, depending on the status of the CPE session and idle timeouts. If the timeouts are not invoked, the ADSL connection is not lost. However, if ADSL connections are not lost, all connected subscribers still lose ATM connectivity to the ATM bearer service and IP connectivity to far end routers during the disconnect period.
Step 4 Reinsert the NI module, making sure the top and bottom of the module are squarely seated in the proper slot.

The module begins executing a self-test. The LEDs cycle for 45 seconds. On completion of the self-test, the status and active LEDs are green, and the alarm LED is off.

If the LEDs do not respond when you insert the NI module is inserted, ensure that the MC is properly powered. Refer to the Cisco 6100 Series Direct Connect Installation Guide (for a Direct Connect configuration) or the Cisco 6100 Set Up and Installation Manual (for a Digital Off-Hook [DOH] configuration) for powering instructions.

Step 5 Ensure that a working SC module is inserted in the MC and that it is configured with the correct NI module software image.

As part of the NI module startup, the NI module communicates with the SC module to obtain its software and configuration information. If the SC module is not available, the NI module waits in the initializing state.

Step 6 If the LEDs do not respond as indicated in Step 4 when you reinsert the NI module, remove the NI module and repeat Steps 1 through 5 with the spare NI module.

Step 7 If the spare NI module executes properly, return the initial NI module to Cisco for repair. Contact TAC for the nearest Cisco service center.

The MC might not be properly powered

Refer to the Cisco 6100 Series Direct Connect Installation Guide (for a Direct Connect configuration) or the Cisco 6100 Set Up and Installation Manual (for a DOH configuration) for powering instructions.

The software does not load

Incorrect software image resides on the SC module for the type of module inserted in the MC.

The software download feature of the system cannot update any module that:

Has an earlier Release 1.x top-level part number

Has Release 1.x "boot code", which was not been upgraded to 2.x boot code

Also, a module with an incorrect part number cannot receive downloads (upgrades) from an SC module.

If the status light on a module flashes at an approximate 1-second on, 1-second off rate for longer than 3 to 4 minutes, the problem could be an incorrect part number or a spare module that was not yet been upgraded to 2.x boot code.

A module that receives normal download from the SC module will have a Status LED flash rate slightly faster than one-half second on, one-half second off for approximately 3 to 4 minutes.

A preconfigured SC module is not assigned an IP address

Step 1 Refer to the Connection Test Procedures in the Cisco 6100 Series Direct Connect Installation Guide for instructions on configuring the node and server IP addresses.

Step 2 To specify the location and name of the boot image file, enter 999

Step 3 Enter the password ADSL SPEED.

Step 4 The Option menu appears.

Step 5 Set TFTP Path and File to Load as follows:

At the Enter Selection prompt, enter: 9
At the Enter new bootfile prompt, enter:

C:\pscxxxxxx.ima\

Enter new Bootpath

C:\directoryname\

(When you specify the path, you must include the backslash.)

Step 6 Press Enter.

Step 7 Enter 7 to save.

Step 8 Entered data is not saved until the save option is executed. All changes are lost if Exit is executed before the save option.

Step 9 Enter 0 to exit.

Step 10 Make sure ViewRunner is running and the bootfile is at:

C:\directoryname\pscxxxxxx.ima

Step 11 At the Hardware reset? prompt, enter No. The following appears:

Transferring Data to run prior to placing in Flash Starting the TFTP download of C:\ascxxxxxx.ima DIR asc*

Step 12 The SC module might take up to 5 minutes to come up if a download is required.

¹LOS = loss of signal

**Table 6-3: NI Module Fault Indications**
Symptom	Probable Cause	Action
The NI module status and active LEDs are not solid green or Status and Active LEDs are off after the self-test Status red and Active off.	The module might be in an incorrect slot Module might not be properly seated	Step 1 Ensure that the NI module is installed in the proper slot. Slot 10 in the MC is the only valid slot for the NI module. When NI redundancy is supported, slots 10 and 11 will be valid slots. Step 2 If connected, disconnect the transmit and receive transmission cables (optical or electrical, depending on the NI type). Step 3 Remove the NI module from the slot by lifting up the ejector tab(s) and carefully sliding the module out of the MC. Note The removal and reinsertion of an NI module will cause LOS¹ alarms at both the MC and the ATM switch to which the transmission lines are connected. Active ADSL connections might or might not be lost, depending on the status of the CPE session and idle timeouts. If the timeouts are not invoked, the ADSL connection is not lost. However, if ADSL connections are not lost, all connected subscribers still lose ATM connectivity to the ATM bearer service and IP connectivity to far end routers during the disconnect period. Step 4 Reinsert the NI module, making sure the top and bottom of the module are squarely seated in the proper slot. The module begins executing a self-test. The LEDs cycle for 45 seconds. On completion of the self-test, the status and active LEDs are green, and the alarm LED is off. If the LEDs do not respond when you insert the NI module is inserted, ensure that the MC is properly powered. Refer to the Cisco 6100 Series Direct Connect Installation Guide (for a Direct Connect configuration) or the Cisco 6100 Set Up and Installation Manual (for a Digital Off-Hook [DOH] configuration) for powering instructions. Step 5 Ensure that a working SC module is inserted in the MC and that it is configured with the correct NI module software image. As part of the NI module startup, the NI module communicates with the SC module to obtain its software and configuration information. If the SC module is not available, the NI module waits in the initializing state. Step 6 If the LEDs do not respond as indicated in Step 4 when you reinsert the NI module, remove the NI module and repeat Steps 1 through 5 with the spare NI module. Step 7 If the spare NI module executes properly, return the initial NI module to Cisco for repair. Contact TAC for the nearest Cisco service center.
The MC might not be properly powered	Refer to the Cisco 6100 Series Direct Connect Installation Guide (for a Direct Connect configuration) or the Cisco 6100 Set Up and Installation Manual (for a DOH configuration) for powering instructions.
	The software does not load Incorrect software image resides on the SC module for the type of module inserted in the MC.	The software download feature of the system cannot update any module that: Has an earlier Release 1.x top-level part number Has Release 1.x "boot code", which was not been upgraded to 2.x boot code Also, a module with an incorrect part number cannot receive downloads (upgrades) from an SC module. If the status light on a module flashes at an approximate 1-second on, 1-second off rate for longer than 3 to 4 minutes, the problem could be an incorrect part number or a spare module that was not yet been upgraded to 2.x boot code. A module that receives normal download from the SC module will have a Status LED flash rate slightly faster than one-half second on, one-half second off for approximately 3 to 4 minutes.
A preconfigured SC module is not assigned an IP address	Step 1 Refer to the Connection Test Procedures in the Cisco 6100 Series Direct Connect Installation Guide for instructions on configuring the node and server IP addresses. Step 2 To specify the location and name of the boot image file, enter 999 Step 3 Enter the password ADSL SPEED. Step 4 The Option menu appears. Step 5 Set TFTP Path and File to Load as follows: At the Enter Selection prompt, enter: 9 At the Enter new bootfile prompt, enter: C:\pscxxxxxx.ima\ Enter new Bootpath C:\directoryname\ (When you specify the path, you must include the backslash.) Step 6 Press Enter. Step 7 Enter 7 to save. Step 8 Entered data is not saved until the save option is executed. All changes are lost if Exit is executed before the save option. Step 9 Enter 0 to exit. Step 10 Make sure ViewRunner is running and the bootfile is at: C:\directoryname\pscxxxxxx.ima Step 11 At the Hardware reset? prompt, enter No. The following appears: `Transferring Data to run prior to placing in Flash Starting the TFTP download of C:\ascxxxxxx.ima` DIR asc* Step 12 The SC module might take up to 5 minutes to come up if a download is required.

Table 6-4 provides troubleshooting procedures for the xTU-C modules.

Table 6-4: xTU-C Module(s) Fault Indications
Symptom Probable Cause Action

The xTU-C module(s) status and active LEDs are not solid green or Status and Active LEDs are off after the self-test status red active off.

The module might be in an incorrect slot

Module might not be properly seated

Step 1 Ensure that the xTU-C module is installed in the proper slot. Slots 1 to 8, 13 to 28, and 31 to 38 in the MC are the only valid slots for the xTU-C module(s)

Step 2 Remove the module from the slot by lifting up the ejector tab and carefully sliding the module out of the MC.
Note The removal of an xTU-C module can affect up to four subscriber connections, depending on dual-port or quad-port configuration. Assuming that there are idle modems in the same logical pool, the removal of an xTU-C module with active connections causes the CPE to retrain the ADSL connections to available xTU-C modules.
Step 3 Reinsert the xTU-C module, making sure the top and bottom of the module are squarely seated in the proper slot.

The module begins executing a self-test. The LEDs cycle for 3 to 5 seconds. On completion of the self-test, the status and active LEDs are green, and the alarm LED is off.

If the LEDs do not respond when you insert the xTU-C module is inserted, ensure that the MC is properly powered. Refer to the Cisco 6100 Series Direct Connect Installation Guide (for a Direct Connect configuration) or the Cisco 6100 Set Up and Installation Manual (for a Digital Off-Hook [DOH] configuration) for powering instructions.

Step 4 Ensure that a working SC module is inserted in the MC and that it is configured with the correct software image.

Step 5 If the LEDs do not respond as indicated in Step 3 when you reinsert the xTU-C module, remove the module and repeat Steps 1 through 4 with the spare xTU-C module.

Step 6 If the spare xTU-C module executes properly, return the initial module to Cisco for repair. Contact TAC for the nearest Cisco service center.

**Table 6-4: xTU-C Module(s) Fault Indications**
Symptom	Probable Cause	Action
The xTU-C module(s) status and active LEDs are not solid green or Status and Active LEDs are off after the self-test status red active off.	The module might be in an incorrect slot Module might not be properly seated	Step 1 Ensure that the xTU-C module is installed in the proper slot. Slots 1 to 8, 13 to 28, and 31 to 38 in the MC are the only valid slots for the xTU-C module(s) Step 2 Remove the module from the slot by lifting up the ejector tab and carefully sliding the module out of the MC. Note The removal of an xTU-C module can affect up to four subscriber connections, depending on dual-port or quad-port configuration. Assuming that there are idle modems in the same logical pool, the removal of an xTU-C module with active connections causes the CPE to retrain the ADSL connections to available xTU-C modules. Step 3 Reinsert the xTU-C module, making sure the top and bottom of the module are squarely seated in the proper slot. The module begins executing a self-test. The LEDs cycle for 3 to 5 seconds. On completion of the self-test, the status and active LEDs are green, and the alarm LED is off. If the LEDs do not respond when you insert the xTU-C module is inserted, ensure that the MC is properly powered. Refer to the Cisco 6100 Series Direct Connect Installation Guide (for a Direct Connect configuration) or the Cisco 6100 Set Up and Installation Manual (for a Digital Off-Hook [DOH] configuration) for powering instructions. Step 4 Ensure that a working SC module is inserted in the MC and that it is configured with the correct software image. Step 5 If the LEDs do not respond as indicated in Step 3 when you reinsert the xTU-C module, remove the module and repeat Steps 1 through 4 with the spare xTU-C module. Step 6 If the spare xTU-C module executes properly, return the initial module to Cisco for repair. Contact TAC for the nearest Cisco service center.

6.2.2 Line Concentration Chassis Modules Do Not Work Properly

This section provides tables for troubleshooting the following line concentration chassis (LCC) modules:

Line interface module (LIM) controller module---Table 6-5
LIM---Table 6-6

Table 6-5 provides troubleshooting procedures for the LIM controller module.

.

Table 6-5: LIM Controller Module Status Fault Indications
Symptom Probable Cause Action

The LIM controller module status and line LEDs are not solid green after self-test

The module might be in an incorrect slot

Module might not be properly seated

Step 1 Ensure that the LIM controller module is installed in the proper slot. Slots 11 and 12 in the LCC are the only valid slots for the LIM controller module. Until LIM controller module redundancy is supported, only slot 11 is valid.

Step 2 Remove the LIM controller module from the slot by lifting up the ejector tab and carefully sliding the module out of the LCC.
Note The removal and reinsertion of a LIM controller module causes a loss of service for all active subscribers on the entire LCC. Removal of a LIM controller module causes immediate loss of power to all LIMs in that LCC. Reinsertion of a LIM controller module causes each LIM (and the LIM controller module) to power cycle and self test. When a self-test is complete, connections are automatically restored by the CPE.
Step 3 Reinsert the LIM controller module, making sure the top and bottom of the module are squarely seated in the proper slot.

The module begins executing a self-test. The LEDs cycle for 3 to 5 seconds. On completion of the self-test, the status and active LEDs are green, and the alarm LED is off.

If the LEDs do not respond when the LIM controller module is inserted, ensure that the MC is properly powered. Refer to the Cisco 6100 Set Up and Installation Manual for powering instructions.

Step 4 Ensure that a working SC module is inserted in the MC and that it is configured with the correct NI module software image.

Step 5 If the LEDs do not respond as indicated in Step 3 when you reinsert the LIM controller module, remove the LIM controller module and repeat Steps 1 through 4 with the spare LIM controller module.

Step 6 If the spare LIM controller module executes properly, return the initial LIM controller module to Cisco for repair. Contact TAC for the nearest Cisco service center

Alarm indicates that the LIM controller module does not respond to the System Monitor

Two or more LCCs are jumpered with the same LCC ID

Step 1 Delete all LCCs with the same LCC ID

Step 2 Re-jumper the LCCs using the correct LCC ID. Refer to the Cisco 6100 Set Up and Installation Manual for information about setting the LCC IDs.

Step 3 Repeat Steps 3 through 6 of the preceding procedure.

**Table 6-5: LIM Controller Module Status Fault Indications**
Symptom	Probable Cause	Action
The LIM controller module status and line LEDs are not solid green after self-test	The module might be in an incorrect slot Module might not be properly seated	Step 1 Ensure that the LIM controller module is installed in the proper slot. Slots 11 and 12 in the LCC are the only valid slots for the LIM controller module. Until LIM controller module redundancy is supported, only slot 11 is valid. Step 2 Remove the LIM controller module from the slot by lifting up the ejector tab and carefully sliding the module out of the LCC. Note The removal and reinsertion of a LIM controller module causes a loss of service for all active subscribers on the entire LCC. Removal of a LIM controller module causes immediate loss of power to all LIMs in that LCC. Reinsertion of a LIM controller module causes each LIM (and the LIM controller module) to power cycle and self test. When a self-test is complete, connections are automatically restored by the CPE. Step 3 Reinsert the LIM controller module, making sure the top and bottom of the module are squarely seated in the proper slot. The module begins executing a self-test. The LEDs cycle for 3 to 5 seconds. On completion of the self-test, the status and active LEDs are green, and the alarm LED is off. If the LEDs do not respond when the LIM controller module is inserted, ensure that the MC is properly powered. Refer to the Cisco 6100 Set Up and Installation Manual for powering instructions. Step 4 Ensure that a working SC module is inserted in the MC and that it is configured with the correct NI module software image. Step 5 If the LEDs do not respond as indicated in Step 3 when you reinsert the LIM controller module, remove the LIM controller module and repeat Steps 1 through 4 with the spare LIM controller module. Step 6 If the spare LIM controller module executes properly, return the initial LIM controller module to Cisco for repair. Contact TAC for the nearest Cisco service center
Alarm indicates that the LIM controller module does not respond to the System Monitor	Two or more LCCs are jumpered with the same LCC ID	Step 1 Delete all LCCs with the same LCC ID Step 2 Re-jumper the LCCs using the correct LCC ID. Refer to the Cisco 6100 Set Up and Installation Manual for information about setting the LCC IDs. Step 3 Repeat Steps 3 through 6 of the preceding procedure.

Table 6-6 provides troubleshooting procedures for the LIMs.

Table 6-6: LIM Fault Indications
Symptom Probable Cause Action

LIM(s) status and active LEDs are not solid green after self-test

The module might be in an incorrect slot

Module might not be properly seated

Step 1 Ensure that the LIM is installed in the proper slot. Slots 1 to 10 and 13 to 22 in the LCC are the only valid slots for the LIMs.

Step 2 Remove the LIM from the slot by lifting up the ejector tab(s) and carefully sliding the module out of the LCC.
Note The removal and reinsertion of a LIM can affect no more than four subscriber connections. There is no recovery for the removal of a LIM, because each subscriber line is discretely connected to a specific LIM port through the PSC¹. Subscriber data connects are lost for the duration of the LIM removal. Subscriber voice connections are unaffected.
Step 3 Reinsert the LIM, making sure the top and bottom of the module are squarely seated in the proper slot.

The module begins executing a self-test. The LEDs cycle for 3 to 5 seconds. On completion of the self-test, the status and active LEDs are green, and the alarm LED is off.

If the LEDs do not respond when the LIM controller is inserted, ensure that the MC is properly powered. Refer to the Cisco 6100 Set Up and Installation Guide for powering instructions.

Step 4 Ensure that a working SC module is inserted in the MC and that it is configured with the correct NI module software image.

The LIM controller module communicates with the SC module to obtain software and configuration information for the LIMs. If the SC module is not available, the LIM controller module waits in the initializing state.

Step 5 If the LEDs do not respond as indicated in Step 3 when you reinsert the LIM, remove the LIM and repeat Steps 1 through 4 with the spare LIM.

Step 6 If the spare LIM executes properly, return the initial LIM to Cisco for repair. Contact TAC for the nearest Cisco service center

LIM Line LED blinking green and the subscriber cannot train the line

Subscriber configuration has been deleted

Subscriber's LIM port has been deleted

Refer to a ViewRunner for Windows Provisioning and Operation Guide or the ViewRunner for HP OpenView Provisioning and Operation Guide for information on subscribers and LIM ports.

LIM status LED is off

LIM power failure

Step 1 Reseat the LIM to see of the LEDs are on during power up and progress through self-test

Step 2 If the LEDs are not on, replace the module with a second LIM and repeat Step 1

Step 3 If the second LIM powers and self-tests properly, the first LIM has failed. Return the failed LIM to Cisco. Contact TAC for the nearest Cisco service center

Step 4 If none of the LIMs work in any slot, verify that the LIM controller module is working.

Step 5 Replace the LIM controller module if it is not working.

LIM line LED is solid green, indicating the system has trained. When the LIM receives a signal that an ATU-C is not available, a different ATU-C is chosen

Line quality is poor and the lowest data rates cannot be achieved.

Step 1 See the "Cisco DSL Components Unable to Train" section.

Step 2 If the line trains, review the ATU-C train statistics to determine if some modems are exhibiting a greater number of failed trains than other modems

Step 3 If so, swap modems into the problem slots and recheck train statistics periodically

Step 4 Refer to ViewRunner for Windows Provisioning and Operation Guide or the ViewRunner for HP OpenView Provisioning and Operation Guide for more information on multi-based training.

¹PSC = POTS splitter chassis

**Table 6-6: LIM Fault Indications**
Symptom	Probable Cause	Action
LIM(s) status and active LEDs are not solid green after self-test	The module might be in an incorrect slot Module might not be properly seated	Step 1 Ensure that the LIM is installed in the proper slot. Slots 1 to 10 and 13 to 22 in the LCC are the only valid slots for the LIMs. Step 2 Remove the LIM from the slot by lifting up the ejector tab(s) and carefully sliding the module out of the LCC. Note The removal and reinsertion of a LIM can affect no more than four subscriber connections. There is no recovery for the removal of a LIM, because each subscriber line is discretely connected to a specific LIM port through the PSC¹. Subscriber data connects are lost for the duration of the LIM removal. Subscriber voice connections are unaffected. Step 3 Reinsert the LIM, making sure the top and bottom of the module are squarely seated in the proper slot. The module begins executing a self-test. The LEDs cycle for 3 to 5 seconds. On completion of the self-test, the status and active LEDs are green, and the alarm LED is off. If the LEDs do not respond when the LIM controller is inserted, ensure that the MC is properly powered. Refer to the Cisco 6100 Set Up and Installation Guide for powering instructions. Step 4 Ensure that a working SC module is inserted in the MC and that it is configured with the correct NI module software image. The LIM controller module communicates with the SC module to obtain software and configuration information for the LIMs. If the SC module is not available, the LIM controller module waits in the initializing state. Step 5 If the LEDs do not respond as indicated in Step 3 when you reinsert the LIM, remove the LIM and repeat Steps 1 through 4 with the spare LIM. Step 6 If the spare LIM executes properly, return the initial LIM to Cisco for repair. Contact TAC for the nearest Cisco service center
LIM Line LED blinking green and the subscriber cannot train the line	Subscriber configuration has been deleted Subscriber's LIM port has been deleted	Refer to a ViewRunner for Windows Provisioning and Operation Guide or the ViewRunner for HP OpenView Provisioning and Operation Guide for information on subscribers and LIM ports.
LIM status LED is off	LIM power failure	Step 1 Reseat the LIM to see of the LEDs are on during power up and progress through self-test Step 2 If the LEDs are not on, replace the module with a second LIM and repeat Step 1 Step 3 If the second LIM powers and self-tests properly, the first LIM has failed. Return the failed LIM to Cisco. Contact TAC for the nearest Cisco service center Step 4 If none of the LIMs work in any slot, verify that the LIM controller module is working. Step 5 Replace the LIM controller module if it is not working.
LIM line LED is solid green, indicating the system has trained. When the LIM receives a signal that an ATU-C is not available, a different ATU-C is chosen	Line quality is poor and the lowest data rates cannot be achieved.	Step 1 See the "Cisco DSL Components Unable to Train" section. Step 2 If the line trains, review the ATU-C train statistics to determine if some modems are exhibiting a greater number of failed trains than other modems Step 3 If so, swap modems into the problem slots and recheck train statistics periodically Step 4 Refer to ViewRunner for Windows Provisioning and Operation Guide or the ViewRunner for HP OpenView Provisioning and Operation Guide for more information on multi-based training.

6.2.3 Cisco DSL Components Unable to Train

This section provides troubleshooting tables for the following Cisco DSL components if they are unable to train:

Central office (CO) components---Table 6-7
CPE components---Table 6-8
End-to-end components---Table 6-9

Table 6-7 provides troubleshooting procedures for the CO components that will not train.

Table 6-7: CO DSL Components Unable to Train
Symptom Probable Cause Action

Subscriber cannot get the line to train

Possible hardware failure on system management bus circuit

Step 1 Reseat the LIM or xTU-C module.

Step 2 Verify if LEDs are on during power up.

If the LEDs are on, continue with self-test.
If the LED continues to blink, Go to Step 3.

Step 3 Verify that the modems match with ports by checking the part numbers

Incorrect configuration of CAP ATU-C and DMT-2 ATU-C modules

Note CAP ATU-C and DMT-2 ATU-C modules are easily confused. In a MC of CAP ATU-C modules, you can pull out modules and replace them with DMT-2 ATU-C modules, but the modules will not work. The modules would need to be reconfigured.
Step 1 In the Cisco ViewRunner 6100 Chassis View window, place your cursor over the module slot and click the right mouse button.

Step 2 Click Module Properties, then Configuration.

Step 3 Click Locked.

Step 4 Click OK.

Step 5 From the Edit menu, select Delete.

Step 6 Insert the new module into the MC and wait for the module to be detected

Step 7 The discovery process begins. If using ViewRunner for Windows, Click Discover.

A line is unable to train at the maximum or provisioned upstream/downstream combination data rates

The line reach, gauge (including in-home wiring), and/or quality might prevent this rate combination from being achieved.

Step 1 In the ViewRunner Subscriber Properties window, click Lock on the Administrative State to lock the port.

Step 2 For Margin Configuration, set the noise margins for the downstream and upstream (3D, 6U recommended; 6D, 6U recommended for DMT-2 ATU-C modules).

Step 3 Click Unlocked on the Administrative State to unlock the port.

Step 4 Click Apply or OK.

"Apply" leaves the window open, "OK" closes the window.

The logical pool might contain a faulty xTU-C module (if one train session enables the rates to be achieved and another train session does not).

See Table 6-4 for procedures on replacing faulty xTU-C modules.

**Table 6-7: CO DSL Components Unable to Train**
Symptom	Probable Cause	Action
Subscriber cannot get the line to train	Possible hardware failure on system management bus circuit	Step 1 Reseat the LIM or xTU-C module. Step 2 Verify if LEDs are on during power up. If the LEDs are on, continue with self-test. If the LED continues to blink, Go to Step 3. Step 3 Verify that the modems match with ports by checking the part numbers
Incorrect configuration of CAP ATU-C and DMT-2 ATU-C modules	Note CAP ATU-C and DMT-2 ATU-C modules are easily confused. In a MC of CAP ATU-C modules, you can pull out modules and replace them with DMT-2 ATU-C modules, but the modules will not work. The modules would need to be reconfigured. Step 1 In the Cisco ViewRunner 6100 Chassis View window, place your cursor over the module slot and click the right mouse button. Step 2 Click Module Properties, then Configuration. Step 3 Click Locked. Step 4 Click OK. Step 5 From the Edit menu, select Delete. Step 6 Insert the new module into the MC and wait for the module to be detected Step 7 The discovery process begins. If using ViewRunner for Windows, Click Discover.
A line is unable to train at the maximum or provisioned upstream/downstream combination data rates	The line reach, gauge (including in-home wiring), and/or quality might prevent this rate combination from being achieved.	Step 1 In the ViewRunner Subscriber Properties window, click Lock on the Administrative State to lock the port. Step 2 For Margin Configuration, set the noise margins for the downstream and upstream (3D, 6U recommended; 6D, 6U recommended for DMT-2 ATU-C modules). Step 3 Click Unlocked on the Administrative State to unlock the port. Step 4 Click Apply or OK. "Apply" leaves the window open, "OK" closes the window.
The logical pool might contain a faulty xTU-C module (if one train session enables the rates to be achieved and another train session does not).	See Table 6-4 for procedures on replacing faulty xTU-C modules.

Table 6-8 provides troubleshooting procedures for the CPE components that will not train.

Table 6-8: Cisco 600 Series CPE LED Fault Indicators
Symptom Probable Cause Action

WAN LNK LED blinks continuously and does not stay on solid

Improper cabling/connector

Step 1 Check to see if the correct cable and port are connected.
Note You can provide support personnel with valuable information about a problem by reporting the status of the front-panel LEDs.
Step 2 All remaining probable causes are software configuration issues. See the "Software" section.

Subscriber's LIM port is locked on the Cisco 6100 or Cisco 6130

The ports and modules must be set to "Unlocked" in order for the CPE to train.

Step 1 In the ViewRunner LIM Module Properties window, click the appropriate Port and Configuration tabs.

Step 2 Click Unlocked.

Step 3 Click Apply or OK.

"Apply" leaves the window open, "OK" closes the window.

Subscriber's LIM port is not assigned to an xTU-C pool

Step 1 In the ATU-C Module Properties window, click the appropriate Port tab.

Step 2 Click Edit Pool.

Step 3 Click the Configuration tab.

Step 4 Set the Administrative state to Unlocked.

Step 5 Click Apply or OK.

"Apply" leaves the screen open, "OK" closes the screen.

Port tab LED should change to green.

Step 6 Unlock the module by clicking Module.

Step 7 Click Configuration.

Step 8 Click Unlocked.

Step 9 Click Apply or OK.

"Apply" leaves the screen open, "OK" closes the screen.

The ADSL circuit is physically too long, resulting in excessive attenuation and increased signal-to-noise ratio

Excessive noise on the ADSL circuit

The ADSL line is excessively unbalanced

Call the CO and provide them with the necessary information.

The ADSL line is not connected to the MC

Connect the ADSL line to the MC.

WAN LNK LED turns off after approximately 1.5 minutes

VPI/VCI settings on the CPE do not match the settings on the line card subscriber side

Each subscriber might have multiple PVCs¹ provisioned. Each PVC contains both a network side and a subscriber side virtual connection that are known as VCCs. Each VCC has both a VPI and VCI. All virtual connections consist of a subscriber side VC and network side VC and they must match.

Each subscriber defined must have a VPI/VCI address associated with it before the subscriber can be "Unlocked".

Step 1 From the Subscriber Properties dialog box, click on the Service Provisioning button.

You can add or delete a subscriber's PVC in the Service Provisioning dialog box only when the subscriber's Administrative State is Locked.

Step 2 Enter the VCI/VPI information in the Subscriber and Network boxes. The subscriber side VPI defaults to 1 and is not editable.

Step 3 Click on Add Now. The changes take effect immediately.

Step 4 Repeat Steps 1 through 3 for each VCI/VPI you want to define.

Step 5 When you are finished, click on the Close.

Step 6 To complete this procedure and place the subscriber in service:

Unlock the subscriber.

Subscriber's logical port is locked on the MC

The subscriber setting must be set to "unlocked" in order for the CPE to train.

Step 1 In the ViewRunner Subscriber Properties window, click Unlocked

Step 1 Click OK or Apply

"Apply" leaves the screen open, "OK" closes the screen.

WAN LNK LED turns off after successful transfer of data end-to-end for a variable period of time

There are two timeout features in a modem (xTU-C) that could affect the WAN LNK LED:

IDLE timeout - CPE untrains and the WAN LNK LED turns off (the connected xTU-C module in the Cisco 6100 returns to idle)

Note Continuous WAN traffic keeps resetting the idle timer and no timeout occurs.

SESSION timeout - the WAN LNK LED turns off after a specified time elapses

Note WAN traffic does not reset the session timer and a timeout occurs at the specified time interval.
Step 1 Check to see if the CPE or a far-end router has a PPP timeout set.

Step 2 Check if the MC might be setting a timer in the CPE at the time of train-up.

cbos#show timeout.

If Session timeout is disabled, the VC Reset could determine the wait time before a PPP session restart retries.
Note User activity resets the countdown to 0. In normal operation, when the idle timer is set and active, the countdown continuously runs and is reset by user traffic. After outbound traffic begins, the unit trains up again and reestablishes a PPP session.
Step 3 Set the idle timer either manually (using the management port or telnet) or by the MC at the time train-up occurs.

WAN LNK LED lights solid for approximately 4 seconds and then turns off (drops train and remains idle)

Password authentication problem

The username or password set in the CPE does not match the username and/or password set in the RADIUS² server user list or the router username and password list (when authentication is performed by the router).

Step 1 Type your username and password again.

Step 2 If authentication fails again and/or you forget your password, clear nvram, which returns you to the default user name "root" and no password is assigned.

cbos>en

Password: ******

The cbos# prompt appears indicating the unit is in enable mode. Passwords can be entered, changed, or removed in enable mode.

Step 3 cbos#show run

Verify that the password and username are correct. If not correct,

Step 4 cbos#set ppp wan0-0 login loginname

Step 5 cbos#set ppp wan0-0 password passwordname
Note The CPE is shipped with no passwords assigned. Until passwords are entered by the user, simply press Enter when prompted for an exec or enable password.

WAN ACT LED is off

VPI/VCI settings on the CPE do not match the settings on the line card subscriber side

Each subscriber might have multiple PVCs provisioned. Each PVC contains both a network side and a subscriber side virtual connection called a VCC. Each VCC has both a VPI and VCI. All virtual connections consist of a subscriber side VC and network side VC, and the number of connections must match.

Each subscriber defined must have a VPI/VCI address associated with it before the subscriber can be "Unlocked"

Step 1 From the Subscriber Properties dialog box, click on the Service Provisioning button.

You can add or delete a subscriber's PVC in the Service Provisioning dialog box only when the subscriber's Administrative State is Locked.

Step 2 Enter the VCI/VPI information in the Subscriber and Network boxes. The subscriber side VPI defaults to 1 and is not editable.

Step 3 Click on Add Now. The changes take effect immediately.

Step 4 Repeat Steps 1 through 3 for each VCI/VPI you want to define.

Step 5 When you are finished, click on the Close button.

Step 6 To complete this procedure and place the subscriber in service:

Unlock the subscriber.

The ADSL line is open or shorted

Call the CO and provide them with the necessary information

LAN LNK LED is off

Ethernet connectivity problem

Step 1 If you can not establish a session with the far-end destination, verify that you can ping the Ethernet interface

cbos>show int

cbos>ping xxx.xxx.xxx.xxx (IP address)

or

Step 2 Use a cross-over ("reversal", "null modem", etc.) Ethernet cable between the PC and the CPE.
Note A cross-over cable is shipped with each CPE and is identified by having RJ-45 pins 1 and 2 wired to pins 3 and 6 at the opposite end of the cable.

LAN LNK LED is on

Cannot ping the Ethernet device

If the PC is connected directly to the CPE and still cannot ping the Ethernet interface, the problem might either be with the IP address or subnet mask assignments in either the PC or the CPE.

LAN ACT LED is off

If no activity indicated at the Ethernet hub port, the Ethernet hub could be a source of trouble

Step 1 This LED should be flashing on a busy network and could appear constantly lit during heavy traffic conditions.

Step 2 If this LED is not flashing when traffic is known to be active on the LAN segment where the unit is connected, check the corresponding LED on the LAN hub.

Alarm LED is red
Note It is normal for the Alarm LED will to light for 1 second when the unit is powered up or rebooted.
Hardware is faulty

Step 1 Turn the unit off for at least 5 seconds

Step 2 Turn the unit back on

If the alarm LED still lights continuously, this indicates a hardware problem. Contact TAC for the nearest Cisco service center.

¹PVC = permanent virtual circuits
²RADIUS = Remote Authentication Dial In User Service

**Table 6-8: Cisco 600 Series CPE LED Fault Indicators**
Symptom	Probable Cause	Action
WAN LNK LED blinks continuously and does not stay on solid	Improper cabling/connector	Step 1 Check to see if the correct cable and port are connected. Note You can provide support personnel with valuable information about a problem by reporting the status of the front-panel LEDs. Step 2 All remaining probable causes are software configuration issues. See the "Software" section.
Subscriber's LIM port is locked on the Cisco 6100 or Cisco 6130	The ports and modules must be set to "Unlocked" in order for the CPE to train. Step 1 In the ViewRunner LIM Module Properties window, click the appropriate Port and Configuration tabs. Step 2 Click Unlocked. Step 3 Click Apply or OK. "Apply" leaves the window open, "OK" closes the window.
Subscriber's LIM port is not assigned to an xTU-C pool	Step 1 In the ATU-C Module Properties window, click the appropriate Port tab. Step 2 Click Edit Pool. Step 3 Click the Configuration tab. Step 4 Set the Administrative state to Unlocked. Step 5 Click Apply or OK. "Apply" leaves the screen open, "OK" closes the screen. Port tab LED should change to green. Step 6 Unlock the module by clicking Module. Step 7 Click Configuration. Step 8 Click Unlocked. Step 9 Click Apply or OK. "Apply" leaves the screen open, "OK" closes the screen.
The ADSL circuit is physically too long, resulting in excessive attenuation and increased signal-to-noise ratio Excessive noise on the ADSL circuit The ADSL line is excessively unbalanced	Call the CO and provide them with the necessary information.
The ADSL line is not connected to the MC	Connect the ADSL line to the MC.
WAN LNK LED turns off after approximately 1.5 minutes	VPI/VCI settings on the CPE do not match the settings on the line card subscriber side	Each subscriber might have multiple PVCs¹ provisioned. Each PVC contains both a network side and a subscriber side virtual connection that are known as VCCs. Each VCC has both a VPI and VCI. All virtual connections consist of a subscriber side VC and network side VC and they must match. Each subscriber defined must have a VPI/VCI address associated with it before the subscriber can be "Unlocked". Step 1 From the Subscriber Properties dialog box, click on the Service Provisioning button. You can add or delete a subscriber's PVC in the Service Provisioning dialog box only when the subscriber's Administrative State is Locked. Step 2 Enter the VCI/VPI information in the Subscriber and Network boxes. The subscriber side VPI defaults to 1 and is not editable. Step 3 Click on Add Now. The changes take effect immediately. Step 4 Repeat Steps 1 through 3 for each VCI/VPI you want to define. Step 5 When you are finished, click on the Close. Step 6 To complete this procedure and place the subscriber in service: Unlock the subscriber.
Subscriber's logical port is locked on the MC	The subscriber setting must be set to "unlocked" in order for the CPE to train. Step 1 In the ViewRunner Subscriber Properties window, click Unlocked Step 1 Click OK or Apply "Apply" leaves the screen open, "OK" closes the screen.
WAN LNK LED turns off after successful transfer of data end-to-end for a variable period of time	There are two timeout features in a modem (xTU-C) that could affect the WAN LNK LED: IDLE timeout - CPE untrains and the WAN LNK LED turns off (the connected xTU-C module in the Cisco 6100 returns to idle) Note Continuous WAN traffic keeps resetting the idle timer and no timeout occurs. SESSION timeout - the WAN LNK LED turns off after a specified time elapses Note WAN traffic does not reset the session timer and a timeout occurs at the specified time interval.	Step 1 Check to see if the CPE or a far-end router has a PPP timeout set. Step 2 Check if the MC might be setting a timer in the CPE at the time of train-up. cbos#show timeout. If Session timeout is disabled, the VC Reset could determine the wait time before a PPP session restart retries. Note User activity resets the countdown to 0. In normal operation, when the idle timer is set and active, the countdown continuously runs and is reset by user traffic. After outbound traffic begins, the unit trains up again and reestablishes a PPP session. Step 3 Set the idle timer either manually (using the management port or telnet) or by the MC at the time train-up occurs.
WAN LNK LED lights solid for approximately 4 seconds and then turns off (drops train and remains idle)	Password authentication problem	The username or password set in the CPE does not match the username and/or password set in the RADIUS² server user list or the router username and password list (when authentication is performed by the router). Step 1 Type your username and password again. Step 2 If authentication fails again and/or you forget your password, clear nvram, which returns you to the default user name "root" and no password is assigned. cbos>en Password: **** The cbos# prompt appears indicating the unit is in enable mode. Passwords can be entered, changed, or removed in enable mode. Step 3 cbos#show run Verify that the password and username are correct. If not correct, Step 4 cbos#set ppp wan0-0 login loginname Step 5 cbos#set ppp wan0-0 password passwordname Note The CPE is shipped with no passwords assigned. Until passwords are entered by the user, simply press Enter** when prompted for an exec or enable password.
WAN ACT LED is off	VPI/VCI settings on the CPE do not match the settings on the line card subscriber side	Each subscriber might have multiple PVCs provisioned. Each PVC contains both a network side and a subscriber side virtual connection called a VCC. Each VCC has both a VPI and VCI. All virtual connections consist of a subscriber side VC and network side VC, and the number of connections must match. Each subscriber defined must have a VPI/VCI address associated with it before the subscriber can be "Unlocked" Step 1 From the Subscriber Properties dialog box, click on the Service Provisioning button. You can add or delete a subscriber's PVC in the Service Provisioning dialog box only when the subscriber's Administrative State is Locked. Step 2 Enter the VCI/VPI information in the Subscriber and Network boxes. The subscriber side VPI defaults to 1 and is not editable. Step 3 Click on Add Now. The changes take effect immediately. Step 4 Repeat Steps 1 through 3 for each VCI/VPI you want to define. Step 5 When you are finished, click on the Close button. Step 6 To complete this procedure and place the subscriber in service: Unlock the subscriber.
The ADSL line is open or shorted	Call the CO and provide them with the necessary information
LAN LNK LED is off	Ethernet connectivity problem	Step 1 If you can not establish a session with the far-end destination, verify that you can ping the Ethernet interface cbos>show int cbos>ping xxx.xxx.xxx.xxx (IP address) or Step 2 Use a cross-over ("reversal", "null modem", etc.) Ethernet cable between the PC and the CPE. Note A cross-over cable is shipped with each CPE and is identified by having RJ-45 pins 1 and 2 wired to pins 3 and 6 at the opposite end of the cable.
LAN LNK LED is on	Cannot ping the Ethernet device	If the PC is connected directly to the CPE and still cannot ping the Ethernet interface, the problem might either be with the IP address or subnet mask assignments in either the PC or the CPE.
LAN ACT LED is off	If no activity indicated at the Ethernet hub port, the Ethernet hub could be a source of trouble	Step 1 This LED should be flashing on a busy network and could appear constantly lit during heavy traffic conditions. Step 2 If this LED is not flashing when traffic is known to be active on the LAN segment where the unit is connected, check the corresponding LED on the LAN hub.
Alarm LED is red Note It is normal for the Alarm LED will to light for 1 second when the unit is powered up or rebooted.	Hardware is faulty	Step 1 Turn the unit off for at least 5 seconds Step 2 Turn the unit back on If the alarm LED still lights continuously, this indicates a hardware problem. Contact TAC for the nearest Cisco service center.

Table 6-9 provides troubleshooting procedures for the end-to-end components that will not train.

Table 6-9: System Trained but Observing SNR Fluctuations
Symptom Probable Cause Action

You observe SNR fluctuations

The xTU-C might be faulty

Fluctuations larger than 6 dB cause the line to drop. The line attempts to retrain on the next round-robin port.

No action is necessary because the modem will retrain at a lower upstream/downstream combination rate.

Hardware and software do not match (and the system does not function).

Upgrade the xTU-C module. See Table 6-4 for details.

**Table 6-9: System Trained but Observing SNR Fluctuations**
Symptom	Probable Cause	Action
You observe SNR fluctuations	The xTU-C might be faulty	Fluctuations larger than 6 dB cause the line to drop. The line attempts to retrain on the next round-robin port. No action is necessary because the modem will retrain at a lower upstream/downstream combination rate.
Hardware and software do not match (and the system does not function).	Upgrade the xTU-C module. See Table 6-4 for details.

6.2.4 Cannot Pass Traffic

This section provides tables for troubleshooting the following:

Table 6-10 provides troubleshooting procedures to use if the system experiences data traffic busy signals.

Table 6-10: Experiencing Data Traffic Busy Signals
Symptom Probable Cause Action

Logical pools indicate busy signals (DOH only)

Logical pools are not sized properly for the number of connection requests over a given period of time

Step 1 Check the logical pool performance statistics to see if the number of blocked connections is high relative to the number of successful connections

Step 2 Resize the logical pool by either reducing the number of subscribers or increasing the number of modems. The Logical Pool window in ViewRunner provides subscriber-to-modem ratios

Step 3 If connection statistics appear to be OK, check to see if the subscriber configuration data was deleted, or if the subscriber LIM ports were locked.

If either proves true, incoming connection requests on that LIM port are denied.

You can also detect this problem by observing the blinking LIM ports on a LIM faceplate during a connection request. The LIM port blinks only if a CPE connection request is not in process.

Subscribers cannot see a solid WAN LED on the CPE, and the WAN connection lights on the xTU-C are off (Direct Connect)

Subscriber, port, or module could be administratively locked

No subscriber exists

If connection statistics appear to be OK, check to see if the subscriber configuration data was deleted, or if the subscriber ports were locked.

If either proves true, incoming connection requests on that port are denied.

**Table 6-10: Experiencing Data Traffic Busy Signals**
Symptom	Probable Cause	Action
Logical pools indicate busy signals (DOH only)	Logical pools are not sized properly for the number of connection requests over a given period of time	Step 1 Check the logical pool performance statistics to see if the number of blocked connections is high relative to the number of successful connections Step 2 Resize the logical pool by either reducing the number of subscribers or increasing the number of modems. The Logical Pool window in ViewRunner provides subscriber-to-modem ratios Step 3 If connection statistics appear to be OK, check to see if the subscriber configuration data was deleted, or if the subscriber LIM ports were locked. If either proves true, incoming connection requests on that LIM port are denied. You can also detect this problem by observing the blinking LIM ports on a LIM faceplate during a connection request. The LIM port blinks only if a CPE connection request is not in process.
Subscribers cannot see a solid WAN LED on the CPE, and the WAN connection lights on the xTU-C are off (Direct Connect)	Subscriber, port, or module could be administratively locked No subscriber exists	If connection statistics appear to be OK, check to see if the subscriber configuration data was deleted, or if the subscriber ports were locked. If either proves true, incoming connection requests on that port are denied.

Table 6-11 provides troubleshooting procedures to use if a subscriber line cannot pass voice.

Table 6-11: Subscriber Line Cannot Pass Voice
Symptom Probable Cause Action

The subscriber line cannot pass voice

A lightning or power cross event occurred

The POTS module is broken

There is an open fuse on the POTS module

Fuses at the customer premise equipment (CPE) splitter are open or damaged

The LIM is broken

Step 1 Check both the CPE and CO ends to make sure that you have the correct filter for the phone type being used:

POTS --- 8 MHz
CTX --- 15 MHz

Step 2 Make sure the wiring punch-downs at the MDF¹ are correct.

Step 3 Check the continuity of the tip/ring pair from the MDF to the PSC and back to the MDF.

Step 4 Check for correct POTS module.

Step 5 Replace CO splitter or CPE splitter, if necessary.

Step 6 Refer to the Connection Test Procedures in your ViewRunner Provisioning and Operation Guide to check connectivity.

¹MDF = main distribution frame

**Table 6-11: Subscriber Line Cannot Pass Voice**
Symptom	Probable Cause	Action
The subscriber line cannot pass voice	A lightning or power cross event occurred The POTS module is broken There is an open fuse on the POTS module Fuses at the customer premise equipment (CPE) splitter are open or damaged The LIM is broken	Step 1 Check both the CPE and CO ends to make sure that you have the correct filter for the phone type being used: POTS --- 8 MHz CTX --- 15 MHz Step 2 Make sure the wiring punch-downs at the MDF¹ are correct. Step 3 Check the continuity of the tip/ring pair from the MDF to the PSC and back to the MDF. Step 4 Check for correct POTS module. Step 5 Replace CO splitter or CPE splitter, if necessary. Step 6 Refer to the Connection Test Procedures in your ViewRunner Provisioning and Operation Guide to check connectivity.

Table 6-12 provides troubleshooting procedures to use if a subscriber experiences phone problems.

Table 6-12: Subscriber Experiencing Phone Problems
Symptom Probable Cause Action

No Dial Tone

Continuity was lost in the voice wiring path (from the MDF to the voice switch),

A POTS splitter module is not inserted

A Class 5 voice switch line card was not provisioned.

Step 1 Check the continuity path from CO POTS module to the class 5 switch line card.

Step 2 If good, check the continuity path from CO POTS splitter to the CPE POTS splitter.

Step 3 If good, ensure that a dial tone can be achieved from the CO voice switch line card. (Ensure that the module is provisioned and operational.)

Step 4 Make sure the CO and CPE POTS splitters are compatible with each other and with a phone set in use.

Step 5 If problem persists, replace the POTS module.

There is dial tone, but subscriber cannot place or receive a call

Faulty POTS splitter module

Possible provisioning error for subscriber. The Subscriber, Port, and Module must all be administratively set to unlock or the CPE will not train (See section "Software" for software configuration procedures)

Step 1 If the dial tone can be provided to the phone terminated to the CPE POTS splitter, but an outbound call cannot be placed, the CO POTS splitter might be faulty. Do one of the following:

Step 2 Replace the POTS module (for inability to place a call).

Step 3 Replace the POTS module (for inability to receive a call).

**Table 6-12: Subscriber Experiencing Phone Problems**
Symptom	Probable Cause	Action
No Dial Tone	Continuity was lost in the voice wiring path (from the MDF to the voice switch), A POTS splitter module is not inserted A Class 5 voice switch line card was not provisioned.	Step 1 Check the continuity path from CO POTS module to the class 5 switch line card. Step 2 If good, check the continuity path from CO POTS splitter to the CPE POTS splitter. Step 3 If good, ensure that a dial tone can be achieved from the CO voice switch line card. (Ensure that the module is provisioned and operational.) Step 4 Make sure the CO and CPE POTS splitters are compatible with each other and with a phone set in use. Step 5 If problem persists, replace the POTS module.
There is dial tone, but subscriber cannot place or receive a call	Faulty POTS splitter module Possible provisioning error for subscriber. The Subscriber, Port, and Module must all be administratively set to unlock or the CPE will not train (See section "Software" for software configuration procedures)	Step 1 If the dial tone can be provided to the phone terminated to the CPE POTS splitter, but an outbound call cannot be placed, the CO POTS splitter might be faulty. Do one of the following: Step 2 Replace the POTS module (for inability to place a call). Step 3 Replace the POTS module (for inability to receive a call).

6.3 Software

This section describes problems or conditions you could encounter when you use the ViewRunner management software.

If none of the actions presented are successful, please contact the Cisco TAC for additional support.

Table 6-13 provides troubleshooting procedures to use if the PC running ViewRunner software does not receive information from the MC

Table 6-13: ViewRunner Not Receiving Information from the MC
Symptom Probable Cause Action

The PC running the ViewRunner software is not receiving any information from the MC

Faulty ViewRunner operation

Network congestion

SC module does not respond to SNMP requests (status or configuration)

MC cable might not have connectivity

ViewRunner box might not have route to the MC ethernet network

Incorrect IP address on the ethernet interface to the MC

Step 1 First, check ViewRunner and the MC IP addresses, subnet mask, and default gateway addresses to verify that they are correct. If this is the first time you are accessing the node from ViewRunner, perform this check while ViewRunner is locally attached. This eliminates the management network (LAN) as a potential source of the problem.

Step 2 If you have accessed the node before (from the same ViewRunner PC or workstation) and no IP address changes have occurred, the problem could be caused by management network congestion. Try to ping the MC from the ViewRunner PC or workstation. To do so, open a DOS window and type ping xxx.xxx.xxx.xxx, where xxx.xxx.xxx.xxx represents the IP address of the MC.

Step 3 If the node responds to the ping, there might be nothing wrong with the MC. The problem could be associated with the ViewRunner PC or LAN congestion between the PC and the MC.

Step 4 If the node does not respond to the ping, try to ping to some other location to make sure the problem is not with the ViewRunner PC or workstation, or something associated with the ViewRunner's network connection.

Step 5 If all pings fail, the problem is in the management network. Ask your local Ethernet/IP network administrator for assistance.

Step 6 If other pings are successful, but pings to the MC in question continue to fail, send a technician to the site to see if a local attachment to the MC Ethernet port is successful.

Step 7 If the local attachment succeeds, the problem is almost certainly associated with network congestion.

Step 8 If you conclude that network congestion is the problem, contact your Ethernet/IP network administrator for assistance. Additionally, you can choose the SNMP message timeout from 1 or 5 seconds. To do so, right-click on the MC in the Chassis View, and select the Preferences option.

Step 9 Extending the SNMP message timeout parameter allows for greater delays in the management network. Consequently, SNMP message requests that result from discovery, configuration, or status queries are allowed more time to traverse a potentially congested network between the PC running the ViewRunner software and the MC.

Step 10 If the MC cannot be pinged remotely and cannot be discovered or pinged locally, check the SC faceplate to see if the Alarm LED is on. If it is, an alarm event is present. Refer to the Cisco 6100 Series Alarm Summary Guide to determine the alarm event and respond appropriately. This might result in resetting the SC module.

Step 11 An SC module reset causes all subscriber connections to become disconnected. The connections should be reestablished automatically, however, as a result of the Cisco 67x CPE request for ADSL layer 1 connection. This might require a few seconds, depending on the number of active connections at the time of reset. Resetting the SC module erases the node's event log, so no historical event information will be retrievable.

Step 12 Repeat Steps 1 through 6 to determine if the node is now accessible from the PC running ViewRunner software.

Step 13 If the MC is still inaccessible, the SC module might be faulty.

Step 14 Replace the current SC module with a spare SC module. This is a drastic action because it requires that the new SC module be characterized with the old SC module's NVRAM configuration data. Refer to the ViewRunner for Windows Provisioning and Operation Guide or the ViewRunner for HP OpenView Provisioning and Operation Guide for configuration save and restore procedures.

**Table 6-13: ViewRunner Not Receiving Information from the MC**
Symptom	Probable Cause	Action
The PC running the ViewRunner software is not receiving any information from the MC	Faulty ViewRunner operation Network congestion SC module does not respond to SNMP requests (status or configuration) MC cable might not have connectivity ViewRunner box might not have route to the MC ethernet network Incorrect IP address on the ethernet interface to the MC	Step 1 First, check ViewRunner and the MC IP addresses, subnet mask, and default gateway addresses to verify that they are correct. If this is the first time you are accessing the node from ViewRunner, perform this check while ViewRunner is locally attached. This eliminates the management network (LAN) as a potential source of the problem. Step 2 If you have accessed the node before (from the same ViewRunner PC or workstation) and no IP address changes have occurred, the problem could be caused by management network congestion. Try to ping the MC from the ViewRunner PC or workstation. To do so, open a DOS window and type ping xxx.xxx.xxx.xxx, where xxx.xxx.xxx.xxx represents the IP address of the MC. Step 3 If the node responds to the ping, there might be nothing wrong with the MC. The problem could be associated with the ViewRunner PC or LAN congestion between the PC and the MC. Step 4 If the node does not respond to the ping, try to ping to some other location to make sure the problem is not with the ViewRunner PC or workstation, or something associated with the ViewRunner's network connection. Step 5 If all pings fail, the problem is in the management network. Ask your local Ethernet/IP network administrator for assistance. Step 6 If other pings are successful, but pings to the MC in question continue to fail, send a technician to the site to see if a local attachment to the MC Ethernet port is successful. Step 7 If the local attachment succeeds, the problem is almost certainly associated with network congestion. Step 8 If you conclude that network congestion is the problem, contact your Ethernet/IP network administrator for assistance. Additionally, you can choose the SNMP message timeout from 1 or 5 seconds. To do so, right-click on the MC in the Chassis View, and select the Preferences option. Step 9 Extending the SNMP message timeout parameter allows for greater delays in the management network. Consequently, SNMP message requests that result from discovery, configuration, or status queries are allowed more time to traverse a potentially congested network between the PC running the ViewRunner software and the MC. Step 10 If the MC cannot be pinged remotely and cannot be discovered or pinged locally, check the SC faceplate to see if the Alarm LED is on. If it is, an alarm event is present. Refer to the Cisco 6100 Series Alarm Summary Guide to determine the alarm event and respond appropriately. This might result in resetting the SC module.
		Step 11 An SC module reset causes all subscriber connections to become disconnected. The connections should be reestablished automatically, however, as a result of the Cisco 67x CPE request for ADSL layer 1 connection. This might require a few seconds, depending on the number of active connections at the time of reset. Resetting the SC module erases the node's event log, so no historical event information will be retrievable. Step 12 Repeat Steps 1 through 6 to determine if the node is now accessible from the PC running ViewRunner software. Step 13 If the MC is still inaccessible, the SC module might be faulty. Step 14 Replace the current SC module with a spare SC module. This is a drastic action because it requires that the new SC module be characterized with the old SC module's NVRAM configuration data. Refer to the ViewRunner for Windows Provisioning and Operation Guide or the ViewRunner for HP OpenView Provisioning and Operation Guide for configuration save and restore procedures.

Table 6-14 provides troubleshooting procedures to use if the PC running ViewRunner software displays incorrect color tabs.

Table 6-14: Incorrect ViewRunner Color Tabs
Symptom Probable Cause Action

ViewRunner color tabs are not correct with what the technician or network administrator should see

Incorrect module seated in slot

The SC module has a slot configuration in its MIB, but no module is present when the SC module is initialized or reset. The result is that a blue ejector tab appears.

The modules in the MC display (in ViewRunner for Windows) only the highest hierarchical state color on the ejector tab. The hierarchy (from top to bottom) is

Blue---Unknown

Brown---Locked

Red---Critical (critical alarm event present)

Orange---Major (major alarm event present)

Yellow---Minor (minor alarm event present)

Green---Normal (no alarm event present)

If, for example, a module is in a critical Operational state and a locked Administrative state, the ViewRunner Chassis View displays the higher hierarchical state---in this case, brown.

The actions pertain to the display of the blue (Unknown) state. The significance of each of the other colors should be apparent.

If a module ejector tab is blue, it is typically because one of three things has occurred:

The SC module was reset, and before the reset, a module was installed that has now been removed without being first deleted.

A module was not physically inserted into the slot, but a module configuration was entered at a ViewRunner PC or workstation.

The module in the slot is currently requesting or receiving an image from the SC module. This occurs immediately after a software download.

In any of the previous three cases, a blue tab appears if the SC module has stored a configuration associated with a particular slot. That slot is now empty on reset, it has never been populated since the configuration was created or recently downloaded, or the type of module in the slot is different than the original module configuration.

Step 1 Check the ViewRunner module configuration for the slot. Verify that a configuration exists.

Step 2 If a configuration exists, you have three options:

You can wait until the module has had time to receive its image from the SC module and reset.
You can fill the slot with a module matching the configuration type and rediscover. The tab color should change to either brown (administratively locked) or green (administratively unlocked and operationally enabled).
You can delete the configuration with ViewRunner and rediscover. The slot must contain a filler faceplate if the slot does not contain a module or a module is going to be out of the slot for more than a couple of minutes.

Refer to the ViewRunner for Windows Provisioning and Operation Guide or the ViewRunner for HP OpenView Provisioning and Operation Guide for more information on the Cisco 6100 Series states and tab colors.

**Table 6-14: Incorrect ViewRunner Color Tabs**
Symptom	Probable Cause	Action
ViewRunner color tabs are not correct with what the technician or network administrator should see	Incorrect module seated in slot The SC module has a slot configuration in its MIB, but no module is present when the SC module is initialized or reset. The result is that a blue ejector tab appears. The modules in the MC display (in ViewRunner for Windows) only the highest hierarchical state color on the ejector tab. The hierarchy (from top to bottom) is Blue---Unknown Brown---Locked Red---Critical (critical alarm event present) Orange---Major (major alarm event present) Yellow---Minor (minor alarm event present) Green---Normal (no alarm event present) If, for example, a module is in a critical Operational state and a locked Administrative state, the ViewRunner Chassis View displays the higher hierarchical state---in this case, brown. The actions pertain to the display of the blue (Unknown) state. The significance of each of the other colors should be apparent.	If a module ejector tab is blue, it is typically because one of three things has occurred: The SC module was reset, and before the reset, a module was installed that has now been removed without being first deleted. A module was not physically inserted into the slot, but a module configuration was entered at a ViewRunner PC or workstation. The module in the slot is currently requesting or receiving an image from the SC module. This occurs immediately after a software download. In any of the previous three cases, a blue tab appears if the SC module has stored a configuration associated with a particular slot. That slot is now empty on reset, it has never been populated since the configuration was created or recently downloaded, or the type of module in the slot is different than the original module configuration. Step 1 Check the ViewRunner module configuration for the slot. Verify that a configuration exists. Step 2 If a configuration exists, you have three options: You can wait until the module has had time to receive its image from the SC module and reset. You can fill the slot with a module matching the configuration type and rediscover. The tab color should change to either brown (administratively locked) or green (administratively unlocked and operationally enabled). You can delete the configuration with ViewRunner and rediscover. The slot must contain a filler faceplate if the slot does not contain a module or a module is going to be out of the slot for more than a couple of minutes. Refer to the ViewRunner for Windows Provisioning and Operation Guide or the ViewRunner for HP OpenView Provisioning and Operation Guide for more information on the Cisco 6100 Series states and tab colors.

Table 6-15 provides troubleshooting procedures to use if the PC running ViewRunner software displays incompatible performance statistics.

Table 6-15: Incompatible Performance Statistic Associations
Symptom Probable Cause Action

The associations of the ViewRunner performance statistics, pool summary, subscriber, LIM port, and ATU-C port counters, are incorrect.

If resources are locked, deleted, or reset, the action can affect the association of counters with one another.

Step 1 Determine if the SC module was reset.

Step 2 Determine if a subscriber and/or LIM port was locked or deleted.

Step 3 Determine if an LIM was deleted.

Step 4 If any of the above events have occurred, pool summary, subscriber, and ATU-C port counters do not associate. For example, if a subscriber was deleted, the sum of all subscriber counters does not necessarily associate with the logical pool statistics.

Refer to the ViewRunner for Windows Provisioning and Operation Guide or the ViewRunner for HP OpenView Provisioning and Operation Guide for more information on the resetting of counters.

Table of Contents

Troubleshooting