<?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: What is Subordinate VC Module ? in BladeSystem - General</title>
    <link>https://community.hpe.com/t5/bladesystem-general/what-is-subordinate-vc-module/m-p/6877728#M29974</link>
    <description>&lt;P&gt;Thanks for the reply !!&amp;nbsp;&lt;/P&gt;&lt;P&gt;Instead of automatic sequence, we are thinking about running the reboot in manual mode, using the following command -&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;vcsu -a update -i &amp;lt;enclosure OA IP&amp;gt; -u &amp;lt;OA username&amp;gt; -p &amp;lt;OA password&amp;gt; -vcu &amp;lt;VC domain user&amp;gt; -vcp &amp;lt;VC domain password&amp;gt; -l &amp;lt;firmware image path&amp;gt; &lt;U&gt;-oe manual -of manual&lt;/U&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;Therefore, the order of reboot of VC's would fall as &amp;nbsp;-&amp;nbsp;&lt;/P&gt;&lt;P&gt;Backup config&lt;BR /&gt;Healthcheck&lt;BR /&gt;vcsu -a update -i ..... &amp;nbsp; &amp;nbsp;(above command)&lt;BR /&gt;Reset Bay2 (standby)&lt;BR /&gt;Healthcheck&lt;BR /&gt;Reset Bay1&lt;BR /&gt;Healthcheck&lt;BR /&gt;Reset Bay 4&lt;BR /&gt;Healthcheck&lt;BR /&gt;Reset Bay 3&lt;/P&gt;&lt;P&gt;Is there any problem in above choice ?&amp;nbsp;&lt;/P&gt;&lt;P&gt;Just want to ensure that we wont have a network interruption by following the above steps - customer doesnt want even few seconds of outage :)&amp;nbsp;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Wed, 13 Jul 2016 03:39:14 GMT</pubDate>
    <dc:creator>grinningdevil</dc:creator>
    <dc:date>2016-07-13T03:39:14Z</dc:date>
    <item>
      <title>What is Subordinate VC Module ?</title>
      <link>https://community.hpe.com/t5/bladesystem-general/what-is-subordinate-vc-module/m-p/6877316#M29972</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;For one of my customer, we have the following config -&amp;nbsp;&lt;/P&gt;&lt;P&gt;1 * Primary Virtual Connect Module&amp;nbsp;&lt;/P&gt;&lt;P&gt;1 * Backup Virtual Connect Module&amp;nbsp;&lt;/P&gt;&lt;P&gt;2 * Subordinate Virtual Connect Module&amp;nbsp;&lt;/P&gt;&lt;P&gt;Presently all are running with firmware version 3.70 , and I need to update them.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Question -&amp;nbsp;&lt;/P&gt;&lt;P&gt;- What are these subordinate VCM 's ? &amp;nbsp;When I go to their IP for login, I am redirected to Primary VC Module automatically.&amp;nbsp;&lt;/P&gt;&lt;P&gt;- Since I am not able to login to subordinate VCM's, how would I update firmware ? &amp;nbsp;&lt;/P&gt;&lt;P&gt;- Globally, for all four VC's, what is the sequence to follow for upgrading firmware ? first get suboridnate upgraded, then backup and then primary ??&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 12 Jul 2016 04:39:30 GMT</pubDate>
      <guid>https://community.hpe.com/t5/bladesystem-general/what-is-subordinate-vc-module/m-p/6877316#M29972</guid>
      <dc:creator>grinningdevil</dc:creator>
      <dc:date>2016-07-12T04:39:30Z</dc:date>
    </item>
    <item>
      <title>Re: What is Subordinate VC Module ?</title>
      <link>https://community.hpe.com/t5/bladesystem-general/what-is-subordinate-vc-module/m-p/6877552#M29973</link>
      <description>&lt;P&gt;In a Virtual Connect environment there are two VC modules that run the Virtual Connect Manager. &amp;nbsp;The primary and the secondary as you have noted. &amp;nbsp;Any other VC module in that domain would be considered subordinate. &amp;nbsp;Those VC modules do not run the VCM software, but only handle the I/O traffic.&lt;/P&gt;&lt;P&gt;When you perform a firmware update, the update process will see all VC modules and update them accordingly. &amp;nbsp;The update scripts will default to update each module alternately, but you can change this to update them in parallel or in a certain order. &amp;nbsp;In most cases, its best to take the defaults.&lt;/P&gt;&lt;P&gt;-Bob&lt;/P&gt;</description>
      <pubDate>Tue, 12 Jul 2016 16:19:58 GMT</pubDate>
      <guid>https://community.hpe.com/t5/bladesystem-general/what-is-subordinate-vc-module/m-p/6877552#M29973</guid>
      <dc:creator>Robert_Jewell</dc:creator>
      <dc:date>2016-07-12T16:19:58Z</dc:date>
    </item>
    <item>
      <title>Re: What is Subordinate VC Module ?</title>
      <link>https://community.hpe.com/t5/bladesystem-general/what-is-subordinate-vc-module/m-p/6877728#M29974</link>
      <description>&lt;P&gt;Thanks for the reply !!&amp;nbsp;&lt;/P&gt;&lt;P&gt;Instead of automatic sequence, we are thinking about running the reboot in manual mode, using the following command -&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;vcsu -a update -i &amp;lt;enclosure OA IP&amp;gt; -u &amp;lt;OA username&amp;gt; -p &amp;lt;OA password&amp;gt; -vcu &amp;lt;VC domain user&amp;gt; -vcp &amp;lt;VC domain password&amp;gt; -l &amp;lt;firmware image path&amp;gt; &lt;U&gt;-oe manual -of manual&lt;/U&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;Therefore, the order of reboot of VC's would fall as &amp;nbsp;-&amp;nbsp;&lt;/P&gt;&lt;P&gt;Backup config&lt;BR /&gt;Healthcheck&lt;BR /&gt;vcsu -a update -i ..... &amp;nbsp; &amp;nbsp;(above command)&lt;BR /&gt;Reset Bay2 (standby)&lt;BR /&gt;Healthcheck&lt;BR /&gt;Reset Bay1&lt;BR /&gt;Healthcheck&lt;BR /&gt;Reset Bay 4&lt;BR /&gt;Healthcheck&lt;BR /&gt;Reset Bay 3&lt;/P&gt;&lt;P&gt;Is there any problem in above choice ?&amp;nbsp;&lt;/P&gt;&lt;P&gt;Just want to ensure that we wont have a network interruption by following the above steps - customer doesnt want even few seconds of outage :)&amp;nbsp;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 13 Jul 2016 03:39:14 GMT</pubDate>
      <guid>https://community.hpe.com/t5/bladesystem-general/what-is-subordinate-vc-module/m-p/6877728#M29974</guid>
      <dc:creator>grinningdevil</dc:creator>
      <dc:date>2016-07-13T03:39:14Z</dc:date>
    </item>
  </channel>
</rss>

