Cisco Router 826 Routers Software Configuration Guide

							  
4-45
Cisco 826, 827, 828, 831, 836, and 837 and Cisco SOHO 76, 77, 78, 91, 96, and 97 Routers Software Configuration Guide
78-14565-03
Chapter 4      Advanced Router Configuration
Configuring FTP Client
 dsl firmware secondary  ===========> New CLI
!
ip classless
ip http server
ip pim bidir-enable
!
line con 0
 exec-timeout 0 0
 stopbits 1
line vty 0 4
 login
!
scheduler max-task-time 5000
end
827-sus2#
Configuring FTP Client
The File Transfer Protocol (FTP) is an application protocol in the Internet protocol suite. It supports file 
transfers among unlike hosts in diverse internetworking environments. Using FTP, you can move a file 
from one computer to another, even if each computer runs a different operating system and uses a 
different file storage format. Cisco routers that can function as FTP clients can copy files from FTP 
servers into Flash memory. 
When Cisco Router Web Setup (CRWS) software is installed on the router, it uses FTP to update the 
Cisco IOS image in Flash memory, and it configures the router with the FTP username and password that 
it requires. 
CautionCRWS is unable to perform automatic updates if the FTP username and password values it places in 
the configuration file are changed.
If you need to use FTP to manually copy system images to Flash memory, see the instructions for adding 
an FTP username and password to the configuration file at the following URL:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122cgcr/
ffun_c/ffcprt2/fcf008.htm 
						

							  
4-46
Cisco 826, 827, 828, 831, 836, and 837 and Cisco SOHO 76, 77, 78, 91, 96, and 97 Routers Software Configuration Guide
78-14565-03
Chapter 4      Advanced Router Configuration
Configuring FTP Client 
						

							CHAPTER
  
5-1
Cisco 826, 827, 828, 831, 836, and 837 and Cisco SOHO 76, 77, 78, 91, 96, and 97 Routers Software Configuration Guide
78-14565-03
5
Troubleshooting
Use the information in this chapter to help isolate problems you might encounter or to rule out the router 
as the source of the problem. This chapter contains the following sections:
Before Contacting Cisco or Your Reseller, page 5-1
ADSL Troubleshooting, page 5-2
G.SHDSL Troubleshooting, page 5-2
ATM Troubleshooting Commands, page 5-5
Software Upgrade Methods, page 5-11
Recovering a Lost Password, page 5-11
Managing the Cisco Router Web Setup Tool, page 5-14
Before troubleshooting a software problem, you must connect a terminal or PC to the router via the 
light-blue console port. (For information on making this connection, see the documentation listed in the 
“Related Documents” section on page -xiii.) With a connected terminal or PC, you can read status 
messages from the router and enter commands to troubleshoot a problem.
You can also remotely access the interface (Ethernet, ADSL, or telephone) by using Telnet. The Telnet 
option assumes that the interface is up and running.
Before Contacting Cisco or Your Reseller
If you cannot locate the source of a problem, contact your local reseller for advice. Before you call, you 
should have the following information ready:
Chassis type and serial number
Maintenance agreement or warranty information
Type of software and version number 
Date you received the hardware
Brief description of the problem
Brief description of the steps you have taken to isolate the problem 
						

							  
5-2
Cisco 826, 827, 828, 831, 836, and 837 and Cisco SOHO 76, 77, 78, 91, 96, and 97 Routers Software Configuration Guide
78-14565-03
Chapter 5      Troubleshooting
ADSL Troubleshooting
ADSL Troubleshooting
This section describes some asymmetric digital service line (ADSL) troubleshooting checks that you can 
perform if the router is not working properly. If you experience trouble with the ADSL connection, make 
sure to verify the following:
That the ADSL line is connected and is using pins 3 and 4. For more information on the ADSL 
connection, see the hardware guide for your router.
That the ADSL CD LED is on. If it is not on, the router may not be connected to the digital 
subscriber line access multiplexer (DSLAM). For more information on the ADSL LEDs, see the 
hardware installation guide specific to your router.
That you are using the correct Asynchronous Transfer Mode (ATM) variable path 
indentifier/variable circuit identifier (VPI/VCI).
That the DSLAM supports discrete multi-tone (DMT) Issue 2.
ADSL Cable Requirements
The ADSL cable that you connect to the Cisco router must be 10BaseT Category 5, unshielded 
twisted-pair (UTP) cable. Using regular telephone cable can introduce line errors.
G.SHDSL Troubleshooting
Symmetrical high-data-rate digital subscriber line (G.SHDSL) is available on Cisco 828 and 
Cisco SOHO 78 routers. This section describes some G.SHDSL troubleshooting checks that you can 
perform if the router is not working properly. If you experience trouble with the G.SHDSL connection, 
verify the following:
That the G.SHDSL line is connected and using pins 3 and 4 — For more information on the 
G.SHDSL connection, see the Cisco 828 Router and SOHO 78 Router Hardware Installation Guide.
That the G.SHDSL CD LED is on — If it is not on, the router may not be connected to the digital 
subscriber line access multiplexer (DSLAM). For more information on the G.SHDSL LEDs, see the 
Cisco 828 Router and SOHO 78 Router Hardware Installation Guide.
That you are using the correct asynchronous transfer mode (ATM) variable path indentifier/variable 
circuit identifier (VPI/VCI).
That the DSLAM supports G.SHDSL.
show dsl interface Command
Use the show dsl interface command to display the status of a G.SHDSL physical port on the router.
Following is example output for the show dsl interface command:
_Router# show dsl interface atm0
Globespan G.SHDSL/SDSL Chipset Information
 Equipment Type:         Customer Premise
 Operating Mode:         G.SHDSL Annex A
 Clock Rate Mode:        Fixed rate Mode 
						

							  
