<?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: replacement procedure for Oneview managed Flex 10 / flex 10D Virtual connect module in BladeSystem - General</title>
    <link>https://community.hpe.com/t5/bladesystem-general/replacement-procedure-for-oneview-managed-flex-10-flex-10d/m-p/7255619#M34777</link>
    <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.hpe.com/t5/user/viewprofilepage/user-id/2044624"&gt;@AndrewR2&lt;/a&gt;&amp;nbsp;,&lt;BR /&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp;Please follow these-&lt;BR /&gt;a.&amp;nbsp; Please check whether network configuration issue for Bay 1 and Bay 2 or the VC Modules are failed.&amp;nbsp;&amp;nbsp;&lt;BR /&gt;b.&amp;nbsp; Please check LEDs notification on VC, Is it detecting in OneView?&lt;BR /&gt;c.&amp;nbsp; If you are sure that the VC module is failed. Call HPE support and get the new compatible module and install it.&lt;BR /&gt;d. Please check the new module is listing in OneView. Configure the IP address.&lt;BR /&gt;Regards,&lt;BR /&gt;Shiva_jr&lt;/P&gt;</description>
    <pubDate>Wed, 10 Sep 2025 11:20:44 GMT</pubDate>
    <dc:creator>shiva_jr</dc:creator>
    <dc:date>2025-09-10T11:20:44Z</dc:date>
    <item>
      <title>replacement procedure for Oneview managed Flex 10 / flex 10D Virtual connect module</title>
      <link>https://community.hpe.com/t5/bladesystem-general/replacement-procedure-for-oneview-managed-flex-10-flex-10d/m-p/7255559#M34776</link>
      <description>&lt;P&gt;Afternon all.&lt;/P&gt;&lt;P&gt;I have a C700o chassis rnning several production critical bl460Cgen 9's.&amp;nbsp;&lt;/P&gt;&lt;P&gt;It has 2&amp;nbsp; flex 10 / Flex10d VC modules and the module in Bay 1 is failed with all links down.&amp;nbsp;&lt;/P&gt;&lt;P&gt;VCSU health check had the folloowing output :&amp;nbsp;&lt;/P&gt;&lt;P&gt;(22220)[VcsuCore.cpp:5938] : Failed to get the IP Address for bay 1&lt;BR /&gt;[Tue Sep 09 11:47:03 2025] (22220)[VcsuCore.cpp:5944] : Bay 1 IP Address is *.*.*.* and type is Not Reachable&lt;BR /&gt;[Tue Sep 09 11:47:03 2025] (22220)[VcsuCore.cpp:620] : Failed to get Bay IP address, trying again&lt;BR /&gt;[Tue Sep 09 11:47:25 2025] (22220)[LocalIp.cpp:92] : Failed to connect, errno = 2&lt;BR /&gt;[Tue Sep 09 11:47:25 2025] (22220)[VcsuCore.cpp:5938] : Failed to get the IP Address for bay 1&lt;BR /&gt;[Tue Sep 09 11:47:25 2025] (22220)[VcsuCore.cpp:5944] : Bay 1 IP Address is *.*.*.* and type is Not Reachable&lt;BR /&gt;[Tue Sep 09 11:47:25 2025] (22220)[VcsuCore.cpp:620] : Failed to get Bay IP address, trying again&lt;BR /&gt;[Tue Sep 09 11:47:26 2025] (22220)[VcsuCore.cpp:633] : Get Bay IP call failed all retries&lt;BR /&gt;[Tue Sep 09 11:47:26 2025] (22220)[VcsuCore.cpp:1035] : fillEnetTrayinfo failed&lt;BR /&gt;[Tue Sep 09 11:47:26 2025] (22220)[VcsuCore.cpp:1071] : [GB8930Y2LW:1] Failed to get the Enclosure tray Info&lt;BR /&gt;[Tue Sep 09 11:47:27 2025] (22220)[VcsuCore.cpp:5944] : Bay 2 IP Address is *.*.*.* and type is IPv4&lt;BR /&gt;[Tue Sep 09 11:47:28 2025] (22220)[VcsuSsh.cpp:143] : Connection established to *.*.*.*&lt;BR /&gt;[Tue Sep 09 11:47:28 2025] (22220)[VcsuSsh.cpp:163] : Successfully established session to *.*.*.*&lt;BR /&gt;[Tue Sep 09 11:47:29 2025] (22220)[VcsuCore.cpp:655] : Bay 2 Firmware Version: 4.63 2018-08-21T19:09:38Z&lt;BR /&gt;[Tue Sep 09 11:47:31 2025] (22220)[VcsuCore.cpp:2052] : Module not present in bay 3&lt;BR /&gt;[Tue Sep 09 11:47:32 2025] (22220)[VcsuCore.cpp:2052] : Module not present in bay 4&lt;BR /&gt;[Tue Sep 09 11:47:34 2025] (22220)[VcsuCore.cpp:2052] : Module not present in bay 5&lt;BR /&gt;[Tue Sep 09 11:47:34 2025] (22220)[VcsuCore.cpp:2052] : Module not present in bay 6&lt;BR /&gt;[Tue Sep 09 11:47:35 2025] (22220)[VcsuCore.cpp:2052] : Module not present in bay 7&lt;BR /&gt;[Tue Sep 09 11:47:36 2025] (22220)[VcsuCore.cpp:2052] : Module not present in bay 8&lt;BR /&gt;[Tue Sep 09 11:47:36 2025] (22220)[VcsuCore.cpp:1117] : Domain configuration is present&lt;BR /&gt;[Tue Sep 09 11:49:36 2025] (22220)[VcsuCore.cpp:1131] : This is primary enclosure&lt;/P&gt;&lt;P&gt;I would like to know the process for replacing the failed VC including what I will need to do to ensure it is properlly configured by oneview once the physical replacement has occured.&amp;nbsp;&lt;/P&gt;&lt;P&gt;I would also like to know if any of this would be disruptive or not.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks in advance for the info..&lt;/P&gt;&lt;P&gt;Andrew&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 11 Sep 2025 04:32:04 GMT</pubDate>
      <guid>https://community.hpe.com/t5/bladesystem-general/replacement-procedure-for-oneview-managed-flex-10-flex-10d/m-p/7255559#M34776</guid>
      <dc:creator>AndrewR2</dc:creator>
      <dc:date>2025-09-11T04:32:04Z</dc:date>
    </item>
    <item>
      <title>Re: replacement procedure for Oneview managed Flex 10 / flex 10D Virtual connect module</title>
      <link>https://community.hpe.com/t5/bladesystem-general/replacement-procedure-for-oneview-managed-flex-10-flex-10d/m-p/7255619#M34777</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.hpe.com/t5/user/viewprofilepage/user-id/2044624"&gt;@AndrewR2&lt;/a&gt;&amp;nbsp;,&lt;BR /&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp;Please follow these-&lt;BR /&gt;a.&amp;nbsp; Please check whether network configuration issue for Bay 1 and Bay 2 or the VC Modules are failed.&amp;nbsp;&amp;nbsp;&lt;BR /&gt;b.&amp;nbsp; Please check LEDs notification on VC, Is it detecting in OneView?&lt;BR /&gt;c.&amp;nbsp; If you are sure that the VC module is failed. Call HPE support and get the new compatible module and install it.&lt;BR /&gt;d. Please check the new module is listing in OneView. Configure the IP address.&lt;BR /&gt;Regards,&lt;BR /&gt;Shiva_jr&lt;/P&gt;</description>
      <pubDate>Wed, 10 Sep 2025 11:20:44 GMT</pubDate>
      <guid>https://community.hpe.com/t5/bladesystem-general/replacement-procedure-for-oneview-managed-flex-10-flex-10d/m-p/7255619#M34777</guid>
      <dc:creator>shiva_jr</dc:creator>
      <dc:date>2025-09-10T11:20:44Z</dc:date>
    </item>
    <item>
      <title>Re: replacement procedure for Oneview managed Flex 10 / flex 10D Virtual connect module</title>
      <link>https://community.hpe.com/t5/bladesystem-general/replacement-procedure-for-oneview-managed-flex-10-flex-10d/m-p/7255747#M34781</link>
      <description>&lt;P&gt;HI&amp;nbsp;&lt;a href="https://community.hpe.com/t5/user/viewprofilepage/user-id/2067433"&gt;@shiva_jr&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Replaced the module after confirming it was definitelly failed by reseating it several times and the ip address was configured by EBIPA.&lt;/P&gt;&lt;P&gt;The rest of the configuration was automated by Oneview so was much less complicated than I thought it would be.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 12 Sep 2025 15:03:53 GMT</pubDate>
      <guid>https://community.hpe.com/t5/bladesystem-general/replacement-procedure-for-oneview-managed-flex-10-flex-10d/m-p/7255747#M34781</guid>
      <dc:creator>AndrewR2</dc:creator>
      <dc:date>2025-09-12T15:03:53Z</dc:date>
    </item>
  </channel>
</rss>

