<?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 Deployment patching in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/ise-deployment-patching/m-p/5325791#M598000</link>
    <description>At least we agree on PPAN first. I think the order I described is the same as what ISE developers chose when you patch via the GUI. I think that TAC has a more efficient method because you can test the patch on PSN a bit sooner. But apart from that it’s horses for courses.&lt;BR /&gt;</description>
    <pubDate>Sat, 30 Aug 2025 11:30:01 GMT</pubDate>
    <dc:creator>Arne Bier</dc:creator>
    <dc:date>2025-08-30T11:30:01Z</dc:date>
    <item>
      <title>ISE Deployment patching</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-deployment-patching/m-p/5325240#M597981</link>
      <description>&lt;P&gt;Hi&lt;/P&gt;&lt;P&gt;Six node distributed ISE Deployment&lt;/P&gt;&lt;P&gt;Whats the recommended order to patch fronm cli please.??&lt;/P&gt;&lt;P&gt;1.PRI-PAN which is also SEC MNT&lt;/P&gt;&lt;P&gt;2.SEC-PAN which is also PRI MNT&lt;/P&gt;&lt;P&gt;3.PSNs&lt;/P&gt;</description>
      <pubDate>Thu, 28 Aug 2025 12:53:58 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-deployment-patching/m-p/5325240#M597981</guid>
      <dc:creator>N3om</dc:creator>
      <dc:date>2025-08-28T12:53:58Z</dc:date>
    </item>
    <item>
      <title>Re: ISE Deployment patching</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-deployment-patching/m-p/5325405#M597984</link>
      <description>&lt;P&gt;Always Primary PAN first. Then the next PAN, PSNs last. I can't remember seeing a documented technical reason why this order is good/necessary. I think it's possibly just common sense because the primary database is on the Primary Admin node and since it's in charge of writing to the database, it gets patched first.&amp;nbsp; The operational benefit of doing PAN first, is that you "take the hit" of taking down the admin GUI first, and then you can monitor the rest of the patching process from the GUI.&lt;/P&gt;</description>
      <pubDate>Thu, 28 Aug 2025 21:32:32 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-deployment-patching/m-p/5325405#M597984</guid>
      <dc:creator>Arne Bier</dc:creator>
      <dc:date>2025-08-28T21:32:32Z</dc:date>
    </item>
    <item>
      <title>Re: ISE Deployment patching</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-deployment-patching/m-p/5325462#M597989</link>
      <description>&lt;P&gt;check some guidance :&lt;/P&gt;
&lt;P&gt;&lt;A href="https://www.youtube.com/watch?v=qV5-KY0CCQo&amp;amp;t=177s" target="_blank"&gt;https://www.youtube.com/watch?v=qV5-KY0CCQo&amp;amp;t=177s&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;Post :&lt;/P&gt;
&lt;P&gt;&lt;A href="https://community.cisco.com/t5/network-access-control/patch-upgrade-in-cisco-ise-distributed-deployment/m-p/5287196" target="_blank"&gt;https://community.cisco.com/t5/network-access-control/patch-upgrade-in-cisco-ise-distributed-deployment/m-p/5287196&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 29 Aug 2025 06:35:12 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-deployment-patching/m-p/5325462#M597989</guid>
      <dc:creator>balaji.bandi</dc:creator>
      <dc:date>2025-08-29T06:35:12Z</dc:date>
    </item>
    <item>
      <title>Re: ISE Deployment patching</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-deployment-patching/m-p/5325783#M597999</link>
      <description>&lt;BLOCKQUOTE&gt;&lt;HR /&gt;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/158532"&gt;@Arne Bier&lt;/a&gt;&amp;nbsp;wrote:&lt;BR /&gt;&lt;P&gt;Always Primary PAN first. Then the next PAN, PSNs last. I can't remember seeing a documented technical reason why this order is good/necessary. I think it's possibly just common sense because the primary database is on the Primary Admin node and since it's in charge of writing to the database, it gets patched first.&amp;nbsp; The operational benefit of doing PAN first, is that you "take the hit" of taking down the admin GUI first, and then you can monitor the rest of the patching process from the GUI.&lt;/P&gt;&lt;HR /&gt;&lt;/BLOCKQUOTE&gt;&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/158532"&gt;@Arne Bier&lt;/a&gt;:&amp;nbsp; The poster asked about patching via the CLI.&amp;nbsp; I just did one recently, and according to Cisco TAC, it should be in this order:&lt;/P&gt;&lt;P&gt;1- PAN&lt;/P&gt;&lt;P&gt;2- PSNs&lt;/P&gt;&lt;P&gt;3- SAN&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sat, 30 Aug 2025 10:19:19 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-deployment-patching/m-p/5325783#M597999</guid>
      <dc:creator>adamscottmaster2013</dc:creator>
      <dc:date>2025-08-30T10:19:19Z</dc:date>
    </item>
    <item>
      <title>Re: ISE Deployment patching</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-deployment-patching/m-p/5325791#M598000</link>
      <description>At least we agree on PPAN first. I think the order I described is the same as what ISE developers chose when you patch via the GUI. I think that TAC has a more efficient method because you can test the patch on PSN a bit sooner. But apart from that it’s horses for courses.&lt;BR /&gt;</description>
      <pubDate>Sat, 30 Aug 2025 11:30:01 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-deployment-patching/m-p/5325791#M598000</guid>
      <dc:creator>Arne Bier</dc:creator>
      <dc:date>2025-08-30T11:30:01Z</dc:date>
    </item>
  </channel>
</rss>

