After installation, you must configure the ULRM. Configuration of the agent involves specifying the primary and secondary Operations Sentinel server. Specifying a secondary Operations Sentinel server is optional but allows for more robust monitoring because it provides a hot-standby and concurrent monitoring capabilities.
The following environment variables specify the primary and secondary Operations Sentinel servers:
SPO_EVENT
SPO_EVENT_SECONDARY
The ULRMConfigure script sets up these environment variables for the ULRM. The ULRMConfigure script is called during installation to configure the environment variables and can also be called anytime after installation to change the values. If the ULRM is running when ULRMConfigure is called, the ULRM is terminated. The ULRMConfigure script automatically restarts the ULRM when it completes.
The ULRMConfigure script is located in the ULRM installation directory. The following is the call for the script:
ULRMConfigure [-quiet] [-CO] [-ipv4 or -ipv6] [-secure] [-trusted]
Without the –quiet option, ULRMConfigure prompts the user for the primary and secondary Operations Sentinel servers.
With the –quiet option, ULRMConfigure uses a response file so no user interaction is needed. The response file must be named ULRMResponse and located in the ULRM installation directory. The format for the file is as follows:
SPO_EVENT=<server> SPO_EVENT_SECONDARY=<server>
Where <server> is the network name or IP address for the Operations Sentinel server. Note that there are no spaces around the equal sign “=”. The SPO_EVENT_SECONDARY line is optional and used only when there is a backup Operations Sentinel Server.
With the -CO option, ULRM is configured in Concurrent monitoring mode.
Without the -CO option, ULRM is configured in Hot-standby mode.
With -IPv4, ULRM is configured for IPv4 network addressing.
With -IPv6, ULRM is configured for IPv6 network addressing.
With -secure, ULRM is configured for secure communication.
With -trusted, ULRM uses configured certificate to establish secure communication. With this option, the user must provide trusted certificate and private key while configuring ULRM. This allows the Operations Sentinel server to validate the client certificates when configured to do so.
Notes:
If no option is provided, by default, the following options are selected:
IPv4 network addressing.
Non-secure communication.
Certificate is not used to establish the secure communication.
ULRMConfigure starts the ULRM when it completes.
Configuring URLM on SAIL
ULRM is an agent that monitors host (PMM) resources. Based on a preconfigured monitor policy it sends alerts to the Operations Server when appropriate. The Resource Monitor configuration includes the Operations Server primary path information (IP or DNS address) and, optionally, the secondary path information if a second Operations Server is configured.
The ULRM can be configured by performing the following steps:
On the SAIL Control Center web page, click Configuration.
Click SAIL Resource Monitor.
Enter the IP or DNS address for the primary Operations Server in the Primary Path box.
Enter the IP or DNS address for the Secondary Operations Server in the Secondary Path box
Click Apply Configuration.
A message is displayed indicating that the configuration has been successfully updated.