<?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: NTP Sync Failure CISCO ISE in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/ntp-sync-failure-cisco-ise/m-p/2075843#M921086</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;We are having the same issue. What's worst: The error is reported as &lt;STRONG&gt;CRITICAL &lt;/STRONG&gt;and the description says that "&lt;STRONG&gt;No &lt;/STRONG&gt;NTP Server reachable" (or that "&lt;STRONG&gt;All &lt;/STRONG&gt;of the NTP Servers configured on this node are unreachable") and this is clearly wrong.&lt;/P&gt;&lt;P&gt;Running "sho ntp" about one hour after the error message clearly shows that only &lt;EM&gt;one out of three&lt;/EM&gt; configured redundant ntp sources had a &lt;EM&gt;temporary &lt;/EM&gt;problem:&lt;/P&gt;&lt;PRE&gt;Configured NTP Servers: 
&amp;nbsp; 10.0.1.119
&amp;nbsp; pool.ntp.org
&amp;nbsp; de.pool.ntp.org

synchronised to NTP server (91.64.203.19) at stratum 2 
&amp;nbsp;&amp;nbsp; time correct to within 54 ms
&amp;nbsp;&amp;nbsp; polling server every 1024 s

&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; remote&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; refid&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; st t when poll reach&amp;nbsp;&amp;nbsp; delay&amp;nbsp;&amp;nbsp; offset&amp;nbsp; jitter
==============================================================================
 127.127.1.0&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; .LOCL.&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 10 l&amp;nbsp;&amp;nbsp; 27&amp;nbsp;&amp;nbsp; 64&amp;nbsp; 377&amp;nbsp;&amp;nbsp;&amp;nbsp; 0.000&amp;nbsp;&amp;nbsp;&amp;nbsp; 0.000&amp;nbsp;&amp;nbsp; 0.001
+10.0.1.119&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 217.79.179.106&amp;nbsp;&amp;nbsp; 3 u&amp;nbsp; 224 1024&amp;nbsp; 367&amp;nbsp;&amp;nbsp;&amp;nbsp; 0.234&amp;nbsp; -27.926&amp;nbsp;&amp;nbsp; 6.174
+89.163.176.81&amp;nbsp;&amp;nbsp; 178.63.97.57&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 3 u&amp;nbsp;&amp;nbsp; 95 1024&amp;nbsp; 377&amp;nbsp;&amp;nbsp; 10.224&amp;nbsp;&amp;nbsp; -4.777&amp;nbsp;&amp;nbsp; 0.533
*91.64.203.19&amp;nbsp;&amp;nbsp;&amp;nbsp; .PPS.&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 1 u&amp;nbsp; 348 1024&amp;nbsp; 377&amp;nbsp;&amp;nbsp; 29.527&amp;nbsp;&amp;nbsp;&amp;nbsp; 0.121&amp;nbsp;&amp;nbsp; 3.608

* Current time source, + Candidate 

