VMware Cloud Community
Gert101
Contributor
Contributor

Network uplink redundancy lost

Hi Guys

I keep getting the above mentioned alarm once in a while and I haven't been able to find the problem. I've replaced network cables and checked in Vcentre everything looks fine.

Twice now over the past few weeks I've lost access to the VMs on the server but not all of them only some of them. Then as soon as I migrate them to another host all is working again.

Any where I can start looking?

I have 5x ESXI 5.1 servers running.

Compellent storage

Dell R710 servers.

Reply
0 Kudos
6 Replies
zXi_Gamer
Virtuoso
Virtuoso

I keep getting the above mentioned alarm once in a while and I haven't been able to find the problem. I've replaced network cables and checked in Vcentre everything looks fine.

If you have configured a cluster with a HA/DRS, then the agent requires that the Management portgroup should be having 2 uplinks in case of any 1 nic failure. If you have provided 2 nics, and still you are getting this error, then you need to check in the vmkernel logs of the host to see if the nic has gone any auto-negate process.

Twice now over the past few weeks I've lost access to the VMs on the server but not all of them only some of them. Then as soon as I migrate them to another host all is working again.

I do believe if your VMs are in the same vswitch as your management portgroup. Can you move your VMs to a different vSwitch to eliminate the vmnic probability?

Reply
0 Kudos
Gert101
Contributor
Contributor

Thanks zXi-Gamer I will check the logs.

My Management and VM portgroups are both in their own Vswitch.

Reply
0 Kudos
abhilashhb
VMware Employee
VMware Employee

Can you check the logs at the time of this alarm?

cat /var/log/messages | grep -i link

tail -fv /var/log/messages | grep -i link

Abhilash B
LinkedIn : https://www.linkedin.com/in/abhilashhb/

Reply
0 Kudos
Gert101
Contributor
Contributor

Hi Guys this is all I have under Var/log

/var/log # ls

Xorg.log              ipmi                  vmkdevmgr.log

auth.log              lacp.log              vmkernel.log

boot.gz               rhttpproxy.log        vmkeventd.log

configRP.log          shell.log             vmksummary.log

dhclient.log          smbios.bin            vmkwarning.log

esxcli.log            storagerm.log         vmware

esxupdate.log         sysboot.log           vobd.log

fdm.log               syslog.log            vprobed.log

hostd-probe.log       usb.log               vpxa.log

hostd.log             vmamqpd.log

hostprofiletrace.log  vmauthd.log

Reply
0 Kudos
wmarusiak
Enthusiast
Enthusiast

Hi,

I suggest to provide more information about your config.

Best Regards, Wojciech https://wojcieh.net
Reply
0 Kudos
pierreLx
Enthusiast
Enthusiast

Hi,

I think you should check your load balancing settings. If you are doing iscsi port binding don't forget that the native loadbalancing technics are not all compatible with your storage array so put it to fixed to be sure and test active/passive configuration with nics in different order.

Regards

Reply
0 Kudos