Troubleshooting Directly Connected Serial Interfaces
2007-09-02 22:35
411 查看
原文地址:http://www.myarticlemall.com/Article/Cisco-CCNA-Exam-Tutorial---Troubleshooting-Directly-Connected-Serial-Interfaces/2611
Controllers are the part of the interface that makes the physical connection.The
most important to us is what kind of cable is attathed to a Serial interface.
A DTE (data terminating equipment) cable is the normal cable you should use.
Being DTE means you expect the other end to providing clocking.
A DCE (data circuit-terminating equipment) means that this device must provide
the clocking on the wire.
The show controllers command will allow you to see if you are DCE or DTE.
A Cisco router is a DTE by default, but directly connecting two DTEs with a DCE/DTE cable is not enough. In the following example, R1 and R3 are directly connected at their Serial1 interfaces. The line goes up briefly after being opened, but the line protocol goes down after about 30 seconds.
R3(config-if)#int s1
R3(config-if)#ip address 172.12.13.3 255.255.255.0
R3(config-if)#no shutdown
2d18h: %LINK-3-UPDOWN: Interface Serial1, changed state to up
2d18h: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1, changed state to up
R3(config-if)#
2d18h: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1, changed state to down
The problem is that one of the routers needs to act as the DCE in order for the line protocol to come up and stay up. If this were your CCNA / CCNP home lab, you could just go over and look at the DTE/DCE cable to see which router had the DCE end of the cable attached. In this example, though, we don't have physical access to the routers. How can we tell which router has the DCE end of the cable attached?
R3#show controller serial 1
HD unit 1, idb = 0x1C44E8, driver structure at 0x1CBAC8
buffer size 1524 HD unit 1, V.35 DCE cable
The show controller command gives us this information. (There's a lot more output that this with this command, but it's unimportant for our purposes.) The router with the DCE end of the cable needs to supply a clock rate to the DTE, and we'll do just that with the interface-level clockrate command.
R3#conf t
Enter configuration commands, one per line. End with CNTL/Z.
R3(config)#int serial1
R3(config-if)#clockrate 56000
2d18h: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1, changed state to up
In just a few seconds, the line protocol goes up and stays up.
When troubleshooting a connection, always run show interface first. If you see the combination shown below, the connection is physically fine but logically down. That's generally the result of a needed keepalive not being present. With Frame Relay, it's probably an LMI issue, but with directly connected serial interfaces the issue is most likely the DCE end of the connection not supplying clockrate.
Controllers are the part of the interface that makes the physical connection.The
most important to us is what kind of cable is attathed to a Serial interface.
A DTE (data terminating equipment) cable is the normal cable you should use.
Being DTE means you expect the other end to providing clocking.
A DCE (data circuit-terminating equipment) means that this device must provide
the clocking on the wire.
The show controllers command will allow you to see if you are DCE or DTE.
A Cisco router is a DTE by default, but directly connecting two DTEs with a DCE/DTE cable is not enough. In the following example, R1 and R3 are directly connected at their Serial1 interfaces. The line goes up briefly after being opened, but the line protocol goes down after about 30 seconds.
R3(config-if)#int s1
R3(config-if)#ip address 172.12.13.3 255.255.255.0
R3(config-if)#no shutdown
2d18h: %LINK-3-UPDOWN: Interface Serial1, changed state to up
2d18h: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1, changed state to up
R3(config-if)#
2d18h: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1, changed state to down
The problem is that one of the routers needs to act as the DCE in order for the line protocol to come up and stay up. If this were your CCNA / CCNP home lab, you could just go over and look at the DTE/DCE cable to see which router had the DCE end of the cable attached. In this example, though, we don't have physical access to the routers. How can we tell which router has the DCE end of the cable attached?
R3#show controller serial 1
HD unit 1, idb = 0x1C44E8, driver structure at 0x1CBAC8
buffer size 1524 HD unit 1, V.35 DCE cable
The show controller command gives us this information. (There's a lot more output that this with this command, but it's unimportant for our purposes.) The router with the DCE end of the cable needs to supply a clock rate to the DTE, and we'll do just that with the interface-level clockrate command.
R3#conf t
Enter configuration commands, one per line. End with CNTL/Z.
R3(config)#int serial1
R3(config-if)#clockrate 56000
2d18h: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1, changed state to up
In just a few seconds, the line protocol goes up and stays up.
When troubleshooting a connection, always run show interface first. If you see the combination shown below, the connection is physically fine but logically down. That's generally the result of a needed keepalive not being present. With Frame Relay, it's probably an LMI issue, but with directly connected serial interfaces the issue is most likely the DCE end of the connection not supplying clockrate.
相关文章推荐
- Troubleshooting with serial consoles
- Linux TroubleShooting
- neutron trouble shooting - ip can not ping
- Troubleshooting Open Cursor Issues
- Troubleshooting a node by using the netapp SP
- Troubleshooting Guide for HotSpot VM
- Interlude: Troubleshooting for Failed to Declare Table-type Variables
- Trafodion Troubleshooting-server handle not available
- Troubleshooting OpenStack 瘫痪 - 每天5分钟玩转 OpenStack(160)
- spark troubleshooting--JVM GC导致的shuffle文件拉取失败
- Reactive Programming with RxJava-Chapter7:Test and Troubleshooting(1)
- Troubleshooting Scheduler Autotask Issues (Doc ID 1561498.1)
- Trafodion Troubleshooting - TrxRegionEndpoint cannot be loaded
- Unprocessed Shipping Transactions Troubleshooting Techniques (文档 ID 262979.1)
- Trafodion Troubleshooting-current onlineEpoch is less than new onlineEpoch
- Troubleshooting Failed Requests Using Tracing in IIS 8.5
- Group Replication GCS Troubleshooting
- Troubleshooting The Asset Workbench Form (FAXASSET) (文档 ID 784285.1)
- Troubleshooting Guide for TNS-12518 TNS listener could not hand off client connection (文档 ID 550859.
- windows pip install twisted troubleshooting