<?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: Two ISE Policy Nodes, One DNS Name in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/two-ise-policy-nodes-one-dns-name/m-p/3762501#M487166</link>
    <description>I would recommend looking at the Cisco live for performance and scale for any cast load balancing questions&lt;BR /&gt;&lt;BR /&gt;&lt;A href="https://community.cisco.com/t5/security-documents/ise-training/ta-p/3619944#toc-hId-1281981443" target="_blank"&gt;https://community.cisco.com/t5/security-documents/ise-training/ta-p/3619944#toc-hId-1281981443&lt;/A&gt;&lt;BR /&gt;</description>
    <pubDate>Thu, 13 Dec 2018 02:41:52 GMT</pubDate>
    <dc:creator>Jason Kunst</dc:creator>
    <dc:date>2018-12-13T02:41:52Z</dc:date>
    <item>
      <title>Two ISE Policy Nodes, One DNS Name</title>
      <link>https://community.cisco.com/t5/network-access-control/two-ise-policy-nodes-one-dns-name/m-p/3762424#M487163</link>
      <description>&lt;P&gt;We have two policy nodes. When one goes offline the DNS name for provisioning is not updated with the IP address of the second node. What is the recommended best practice so that when the primary provisioning server goes offline, it's DNS record is updated with the IP address of the secondary node? Thanks!&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 12 Dec 2018 22:30:42 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/two-ise-policy-nodes-one-dns-name/m-p/3762424#M487163</guid>
      <dc:creator>no_prop</dc:creator>
      <dc:date>2018-12-12T22:30:42Z</dc:date>
    </item>
    <item>
      <title>Re: Two ISE Policy Nodes, One DNS Name</title>
      <link>https://community.cisco.com/t5/network-access-control/two-ise-policy-nodes-one-dns-name/m-p/3762498#M487164</link>
      <description>&lt;P&gt;Hi&lt;BR /&gt;&lt;BR /&gt;When you say provisioning is for byod features?&lt;BR /&gt;Or for any authorization profile?&lt;BR /&gt;&lt;BR /&gt;On your authz profile, you can specify 1 fqdn but you need to have a load balancer to send the traffic to one or the other. If you just use dns, it'll do kind of hashing and some features like guest won't work correctly.&lt;BR /&gt;The other option, depending on your design, you can have an anycast design on the 2nd nic and then have only 1 fqdn.&lt;BR /&gt;&lt;BR /&gt;If you don't setup a fqdn in your authz profile, it will return it's own hostname with its dns suffix. If services are on additional nic (not the 1st), you can&amp;nbsp;configure an alias and ise will return this value.&lt;/P&gt;</description>
      <pubDate>Thu, 13 Dec 2018 02:36:09 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/two-ise-policy-nodes-one-dns-name/m-p/3762498#M487164</guid>
      <dc:creator>Francesco Molino</dc:creator>
      <dc:date>2018-12-13T02:36:09Z</dc:date>
    </item>
    <item>
      <title>Re: Two ISE Policy Nodes, One DNS Name</title>
      <link>https://community.cisco.com/t5/network-access-control/two-ise-policy-nodes-one-dns-name/m-p/3762501#M487166</link>
      <description>I would recommend looking at the Cisco live for performance and scale for any cast load balancing questions&lt;BR /&gt;&lt;BR /&gt;&lt;A href="https://community.cisco.com/t5/security-documents/ise-training/ta-p/3619944#toc-hId-1281981443" target="_blank"&gt;https://community.cisco.com/t5/security-documents/ise-training/ta-p/3619944#toc-hId-1281981443&lt;/A&gt;&lt;BR /&gt;</description>
      <pubDate>Thu, 13 Dec 2018 02:41:52 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/two-ise-policy-nodes-one-dns-name/m-p/3762501#M487166</guid>
      <dc:creator>Jason Kunst</dc:creator>
      <dc:date>2018-12-13T02:41:52Z</dc:date>
    </item>
  </channel>
</rss>

