Home > ESX, Flex-10, HP, VMware > New Emulex be2net drivers for ESX(i) 4.x and ESXi 5.x but they’re not supported yet for HP G7 Blades

New Emulex be2net drivers for ESX(i) 4.x and ESXi 5.x but they’re not supported yet for HP G7 Blades

Update: 06 June 2012 – These drivers are now supported by HP – HP G7 Blade new Emulex be2net ESX(i) drivers 4.1.334.0 now supported

Update: 11 May 2012 to amend link and try work out HP support. Apologies I had the wrong ESX(i) version link in the original post and hadn’t properly investigated HP support for  Virtual Connect/FlexFabric which is confusing. Sorry, Sloppy me! 🙁

VMware has released a new Emulex be2net driver version 4.1.334.0 for both ESX(i) 4.x and ESXi 5.x for the Emulex OneConnect 10Gb Ethernet Controller which is used in HP G7 Blades. But, before you get too excited, HP has NOT certified these drivers for use with HP Virtual Connect and FlexFabric…I think.

You see in this page from VMware which was updated on 4 April 2012 the advice is to use the 4.0.306.0 driver for ESX(i) 4.x and 4.0.355.1 for ESXi 5.x
http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2007397

This page however from VMware says for ESXi 5 driver version 4.0.355.1 isn’t supported for HP ProLiant G7 servers. It requires a new firmware version that is not currently available.
http://partnerweb.vmware.com/comp_guide2/detail.php?deviceCategory=io&productid=19067&vcl=true

but I think this is old as the HP advisory has been updated to say the 4.0.355.1 driver is supported
http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c03005737

But in this document which looks like it has been written by HP, the 4.1.334 drivers for both versions ARE supported (but again with different firmware version numbers that don’t really tally up with what has been supported before)
http://partnerweb.vmware.com/programs/hcl/ESX_Flex_config.pdf

I’m thinking that this document may be a little premature as no other HP information has been updated to reflect support for the 4.1.334 drivers

So, just for your information, the 4.1.334 drivers can be downloaded from the following links when they may be supported:

ESX(i) 4.x:
https://my.vmware.com/web/vmware/details?downloadGroup=DT-ESX4041-EMULEX-be2net-413340&productId=230

ESXi 5.x:
https://my.vmware.com/web/vmware/details/dt_esxi50_emulex_be2net_413340/dHRAYndld3diZHBqaA==

But, I’m thinking the currently supported drivers are:

ESX(i) 4.x: version 4.0.306.0
http://downloads.vmware.com/d/details/dt_esxi40_emulex_be2net_403060/ZHcqYnQqaGpiZEBlZA

ESXi 5.x: version 4.0.355.1
https://my.vmware.com/web/vmware/details/dt_esxi50_emulex_be2net_413340/dHRAYndld3diZHBqaA==

I’ve updated my post: HP Virtual Connect Flex-10 & VMware ESX(i) pre-requisites

