Search the VMware Knowledge Base (KB)
View by Article ID

Node status reports as Waiting for Analytics in vRealize Operations Manager 6.x (2143800)

  • 1 Ratings

Symptoms

  • VMware vRealize Operations Manager 6.x user interface is inaccessible.
  • The status of all nodes is stuck on Waiting for Analytics in the admin UI.
  • The node loses hostname (renames to localhost).
  • The VM has been cloned.
  • When you run the command ifconfig eth0, you see the output:

    eth0: error fetching interface information: Device not found

Purpose

If node status reports as Waiting for Analytics in VMware vRealize Operations Manager 6.x, correct the MAC address of the NIC in the VMware vRealize Operations Manager node(s) to resolve the issue.

Cause

This occurs when the MAC address of the NIC has changed on the vRealize Operations Manager node(s).

Resolution

To resolve this issue, correct the MAC address of the NIC in the VMware vRealize Operations Manager node(s).

Note: Before proceeding, stop the services on all the nodes before correcting the MAC address on the affected node:
  1. Log in to the Master node as root through console or SSH.
  2. Run these commands to stop the vRealize Operations Manager services.

    service vmware-vcops stop
    service vmware-casa stop

  3. Repeat steps 1 to 2 on all other nodes in the vRealize Operations Manager cluster.
To correct the MAC address of the NIC in affected node:

  1. Log in to the affected vRealize Operations Manager node as root through console or SSH.
  2. Copy the /etc/udev/rules.d/70-persistance-net.rules file to /tmp/70-persistance-net.rules.bak.
  3. Open the /etc/udev/rules.d/70-persistance-net.rules file using a text editor.
  4. Comment out the first SUBSYSTEM line by adding # at the beginning of the line.

    For example:

    #SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:50:56:03:44:77", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"

  5. Change the second SUBSYSTEM line from eth1 to eth0.

    For example:

    SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:50:56:03:35:2f", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"

  6. Save and close the file.
  7. Repeat steps 1 to 6 on all affected vRealize Operations Manager nodes.
  8. Restart all nodes in the vRealize Operations Manager cluster.

See Also

Request a Product Feature

To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.

Feedback

  • 1 Ratings

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.

What can we do to improve this information? (4000 or fewer characters)




Please enter the Captcha code before clicking Submit.
  • 1 Ratings
Actions
KB: