The Odd Angry Shot

Virtualisation from the trenches

Nov 12, 2013 - 2 minute read - ESXi troubleshooting vCenter

Constant Alarm ‘Network Uplink Redundancy Lost’

It’s amazing how much is going on when you dig through logs. On this occasion I was looking at  “tasks & events” of a host and noticed a lot of network errors.

Alarm ‘Network uplink redundancy lost’ on triggered an action

The error was occurring every 5 minutes. This was made visual with the use of Log Insight. My new favourite tool.

LogInsight

I couldn’t find anything wrong with this particular ESXi host, vSwitch or uplink. It had the same configuration as all the other hosts in the cluster.

The fix was to go to the top level where the alarm is defined, Edit Settings, disable the alarm, then go back and re-enable it.

After that, the errors stopped appearing.

LogInsight

Comments

Comment by Anonymous on 2014-02-24 17:45:42 +0000

Hello Daunce,

I have same issue at the moment, errors also stopped for me by following your steps
however on checking logs within host, issue is still there.

So you should remove this blog, which provides a wrong soln, which only stops events from coming.

BR

Comment by daunce on 2014-02-24 17:53:57 +0000

Hi BR.

Of course you need to re-enable the alarm.

In my case it was a false positive.

Your situation may be different. If it continues, contact VMware support.

Comment by Anonymous on 2015-03-27 12:13:48 +0000

Thanks! Turning this alarm off then back on fixed the same issue here. Wonder what might trigger that.

Comment by Anonymous on 2015-07-14 02:30:07 +0000

Ran the most recent updates for 5.5 and this alarm triggered afterwords. Disabling then re-enabling still fixed it! Thanks for posting the tip.

Comment by MIke on 2017-05-12 18:57:15 +0000

Issue still occurring in esxi 6.0 just disabled and then reenabled we will see what happens

Comment by Kamran Zafar Syed on 2018-03-05 13:59:05 +0000

thanks man that did the trick it is VC 5.0. And email keeps popping after every 5 minutes.

Comment by Tony on 2018-11-20 05:43:29 +0000

This worked great on an ESXi 5.1.0 host. We had a network switch problem that caused links to go up and down. The alarms continued after the switch stack restart even though the connections were all restored.