<?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: Update Virtual Connect Manager in a stacked environment in BladeSystem - General</title>
    <link>https://community.hpe.com/t5/bladesystem-general/update-virtual-connect-manager-in-a-stacked-environment/m-p/4688987#M11450</link>
    <description>1.5.1 is the latest. By default (interactive mode) will reboot modules parallel so there should always be network. Of course if You have not created redundant networks the situation is different</description>
    <pubDate>Wed, 22 Sep 2010 11:38:26 GMT</pubDate>
    <dc:creator>JKytsi</dc:creator>
    <dc:date>2010-09-22T11:38:26Z</dc:date>
    <item>
      <title>Update Virtual Connect Manager in a stacked environment</title>
      <link>https://community.hpe.com/t5/bladesystem-general/update-virtual-connect-manager-in-a-stacked-environment/m-p/4688982#M11445</link>
      <description>I have two c7000 enclosures with Flex-10 modules.  I have connected the two enclosures via the Flex-10's in a "stacked" environment.  I need to update Virtual Connect Manager.  When I use vcsu to update one of the Flex-10's it gives me an error saying I have to do all of them at once. If I do all of them at once will this cause a network outage?  My current versions are OA=3.00 VCM=2.32  Want to go to OA=3.11 VCM=3.01&lt;BR /&gt;&lt;BR /&gt;Thanks,&lt;BR /&gt;&lt;BR /&gt;Bob&lt;BR /&gt;</description>
      <pubDate>Mon, 20 Sep 2010 17:29:09 GMT</pubDate>
      <guid>https://community.hpe.com/t5/bladesystem-general/update-virtual-connect-manager-in-a-stacked-environment/m-p/4688982#M11445</guid>
      <dc:creator>Robert Cook_6</dc:creator>
      <dc:date>2010-09-20T17:29:09Z</dc:date>
    </item>
    <item>
      <title>Re: Update Virtual Connect Manager in a stacked environment</title>
      <link>https://community.hpe.com/t5/bladesystem-general/update-virtual-connect-manager-in-a-stacked-environment/m-p/4688983#M11446</link>
      <description>Hello Bob, &lt;BR /&gt;&lt;BR /&gt;When I use the VCSU Stacked or otherwise it always copies the FW to one of the modules updates it and fails to the next to update it. There shouldn't be a need to take them down two at once. Especially if you're stacked on both sides. &lt;BR /&gt;&lt;BR /&gt;Can you attach a screenshot of the error maybe?&lt;BR /&gt;&lt;BR /&gt;Dan</description>
      <pubDate>Mon, 20 Sep 2010 19:04:12 GMT</pubDate>
      <guid>https://community.hpe.com/t5/bladesystem-general/update-virtual-connect-manager-in-a-stacked-environment/m-p/4688983#M11446</guid>
      <dc:creator>Daniel A. Alonso</dc:creator>
      <dc:date>2010-09-20T19:04:12Z</dc:date>
    </item>
    <item>
      <title>Re: Update Virtual Connect Manager in a stacked environment</title>
      <link>https://community.hpe.com/t5/bladesystem-general/update-virtual-connect-manager-in-a-stacked-environment/m-p/4688984#M11447</link>
      <description>Dan,&lt;BR /&gt;     This is a production environment so I can't recreate the output until this Sunday.  The command I used from my laptop on the network was: &lt;BR /&gt; &lt;BR /&gt;"vcsa -a update -i 10.11.2.150 -u Administrator -p xxxxx -vcu Administrator -vcp xxxxx -l c:\firmware\vcfwall301.bin -b 1". &lt;BR /&gt; &lt;BR /&gt;Now that I read the help on the command it appears that I should not have used the "-b 1" parameter.&lt;BR /&gt;&lt;BR /&gt;Bob&lt;BR /&gt;</description>
      <pubDate>Mon, 20 Sep 2010 19:26:35 GMT</pubDate>
      <guid>https://community.hpe.com/t5/bladesystem-general/update-virtual-connect-manager-in-a-stacked-environment/m-p/4688984#M11447</guid>
      <dc:creator>Robert Cook_6</dc:creator>
      <dc:date>2010-09-20T19:26:35Z</dc:date>
    </item>
    <item>
      <title>Re: Update Virtual Connect Manager in a stacked environment</title>
      <link>https://community.hpe.com/t5/bladesystem-general/update-virtual-connect-manager-in-a-stacked-environment/m-p/4688985#M11448</link>
      <description>Are You using the latest support utility ? You could try the interactive mode from it.</description>
      <pubDate>Tue, 21 Sep 2010 17:17:37 GMT</pubDate>
      <guid>https://community.hpe.com/t5/bladesystem-general/update-virtual-connect-manager-in-a-stacked-environment/m-p/4688985#M11448</guid>
      <dc:creator>JKytsi</dc:creator>
      <dc:date>2010-09-21T17:17:37Z</dc:date>
    </item>
    <item>
      <title>Re: Update Virtual Connect Manager in a stacked environment</title>
      <link>https://community.hpe.com/t5/bladesystem-general/update-virtual-connect-manager-in-a-stacked-environment/m-p/4688986#M11449</link>
      <description>I believe it is the latest Version 1.5.0. I have not tried it in interactive mode.  My concern is that I will take both c7000 enclosures off the network when I do the update.  Do you know if it is smart enough to keep the network up?&lt;BR /&gt;&lt;BR /&gt;Bob</description>
      <pubDate>Tue, 21 Sep 2010 18:00:34 GMT</pubDate>
      <guid>https://community.hpe.com/t5/bladesystem-general/update-virtual-connect-manager-in-a-stacked-environment/m-p/4688986#M11449</guid>
      <dc:creator>Robert Cook_6</dc:creator>
      <dc:date>2010-09-21T18:00:34Z</dc:date>
    </item>
    <item>
      <title>Re: Update Virtual Connect Manager in a stacked environment</title>
      <link>https://community.hpe.com/t5/bladesystem-general/update-virtual-connect-manager-in-a-stacked-environment/m-p/4688987#M11450</link>
      <description>1.5.1 is the latest. By default (interactive mode) will reboot modules parallel so there should always be network. Of course if You have not created redundant networks the situation is different</description>
      <pubDate>Wed, 22 Sep 2010 11:38:26 GMT</pubDate>
      <guid>https://community.hpe.com/t5/bladesystem-general/update-virtual-connect-manager-in-a-stacked-environment/m-p/4688987#M11450</guid>
      <dc:creator>JKytsi</dc:creator>
      <dc:date>2010-09-22T11:38:26Z</dc:date>
    </item>
  </channel>
</rss>

