Troubleshooting

You will, at some point, need to troubleshoot your modem and its configuration. Debug output is usually crucial to this process. As always with debugging, only turn on that which is absolutely necessary and turn it off as soon as you are done. Debug commands can produce substantial amounts of output and can have a rather dramatic (and negative) effect on the functionality of your router.

Debugging Modem Autoconfiguration

If you suspect that your modem is not being detected during autoconfiguration or discovery, debug is the first thing to check. From an enable prompt, issue the debug confmodem command. You see each string that the router is trying and the current bit rate. If after all the initialization strings are tried at all bit rates, you have not detected your modem, there is something wrong at the physical level:

 Router#debug confmodem Modem Configuration Database debugging is on Jan 1 01:01:01.000: TTY1: detection speed (115200) response ---OK--- Jan 1 01:01:01.000: TTY1: Modem command: --AT&FS0=1&D3-- Jan 1 01:01:02.000: TTY1: Modem configuration succeeded Jan 1 01:01:02.000: TTY1: Detected modem speed 115200 Jan 1 01:01:02.000: TTY1: Done with modem configuration 

In addition to issuing the debug command, it is advisable to use show line to see which lines are currently in use (and have been configured) and use clear line if necessary. Occasionally, a modem encounters a problem and does not reset when it loses the carrier signal. If this problem happens, the router doesn't actually know to redetect the modem and a clear line resets the process:

 Router#show line    Tty Typ     Tx/Rx    A   Modem  Roty AccO AccI   Uses   Noise  Overruns *    0 CTY               -    -      -    -    -      0       0     0/0 *    1 TTY 115200/115200 -  inout    -    -    -      0       0     0/0     65 AUX   9600/9600   -    -      -    -    -      0       0     0/0 *   66 VTY               -    -      -    -    -      8       0     0/0     67 VTY               -    -      -    -    -      3       0     0/0     68 VTY               -    -      -    -    -      1       0     0/0     69 VTY               -    -      -    -    -      0       0     0/0     70 VTY               -    -      -    -    -      0       0     0/0 Router#clear line 1 

The * in the show line output shows that a line is in use, and the clear line command uses the line number from the show line output.

graphics/alert_icon.gif

debug confmodem is one of the best tools you have to troubleshoot a modem that is not responsive. It does produce a lot of output, however, so be sure to turn off or disable the debug command when you are done.


Additional Troubleshooting

One common mistake, or overlooked step, is to make sure that the serial interface is configured for asynchronous mode. If you cannot get into asynchronous interface mode, you have probably forgotten this step:

 Router(config-if)#physical-layer async 

Once you configure the serial interface to be asynchronous, it can communicate with the modem.

If debugging shows that the modem isn't being detected, check the following:

  • Is the power supply connected?

  • Is the modem powered on?

  • Is the cable connected securely between the modem and the router?

  • Can you reverse Telnet to the modem?

graphics/alert_icon.gif

If the physical port is in asynchronous mode and you still cannot use the modem, check your physical connections, try another modem, and make sure that you are connected to the correct serial port.




CCNP BCRAN Remote Access Exam Cram 2 (Exam Cram 640 - XXX)
CCNP BCRAN Remote Access Exam Cram 2 (Exam Cram 640 - XXX)
ISBN: N/A
EAN: N/A
Year: 2003
Pages: 183

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net