<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Two routers connected with a serial line, why they can ping each other without clock rate setting? in Routing and SD-WAN</title>
    <link>https://community.cisco.com/t5/routing-and-sd-wan/two-routers-connected-with-a-serial-line-why-they-can-ping-each/m-p/4287810#M346592</link>
    <description>&lt;P&gt;Hello &lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/1160434"&gt;@ew6DjDBNs48JaZYu3aiwaCrxvYfm2X&lt;/a&gt; ,&lt;/P&gt;
&lt;P&gt;your understanding is correct in real world with real cables , the DCE side of the cable can and must provide the clock rate.&lt;/P&gt;
&lt;P&gt;This can be checked usually with show controller serial x/y to see the cable type connected to the router interface.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;What you see in GNS3 is a known limitation of the emulation software that makes life a little easier then in real world.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Hope to help&lt;/P&gt;
&lt;P&gt;Giuseppe&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Mon, 08 Feb 2021 08:04:58 GMT</pubDate>
    <dc:creator>Giuseppe Larosa</dc:creator>
    <dc:date>2021-02-08T08:04:58Z</dc:date>
    <item>
      <title>Two routers connected with a serial line, why they can ping each other without clock rate setting?</title>
      <link>https://community.cisco.com/t5/routing-and-sd-wan/two-routers-connected-with-a-serial-line-why-they-can-ping-each/m-p/4287681#M346572</link>
      <description>&lt;P&gt;I'm pretty new to networking and still learning CCNA stuff. I'm reading a book and as I understand, when you are connecting two routers using a serial line, one router is considered DCE and the other is DTE. The DCE side should set clock rate in order to make them communicate successfully. Is my understanding correct? I did some test in gns3 and it seems my understanding is wrong. Below is the topology I have.&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="WDj3L" style="width: 292px;"&gt;&lt;img src="https://community.cisco.com/t5/image/serverpage/image-id/103888iC2251EE17B72D442/image-size/large?v=v2&amp;amp;px=999" role="button" title="WDj3L" alt="WDj3L" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;This is the configuration for R1.&lt;/P&gt;&lt;PRE&gt;R1#sh run | s interface Serial2/0
interface Serial2/0
ip address 192.168.1.1 255.255.255.0
serial restart-delay 0
R1#&lt;/PRE&gt;&lt;P&gt;This is the configuration for R2.&lt;/P&gt;&lt;PRE&gt;R2#sh run | s interface Serial2/0
interface Serial2/0
ip address 192.168.1.2 255.255.255.0
serial restart-delay 0
R2#&lt;/PRE&gt;&lt;P&gt;As you can see, I haven't set clock rate for both of them. But I can successfully ping from both ends.&lt;/P&gt;&lt;PRE&gt;R1#ping 192.168.1.2
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.1.2, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 8/17/36 ms
R1#&lt;/PRE&gt;&lt;PRE&gt;R2#ping 192.168.1.1
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.1.1, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 4/13/32 ms
R2#p&lt;/PRE&gt;&lt;P&gt;Is there anything wrong with my understanding or my testing?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 08 Feb 2021 01:20:55 GMT</pubDate>
      <guid>https://community.cisco.com/t5/routing-and-sd-wan/two-routers-connected-with-a-serial-line-why-they-can-ping-each/m-p/4287681#M346572</guid>
      <dc:creator>ew6DjDBNs48JaZYu3aiwaCrxvYfm2X</dc:creator>
      <dc:date>2021-02-08T01:20:55Z</dc:date>
    </item>
    <item>
      <title>Re: Two routers connected with a serial line, why they can ping each other without clock rate setting?</title>
      <link>https://community.cisco.com/t5/routing-and-sd-wan/two-routers-connected-with-a-serial-line-why-they-can-ping-each/m-p/4287810#M346592</link>
      <description>&lt;P&gt;Hello &lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/1160434"&gt;@ew6DjDBNs48JaZYu3aiwaCrxvYfm2X&lt;/a&gt; ,&lt;/P&gt;
