Hi there,
Do you all encounter false alert for network uplink redundancy alarms and network connectivity lost? Everytime the alarm triggered, customer will call and request me to check onsite, but the connection was fine and the cable was in good condition. Anything I can do to check what is actually going on with the alarms?
Regards,
bulkbiz
Do you see any error on switch ports when the alerts are triggered?
You can follow this KB(http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=100954...) for troubleshooting
Can you please provide some details about the network configuration. vSwitch and port group settings, physical switch/port configuration, ...
André
There are no problem with the vswitch or any vmnic connection, everything running just fine. Is just that the alarm will trigger once in a while.
Can you please provide some details about the network configuration. vSwitch and port group settings, physical switch/port configuration, ...
I am using standard vSwitch with two vmnic attached to it, only one port groups. I have physically check the cable connection from the network card to the physical switch, everything is good.
Do you notice any flapping issue on Physical switch?
Did you ever find a solution to this? We upgraded from vCenter 4.1 to 5.0U1 last night, and today many of our ESXi 4.1U1 hosts have been having this alert. I see no evidence of a real problem, they are blades scattered around the datacenter.
Hi,
I am using HP BL685c Blade servers and I am also getting these alerts in the exact order:
AG,
Did you find a solution or root cause of this issue?
TIA,
Amir
Jesse,
Did you ever find the root cause of these alerts?
TIA,
Amir
I saw a similar issue today at a customer... every 5 minutes this event would be generated. We confirmed DNS and vSwitch settings and verified there were no packets being dropped or errors on the physical NIC.
Tried restarting the management agents on the host but no dice. Finally removing and re-adding the host to vCenter resolved the issue - we waited 10 minutes and the error did not return.