<?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: Longer RTT consequences in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/longer-rtt-consequences/m-p/3569025#M520164</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Database replication issues may result. Its not recommended or supported to deploy separation of PSN from PAN/MNT more than this value. Please consider moving the PSN closer to PAN/MNT, if this is not possible due to concerns with WAN survivability then may need separate ISE deployments.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 06 Nov 2017 15:58:13 GMT</pubDate>
    <dc:creator>Jason Kunst</dc:creator>
    <dc:date>2017-11-06T15:58:13Z</dc:date>
    <item>
      <title>Longer RTT consequences</title>
      <link>https://community.cisco.com/t5/network-access-control/longer-rtt-consequences/m-p/3569024#M520163</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P style="font-size: 13.3333px;"&gt;&lt;SPAN style="color: #333333;"&gt;Hi Team, &lt;/SPAN&gt;&lt;/P&gt;&lt;P style="font-size: 13.3333px;"&gt;&lt;SPAN style="font-size: 10pt; color: #333333;"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P style="font-size: 13.3333px;"&gt;&lt;SPAN style="color: #333333;"&gt;&lt;SPAN style="font-size: 10pt;"&gt; Could you please explain &lt;/SPAN&gt;&lt;SPAN style="font-size: 11pt; font-family: Calibri, sans-serif;"&gt;how the PSNs will react if the roundtrip delay between a PSN and PAN/MNT is more than 300ms?&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P style="font-size: 13.3333px;"&gt;&lt;SPAN style="font-size: 11pt; font-family: Calibri, sans-serif; color: #333333;"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P style="font-size: 13.3333px;"&gt;&lt;SPAN style="font-size: 11pt; font-family: Calibri, sans-serif; color: #333333;"&gt;Thank you!&lt;/SPAN&gt;&lt;/P&gt;&lt;P style="font-size: 13.3333px;"&gt;&lt;SPAN style="font-size: 11pt; font-family: Calibri, sans-serif; color: #333333;"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P style="font-size: 13.3333px;"&gt;&lt;SPAN style="font-size: 11pt; font-family: Calibri, sans-serif; color: #333333;"&gt;Best regards,&lt;/SPAN&gt;&lt;/P&gt;&lt;P style="font-size: 13.3333px;"&gt;&lt;SPAN style="color: #333333; font-size: 11.0pt; font-family: 'Calibri',sans-serif;"&gt;Gyorgy&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 06 Nov 2017 09:55:47 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/longer-rtt-consequences/m-p/3569024#M520163</guid>
      <dc:creator>gacs</dc:creator>
      <dc:date>2017-11-06T09:55:47Z</dc:date>
    </item>
    <item>
      <title>Re: Longer RTT consequences</title>
      <link>https://community.cisco.com/t5/network-access-control/longer-rtt-consequences/m-p/3569025#M520164</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Database replication issues may result. Its not recommended or supported to deploy separation of PSN from PAN/MNT more than this value. Please consider moving the PSN closer to PAN/MNT, if this is not possible due to concerns with WAN survivability then may need separate ISE deployments.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 06 Nov 2017 15:58:13 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/longer-rtt-consequences/m-p/3569025#M520164</guid>
      <dc:creator>Jason Kunst</dc:creator>
      <dc:date>2017-11-06T15:58:13Z</dc:date>
    </item>
  </channel>
</rss>

