<?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: Upgrade options in large critical deployments in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/upgrade-options-in-large-critical-deployments/m-p/3531464#M519858</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Krishnan,&lt;/P&gt;&lt;P&gt;This could be a number of versions, but we'll assume that it's a 1.4 or 2.2 deployment for long lived support.&amp;nbsp; Typically most of the financials I work with have 24 PSN's and are upgrading minor versions to remain within support, or are upgrading due to PSIRTs or bug fixes.&amp;nbsp; Without splitting the deployment, we would need to factor in about 24-28 straight hours of upgrades to upgrade all of the PAN's, MNT's and PSN's, but splitting can at least lead to a burn in type test capability.&amp;nbsp; Features would vary across customers, but for the sake of argument, my main customer has Auth, a large number of custom profiles, Guest, and would be looking to add Posture capabilities at some time in the future if this hangup was addressed.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 27 Nov 2017 17:10:30 GMT</pubDate>
    <dc:creator>Patrick Lloyd</dc:creator>
    <dc:date>2017-11-27T17:10:30Z</dc:date>
    <item>
      <title>Upgrade options in large critical deployments</title>
      <link>https://community.cisco.com/t5/network-access-control/upgrade-options-in-large-critical-deployments/m-p/3531462#M519847</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I work with large financials and one of the largest questions one of them has is the concern around upgrades and ensuring that major disasters don't occur.&amp;nbsp; As a result, they split their deployment when doing upgrades and rejoin the deployments back together post upgrade when both deployments have been successful.&amp;nbsp; An additional option of upgrading through CLI and having nodes subsequently upgraded but a manual rolling upgrade or individual nodes being on either the pre or post upgrade version has also been asked about.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is there a preferred way that the ISE BU recommends when dealing with &amp;gt;20 PSN's in critical financial environments?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 15 Nov 2017 17:15:01 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/upgrade-options-in-large-critical-deployments/m-p/3531462#M519847</guid>
      <dc:creator>Patrick Lloyd</dc:creator>
      <dc:date>2017-11-15T17:15:01Z</dc:date>
    </item>
    <item>
      <title>Re: Upgrade options in large critical deployments</title>
      <link>https://community.cisco.com/t5/network-access-control/upgrade-options-in-large-critical-deployments/m-p/3531463#M519852</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Patrick,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It would be good to know the following&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What is the ISE version the customer is on, size of deployment(locations)?&lt;/P&gt;&lt;P&gt;Are there any critical reasons for upgrade?&lt;/P&gt;&lt;P&gt;What are the services/features turned on in ISE?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Yes we have seen a split upgrade in large customers having number of PSN’s, so that they upgrade part of the deployment first and test it then upgrade the rest.&lt;/P&gt;&lt;P&gt;It would be good to know further information before any recommendation.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;Krishnan&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 15 Nov 2017 17:40:54 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/upgrade-options-in-large-critical-deployments/m-p/3531463#M519852</guid>
      <dc:creator>kthiruve</dc:creator>
      <dc:date>2017-11-15T17:40:54Z</dc:date>
    </item>
    <item>
      <title>Re: Upgrade options in large critical deployments</title>
      <link>https://community.cisco.com/t5/network-access-control/upgrade-options-in-large-critical-deployments/m-p/3531464#M519858</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Krishnan,&lt;/P&gt;&lt;P&gt;This could be a number of versions, but we'll assume that it's a 1.4 or 2.2 deployment for long lived support.&amp;nbsp; Typically most of the financials I work with have 24 PSN's and are upgrading minor versions to remain within support, or are upgrading due to PSIRTs or bug fixes.&amp;nbsp; Without splitting the deployment, we would need to factor in about 24-28 straight hours of upgrades to upgrade all of the PAN's, MNT's and PSN's, but splitting can at least lead to a burn in type test capability.&amp;nbsp; Features would vary across customers, but for the sake of argument, my main customer has Auth, a large number of custom profiles, Guest, and would be looking to add Posture capabilities at some time in the future if this hangup was addressed.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 27 Nov 2017 17:10:30 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/upgrade-options-in-large-critical-deployments/m-p/3531464#M519858</guid>
      <dc:creator>Patrick Lloyd</dc:creator>
      <dc:date>2017-11-27T17:10:30Z</dc:date>
    </item>
  </channel>
</rss>

