Forum, I have a
home lab running ESXi 5.5 and every time I try to copy a file to the datastore my management network goes down. I am using Intel Pro/1000 MT dual server adapter. The logs show following messages.
syslog.log
2014-08-25T12:57:30.537Z: [netCorrelator] 8425496865us: [vob.net.pg.uplink.transition.down] Uplink: vmnic0 is down. Affected portgroup: Management Network. 0 uplinks up. Failed criteria: 128
2014-08-25T12:57:30.538Z: [netCorrelator] 8425496949us: [vob.net.vmnic.linkstate.down] vmnic vmnic0 linkstate down
2014-08-25T12:57:32.001Z: [netCorrelator] 8426960975us: [esx.problem.net.connectivity.lost] Lost network connectivity on virtual switch "vSwitch0". Physical NIC vmnic0 is down. Affected port groups: "Management Network"
2014-08-25T12:57:33.045Z: [netCorrelator] 8428004881us: [vob.net.vmnic.linkstate.up] vmnic vmnic0 linkstate up
2014-08-25T12:57:33.147Z: [netCorrelator] 8428106889us: [vob.net.pg.uplink.transition.up] Uplink:vmnic0 is up. Affected portgroup: Management Network. 1 uplinks up
2014-08-25T12:57:35.001Z: [netCorrelator] 8429960958us: [esx.clear.net.connectivity.restored] Network connectivity restored on virtual switch "vSwitch0", portgroups: "Management Network". Physical NIC vmnic0 is up
Vbod.log
--------------
2014-08-25T12:57:30.537Z: [netCorrelator] 8425496865us: [vob.net.pg.uplink.transition.down] Uplink: vmnic0 is down. Affected portgroup: Management Network. 0 uplinks up. Failed criteria: 128
2014-08-25T12:57:30.538Z: [netCorrelator] 8425496949us: [vob.net.vmnic.linkstate.down] vmnic vmnic0 linkstate down
2014-08-25T12:57:32.001Z: [netCorrelator] 8426960975us: [esx.problem.net.connectivity.lost] Lost network connectivity on virtual switch "vSwitch0". Physical NIC vmnic0 is down. Affected port groups: "Management Network"
2014-08-25T12:57:33.045Z: [netCorrelator] 8428004881us: [vob.net.vmnic.linkstate.up] vmnic vmnic0 linkstate up
2014-08-25T12:57:33.147Z: [netCorrelator] 8428106889us: [vob.net.pg.uplink.transition.up] Uplink:vmnic0 is up. Affected portgroup: Management Network. 1 uplinks up
2014-08-25T12:57:35.001Z: [netCorrelator] 8429960958us: [esx.clear.net.connectivity.restored] Network connectivity restored on virtual switch "vSwitch0", portgroups: "Management Network". Physical NIC vmnic0 is up
2014-08-25T13:15:40.207Z: [netCorrelator] 9515167030us: [vob.net.pg.uplink.transition.down] Uplink: vmnic0 is down. Affected portgroup: Management Network. 0 uplinks up. Failed criteria: 128
2014-08-25T13:15:40.208Z: [netCorrelator] 9515167111us: [vob.net.vmnic.linkstate.down] vmnic vmnic0 linkstate down
2014-08-25T13:15:42.001Z: [netCorrelator] 9516961074us: [esx.problem.net.connectivity.lost] Lost network connectivity on virtual switch "vSwitch0". Physical NIC vmnic0 is down. Affected port groups: "Management Network"
2014-08-25T13:15:52.251Z: [netCorrelator] 9527210926us: [vob.net.vmnic.linkstate.up] vmnic vmnic0 linkstate up
2014-08-25T13:15:52.353Z: [netCorrelator] 9527312924us: [vob.net.pg.uplink.transition.up] Uplink:vmnic0 is up. Affected portgroup: Management Network. 1 uplinks up
2014-08-25T13:15:54.001Z: [netCorrelator] 9528961043us: [esx.clear.net.connectivity.restored] Network connectivity restored on virtual switch "vSwitch0", portgroups: "Management Network". Physical NIC vmnic0 is up
Configs
--------------
Montherboard: Asus DSBF-D12/SAS
Storage Adapter: Perc 6i
CPU: Intel E5420 and 32 GB of Ram
NIC: Intel Pro/1000 MT dual server adapter
Hi Virtusli3ed,
There is a related article here.
VMware KB: ESX/ESXi reports a vmnic as down and displays the error: Failed criteria: 32
Whilst the failed criteria is different it does point to the physical network.
Similarly someone had the same error as you on a UCS chassis
https://supportforums.cisco.com/discussion/11721481/b200-m3-network-connection-silently-failing
This points to a network issue and a duplicate IP being leased from a DHCP server.
So for starters I would try changing the Network Failover Detection of your vswitch to "link status only" and ensuring nothing else in your lab is using the IP in question.
Hope that helps
Thanks for the response NealeC! Did some more testing and seems like it was drivers on the client laptop, updated it and seems to be working ok now. Still got to do more testing though so won't close this post yet.
Hi Virtusli3ed,
Also refer the following VMware KB: Devices deprecated and unsupported in ESXi 5.5 mentioned e1000 many models mentioned as unsupported. Please check whether your network card is falls under this category...
Yuvaraj.M
