Configure Operations Connector High Availability Policies

You can create or edit an Operations Connector High Availability template using the Operations Connector High Availability policy editor, which you can open in the following ways.

• To open the editor from the Edit Aspect dialog box:

  1. Open the Management Templates & Aspects manager:

     Administration > Monitoring > Management Templates & Aspects

     Alternatively, click Management Templates & Aspects.

  2. In the Configuration Folders pane, expand the configuration folders.

  3. In the Management Templates & Aspects pane, click an aspect, and then click the  Edit Item button.

     The Edit Aspect dialog box opens.

  4. Click the Policy Templates tab, and then do one of the following:

     • To add a new policy template:

       1. Click the Add Policy Templates From List button. The Add Policy Templates From List dialog box opens.

       2. Click the  New Item button, and then click the Add New Policy Template or the Add New Policy Template (Raw Mode) button. The Select Type for New Policy Template dialog box opens.

       3. Select the type Operations Connector High Availability, and then click OK.

     • To edit an existing policy template, click the policy template in the list, click the button, and then click the Edit Policy Template or the Edit Policy Template (Raw Mode) button.

     The Operations Connector High Availability policy editor opens.

• To open the editor from the Policy Templates manager:

  1. Open the Policy Templates manager:

     Administration > Monitoring > Policy Templates

     Alternatively, click Policy Templates.

  2. In the Policy Template Groups pane, expand Policy Management > Templates grouped by type.

  3. Depending on the type of data collected by the particular policy, expand Configuration, Events, Generic, Metrics, or Topology. Each policy type can be used only for a subset of the available data types.

  4. Click the Operations Connector High Availability item, and then do one of the following:

     • To add a new policy template, in the Policy Templates pane, click the button, and then click the Add New Policy Template or the Add New Policy Template (Raw Mode) button.

       The New ConfigFile policy editor opens.

     • To edit an existing policy template, click the policy template in the Policy Templates pane, click the button, and then click the Edit Policy Template or the Edit Policy Template (Raw Mode) button.

       The Edit ConfigFile policy editor opens.

Operations Connector High Availability package policies define the integration policies, collectors, and data that operate in an high-availability mode. Only Operations Connector policies that are deployed as part of an HA package are high available. Policies defined locally (on the nodes) are not high available.

To define an Operations Connector HA package policy, you must create a HA package. Operations Connector HA packages contain the following elements:

• Policies, which implement data integration by transformation, enrichment, and filtering.

• Components, which are typically data collectors (executables) that run on the Operations Connector. They can either be controlled by OVC or by external commands.

  The management mode defines when the policies are enabled. They are by default managed from the OpsCx HA component and enabled if the package is active on an Operations Connector node and disabled if not. Alternatively they can be always enabled from the OpsCx HA component, regardless whether the package is active on a node or not.

• Sync items (files), which are synchronized to all nodes. Sync items contain the run-time information typically used by collectors, for example the timestamps on when the data was read the last time and similar.

Each element (a policy, a component, or a sync item), can be added to the package only once.

The policies can be activated either by Operations Connector or externally by a specified command, if for example the component needs to be active on a specific node.

Event back synchronization

Events are synced back by the active node. If the back sync target is inactive, the event ID is forwarded to an ombacksync instance of another Operations Connector node through the network and the next ID is processed.

Metric data

Metric data is collected on the active node and is replicated to the other nodes by the bsmczedo service.

Topology data

Topology data is collected on the active node and forwarded to OMi. If delta detection is enabled for the topology processing policies, the processed topology data is replicated to other nodes by the bsmczedo service to avoid data duplication in case of a failover.

In the Operations Connector High Availability policy editor, follow the steps:

1. In the Properties page, define general policy information.
   

   Type the name of the policy in the Name text box.

   Optional. Provide a description of the policy (Description), select the instrumentation that will be deployed with the policy onto the host system where the agent is running (Instrumentation), and select the operating systems with which the policy is compatible (OS Types).

   For more information, see Properties Page.

2. In the HA package page, define the policy content.

   The name of the package is set in the Properties page and cannot be changed.

   Optionally, select use command to determine activation state and enter the command that determines if a package should be enabled on the current node. By using a command, you can enable the package depending on external constraints, such as whether the external software is active on a node and similar. If the command returns 0 as the exit code, the package can be activated. A non-zero value means that the package may not be activated on this specific node now. The command is executed periodically on each node, so if the condition on a node changes, the package state changes accordingly after next scheduled execution.

   Add new policies, components, and sync items to the HA package configuration:

   1. In the Policies tab, add new policies.

      Click to add a new policy to the HA package configuration. To enter the policy name and ID, select Add Policy to HA Package configuration:. To select the policy from a list, select Add Policy to HA Package from list of available policy templates and select the policy in the Open the Policy Templates dialog box.

      Note Operations Connector High Availability polices cannot contain other Operations Connector HA policies.

      Optionally, select the management mode. By default, the polices are assumed to be in managed mode.

   2. In the Components tab, add new components.

      Click to add a new component. Enter the component name, and select the component control type (OV control or External). Depending on the selected control type, enter the OVC registration file or the component start-up and stop commands.

      Optionally, select the management mode.

   3. In the Sync Items tab, add new sync items.

      Click to add a new sync item and enter the sync item file name.

   For more information, see HA Package Page.

3. Click Save and Close to save the policy template and exit the dialog.

• To start troubleshooting, check the log files of the agent in the %OvDataDir%log directory (Windows systems) or the /var/opt/OV/log directory (Linux systems).

• To investigate issues related to policy execution, first examine the %OvDataDir%log\System.txt file (Windows systems) or the /var/opt/OV/log/System.txt file (Linux systems).

  Note The log files whose names start with the opr- prefix are generated by the OMi web console.

You can use the bsmczedo command to check the following:

• To get the state of each HA node, execute:

  <OvInstallDir>\lbin\eaagt\bsmczedo -check_nodes (Windows systems)

  /opt/OV/lbin/eaagt/bsmczedo -check_nodes (Linux systems)

• To get the state of each HA package on all HA nodes, execute:

  <OvInstallDir>\lbin\eaagt\bsmczedo -check_pkgs (Windows systems)

  /opt/OV/lbin/eaagt/bsmczedo -check_pkgs (Linux systems)