Warning: Output results may conflict during periods of changing synchronization.
&lt;/PRE&gt;&lt;P&gt;Given that non-reachability of single hosts is something the ntp protocol is specifically &lt;EM&gt;designed &lt;/EM&gt;for, issuing a "critical" message in a far-from-critical situation (it's not even an "error", it should be at most a "warning" I guess) is very annoying.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 26 Sep 2013 12:17:20 GMT</pubDate>
    <dc:creator>Andreas Hoffmann</dc:creator>
    <dc:date>2013-09-26T12:17:20Z</dc:date>
    <item>
      <title>NTP Sync Failure CISCO ISE</title>
      <link>https://community.cisco.com/t5/network-security/ntp-sync-failure-cisco-ise/m-p/2075840#M921083</link>
      <description>&lt;P&gt;hello guys,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'm having problems with the cisco ise in my company.&lt;/P&gt;&lt;P&gt;every day is got the following error:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cause:&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; No NTP Server reachable from SPCISE01&lt;/P&gt;&lt;P&gt;Details:&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; All of the NTP Servers configured on this node are unreachable. If NTP authentication is configured ensure that key ID and value match that of the server. Execute 'show ntp' from CLI for troubleshooting.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;admin# show ntp&lt;/P&gt;&lt;P&gt;Configured NTP Servers:&lt;/P&gt;&lt;P&gt;&amp;nbsp; 10.0.4.6&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;synchronised to NTP server (10.0.4.6) at stratum 7&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; time correct to within 556 ms&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; polling server every 256 s&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; remote&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; refid&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; st t when poll reach&amp;nbsp;&amp;nbsp; delay&amp;nbsp;&amp;nbsp; offset&amp;nbsp; jitter&lt;/P&gt;&lt;P&gt;==============================================================================&lt;/P&gt;&lt;P&gt; 127.127.1.0&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; .LOCL.&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 10 l&amp;nbsp;&amp;nbsp; 49&amp;nbsp;&amp;nbsp; 64&amp;nbsp; 377&amp;nbsp;&amp;nbsp;&amp;nbsp; 0.000&amp;nbsp;&amp;nbsp;&amp;nbsp; 0.000&amp;nbsp;&amp;nbsp; 0.001&lt;/P&gt;&lt;P&gt;*10.0.4.6&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 10.0.4.4&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 6 u&amp;nbsp;&amp;nbsp;&amp;nbsp; 1&amp;nbsp; 256&amp;nbsp; 377&amp;nbsp;&amp;nbsp;&amp;nbsp; 2.133&amp;nbsp;&amp;nbsp;&amp;nbsp; 6.875&amp;nbsp;&amp;nbsp; 8.734&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;* Current time source, + Candidate&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Warning: Output results may conflict during periods of changing synchronization.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;how can I force the sync ntp in ise?&lt;/P&gt;</description>
      <pubDate>Fri, 21 Feb 2020 12:46:51 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ntp-sync-failure-cisco-ise/m-p/2075840#M921083</guid>
      <dc:creator>tmarques87</dc:creator>
      <dc:date>2020-02-21T12:46:51Z</dc:date>
    </item>
    <item>
      <title>NTP Sync Failure CISCO ISE</title>
      <link>https://community.cisco.com/t5/network-security/ntp-sync-failure-cisco-ise/m-p/2075841#M921084</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;We are having the same problem, have you managed to find any solution for this issue?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 24 Jan 2013 15:08:03 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ntp-sync-failure-cisco-ise/m-p/2075841#M921084</guid>
      <dc:creator>venkata dandu</dc:creator>
      <dc:date>2013-01-24T15:08:03Z</dc:date>
    </item>
    <item>
      <title>NTP Sync Failure CISCO ISE</title>
      <link>https://community.cisco.com/t5/network-security/ntp-sync-failure-cisco-ise/m-p/2075842#M921085</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt; I am also having this issue.&amp;nbsp; Every 15 minutes I get alarms.&amp;nbsp; Tried differnt NTp servers 0 AD, external, etc.. with no luck.&amp;nbsp; I am hoping someone has made progress in resolving this issue.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 29 Jul 2013 18:03:12 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ntp-sync-failure-cisco-ise/m-p/2075842#M921085</guid>
      <dc:creator>Michael.Bienkowski</dc:creator>
      <dc:date>2013-07-29T18:03:12Z</dc:date>
    </item>
    <item>
      <title>Re: NTP Sync Failure CISCO ISE</title>
      <link>https://community.cisco.com/t5/network-security/ntp-sync-failure-cisco-ise/m-p/2075843#M921086</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;We are having the same issue. What's worst: The error is reported as &lt;STRONG&gt;CRITICAL &lt;/STRONG&gt;and the description says that "&lt;STRONG&gt;No &lt;/STRONG&gt;NTP Server reachable" (or that "&lt;STRONG&gt;All &lt;/STRONG&gt;of the NTP Servers configured on this node are unreachable") and this is clearly wrong.&lt;/P&gt;&lt;P&gt;Running "sho ntp" about one hour after the error message clearly shows that only &lt;EM&gt;one out of three&lt;/EM&gt; configured redundant ntp sources had a &lt;EM&gt;temporary &lt;/EM&gt;problem:&lt;/P&gt;&lt;PRE&gt;Configured NTP Servers: 
&amp;nbsp; 10.0.1.119
&amp;nbsp; pool.ntp.org
&amp;nbsp; de.pool.ntp.org

synchronised to NTP server (91.64.203.19) at stratum 2 
&amp;nbsp;&amp;nbsp; time correct to within 54 ms
&amp;nbsp;&amp;nbsp; polling server every 1024 s

&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; remote&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; refid&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; st t when poll reach&amp;nbsp;&amp;nbsp; delay&amp;nbsp;&amp;nbsp; offset&amp;nbsp; jitter
==============================================================================
 127.127.1.0&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; .LOCL.&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 10 l&amp;nbsp;&amp;nbsp; 27&amp;nbsp;&amp;nbsp; 64&amp;nbsp; 377&amp;nbsp;&amp;nbsp;&amp;nbsp; 0.000&amp;nbsp;&amp;nbsp;&amp;nbsp; 0.000&amp;nbsp;&amp;nbsp; 0.001
+10.0.1.119&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 217.79.179.106&amp;nbsp;&amp;nbsp; 3 u&amp;nbsp; 224 1024&amp;nbsp; 367&amp;nbsp;&amp;nbsp;&amp;nbsp; 0.234&amp;nbsp; -27.926&amp;nbsp;&amp;nbsp; 6.174
+89.163.176.81&amp;nbsp;&amp;nbsp; 178.63.97.57&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 3 u&amp;nbsp;&amp;nbsp; 95 1024&amp;nbsp; 377&amp;nbsp;&amp;nbsp; 10.224&amp;nbsp;&amp;nbsp; -4.777&amp;nbsp;&amp;nbsp; 0.533
*91.64.203.19&amp;nbsp;&amp;nbsp;&amp;nbsp; .PPS.&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 1 u&amp;nbsp; 348 1024&amp;nbsp; 377&amp;nbsp;&amp;nbsp; 29.527&amp;nbsp;&amp;nbsp;&amp;nbsp; 0.121&amp;nbsp;&amp;nbsp; 3.608

* Current time source, + Candidate 

Warning: Output results may conflict during periods of changing synchronization.
&lt;/PRE&gt;&lt;P&gt;Given that non-reachability of single hosts is something the ntp protocol is specifically &lt;EM&gt;designed &lt;/EM&gt;for, issuing a "critical" message in a far-from-critical situation (it's not even an "error", it should be at most a "warning" I guess) is very annoying.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 26 Sep 2013 12:17:20 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ntp-sync-failure-cisco-ise/m-p/2075843#M921086</guid>
      <dc:creator>Andreas Hoffmann</dc:creator>
      <dc:date>2013-09-26T12:17:20Z</dc:date>
    </item>
    <item>
      <title>Re: NTP Sync Failure CISCO ISE</title>
      <link>https://community.cisco.com/t5/network-security/ntp-sync-failure-cisco-ise/m-p/2075844#M921087</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt; Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I resolved this issue by setting up NTP on our core switch 6513 and pointing ISE towards that.&amp;nbsp; We got the same errors you are seeing when using an AD server for NTP.&amp;nbsp; Since moving I have not gotten any NTP errors.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 26 Sep 2013 12:54:14 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ntp-sync-failure-cisco-ise/m-p/2075844#M921087</guid>
      <dc:creator>Michael.Bienkowski</dc:creator>
      <dc:date>2013-09-26T12:54:14Z</dc:date>
    </item>
  </channel>
</rss>

