0% found this document useful (0 votes)
51 views5 pages

Configuring Cisco Back-to-Back Serial

This lab document provides instructions for configuring a back-to-back serial connection between two Cisco routers. The objective is to understand how to bring up a serial connection when routers do not receive clocking from an external source. The tasks include configuring hostnames on the routers, enabling the serial interfaces, configuring one router interface as the clock source, setting the clock rate, configuring IP addresses, and verifying connectivity.

Uploaded by

mayudesk desk
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
51 views5 pages

Configuring Cisco Back-to-Back Serial

This lab document provides instructions for configuring a back-to-back serial connection between two Cisco routers. The objective is to understand how to bring up a serial connection when routers do not receive clocking from an external source. The tasks include configuring hostnames on the routers, enabling the serial interfaces, configuring one router interface as the clock source, setting the clock rate, configuring IP addresses, and verifying connectivity.

Uploaded by

mayudesk desk
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd

Lab 5.

Configuring Back-to-
Back Serial Connections

Lab Objective:
The objective of this lab exercise is to configure back-to-back Serial
interfaces between two Cisco routers. By default, router Serial
interfaces receive their clocking information from an external device
such as a CSU/DSU.

Lab Purpose:
Back-to-back Serial interface configuration is a fundamental skill.
Because routers typically receive clocking from an external device
such as a CSU/DSU, it is imperative to understand how to bring up a
back-to-back Serial connection between two routers to set up your
home lab, for example. As a Cisco engineer, as well as in the Cisco
CCNA exam, you will be expected to know how to configure back-to-
back Serial connections.

Lab Topology:
Please use the following topology to complete this lab exercise:

Task 1:
Configure hostnames on R1 and R2 as illustrated in the topology.

Task 2:
Enable Serial interfaces on R1 and R2. The Serial0/0 interface on
R2 is identified as the DCE in the topology. Use the appropriate show
command to verify that this interface is indeed the DCE.

Task 3:
Configure the DCE interface on R2 to provide clocking to R1. The
clock speed should be 256 Kbps. Remember that 1 Kbps = 1000
bps. Verify that R1 receives clocking information from R2.

Task 4:
Configure IP addressing on R1 and R2 Serial0/0 interfaces as
illustrated in the topology.

Task 5:
Verify your interface status and ping between R1 and R2 to validate
connectivity.
Lab 5. Configuration and
Verification

Task 1:
For reference information on configuring hostnames, please refer to
earlier labs.

Task 2:
R1(config)#interface serial0/0
R1(config-if)#no shut
*Mar 1 00:36:47.282: %LINK-3-UPDOWN: Interface Serial0/0, changed state
to down
R1(config-if)#end
R1#

R2(config)#interface serial0/0
R2(config-if)#no shut
*Mar 1 00:36:47.282: %LINK-3-UPDOWN: Interface Serial0/0, changed state
to down
R2(config-if)#end
R2#show controllers serial 0/0
Interface Serial0/0
Hardware is PowerQUICC MPC860
DCE V.35, no clock

NOTE: The show controllers command will tell you whether the
interface is the DCE side (which provides the clocking) or the DTE
side (which receives the clocking) on a particular router interface.
Note that GNS3 doesn’t use actual cables so there is no need to
configure clocking.

Task 3:
R2#conf t
Enter configuration commands, one per line. End with CTRL/Z.
R2(config)#interface serial0/0
R2(config-if)#clock rate 256000
R2(config-if)#end
R2#show controllers serial0/0
Interface Serial0/0
Hardware is PowerQUICC MPC860
DCE V.35, clock rate 256000

R1#show controllers serial0/2


Interface Serial0/0
Hardware is PowerQUICC MPC860
DTE V.35 TX and RX clocks detected.

Task 4:
For reference information on configuring IP addressing, please refer
to earlier labs.

Task 5:
R1#show ip interface brief
Interface IP-Address OK? Method Status Protocol
Serial0/0 [Link] YES manual up up

R1#ping [Link]

Type escape sequence to abort.


Sending 5, 100-byte ICMP Echos to [Link], timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 8/8/12 ms

R2#show ip interface brief


Interface IP-Address OK? Method Status Protocol
Serial0/0 [Link] YES manual up up

