<?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: Cisco ISE pxGrid Issue - It gets disabled on the Secodnary ISE Node !! in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/cisco-ise-pxgrid-issue-it-gets-disabled-on-the-secodnary-ise/m-p/3881819#M471868</link>
    <description>&lt;P&gt;This could use some clarification from a TME because I don't consider myself the ultimate source on pxGrid info.&lt;/P&gt;
&lt;P&gt;From a pxGrid v1 perspective, 100% active/standby, and the services will be down on the secondary node. But the 2.4 admin guide does indicate that port 8910, which is leveraged by webclients, will be active. Port 8910 with websockets is the way that pxgrid v2 operates, while port 5222 was the XMPP port pxgrid v1 used. The guide indicates that 5222 will only be open on the active node.&lt;/P&gt;
&lt;P&gt;I just tested this in my lab by firing up pxgrid services on 3 nodes, there are active web client connections on all three servers concurrently.&lt;/P&gt;
&lt;P&gt;This would also help clarify why the ISE performance and scale guide indicates 800 max subscribers for a dedicated deployment, while the per node pxGrid v2 scale is between 200-250 depending on the VM template deployed.&lt;/P&gt;</description>
    <pubDate>Sat, 29 Jun 2019 05:23:26 GMT</pubDate>
    <dc:creator>Damien Miller</dc:creator>
    <dc:date>2019-06-29T05:23:26Z</dc:date>
    <item>
      <title>Cisco ISE pxGrid Issue - It gets disabled on the Secodnary ISE Node !!</title>
      <link>https://community.cisco.com/t5/network-access-control/cisco-ise-pxgrid-issue-it-gets-disabled-on-the-secodnary-ise/m-p/3881380#M471858</link>
      <description>&lt;P&gt;Hi all,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&lt;U&gt;Environment:&lt;/U&gt;&lt;/STRONG&gt; I have two ISE nodes running as Cluster.&lt;/P&gt;&lt;P&gt;&lt;U&gt;&lt;STRONG&gt;&lt;FONT color="#3366FF"&gt;Trying to achieve:&lt;/FONT&gt;&lt;/STRONG&gt;&lt;/U&gt; I need to run pxGrid. So it needs to enable on both boxes manually. Correct!&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;U&gt;&lt;STRONG&gt;&lt;FONT color="#FF0000"&gt;Issue:&lt;/FONT&gt;&lt;/STRONG&gt;&lt;/U&gt; When I select the pxGrid checkbox then it does not run the pxGrid services on both boxes. but just on one box. On GUI, pxGrid option is Checked on both ISE nodes. But in CLI I can see clearly it is not running on both.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Primary ISE Node:&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;pxGrid Infrastructure Service&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &lt;FONT color="#008000"&gt;running&lt;/FONT&gt;&lt;BR /&gt;pxGrid Publisher Subscriber Service&amp;nbsp; &lt;FONT color="#008000"&gt;running&lt;/FONT&gt;&lt;BR /&gt;pxGrid Connection Manager&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &lt;FONT color="#008000"&gt;running&lt;/FONT&gt;&lt;BR /&gt;pxGrid Controller&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &lt;FONT color="#008000"&gt;running &lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Secondary ISE Node:&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;pxGrid Infrastructure Service&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;&lt;FONT color="#FF0000"&gt;disabled&lt;/FONT&gt;&lt;BR /&gt;pxGrid Publisher Subscriber Service&amp;nbsp; &lt;FONT color="#FF0000"&gt;disabled&lt;/FONT&gt;&lt;BR /&gt;pxGrid Connection Manager&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &lt;FONT color="#FF0000"&gt;disabled&lt;/FONT&gt;&lt;BR /&gt;pxGrid Controller&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;&lt;FONT color="#FF0000"&gt;disabled&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;FONT color="#000000"&gt;I have ran the pxGrid service manually but it still disables.&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT color="#000000"&gt;Is there any other settings that I'm missing?&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;FONT color="#000000"&gt;Regards,&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT color="#000000"&gt;B&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 28 Jun 2019 10:20:20 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/cisco-ise-pxgrid-issue-it-gets-disabled-on-the-secodnary-ise/m-p/3881380#M471858</guid>
      <dc:creator>Beacon Bits</dc:creator>
      <dc:date>2019-06-28T10:20:20Z</dc:date>
    </item>
    <item>
      <title>Re: Cisco ISE pxGrid Issue - It gets disabled on the Secodnary ISE Node !!</title>
      <link>https://community.cisco.com/t5/network-access-control/cisco-ise-pxgrid-issue-it-gets-disabled-on-the-secodnary-ise/m-p/3881509#M471863</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;That is by design, pxGrid runs in Active/Standby - therefore the services on the Secondary node will be disabled until it becomes Active.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Cisco reference doc &lt;A href="https://www.cisco.com/c/en/us/td/docs/security/ise/2-4/admin_guide/b_ise_admin_guide_24/b_ise_admin_guide_24_new_chapter_011.html#concept_FA33C4F07E274E7F9F2F3D33A9C2C0F0" target="_self"&gt;here&lt;/A&gt;. Quote from that doc "pxGrid nodes work in Active/Standby high availability mode which means that the pxGrid Service is in "running" state on the active node and in &lt;U&gt;&lt;EM&gt;&lt;STRONG&gt;"disabled" state on the standby&lt;/STRONG&gt; &lt;/EM&gt;&lt;/U&gt;node." &lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;HTH&lt;/P&gt;</description>
      <pubDate>Fri, 28 Jun 2019 14:16:55 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/cisco-ise-pxgrid-issue-it-gets-disabled-on-the-secodnary-ise/m-p/3881509#M471863</guid>
      <dc:creator>Rob Ingram</dc:creator>
      <dc:date>2019-06-28T14:16:55Z</dc:date>
    </item>
    <item>
      <title>Re: Cisco ISE pxGrid Issue - It gets disabled on the Secodnary ISE Node !!</title>
      <link>https://community.cisco.com/t5/network-access-control/cisco-ise-pxgrid-issue-it-gets-disabled-on-the-secodnary-ise/m-p/3881819#M471868</link>
      <description>&lt;P&gt;This could use some clarification from a TME because I don't consider myself the ultimate source on pxGrid info.&lt;/P&gt;
