<?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 2.1 Patch Mismatch in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/ise-2-1-patch-mismatch/m-p/3201630#M553579</link>
    <description>I am not sure if there is a way to patch just one node in the deployment. If this is a PSN and you have other fallback nodes, I would de-register this from the deployment, patch it with the same version as others and add it back again.</description>
    <pubDate>Thu, 19 Oct 2017 13:26:42 GMT</pubDate>
    <dc:creator>Rahul Govindan</dc:creator>
    <dc:date>2017-10-19T13:26:42Z</dc:date>
    <item>
      <title>ISE 2.1 Patch Mismatch</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-2-1-patch-mismatch/m-p/3200243#M553422</link>
      <description>&lt;P&gt;I am looking at upgrading a 5 node 2.1.0.474 deployment. When I select Upgrade I get the following error about patch versions. Patch 2 is installed on all nodes. Patch 1 in installed on 4 of the 5 nodes. We had to rebuild one of the nodes and during the build process installed patch 2 but not patch 1. The patches are cumulative so doesn't seem like this difference should matter but apparently it does. Any advice?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Screen Shot 2017-10-17 at 11.42.28 AM.png" style="width: 999px;"&gt;&lt;img src="https://community.cisco.com/t5/image/serverpage/image-id/2061iB3CC17BE76438CD6/image-size/large?v=v2&amp;amp;px=999" role="button" title="Screen Shot 2017-10-17 at 11.42.28 AM.png" alt="Screen Shot 2017-10-17 at 11.42.28 AM.png" /&gt;&lt;/span&gt;&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>Fri, 21 Feb 2020 18:36:23 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-2-1-patch-mismatch/m-p/3200243#M553422</guid>
      <dc:creator>dporod</dc:creator>
      <dc:date>2020-02-21T18:36:23Z</dc:date>
    </item>
    <item>
      <title>Re: ISE 2.1 Patch Mismatch</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-2-1-patch-mismatch/m-p/3201630#M553579</link>
      <description>I am not sure if there is a way to patch just one node in the deployment. If this is a PSN and you have other fallback nodes, I would de-register this from the deployment, patch it with the same version as others and add it back again.</description>
      <pubDate>Thu, 19 Oct 2017 13:26:42 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-2-1-patch-mismatch/m-p/3201630#M553579</guid>
      <dc:creator>Rahul Govindan</dc:creator>
      <dc:date>2017-10-19T13:26:42Z</dc:date>
    </item>
    <item>
      <title>Re: ISE 2.1 Patch Mismatch</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-2-1-patch-mismatch/m-p/3201802#M553580</link>
      <description>&lt;P&gt;I agree with Rahul.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;This is a known bug on 2.1. Patches are indeed cumulative but the upgrade process doesn't parse this use case properly.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;By the way - I would definitely recommend going to 2.3 (Patch 1). Do not go to 2.2 (no matter what patch).&amp;nbsp;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 19 Oct 2017 16:06:09 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-2-1-patch-mismatch/m-p/3201802#M553580</guid>
      <dc:creator>Marvin Rhoads</dc:creator>
      <dc:date>2017-10-19T16:06:09Z</dc:date>
    </item>
  </channel>
</rss>

