Follow these steps:
Specifies the name of the alert.
Specifies the alert template name from which the alert is derived.
Note: Select a template from the drop-down list to create a template-based alert. For example, Asset Jobs not Updated.
Specifies the script name for script-based alerts.
Specifies the parameters suitable to the alert.
Note: When the alert is derived from a template, the template parameters are carried over from the template. For example,
GROUPS=ComputerGroups;RequiredPercentage=MINPERCENT;IncludeLinkedAssetJobs=TRUE;IncludeLinkedGroupJobs=TRUE;assetJobNames=%
Note: You can also specify parameters for script-based alerts.
Defines the alert-related information that is evaluated when an alert condition is detected. This evaluated information is passed as part of the alert raised by HM Agent. For example,
Less than $PERCENTAGE of the computers reported the asset job results from within the computer group $GROUPS
Configures the severity of the alert from the drop-down list.
Specifies the state of the alert. When set to True, the alert is monitored by the HM agent otherwise excluded from monitoring.
Specifies the tiers on which the alert is detected. For example, EM, DM, SS, and Agent.
Note: For predefined alerts, select the tiers from the supported list. For template-based alert, select a tier from the template-supported ones.
Specifies the interval at which the alert is monitored. You can specify the frequency in minutes, hours or days for each detected tier.
Specifies the threshold value. This value indicates the minutes/hours/days an alert condition is present, or the number of times an alert condition occurs before raising an alert.
For example, when you configure Agent not able to communicate to SS with a frequency of one hour and a threshold of six hours on the Agent tier, the HM Agent checks every one hour to see if the agent is able to communicate to the remote scalability server. On failure to communicate for six hours, an alert is raised.
Identifies the remediation methods for the alert.
Starts the CAF service.
Repairs the components that are specified under Parameters. The agents must be staged on Scalability server. (available for Windows only).
Specifies the component(s) on which remediation is required. For example, for hmRepairWinAgent.dms, you can specify AM, SD, RC, and ALL that require repair as remediation. Specify combinations of AM, SD, RC, and ALL with comma separated list.
Note: In case of hmRepairWinAgent.dms, you must configure the following parameters before applying the policy to the agent.
To share the SD Package Library run the command sd_sscmd addshare SDLIBRARY on the scalability server.
Double-click the Package Library Share, go to value field, and specify the shared folder path as one of the following:
\\<hostname>\sdlibrary$
The <hostname> specifies the host name or IP address of the scalability server.
\\%SCALABILITY_SERVER%\SDLIBRARY$
This macro is evaluated on the agent and is replaced with hostname or IP address or FQDN of the scalability server that is configured using caf setserveraddress command on the agent.
Double click the User Name parameter, go to Value field, and specify the user name to access the share.
Double click the Password parameter, go to Value field, and specify the password used to access the share.
Note: The user name and password are optional, if the SDLIBRARY$ share is set up as a NULL session share. Following security options must be set in the Local Security Policy for using null session shares.
1) Network Access: Restrict anonymous access to Named Pipes and Shares – Disabled
2) Network Access: Let Everyone permissions apply to anonymous users - Enabled
Reboot the machine for the changes to take effect.
Double click Remediation Script Time-out, go to value field, and specify the time required for remediation based on your network environment.
The alert is now configured.
|
Copyright © 2014 CA Technologies.
All rights reserved.
|
|