Setting up a system filter
fileSet up the following discovery overrides for the ESI Service. After setting up all applicable overrides, you can then enable the discovery of the ESI Service. Setting up the ESI Service Host override provides details.
Setting up a system filter
file
Changing
the HTTPS to HTTP override
Setting the
Ignore client certificate error override
Setting basic
authentication overrides
Setting up an
ESI Service SCOM monitoring agent
Setting up the ESI Service
Host override
Enabling the ESI Service
discovery
Setting up a system filter file
If you are using more than one SCOM agent
to connect to one or more ESI Services, set up a system filter file
for each SCOM agent. The filter file tells the SCOM agent which
system to monitor. This text file must be set up on each SCOM agent
with the ESI Service Registered Systems Friendly Name for all the
supported systems. Confirm that each system appears in a single
list.
To set up the system filter file on a SCOM agent for an ESI Service:
On the SCOM agent, open Notepad.
Type the ESI Service Registered Systems Friendly Name of each supported system being monitored by this agent. Use one name per line in the text file.
Save the file to a location on the SCOM agent machine. Confirm that the Windows domain account set up in the Run As Account has at least read access to this file.
Enter the full path to this file in the Filter File Path override field for the ESI Service Discovery management pack.
If the SCOM agent must connect to the ESI Service through a web proxy server, provide the following information for the Proxy Server and Bypass List overrides in the EMC SI Service Discovery for each related SCOM agent:
Proxy server: proxy server string. For example:
proxy_server:80
Bypass List: domain bypass list string. For example, the following represents that the discovery can bypass the proxy server when the host name ends with .emc.com:
. *.emc.com
If the overrides above are not set, then the proxy settings are obtained from the registry. This assumes the proxy configuration tool, Proxycfg.exe has been run. If Proxycfg.exe has not been run, then the ESI Service can be accessed directly.
Changing the HTTPS to HTTP override
The SCOM agent will always try to connect to the ESI Service by using an HTTPS connection. By default, if the HTTPS connection fails, the SCOM agent cannot communicate with the ESI Service.
If you want the ESI Service to connect with an HTTP connection instead of an HTTPS connection, you can set the HTTPS to HTTP Override to True for the ESI Service connection.
Note: If you set up the override,
secure the SCOM agents. With this override, SCOM sends the username
and password as text, which can be hijacked. This option is a data
security risk.
To change the HTTPS to HTTP override:
Open the SCOM Operations Console and connect to the SCOM Management Group.
From the menu bar, select Go > Authoring.
In the left pane, select Object Discoveries.
Locate and double-click the EMC SI Service Discovery.
Open the Overrides properties and select to Override > For a specific object of class: Windows Computer.
In the Select Object dialog box, select the SCOM proxy agent that you want to connect to the ESI Service, and then click OK. The Override Properties page appears .
Click the Override checkbox for the HTTPS to HTTP Fallback override to enable it.
Change the value of the Override Value field to True and click OK.
Click Close to save the change.
HTTPS to HTTP Override
Setting the ignore client certificate error override
You can set up an override to ignore the client certificate when the SCOM agent connects to the ESI Service. You can set up this override by following the same steps in Set up HTTPS to HTTP override and selecting the Ignore Certificate Error override and setting it to True.
Setting basic authentication overrides
If one or more SCOM agents are not on the same domain or trusted domain as the ESI Service, you can use basic authentication. To use basic authentication, set up the User Name and Password overrides for the EMC SI Service Discovery.
Note: This override is a data security risk, because SCOM stores the username and password as text, so any user with SCOM console access or access to the file system on the agent can view and hijack the account credentials. If you set up the basic authentication overrides, you must secure the SCOM agents to avoid this risk.
Setting up an ESI Service SCOM monitoring agent
If you install a SCOM agent on the ESI controller host, the agent discovers and monitors the health state of the ESI Service. The SCOM agent periodically checks to see if the ESI Service is running and checks the application event log for any events written by the service. The agent also raises alerts if the service is not running, if any events that indicate problems with the service occur, or if any expected events are not received.
Some errors are only detected and reported with a SCOM agent installed on the ESI host controller. Your SCOM documentation has more details on agent installation considerations and instructions.
Setting up the ESI Service Host override
After changing the registry key value for each SCOM agent and setting up any applicable overrides, to set up the ESI Service Host override for each SCOM agent:
Open the SCOM Operations Console and connect to the SCOM Management Group.
From the menu bar, select Go > Authoring.
In the left pane, select Object Discoveries.
Locate and double-click EMC SI Service Discovery and the EMC SI Service Discovery Properties page appears.
Open the Overrides properties and select Override > For a specific object of class: Windows Computer.
EMC SI Service Discovery overrides
In the Select Object dialog box, select the SCOM proxy agent that you want to connect to the ESI Service from the list and click OK. The Override Properties page appears.
Change the override value for the ESI Service Host parameter to the IP address of the computer hosting the ESI Service.
If the default port number of 54500 or 54501 for the ESI Service has been changed, change the port parameter default value to the correct port number.
In the Select destination management pack list box, select the EMC Storage Integrator Customizations management pack.
Click Apply and confirm the changed values.
Click OK.
Note: If you change the Interval or Discovery Timeout (sec) values, discovery performance may be affected.
After completing this setup, export and save a copy of the EMC.SI.Customization.xml file as a backup of your customization values. If you lose a needed customization, you can import this backup copy to recover your set customizations.
Note: How to Monitor Using Overrides on Microsoft TechNet provides more information on creating overrides.
Enabling the ESI Service discovery
After setting up any applicable overrides and the ESI Service Host override, you must then enable the discovery of the ESI Service for each SCOM agent:
Open the SCOM Operations Console and connect to the SCOM Management Group.
From the menu bar, select Go > Authoring.
In the left pane, select Object Discoveries.
Locate and double-click EMC SI Service Discovery and the EMC SI Service Discovery Properties page appears.
Open the Overrides properties and select to Override > For a specific object of class: Windows Computer.
In the Select Object dialog box, select the SCOM proxy agent that you want to connect to the ESI Service from the list and click OK.
The Override Properties page appears.
Confirm the Enabled parameter name override is selected and that the override value is set to True.
In the Select destination management pack list box, select the EMC Storage Integrator Customizations management pack.
Click Apply and confirm the changed values.
Click OK.
Note: If you change the Interval or Discovery Timeout (sec) values, discovery performance may be affected.
After completing this setup, export and save a copy of the EMC.SI.Customization.xml file as a backup of your customization values. If you lose a needed customization, you can import this backup copy to recover your set customizations. This file is installed with version number 1.0.0.0. You can increment the version number when you make changes.
Note: How to Monitor Using Overrides on Microsoft TechNet provides more information on creating overrides.