Configuring Operations Manager agent

KB ID: 1026
Product: Veeam Management Pack for System Center
Version: 5.x, 6.x, 7.x
Published:
Last Modified: 2015-02-13

Challenge

No performance data regarding VMware objects is available in SCOM or gaps or dotted lines are visible in Performance views.

Cause

If the collection is properly configured, but performance data is missing from the Operations Manager console, the issue may be related to the Health Service's configuration. The collector sends a significant amount of data to the Health Service - more than it normally receives when configured to monitor just the node where the Health Service is deployed. As a result, it is necessary to configure the Health Service to have additional space set aside to receive the incoming data from the collector. Without these adjustments, the Health Service can become overwhelmed and the cache may need to be cleared.

Solution

There are two ways to configure the agent: automated (available since version 5.5) and manual. Below are the steps to configure either option:

Automated configuration of the Health Service

Run the task for each collector system in your environment. This task is included in Veeam Management Pack and sets the registry entries for OpsMgr agent  or Management Server to maximize efficiency when processing large data volumes as a proxy. The task name and location have changed between versions of the Management Pack, so the instructions are specific to the version that you have installed:

Version 5.x

After discovery of collector services is complete in Ops Mgr, you will see that the ‘_Collector State’ view under the Enterprise Manager Dashboard is populated with the Collectors. To run the task:

 

  1. Open the Monitoring pane of OpsMgr console
  2. Select nworks VMware > Enterprise Manager > Collector Servers > _Collector State view
  3. Select the collector system
  4. From the Actions pane, select task to configure the Health Service: nworks Collector Tasks > Configure OpsMgr agent
  5. Run this task against each collector system

Version 6.x and later

After discovery of collector services is complete in Ops Mgr, you should see the collector servers listed under the Veeam Collector s > _Veeam Collectors view. The task should run automatically when the collector is installed, but to run it again at any time later with the following instructions:

 

  1. Open the Monitoring pane of OpsMgr console
  2. Select the Veeam for VMware > Veeam Collectors >  _Veeam Collectors view
  3. Select the collector system
  4. From the Actions pane, select task Veeam VMware Collector Service Tasks > Configure Health Service
  5. Run this task against each collector system

Note: The task will cause the Health Service to restart. Also, the values (listed below) are the default base values. If they values in the registry are already higher than the ones associated with the task, they will not be lowered by the task. In addition, you have may increase these values by editing the parameters before running the task, if it is necessary to increase these values beyond the default.


Manual configuration of the agent

To configure the agent manually, it is necessary to create/change certain keys in the registry on the collector system. All of the settings below as DWORD values with the data expressed in decimal format (please note that the registry editor defaults to hexadecimal).



Registry Key: HKLM\SYSTEM\CurrentControlSet\Services\HealthService\Parameters\

NameValue
Persistence Cache Maximum102400
Persistence Checkpoint Depth Maximum104857600
Persistence Version Store Maximum20480
State Queue Items20480

Note: If the State Queue Items entry does not already exist, it should be created as a 32-bit DWORD value.


Registry Key: HKLM\SYSTEM\CurrentControlSet\Services\HealthService\Parameters\Management Groups\<GroupName>

MaximumQueueSizeKb204800


The changes to the registry will take effect when the Health Service on the collector system is restarted.

More Information

Please note that if the OpsMgr agent on any Collector server is repaired or reinstalled, then the above task should be run again.

Please be aware that starting from September 2018 downloading updates will require an active contract for the corresponding product.

OK

Rate the quality of this KB article: 
5 out of 5 based on 1 ratings

Couldn't find what you were looking for?

Below you can submit an idea for a new knowledge base article.

Request new content

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!

Orphus system