Repeating Uplink redundancy restored messages

[FredPeterson]

ESX build base v4.1

So I've noticed these messages in my "messages.log" for awhile now but havn't ever cared to figure out why or if its even a concern since nothing seems to be affected.

JAN 07 16:02:11 dhsesx05 vobd: Jan 07 16:02:05.519: 257720137084us: [vob.net.dvport.uplink.transition.up] Uplink: vmnic2 is up. Affected dvPort: 977/09 69 11 50 27 65 70 db-ea 26 dc 31 12 a2 60 d6. 1 uplinks up.

JAN 07 16:02:11 dhsesx05 vobd: Jan 07 16:02:05.520: 257720137091us: [vob.net.dvport.uplink.transition.up] Uplink: vmnic3 is up. Affected dvPort: 977/09 69 11 50 27 65 70 db-ea 26 dc 31 12 a2 60 d6. 2 uplinks up.

JAN 07 16:02:11 dhsesx05 vobd: Jan 07 16:02:05.521: 257720137093us: [vob.net.dvport.uplink.transition.up] Uplink: vmnic5 is up. Affected dvPort: 977/09 69 11 50 27 65 70 db-ea 26 dc 31 12 a2 60 d6. 3 uplinks up.

JAN 07 16:02:11 dhsesx05 vobd: Jan 07 16:02:07.522: 257722141608us: [esx.clear.net.dvport.connectivity.restored] Network connectivity restored on DVPorts: "977/09 69 11 50 27 65 70 db-ea 26 dc 31 12 a2 60 d6". Physical NIC vmnic2 is up.

JAN 07 16:02:11 dhsesx05 vobd: Jan 07 16:02:07.539: 257722158184us: [esx.clear.net.dvport.redundancy.restored] Uplink redundancy restored on DVPorts: "977/09 69 11 50 27 65 70 db-ea 26 dc 31 12 a2 60 d6". Physical NIC vmnic3 is up.

JAN 07 16:02:11 dhsesx05 vobd: Jan 07 16:02:07.543: 257722162154us: [esx.clear.net.dvport.redundancy.restored] Uplink redundancy restored on DVPorts: "977/09 69 11 50 27 65 70 db-ea 26 dc 31 12 a2 60 d6". Physical NIC vmnic5 is up.

This is happening on a brand new server (fwiw IBM x3850X5 w/Dual port Broadcom NICs)  The messages repeat oh, I don't know about once an hour.

The other servers (IBM x3850M2) this occurs on also, but not as frequently it seems.

There is never a message about the NIC going down - just that its up and redundancy is restored.

[mal_michael]

Hi,

I see exactly the same messages on all of my ESXi 4.1 hosts connected to vDS. They are installed with HP / IBM customized ISO and have latest patches applied.

I have found kb dvPort uplink redundancy restored but the NICs are not going down and still the messages appear.

Michael

[JayCardin · Accepted solution]

I have noticed this too (ESXi 4.1 with DVS).  It always occurs after a snapshot is released by our backup software (vRanger Pro).

[FredPeterson]

Bingo!  I didn't even think about that as a possibility and just confirmed it by tracking down through the port it shows and the timing of a vReplicator action that just took place.

Unfortunate message but at least now I know.

[mal_michael]

Good find! In my case VCB snaps cause these events to appear.

Thanks.

[sangk]

THis just a Information message and no workaround is needed

check

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=102037...

[sdean0202]

Repeating Uplink redundancy restored errors can also be caused by incorrect settings in virtual switch Port groups.  If you are using ether channeling and you have configured a port group using the ether channel vmnics to use "Beacon Probing" in the "Network Failover Detection" setting you will have this error occur.  When using Ether channel you need to set the "Load Balancing" option for the port group to "Route based on IP hash". "Beacon Probing" is not allowed when using IP hash load balancing.

This is also true for Distributed switches and will affect any host associated to the dvSwitch/port group. 

The fix for the issue is to set Network Failover detection to "Link status only".

[30hotham]

It doesn't sound like a problem at all. It happens everytime a VM is power-on or vmotioned to the host.

See http://kb.vmware.com/kb/1032895

[sdean0202]

So with the conditions I noted the vmnics associated to the incorrectly configured port group will each generate an uplink redundancy restored message about every 3-5 seconds. No vmotions or VM power-on need occur for these message to appear. The beacon probing is the cause of the uplink errors.