&lt;P&gt;From a pxGrid v1 perspective, 100% active/standby, and the services will be down on the secondary node. But the 2.4 admin guide does indicate that port 8910, which is leveraged by webclients, will be active. Port 8910 with websockets is the way that pxgrid v2 operates, while port 5222 was the XMPP port pxgrid v1 used. The guide indicates that 5222 will only be open on the active node.&lt;/P&gt;
&lt;P&gt;I just tested this in my lab by firing up pxgrid services on 3 nodes, there are active web client connections on all three servers concurrently.&lt;/P&gt;
&lt;P&gt;This would also help clarify why the ISE performance and scale guide indicates 800 max subscribers for a dedicated deployment, while the per node pxGrid v2 scale is between 200-250 depending on the VM template deployed.&lt;/P&gt;</description>
      <pubDate>Sat, 29 Jun 2019 05:23:26 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/cisco-ise-pxgrid-issue-it-gets-disabled-on-the-secodnary-ise/m-p/3881819#M471868</guid>
      <dc:creator>Damien Miller</dc:creator>
      <dc:date>2019-06-29T05:23:26Z</dc:date>
    </item>
    <item>
      <title>Re: Cisco ISE pxGrid Issue - It gets disabled on the Secodnary ISE Node !!</title>
      <link>https://community.cisco.com/t5/network-access-control/cisco-ise-pxgrid-issue-it-gets-disabled-on-the-secodnary-ise/m-p/3882180#M471873</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;For pxGrid 1.0, you can only have 2 pxGrid nodes per ISE deployment, where only one pxGrid node can be active at a time and the other node will be in standby.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;If you have any additional questions, please email me directly.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks,&lt;/P&gt;
&lt;P&gt;John&lt;/P&gt;
&lt;P&gt;jeppich@cisco.com&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sun, 30 Jun 2019 16:08:57 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/cisco-ise-pxgrid-issue-it-gets-disabled-on-the-secodnary-ise/m-p/3882180#M471873</guid>
      <dc:creator>jeppich</dc:creator>
      <dc:date>2019-06-30T16:08:57Z</dc:date>
    </item>
  </channel>
</rss>

