Free 30 Day Trial
Find the root-cause of your cloud, hybrid-cloud
or on-prem performance issues
|
||
|
Configuring the eG SCOM Connector
If the Launch Configuration & Setup Tool check box is selected in Figure 7, then finishing the installation will automatically launch the eG SCOM Connector configuration tool. If this check box is deselected, then, you will have to manually launch the configuration tool by following the menu sequence: Start -> Programs -> eG SCOM Connector. Either way, once the tool is launched, proceed to configure the connector using the steps discussed below:
Upon launching the tool, Figure 1 will appear with the SCOM Server tab page open.
Then, to check whether your specifications are correct, click the Test Connection button. If the eG SCOM Connector is able to connect to the SCOM server with the given specifications, then a message to that effect will appear.
Figure 2 : Connection to the SCOM server is successful
On the other hand, if the connector is not able to connect to the SCOM server, then a message indicating the connection failure and reasons for the same will appear.
In case of a failure, first click the ok button in Figure 3 to close the message box. Then, take another look at your specifications, make changes wherever necessary, test the connectivity yet again, and if successful, proceed with your configuration. To proceed, click the eG Manager tab page in Figure 4. Typically, the eG connector polls the eG manager for discovering the managed components/layers/tests/descriptors/measures from the eG Enterprise system and inserting corresponding monitoring objects and unit monitors in the SCOM server. Using the eG Manager tab page of Figure 4, you can indicate which eG manager is integrating with the SCOM server and how to connect to it. As part of this exercise, specify the following:
In the Manager Unique ID text box, provide a unique ID for the eG manager with which the SCOM server will be integrating.
Note:
In the Manager URL text box, specify the URL using which the connector should connect to the eG manager. The URL should be of one of the following formats, depending upon whether the eG manager is SSL-enabled or not: http://<eGManagerIP>:<Portno> or https://<eGManagerIP>:<Portno>.
Note:
The integration will work in a redundant eG manager setup as well. In other words, if the primary manager fails, then the SCOM connector is capable of automatically polling the secondary manager in the environment for state information.
Next, in User and Password text boxes specify the credentials of a user who is registered with the eG Enterprise system, and who has the right to monitor one/more components in the target environment. The components assigned to this user will only be managed by the SCOM server.
Finally, test whether the given specifications are correct by clicking the Test Connection button.
Click on the Connector Service tab page. If the connector service is yet to be installed, then the Start and Stop buttons in Figure 5 will be disabled. Also, the Connector Service Status will be Not installed (as shown by Figure 5). If the connector has been installed but is yet to be started, then the Start button alone will be enabled. You can click on the Start button to start the service and the Stop button to stop the service.
Now, click on the Setup tab in Figure 5 to execute the setup tasks. The Setup tab provides 2 options. Automatic setup will execute all the required tasks in a single action. To perform this auto setup, click on the Install button in the Automatic section of Figure 6. You can uninstall the connector at any point in time, by simply clicking the Uninstall button in the Automatic section.
On the other hand, if you wish to execute specific setup tasks, click on the Custom option and proceed as follows:
SCOM Agent: In large environments where hundreds of components are managed by the eG Enterprise manager, the load on the connector would increase as it attempts to discover all the components from the eG manager. This in turn may increase the load on the SCOM agent on the connector system as well, as this agent would now be handling the hundreds of discovered components and their corresponding state changes. Under conditions of such high load, the default performance settings for the SCOM agent may not be conducive to healthy agent-connector traction. By clicking the Optimize button here, you can change the values of default parameters to the values shown in the table below:
Registry Parameter | Location in Registry | Value |
---|---|---|
Persistence Version Store Maximum |
HKLM\System\CurrentControlSet\Services\HealthService\Parameters\ |
65536 decimal |
Persistence Cache Maximum |
HKLM\SYSTEM\CurrentControlSet\Services\HealthService\Parameters\ |
1048576 decimal |
State Queue Items |
HKLM\SYSTEM\CurrentControlSet\Services\HealthService\Parameters |
250000 decimal |
MaximumQueueSizeKb |
HKLM\SYSTEM\CurrentControlSet\Services\HealthService\Parameters\ ManagementGroups\<Management_Group_Name> |
262144 decimal |
Persistence Checkpoint Depth Maximum |
HKLM\SYSTEM\CurrentControlSet\Services\HealthService\Parameters |
52428800 decimal
|
These default settings are ideal for small/medium-sized environments, where only a few components are monitored - say, less than 50 components. Where the connector needs to handle a large number of components, the value of these registry entries have to be tuned further. This is because, with an increase in monitored targets, the load on the SCOM agent also increases. The agent will hence require more memory for its processing to be faster and also to avoid the following error in “Operations Manager” event log on the connector machine.
Event ID: 4506
Event Source: HealthService
Event Description: Operations Manager
Data was dropped due to too much outstanding data in rule <rulename> running for instance <instance name> with id:<instance id> in management group <management group name>.
To allow the SCOM agent to utilize more memory available in the system, you can use regedit to manually set a higher value for the Persistence Cache Maximum registry entries in HKLM\System\CurrentControlSet\Services\ HealthService\Parameters\.
First, double the current value of this parameter and check if performance improves. Also, confirm that no errors are captured by the event log post this change. If no performance improvements are visible, double the value of this parameter again. Repeat this procedure until the value of this parameter is set as high as “2048000”.
With the above setting, the typical memory usage of SCOM agent processes would be around 3GB.
Also, with this value increased, the startup and stopping of the “Health Service” will take longer than normal.
Note:
The Optimize button will be disabled if the registry entries mentioned in the table above have already been set to the values prescribed above.