Creating a notification job
Various types of notification actions are available for the creation of notification jobs.
For more generic information about job creation, see Creating a job.
The Log Event action (Add Action > Notifications > Log Event) is primarily intended for use in policies. This action logs an event to the Event Log.
In the Annotation field, specify the event to log. The annotation appears as the event description. When used as a policy action, the triggering condition trace is included in the description.
The Send Email action (Add Action > Notifications > Send Email) is primarily intended for use in policies. The action sends an email notification to one or more recipients. You can optionally attach one of the following reports to the email notification:
- Change Summary report
- Compliance Summary report
- Configuration Comparison report
- NEW IN 8.9.02Device Inventory report
- Discrepancy Summary report
This example illustrates attaching a Change Summary report to the email notification:
To configure the Send Email action, you must enter information in the following fields:
Specify an annotation to add to the email notification.
Specify an email subject for user-initiated jobs.
Specify additional text to add to the body of the email for user-initiated Jobs.
Select the email recipients.
(Optional) Select a report to attach to the email notification:
Include a report URL link in the email body.
Attach the report to the email in the selected format. Select a format (for example, PDF).
Include All Details
Include a detailed per-device difference report with the attached summary report.
Hide Sensitive Data
Hide sensitive data (for example, passwords, community strings) in the attached report.
|Hide Header and Footer |
(Applicable only for version 8.9.01 and later, and only for CSV format)
|Hide header and footer in the attached report.|
Select the network span to be included in the attached report. When the network span is Realm or Group, you can use Filter Devices to further narrow which devices to include in the report.
When the action is triggered in an event-based policy, additional network span options include: Same as Triggering Realm, Same as Triggering Group, Same as Triggering Device.
Additional report options are specific to each report type.
Sending an SNMP trap to a manager station
The Send Trap action (Add Action > Notifications > Send Trap) is primarily intended for use in policies. This action sends an SNMP trap to a Manager Station. To send multiple traps, create one action per destination Manager Station.
To configure the Send Trap action, you must enter information in the following fields:
Specify an annotation to include in the SNMP trap. When used as a policy action, the triggering condition trace is also added to the SNMP trap.
Select the type of trap to send. The Action Executed, Low Severity trap is the standard trap for event reporting. The Discrepancy Discovered and All Discrepancies Cleared traps are used by Manager Stations (for example, HP NNM) to set or clear discrepancy status on devices displayed on a topology map. You can send special Trap types for detection and clearing of compliance violations (Compliance Violation Discovered, All Compliance Violations Cleared).
Select the SNMP Manager Station(s) to receive the notification.
(Optional) Select a device to associate with the SNMP trap. If the action is triggered by a policy, the network span defaults to the triggering device.
The following text is an example of an SNMP notification:
Policy Severity (0/1) Event w/Change in Past 48 executed Annotation: Severity (0/1) and Change in Past 48 Description of the condition: [(Severity (0/1) Now && Change Detected Past); Severity (0/1) Now=True; Change Detected Past=True]