<?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 2.1 Patch Update in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/cisco-ise-2-1-patch-update/m-p/3730258#M489125</link>
    <description>Thanks for response.&lt;BR /&gt;If we go with CLI, is there any specific sequence we should follow?&lt;BR /&gt;Also, what would be the downtime for the users?&lt;BR /&gt;Thanks.</description>
    <pubDate>Mon, 22 Oct 2018 22:39:30 GMT</pubDate>
    <dc:creator>dot1x</dc:creator>
    <dc:date>2018-10-22T22:39:30Z</dc:date>
    <item>
      <title>Cisco ISE 2.1 Patch Update</title>
      <link>https://community.cisco.com/t5/network-access-control/cisco-ise-2-1-patch-update/m-p/3729471#M489086</link>
      <description>&lt;P&gt;Hi All,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Could someone please assist how long does it take to apply patch on Cisco ISE (distributed environment).&lt;/P&gt;
&lt;P&gt;We have 1 PAN, 1 SAN, 3 PSNs running 2.1&lt;/P&gt;
&lt;P&gt;Thanks.&lt;/P&gt;</description>
      <pubDate>Mon, 22 Oct 2018 02:11:15 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/cisco-ise-2-1-patch-update/m-p/3729471#M489086</guid>
      <dc:creator>dot1x</dc:creator>
      <dc:date>2018-10-22T02:11:15Z</dc:date>
    </item>
    <item>
      <title>Re: Cisco ISE 2.1 Patch Update</title>
      <link>https://community.cisco.com/t5/network-access-control/cisco-ise-2-1-patch-update/m-p/3729495#M489088</link>
      <description>&lt;P&gt;I would plan for about 45 minutes a node. Each node will reload after patch instalation.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 22 Oct 2018 03:04:04 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/cisco-ise-2-1-patch-update/m-p/3729495#M489088</guid>
      <dc:creator>Damien Miller</dc:creator>
      <dc:date>2018-10-22T03:04:04Z</dc:date>
    </item>
    <item>
      <title>Re: Cisco ISE 2.1 Patch Update</title>
      <link>https://community.cisco.com/t5/network-access-control/cisco-ise-2-1-patch-update/m-p/3730254#M489108</link>
      <description>&lt;P&gt;For production, I would suggest to apply patches via CLI because this way gives us a better control when and which ISE nodes to start patching and possible to do a few ISE nodes at the same time. Please remember to take an ISE CFG backup beforehand.&lt;/P&gt;</description>
      <pubDate>Mon, 22 Oct 2018 22:32:01 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/cisco-ise-2-1-patch-update/m-p/3730254#M489108</guid>
      <dc:creator>hslai</dc:creator>
      <dc:date>2018-10-22T22:32:01Z</dc:date>
    </item>
    <item>
      <title>Re: Cisco ISE 2.1 Patch Update</title>
      <link>https://community.cisco.com/t5/network-access-control/cisco-ise-2-1-patch-update/m-p/3730258#M489125</link>
      <description>Thanks for response.&lt;BR /&gt;If we go with CLI, is there any specific sequence we should follow?&lt;BR /&gt;Also, what would be the downtime for the users?&lt;BR /&gt;Thanks.</description>
      <pubDate>Mon, 22 Oct 2018 22:39:30 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/cisco-ise-2-1-patch-update/m-p/3730258#M489125</guid>
      <dc:creator>dot1x</dc:creator>
      <dc:date>2018-10-22T22:39:30Z</dc:date>
    </item>
    <item>
      <title>Re: Cisco ISE 2.1 Patch Update</title>
      <link>https://community.cisco.com/t5/network-access-control/cisco-ise-2-1-patch-update/m-p/3730263#M489141</link>
      <description>&lt;P&gt;First to the primary ISE node and the rest can be in any given order. Best to schedule a maintenance window and use a load balancer to take patching PSNs offline or online.&lt;/P&gt;</description>
      <pubDate>Mon, 22 Oct 2018 22:44:19 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/cisco-ise-2-1-patch-update/m-p/3730263#M489141</guid>
      <dc:creator>hslai</dc:creator>
      <dc:date>2018-10-22T22:44:19Z</dc:date>
    </item>
    <item>
      <title>Re: Cisco ISE 2.1 Patch Update</title>
      <link>https://community.cisco.com/t5/network-access-control/cisco-ise-2-1-patch-update/m-p/3730269#M489156</link>
      <description>For 5 nodes deployment, a maintenance window of 5 hours would work?</description>
      <pubDate>Mon, 22 Oct 2018 22:53:59 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/cisco-ise-2-1-patch-update/m-p/3730269#M489156</guid>
      <dc:creator>dot1x</dc:creator>
      <dc:date>2018-10-22T22:53:59Z</dc:date>
    </item>
    <item>
      <title>Re: Cisco ISE 2.1 Patch Update</title>
      <link>https://community.cisco.com/t5/network-access-control/cisco-ise-2-1-patch-update/m-p/3730272#M489174</link>
      <description>&lt;P&gt;Start with the primary admin node, then choose the node order you want after that. 5 hours should be enough for five nodes.&amp;nbsp;&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;&lt;A href="https://www.cisco.com/c/en/us/td/docs/security/ise/2-1/admin_guide/b_ise_admin_guide_21/b_ise_admin_guide_20_chapter_0100.html#ID202" target="_blank"&gt;https://www.cisco.com/c/en/us/td/docs/security/ise/2-1/admin_guide/b_ise_admin_guide_21/b_ise_admin_guide_20_chapter_0100.html#ID202&lt;/A&gt;&lt;BR /&gt;"If you are installing the patch from the CLI, you can control the order in which the nodes are updated. However, we recommend that you install the patch on the Primary PAN first."&lt;BR /&gt;&lt;BR /&gt;You will use the command "patch install &amp;lt;patch name&amp;gt; &amp;lt;repo name that has patch file&amp;gt;"&lt;BR /&gt;&lt;BR /&gt;The impact to users and services depends on which node is patching and your HA config. If you have redundant radius servers configured on your NAD's then user impact should be relatively minor. &lt;BR /&gt;&lt;BR /&gt;Read this section of the admin guide to see what will be unavailable while the primary admin node is down/patching.&lt;BR /&gt;&lt;A href="https://www.cisco.com/c/en/us/td/docs/security/ise/2-1/admin_guide/b_ise_admin_guide_21/b_ise_admin_guide_20_chapter_010.html#ID59" target="_blank"&gt;https://www.cisco.com/c/en/us/td/docs/security/ise/2-1/admin_guide/b_ise_admin_guide_21/b_ise_admin_guide_20_chapter_010.html#ID59&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 22 Oct 2018 22:58:13 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/cisco-ise-2-1-patch-update/m-p/3730272#M489174</guid>
      <dc:creator>Damien Miller</dc:creator>
      <dc:date>2018-10-22T22:58:13Z</dc:date>
    </item>
    <item>
      <title>Re: Cisco ISE 2.1 Patch Update</title>
      <link>https://community.cisco.com/t5/network-access-control/cisco-ise-2-1-patch-update/m-p/3730275#M489195</link>
      <description>Thanks guys!</description>
      <pubDate>Mon, 22 Oct 2018 23:09:29 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/cisco-ise-2-1-patch-update/m-p/3730275#M489195</guid>
      <dc:creator>dot1x</dc:creator>
      <dc:date>2018-10-22T23:09:29Z</dc:date>
    </item>
  </channel>
</rss>