5-3
Cisco 826, 827, 828, 831, 836, and 837 and Cisco SOHO 76, 77, 78, 91, 96, and 97 Routers Software Configuration Guide
78-14565-03
Chapter 5      Troubleshooting
G.SHDSL Troubleshooting
 Reset Count:            1
 Requested rate:         72 Kbps
 Actual rate:            72 Kbps
 Modem Status:           Data (0x1)
 Noise Margin:           37 dB
 Loop Attenuation:       0.4294963186 dB
 Transmit Power:         11.7 dBm
 Receiver Gain:          4.2040 dB (2271, 4210, 90)
 Last Activation Status: No Failure (0x0)
 CRC Errors:             2
 Chipset Version:        1
 Firmware Version:       R1.0
 Country Code:           0xB500
 Provider Code:          0x4E505347
 Vendor Data:            0x0 0x0 0x0 0x0 
                         0x0 0x0 0x0 0x0 
Performance statistics since reload:
Number of LOS failures:             0
Number of LOSQ failures:            0
Number of coding violations:        0
Number of errored seconds:          0
Number of severely errored seconds: 0
Number of unavailable seconds:      0
Performance statistics for:               Current 15 mins   Current 24 Hours
Time elapsed since beginning of interval:    6Min             0Hr  6Min
Number of LOS seconds:                       0                0
Number of LOSQ seconds:                      0                0
Number of code violations:                   0                0
Number of errored seconds:                   0                0
Number of severely errored seconds:          0                0
Number of unavailable seconds:               0                0
Ta b l e 5 - 1 describes possible command output for the show interface command. Each line in the 
command output example corresponds to a row in this table.
Table 5-1 Show DSL Interface Command Output Description
Output Description
Equipment Type
Customer Premise Equipment (CPE), if 
connected to a DSLAM.
Central Offices (COs); if the routers are 
connected back to back, then one of the routers 
can act as a CO.
Operating Mode G.SHDSL annex configuration
Clock Rate Mode Upstream and downstream bit rate configuration. 
Either AUTO for fixed.
Reset Count Number of times the G.SHDSL chip has been reset 
since power-up.
Requested rate User-specified bit rate requirement.
Actual rate The actual bit rate that the transceiver is using. 
						

							  
5-4
Cisco 826, 827, 828, 831, 836, and 837 and Cisco SOHO 76, 77, 78, 91, 96, and 97 Routers Software Configuration Guide
78-14565-03
Chapter 5      Troubleshooting
G.SHDSL Troubleshooting
Modem StatusHandshake, when local transceiver tries to reach 
the far-end transceiver.
Training; indicates the startup training is in 
progress.
Data, if successfully trained.
Received SNR The received signal-to-noise ratio (SNR).
Loop Attenuation The difference in decibels (dB) between the power 
received at the near-end and the power transmitted 
from the far-end.
Transmit Power Local STU transmit power.
Receiver Gain Total receiver gain.
Last Activation Status Defines the last failure state of the G.SHDSL chip.
CRC Errors Cyclic redundancy check errors.
Chipset Version Vendor’s chipset information.
Firmware Version Vendor’s firmware release version.
Country Code The country identification for the far end.
Provider Code Identification of the vendor.
Vendor data Vendor-specific information.
Number of LOS failures Loss of synchronization counter increased when it 
contains one or more error in the framing bits. If the 
counter continues to increase during or after 
training, the line might be noisy or the cable is not 
connected.
Number of LOSQ failures Loss of signal quality counter is increased when 
SNR is below the threshold.
Number of code violations Code violation is defined as a count of the CRC 
anomalies occurring during the accumulation 
period.
Number of errored seconds An errored second is a count of 1-second intervals 
during which one or more CRC anomalies/loss of 
sync words are declared.
Number of severely errored seconds A severely errored second is a count of 1-second 
intervals during which 50 or more CRC anomalies 
are declared.
Number of unavailable seconds An unavailable second is a count of 1-second 
intervals for which the DSL line is unavailable.
Table 5-1 Show DSL Interface Command Output Description (continued)
Output Description 
						

							  
5-5
Cisco 826, 827, 828, 831, 836, and 837 and Cisco SOHO 76, 77, 78, 91, 96, and 97 Routers Software Configuration Guide
78-14565-03
Chapter 5      Troubleshooting
ATM Troubleshooting Commands
ATM Troubleshooting Commands
This section describes some ATM troubleshooting commands.
ping atm interface Command
You can use the ping atm interface command to determine whether a particular PVC is in use. The PVC 
does not need to be configured on the router in order for you to use this command.
For example, to test whether PVC 1/200 is in use, use the following command:
Router# ping atm interface atm 0 1 200 seg-loopback 
Type escape sequence to abort.
Sending 5, 53-byte segment OAM echoes, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 148/148/148 ms
This command sends five OAM F5 loopback packets to the DSLAM (segment OAM packets). If the PVC 
is configured at the DSLAM, the ping is successful.
To test whether the PVC is being used at the aggregator, enter the following command:
Router# ping atm interface atm 0 1 200 end-loopback 
Type escape sequence to abort.
Sending 5, 53-byte end-to-end OAM echoes, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 400/401/404 ms
This command sends end-to-end OAM F5 packets, which are echoed back by the aggregator.
show interface Command
Use the show interface command to display the status of all physical ports (Ethernet and ATM) and 
logical interfaces on the router. Significant messages in the command output are shown in bold. 
Significant messages are described in Ta b l e 5 - 2 , P a r t 1.
820-uut2#sh int atm0
ATM0 is up, line protocol is up 
  Hardware is PQUICC_SAR (with Alcatel ADSL Module)
  Internet address is 14.0.0.16/8
  MTU 1500 bytes, sub MTU 1500, BW 640 Kbit, DLY 80 usec, 
     reliability 40/255, txload 1/255, rxload 1/255
  Encapsulation ATM, loopback not set
  Keepalive not supported 
  Encapsulation(s):AAL5, PVC mode
  10 maximum active VCs, 1 current VCCs
  VC idle disconnect time:300 seconds
  Last input 01:16:31, output 01:16:31, output hang never
  Last clearing of show interface counters never
  Input queue:0/75/0 (size/max/drops); Total output drops:0
  Queueing strategy:Per VC Queueing
  5 minute input rate 0 bits/sec, 0 packets/sec
  5 minute output rate 0 bits/sec, 0 packets/sec
     512 packets input, 59780 bytes, 0 no buffer
     Received 0 broadcasts, 0 runts, 0 giants, 0 throttles
     0 input errors, 1024 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort 
						

							  
