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=eyJmaW5hbFJlZGlyZWN0TG9jYXRpb24iOiJodHRwczovL3d3dy52ZWVhbS5jb20va2IxMjY0IiwiaGFzaCI6ImIxNjQ1YWE5LWUwMGEtNGE0Yi1hODU0LWZkZmY5MDY2MjA4OCJ9
1-800-691-1991 | 9am - 8pm ET
EN

Empty sockets counter in nworks Enterprise Manager

Challenge

Incorrect number of sockets displayed in nworks Enterprise Manager.

Cause

Enterprise Manager gathers number of sockets from VMware vCenter's "hardware.cpuInfo.numCpuPackages" property.

In some cases if a particular host is in the process of re-adding to the VMware vCenter (for example, if it was renamed, or IP address was changed), then VMware vCenter returns "0" value for this property.

Solution

The work-around is to remove affected VMware vCenter from nworks Enterprise Manager and register it once again.

More information

This particular issue is resolved in nworks v5.7 and later.

KB ID:
1264
Product:
Veeam Management Pack for Microsoft System Center
Version:
5.6
Published:
2011-10-06
Last Modified:
2020-08-28
Please rate how helpful this article was to you:
5 out of 5 based on 1 ratings
Thank you for helping us improve!
An error occurred during voting. Please try again later.

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.
Your report was sent to the responsible team. Our representative will contact you by email you provided.
We're working on it please try again later