'Network connectivity lost'

[L0cayta]

Hi there.

I recently added a new host to me ESXi 5.0 cluster and i am receiving the following 'info' messages within vcentre:

Alarm 'Network connectivity lost': an SNMP trap for entity mvm01 was sent
info
16/04/2012 09:51:46
mvm01

This error has been pretty steady since the host has been up and added to the cluster.

I am unable to find any network issue's and responses to and from the host look good with no latency.

[helltejas]

did you checked last events and tasks??

if possible attech vpxa.log file

[theclintox]

Don't know if this is any help after so long; I found this post while investigating a similar problem, which I've now managed to resolve.

The critical status alert for "Network Connectivity Lost" appears to be configured to repeat forever by default.  To change it:

• Open your vSphere Client
  
• Left-click your vCenter server in the navigation tree on the left
  
• Click the "Alarms" tab
  
• Find and double-click the "Network Connectivity Lost" entry.
  
• Click the "Actions" tab
  
• Change the action for "Warning -> Critical" from "Repeat" to "Once".
  

Hope this helps.

[ngarjuna]

To verify if the NIC is functional:

1. Log in to the ESX console.
2. Run this command:
   
   # ethtool-S vmnicX
   
   If  rx_missed_errors and rx_no_buffer_count increment, the NIC is not functional.

To resolve this issue install this patch depending on your product version:

• For ESX 3.5 : VMware ESX 3.5, Patch ESX350-200912404-BG: Updates igb driver(1016661)
• For ESXi 3.5: VMware ESXi 3.5, Patch ESXe350-200912401-I-BG: Updates Firmware(1016664)

To workaround this issue, you must change the speed settings on the device and then revert to the original settings. For example, if your NIC speed is set to Auto negotiate, change the speed to 1000 Mbps and then revert it to auto negotiate.

To change the speed settings and to revert to the original value:

1. Log in to vCenter Server and  navigate to Host > Configuration.
2. Click Networking under Hardware.
3. Click Properties... of the vSwitch.
4. In the vSwitch Properties dialog, click the Network Adapters tab.
5. Click the network adapter and then click Edit....
6. Select 1000 Mb, Full Duplex from the Configured Speed, Duplex dropdown.
7. Click OK and then Close.
8. Repeat Steps 3 to 5 and reset the speed to the original value.

[rickardnobel]

ngarjuna wrote:

To resolve this issue install this patch depending on your product version:

• For ESX 3.5 : VMware ESX 3.5, Patch ESX350-200912404-BG: Updates igb driver(1016661)
• For ESXi 3.5: VMware ESXi 3.5, Patch ESXe350-200912401-I-BG: Updates Firmware(1016664)

Since this is the ESXi 5 forum these links will not be applicable. It is very nice to try to be helpful, but it is also good to do some verifying that the information seems to be relevant.

[VirtuCloud]

I have seen similar errors when DNS is not functioning properly and that it is configured properly both on the ESX hosts and the vCenter server (I usually go as far as adding the enteries into the HOSTS file on the vCenter server).

I would verify name pings to-and-from on the hosts as well as the vCenter server. This type of problem in particular may cause bigger issues as well.

VC