5-6
Cisco 826, 827, 828, 831, 836, and 837 and Cisco SOHO 76, 77, 78, 91, 96, and 97 Routers Software Configuration Guide
78-14565-03
Chapter 5      Troubleshooting
ATM Troubleshooting Commands
     426 packets output, 46282 bytes, 0 underruns
     0 output errors, 0 collisions, 2 interface resets
     0 output buffer failures, 0 output buffers swapped out
820-uut2#sh int eth0
Ethernet0 is up, line protocol is up 
Hardware is PQUICC Ethernet, address is 0000.Oc13.a4db 
(bia0010.9181.1281)
Internet address is 170.1.4.101/24
MTU 1500 bytes, BW 10000 Kbit, DLY 1000 usec, 
reliability 255/255., txload 1/255, rxload 1/255
Encapsulation ARPA, loopback not set
Keepalive set (10 sec)
820-uut2#sh int dialer 1
Dialer 1 is up, line protocol is up 
Hardware is Dialer interface
Internet address is 1.1.1.1/24
MTU 1500 bytes, BW 100000 Kbit, DLY 100000 usec, reliability
255/255. txload 1/255, rxload 1/255
Encapsulation PPP, loopback not set
Keepalive set (10 sec)
DTR is pulsed for 5 seconds on reset
LCP Closed
Ta b l e 5 - 2 , P a r t 1 describes possible command output for the show interface command. Each line in the 
command output example corresponds to a row in this table.
Table 5-2, Part 1 show interface Command Output Description
Output Description
ATM0 is up, line protocol is up 
Other possible messages:

ATM0 is down, line protocol is down
ATM0 is down, line protocol is down
The ATM line is up and operating correctly.
The ATM interface has been disabled with the 
shutdown command.
The ATM line is down, possibly because the 
ADSL cable is disconnected or because the 
wrong type of cable is connected to the ATM 
port.
ATM0.1 is up, line protocol is up 
Other possible messages:

