Configuring Global Parameters
Follow these steps to configure the router for global parameters.
Configuring Security
Follow these steps to configure the router with security measures.
Configuring the Fast Ethernet Interface
Follow these steps to configure the Fast Ethernet interface, which connects your router to the local network.
Configuring the Serial Interface
Follow these steps to configure the serial interface, which connects your router to the central-site router.
Configuring Dynamic Routing Parameters
Follow these steps to configure some dynamic routing parameters.
Configuring Command-Line Access to the Router
Follow these steps to configure parameters that control access to the router.
Verifying Your Configuration
You can verify your configuration by checking the serial interface configuration:
Step 1 From privileged EXEC command mode, enter the show interface serial0 command. You should see output similar to the following:
Router# show interface ser0
Serial0 is up, line protocol is up
Hardware is PowerQUICC Serial
Description: leased line to headquarters
Interface is unnumbered. Using address of FastEthernet0 (10.1.1.1)
MTU 1500 bytes, BW 1544 Kbit, DLY 20000 usec, rely 255/255, load 1/255
Encapsulation PPP, loopback not set, keepalive set (10 sec)
LCP Closed
.
.
.
Step 2 Confirm that the "Serial0 is up, line protocol is up" message appears, as shown in the command output example.
Step 3 Proceed as appropriate:
•If you see the "Serial0 is up, line protocol is up" message shown in the example command output, continue configuration by reentering global configuration mode.
•If you see one of the following messages instead of the "Serial0 is up, line protocol is up" message, see the "Troubleshooting Problems with Leased Lines" section for possible causes of the message and suggested actions:
–Serial0 is down, line protocol is down.
–Serial0 is up, line protocol is down.
–Serial0 is up, line protocol is up (looped).
–Serial0 is administratively down, line protocol is up.
Troubleshooting Problems with Leased Lines
Table 6-1 describes some common problems with leased lines, possible causes, and suggested actions for solving the problems. The table uses Serial 0 port as the location of the problems.
Table 6-1 Possible Causes of and Suggested Actions for Solving Problems with Leased Lines
Serial0 is down, line protocol is down.
The router is not sensing a Carrier Detect (CD) signal as a result of one of the following:
•Telephone company problem, such as the line is down or not connected to the data service unit / channel service unit (DSU/CSU).
•Faulty or incorrect cabling of the router.
•Local DSU/CSU hardware failure.
•Local router hardware failure.
The following are some steps you can take to isolate the problem:
•Check the LEDs on the external DSU/CSU for CD activity.
•Refer to the Hardware Installation Guide to confirm that your router is correctly installed, using the appropriate cables.
•Contact the telephone company to determine if the leased line is down or not connected.
•Connect the leased line to another port, if possible. If the connection comes up, there is a hardware failure on the Serial 0 port. Contact your Cisco reseller.
Serial0 is up, line protocol is down.
Possible causes for this line state are
•Local or remote router misconfigured.
•The remote router is not sending keepalive packets.
•Problem with the leased line.
•The serial clock transmit external is not set on the DSU/CSU.
•Local or remote DSU/CSU hardware failure.
•Router hardware failure.
The following are some steps you can take to isolate the problem:
•Perform DSU/CSU loopback tests. During local loopback, enter the show interface ser0 command. If the line protocol is shown as up, there might be a problem with the telephone company, or the remote router might be down.
•Refer to the Hardware Installation Guide to confirm that your router is correctly installed, using the appropriate cables.
•Connect the leased line to another port, if possible. If the connection comes up, there is a hardware failure on the Serial 0 port. Contact your Cisco reseller.
Serial0 is up, line protocol is up (looped).
The possible cause is that a loop exists in the circuit. The sequence number in the keepalive packet changes to a random number when a loop is first detected. If the same random number is returned over the line, a loop exists.
The following are some steps you can take to isolate the problem:
•Use the write terminal privileged EXEC command to display any instances of the loopback command. If the router has been configured with the loopback command, enter the no loopback command to remove the loop.
•Check to see whether the DSU/CSU is configured in manual loopback mode. If it is, disable manual loopback.
•Reset the DSU/CSU.
•If you are unable to isolate the problem, contact the telephone company for help with troubleshooting.
Serial0 is administratively down, line protocol is up.
The possible causes for this state are
•The serial interface has been disabled with the shutdown interface configuration command.
•Different interfaces on the router are using the same IP address.
The following are some steps you can take to isolate the problem:
•Use the show configuration privileged EXEC command to display the serial port configuration. If "shutdown" is displayed after "interface Serial0," use the no shutdown interface configuration command to enable the interface.
•Use the show interface privileged EXEC command to display the IP addresses for all router interfaces. Use the ip address interface configuration command to assign unique IP addresses to the router interfaces.