<?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 What is &amp;quot;correct time&amp;quot; that in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/ntp-in-asa-cannot-work/m-p/2735255#M193001</link>
    <description>&lt;P&gt;What is "correct time" that you mentioned ? You mean the same&amp;nbsp;time with other device ? If it does not have correct time, the certificate process can work ? Thank you&amp;nbsp;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Mon, 10 Aug 2015 13:33:05 GMT</pubDate>
    <dc:creator>eigrpy</dc:creator>
    <dc:date>2015-08-10T13:33:05Z</dc:date>
    <item>
      <title>NTP in ASA cannot work</title>
      <link>https://community.cisco.com/t5/network-security/ntp-in-asa-cannot-work/m-p/2735249#M192995</link>
      <description>&lt;P&gt;Hi Anyone can take a the commands. Why NTP in ASA cannot work ? Thank you&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;ASA1(config)# sh run ntp &amp;nbsp;&lt;BR /&gt;ntp server 12.1.1.1 source outside&lt;BR /&gt;ASA1(config)#&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;ASA1(config)# sh ntp statu&lt;BR /&gt;Clock is &lt;STRONG&gt;unsynchronized,&lt;/STRONG&gt; stratum 16, no reference clock&lt;BR /&gt;nominal freq is 99.9984 Hz, actual freq is 99.9984 Hz, precision is 2**6&lt;BR /&gt;reference time is 00000000.00000000 (00:24:16.000 EST Thu Feb 7 2036)&lt;BR /&gt;clock offset is 0.0000 msec, root delay is 0.00 msec&lt;BR /&gt;root dispersion is 0.00 msec, peer dispersion is 0.00 msec&lt;BR /&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;ASA1(config)# sh int ip bri&lt;BR /&gt;Interface &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;IP-Address &amp;nbsp; &amp;nbsp; &amp;nbsp;OK? Method Status &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;Protocol&lt;BR /&gt;Ethernet0/0 &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;unassigned &amp;nbsp; &amp;nbsp; &amp;nbsp;YES unset &amp;nbsp;up &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;up &amp;nbsp;&lt;BR /&gt;Ethernet0/1 &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;unassigned &amp;nbsp; &amp;nbsp; &amp;nbsp;YES unset &amp;nbsp;down &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;down&lt;BR /&gt;Internal-Data0/0 &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; unassigned &amp;nbsp; &amp;nbsp; &amp;nbsp;YES unset &amp;nbsp;up &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;up &amp;nbsp;&lt;BR /&gt;Internal-Data0/1 &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; unassigned &amp;nbsp; &amp;nbsp; &amp;nbsp;YES unset &amp;nbsp;up &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;up &amp;nbsp;&lt;BR /&gt;Vlan1 &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;10.1.1.1 &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;YES manual down &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;down&lt;BR /&gt;Vlan2 &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;12.1.1.1 &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;YES manual up &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;up &amp;nbsp;&lt;BR /&gt;Virtual0 &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; 127.0.0.1 &amp;nbsp; &amp;nbsp; &amp;nbsp; YES unset &amp;nbsp;up &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;up &amp;nbsp;&lt;BR /&gt;ASA1(config)#&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 12 Mar 2019 06:24:02 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ntp-in-asa-cannot-work/m-p/2735249#M192995</guid>
      <dc:creator>eigrpy</dc:creator>
      <dc:date>2019-03-12T06:24:02Z</dc:date>
    </item>
    <item>
      <title>The command is ok, you even</title>
      <link>https://community.cisco.com/t5/network-security/ntp-in-asa-cannot-work/m-p/2735250#M192996</link>
      <description>&lt;P&gt;The command is ok, you even don't need the "source outside". But you have to use the IP address of a public NTP-server like&amp;nbsp;198.24.147.90 (which is&amp;nbsp;3.north-america.pool.ntp.org) and not your ASA IP address.&lt;/P&gt;</description>
      <pubDate>Sat, 08 Aug 2015 22:14:20 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ntp-in-asa-cannot-work/m-p/2735250#M192996</guid>
      <dc:creator>Karsten Iwen</dc:creator>
      <dc:date>2015-08-08T22:14:20Z</dc:date>
    </item>
    <item>
      <title>Thank you so much for your</title>
      <link>https://community.cisco.com/t5/network-security/ntp-in-asa-cannot-work/m-p/2735251#M192997</link>
      <description>&lt;P&gt;Thank you so much for your reply.&amp;nbsp;&lt;/P&gt;&lt;P&gt;With router, we can setup ntp the router itself without other connection to other device. So you mean ASA is different with router ios in ntp, right ? and ASA cannot have its own ntp system ? The ASA that I am talking about is ASA5505&lt;/P&gt;</description>
      <pubDate>Sat, 08 Aug 2015 22:48:26 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ntp-in-asa-cannot-work/m-p/2735251#M192997</guid>
      <dc:creator>eigrpy</dc:creator>
      <dc:date>2015-08-08T22:48:26Z</dc:date>
    </item>
    <item>
      <title>You want to configure the ASA</title>
      <link>https://community.cisco.com/t5/network-security/ntp-in-asa-cannot-work/m-p/2735252#M192998</link>
      <description>&lt;P&gt;You want to configure the ASA to be an NTP-server for other network-devices? No, that's not possible on the ASA. The ASA only has an NTP-client, not an NTP-server as IOS-routers and switches have.&lt;/P&gt;</description>
      <pubDate>Sun, 09 Aug 2015 00:02:04 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ntp-in-asa-cannot-work/m-p/2735252#M192998</guid>
      <dc:creator>Karsten Iwen</dc:creator>
      <dc:date>2015-08-09T00:02:04Z</dc:date>
    </item>
    <item>
      <title>In lab environment, we can</title>
      <link>https://community.cisco.com/t5/network-security/ntp-in-asa-cannot-work/m-p/2735253#M192999</link>
      <description>&lt;P&gt;In lab environment, we can set ASA as ntp client without public ip address, right ?&amp;nbsp;&lt;/P&gt;&lt;P&gt;Sometimes&amp;nbsp;we set&amp;nbsp;NTP for certificate in ASA. So the ntp is not required for the certificate in ASA ? Thank you&lt;/P&gt;</description>
      <pubDate>Sun, 09 Aug 2015 00:47:12 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ntp-in-asa-cannot-work/m-p/2735253#M192999</guid>
      <dc:creator>eigrpy</dc:creator>
      <dc:date>2015-08-09T00:47:12Z</dc:date>
    </item>
    <item>
      <title>When you use the NTP-client,</title>
      <link>https://community.cisco.com/t5/network-security/ntp-in-asa-cannot-work/m-p/2735254#M193000</link>
      <description>&lt;P&gt;When you use the NTP-client, you point the ASA to the IP address of an NTP server. That can be a public or a private address. Very often the switched infrastructure is used as the NTP-server.&lt;/P&gt;&lt;P&gt;You can use the ASA also with certificates without NTP. You only should have a correct time. And using NTP is the easiest way and a best-practice&amp;nbsp;to achieve that.&lt;/P&gt;</description>
      <pubDate>Sun, 09 Aug 2015 08:21:53 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ntp-in-asa-cannot-work/m-p/2735254#M193000</guid>
      <dc:creator>Karsten Iwen</dc:creator>
      <dc:date>2015-08-09T08:21:53Z</dc:date>
    </item>
    <item>
      <title>What is "correct time" that</title>
      <link>https://community.cisco.com/t5/network-security/ntp-in-asa-cannot-work/m-p/2735255#M193001</link>
      <description>&lt;P&gt;What is "correct time" that you mentioned ? You mean the same&amp;nbsp;time with other device ? If it does not have correct time, the certificate process can work ? Thank you&amp;nbsp;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 10 Aug 2015 13:33:05 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ntp-in-asa-cannot-work/m-p/2735255#M193001</guid>
      <dc:creator>eigrpy</dc:creator>
      <dc:date>2015-08-10T13:33:05Z</dc:date>
    </item>
    <item>
      <title>The definition of "correct</title>
      <link>https://community.cisco.com/t5/network-security/ntp-in-asa-cannot-work/m-p/2735256#M193002</link>
      <description>&lt;P&gt;The definition of "correct time" can depend on what you want to achieve. For certificate-based authentication, the ASA-time has to be within the validity period of the certificate. For that, even when the time is minutes or even hours wrong, it could work.&lt;/P&gt;&lt;P&gt;For logging it's different. There you want to correlate exactly with other sources of information what happened. There you need a very exact time.&lt;/P&gt;&lt;P&gt;All in all, there are enough time-sources that you can use for NTP. If you have one internally, take that. If not, take on on the internet.&lt;/P&gt;</description>
      <pubDate>Mon, 10 Aug 2015 14:19:59 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ntp-in-asa-cannot-work/m-p/2735256#M193002</guid>
      <dc:creator>Karsten Iwen</dc:creator>
      <dc:date>2015-08-10T14:19:59Z</dc:date>
    </item>
    <item>
      <title>Excellent, Thank you!</title>
      <link>https://community.cisco.com/t5/network-security/ntp-in-asa-cannot-work/m-p/2735257#M193003</link>
      <description>&lt;P&gt;Excellent,&amp;nbsp;Thank you!&lt;/P&gt;</description>
      <pubDate>Mon, 10 Aug 2015 14:22:58 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ntp-in-asa-cannot-work/m-p/2735257#M193003</guid>
      <dc:creator>eigrpy</dc:creator>
      <dc:date>2015-08-10T14:22:58Z</dc:date>
    </item>
    <item>
      <title>I try and setup NTP as</title>
      <link>https://community.cisco.com/t5/network-security/ntp-in-asa-cannot-work/m-p/2735258#M193004</link>
      <description>&lt;P&gt;I try and setup NTP as follows.&lt;/P&gt;&lt;P&gt;I point the Domain Controller out to a pool of NTP servers on the internet.&lt;/P&gt;&lt;P&gt;I then point the Core switch to the Domain Controller for its time.&lt;/P&gt;&lt;P&gt;Then I point all the IDF switches and the ASA to the core switch for NTP.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Mike&lt;/P&gt;</description>
      <pubDate>Mon, 10 Aug 2015 15:09:44 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ntp-in-asa-cannot-work/m-p/2735258#M193004</guid>
      <dc:creator>burleyman</dc:creator>
      <dc:date>2015-08-10T15:09:44Z</dc:date>
    </item>
  </channel>
</rss>

