<?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 Lifecycle Manager - pin old VIB? in VMware vSphere™ Discussions</title>
    <link>https://communities.vmware.com/t5/VMware-vSphere-Discussions/Lifecycle-Manager-pin-old-VIB/m-p/2945279#M44091</link>
    <description>&lt;P&gt;I have a couple of HPE DL380 servers which have been running v7.0.2 for a while and after reading reports these can run v7.0.3, albeit with warnings about officially unsupported CPUs, I took the plunge on one of the servers. But I'm running into an issue where I suspect that Lifecycle Manager is not allowing me to maintain an old driver for an Intel P4500 NVMe.&lt;/P&gt;&lt;P&gt;Driver 2.6.0 works, but 2.7.0&amp;nbsp; and up require a C620 chipset which my gen8 and gen9 servers do not have. Manually installing the VIB works after uninstalling the v2.7.x VIB. But I suspect Lifecycle Manager will want to revert this VIB.&lt;/P&gt;&lt;P&gt;Lifecycle Manager (vSphere client v7.0 U3c) is being very odd about additional drivers, as I'm seeing cosmetic glitches and it's refusing to add the v2.6.0 or v2.6.1 Inte;l NVMe driver to the baseline. But doesn't show any errors, it just silently completes without adding the driver to the baseline.&lt;/P&gt;&lt;P&gt;Is there a way to pin a VIB or keep an old driver around in a 'newer' baseline? If not I'll just need to manually revert the driver each time I update the cluster.&lt;/P&gt;</description>
    <pubDate>Fri, 23 Dec 2022 16:40:16 GMT</pubDate>
    <dc:creator>dmgeurts</dc:creator>
    <dc:date>2022-12-23T16:40:16Z</dc:date>
    <item>
      <title>Lifecycle Manager - pin old VIB?</title>
      <link>https://communities.vmware.com/t5/VMware-vSphere-Discussions/Lifecycle-Manager-pin-old-VIB/m-p/2945279#M44091</link>
      <description>&lt;P&gt;I have a couple of HPE DL380 servers which have been running v7.0.2 for a while and after reading reports these can run v7.0.3, albeit with warnings about officially unsupported CPUs, I took the plunge on one of the servers. But I'm running into an issue where I suspect that Lifecycle Manager is not allowing me to maintain an old driver for an Intel P4500 NVMe.&lt;/P&gt;&lt;P&gt;Driver 2.6.0 works, but 2.7.0&amp;nbsp; and up require a C620 chipset which my gen8 and gen9 servers do not have. Manually installing the VIB works after uninstalling the v2.7.x VIB. But I suspect Lifecycle Manager will want to revert this VIB.&lt;/P&gt;&lt;P&gt;Lifecycle Manager (vSphere client v7.0 U3c) is being very odd about additional drivers, as I'm seeing cosmetic glitches and it's refusing to add the v2.6.0 or v2.6.1 Inte;l NVMe driver to the baseline. But doesn't show any errors, it just silently completes without adding the driver to the baseline.&lt;/P&gt;&lt;P&gt;Is there a way to pin a VIB or keep an old driver around in a 'newer' baseline? If not I'll just need to manually revert the driver each time I update the cluster.&lt;/P&gt;</description>
      <pubDate>Fri, 23 Dec 2022 16:40:16 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vSphere-Discussions/Lifecycle-Manager-pin-old-VIB/m-p/2945279#M44091</guid>
      <dc:creator>dmgeurts</dc:creator>
      <dc:date>2022-12-23T16:40:16Z</dc:date>
    </item>
  </channel>
</rss>

