<?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: ISE Node Latency Alarms in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/ise-node-latency-alarms/m-p/3557477#M535842</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Not directly. There could be other causes for slow replication.&lt;/P&gt;&lt;P&gt;They are triggered based on for how long an ISE node not consuming replicated messages.&lt;/P&gt;&lt;P&gt;60150 -- INFO: &amp;gt; 60 minutes but &amp;lt;= 180 minutes&lt;/P&gt;&lt;P&gt;60151 -- WARN: &amp;gt; 180 minutes but &amp;lt;= 300 minutes&amp;nbsp; &lt;/P&gt;&lt;P&gt;60152 -- ERROR: &amp;gt; 300 minutes&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 16 May 2017 04:44:24 GMT</pubDate>
    <dc:creator>hslai</dc:creator>
    <dc:date>2017-05-16T04:44:24Z</dc:date>
    <item>
      <title>ISE Node Latency Alarms</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-node-latency-alarms/m-p/3557476#M535841</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The guidance for ISE 2.1+ is to keep latency between nodes lower than 300ms for optimal performance.&amp;nbsp; Is it true that the following ISE alarms pertain to that threshold?&amp;nbsp; If so, what are their trigger points exactly and what is the difference between these 3 messages?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thank you!&lt;/P&gt;&lt;P&gt;&lt;IMG alt="Capture.PNG" class="image-1 jive-image" height="54" src="https://community.cisco.com/legacyfs/online/fusion/107232_Capture.PNG" style="height: 54px; width: 1070.47px;" width="1070" /&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 15 May 2017 22:04:39 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-node-latency-alarms/m-p/3557476#M535841</guid>
      <dc:creator>jofische</dc:creator>
      <dc:date>2017-05-15T22:04:39Z</dc:date>
    </item>
    <item>
      <title>Re: ISE Node Latency Alarms</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-node-latency-alarms/m-p/3557477#M535842</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Not directly. There could be other causes for slow replication.&lt;/P&gt;&lt;P&gt;They are triggered based on for how long an ISE node not consuming replicated messages.&lt;/P&gt;&lt;P&gt;60150 -- INFO: &amp;gt; 60 minutes but &amp;lt;= 180 minutes&lt;/P&gt;&lt;P&gt;60151 -- WARN: &amp;gt; 180 minutes but &amp;lt;= 300 minutes&amp;nbsp; &lt;/P&gt;&lt;P&gt;60152 -- ERROR: &amp;gt; 300 minutes&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 16 May 2017 04:44:24 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-node-latency-alarms/m-p/3557477#M535842</guid>
      <dc:creator>hslai</dc:creator>
      <dc:date>2017-05-16T04:44:24Z</dc:date>
    </item>
    <item>
      <title>Re: ISE Node Latency Alarms</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-node-latency-alarms/m-p/3557478#M535843</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thank you!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Does a more suitable alarm message exist to monitor for latency between the nodes themselves?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 16 May 2017 14:21:31 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-node-latency-alarms/m-p/3557478#M535843</guid>
      <dc:creator>jofische</dc:creator>
      <dc:date>2017-05-16T14:21:31Z</dc:date>
    </item>
  </channel>
</rss>

