<?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: Update to new IP address on Nodes in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/update-to-new-ip-address-on-nodes/m-p/5003001#M586653</link>
    <description>&lt;P&gt;As stated in the &lt;A href="https://www.cisco.com/c/en/us/td/docs/security/ise/3-2/admin_guide/b_ise_admin_3_2/b_ISE_admin_32_deployment.html#ID686" target="_blank" rel="noopener"&gt;Admin Guide&lt;/A&gt;, you can only change the IP address of the node when it is in standalone mode. To make this change, you would need to deregister the nodes from the PAN to make them standalone, change the IP addresses, wait for the ISE services to restart, then join them back to the cluster.&lt;/P&gt;</description>
    <pubDate>Tue, 23 Jan 2024 03:44:47 GMT</pubDate>
    <dc:creator>Greg Gibbs</dc:creator>
    <dc:date>2024-01-23T03:44:47Z</dc:date>
    <item>
      <title>Update to new IP address on Nodes</title>
      <link>https://community.cisco.com/t5/network-access-control/update-to-new-ip-address-on-nodes/m-p/5002998#M586652</link>
      <description>&lt;P&gt;Dear Community,&lt;/P&gt;&lt;P&gt;There are three deployment Nodes.&lt;/P&gt;&lt;P&gt;- Node1 as PAN&lt;/P&gt;&lt;P&gt;- Node2 as Secondary Node&lt;/P&gt;&lt;P&gt;- Node3 as pxGRID Node&lt;/P&gt;&lt;P&gt;Sceanrio:&lt;/P&gt;&lt;P&gt;- In case we perform update new IP subnet for PAN and pxGRID. Are there any impact?&lt;/P&gt;&lt;P&gt;Could you help to achieve change new IP on both Nodes step by step?&lt;/P&gt;&lt;P&gt;Any reload Nodes and down time?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Best regards,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 23 Jan 2024 03:33:00 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/update-to-new-ip-address-on-nodes/m-p/5002998#M586652</guid>
      <dc:creator>Da ICS16</dc:creator>
      <dc:date>2024-01-23T03:33:00Z</dc:date>
    </item>
    <item>
      <title>Re: Update to new IP address on Nodes</title>
      <link>https://community.cisco.com/t5/network-access-control/update-to-new-ip-address-on-nodes/m-p/5003001#M586653</link>
      <description>&lt;P&gt;As stated in the &lt;A href="https://www.cisco.com/c/en/us/td/docs/security/ise/3-2/admin_guide/b_ise_admin_3_2/b_ISE_admin_32_deployment.html#ID686" target="_blank" rel="noopener"&gt;Admin Guide&lt;/A&gt;, you can only change the IP address of the node when it is in standalone mode. To make this change, you would need to deregister the nodes from the PAN to make them standalone, change the IP addresses, wait for the ISE services to restart, then join them back to the cluster.&lt;/P&gt;</description>
      <pubDate>Tue, 23 Jan 2024 03:44:47 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/update-to-new-ip-address-on-nodes/m-p/5003001#M586653</guid>
      <dc:creator>Greg Gibbs</dc:creator>
      <dc:date>2024-01-23T03:44:47Z</dc:date>
    </item>
    <item>
      <title>Re: Update to new IP address on Nodes</title>
      <link>https://community.cisco.com/t5/network-access-control/update-to-new-ip-address-on-nodes/m-p/5003010#M586655</link>
      <description>&lt;P&gt;Dear&amp;nbsp;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/388087"&gt;@Greg Gibbs&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;&lt;P&gt;Are there any MnT and PSN interrupt or not during the Node rejoin cluster?&lt;/P&gt;&lt;P&gt;How long does it take time?&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;</description>
      <pubDate>Tue, 23 Jan 2024 03:51:39 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/update-to-new-ip-address-on-nodes/m-p/5003010#M586655</guid>
      <dc:creator>Da ICS16</dc:creator>
      <dc:date>2024-01-23T03:51:39Z</dc:date>
    </item>
    <item>
      <title>Re: Update to new IP address on Nodes</title>
      <link>https://community.cisco.com/t5/network-access-control/update-to-new-ip-address-on-nodes/m-p/5003013#M586656</link>
      <description>&lt;P&gt;You don't state what nodes the PSN and MnT personas are on, but this is absolutely a disruptive process. Any node that has to be changed to standalone and have the IP changed will experience downtime. The application server will be restarted several times for the change to standalone, ip address change, then join back to the cluster, and each time it can take 10-15 minutes for the application server to start again.&lt;/P&gt;
&lt;P&gt;This operation should be performed during a scheduled outage and you should allow for 1-2 hours for this procedure to be safe.&lt;/P&gt;</description>
      <pubDate>Tue, 23 Jan 2024 04:39:54 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/update-to-new-ip-address-on-nodes/m-p/5003013#M586656</guid>
      <dc:creator>Greg Gibbs</dc:creator>
      <dc:date>2024-01-23T04:39:54Z</dc:date>
    </item>
    <item>
      <title>Re: Update to new IP address on Nodes</title>
      <link>https://community.cisco.com/t5/network-access-control/update-to-new-ip-address-on-nodes/m-p/5003304#M586664</link>
      <description>&lt;P&gt;If the PSN and MnT personas are on separate nodes then changing the IP addresses on the PANs and pxGrid shouldn't affect your endpoints authentications and authorizations sessions.&lt;/P&gt;</description>
      <pubDate>Tue, 23 Jan 2024 10:04:35 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/update-to-new-ip-address-on-nodes/m-p/5003304#M586664</guid>
      <dc:creator>Aref Alsouqi</dc:creator>
      <dc:date>2024-01-23T10:04:35Z</dc:date>
    </item>
  </channel>
</rss>

