What could be the problem?

Refer to the exhibit. An administrator cannot connect from R1 to R2. To troubleshoot this problem, the administrator has entered the command shown in the exhibit. Based on the output shown, what could be the problem?


A. The serial interface is configured for half duplex.
B. The serial interface does not have a cable attached.
C. The serial interface has the wrong type of cable attached.
D. The serial interface is configured for the wrong frame size.
E. The serial interface has a full buffer.


2 thoughts on “What could be the problem?

  1. A Cisco serial interface is operating as a DTE by default. The problem is that when you take a cable and connect two routers directly by their serial interfaces (with a DTE/DCE cable, that is!), they’re both waiting for the other to send them a clock rate. One of the interfaces must act as the DCE and that interface must send the clock rate.
    If you can see the DTE/DCE cable, you can tell by looking which router has the DCE interface connected to it – the letters “DTE” or “DCE” will either be molded into the connector itself, or if it’s an older cable there should be a little piece of tape on the cable that tells you what the interface type is. But what if you have no access to the cable, or there are other cables all around it and you can’t see what type it is?
    Run the command “show controller serial x”, with x representing the interface number the cable’s connected to. There will be quite a bit of output from this command, but the information you need is right at the top:
    R1#show controller serial 1
    HD unit 1, idb = 0x1DBFEC, driver structure at 0x1E35D0
    buffer size 1524 HD unit 1, V.35 DTE cable

    It means we dont need to configure Clock on router1 and its not identify hier, also we need have ” V.35 DTE cable” in output.

Leave a Reply

Your email address will not be published.

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.