<?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: after replancment system VCF not pass certification in ProLiant Servers (ML,DL,SL)</title>
    <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/after-replancment-system-vcf-not-pass-certification/m-p/7130041#M174258</link>
    <description>&lt;P&gt;&lt;SPAN class="VIiyi"&gt;&lt;SPAN class="JLqJ4b ChMk0b"&gt;&lt;SPAN&gt;The problem started with not being able to access an NVMe disk anymore, HPE support has advised to replace the NVME disk, this was not the solution.&lt;/SPAN&gt;&lt;/SPAN&gt; &lt;SPAN class="JLqJ4b ChMk0b"&gt;&lt;SPAN&gt;Then we replaced the systemboard on the advice of HPE and got these problems&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;</description>
    <pubDate>Thu, 15 Apr 2021 14:52:17 GMT</pubDate>
    <dc:creator>JooKal</dc:creator>
    <dc:date>2021-04-15T14:52:17Z</dc:date>
    <item>
      <title>after replancment system VCF not pass certification</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/after-replancment-system-vcf-not-pass-certification/m-p/7130021#M174253</link>
      <description>&lt;P&gt;&lt;SPAN&gt;After the system baord was replaced the system won not start, because VMware cloud foundation (VCF) no longer passes the certification&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;It look like that the new system board use a other controller on the old board was a SK hynix controller and the new board a Toshiba controller.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 15 Apr 2021 12:07:20 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/after-replancment-system-vcf-not-pass-certification/m-p/7130021#M174253</guid>
      <dc:creator>JooKal</dc:creator>
      <dc:date>2021-04-15T12:07:20Z</dc:date>
    </item>
    <item>
      <title>Re: after replancment system VCF not pass certification</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/after-replancment-system-vcf-not-pass-certification/m-p/7130038#M174256</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;Is this a HPE product?&amp;nbsp; Kindly mention the HPE Server model.&lt;/P&gt;&lt;P&gt;Thank You!&lt;BR /&gt;&lt;A href="https://support.hpe.com/hpesc/public/home" target="_blank"&gt;https://support.hpe.com/hpesc/public/home&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 15 Apr 2021 14:38:31 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/after-replancment-system-vcf-not-pass-certification/m-p/7130038#M174256</guid>
      <dc:creator>Suman_1978</dc:creator>
      <dc:date>2021-04-15T14:38:31Z</dc:date>
    </item>
    <item>
      <title>Re: after replancment system VCF not pass certification</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/after-replancment-system-vcf-not-pass-certification/m-p/7130040#M174257</link>
      <description>&lt;P&gt;The system is a HPE DL380 GEN10&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Product Number :&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN&gt;P19720-B21&lt;/SPAN&gt; &lt;SPAN&gt;Description :&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN&gt;HPE PROLIANT DL380 GEN10 8SFF NC CONFIGURE-TO-ORDER SERVER&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 15 Apr 2021 14:40:42 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/after-replancment-system-vcf-not-pass-certification/m-p/7130040#M174257</guid>
      <dc:creator>JooKal</dc:creator>
      <dc:date>2021-04-15T14:40:42Z</dc:date>
    </item>
    <item>
      <title>Re: after replancment system VCF not pass certification</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/after-replancment-system-vcf-not-pass-certification/m-p/7130041#M174258</link>
      <description>&lt;P&gt;&lt;SPAN class="VIiyi"&gt;&lt;SPAN class="JLqJ4b ChMk0b"&gt;&lt;SPAN&gt;The problem started with not being able to access an NVMe disk anymore, HPE support has advised to replace the NVME disk, this was not the solution.&lt;/SPAN&gt;&lt;/SPAN&gt; &lt;SPAN class="JLqJ4b ChMk0b"&gt;&lt;SPAN&gt;Then we replaced the systemboard on the advice of HPE and got these problems&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 15 Apr 2021 14:52:17 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/after-replancment-system-vcf-not-pass-certification/m-p/7130041#M174258</guid>
      <dc:creator>JooKal</dc:creator>
      <dc:date>2021-04-15T14:52:17Z</dc:date>
    </item>
    <item>
      <title>Re: after replancment system VCF not pass certification</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/after-replancment-system-vcf-not-pass-certification/m-p/7130049#M174259</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;As far as I know, it looks like a VMware configuration issue which might have occurred due to HW changes.&lt;/P&gt;&lt;P&gt;Have you tried to log a case with VMware?&amp;nbsp;&amp;nbsp;&lt;A href="https://kb.vmware.com/s/article/2006985" target="_blank"&gt;https://kb.vmware.com/s/article/2006985&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Thank You!&lt;BR /&gt;&lt;A href="https://support.hpe.com/hpesc/public/home" target="_blank"&gt;https://support.hpe.com/hpesc/public/home&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 15 Apr 2021 15:11:17 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/after-replancment-system-vcf-not-pass-certification/m-p/7130049#M174259</guid>
      <dc:creator>Suman_1978</dc:creator>
      <dc:date>2021-04-15T15:11:17Z</dc:date>
    </item>
    <item>
      <title>Re: after replancment system VCF not pass certification</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/after-replancment-system-vcf-not-pass-certification/m-p/7130133#M174266</link>
      <description>&lt;P&gt;&lt;SPAN class="VIiyi"&gt;&lt;SPAN class="JLqJ4b ChMk0b"&gt;&lt;SPAN&gt;HPE support L2 is now looking at the case, if I heard from L2 I will post it&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 16 Apr 2021 06:23:43 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/after-replancment-system-vcf-not-pass-certification/m-p/7130133#M174266</guid>
      <dc:creator>JooKal</dc:creator>
      <dc:date>2021-04-16T06:23:43Z</dc:date>
    </item>
    <item>
      <title>Re: after replancment system VCF not pass certification</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/after-replancment-system-vcf-not-pass-certification/m-p/7136592#M174794</link>
      <description>&lt;P&gt;The problem is solved with the correct part number of de NVMe drive .&lt;/P&gt;&lt;P&gt;P13833-001&lt;/P&gt;&lt;P&gt;SPS-DRV SSD 3.84TB NVMe RI SC2 DS&lt;/P&gt;&lt;P&gt;Spare part number we have now us in three different system with the same problem on de PCI bus.&lt;/P&gt;</description>
      <pubDate>Fri, 28 May 2021 13:36:18 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/after-replancment-system-vcf-not-pass-certification/m-p/7136592#M174794</guid>
      <dc:creator>JooKal</dc:creator>
      <dc:date>2021-05-28T13:36:18Z</dc:date>
    </item>
    <item>
      <title>Re: after replancment system VCF not pass certification</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/after-replancment-system-vcf-not-pass-certification/m-p/7136593#M174795</link>
      <description>&lt;P&gt;Problem solved&lt;/P&gt;</description>
      <pubDate>Fri, 28 May 2021 13:37:07 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/after-replancment-system-vcf-not-pass-certification/m-p/7136593#M174795</guid>
      <dc:creator>JooKal</dc:creator>
      <dc:date>2021-05-28T13:37:07Z</dc:date>
    </item>
  </channel>
</rss>

