Unreliable detection of ethernet link status in a Virtual Connect environment
Issue
A RHEL-6.4 system is not able to reliably detect the correct link status information of an Ethernet network interface under specific operating conditions when deployed in a Virtual Connect environment.
After shutting down the Virtual Connect port that is used by the blade, the link status information on the blade (ethtool ethX) still shows "UP".
The interface status does not get updated and the link is still shown as 'UP' after the link failure whilst the speed and duplex properties of the link are no more available. This behavior has been reproduced on a consistent basis using a Emulex-based card operated by the 'be2net' module.
Environment
- Red Hat Enterprise Linux 6.4
- HP ProLiant BL460c G7 Blade
- Virtual Connect
- be2net driver
- Kernel 2.6.32-358.el6.x86_64
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.
