<?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: Secondary ISE auth requests in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/secondary-ise-auth-requests/m-p/4584833#M573843</link>
    <description>&lt;P&gt;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/161770"&gt;@manvik&lt;/a&gt; I assume these ISE nodes part of the same cluster? If so, then as long as the secondary node is running the PSN persona then yes it can authenticate requests from the DR ASA. It's the configuration of the ASA which is configured with the PSN and which PSN to prefer.&lt;/P&gt;</description>
    <pubDate>Mon, 04 Apr 2022 07:36:37 GMT</pubDate>
    <dc:creator>Rob Ingram</dc:creator>
    <dc:date>2022-04-04T07:36:37Z</dc:date>
    <item>
      <title>Secondary ISE auth requests</title>
      <link>https://community.cisco.com/t5/network-access-control/secondary-ise-auth-requests/m-p/4584798#M573842</link>
      <description>&lt;P&gt;Can secondary ISE serve any authentication requests?&amp;nbsp;Current setup is primary ISE at DC and secondary ISE at DR.&amp;nbsp;&lt;BR /&gt;Testing anyconnect VPN via DR. Since DR ISE is in a secondary role, can it server the authentication&amp;nbsp;requests from DR ASA.&lt;/P&gt;</description>
      <pubDate>Mon, 04 Apr 2022 06:58:07 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/secondary-ise-auth-requests/m-p/4584798#M573842</guid>
      <dc:creator>manvik</dc:creator>
      <dc:date>2022-04-04T06:58:07Z</dc:date>
    </item>
    <item>
      <title>Re: Secondary ISE auth requests</title>
      <link>https://community.cisco.com/t5/network-access-control/secondary-ise-auth-requests/m-p/4584833#M573843</link>
      <description>&lt;P&gt;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/161770"&gt;@manvik&lt;/a&gt; I assume these ISE nodes part of the same cluster? If so, then as long as the secondary node is running the PSN persona then yes it can authenticate requests from the DR ASA. It's the configuration of the ASA which is configured with the PSN and which PSN to prefer.&lt;/P&gt;</description>
      <pubDate>Mon, 04 Apr 2022 07:36:37 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/secondary-ise-auth-requests/m-p/4584833#M573843</guid>
      <dc:creator>Rob Ingram</dc:creator>
      <dc:date>2022-04-04T07:36:37Z</dc:date>
    </item>
    <item>
      <title>Re: Secondary ISE auth requests</title>
      <link>https://community.cisco.com/t5/network-access-control/secondary-ise-auth-requests/m-p/4584859#M573845</link>
      <description>&lt;P&gt;yes, ISE nodes are part of same cluster. currently the authentication is not working, can DR ISE logs viewed from DC ISE in same cluster.&lt;/P&gt;</description>
      <pubDate>Mon, 04 Apr 2022 08:47:40 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/secondary-ise-auth-requests/m-p/4584859#M573845</guid>
      <dc:creator>manvik</dc:creator>
      <dc:date>2022-04-04T08:47:40Z</dc:date>
    </item>
    <item>
      <title>Re: Secondary ISE auth requests</title>
      <link>https://community.cisco.com/t5/network-access-control/secondary-ise-auth-requests/m-p/4584926#M573857</link>
      <description>&lt;P&gt;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/161770"&gt;@manvik&lt;/a&gt; Yes, you should be able to see the authentications in the DC ISE Logs. DC/DR are part of the same cluster, the Primary MnT will log traffic for any PSN in the cluster, regardless of where it is physically located.&lt;/P&gt;</description>
      <pubDate>Mon, 04 Apr 2022 10:25:59 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/secondary-ise-auth-requests/m-p/4584926#M573857</guid>
      <dc:creator>Rob Ingram</dc:creator>
      <dc:date>2022-04-04T10:25:59Z</dc:date>
    </item>
  </channel>
</rss>

