Configure CMA Policies

To create a monitoring policy:

1. Log on to the TrueSight console.
2. In the navigation pane, expand Configuration and select Infrastructure Policies.
3. In the Infrastructure Policies page, ensure that the Monitoring tab is selected and click Create Policy.
4. In the Create Monitoring Policy page, specify the monitoring policy properties:

   Step 1 - Define the General Properties

   Property	Description
   Name	Name for the policy. The policy names must be unique. In an environment with tenants, the policy names must be unique for a single tenant. It is a mandatory field.
   Description	(Optional) A brief description about the policy.
   Associated User Group	Name of the user group that is associated with the PATROL Agents as defined in the Authorization Profile or in the PATROL Agent ACLs. The policy is applicable to these PATROL Agents.
   Share with User Group	Specify whether this policy is to be shared with the users across the associated user group or not. This property can be viewed in READ-ONLY mode by other users of the associated user group. Only the owner of the policy can modify this property.
   Precedence	Priority of the policy. Based on the precedence number that you configure, the configuration is applied to the PATROL Agents and the Infrastructure Management servers. The precedence number ranges from 0 to 999. A lower number indicates a higher precedence. The default value is 900. The configuration from a policy with a higher precedence overrides the configuration from a policy with a lower precedence. If two policies have the same precedence number, then the configuration from the latest created policy takes priority.
   Enable Policy	Indicates whether the policy is enabled or disabled. By default, the policy is disabled. If you do not enable a policy when you create it, the policy configurations are not applied to the PATROL Agents and the Infrastructure Management Servers. If you disable any existing policy, the policy configurations are removed from the PATROL Agents and the Infrastructure Management servers, where the policy was applied.

   Step 2 - Select the PATROL Agents

   Define conditions to select the PATROL Agents on which you want to apply the policy:

   1. Select a property.
   2. Select an operator to create the condition. The available operators depend on the property that you select.
   3. Specify a value for the selected property.
   4. (Optional) To add more than one condition, click the button, and perform the earlier steps.
   5. (Optional) To group the conditions, use the parentheses and Boolean operators from their corresponding lists.

   The Add Monitor Types dialog box presents configuration fields for compatible BMC PATROL monitoring solutions that are located in the Central Monitoring Repository.

   Step 3 - Select the Required Monitor Type

   1. Click the Monitoring tab.
   2. Click Add Monitoring Configuration.
   3. In the Add Monitoring Configuration dialog box, configure the properties:
      • From the Monitoring Solution menu, select Veritas Cluster Server KM.
      • From the Version menu, select the required version.

   The Monitor Profile Veritas Cluster Server KM is automatically selected.

   

   Refer to the table below to know which monitor types are available and their function:

   Monitor Type	Description
   Veritas Cluster Server KM (REQUIRED)	To set the general settings of the Veritas Cluster Server monitoring solution (credentials, debug mode, instances, multi-node mode, etc.). Once this monitor type is configured, all other monitor types are automatically monitored. Their default behavior can however be modified by selecting them from the Monitor Type list. No other monitor types can be configured as long as Veritas Cluster Server KM is not configured.
   VCS Agent	To modify the agent default monitoring.
   VCS Daemon	To modify the daemon default monitoring.
   VCS GAB Port	To modify the GAB port default monitoring.
   VCS Group System	To modify the group system default monitoring.
   VCS LLT Interface	To modify the LLT interface default monitoring.
   VCS Log	To modify the log default monitoring.
   VCS Resource	To modify the resource default monitoring.
   VCS Resource System	To modify the resource system default monitoring.
   VCS Service Group	To modify the service group default monitoring.
   VCS System	To modify the system default monitoring.
   VCS System Heartbeat	To modify the system heartbeat default monitoring.
   VCS WAN Heartbeat	To modify the WAN heartbeat default monitoring.

   Step 4 - Configure the Selected Monitor Type

   1. Depending on the selected Monitor Type, the available fields will vary. Refer to appropriate section below to know how to configure them.
   2. Click Save to apply your changes to the selected PATROL Agent(s).

   Step 5 - Update the Status Mappings

   The predefined status mappings can be changed, using the Monitoring Studio Web Interface.

To edit a monitoring policy

1. Log on to the TrueSight console.
2. In the navigation pane, expand Configuration and select Infrastructure Policies.
3. In the Infrastructure Policies page, locate the monitoring policy you wish to modify, click its action button and click Edit.
4. In the Edit Monitoring Policy page, locate the monitoring configuration you wish to modify and click its action button to access the monitoring options panel.
5. Customize the configuration.
6. Click Save to apply your changes to the selected PATROL Agent(s).

Configuring the Log Scan Limit

Veritas Cluster Server KM scans log files by reading the new log entries since the last data collection cycle. By default, 2 MBytes of data is scanned for each log file during each data collection cycle. This log scan limit can however be modified to better suit your requirements.

To customize the log scan limit:

1. From the Add Monitoring Configuration panel, select VCS Log from the Monitor Type list.
2. In the VCS Log Settings panel, click Add.

   

3. In the Hostname field, enter:

   • localhost to apply these settings to all PATROL Agents installed on the VCS server
   • a hostname or IP address to apply these settings to a specific server
4. Indicate the amount of data (in KBytes) that will be read by the monitoring solution during each data collection cycle.
5. Click OK twice.
6. Click Save.

Configuring Windows Event Log Query Limit

By default, Veritas Cluster Server KM limits the Windows event log query to the last 300 minutes. This limit can however be modified to better suit your requirements.

To customize the log query limit:

1. From the Add Monitoring Configuration panel, select VCS Log from the Monitor Type list.
2. In the VCS Log Settings panel, click Add.

   

3. In the Hostname field, enter:

   • localhost to apply these settings to all PATROL Agents installed on the VCS server
   • a hostname or IP address to apply these settings to a specific server
4. In the Query Limit (in Minutes) field, indicate the maximum limit (in minutes) you wish to query in the raw log or event log during each data collection cycle.
5. Click OK twice.
6. Click Save.

Configuring Custom VCS Logs Monitoring

To override the default configuration and add additional log files, you will have to configure the custom VCS Logs monitoring as follows:

1. From the Add Monitoring Configuration panel, select VCS Log from the Monitor Type list.
2. In the VCS Log Settings panel, click Add.
3. In the Custom VCS Logs section, click Add.

   

4. In the Filename (Full Path) field, enter the full path to the VCS Log file to be monitored using backslash (/) as the file path separator (example:\var\adm\messages). For Windows events, prefix the filename with Events - (example: Events - Systems).

5. (Optional) Enter a brief description of the VCS log.
6. Click OK.
7. Click OK twice.
8. Click Save.

The KM is preconfigured with regular expressions that will generate a warning or an alarm when found in the custom VCS log. These regular expressions can be changed through the Monitoring Studio Web Interface.