Moogsoft Docs

Configure the HP OMi Polling LAM

HP Operations Manager (OMi) is an automated IT operations management software application. HP OMi provides automated monitoring, root cause identification and prioritization with automated remedial action.

See HP OMi Polling for UI configuration instructions.

Note

HP OMi duplicates events within its event browser. The LAM does not fetch all the duplicated events, instead it fetches only single event which is duplicated into multiple events.

Before You Begin

Before you set up the LAM, ensure you have met the following requirements for each HP OMi server:

  • You have the URL of the HP OMi Server.

  • You have credentials to connect to the HP OMi server.

  • You have the URI of the REST server where the HP OMi integration can fetch events.

  • The port for your HP OMi server is open and accessible from Moogsoft AIOps.

Configure the LAM

Edit the configuration file to control the behavior of the HP OMi LAM. You can find the file at $MOOGSOFT_HOME/config/hp_omi_lam.conf.

See the LAM and Integration Reference for a full description of all properties. Some properties in the file are commented out by default. Uncomment properties to enable them.

  1. Configure the connection properties for each target source:

    • url: IP address or host name or FQDN of the HP OMi server along with the port on which it will communicate. For example, http://examplehpomi:80

    • username: Username of the account used to log in to the HP NNMi console

    • password or encrypted_password: Password or encrypted password of the account used to log in to the HP NNMi console.

  2. Configure the LAM behavior for each target:

    • events_date_format: Format of the date/time in event response, in the format "yyyy-MM-dd'T'HH:mm:ss" or "yyyy-MM-dd'T'HH:mm:ss.SSSXXX". If set to blank, event date/time is set to epoch time.

    • event_uri: URI of the REST Server from which the events will be fetched.

    • request_interval: Length of time to wait between requests, in seconds.

    • max_retries: Number of times the LAM attempts to reconnect after connection failure.

    • retry_interval: Length of time to wait between reconnection attempts, in seconds.

    • timeout: Length of time to wait before halting a connection or read attempt, in seconds.

  3. Configure the SSL properties if you want to encrypt communications between the LAM and the REST connection:

    • disable_certificate_validation: Whether to disable SSL certificate validation.

    • path_to_ssl_files: Path to the directory that contains the SSL certificates.

    • server_cert_filename: SSL root CA file.

    • client_key_filename: Client SSL key.

    • client_cert_filename: Client SSL certificate.

  4. Optionally configure the LAM identification and capture logging details:

    • name: Maps to $Laminstancename, so that the agent field indicates events Moogsoft AIOps ingests from this LAM.

    • capture_log: Name and location of the LAM's capture log file, which it writes to for debugging purposes.

  5. Optionally configure severity conversions. See Severity Reference for further information and "Conversion Rules" in Data Parsing for details on conversions in general.

  6. Optionally configure the process logging details:

    • configuration_file: Name and location of the LAM's process log configuration file. See Configure Logging for more information.Configure Logging

Example

You can configure the HP OMi LAM to retrieve events from one or more sources. The following example demonstrates a configuration that targets two HP OMi sources. For a single source comment out the target2 section. If you have more than two sources, add a target section for each one and uncomment properties to enable them.

monitor:
    {
        name: "HpOmi Lam Monitor",
        class: "CHpOmiMonitor",
        request_interval: 60,
        max_retries: -1,
        retry_interval: 60,
        targets:
        {
            target1:
            {
                url: "http://examplehpomi1:80",
                user_name: "hpomi_user1",
                #password: "password",
                encrypted_password: "qJAFVXpNDTk6ANq65pEfVGNCu2vFdcoj70AF5BIebEc=",
                events_date_format: "yyyy-MM-dd'T'HH:mm:ss.SSSXXX",
                event_uri: "/opr-web/rest/9.10/event_list",
                request_interval: 60,
                max_retries: -1,
                retry_interval: 60,
                timeout: 120,
                disable_certificate_validation: false,
                path_to_ssl_files: "config",
                server_cert_filename: "server1.crt",
                client_key_filename: "client1.key",
                client_cert_filename: "client1.crt",
                ssl_protocols: [ "TLSv1.2" ]
                        }
            target2:
            {
                url: "http://examplehpomi2:80",
                user_name: "hpomi_user2",
                #password: "password",
                encrypted_password: "bDGFSClSHBn8DSw43nGwSPLSv2dGwdsj50WD4BHdfVa&",
                events_date_format: "yyyy-MM-dd'T'HH:mm:ss.SSSXXX",
                event_uri: "/opr-web/rest/9.10/event_list",
                request_interval: 60,
                max_retries: -1,
                retry_interval: 60,
                timeout: 120,
                disable_certificate_validation: false,
                path_to_ssl_files: "config",
                server_cert_filename: "server2.crt",
                client_key_filename: "client2.key",
                client_cert_filename: "client2.crt",
                ssl_protocols: [ "TLSv1.2" ]
            }
        }
    }
Configure for High Availability

Configure the HP OMi Polling LAM for high availability if required. See High Availability Overview for details.

Configure LAMbot processing

The HP OMi LAMbot processes and filters events before sending them to the Message Bus. You can customize or bypass this processing if required. You can also load JavaScript files into the LAMbot and execute them.

See LAMbot Configuration for more information. An example HP OMi LAM filter configuration is shown below.

filter:
{
    presend: "HpOmiLam.js",
    modules: [ "CommonUtils.js" ]
}
Start and Stop the LAM

Restart the HP OMi LAM to activate any changes you make to the configuration file or LAMbot.

The LAM service name is hpomilamd.

See Control Moogsoft AIOps Processes for the commands to start, stop and restart the LAM.

You can use a GET request to check the status of the HP NNMi LAM. See "Check the LAM Status" in Configure the REST LAM for further information and examples.

Configure HP OMi

After you have the HP NNMi LAM running and listening for incoming requests, you can configure HP NNMi. See "Configure HP NNMi" in HP OMi Polling.