R2#ping [Link]

Type escape sequence to abort.


Sending 5, 100-byte ICMP Echos to [Link], timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 8/8/12 ms

Common questions

Powered by AI

The 'show ip interface brief' command is used in this lab to quickly assess the status of router interfaces. It provides specific details such as the interface name, assigned IP address, whether the IP configuration is OK and manually configured, and the current operational status and protocol status ('up' or 'down'). This command helps verify that interfaces are correctly configured and operational, such as confirming that the Serial0/0 interface is 'up' and able to transmit data .

The lab exercise demonstrates the use of the 'no shut' command by enabling the Serial0/0 interfaces on both R1 and R2. Interfaces on Cisco routers are administratively down by default, and the 'no shut' command brings them up, allowing data transmission. This step is validated when the interface status changes from 'down' to 'up', indicating that the link is active and ready to transmit data, essential for further configuration and connectivity verification .

The 'show controllers serial' command is used to confirm which device is the DCE on a Cisco router. This is important because the DCE provides the necessary clocking for the serial connection, and knowing which device serves this role is essential for proper configuration and hardware synchronization. Without this setup, the routers may not establish communication effectively as the clocking ensures timing alignment .

In configuring the back-to-back serial connection, IP addressing is crucial for enabling network layer communication between the routers. Each router's Serial0/0 interface needs a unique IP address within the same subnet to ensure they can reach each other. This setup is verified using the 'show ip interface brief' command, which checks the IP setup, ensuring it is manually configured and aligns with the network requirements. Verification is completed by successfully pinging from one router to the other's IP address, confirming connectivity and correct IP configuration .

Verifying the interface status and connectivity is critical to ensure that the configurations are correctly applied and that the routers can communicate over the established serial link. This step helps identify any misconfigurations or issues with the physical or logical setup, such as down interfaces or incorrect IP addresses. Successful verification, indicated by 'up' statuses and 100% ping success rates, confirms that the setup is properly functioning and the routers can exchange information without errors .

The DCE/DTE distinction is crucial as it determines which device provides the clocking needed for serial communication. In a back-to-back serial connection, the DCE interface provides clocking signals to the DTE to ensure synchronized data transmission. In this lab, R2 serves as the DCE and is responsible for providing a clock rate of 256 Kbps, while R1 is the DTE, receiving clock information to maintain the communication's timing integrity. This setting ensures that data flows smoothly between the two devices .

Clock rate is crucial in a back-to-back serial configuration as it dictates the timing of signal transmission between the routers for synchronized communication. In this lab scenario, the clock rate is set by the DCE device, which is R2, using the 'clock rate 256000' command to ensure R1, the DTE, receives consistent timing signals. This rate is implemented and confirmed through the 'show controllers serial' command, guaranteeing that the data transmission is correctly synchronized between the routers .

Achieving a 100% success rate in the ping command indicates that data packets sent between the routers are received without loss, demonstrating that the network layer is properly configured and routed. This success confirms the operational status of the serial connection and the accuracy of the IP addressing, reinforcing that the configuration steps have been implemented correctly, and the routers are able to communicate over the network as intended .

Configuring a back-to-back serial connection requires several steps: First, configure hostnames on the routers to easily identify them in commands and documentation. Second, enable the serial interfaces on both routers to establish communication with the command 'no shut', as interfaces are down by default. Third, identify which serial interface is the DCE (Data Communications Equipment) using the 'show controllers' command, as it will provide clocking; in this scenario, R2 is the DCE. The fourth step involves configuring the DCE to provide clocking (256 Kbps) using the 'clock rate' command, so the DTE (Data Terminal Equipment) on R1 can synchronize. Next, configure IP addressing on the serial interfaces, crucial for IP communication between the routers. Finally, verify the configuration by checking the interface status and pinging between the routers to ensure connectivity as shown by the success rate of ICMP packets .

If the clock rate is not configured correctly on a DCE interface, several issues can arise, including communication failures between the routers, data corruption, and inconsistent data flow. Incorrect clock rates lead to timing mismatches, causing synchronization problems where data might be sent or received too quickly for the associated DTE interface to handle correctly, resulting in data packet errors and degraded network performance .

You might also like