Applications Systems

Polling issues when VMAN monitors a vCenter that is hosted on a virtual machine (affects AppStack)

You may encounter polling issues when VMAN is monitoring a vCenter that is hosted on a virtual machine. In this case, AppStack displays the parent entities of the virtual machine instead of the environment underneath the vCenter. A work-around requires altering the credentials of the vCenter to not poll the VM that the vCenter is hosted on.

First published date

10/31/2018 8:41 PM

Last published date

3/9/2022 12:29 AM

Overview

You may encounter polling issues when VMAN is monitoring a vCenter that is hosted on a virtual machine.

In this case, AppStack will treat the vCenter as a virtual machine and display the parent entities of the virtual machine instead of the environment underneath the vCenter.

Product section

Virtualization Manager

Cause

This is a configuration-based issue, caused by a conflict where VMAN polls the vCenter, which is hosted by a virtual machine underneath that vCenter or another vCenter hosted on a VM that is managed by another VCenter.

Resolution

As a workaround, you can alter the permission of the user/group credential used by VMAN for monitoring the vCenter to prevent polling of the virtual machine.

The user/group's permissions must be modified using the vSphere client. For the virtual machine where the vCenter is installed, set the user/group's permission to "No access".

Doing so will prevent the vCenter from polling the virtual machine.

The following steps and image provide an example.

Locate and select the virtual machine where the vCenter you are polling is installed.
Select the Permissions tab.
Select the user/group and modify the Access Rule to No access.
Select Propagate and click OK.

VMAN vSphere Client Change Access Rule Propogate

(Screenshots property of © 2019 VMware, Inc)

Disclaimer: Please note, any content posted herein is provided as a suggestion or recommendation to you for your internal use. This is not part of the SolarWinds software or documentation that you purchased from SolarWinds, and the information set forth herein may come from third parties. Your organization should internally review and assess to what extent, if any, such custom scripts or recommendations will be incorporated into your environment. You elect to use third party content at your own risk, and you will be solely responsible for the incorporation of the same, if any.

Disclaimer: Please note, any content posted herein is provided as a suggestion or recommendation to you for your internal use. This is not part of the SolarWinds software or documentation that you purchased from SolarWinds, and the information set forth herein may come from third parties. Your organization should internally review and assess to what extent, if any, such custom scripts or recommendations will be incorporated into your environment. You elect to use third-party content at your own risk, and you will be solely responsible for the incorporation of the same if any.