<?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: Virtual Connect Update Path from F/W 2.34 to 3.18 in BladeSystem - General</title>
    <link>https://community.hpe.com/t5/bladesystem-general/virtual-connect-update-path-from-f-w-2-34-to-3-18/m-p/5284378#M17440</link>
    <description>Personally, I would use VCSU, and let the utility decide whether the upgrade path is OK.     Also let VCSU do all modules in one pass, it is smart enought to know the correct order in which to do them.&lt;BR /&gt;&lt;BR /&gt;Dave.</description>
    <pubDate>Thu, 09 Jun 2011 16:43:09 GMT</pubDate>
    <dc:creator>The Brit</dc:creator>
    <dc:date>2011-06-09T16:43:09Z</dc:date>
    <item>
      <title>Virtual Connect Update Path from F/W 2.34 to 3.18</title>
      <link>https://community.hpe.com/t5/bladesystem-general/virtual-connect-update-path-from-f-w-2-34-to-3-18/m-p/5284377#M17439</link>
      <description>Good day&lt;BR /&gt;&lt;BR /&gt;Just want confirmation that the below is the correct path when upgrading virtual connect firmware.&lt;BR /&gt;&lt;BR /&gt;1) Only do one virtual connect at a time&lt;BR /&gt;2) Do not skip more that two versions so:&lt;BR /&gt;a - first upgrade from 2.34 to 3.10&lt;BR /&gt;b - second upgrade from 3.10 to 3.18 (current latest)&lt;BR /&gt;&lt;BR /&gt;Cheers!&lt;BR /&gt;</description>
      <pubDate>Thu, 09 Jun 2011 13:34:54 GMT</pubDate>
      <guid>https://community.hpe.com/t5/bladesystem-general/virtual-connect-update-path-from-f-w-2-34-to-3-18/m-p/5284377#M17439</guid>
      <dc:creator>cosonok</dc:creator>
      <dc:date>2011-06-09T13:34:54Z</dc:date>
    </item>
    <item>
      <title>Re: Virtual Connect Update Path from F/W 2.34 to 3.18</title>
      <link>https://community.hpe.com/t5/bladesystem-general/virtual-connect-update-path-from-f-w-2-34-to-3-18/m-p/5284378#M17440</link>
      <description>Personally, I would use VCSU, and let the utility decide whether the upgrade path is OK.     Also let VCSU do all modules in one pass, it is smart enought to know the correct order in which to do them.&lt;BR /&gt;&lt;BR /&gt;Dave.</description>
      <pubDate>Thu, 09 Jun 2011 16:43:09 GMT</pubDate>
      <guid>https://community.hpe.com/t5/bladesystem-general/virtual-connect-update-path-from-f-w-2-34-to-3-18/m-p/5284378#M17440</guid>
      <dc:creator>The Brit</dc:creator>
      <dc:date>2011-06-09T16:43:09Z</dc:date>
    </item>
    <item>
      <title>Re: Virtual Connect Update Path from F/W 2.34 to 3.18</title>
      <link>https://community.hpe.com/t5/bladesystem-general/virtual-connect-update-path-from-f-w-2-34-to-3-18/m-p/5284379#M17441</link>
      <description>Got it confirmed by HP twice. The entry in the question is a supported path.</description>
      <pubDate>Fri, 10 Jun 2011 09:23:15 GMT</pubDate>
      <guid>https://community.hpe.com/t5/bladesystem-general/virtual-connect-update-path-from-f-w-2-34-to-3-18/m-p/5284379#M17441</guid>
      <dc:creator>cosonok</dc:creator>
      <dc:date>2011-06-10T09:23:15Z</dc:date>
    </item>
    <item>
      <title>Re: Virtual Connect Update Path from F/W 2.34 to 3.18</title>
      <link>https://community.hpe.com/t5/bladesystem-general/virtual-connect-update-path-from-f-w-2-34-to-3-18/m-p/5284380#M17442</link>
      <description>As stated in question.</description>
      <pubDate>Fri, 10 Jun 2011 09:24:08 GMT</pubDate>
      <guid>https://community.hpe.com/t5/bladesystem-general/virtual-connect-update-path-from-f-w-2-34-to-3-18/m-p/5284380#M17442</guid>
      <dc:creator>cosonok</dc:creator>
      <dc:date>2011-06-10T09:24:08Z</dc:date>
    </item>
  </channel>
</rss>