Categories: ESX, Flex-10, HP, VMware Tags: , , , , ,
  1. orzdude
    May 2nd, 2012 at 12:11 | #1

    New? Isn’t that still the same old supplied driver?

    The HCL also still says that supposedly, neither the builtin driver nor this one would be supported for NC553i:
    http://partnerweb.vmware.com/comp_guide2/detail.php?deviceCategory=io&productid=19067&vcl=true

    The builtin driver was also updated back in December and fixed the Flex10 issues too:
    http://kb.vmware.com/kb/2007675

  2. Ben
    May 3rd, 2012 at 08:35 | #2

    Hi, i have downloaded the driver for esxi4.1 and when i try and install its says the metadata is incorrect, i had a look at the xml and its says it for version 5 or 6? can i just edit this to install on my version of the host?
    Thanks

  3. orzdude
    May 3rd, 2012 at 09:55 | #3

    @Ben
    This driver is for 5.x hosts, for 4.x you need to use this be2net driver:
    https://my.vmware.com/web/vmware/details/dt_esxi40_emulex_be2net_403060/ZHcqYnQqaGpiZEBlZA

    Also see http://kb.vmware.com/kb/2007397.

  4. Remy Zandwijk
    May 4th, 2012 at 16:10 | #4

    Hi. You explicitly write that VMware certified the 4.0.355.1 is certified door ESX 4.x. But the download link revers to an ESX 5.0 version of the driver. And, a kb article on the VMware site clearly states that the 4.0.306.0 driver should be used on ESX 4.1 (http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2007397).

    So I am confused. Are you sure the 4.0.355.1 driver is supported on ESX 4.x?

  5. Remy Zandwijk
    May 4th, 2012 at 16:13 | #5

    @Remy Zandwijk
    Oops, I missed the post of Ben. I also wrote some grammatical rubbish.

  6. Rotem Agmon
    May 4th, 2012 at 17:50 | #6

    The latest drivers that VMware has certified for the Emulex be2net is version 4.1.334.0.

    Please note that HP has yet to certify these drivers for use with HP Virtual Connect/FlexFabric.

    For ESX/ESXi 4.x:
    https://my.vmware.com/web/vmware/details?downloadGroup=DT-ESX4041-EMULEX-be2net-413340&productId=230

    For ESXi 5.0:
    https://my.vmware.com/web/vmware/details/dt_esxi50_emulex_be2net_413340/dHRAYndld3diZHBqaA==

  7. WoodITWork
    May 11th, 2012 at 13:34 | #7

    @Rotem Agmon

    Hi Rotem,

    I’ve updated the post to try and answer the questions but can you please confirm the supported versions as there seems to be some confusion with the various HP/VMware documents.

  8. WoodITWork
    May 11th, 2012 at 13:35 | #8

    @orzdude

    Thanks for spotting the errors, sorry, I made a complete hash of the original post and have updated it with some more information although I still find the support confusing.

  9. Rotem Agmon
    May 13th, 2012 at 14:09 | #9

    Hi Julian,

    I will look into the matter and check for updates on the driver certification process for these new drivers.
    Until further updates , HP supports version 4.0.306.0 for ESX(i) 4.x and version 4.0.355.1 for ESXi 5.x

  10. orzdude
    May 14th, 2012 at 13:08 | #10

    Thanks for updating the post and sorting out the info.

    Yeah, the current state of information around the be2net drivers is extremely confusing and contradictory. I wish VMware (and HP) would publish an up-to-date, detailed document outlining the real current support policy or at least fix the contradicting statements that are all over the place.

  11. Ben
    May 17th, 2012 at 14:17 | #11

    Hi Thanks for the update, i have a support call open with HP and they have asked me to install

    NC553i NIC Controller driver to 4.1.334.0 (Same as your esxi4.x link)

    https://my.vmware.com/web/vmware/details?downloadGroup=DT-ESX4041-EMULEX-be2net-413340&productId=230

    I have an issue where the be2net where the links will drop and then comeback for a sec. hopefully this driver version will fix the issue.

  12. Remy Zandwijk
    May 17th, 2012 at 15:03 | #12

    @Ben

    And we opened a call as well (auto-negotiation problem) and we were told to contact Emulex to get a hot fix driver. We received it (4.1.334.48) but it didn’t help either.

  13. Ben
    May 17th, 2012 at 15:08 | #13

    @Remy Zandwijk

    Yeah wishing i never upgraded from the G6s never had an issue! will update in a few days if this fixes my issue.

  14. Remy Zandwijk
    May 17th, 2012 at 15:10 | #14

    @Ben

    If HP is not going to fix our problem in the next week, then they have to replace the G7’s blades with Gen8 blades…

  15. Ben
    May 17th, 2012 at 16:28 | #15

    @Remy Zandwijk
    well my nic has dropped off the network again for a second so the driver update didn’t do anything…..
    Im running:
    esxi 4.1 502767
    Driver:be2net
    Version: 4.1.334.0
    Firmware-version: 4.0.493.0

    what are you running?

  16. Remy Zandwijk
    May 17th, 2012 at 18:39 | #16

    @Ben

    We’re running ESX, not ESXi. Version 433742. Firmware is the same.

    We’ve got an email from Emulex that the driver they sent us is not supported with HP OEMed Emulex NICs. They told us to revert to 4.0.334.0. On the other hand, HP says that our problem is just a cosmetic thing (which is not, NICs dropping connections is just not cosmetic).

    This is getting a real PITA. At least VMware and Emulex are pointing to HP…

  17. Rotem Agmon
    May 22nd, 2012 at 12:46 | #17

    I have an update on HP support status for be2net driver version 4.0.334.0. This driver version will require new Emulex firmware version yet to be released by Emulex and HP.

    I will update on the availability of this new firmware version as soon as it will become available for download.

  18. Ben
    May 22nd, 2012 at 14:28 | #18

    @Rotem Agmon
    Thanks for that, i haven’t heard anything from HP yet, wonder if they will be telling me the same story!

  19. Remy Zandwijk
    May 22nd, 2012 at 19:36 | #19

    We got word from HP that the auto-negotiation problem we have is also reported by another customer. They are working on it with the OEM-vendor and it is handles as a high-priority problem.

  20. Tim
    May 25th, 2012 at 16:47 | #20

    Remy : what do you mean with auto-negotiation problem? Is it the same as the one we are experiencing? :
    I’ve just installed two nex ESXi 4.1 servers on HP BL460c blades and when trying to apply a host profile to them, I receive an error “Autonegotiate option is not supported for the NIC vmnic2”. When I look at the speed settings for the nics, I see that they are empty. In the dropbox I can only select 10 gb full duplex (although I’ve configured custom speeds in Virtual Connect). Is this the same problem that you are experiencing?

    Regards,

    Tim

  21. Remy
    May 25th, 2012 at 17:08 | #21

    @Tim

    Yes, that’s the very same problem. Please open a case at HP. You could refer to our case (4639754370).

  22. Rotem Agmon
    May 29th, 2012 at 05:08 | #22
  23. Rotem Agmon
  24. Michael
    May 29th, 2012 at 07:06 | #24

    @Tim and @Remy, after applying the update are you then setting autonegotiate via the CLI? The GUI bug you are seeing happens to me, but setting it via CLI will actually set it to autonegotiate correctly.

  25. Tim
    May 29th, 2012 at 09:44 | #25

    Thanks for the info guys! I’ve opened a support case @ HP.

  26. Tim
    May 29th, 2012 at 14:08 | #26

    @Michael Thanks for the suggestion but I get the error when applying a host profile. Which is rather annoying because it throws out the “Autonegotiate option is not supported for the NIC” error and refuses to apply the profile to my new hosts. I can of course change every setting on the nics and server manually or through CLI, but it kind of defeats the purpose of having expensive Enterprise Plus licenses if you can’t use host profiles :).

  27. Tim
    May 30th, 2012 at 10:27 | #27

    @Rotem Agmon : Sorry didn’t see your comments, how could I’ve missed those! 🙂 Thanks for the links but I’m already running update 2 (build 502767). And the other link says to adapt the host profile for fixed speeds (my nics are already configured to be set to auto). The strange thing is that other servers have the same build and there the host profile works. They have been installed more than a year ago by my predecessor. The difference is that the newest servers have a newer HP ESXi 4.1 image (with newer drivers I assume).

  28. Remy Zandwijk
    June 4th, 2012 at 09:48 | #28

    Quote from HP:

    “The fix is scheduled due in the 9/2012( September 2012) time frame and is subject to driver testing & confirmation with the involved vendors. The OEM is aware of the issue, need for a fix for host profiles & also the driver. I’ll update you once I receive any further notification.”

  29. Rotem Agmon
    June 5th, 2012 at 22:10 | #29
  30. WoodITWork
    June 6th, 2012 at 13:15 | #30

    @Rotem Agmon

    Thanks for the update, Rotem, we appreciate you keeping us updated. I’ve done a new post to announce the release.

  31. Rotem Agmon
    June 30th, 2012 at 20:59 | #31

    4.1.402.8 firmware that is included with HP Service Pack for ProLiant 2012.06.0(B) has been superseded by version 4.1.402.20 which is available for download as a standalone image:
    http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareDescription.jsp?lang=en&cc=lamerica_nsc_carib&prodTypeId=329290&prodSeriesId=4324629&swItem=co-106538-1&prodNameId=4324630&swEnvOID=54&swLang=8&taskId=135&mode=4&idx=1

  32. Michael Schweiger
    September 27th, 2012 at 10:49 | #32

    Hi I’m also a long time affected BNX2X and BE2NET admin:(

    I just installed HP SPP 201208 which comes with: New Version: 4.1.450.7 (BE2) (4 Sep 2012) on 6 BL685c G7 server and tonight since a longer time I had the BE2Net drivers again unloaded.. so I guess for all of you to wait with this release…

    Anybody has the same issue?

    Cheers Michael

    http://h20565.www2.hp.com/portal/site/hpsc/template.PAGE/public/psi/swdDetails/?sp4ts.oid=4132830&spf_p.tpst=psiSwdMain&spf_p.prp_psiSwdMain=wsrp-navigationalState=lang%3Den%7Ccc%3DUS%7CprodSeriesId%3D4132829%7CprodNameId%3D4132830%7CswEnvOID%3D54%7CswLang%3D8%7CswItem%3Dco-108046-1%7Caction%3DdriverDocument&javax.portlet.begCacheTok=com.vignette.cachetoken&javax.portlet.endCacheTok=com.vignette.cachetoken

  1. No trackbacks yet.
 

Time limit is exhausted. Please reload the CAPTCHA.