Table Of Contents
Using Notification Services
Understanding Notifications and Subscriptions
Customizing the Names of DFM Events
Configuring Event Sets and Notification Groups for Subscriptions
Configuring Event Sets
Configuring Notification Groups
Managing SNMP Trap Notifications
Adding an SNMP Trap Notification Subscription
Editing an SNMP Trap Notification Subscription
Suspending an SNMP Trap Notification Subscription
Resuming an SNMP Trap Notification Subscription
Deleting an SNMP Trap Notification Subscription
Managing E-Mail Notifications
Adding an E-Mail Notification Subscription
Editing an E-Mail Notification Subscription
Suspending an E-Mail Notification Subscription
Resuming an E-Mail Notification Subscription
Deleting an E-Mail Notification Subscription
Managing Syslog Notifications
Adding a Syslog Notification Subscription
Editing a Syslog Notification Subscription
Suspending a Syslog Notification Subscription
Resuming a Syslog Notification Subscription
Deleting a Syslog Notification Subscription
Using Notification Services
Device Fault Manager (DFM) generates alerts in response to events occurring in the IP fabric. DFM displays alerts in the Alerts and Activities display. In addition to monitoring operations with the Alerts and Activities display, you can forward information about alerts and events to other systems and users by using notification services.
Note 
Because DFM 2.0 does not report alerts generated on VLANs, you cannot create notifications for VLAN faults. However, you can view VLAN information on the event properties page and in the Detailed Device View. (Refer to Viewing Event Properties and Starting the Detailed Device View.)
The following topics explain notification service concepts and provide procedures for managing notifications:
•Understanding Notifications and Subscriptions
•Customizing the Names of DFM Events
•Configuring Event Sets and Notification Groups for Subscriptions
•Managing SNMP Trap Notifications
•Managing E-Mail Notifications
•Managing Syslog Notifications
Understanding Notifications and Subscriptions
This topic describe the types of notifications that DFM sends, defines a subscription, and explains how DFM matches alerts and events to subscriptions to determine when to send notifications.
Notification Services tracks events on device types, not on device components. For a list of supported events and the device types on which they can occur, refer to Events Processed.
Creating a Notification Subscription
To create a notification subscription, perform the following steps:
1. If you want to monitor a specific set of events or alerts, create one or more event sets that contain the events you want to monitor. Otherwise, all events and alerts will be monitored.
2. Create a notification group that specifies the criteria DFM should use when generating notifications:
•One or more event sets (if no event set is specified, all events and alerts are monitored)
•Devices, alert severity and status, and event severity and status
You can specify the notification group name, along with entering identifying information (using the Customer ID and Customer Revision fields).
3. Create a subscription by doing the following:
a. Select the notification type (SNMP Trap, E-Mail, or Syslog).
b. Name the subscription and apply a notification group to it.
c. Specify the recipients (hostname, e-mail address).
d. Save the subscription. It will automatically start running.
Notification Types
DFM provides three types of notifications:
•SNMP Trap Notification—DFM generates traps with information about the alert and the events that caused it. CISCO-EPM-NOTIFICATION-MIB defines the trap message format. For more information, see Notification MIB. DFM can also generate SNMP trap notifications for specified events.
Note Using SNMP trap notification is different from forwarding raw traps to another server before they have been processed by DFM. For information about the raw traps that DFM can forward, see Pass-Through SNMP Unidentified Traps.
•E-mail notification—DFM generates e-mail messages containing information about the alert and the events that caused it. CISCO-EPM-NOTIFICATION-MIB defines the message, which is included in the e-mail in text format. DFM can also generate e-mail notifications for specified events.
•Syslog Notification—DFM generates syslog messages that can be forwarded to syslog daemons on remote systems.
Subscriptions
DFM sends notifications based on user-defined subscriptions. You can create up to 32 notification subscriptions. A subscription for SNMP trap notification or e-mail notification includes the following common elements, as determined by the CISCO-EPM-NOTIFICATION-MIB:
•Devices—The devices or device groups of importance to the recipients.
•Alert severity and status—One or more alert severity levels and status.
•Event severity and status—One or more event severity levels and status. You can also customize the names of the events used by Notification Services, the Alerts and Activities display, and Fault History. Refer to Customizing the Names of DFM Events.
•Recipients—One or more hosts to receive SNMP traps or users to receive e-mail. For syslog notifications, the recipient would be the remote host containing a syslog daemon configured to listen for syslog messages.
•Name—A user-defined name to identify the subscription.
Subscriptions are based on user-configured event sets and notification groups. Refer to Configuring Event Sets and Notification Groups for Subscriptions for more information.
Alerts and Events
DFM sends notifications whenever an alert occurs that matches a subscription. DFM also sends notifications whenever specific events occur. For each alert or event, DFM compares the device, severity, and state against subscriptions and sends a notification when there is a match. Matches can be determined by user-configured event sets and notification groups. (The procedure for configuring notification groups is described in Configuring Event Sets and Notification Groups for Subscriptions.)
DFM assigns one severity to each alert or event and changes the state of an alert or event over time, responding to user input and changes on the device. Table 5-1 lists values for severity and explains how the state of an alert or event changes over time.
Note You can change event names to names that are more meaningful to you. Refer to Customizing the Names of DFM Events.
Table 5-1 Alert and Event Severity and Status
DFM categorizes alerts and events by severity and status...
|
Severity
|
Critical
Warning
Informational
|
Status
|
Active—The alert or event is live.
ACK—A user has manually acknowledged the alert. A user can acknowledge only active alerts or events.
Cleared—The alert or event is no longer active.
Note Alerts or events that have been cleared either expire or, if associated with a suspended device, remain in DFM until a user resumes or deletes the device.
|
For additional information, please see the following topics:
•Getting Alert Details
•Getting Event Details
Customizing the Names of DFM Events
Notification Services allows you to customize the names of events displayed in DFM. When you customize an event name, that name is reflected in all notifications, on the Alerts and Activities display, and in Fault History. The new event name is used for all instances of an event, regardless of the component on which the event occurs.
You can easily revert to the default event names as needed. The Notification Customization page also lists the new name and default name, so you can easily check which names have been changed.
Step 1 From the DFM home page, select Notification Services > Notification Customization. The Notification Customization page appears. as shown in Figure 5-1.
Figure 5-1 Notification Customization Page
Step 2 Select the event names you want to customize by clicking the check box beside each event name.
Step 3 Enter your new names in the New Event Description fields.
Step 4 Do one of the following:
•Click Save new descriptions to save your changes but not apply them to the DFM displays.
•Click Apply saved descriptions to apply your changes to subsequent DFM displays. When the confirmation window appears, click Yes, and your changes will be applied to DFM.
Step 5 To revert to default event names:
a. From the Notification Customization page, select the events you want to restore to their default names, and click Restore factory settings.
b. Apply your changes by clicking Yes when the confirmation window appears.
For additional information, please see the following topic:
•Getting Event Details
Configuring Event Sets and Notification Groups for Subscriptions
Before you can create an SNMP trap or an e-mail or syslog notification subscription, you must create a notification group. Creating event sets is optional.
•Event sets list the events you want monitored for notifications
•Notification groups contain the criteria that DFM should use when generating a notification:
–One or more event sets, or all events and alerts
–Devices
–Alert status and severity
–Event status and severity
–Fields for user-specified additional information you want to include with the subscription
Creating event sets and notification groups are described in the following topics:
•Configuring Event Sets
•Configuring Notification Groups
Configuring Event Sets
Event sets are simply groups of the events you want to monitor. You can create up to 9 event sets, labeled A through I. Once you have created an event set, you can apply as many of them as you want to a notification group, thereby tracking the specific events in which you are interested. If you do not specify an event set, DFM will monitor all events and alerts for notifications.
Step 1 From the DFM home page, select Notification Services > Event Sets. The Event Sets page appears, as shown in Figure 5-2.
Figure 5-2 Event Sets Page
The Event Sets page contains the following information.
Event Code
|
Notification Services code for the event. This number cannot be changed and is used to map default names to customized names.
|
Description
|
Event description (user-defined or default).
|
Severity
|
Event severity.
|
A - I
|
Event set label. If an X appears in this column, the corresponding event belongs to that event set.
|
Step 2 For each event set you want to configure, select events by doing one of the following:
•Select specific events by clicking the editable field under the label, and selecting X.
•Select or deselect all events for an event set using the Select/Deselect button.
Step 3 Click Apply.
Step 4 If you want to create a notification subscription, first create a notification group that uses your event set. See Configuring Notification Groups.
For additional information, please see the following topic:
•Configuring Notification Groups
Configuring Notification Groups
When you set up a subscription, DFM lets you choose from existing notification groups. You can then configure an SNMP trap or an e-mail or syslog notification to use a specific notification group. The notification groups contains the following information:
•One or more event sets, if desired (otherwise, the notification group will contain all events and alerts)
•Devices
•Alert status and severity
•Event status and severity
•Fields for user-specified additional information you want to include with the subscription
You can configure a maximum of 64 notification groups. If the DFM server is using Access Control Server (ACS) mode, ACS may limit the devices you can view and then apply to a notification group. Notification Services will not refilter the devices if there is a change in the device list you may access. For more information, refer to Device-Based Filtering.
Note You cannot delete a notification group that is being used by a running subscription.
Step 1 From the DFM home page, select Notification Services > Notification Groups. The Notification Groups page appears, as shown in Figure 5-3.
Figure 5-3 Notification Groups Page
Step 2 To create a notification group, click Add. (If you want to edit or delete a notification group, click the appropriate button and follow the instructions.)
Step 3 Specify the devices, alert severity and status, event sets (if desired), and event severity and status. Click Next.
Step 4 Specify the notification group name, and enter any desired identifying information in the Customer ID and Customer Revision fields.
•For e-mail and syslog notifications, if you leave these fields empty, they are left blank in the notification.
•For SNMP trap notifications, if you leave these fields empty, they are displayed as followed in any notifications:
Click Next.
Step 5 Create the notification group by clicking Finish.
Step 6 To create a notification subscription, follow the instructions in one of these topics:
•Adding an SNMP Trap Notification Subscription
•Adding an E-Mail Notification Subscription
•Adding a Syslog Notification Subscription
For additional information, please see the following topic:
•Configuring Event Sets
Managing SNMP Trap Notifications
The SNMP Trap Notifications page displays the following information:
•Subscription—The name of the user-defined request for notification.
•Status—The subscription status; can be either of the following:
–Running—DFM is using the subscription while monitoring alerts to determine when to send a notification.
–Suspended—DFM will not use the subscription unless you resume it.
•Notification Group—The name of notification group that is applied to the subscription.
You are completely in control of subscriptions. DFM does not delete subscriptions under any circumstances.
From the SNMP Trap Notifications page, you can perform the tasks listed in Table 5-2.
Adding an SNMP Trap Notification Subscription
After you add a subscription for SNMP trap notification, generated SNMP traps are forwarded to the hosts you specify until you change, suspend, or delete the subscription.
Note Adding a subscription is a multistep process. Your changes are not saved until you click the Finish button on the final page.
Before You Begin
You must create a notification group before you can create an SNMP trap notification subscription. Refer to Configuring Notification Groups.
Step 1 From the DFM home page, select Notification Services > SNMP Trap Notification. The SNMP Trap Notification Subscriptions page appears.
Step 2 Click the Add button.
Step 3 Complete the Trap Subscription Save: Add window:
a. Enter a subscription name.
b. Select a notification group.
c. If you are upgrading DFM and want to use the trap recipients from an earlier configuration, activate the Recipients from Upgrade check box. (This choice is only available for systems that have been upgraded from earlier versions of DFM.)
d. Click Next.
Step 4 Enter one or more hosts as recipients for traps:
a. For each host, enter:
•An IP address or DNS name for the hostname.
•A port number on which the host can receive traps. If the port number is unspecified (empty), the port defaults to 162. (You can verify this in Step 5.)
•(Optional) A comment.
b. Click Next.
Step 5 Review the information that you entered and click Finish. The SNMP Trap Notifications page is displayed, showing the new subscription.
Note No information is saved until you complete Step 5.
Editing an SNMP Trap Notification Subscription
You can edit an SNMP trap notification subscription regardless of its status (Running or Suspended).
After you edit an SNMP trap notification subscription, if the subscription status is Running, traps are forwarded as specified until you edit, suspend, or delete the subscription. Editing a suspended subscription automatically resumes it.
Note Editing a subscription is a multistep process. Your changes are not saved until you click the Finish button on the final page.
Step 1 From the DFM home page, select Notification Services > SNMP Trap Notification. The SNMP Trap Notification Subscriptions page appears.
Step 2 Select the subscription you want to edit by clicking the radio button beside it.
Step 3 Click the Edit button.
No information is saved until you complete Step 5.
Step 4 Edit the Trap Subscription Save: Edit window:
a. Change the subscription name.
b. Select another notification group.
c. Click Next.
Step 5 Add or delete a recipient host or change the port number for a host:
a. To add one or more recipients, for each host, enter:
•An IP address or DNS name for the hostname.
•A port number on which the host can receive traps. If the port number is unspecified (empty), the port defaults to 162. (You can verify this in Step 6.)
•(Optional) A comment.
b. To delete a recipient, delete the hostname, port number, and comment, if any.
c. Click the Next button.
Step 6 Review the information that you entered and click the Finish button. The SNMP Trap Notifications page is displayed.
Suspending an SNMP Trap Notification Subscription
After you suspend an SNMP trap notification subscription, DFM stops using the subscription to select and forward traps. The subscription status changes to Suspended.
Step 1 From the DFM home page, select Notification Services > SNMP Trap Notification. The SNMP Trap Notification Subscriptions page appears.
Step 2 Select the subscription you want to suspend by clicking the radio button beside it.
Step 3 Click the Suspend button.
Step 4 Click OK in the confirmation dialog box. The SNMP Trap Notification Subscriptions page is displayed. The subscription status is Suspended.
Resuming an SNMP Trap Notification Subscription
You can resume an SNMP trap notification subscription only when the subscription status is Suspended. After you resume a subscription, DFM starts using it to identify alerts for which to forward traps. The subscription status changes to Running.
Step 1 From the DFM home page, select Notification Services > SNMP Trap Notification. The SNMP Trap Notification Subscriptions page appears.
Step 2 Select the subscription you want to resume by clicking the radio button beside it.
Step 3 Click the Resume button.
Step 4 Click OK in the confirmation dialog box. The SNMP Trap Notification Subscriptions page is displayed. The subscription status is Running.
Deleting an SNMP Trap Notification Subscription
You can delete an SNMP trap notification subscription regardless of the subscription status. Deleting a subscription removes it permanently from DFM.
Note You can also suspend a subscription. Suspending a subscription causes the subscription to not be used until a user resumes it.
Step 1 From the DFM home page, select Notification Services > SNMP Trap Notification.
Step 2 Select the subscription you want to delete by clicking the radio button beside it.
Step 3 Click the Delete button.
Step 4 Click OK in the confirmation dialog box. The SNMP Trap Subscriptions page appears. The subscription is no longer displayed.
Managing E-Mail Notifications
The E-Mail Notifications page displays the following information:
•Subscription—The name of the user-defined request for notification.
•Status—The subscription status; can be either of the following:
–Running—DFM is using the subscription while monitoring alerts to determine when to send a notification.
–Suspended—DFM will not use the subscription unless you resume it.
•Notification Group—The name of notification group that is applied to the subscription.
You are completely in control of subscriptions. DFM does not delete subscriptions under any circumstances. From the E-Mail Notifications page, you can perform the tasks listed in Table 5-3.
Adding an E-Mail Notification Subscription
After you add a subscription for e-mail notification, DFM sends e-mail to the users you specify whenever an alert occurs that matches the subscription.
Note Adding a subscription is a multistep process. Your changes are not saved until you click the Finish button on the final page.
Before You Begin
You must create a notification group before you can create an E-Mail Notification subscription. Refer to Configuring Notification Groups.
Step 1 From the DFM home page, select Notification Services > E-Mail Notification. The E-Mail Notification Subscriptions page appears.
Step 2 Click the Add button.
Step 3 Complete the E-Mail Subscription Save: Add window:
a. Enter a subscription name.
b. Select a notification group.
c. If you are upgrading DFM and want to use the e-mail recipients from an earlier configuration, activate the Recipients from Upgrade check box. (This choice is only available for systems that have been upgraded from earlier versions of DFM.)
d. Click Next.
Step 4 Enter the e-mail information:
a. Provide the following information:
•SMTP Server—The name of the default Simple Mail Transfer Protocol (SMTP) server may already be displayed. The server is specified using Configuration > Other Configuration > SMTP Default Server. You may also enter a fully qualified DNS name or IP address for an SMTP server.
Note To select from any nondefault SMTP servers in use by existing subscriptions, click the SMTP Servers button.
•Sender Address—Enter the e-mail address that notifications should be sent from. If the sender's e-mail service is hosted on the SMTP server specified, you need enter only the username. You do not need to enter the domain name.
•Recipient Address(es)—Enter one or more e-mail addresses that notifications should be sent to, separating multiple addresses with either a comma or a semicolon. If a recipient's e-mail service is hosted on the SMTP server specified, you need to enter only the username. You do not need to enter the domain name.
•By default, e-mail notification supplies a fully detailed e-mail message. To omit the message body and send only a subject line, select the Headers Only check box.
b. Click the Next button located at the bottom of the page.
Step 5 Review the information that you entered and click the Finish button. The E-Mail Notification Subscriptions page is displayed, showing the new subscription.
Note No information is saved until you complete Step 5.
Note For instructions on how to configure a default SMTP server, see Configuring a Default SMTP Server.
Editing an E-Mail Notification Subscription
You can edit an e-mail notification subscription regardless of its status (Running or Suspended).
After you edit an e-mail notification subscription, if the subscription status is Running, e-mail is forwarded as specified until you change, suspend, or delete the subscription. Editing a suspended subscription automatically resumes it.
Note Editing a subscription is a multistep process. Your changes are not saved until you click the Finish button on the final page.
Step 1 From the DFM home page, select Notification Services > E-Mail Notification. The E-Mail Notification Subscriptions page appears.
Step 2 Select the subscription you want to edit by clicking the radio button beside it.
Step 3 Click the Edit button.
Step 4 Edit the E-Mail Subscription Save: Edit window:
a. Change the subscription name.
b. Select another notification group.
c. Click Next.
Step 5 Change the SMTP server, the sender, the recipients, or the amount of detail sent in e-mail as needed:
•SMTP Server—The name of the default Simple Mail Transfer Protocol (SMTP) server may already be displayed. The server is specified using Configuration > Other Configuration > SMTP Default Server. You may also enter a fully qualified DNS name or IP address for an SMTP server.
Note To select from any nondefault SMTP servers in use by existing subscriptions, click the SMTP Servers button.
•Sender Address—Enter the e-mail address that notifications should be sent from. If the sender's e-mail service is hosted on the SMTP server specified, you need to enter only the username. You do not need to enter the domain name.
•Recipient Address(es)—Enter one or more e-mail addresses that notifications should be sent to. When entering multiple addresses, include a comma or a semicolon between addresses. If a recipient's e-mail service is hosted on the SMTP server specified, you need to enter only the username. You do not need to enter the domain name.
•By default, e-mail notification supplies a fully detailed e-mail message. If, however, the Headers Only check box is selected, the message body is omitted from the e-mail.
Step 6 Click the Next button located at the bottom of the page.
Step 7 Review the information that you entered and click the Finish button. The E-Mail Notification Subscriptions page is displayed.
Note For instructions on how to configure a default SMTP server, see Configuring a Default SMTP Server.
Suspending an E-Mail Notification Subscription
After you suspend an e-mail notification subscription, DFM stops using the subscription to send e-mail notification. The subscription status changes to Suspended.
Step 1 From the DFM home page, select Notification Services > E-Mail Notification. The E-Mail Notification Subscriptions page appears.
Step 2 Select the subscription you want to suspend by clicking the radio button beside it.
Step 3 Click the Suspend button.
Step 4 Click OK in the confirmation dialog box. The E-Mail Notification Subscriptions page is displayed. The subscription status is Suspended.
Resuming an E-Mail Notification Subscription
After you resume an e-mail notification subscription, DFM starts using the subscription to determine when e-mail notification should be sent in response to an alert. The subscription status changes to Running.
Step 1 From the DFM home page, select Notification Services > E-Mail Notification. The E-Mail Notification Subscriptions page appears.
Step 2 Select the subscription you want to resume by clicking the radio button beside it.
Step 3 Click the Resume button.
Step 4 Click OK in the confirmation dialog box. The E-Mail Notification Subscriptions page is displayed. The subscription status is Running.
Deleting an E-Mail Notification Subscription
You can delete an e-mail notification subscription regardless of the subscription status. Deleting a subscription removes it permanently from DFM.
Note You can also suspend a subscription. Doing so causes the subscription to not be used until a user resumes it.
Step 1 From the DFM home page, select Notification Services > E-Mail Notification.
Step 2 Select the subscription you want to delete by clicking the radio button beside it.
Step 3 Click the Delete button.
Step 4 Click OK in the confirmation dialog box. The E-Mail Subscriptions page appears. The subscription is no longer displayed.
Managing Syslog Notifications
The Syslog Notifications page displays the following information:
•Subscription—The name of the user-defined request for notification.
•Notification Group—The name of notification group that is applied to the subscription.
•Status—The subscription status; can be either of the following:
–Running—DFM is using the subscription while monitoring alerts to determine when to send a notification.
–Suspended—DFM will not use the subscription unless you resume it.
You are completely in control of subscriptions. DFM does not change or delete subscriptions under any circumstances. From the syslog Notifications page, you can perform the tasks listed in Table 5-4.
Adding a Syslog Notification Subscription
After you add a subscription for syslog notification, DFM sends a syslog message to the specified remote hosts whenever an alert or event occurs that matches the subscription.
Note Adding a subscription is a multistep process. Your changes are not saved until you click the Finish button on the final page.
Before You Begin
•You must create a notification group before you can create a Syslog Notification subscription. Refer to Configuring Notification Groups.
•A remote machine's syslog daemon must be configured to listen on a specified port, and you must enter this information in Step 3 of the following procedure. DFM uses the default port 514.
Step 1 From the DFM home page, select Notification Services > Syslog Notification. The Syslog Notification Subscriptions page appears.
Step 2 Click the Add button.
a. Enter a subscription name.
b. Select a notification group.
c. Select a facility from the drop-down list (the default is Local Use 0). The Facility field and the event/alert severity are used for the PRI portion of the syslog message, as follows:
[Facility*8][Severity]
Event/alert severity values are as follows:
•Critical = 2
•Warning = 4
•Information = 6
d. (Optional) Enter location information (up to 29 characters). This information will be populated in the syslog message.
e. Click Next.
Step 3 Enter one or more hosts as recipients for syslog notifications.
a. For each host, enter:
•An IP address or DNS name for the hostname.
•A port number on which the syslog daemon is listening. If the port number is unspecified (empty), the port defaults to 514. (You can verify this in Step 5.)
•(Optional) A comment.
b. Click Next.
Step 4 Enter the name of the subscription in the Save As field and click the Next button.
Step 5 Review the information that you entered and click the Finish button. The Syslog Notification Subscriptions page is displayed, showing the new subscription.
Note No information is saved until you complete Step 5.
Editing a Syslog Notification Subscription
You can edit a syslog notification subscription regardless of its status (Running or Suspended).
After you edit a syslog notification subscription, if the subscription status is Running, syslog messages are forwarded as specified until you change, suspend, or delete the subscription. Editing a suspended subscription automatically resumes it.
Note Editing a subscription is a multistep process. Your changes are not saved until you click the Finish button on the final page.
Step 1 From the DFM home page, select Notification Services > Syslog Notification. The Syslog Notification Subscriptions page appears.
Step 2 Select the subscription you want to edit by clicking the radio button beside it.
Step 3 Click the Edit button.
Step 4 Edit the Syslog Subscription Save: Edit window:
a. Change the subscription name.
b. Select a different notification group.
c. Select a Facility from the drop-down list (the default is Local Use 0). The Facility field and the event/alert severity is used for the PRI portion of the syslog message, as follows:
[Facility*8][Severity]
Event/alert severity values are as follows:
•Critical = 2
•Warning = 4
•Informational = 6
d. (Optional) Enter location information (up to 29 characters). This information will be populated in the syslog message.
e. Click Next.
Step 5 Add or delete a recipient host or change the port number for a host:
a. To add one or more recipients, for each host, enter:
•An IP address or DNS name for the hostname.
•A port number on which the syslog daemon is listening. If the port number is unspecified (empty), the port defaults to 514. (You can verify this in Step 7.)
•(Optional) A comment.
b. To delete a recipient, delete the hostname, port number, and comment, if any.
c. Click the Next button.
Step 6 Click the Next button located at the bottom of the page.
Step 7 Review the information that you entered and click the Finish button. The Syslog Notification Subscriptions page is displayed.
Suspending a Syslog Notification Subscription
After you suspend a syslog notification subscription, DFM stops using the subscription to send syslog notifications. The subscription status changes to Suspended.
Step 1 From the DFM home page, select Notification Services > Syslog Notification. The Syslog Notification Subscriptions page appears.
Step 2 Select the subscription you want to suspend by clicking the radio button beside it.
Step 3 Click the Suspend button.
Step 4 Click OK in the confirmation dialog box. The Syslog Notification Subscriptions page is displayed. The subscription status is Suspended.
Resuming a Syslog Notification Subscription
After you resume a syslog notification subscription, DFM starts using the subscription to determine when syslog notifications should be sent in response to an alert or event. The subscription status changes to Running.
Step 1 From the DFM home page, select Notification Services > Syslog Notification. The Syslog Notification Subscriptions page appears.
Step 2 Select the subscription you want to resume by clicking the radio button beside it.
Step 3 Click the Resume button.
Step 4 Click OK in the confirmation dialog box. The Syslog Notification Subscriptions page is displayed. The subscription status is Running.
Deleting a Syslog Notification Subscription
You can delete a syslog notification subscription regardless of the subscription status. Deleting a subscription removes it permanently from DFM.
Note You can also suspend a subscription. Doing so causes the subscription to not be used until a user resumes it.
Step 1 From the DFM home page, select Notification Services > Syslog Notification.
Step 2 Select the subscription you want to delete by clicking the radio button beside it.
Step 3 Click the Delete button.
Step 4 Click OK in the confirmation dialog box. The Syslog Subscriptions page appears. The subscription is no longer displayed.
