Thanks for your feedback! You might just need to refresh it. Please reboot server to recover be2net It may not work in other scenarios. In this case after a reboot the kernel fails to recognize the be2net ports and bring them online. For more information, see the HP Advisory http:
|Date Added:||9 February 2012|
|File Size:||60.52 Mb|
|Operating Systems:||Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X|
|Price:||Free* [*Free Regsitration Required]|
To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.
Traffic drop on 10Gb Emulex OneConnect ethernet interfaces on HP servers
Copy To Clipboard copy external link to clipboard copied! Are you sure you want to rate this stars? After cold reboot error messages disappear.
Your rating was not submitted, please try again later. For more information, see the HP Advisory http: This article helped but additional information was emuoex to resolve my issue. To resolve this issue, contact HP for the newer Emulex firmware.
Did this article help you? Run the ‘reset’ command from the onboard administrator cli to reset the blade.
Select your language
Sep 29, Last Updated: RXF bit oneconnct kernel: Please reboot server to recover be2net Link to the article explaining the issue: What can we do to improve this information? Unrecoverable Error detected in the adapter be2net An unexpected error occurred on a receive.
Rate This Rating submitted. Customers using HP blades with an on-board be2net card have reported this. You need to enable security on this component, as it could expose confidential information see Allowing User Impersonation. To ojeconnect alerted when this document is updated, click the Subscribe to Article link in the Actions box.
This article did not resolve my issue. Please rate this document Rating submitted. This article resolved my issue. If you find the link is broken, provide feedback and a VMware employee will update the link. Rate This Rating submitted Your rating was not submitted, please try again later.
The underlying connection was closed: If you choose to install the rpm package, on eeach upgrade of hotfix or JHF version that rpm package will be restored to the problematic version of be2net and reinstallation of the package is needed.
In this case after a reboot the kernel fails to recognize the be2net ports and bring them online.