<?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: VC-FC module replacement in BladeSystem - General</title>
    <link>https://community.hpe.com/t5/bladesystem-general/vc-fc-module-replacement/m-p/4661374#M10909</link>
    <description>If the firmware on your new model is not the same then you will start getting :firmware mismatch" messages and the module will not join the VC Domain.&lt;BR /&gt;&lt;BR /&gt;If you have the firmware image for version 1.24, then you can (normally) downgrade the module to the same as the others, (although 1.24 might be too much of a downgrade, never tried it.).&lt;BR /&gt;&lt;BR /&gt;However you should seriously consider UpGrading your existing VC modules.   Version 1.24 is veeerrrrry old.   The current version is 2.33.&lt;BR /&gt;&lt;BR /&gt;Dave.</description>
    <pubDate>Wed, 14 Jul 2010 16:14:52 GMT</pubDate>
    <dc:creator>The Brit</dc:creator>
    <dc:date>2010-07-14T16:14:52Z</dc:date>
    <item>
      <title>VC-FC module replacement</title>
      <link>https://community.hpe.com/t5/bladesystem-general/vc-fc-module-replacement/m-p/4661373#M10908</link>
      <description>Dear All,&lt;BR /&gt;&lt;BR /&gt;We have the below configuration&lt;BR /&gt;&lt;BR /&gt;C-7000 Encl&lt;BR /&gt;2-Full height Server&lt;BR /&gt;12- Half height Server&lt;BR /&gt;Interconnect Bays &lt;BR /&gt;Bay  Type       &lt;BR /&gt;1    VC-ENET                &lt;BR /&gt;2    VC-ENET            &lt;BR /&gt;5    VC-ENET         &lt;BR /&gt;6    VC-ENET                &lt;BR /&gt;7    VC-ENET               &lt;BR /&gt;8    VC-ENET               &lt;BR /&gt;3    VC-FC          &lt;BR /&gt;4    VC-FC&lt;BR /&gt;&lt;BR /&gt;the bay 4 has VC-FC on which the uplink port X1 is faulty due to which we need to replace it&lt;BR /&gt;&lt;BR /&gt;the fimware on the current VC-Ethernet &amp;amp; fibre channel are 1.24 &amp;amp; 1.11&lt;BR /&gt;&lt;BR /&gt;the replacement which we will get will have a firmware with a new version, under such situation how will the VC-FC synchronise with the other interconnect bays having old version firmware.&lt;BR /&gt;&lt;BR /&gt;Would appreciate your response on the above.</description>
      <pubDate>Wed, 14 Jul 2010 15:14:12 GMT</pubDate>
      <guid>https://community.hpe.com/t5/bladesystem-general/vc-fc-module-replacement/m-p/4661373#M10908</guid>
      <dc:creator>farhat_1</dc:creator>
      <dc:date>2010-07-14T15:14:12Z</dc:date>
    </item>
    <item>
      <title>Re: VC-FC module replacement</title>
      <link>https://community.hpe.com/t5/bladesystem-general/vc-fc-module-replacement/m-p/4661374#M10909</link>
      <description>If the firmware on your new model is not the same then you will start getting :firmware mismatch" messages and the module will not join the VC Domain.&lt;BR /&gt;&lt;BR /&gt;If you have the firmware image for version 1.24, then you can (normally) downgrade the module to the same as the others, (although 1.24 might be too much of a downgrade, never tried it.).&lt;BR /&gt;&lt;BR /&gt;However you should seriously consider UpGrading your existing VC modules.   Version 1.24 is veeerrrrry old.   The current version is 2.33.&lt;BR /&gt;&lt;BR /&gt;Dave.</description>
      <pubDate>Wed, 14 Jul 2010 16:14:52 GMT</pubDate>
      <guid>https://community.hpe.com/t5/bladesystem-general/vc-fc-module-replacement/m-p/4661374#M10909</guid>
      <dc:creator>The Brit</dc:creator>
      <dc:date>2010-07-14T16:14:52Z</dc:date>
    </item>
    <item>
      <title>Re: VC-FC module replacement</title>
      <link>https://community.hpe.com/t5/bladesystem-general/vc-fc-module-replacement/m-p/4661375#M10910</link>
      <description>the present VC Domain is managed by Virtual Connect Enterprise Manager (VCEM) and in it the below procedure is mentioned can I do the replacement of the VC-FC by the below&lt;BR /&gt;&lt;BR /&gt;Replace VC modules in a VC Domain managed by VCEM&lt;BR /&gt;To replace a VC Ethernet module or a VC Fibre Channel module of a VC Domain managed by VCEM,&lt;BR /&gt;perform the following:&lt;BR /&gt;1. From the VCEM home page, click the VC Domains tab.&lt;BR /&gt;2. Select the VC Domain with the VC modules to be replaced.&lt;BR /&gt;3. Click Remove from VC Domain Group. Wait for the job to complete successfully.&lt;BR /&gt;4. Replace the VC modules from the enclosure reader interconnect bays. Verify that the network and SAN&lt;BR /&gt;connections that are wired to the new VC modules are the same as the old connections.&lt;BR /&gt;5. If the primary VC Ethernet module was replaced, then you must configure the VC Domain again through&lt;BR /&gt;virtual Connect. For more information about configuring the VC Domain, see the HP virtual connect for&lt;BR /&gt;c-Class BladeSystem User Guide.&lt;BR /&gt;6. Access the Onboard Administrator web interface for the enclosure to verify that the VC Domain link in&lt;BR /&gt;the bottom left portion of the screen correctly points to the VC Domain Manager IP address.&lt;BR /&gt;7. Perform an HP SIM discovery against the Onboard Administrator IP address.&lt;BR /&gt;8. From the VCEM home page, click the VC Domains tab.&lt;BR /&gt;9. Select the same VC Domain, and then click Add to VC Domain Group. Wait for the job to complete&lt;BR /&gt;successfully.&lt;BR /&gt;Verify that the VC Domain meets the requirements for adding a VC Domain to a VC Domain Group.&lt;BR /&gt;For more information, see Requirements for adding a VC Domain to a VC Domain Group.&lt;BR /&gt;&lt;BR /&gt;well has someone tried with the above steps to replace the VC_FC</description>
      <pubDate>Wed, 14 Jul 2010 16:48:44 GMT</pubDate>
      <guid>https://community.hpe.com/t5/bladesystem-general/vc-fc-module-replacement/m-p/4661375#M10910</guid>
      <dc:creator>farhat_1</dc:creator>
      <dc:date>2010-07-14T16:48:44Z</dc:date>
    </item>
  </channel>
</rss>

