https://login.veeam.com/en/oauth?client_id=nXojRrypJ8&redirect_uri=https%3A%2F%2Fwww.veeam.com%2Fservices%2Fauthentication%2Fredirect_url&response_type=code&scope=profile&state=eyJmaW5hbFJlZGlyZWN0TG9jYXRpb24iOiJodHRwczovL3d3dy52ZWVhbS5jb20va2IxMzA1IiwiaGFzaCI6IjBlODBjMzVjLTI1ZmQtNDg1Zi05YmI4LTE2NGIxZDlmOWE1ZCJ9
1-800-691-1991 | 9am - 8pm ET
EN

VMware vCenter or Host are not monitored after upgrading nworks SPI to v5.6

KB ID: 1305
Version: 5.x
Published: 2011-10-20
Last Modified: 2020-08-13

Challenge

If upgrading from a previous version of nworks and monitoring objects is disabled, collection may not occur correctly.

Reading the Virtual Center and/or rebuilding the topology does not show information in HP OMW console. Also there is no discovery or events presented in HP OMW console.

Monitoring of previously disabled VMware vCenter or Host is not working after the upgrade to latest nworks even though collectors in Enterprise Manager are functioning correctly.

Cause

In nworks SPI the settings that were older than v5.0.x were kept in the registry of the computer where the Management server or collector are installed.

Solution

Check this parameter in registry of Veeam Enterprise Manager or collector:
 
HKEY_LOCAL_MACHINE\SOFTWARE\nworks\VIC\Config\VIServers\*name of host or vc*\Collection=0

The parameter specified above prevents collectors from monitoring VMware vCenter or Hosts so it is necessary to remove the "Collection=0" parameter, if required. After several hours, configuration will be renewed and VMware vCenter or Hosts  will be monitored correctly.

KB ID: 1305
Version: 5.x
Published: 2011-10-20
Last Modified: 2020-08-13

Couldn't find what you were looking for?

Below you can submit an idea for a new knowledge base article.
Report a typo on this page:

Please select a spelling error or a typo on this page with your mouse and press CTRL + Enter to report this mistake to us. Thank you!

Spelling error in text

Knowledge base content request
By submitting, you agree that your personal data will be managed by Veeam in accordance with the Privacy Policy.

ty icon

Thank you!

We have received your request and our team will reach out to you shortly.

OK

error icon

Oops! Something went wrong.

Please go back try again later.