<?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 IMC Deploy device software ISSU in IMC</title>
    <link>https://community.hpe.com/t5/imc/imc-deploy-device-software-issu/m-p/6974635#M4007</link>
    <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;I'm trying to use Deploy Software on device using ISSU feature on IMC.&lt;/P&gt;&lt;P&gt;The goal is to upgrade a stack of 4 units.&lt;/P&gt;&lt;P&gt;I did the deployment and the entire stack was succesfully upgraded by IMC unsing ISSU.&lt;/P&gt;&lt;P&gt;However, IMC reboot 2 switches of four (in my case) in the same time. So, the upgarde is done in the 2 first switches and then in the 2 last switches. How can we control the order IMC do the upgarde ?&lt;/P&gt;&lt;P&gt;Should IMC upgrade the switches with ISSU one after one in order to garantee the high availability ?&lt;/P&gt;&lt;P&gt;For example, I have a stack of 4 units, in my core switch and the link-aggregation to the access switches are made on the unit 3 and unit 4. I want to control the upgrade process to be sure the unit 3 and unit are not rebooted at the same time. In the lab I prepared to test this functionnality, the uni3 and unit4 were rebooted at the same time.&lt;/P&gt;&lt;P&gt;I dind't find information on the guide&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;David&lt;/P&gt;</description>
    <pubDate>Wed, 23 Aug 2017 09:36:36 GMT</pubDate>
    <dc:creator>Daddy72</dc:creator>
    <dc:date>2017-08-23T09:36:36Z</dc:date>
    <item>
      <title>IMC Deploy device software ISSU</title>
      <link>https://community.hpe.com/t5/imc/imc-deploy-device-software-issu/m-p/6974635#M4007</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;I'm trying to use Deploy Software on device using ISSU feature on IMC.&lt;/P&gt;&lt;P&gt;The goal is to upgrade a stack of 4 units.&lt;/P&gt;&lt;P&gt;I did the deployment and the entire stack was succesfully upgraded by IMC unsing ISSU.&lt;/P&gt;&lt;P&gt;However, IMC reboot 2 switches of four (in my case) in the same time. So, the upgarde is done in the 2 first switches and then in the 2 last switches. How can we control the order IMC do the upgarde ?&lt;/P&gt;&lt;P&gt;Should IMC upgrade the switches with ISSU one after one in order to garantee the high availability ?&lt;/P&gt;&lt;P&gt;For example, I have a stack of 4 units, in my core switch and the link-aggregation to the access switches are made on the unit 3 and unit 4. I want to control the upgrade process to be sure the unit 3 and unit are not rebooted at the same time. In the lab I prepared to test this functionnality, the uni3 and unit4 were rebooted at the same time.&lt;/P&gt;&lt;P&gt;I dind't find information on the guide&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;David&lt;/P&gt;</description>
      <pubDate>Wed, 23 Aug 2017 09:36:36 GMT</pubDate>
      <guid>https://community.hpe.com/t5/imc/imc-deploy-device-software-issu/m-p/6974635#M4007</guid>
      <dc:creator>Daddy72</dc:creator>
      <dc:date>2017-08-23T09:36:36Z</dc:date>
    </item>
    <item>
      <title>Re: IMC Deploy device software ISSU</title>
      <link>https://community.hpe.com/t5/imc/imc-deploy-device-software-issu/m-p/6976661#M4062</link>
      <description>&lt;P&gt;If no information in the field is available, then I will ask the HPE PLM and come back, if I got an answer.&lt;/P&gt;</description>
      <pubDate>Fri, 15 Sep 2017 10:19:37 GMT</pubDate>
      <guid>https://community.hpe.com/t5/imc/imc-deploy-device-software-issu/m-p/6976661#M4062</guid>
      <dc:creator>ibias</dc:creator>
      <dc:date>2017-09-15T10:19:37Z</dc:date>
    </item>
  </channel>
</rss>

