This article describes a specific issue. If you experience all of the symptoms, this article applies to you. If you experience some but not all of the symptoms, your issue is probably not related to this article. Search the knowledge base for your symptoms, review ESX/ESXi host has intermittent or no network connectivity (1004109) for similar issues, or open a Support Request. For more information, see How to Submit a Support Request.
[esx.problem.net.redundancy.lost] Lost uplink redundancy on virtual switch "vSwitch0". Physical NIC vmnic0 is down. Affected port groups: "Portgroup Name".
[esx.problem.net.connectivity.lost] Lost network connectivity on virtual switch "vSwitch0". Physical NIC vmnic1 is down. Affected port groups: "Portgroup Name".
Note: To confirm the ESX version, see Determining VMware Software Version and Build Number (392)
This issue occurs due to memory exhaustion in the Broadcom bnx2x network interface driver.
This issue is resolved in Broadcom bnx2x driver release version 1.62.15.v41 build 380522, released 2011-03-23.
The latest Broadcom bnx2x version bnx2x-1.64.32.v41.1 can be downloaded here.
To resolve this issue:
esxcfg-module -s "" bnx2x
Install the async Broadcom driver on the ESX/ESXi host. For more information, see How to install async drivers on ESX/ESXi 4.x (1032936).esxcfg-module -g bnx2x
bnx2x enabled = 1 options = ''
esxcfg-module -s skb_heap_max=36000000 bnx2x
To remove the changes to the heap memory allocations:
esxcfg-module -g bnx2x
bnx2x enabled = 1 options = '
skb_heap_max=36000000
'
esxcfg-module -s "" bnx2x