<?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 ISE 2.3 - Temporal agent issue in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/ise-2-3-temporal-agent-issue/m-p/3684976#M508408</link>
    <description>&lt;P&gt;HI&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;We are working with ISE 2.3 and Posture to guest clients using cisco temporal agent, but when we download and run the temporal agent we got the following error "Failed to contact policy server"&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Does anybody know how to resolve this issue ?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="1.PNG" style="width: 753px;"&gt;&lt;img src="https://community.cisco.com/t5/image/serverpage/image-id/16477i4388F2A3EE9C5546/image-size/large?v=v2&amp;amp;px=999" role="button" title="1.PNG" alt="1.PNG" /&gt;&lt;/span&gt;&lt;/P&gt;</description>
    <pubDate>Thu, 09 Aug 2018 14:13:47 GMT</pubDate>
    <dc:creator>dhanushka_</dc:creator>
    <dc:date>2018-08-09T14:13:47Z</dc:date>
    <item>
      <title>ISE 2.3 - Temporal agent issue</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-2-3-temporal-agent-issue/m-p/3684976#M508408</link>
      <description>&lt;P&gt;HI&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;We are working with ISE 2.3 and Posture to guest clients using cisco temporal agent, but when we download and run the temporal agent we got the following error "Failed to contact policy server"&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Does anybody know how to resolve this issue ?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="1.PNG" style="width: 753px;"&gt;&lt;img src="https://community.cisco.com/t5/image/serverpage/image-id/16477i4388F2A3EE9C5546/image-size/large?v=v2&amp;amp;px=999" role="button" title="1.PNG" alt="1.PNG" /&gt;&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 09 Aug 2018 14:13:47 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-2-3-temporal-agent-issue/m-p/3684976#M508408</guid>
      <dc:creator>dhanushka_</dc:creator>
      <dc:date>2018-08-09T14:13:47Z</dc:date>
    </item>
    <item>
      <title>Re: ISE 2.3 - Temporal agent issue</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-2-3-temporal-agent-issue/m-p/3685549#M508409</link>
      <description>&lt;P&gt;make sure you have appropriate dACL configured for the PSNs to be discovered. you can go through this link - &lt;A href="https://www.cisco.com/c/en/us/support/docs/security/identity-services-engine/116143-config-cise-posture-00.html" target="_self"&gt;Link&lt;/A&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Also please work with TAC to troubleshoot this issue further.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks,&lt;/P&gt;
&lt;P&gt;Nidhi&lt;/P&gt;</description>
      <pubDate>Fri, 10 Aug 2018 05:40:26 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-2-3-temporal-agent-issue/m-p/3685549#M508409</guid>
      <dc:creator>Nidhi</dc:creator>
      <dc:date>2018-08-10T05:40:26Z</dc:date>
    </item>
    <item>
      <title>Re: ISE 2.3 - Temporal agent issue</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-2-3-temporal-agent-issue/m-p/3686814#M508412</link>
      <description>HI Nidhi,&lt;BR /&gt;&lt;BR /&gt;Thanks for your reply.</description>
      <pubDate>Mon, 13 Aug 2018 04:13:42 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-2-3-temporal-agent-issue/m-p/3686814#M508412</guid>
      <dc:creator>dhanushka_</dc:creator>
      <dc:date>2018-08-13T04:13:42Z</dc:date>
    </item>
    <item>
      <title>Re: ISE 2.3 - Temporal agent issue</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-2-3-temporal-agent-issue/m-p/3686821#M508415</link>
      <description>&lt;P&gt;HI&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I have able to found a solution for this issue.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;This Failed to contact policy server error got because of the DNS error. If temporal agent could not able to resolve FQDN as defined for G0 on ISE primary server this error occurred.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;FQDN (“hostname” and “ip domain-name”) of the ISE admin server itself must be added as a DNS entry.&lt;/P&gt;</description>
      <pubDate>Mon, 13 Aug 2018 04:52:37 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-2-3-temporal-agent-issue/m-p/3686821#M508415</guid>
      <dc:creator>dhanushka_</dc:creator>
      <dc:date>2018-08-13T04:52:37Z</dc:date>
    </item>
    <item>
      <title>Re: ISE 2.3 - Temporal agent issue</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-2-3-temporal-agent-issue/m-p/3687920#M508417</link>
      <description>Great! Yes all your ISE Nodes should be resolvable via DNS forward and reverse lookups for proper functionality &lt;BR /&gt;</description>
      <pubDate>Tue, 14 Aug 2018 11:48:19 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-2-3-temporal-agent-issue/m-p/3687920#M508417</guid>
      <dc:creator>Jason Kunst</dc:creator>
      <dc:date>2018-08-14T11:48:19Z</dc:date>
    </item>
  </channel>
</rss>

