<?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 Problem with latest drivers for DL380 G7 in Operating System - VMware</title>
    <link>https://community.hpe.com/t5/operating-system-vmware/problem-with-latest-drivers-for-dl380-g7/m-p/6457008#M1983</link>
    <description>&lt;P&gt;I have three of these servers running ESXi 5.5 (ent+) with Emulex LPe11000 FC HBAs attached to two P2000 G3 MSAs.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The latest round of updates in VUM has a new driver for the HBAs which does not actually work with them.&amp;nbsp; Upon installing the lpfc update (VMW-ESX-5.5.0-lpfc-10.0.727.44) the FC HBAs are no longer detected by vmware.&amp;nbsp; The only way to restore access to the FC SAN, short of reinstalling ESX (which I've done on one host *several* times to try and narrow down the problem) is to use esxcli to uninstall the lpfc VIB, which reverts it back to the one that ships from VMWare (10.0.100.1-1vmw.550.0.0.1331820).&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I've been trying to track down exactly what updates or combination of updates causes the problem and have been unsuccessful.&amp;nbsp; I have reinstalled ESX on all three hosts over the course of this week.&amp;nbsp; I have one "vanilla" host (esxi01) with no updates applied, working properly.&amp;nbsp; I have another (esxi02) that has been updated with VUM to the latest set of updates, patches, and extensions which also works properly.&amp;nbsp; The final host (esxi03), which I began updating exactly as I did with esxi02 lost connectivity to the SAN as described.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;To eliminate any weird VUM conflicts or problems I tried using the HP supplied ESXi 5.5 ISOs, both VMware-ESXi-5.5.0-1331820-HP-5.72.27-Feb2014.iso and VMware-ESXi-5.5.0-Update1-1623387-HP-5.73.21-Mar2014.iso and both of them have the same problem right out of the gate -- no FC SAN connectivity.&amp;nbsp; Additionally, they both fail to start vmnic0 but start 1-3 just fine.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Something is wrong with the latest round of updates..&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Thu, 24 Apr 2014 17:55:34 GMT</pubDate>
    <dc:creator>alandsidel</dc:creator>
    <dc:date>2014-04-24T17:55:34Z</dc:date>
    <item>
      <title>Problem with latest drivers for DL380 G7</title>
      <link>https://community.hpe.com/t5/operating-system-vmware/problem-with-latest-drivers-for-dl380-g7/m-p/6457008#M1983</link>
      <description>&lt;P&gt;I have three of these servers running ESXi 5.5 (ent+) with Emulex LPe11000 FC HBAs attached to two P2000 G3 MSAs.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The latest round of updates in VUM has a new driver for the HBAs which does not actually work with them.&amp;nbsp; Upon installing the lpfc update (VMW-ESX-5.5.0-lpfc-10.0.727.44) the FC HBAs are no longer detected by vmware.&amp;nbsp; The only way to restore access to the FC SAN, short of reinstalling ESX (which I've done on one host *several* times to try and narrow down the problem) is to use esxcli to uninstall the lpfc VIB, which reverts it back to the one that ships from VMWare (10.0.100.1-1vmw.550.0.0.1331820).&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I've been trying to track down exactly what updates or combination of updates causes the problem and have been unsuccessful.&amp;nbsp; I have reinstalled ESX on all three hosts over the course of this week.&amp;nbsp; I have one "vanilla" host (esxi01) with no updates applied, working properly.&amp;nbsp; I have another (esxi02) that has been updated with VUM to the latest set of updates, patches, and extensions which also works properly.&amp;nbsp; The final host (esxi03), which I began updating exactly as I did with esxi02 lost connectivity to the SAN as described.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;To eliminate any weird VUM conflicts or problems I tried using the HP supplied ESXi 5.5 ISOs, both VMware-ESXi-5.5.0-1331820-HP-5.72.27-Feb2014.iso and VMware-ESXi-5.5.0-Update1-1623387-HP-5.73.21-Mar2014.iso and both of them have the same problem right out of the gate -- no FC SAN connectivity.&amp;nbsp; Additionally, they both fail to start vmnic0 but start 1-3 just fine.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Something is wrong with the latest round of updates..&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 24 Apr 2014 17:55:34 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-vmware/problem-with-latest-drivers-for-dl380-g7/m-p/6457008#M1983</guid>
      <dc:creator>alandsidel</dc:creator>
      <dc:date>2014-04-24T17:55:34Z</dc:date>
    </item>
    <item>
      <title>Re: Problem with latest drivers for DL380 G7</title>
      <link>https://community.hpe.com/t5/operating-system-vmware/problem-with-latest-drivers-for-dl380-g7/m-p/6458204#M1984</link>
      <description>&lt;P&gt;Just an update, what I've found is that an LPe11002 will not work with the latest drivers unless it's also on the latest firmware, but an LPe11000 will.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I don't know if these are both rebranded to the same HP model # and that's why they're not being picked up or what, but once I was able to get the firmware updated on the host with the LPe11002, the latest emulex drivers an CIM (and oneCommand) are working fine on that host.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Getting the firmware flashed is a chore in itself.&amp;nbsp; I finally got it done by booting a CentOS LiveCD via iLO and downloading the appropriate emulex drivers and tools, and flashing it from there.&lt;/P&gt;</description>
      <pubDate>Sat, 26 Apr 2014 00:29:02 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-vmware/problem-with-latest-drivers-for-dl380-g7/m-p/6458204#M1984</guid>
      <dc:creator>alandsidel</dc:creator>
      <dc:date>2014-04-26T00:29:02Z</dc:date>
    </item>
  </channel>
</rss>