&lt;P&gt;your understanding is correct in real world with real cables , the DCE side of the cable can and must provide the clock rate.&lt;/P&gt;
&lt;P&gt;This can be checked usually with show controller serial x/y to see the cable type connected to the router interface.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;What you see in GNS3 is a known limitation of the emulation software that makes life a little easier then in real world.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Hope to help&lt;/P&gt;
&lt;P&gt;Giuseppe&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 08 Feb 2021 08:04:58 GMT</pubDate>
      <guid>https://community.cisco.com/t5/routing-and-sd-wan/two-routers-connected-with-a-serial-line-why-they-can-ping-each/m-p/4287810#M346592</guid>
      <dc:creator>Giuseppe Larosa</dc:creator>
      <dc:date>2021-02-08T08:04:58Z</dc:date>
    </item>
    <item>
      <title>Re: Two routers connected with a serial line, why they can ping each other without clock rate setting?</title>
      <link>https://community.cisco.com/t5/routing-and-sd-wan/two-routers-connected-with-a-serial-line-why-they-can-ping-each/m-p/4287833#M346599</link>
      <description>&lt;P&gt;Thanks for the clarification. In real world with real cables, if I remove clock rate on the current DCE end and enable it on the current DTE end, will the connection still work as expected?&lt;/P&gt;</description>
      <pubDate>Mon, 08 Feb 2021 09:08:58 GMT</pubDate>
      <guid>https://community.cisco.com/t5/routing-and-sd-wan/two-routers-connected-with-a-serial-line-why-they-can-ping-each/m-p/4287833#M346599</guid>
      <dc:creator>ew6DjDBNs48JaZYu3aiwaCrxvYfm2X</dc:creator>
      <dc:date>2021-02-08T09:08:58Z</dc:date>
    </item>
    <item>
      <title>Re: Two routers connected with a serial line, why they can ping each other without clock rate setting?</title>
      <link>https://community.cisco.com/t5/routing-and-sd-wan/two-routers-connected-with-a-serial-line-why-they-can-ping-each/m-p/4287851#M346603</link>
      <description>&lt;P&gt;Hello &lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/1160434"&gt;@ew6DjDBNs48JaZYu3aiwaCrxvYfm2X&lt;/a&gt; ,&lt;/P&gt;
&lt;P&gt;no in real world the clock rate command is accepted only on the DCE side, if you try to give it on the DTE side you should get an error message.&lt;/P&gt;
&lt;P&gt;This is the reason why we need to check what type of cable is actually connected to the interface.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Hope to help&lt;/P&gt;
&lt;P&gt;Giuseppe&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 08 Feb 2021 09:43:50 GMT</pubDate>
      <guid>https://community.cisco.com/t5/routing-and-sd-wan/two-routers-connected-with-a-serial-line-why-they-can-ping-each/m-p/4287851#M346603</guid>
      <dc:creator>Giuseppe Larosa</dc:creator>
      <dc:date>2021-02-08T09:43:50Z</dc:date>
    </item>
    <item>
      <title>Re: Two routers connected with a serial line, why they can ping each other without clock rate setting?</title>
      <link>https://community.cisco.com/t5/routing-and-sd-wan/two-routers-connected-with-a-serial-line-why-they-can-ping-each/m-p/4287858#M346604</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;it won't work. The clock has to be configured on the DCE end. I don't think you can even use the clock rate command on a DTE end, it will generate an error message.&lt;/P&gt;</description>
      <pubDate>Mon, 08 Feb 2021 09:54:53 GMT</pubDate>
      <guid>https://community.cisco.com/t5/routing-and-sd-wan/two-routers-connected-with-a-serial-line-why-they-can-ping-each/m-p/4287858#M346604</guid>
      <dc:creator>Georg Pauwen</dc:creator>
      <dc:date>2021-02-08T09:54:53Z</dc:date>
    </item>
  </channel>
</rss>

