<?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 single cluster with 2 AD in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/ise-single-cluster-with-2-ad/m-p/3469553#M496595</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;As Dustin said the ISE deployment can join multiple AD domains.&amp;nbsp; Then it is up to you and the rule base how you authenticate against those domains.&amp;nbsp; There would be no need to separate by PSN or anything.&amp;nbsp; It is up to the network to utilize the PSNs as needed.&amp;nbsp; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I guess in theory you could do something like:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;PSN 1 and PSN 2 join AD domain 1&lt;/P&gt;&lt;P&gt;PSN 3 and PSN 4 join AD domain 2&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;but not sure why you would want to do that.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 29 Jun 2018 18:37:48 GMT</pubDate>
    <dc:creator>paul</dc:creator>
    <dc:date>2018-06-29T18:37:48Z</dc:date>
    <item>
      <title>ISE single cluster with 2 AD</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-single-cluster-with-2-ad/m-p/3469551#M496593</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Experts,&lt;/P&gt;&lt;P&gt;Want to ask whether it is feasible to have 2 separate AD for a single cluster, say segregate them by PSN?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;BR /&gt;Wendy&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 29 Jun 2018 10:46:18 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-single-cluster-with-2-ad/m-p/3469551#M496593</guid>
      <dc:creator>wchik</dc:creator>
      <dc:date>2018-06-29T10:46:18Z</dc:date>
    </item>
    <item>
      <title>Re: ISE single cluster with 2 AD</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-single-cluster-with-2-ad/m-p/3469552#M496594</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;You can have multiple AD's on a cluster, but I don't think you can have a node do one AD and the second do the other since when they are clustered, only one is able to be configured and it duplicates it to both.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You may be able to do some of it through rules, but I haven't looked if you can call out the specific node in a rule.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 29 Jun 2018 18:08:36 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-single-cluster-with-2-ad/m-p/3469552#M496594</guid>
      <dc:creator>Dustin Anderson</dc:creator>
      <dc:date>2018-06-29T18:08:36Z</dc:date>
    </item>
    <item>
      <title>Re: ISE single cluster with 2 AD</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-single-cluster-with-2-ad/m-p/3469553#M496595</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;As Dustin said the ISE deployment can join multiple AD domains.&amp;nbsp; Then it is up to you and the rule base how you authenticate against those domains.&amp;nbsp; There would be no need to separate by PSN or anything.&amp;nbsp; It is up to the network to utilize the PSNs as needed.&amp;nbsp; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I guess in theory you could do something like:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;PSN 1 and PSN 2 join AD domain 1&lt;/P&gt;&lt;P&gt;PSN 3 and PSN 4 join AD domain 2&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;but not sure why you would want to do that.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 29 Jun 2018 18:37:48 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-single-cluster-with-2-ad/m-p/3469553#M496595</guid>
      <dc:creator>paul</dc:creator>
      <dc:date>2018-06-29T18:37:48Z</dc:date>
    </item>
    <item>
      <title>Re: ISE single cluster with 2 AD</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-single-cluster-with-2-ad/m-p/3469554#M496597</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Adding to what Paul and Dustin said... which seems related to how it is done in ACS 5.x -- &lt;A href="https://www.cisco.com/c/en/us/td/docs/net_mgmt/cisco_secure_access_control_system/5-8/ACS-ADIntegration/guide/Active_Directory_Integration_in_ACS_5-8.html#pgfId-417854"&gt;Joining ACS to Active Directory Domain&lt;/A&gt;&lt;/P&gt;&lt;BLOCKQUOTE&gt;&lt;TABLE border="1"&gt;&lt;TBODY&gt;&lt;TR&gt;&lt;TD&gt;&lt;SPAN style="color: #525252; font-family: Arial, Helvetica, sans-serif; font-size: 14px;"&gt;&lt;EM&gt;You can join the ACS nodes from same deployment to different AD domains. However, each node can be joined to a single AD domain. ...&lt;/EM&gt;&lt;/SPAN&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;/TBODY&gt;&lt;/TABLE&gt;&lt;/BLOCKQUOTE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ISE 1.3+ does not have this limitation.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10pt;"&gt;If 2 AD means 2 AD domain controllers, then we may use &lt;/SPAN&gt;&lt;A href="https://technet.microsoft.com/en-us/library/dd277428.aspx" style="font-size: 10pt;"&gt;Microsoft Active Directory Sites and Services&lt;/A&gt;&lt;SPAN style="font-size: 10pt;"&gt; to have PSNs use the domain controllers designated to the sites that have the subnets where PSNs residing in.&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 29 Jun 2018 21:15:28 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-single-cluster-with-2-ad/m-p/3469554#M496597</guid>
      <dc:creator>hslai</dc:creator>
      <dc:date>2018-06-29T21:15:28Z</dc:date>
    </item>
  </channel>
</rss>

