[Webinar] Streamline your web hosting managementRegister Today

x
?
Solved

VCenter-VROPS error message

Posted on 2016-08-16
3
Medium Priority
?
281 Views
Last Modified: 2016-09-06
I am getting the following error message in VROPS:


ESXi host has detected a link status down on a physical NIC

Recommendation(s)
ESXi disables the device to avoid the link flapping state. You might need to replace the physical NIC. The alert will be canceled when the NIC is repaired and functioning. If you replace the physical NIC, you might need to manually cancel the alert.

I checkedthe  vCenter 6 and Host  and there is no such error and I am confused how to fix this in VROPS.
0
Comment
Question by:cgeorgeisaac
  • 2
3 Comments
 
LVL 125

Accepted Solution

by:
Andrew Hancock (VMware vExpert / EE MVE^2) earned 2000 total points
ID: 41758268
This is currently an issue in vROPS version 6.0.1

see the release notes

Network link failure related alerts might not auto clear when the problem is fixed

The following network link failure related alerts might not be cleared if the vSphere Client does not report that the events are cleared to vRealize Operations Manager, even if the underlying problem is fixed:

ESXi host has detected a link status down on a physical NIC

The host has lost connectivity to a dvPort

The host has lost redundant connectivity to a dvPort

The host has lost connectivity to physical network

The host has lost redundant uplinks to the network

Workaround: When the physical NIC or vSwitch or DV Port is functional, confirm that the network issue no longer exists, and manually cancel the alert.

Source
https://www.vmware.com/support/vrops/doc/vrops-601-release-notes.html
0
 

Author Comment

by:cgeorgeisaac
ID: 41758357
Thanks I am looking into it.  However, my version of VROPS is 6.2.1
0
 
LVL 125
ID: 41776956
did you require any further assistance to close this question.
0

Featured Post

The 14th Annual Expert Award Winners

The results are in! Meet the top members of our 2017 Expert Awards. Congratulations to all who qualified!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

When rebooting a vCenters 6.0 and try to connect using vSphere Client we get this issue "Invalid URL: The hostname could not parsed." When we get this error we need to do some changes in the vCenter advanced settings to fix the issue.
If you need to complete a Physical to Virtual (P2V), Virtual to Virtual (V2V) conversion to a VMware product (VMware Workstation, Player or VMware vSphere (ESXi) ) for FREE, then there is some good news...
Teach the user how to rename, unmount, delete and upgrade VMFS datastores. Open vSphere Web Client: Rename VMFS and NFS datastores: Upgrade VMFS-3 volume to VMFS-5: Unmount VMFS datastore: Delete a VMFS datastore:
Teach the user how to use vSphere Update Manager to update the VMware Tools and virtual machine hardware version Open vSphere Client: Review manual processes for updating VMware Tools and virtual hardware versions: Create a new baseline group in vSpā€¦
Suggested Courses

640 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question