Systems Infrastructure Aspects

1. Enable baselining in Operations Agent.

   By default, baselining is disabled on the Operations Agent node. You can enable baselining either through command line or configuration file.

   For more information about how to enable baselining through command line, see the section Configuring Baseline on the Operations Agent Node in the Operations Agent (12.0 or later) - User Guide.

   To enable base using the configuration file, follow the steps:

   1. Open the Policy Template pane:

      Administration > Monitoring > Policy Template.

   2. In the Policy Template Groups pane, expand Policy Management > Templates grouped by type > Configuration > Node Info.
   3. In the Policy Templates pane, select the OPC_PERL_INCLUDE_INSTR_DIR policy and click . The Edit Node Info Policy window opens.

   4. In the Policy Data pane, at the end add the following lines:

      [oacore]

      ENABLE_BASELINE=TRUE

   5. Click Save and Close.

   Baseline data is computed only at the end of every hour. If you want the baseline data to be computed immediately after you enable baseline, you must restart the oacore process.

   Run the following command to restart oacore:

   ovc -restart oacore

2. Define metrics to create baseline metrics.

   Based on the classes defined in the baseline.cfg file, corresponding baseline classes are created in the Metrics Datastore. For every metric specified in the baseline.cfg file, sixteen baseline metrics are created. The original baseline.cfg file is available at %OvDataDir%/conf/sispi/configuration location. The baseline.cfg file is overwritten after the ConfigFile policy is deployed.

   For more information about baseline metrics, see the chapter Overview of Baselining in the HP Operations Agent (12.0 or later) - User Guide.

3. Decide where the deviation is required.

   You can configure deviations (N) either in the Sys_ConfigureBaselining policy or in the Sys_AdaptiveThresholdingMonitor policy.

   • To configure deviations for specific metrics, set the deviations in the Sys_ConfigureBaselining policy.
   • To configure deviations for all metrics, set the deviations in the Script-Parameters tab in the Sys_AdaptiveThresholdingMonitor policy.
   • If no deviations are set for a metrics in the Sys_ConfigureBaselining policy, then the deviations set in the Sys_AdaptiveThresholdingMonitor policy are used to calculate adaptive threshold values.

4. Edit Sys_ConfigureBaselining ConfigFile policy to specify single deviation.

   1. Open the Management Templates & Aspects pane:

      Click Administration > Monitoring > Management Templates & Aspects.

   2. In the Configuration pane, expand Configuration Folders > Infrastructure Management > System Infrastructure Aspects.
   3. In the Management Templates & Aspects pane, select the Adaptive Thresholding Aspect and click . The Edit Aspect window opens.
   4. In the Policy Templates tab, double-click Sys_ConfigureBaselining policy. The Edit ConfigFile Policy window opens.

   5. In the Policy Data tab, specify class, metric and deviation in the following format.

      <Class>:<Metric>,<Warning Deviation>,<Minor Deviation>,<Major Deviation>,<Minimum Value>,<Maximum Value>,<CutOff>

      In this instance:

      • <Class> is the metrics class.
      • <Metric> is the metrics for which baseline data must be computed.

      Only class and metric are mandatory. You can define deviation for specific instance for instance based monitoring.

      For Example,

      dsk0,0.1,0.2,0.3,0,100,20

      dsk1,0.2,0.3,0.4,0,100,15

      dsk2:exclude

      For every group, one corresponding CFG file is created. The CFG files are automatically deleted once the instance metric are delete in the policy.

   6. Click Save and Close.

5. Edit Sys_AdaptiveThresholdingMonitor policy for defining deviation for each metric.

   1. Open the Management Templates & Aspects pane:

      Click Administration > Monitoring > Management Templates & Aspects.

   2. In the Configuration pane, expand Configuration Folders > Infrastructure Management > System Infrastructure Aspects.
   3. In the Management Templates & Aspects pane, select the Adaptive Thresholding Aspect and click . The Edit Aspect window opens.
   4. In the Policy Templates tab, double-click Sys_AdaptiveThresholdingMonitor policy. The Edit ConfigFile Policy window opens.

   5. In the Policy Data tab, you can modify the default parameters in the Policy Parameters tab.

   6. Click Save and Close.
6. Include the latest version of policies in Aspect and deploy.

This Aspect monitors the Operations Agent baseline metrics.

