Newly added VCenter is not polled

This article helps to resolve issues seen with vCenter polling. The vCenter MOB may be accessible via https://yourvcenterIP/mob but the VCenter is not not actively polling in VMAN. 

Scenario 1:
Message displayed in the virtual center resource may read "no entity to collect."


Scenario 2:
There is no message like above, but the VCenter Status is Unknown, the node is added in VIM_VCenter and Nodes table(s). This is noticed in SolarWinds platform 2020.2.6 HF1 
 

1. Insufficient permissions
2. Java poller is not initialized for some reason

Basic checks:

1. Go to summary page, Edit node
2. Verify Polling Method is Set to ICMP (and ICMP is enabled between Polling engine and VCenter server) on the network
3. Note VMan does not support polling via Agent / WMI / SNMP

Validate account used to poll the VCenter: (Solution to Scenario 1 )

1. From the Poller that will be polling this VCenter > Navigate to MOB page of the VCenter you are trying to add via https://YourVcenterHostname/mob
2. Proceed past the certificate message.
3. Enter vCenter account details you got from your VMware admin
4. Make sure you can navigate down to see the ESX hosts: content -> rootFolder -> childEntity (choose datacenter) -> hostFolder -> childEntity (choose domain) -> host (choose ESX host).

If you cannot navigate down to see the hosts this indicates that the permissions are not set properly for the account. Or perhaps no ESX hosts have been established under this vCenter. 
Related: Minimum required permissions for vCenter polling in the SolarWinds Platform

Note:

• Mob and sdk are different channels, so it can be possible to connect to Mob but not the sdk.
• Also communication to MOB is one way
• You cannot poll A Vcenter with No Objects ( Esxi Hosts)

Additionally you can Check(if applicable in your environment):

• Firewall Rules
• Ports &  URL filters
• Proxy Rules

Disable Default Proxy Server for Virtualization Monitor Connections to VMware vCenter
https://support.solarwinds.com/SuccessCenter/s/article/Disable-Default-Proxy-Server-for-Orion-Virtualization-Monitor-Connections-to-VMware-vCenter?language=en_US

Solution Scenario 2:
1. Check via task manager if java.exe is running
2. If it is not running, restart the Orion Module Engine, Collector Service, and Job Engine
3. Wait for 5-10 minutes (grab a cup of tea or coffee) for polling to complete, as it may take some time to update the info in the SolarWinds Platform Web Console, depending on how many hosts and VMs the VCenter you added has for the collection job to finish.