ATM0.1 is administratively down, line 
protocol is down
ATM0.1 is down, line protocol is down
The first ATM subinterface is up and operating 
correctly.
The ATM subinterface has been disabled with 
the shutdown command.
The ATM subinterface is down, possibly 
because the ATM line has been disconnected (by 
the service provider).
Ethernet0 is up, line protocol is up
Other possible messages:

Ethernet0 is up, line protocol is down
Ethernet0 is administratively down, line 
protocol is down
The Ethernet interface is connected to the 
network and operating correctly.
The Ethernet interface has been correctly 
configured and enabled, but the Ethernet cable 
might be disconnected from the LAN.
The Ethernet interface has been disabled with 
the shutdown command, and the interface is 
disconnected. 
						

							  
5-7
Cisco 826, 827, 828, 831, 836, and 837 and Cisco SOHO 76, 77, 78, 91, 96, and 97 Routers Software Configuration Guide
78-14565-03
Chapter 5      Troubleshooting
ATM Troubleshooting Commands
show atm interface Command
To display ATM-specific information about an ATM interface, use the show atm interface atm0 
privileged EXEC command. Following is the command syntax:
show atm interface atm0
Following is an output example from the show interface atm command:
tw_820#sh atm int atm 0
Interface ATM0:
AAL enabled: AAL5 , Maximum VCs:11, Current VCCs:0
Maximum Transmit Channels:0
Max. Datagram Size:1528
PLIM Type:INVALID - 640Kbps, Framing is INVALID,
DS3 lbo:short, TX clocking:LINE
0 input, 0 output, 0 IN fast, 0 OUT fast
Avail bw = 640 
Config. is ACTIVE
Ta b l e 5 - 3 describes the fields shown in the command output. Dialer1 is up, line protocol is up
Another possible message:
Dialer1 is down, line protocol is down
Dialer1 is up and operating correctly.
Dialer1 is not operating, possibly because the 
interface has been brought down with the 
shutdown command or the ADSL cable is 
disconnected.
Dialer1 is down, line protocol is down 
This is a standard message and does not indicate 
anything wrong with the configuration
Table 5-2, Part 1 show interface Command Output Description (continued)
Output Description
Table 5-3 show atm interface Command Output Description
Field Description
ATM interface Interface number. Always 0 for the Cisco 827 routers.
AAL enabled Type of AAL enabled. The Cisco 827 routers support AAL5.
Maximum VCs Maximum number of virtual connections this interface 
supports.
Current VCCs Number of active virtual channel connections (VCCs).
Maximum 
Transmit
ChannelsMaximum number of transmit channels.
Max Datagram 
SizeThe configured maximum number of bytes in the largest 
datagram.
PLIM Type Physical layer interface module (PLIM) type 
						

							  
5-8
Cisco 826, 827, 828, 831, 836, and 837 and Cisco SOHO 76, 77, 78, 91, 96, and 97 Routers Software Configuration Guide
78-14565-03
Chapter 5      Troubleshooting
ATM Troubleshooting Commands
debug atm Commands
This section describes how to use the debug atm commands with additional keywords to troubleshoot 
the router.
Before Using Debug Commands
You can use the debug commands to troubleshoot configuration problems that you might be having on 
your network. Debug commands provide extensive, informative displays to help you interpret any 
possible problems. All debug commands are entered in privileged EXEC mode, and most debug 
commands take no arguments. Read the information in  before using debug commands.
CautionDebugging is assigned a high priority in your router CPU process, and it can render your router unusable. 
For this reason, use debug commands only to troubleshoot specific problems. The best time to use debug 
commands is during periods of low network traffic so that other activity on the network is not adversely 
affected.
debug atm errors Command
Use the debug atm errors command to display ATM errors. The no form of this command disables 
debugging output. Following is the command syntax:
debug atm errors
no debug atm errors
Following is sample debug atm errors output.
820-uut2#deb atm err
ATM errors debugging is on
Router#
01:32:02:ATM(ATM0.2):VC(3) Bad SAP received 4500
01:32:04:ATM(ATM0.2):VC(3) Bad SAP received 4500
01:32:06:ATM(ATM0.2):VC(3) Bad SAP received 4500
01:32:08:ATM(ATM0.2):VC(3) Bad SAP received 4500
01:32:10:ATM(ATM0.2):VC(3) Bad SAP received 4500
Table 5-4 Important Information About Debug Commands
Additional documentation You can find additional information and documentation about the 
debug commands in the Debug Command Reference document on 
the Cisco IOS software documentation CD-ROM that came with 
your router.
If you are not sure where to find this document on the CD-ROM, use 
the Search function in the Verity Mosaic browser that comes with 
the CD-ROM.
Disabling debugging To turn off any debugging, enter the undebug all command.
Viewing debug message To view debug messages on the console, enter the logging console 
debug command.
Telnet sessions If you want to use debug commands during a Telnet session with 
your router, you must first enter the terminal monitor command.