CCI Monitoring

During the first polling interval, backup of all the files specified in the ccilist.cfg file. From the consecutive polling, a comparison is performed between current version and backup version of files. Alerts are generated if modification is identified. The backup files are overwritten with fresh backup. Comparison is always between current version and recent backup version of files.

Desired State Monitoring

A gold file (with extension .gold) must be created for every single file that must be monitored and must be available in the same directory as the file. A gold file is a backup or reference file that remains unchanged.

For example, let us consider that you want to monitor the mtab file located in the /etc directory. Take a backup of this file and save it as mtab.gold in the /etc directory. This is your reference file or gold file which does not change. To monitor the mtab file add the following to the configuration file:

/etc/mtab==/etc/mtab.gold,file,Os,,major.

After deploying the Aspect, a check is performed to verify if desired state monitoring is defined in the ccilist.cfg configuration file. A comparison is performed for the files, windows registry settings, and command outputs specified in the configuration file with the corresponding gold file. Alerts are generated whenever there is a difference is identified between the two files.

You must tune one of the following policies based on the Operating System of the node to specify CCI or desired state monitoring:

• Sys_MSWindowsChangeConfig
• Sys_SunSolarisChangeConfig
• Sys_LinuxChangeConfig
• Sys_HPUXChangeConfig
• Sys_AIXChangeConfig

1. Open the Management Templates & Aspects pane:

   Click Administration > Monitoring > Management Templates & Aspects.

2. In the Configuration pane, expand Configuration Folders > Infrastructure Management > System Infrastructure Aspects.
3. In the Management Templates & Aspects pane, select the Change Configuration Monitor Aspect and click . The Edit Aspect window opens.
4. In the Policy Templates tab, double-click the required policy. The Edit ConfigFile Policy window opens.

5. In the Policy Data tab, specify class, metric and deviation in the following format.

   change ci key,cci type (file|cmd),msg group,backup filename,alert severity

   In this instance:

   • <change ci key> - Specifies a registry key, a command or a file name with complete path.

   • <cci type> - Set this to the following values - cmd, regkey, or file based on the change ci key. Registry key (regkey) type is available only for Windows managed nodes.

   • <msg group> - Specifies the OMi message group setting for the change alert. The default message group is Misc.

   • <backup filename> - This is the name with which a backup file is created in the backup folder. The backup file created is used for comparisons with the parent file (provide empty value for monitoring CCI type 'file'). (not required for cci type file) Backup folder is located in the<OvDataDir>/tmp file.

   • <alert severity> - Specifies the HPE OMi alert severity setting. The default alert severity is Warning.

6. Click Save and Close.

Aspect monitors the system configuration related changes.

[ProcessGroupName]

Process name<tab>Argument<tab>Time of the day<tab>Days of Week<tab>Bounds

In this instance,

• Process Name: Specifies the name of the process to be monitored.
• Arguments: Specifies the arguments that are used to distinguish between multiple processes running simultaneously. If no arguments are present, an asterisk (*) must be specified.
• Time of the day: Specifies the time duration (in the 24-hour format) during which a process failure must be reported.
• Day of Week: Specifies the day or days to report process failure. Each day of week is identified with a number as listed in the table. 0 being Sunday and 6 being Saturday. Numbers should be separated by commas.

• Bounds: Specifies the number of instances of named processes. You can specify the number of instance as follows:

  n: An exact number

  n: A minimum of n

  -n: A maximum of n

  m-n: A range of m to n

• @ severity: Specifies the severity of alert messages such as Minor, Major or Critical. Default severity is Warning.

• @Start: Specifies the command (<cmd>) that must be run during a process failure.

Scenarios and syntax for customizing ConfigFile policy:

[ProcessGroupName]

processname<tab>Argument<tab>ProcessLimits

/opt/OV/lbin/eaagt/opcmona	*	1

[OMi_Mgt]

/opt/OV/bin/oacore	oacore /var/opt/OV/conf/oa/PipeDefinitions/oacore.xml	1

[ProcessGroupName]

processname<tab>Argument<tab>Timeoftheday<tab>Daysofweek<tab>ProcessLimits

[OMi_Mgt]

/opt/OV/lbin/agtrep/agtrep	-start	5-23	0,1,2,3	1

This Aspect consists of the following policy templates: