<?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 node group behind load balancer in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/ise-node-group-behind-load-balancer/m-p/2193497#M137948</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;You can place them in either. The trouble becomes with having to deal with all of the ACL rules that you have to manage. There are a lot of ports and protocols used by ISE. Also, it is not not uncommon for some of those ports to change with new releases &lt;SPAN __jive_emoticon_name="happy" __jive_macro_name="emoticon" class="jive_macro jive_emote" src="https://community.cisco.com/4.5.4/images/emoticons/happy.gif"&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;Thank you for rating!&lt;/EM&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 20 Mar 2013 18:27:03 GMT</pubDate>
    <dc:creator>nspasov</dc:creator>
    <dc:date>2013-03-20T18:27:03Z</dc:date>
    <item>
      <title>ISE node group behind load balancer</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-node-group-behind-load-balancer/m-p/2193494#M137866</link>
      <description>&lt;P&gt;I'm trying to gather info on distributed deployment w/ multiple PSN nodes.&lt;/P&gt;&lt;P&gt;Having read through some documents, it looks like you can put multiple PSN's in a node group, and then place the node group behind a load balancer.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Q1:&lt;/P&gt;&lt;P&gt;Node group config requires multicast.&lt;/P&gt;&lt;P&gt;Cisco ACE LB doesn't support multicast, except in brige mode.&lt;/P&gt;&lt;P&gt;How do people support distributed deployment in node group behind Ciso ACE?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Q2:&lt;/P&gt;&lt;P&gt;User guide says: "We recommend that you have two, three, or a maximum of four nodes in a node group."&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-external-small" href="http://www.cisco.com/en/US/docs/security/ise/1.1.1/user_guide/ise_dis_deploy.html#wp1134272" target="_blank"&gt;http://www.cisco.com/en/US/docs/security/ise/1.1.1/user_guide/ise_dis_deploy.html#wp1134272&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What if we need more than 4 PSN nodes to support our network &amp;amp; user base?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Q3:&lt;/P&gt;&lt;P&gt;Has anyone been able to implement distributed deployment between two datacenters behind GSS?&lt;/P&gt;&lt;P&gt;If GSS isn't possible, we'll be happy to just have it in working state behind ACE LB.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;thx!&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 03:13:08 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-node-group-behind-load-balancer/m-p/2193494#M137866</guid>
      <dc:creator>huangedmc</dc:creator>
      <dc:date>2019-03-11T03:13:08Z</dc:date>
    </item>
    <item>
      <title>ISE node group behind load balancer</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-node-group-behind-load-balancer/m-p/2193495#M137886</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I have had close to zero experience with LBs so my answers will be limited:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Q1: I don't think the multicast plays any role with the LB. The multicast address is needed for the ISE nodes for replication&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Q2: You will have to create a new node group with a new multicast address&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Q3: No help here&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Couple of other things to remember:&lt;/P&gt;&lt;P&gt;1. The nodes must be layer 2 adjacent&lt;/P&gt;&lt;P&gt;2. You must use routed mode...no NAT/SNAT. Each node must be reachable directly from the end clients&lt;/P&gt;&lt;P&gt;3. You must perform sticky&lt;/P&gt;&lt;P&gt;4. The Load balancers must be listed as NADs in ISE&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope this provides some help to you.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;Thank you for rating!&lt;/EM&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 20 Mar 2013 17:58:54 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-node-group-behind-load-balancer/m-p/2193495#M137886</guid>
      <dc:creator>nspasov</dc:creator>
      <dc:date>2013-03-20T17:58:54Z</dc:date>
    </item>
    <item>
      <title>ISE node group behind load balancer</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-node-group-behind-load-balancer/m-p/2193496#M137919</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks Neno.&lt;/P&gt;&lt;P&gt;Follow-up question:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Where do people usually place their ISE nodes? Internal or DMZ?&lt;/P&gt;&lt;P&gt;I heard they're typically put in the internal networks...&lt;/P&gt;&lt;P&gt;Why it's a good idea to keep ISE in the internal networks, instead of DMZ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If guests can interface directly w/ the ISE, wouldn't it be safer to place it in the DMZ?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 20 Mar 2013 18:20:54 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-node-group-behind-load-balancer/m-p/2193496#M137919</guid>
      <dc:creator>huangedmc</dc:creator>
      <dc:date>2013-03-20T18:20:54Z</dc:date>
    </item>
    <item>
      <title>ISE node group behind load balancer</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-node-group-behind-load-balancer/m-p/2193497#M137948</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;You can place them in either. The trouble becomes with having to deal with all of the ACL rules that you have to manage. There are a lot of ports and protocols used by ISE. Also, it is not not uncommon for some of those ports to change with new releases &lt;SPAN __jive_emoticon_name="happy" __jive_macro_name="emoticon" class="jive_macro jive_emote" src="https://community.cisco.com/4.5.4/images/emoticons/happy.gif"&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;Thank you for rating!&lt;/EM&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 20 Mar 2013 18:27:03 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-node-group-behind-load-balancer/m-p/2193497#M137948</guid>
      <dc:creator>nspasov</dc:creator>
      <dc:date>2013-03-20T18:27:03Z</dc:date>
    </item>
  </channel>
</rss>

