Cisco Prime Unified Operations Manager 9.0 User Guide
Using Notifications
Downloads: This chapterpdf (PDF - 402.0KB) The complete bookPDF (PDF - 18.07MB) | Feedback

Using Notifications

Table Of Contents

Using Notifications

Understanding Notifications

What Causes Prime UOM to Send Notifications?

Notification Groups

Notification Criteria

Types of Notifications

SNMP Trap Notifications

E-Mail Notifications

Syslog Notifications

Configuring Systems and Users for Notification

Limiting Notifications to Specific Events

Configuring Event Sets

Adding and Editing an Event Set

Viewing an Event Set

Deleting an Event Set

Configuring Notifications

Adding and Editing Device Notification Groups

Adding and Editing Service Quality Notification Groups

Adding and Editing Phone Notification Groups

Cloning a Notification Group

Viewing Notification Group Configuration Details

Deleting Notification Groups

Suspending a Notification

Resuming a Notification

Mapping Device Types to Values that Display in Events Sent by Devices

Notifying Users About EPM Log Updates


Using Notifications


Cisco Prime Unified Operations Manager (Prime UOM) displays event information in response to events that occur in the IP Telephony environment and the IP fabric.

You can view events on Prime UOM dashboards, such as the Device Events Summary. In addition, you can configure notifications to forward information about events to SNMP trap daemons on other hosts, syslog daemons, and users.

The following topics explain notifications concepts and provide procedures for managing notifications:

Understanding Notifications

Configuring Event Sets

Configuring Notifications

Understanding Notifications

This topic describes how Prime UOM determines when to send a notification and introduces the concepts that you need to be familiar with to configure notifications.


Note Notifications monitor events on device roles, not on device components. For a list of supported events and the device roles on which they can occur, see "Events Processed."


This section contains:

What Causes Prime UOM to Send Notifications?

Notification Groups

Notification Criteria

Types of Notifications

Configuring Systems and Users for Notification

Limiting Notifications to Specific Events

What Causes Prime UOM to Send Notifications?

For each event, Prime UOM compares the event, devices, severity, and state against the configured notification groups and sends a notification when there is a match. Matches can be determined by user-configured event sets and notification criteria. (The procedure for configuring notification criteria is described in Configuring Notifications.)

Prime UOM assigns one severity to each event and changes the state of an event over time, responding to user input and changes on the device. Table 15-1 lists values for severity and explains how the state of an event changes over time.


Note You can change event names to names that are more meaningful to you. You can also change the event severity sent in notifications from the Prime UOM default value to a user-defined value. See Customizing Events.


Table 15-1 Event Severity and Status

Prime UOM categorizes events by severity and status...
Severity

Critical

Warning

Informational

Status

Active—The event is live.

Acknowledged—A user has manually acknowledged the event. A user can acknowledge only active events.

Cleared—The event is no longer active.

Events that have been cleared either expire or, if associated with a suspended device, remain in Prime UOM until a user resumes or deletes the device.


Notification Groups

A notification group is a user-defined set of rules for generating and sending notifications. A notification group includes:

Notification criterion—A named set of reasons to generate a notification.

Notification type—The type of notification to send: SNMP trap, e-mail, or syslog.

Notification recipients—Hostnames and ports for systems that listen for SNMP traps, syslog messages, or e-mail addresses.

Daily subscription activity period—The hours during which Prime UOM should use this subscription while monitoring the events for which to send notifications.

Notification Criteria

Notification criteria define what you want to monitor for the purpose of sending notifications. A notification criterion is a user-defined, named set of devices or phones, and events of a particular severity and status. You must specify notification criteria to configure a notification group.

Prime UOM supports three types of notification criteria:

Device-Based Criteria—Includes the following:

Devices—The devices, device groups, or clusters that you want to monitor.

Event sets—(Optional). One or more groups of events that you want to monitor. See Limiting Notifications to Specific Events.

Event severity and status—One or more event severity levels and status.

You can also customize the names and severity of the device-based events displayed by Notifications.

Service Quality-Based Criteria—Includes the following:

Phones, endpoints, or probes—Phones, call endpoints, or probes that you want to monitor.

Event severity and status—One or more event severity levels and status.

You cannot customize the names and severity of the Service Quality-based events displayed by Notifications.

Service Quality-based criteria are useful when you have purchased a license for Service Monitor and configured Prime UOM as a trap receiver on Service Monitor. Service Quality-based criteria do not include events sets.

Phone-Based Criteria—Includes the following:

Phones—Phones you want to monitor.

Event severity and status—One or more event severity levels and status.

Types of Notifications

Prime UOM provides three types of notification: SNMP trap, e-mail, and syslog. When you configure a notification group, you specify one or more types of notification to send and you must also specify recipients for each type of notification.

This section contains:

SNMP Trap Notifications

E-Mail Notifications

Syslog Notifications

SNMP Trap Notifications

Prime UOM generates traps with information about the events that caused it. CISCO-EPM-NOTIFICATION-MIB defines the trap message format. For more information, see "Notification MIB."

Using SNMP trap notification is different from forwarding raw traps to another server before they have been processed by Prime UOM. For information about the raw traps that Prime UOM can forward, see "Processed SNMP Traps."

E-Mail Notifications

Prime UOM generates e-mail messages containing information about the events that caused it. CISCO-EPM-NOTIFICATION-MIB defines the message, which is included in the e-mail in text format. When you create an e-mail subscription, you can choose whether to include the subject line only or the complete e-mail message.

Syslog Notifications

Prime UOM generates syslog messages that can be forwarded to syslog daemons on remote systems.

Syslog messages have a limitation of 1,024 characters (including the heading). Any syslog-based event details may not contain the full information due to this syslog limitation. If the syslog message exceeds this limitation, it is truncated to 1,024 characters by the syslog sender.

Configuring Systems and Users for Notification

When you configure a notification group, you must specify recipients for each type of notification:

SNMP trap—Send SNMP traps to a port number on which the host can receive traps. Prime UOM defaults to sending SNMP traps to the port 162. However, you can specify a different port.

E-Mail—Send e-mail to one or more addresses.

Syslog—Send syslog messages to a remote system on which the syslog daemon is configured to listen on a specified port. Prime UOM defaults to sending syslog messages to port 514. However, you can specify a different port.

You can send notifications to multiple destinations. For traps and syslogs, you can add upto 20 destinations. For emails, the number of destinations you can enter depends on the length of the email ID string, and the your mail server configuration.

Limiting Notifications to Specific Events

In some cases, you might want to send notifications for only a subset of the events that Prime UOM monitors. You can set the events that are of interest to you when you define the notification criterion:

Specify an event set for a device-based notification criterion. You can create as many events sets as you would like.

Select the events that you want Prime UOM to monitor for Service Quality-based notification criteria. There are few Service Quality-based events and you can select among them when you add or edit Service Quality-based notification criteria.

Configuring Event Sets

Event sets enable you to group the events the you want Prime UOM to monitor for the purpose of sending notifications.

You cannot use event sets if you have configured alarms concurrently. If you want to limit information to the selections in the event set, deselect the alarm functionality.

This section contains:

Adding and Editing an Event Set

Viewing an Event Set

Deleting an Event Set

Events Processed

To configure event sets, select Notifications > Event Sets.

The Event Set page appears. This page displays the following information:

GUI Element
Description/Action

Check Box column

Select one check box to edit, delete, or view an event set.

Name column

Event set name.

Description column

Event set description.

Add button

Click to add an event set. See Adding and Editing an Event Set.

Edit button

Click to edit an event set. See Adding and Editing an Event Set.

View button

Click to view an event set. See Viewing an Event Set.

Delete button

Click to delete an event set.


You can use event sets to:

Limit the number of events that Prime UOM notification monitors. When you do not use event sets, Prime UOM notification monitors all events to determine whether to send a notification.

Aggregate the notifications that you want to send to different destinations. For example, you can create separate event sets for each of the following purposes:

Limit the amount of e-mail notification sent to specific individuals or departments to only those for certain events.

Write all occurrences of particular events to syslog.

Send SNMP traps when certain events occur.

When you create device-based notification criteria, you must include an event set as one of the criteria. The default event set, All_Events, includes all events.

For additional information, see the following topic:

Events Processed

Adding and Editing an Event Set

To add and edit an Event set:


Step 1 Select Notifications > Event Sets.

The Event Set page appears, displaying the information in the following table.

GUI Element
Description/Action

Name column

Event set name.

Description column

Event set description.


Step 2 Do one of the following:

Click Add

Select a check box for an event set and click Edit.

Depending on your selection, the Add Event Set or Edit Event Set page appears.

Step 3 Edit the information on the page, described in the following table.

GUI Element
Description/Action

Event Set Name field

Event set name—Enter or edit the event set name.

Event Set Description field

Event set description—Optional. Enter a description.

Events table

Number column

Numbers events serially from one.

Check box column

Select to add an event to the event set.

Deselect to remove the event from the event set.

Event column

Event description.


Step 4 Click OK to save your changes.


Viewing an Event Set

To view an Event set:


Step 1 Select Notifications > Event Sets.

The Event Set page appears, displaying the information in the following table.

GUI Element
Description/Action

Name column

Event set name.

Description column

Event set description.


Step 2 Select the check box for an event set and click View.

The Event Set Summary dialog box appears, displaying the following information:

Name—User-supplied name.

Description—User-supplied description.

Events—List of events in the event set.


Deleting an Event Set

To delete an event set:


Step 1 Select Notifications > Event Sets.

The Event Set page appears, displaying the information in the following table.

GUI Element
Description

Name column

Event set name.

Description column

Event set description.


Step 2 Select the check box next to each event set that you want to delete.

Step 3 Click Delete.

A confirmation dialog box appears.

Step 4 Click Yes to confirm.


For additional information, see the following topic:

Events Processed

Configuring Notifications

The Notification Groups page is where notification management activities take place. To open the Notification Groups page, select Administration > Notifications > Notification Criteria.

The notification criteria feature has the following role rules:

The System Identity User (created during installation) can see all the notification criteria created and can edit them.

The Network Administrator can only see the notification criteria which he or she created for the customers they are authorized to create and edit.

The Network Operator does not have any access.

You can use the copy function in Role Management Setup to view what tasks are associated with each role. Select a role and click on copy to view the tasks this role is authorized to do.

These topics explain the activities you can perform from the Notification Groups page:

Adding and Editing Device Notification Groups

Adding and Editing Service Quality Notification Groups

Adding and Editing Phone Notification Groups

Cloning a Notification Group

Viewing Notification Group Configuration Details

Deleting Notification Groups

Suspending a Notification

Resuming a Notification

Mapping Device Types to Values that Display in Events Sent by Devices

Notifying Users About EPM Log Updates

Figure 15-1 shows an example of the Notification Groups page.

Figure 15-1 Notification Groups page

Table 15-2 describes the fields in the Notification Groups page.

Table 15-2 Fields on the Notification Groups Page 

GUI Element
Description/Action

Check box column

Select one check box to edit or delete a notification.

Name column

Notification group name.

Devices/Device Groups

Devices, device groups, and clusters that are configured for the notification.

Events

Event sets that cause the notification to be sent.

Destinations

Type of notification that will be sent—e-mail, SNMP trap, or syslog message—and the hostnames and e-mail recipients it will be sent to.

Information shown in the destination box is limited. If the information exceeds the limit, an ellipses (...) is displayed. The complete information will be shown in the tooltip.

Operating Interval

Hours of the day during which the subscription is active.

Status

Notification group status. It can be any of the following:

Active—Prime UOM is using the notification group while monitoring events to determine when to send a notification.

Suspended—The notification has been manually suspended. Prime UOM will not use the notification group unless you resume it.

Inactive—During a period of the day when the notification group is not scheduled to be active.

Filter drop-down menu/Filter button

Enables you to filter what is displayed on the Notifications Group page.

Add > Device-Based Criterion button

Click to add a device notification group. See Adding and Editing Device Notification Groups.

Add > Service Quality-Based Criterion button

Click to add a Service Quality notification group. See Adding and Editing Service Quality Notification Groups.

A Service Quality-based criterion is useful only if you have purchased a license for Service Monitor.

Clone button

Starts the process of adding a notification group using a current notification group as a template. See Cloning a Notification Group.

Cloning a phone-based notification group is not supported due to the maximum phone limit of 10,000.

Edit button

Click to edit a notification criterion. See Adding and Editing Device Notification Groups and Adding and Editing Service Quality Notification Groups.

View button

Displays the Notification Group Summary page, where the configuration information for a notification group is displayed.

Suspend button

Temporarily stops sending notifications to a host.

Temporarily stops sending notifications about a device group. That is, it overrides scheduled notification's run time.

See Suspending a Notification.

Resume button

Start sending notifications to a host again.

Start sending notifications about a device group using a previously suspended notification.

See Resuming a Notification.

Delete button

Click to delete a notification group. See Deleting Notification Groups.


The following recommended guidelines provide the maximum number of recommended notification groups that you can create. These numbers include Suspended notification groups.

For notification groups with over 400 devices the maximum number is:

Five phone-based notification groups containing up to 2,000 phones.

One device-based notification group containing up to 2,000 devices.

One Service Quality notification group.

Adding and Editing Device Notification Groups

This section describes the procedure for adding or editing a device notification group.


Note You can use existing notification groups as templates for creating new notification groups. For procedures, see Cloning a Notification Group.


To add and edit device notification groups:


Step 1 Select Administration > Notifications > Notification Criteria.

Step 2 Do one of the following:

To add a new criterion, click Add > Device-Based Criterion.

To edit an existing criterion, select the check box for a device notification group and click Edit.

Depending on your selection, the Add Device-Based Criterion page or Edit Device-Based Criterion page appears.

To add or edit clusters for Notification, select clusters (which are available under the Cisco Unified Communications Manager or Cluster group). The clusters have a VE- prefix in their names.

To add or edit phones (which are configured for the Diagnostics test), select phones under System Defined Groups\Phones with tests configured.

Step 3 Edit the information on the page, described in the following table.

Table 15-3 Device-Based Criterion 

GUI Element
Description/Action

Device selector pane

Expand device group folders and select check boxes for one or more devices, device groups, or clusters.

If you select a device group, the notification criterion will stay up-to-date when devices are added or deleted from Prime UOM only if you also select the Include updates to group membership check box.

Criterion Name field

Enter a name for the notification criterion.

Customer Identification field

Enter any desired identifying information. If you leave this field empty, it remains blank in e-mail and syslog notifications.

In SNMP trap notifications, it is displayed as follows:

Customer ID: -

Customer Revision field

Enter any desired identifying information. If you leave this field blank, it remains blank in e-mail and syslog notifications.

In SNMP trap notifications, it is displayed as follows:

Customer Revision: *

Event Set Type list box

Select one.

Event Severity check boxes

Select none, one, or more of the following:

Critical.

Warning.

Informational.

Event Status check boxes

Select none, one, or more of the following:

Active.

Acknowledged.

Cleared.

User Cleared

Include updates to group membership check box

When selected, if devices are added to or deleted from Prime UOM, the devices are also added to or deleted from the notification criterion. This happens when the notification criterion includes a device group that the devices belong to.

Deselect to maintain a static list of devices for any device groups included in the notifications criterion.


Step 4 Click Next.

The Destination: Edit Device-Based Criterion page appears.

Step 5 Edit the information on this page as described in the following table.

Table 15-4 Edit Device Criteria 

GUI Element
Description/Action

Always Active check box

Schedules the notification group to always be active.

Active From: To: fields

Select the hours of the day during which you want this notification group to be active:

From: HH:MM—Select hour and minute that the subscription becomes active.

To: HH:MM—Select the last hour and minute during which the subscription is active.

By default, the values are from 00:00 to 00:00 and the subscription is active for 24 hours.

Use this field, for example, to send e-mail notifications during one shift and not during another.

Include Link to Notification Details check box

Select to include URLs in the notification from which users can directly open the relevant page in Prime UOM for more information.

Deselect to omit URLs from notifications.

Subscription Type radio buttons

Select one at a time to enter data for each subscription type that you want to include in this subscription:

Trap—Enter data in the Trap Subscription Type fields.

E-Mail—Enter data in the E-Mail Subscription Type fields.

Syslog—Enter data in the Syslog Subscription Type fields.

Prime UOM does not save the data you enter until you click Finish on the Subscription: Summary page. To go to the Subscription: Summary page, click Next.

Trap Subscription Type fields

IP Address/Fully Qualified Domain Name editable column

Enter an IP address or Fully Qualified Domain Name (FQDN) of the host.

Port editable column

Enter a port number on which the host can receive traps. A valid port value is a number from 0 to 65,535. You can enter the default port number value 162.

Comments editable column

(Optional) Enter a comment.

E-Mail Subscription Type fields

SMTP Server field

Enter a fully qualified DNS name or IP address for a Simple Mail Transfer Protocol (SMTP) server. (The name of the default SMTP server might already be displayed.)

To select from any nondefault SMTP servers in use by existing subscriptions, click the SMTP Servers button.

For instructions on how to configure a default SMTP server, see the Setting System-Wide Parameters Using System Preferences.

Sender Address field

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) field

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.

Subject Only check box

Select to include only the subject in the e-mail message.

Deselect to send a fully detailed e-mail message (default).

Syslog Subscription Type fields

Facility list

Select a facility from the list (the default is Local Use 0). The Facility field and the event severity are used for the PRI portion of the syslog message, as follows:

[Facility*8][Severity]

Event severity values are as follows:

Critical = 2

Warning = 4

Informational = 6

Location field

(Optional) Enter location information (up to 29 characters). This information will be populated in the syslog message.

IP Address/Fully Qualified Domain Name editable column

Enter an IP address or Fully Qualified Domain Name (FQDN) of the host.

Port editable column

Enter a port number on which the syslog daemon is listening. A valid port value is a number from 0 to 65,535. You can enter the default port number value 514.

The syslog daemon on the remote system (hostname) must be configured to listen on a specified port.

Comments editable column

(Optional) A comment.


Step 6 Click Next.

The Notification Group Summary page appears, displaying all information entered on the previous page.

Step 7 Click Finish.

The notification information is saved.


Adding and Editing Service Quality Notification Groups

This section describes the procedure for adding or editing a service quality notification group.


Note You can use existing notification groups as templates for creating new notification groups. For procedures, see Cloning a Notification Group.


To add and edit Service Quality Notification groups:


Step 1 Select Notifications > Notification Criteria.

Step 2 Do one of the following:

To add a new group, click Add > Service Quality-Based Criterion.

To edit an existing group, select the check box next to a service quality notification group and click Edit.

Depending on your selection, the Add Service Quality-Based Criterion page or Edit Service Quality-Based Criterion page appears.

Step 3 Edit the information on the page, described in the following table.

Table 15-5 Service Quality-Based Criterion 

GUI Element
Description/Action

Notification Criterion field

Enter a name for the notification criterion.

Customer Identification field

Enter any desired identifying information. If you leave this field empty, it remains blank in e-mail and syslog notifications.

In SNMP trap notifications, it is displayed as follows:

Customer ID: -

Customer Revision field

Enter any desired identifying information. If you leave this field blank, it remains blank in e-mail and syslog notifications.

In SNMP trap notifications, it is displayed as follows:

Customer Revision: *

Destination fields

To generate notifications for events on call destinations, do the following:

1. Select an operator (Is Exactly, Contains, Begins With, Any).

2. Enter an appropriate value: Phone extension or IP address for an endpoint, such as a voice gateway or a phone.

Source fields

To generate notifications for events on call sources, do the following:

1. Select an operator (Is Exactly, Contains, Begins With, Any).

2. Enter an appropriate value: Phone extension or IP address for a voice gateway or a phone.

Sensor MAC fields

To generate notifications for events on particular Cisco 1040 Sensors, do the following:

1. Select an operator (Is Exactly, Contains, Begins With, Any).

2. Enter the MAC address for a Cisco 1040 Sensor.

Cluster ID fields

To generate notifications for events from a particular cluster, do the following:

1. Select an operator (Is Exactly, Contains, Begins With, Any).

2. Enter the cluster ID.

Listener or Speaker Phone Model lists

To generate notifications for events on particular phone models, enter a comma-separated list of Cisco Unified IP Phone models or select them from a list:

1. Click the icon to open a selector.

2. Select a phone model from the list.

To select more than one phone model, hold down Ctrl while selecting.

3. Click OK.

Event Severity check boxes

Select any:

Critical.

Informational.

Warning.

Event Description check boxes

Select any:

Service Quality Issue.

Sensor Down.

For more information about these events, see Events Processed.

Cause check boxes

Select any:

Jitter.

Packet Loss.


Step 4 Click Next.

The Destination: Edit Qov Criteria page appears.

Step 5 Edit the information on this page as described in the following table.

Table 15-6 Edit Quality-Based Criteria 

GUI Element
Description/Action

Always Active check box

Schedules the notification group to always be active.

Active From: To: fields

Select the hours of the day during which you want this subscription to be active:

From: HH:MM—Select hour and minute that the subscription becomes active.

To: HH:MM—Select the last hour and minute during which the subscription is active.

By default, the values are from 00:00 to 00:00 and the subscription is active for 24 hours.

Use this field, for example, to send e-mail notifications during one shift and not during another.

Include Link to Notification Details check box

Select to include URLs in the notification from which users can directly open the relevant page in Prime UOM for more information.

Deselect to omit URLs from notifications.

Subscription Type radio buttons

Select one at a time to enter data for each subscription type that you want to include in this subscription:

Trap—Enter data in the Trap Subscription Type fields.

E-Mail—Enter data in the E-Mail Subscription Type fields.

Syslog—Enter data in the Syslog Subscription Type fields.

Prime UOM does not save the data you enter until you click Finish on the Subscription: Summary page. To go to the Subscription: Summary page, click Next.

Trap Subscription Type fields

IP Address/Fully Qualified Domain Name editable column

Enter an IP address or Fully Qualified Domain Name (FQDN) of the host.

Port editable column

Enter a port number on which the host can receive traps. If the port number is left unspecified (blank), the port defaults to 162.

Comments editable column

(Optional) Enter a comment.

E-Mail Subscription Type fields

SMTP Server field

Enter a fully qualified DNS name or IP address for a Simple Mail Transfer Protocol (SMTP) server. (The name of the default SMTP server might already be displayed.)

To select from any nondefault SMTP servers in use by existing subscriptions, click the SMTP Servers button.

For instructions on how to configure a default SMTP server, see the Setting System-Wide Parameters Using System Preferences.

Sender Address field

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) field

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.

Subject Only check box

Select to include only the subject in the e-mail message.

Deselect to send a fully detailed e-mail message (default).

   
Syslog Subscription Type fields

Facility list

Select a facility from the list (the default is Local Use 0). The Facility field and the event severity are used for the PRI portion of the syslog message, as follows:

[Facility*8][Severity]

Event severity values are as follows:

Critical = 2

Warning = 4

Informational = 6

Location field

(Optional) Enter location information (up to 29 characters). This information will be populated in the syslog message.

IP Address/Fully Qualified Domain Name editable column

Enter an IP address or Fully Qualified Domain Name (FQDN) of the host.

Port editable column

Enter a port number on which the syslog daemon is listening. A valid port value is a number from 0 to 65,535. You can enter the default port number value 514.

The syslog daemon on the remote system (hostname) must be configured to listen on a specified port.

Comments editable column

(Optional) A comment.


Step 6 Click Next.

The Notification Group Summary page appears, displaying all information entered on the previous page.

Step 7 Click Finish.

The notification information is saved.


Adding and Editing Phone Notification Groups

This section describes the procedure for adding or editing a phone notification group.


Note The maximum number of phone notification groups allowed is five, and each notification group can contain a maximum of 2,000 phones. Cloning a phone notification group is not supported due to the maximum phone limit of 10,000.


To add and edit Phone Notification groups:


Step 1 Select Administration > Notifications > Notification Criteria.

When you select Phone-Based Notification Criteria > Phone Report, each phone displays two phone entries (which contain two Directory Numbers/Extension Numbers (DNs). To leverage a phone count of 10,000, select one of the two entries.

Step 2 Do one of the following:

To add a new criterion, click Add > Phone-Based Criterion.

To edit an existing criterion, select the check box for a phone notification group and click Edit.

Depending on your selection, the Phone-Based Criterion page or Edit Phone-Based Criterion page appears.

Step 3 Edit the information on the page, described in Table 15-7.

Table 15-7 Phone-Based Criterion 

GUI Element
Description/Action

Criterion Name field

Enter a name for the notification criterion.

Customer Identification field

Enter any desired identifying information. If you leave this field empty, it remains blank in e-mail and syslog notifications.

In SNMP trap notifications, it is displayed as follows:

Customer ID: -

Customer Revision field

Enter any desired identifying information. If you leave this field empty, it remains blank in e-mail and syslog notifications.

In SNMP trap notifications, it is displayed as follows:

Customer Revision: *

Unified CM/Unified CM Express-Based Event Threshold

Enter a value for the Unified CM/Unified CM Express-Based Event Threshold. The value should be between 1 and 20. The default value is 5.

If the unregistered count of the phone selected in this notification group is more than the Unified CM/Unified CM Express-based event threshold, then a group event for the Unified Communications Manager
(PhonesUnregisteredThresholdBased) is created.

If it is less than the threshold, an individual PhoneUnregistered event is created.

The Energywise Power Save Plus mode phones in unregistered state are not considered for Notification service.

Prime UOM displays the MAC address of the phone under the cenEventIdList for the PhoneUnregistered event trap notification (Phone Notification). The same traps used for the Phone Notification traps are used in the CISCO-EPM-Notification events.

Selected Phones

Click Add From Phone Report to display a phone report. Selected phones will display in this text area.

Adding more than five phone notification groups and adding the same phone to more than one phone notification group is not recommended.

Add From Phone Report button

Displays the All IP Phones/Lines report, from which you can select phones for your criterion. The maximum number of phones per phone-based notification group is 2,000.


s

Step 4 Click Next.

A page displays the number of phones selected.

Step 5 Click OK.

The Destination: Add or Edit Phone-Based Criterion page appears.

Step 6 Edit the information on this page as described in the Table 15-8.

Table 15-8 Edit Phone Criteria 

GUI Element
Description/Action

Always Active check box

Schedules the notification group to always be active.

Active From: To: fields

Select the hours of the day during which you want this notification group to be active:

From: HH:MM—Select hour and minute that the subscription becomes active.

To: HH:MM—Select the last hour and minute during which the subscription is active.

By default, the values are from 00:00 to 00:00 and the subscription is active for 24 hours.

Use this field, for example, to send e-mail notifications to a pager during one shift and not during another.

Subscription Type radio buttons

Select one at a time to enter data for each subscription type that you want to include in this subscription:

Trap—Enter data in the Trap Subscription Type fields.

E-Mail—Enter data in the E-Mail Subscription Type fields.

Syslog—Enter data in the Syslog Subscription Type fields.

Prime UOM does not save the data you enter until you click Finish on the Subscription: Summary page. To go to the Subscription: Summary page, click Next.

Trap Subscription Type fields

IP Address/Fully Qualified Domain Name editable column

Enter an IP address or Fully Qualified Domain Name (FQDN) of the host.

Port editable column

Enter a port number on which the host can receive traps. A valid port value is a number from 0 to 65,535. You can enter the default port number value 162.

Comments editable column

(Optional) Enter a comment.

E-Mail Subscription Type fields

SMTP Server field

Enter a fully qualified DNS name or IP address for a Simple Mail Transfer Protocol (SMTP) server. (The name of the default SMTP server might already be displayed.)

To select from any nondefault SMTP servers in use by existing subscriptions, click the SMTP Servers button.

For instructions on how to configure a default SMTP server, see the Setting System-Wide Parameters Using System Preferences.

Sender Address field

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) field

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.

Subject Only check box

Select to include only the subject in the e-mail message.

Deselect to send a fully detailed e-mail message (default).

Syslog Subscription Type fields

Facility list

Select a facility from the list (the default is Local Use 0). The Facility field and the event severity are used for the PRI portion of the syslog message, as follows:

[Facility*8][Severity]

Event severity values are as follows:

Critical = 2

Warning = 4

Informational = 6

Location field

(Optional) Enter location information (up to 29 characters). This information will be populated in the syslog message.

IP Address/Fully Qualified Domain Name editable column

Enter an IP address or Fully Qualified Domain Name (FQDN) of the host.

Port editable column

Enter a port number on which the syslog daemon is listening. A valid port value is a number from 0 to 65,535. You can enter the default port number value 514.

The syslog daemon on the remote system (hostname) must be configured to listen on a specified port.

Comments editable column

(Optional) A comment.


Step 7 Click Next.

The Notification Group Summary page appears, displaying all information entered on the previous page.

Step 8 Click Finish.

The notification information is saved.


Cloning a Notification Group

You can use existing notification groups as templates for creating new notification groups.


Caution Cloning a phone notification group is not supported due to the maximum phone limit of 10,000.

To clone a Notification group:


Step 1 Select Administration > Notifications > Notification Criteria.

The Notification Groups Summary page appears.

Step 2 Select the check box next to the notification group that you want to use as the base for your new notification group.

Step 3 Click Clone.

Depending on your selection, the Clone Device-Based Criterion or Clone Service Quality-Based Criterion page appears.

The rest of the procedures for cloning a notification group are the same as when a notification group is edited. For further instructions, see the following:

Adding and Editing Device Notification Groups

Adding and Editing Service Quality Notification Groups


Viewing Notification Group Configuration Details

To view Notification Group Configuration details:


Step 1 Select Administration > Notifications > Notification Criteria.

The Notification Groups Summary page appears.

Step 2 Select the check box next to a notification group.

Step 3 Click View.

Step 4 The Notification Group Summary page appears, displaying the following information:

Notification Name.

Notification Group Details—Event and device type information.

Destination Details—Trap, e-mail, or syslog destination information.


Deleting Notification Groups

To delete Notification groups:


Step 1 Select Administration > Notifications > Notification Criteria.

The Notification Groups Summary page appears.

Step 2 Select the check box next to each notification group that you want to delete.

Step 3 Click Delete.

A confirmation dialog box appears.

Step 4 Click Yes to confirm.


Suspending a Notification

After you suspend a notification, Prime UOM stops using it until you resume it (see Resuming a Notification).

You can suspend a subscription and resume it at any time. You can also schedule a period during the day when you want a notification to be active. For more information, see Adding and Editing Device Notification Groups.

After suspending a notification, the suspend button may still appear enabled. You cannot suspend an already suspended notification. If you click the Suspend button, it will have no effect on the notification. You should use the Notification Groups page to determine the status of a notification.

To suspend any type of notification:


Step 1 Select Administration > Notifications > Notification Criteria.

Step 2 The Notifications Group Summary page appears. Select the check box next to each notification group that you want to suspend.

Step 3 Click Suspend.

A confirmation dialog box appears.

Step 4 Click Yes to confirm.


Resuming a Notification

You can resume a notification when its status is Suspended. After resuming a notification it will go into either active or inactive state depending on the time at which the notification group is resumed, and the time of day settings for that notification group.

Resuming a notification group does not override its time of day settings. The group will resume to operate as it did before suspension.


Note You can resume a notification group only after it has been suspended (it is in the Suspended state). You cannot resume a notification group during its inactive time (it is in the Inactive state), even if the Resume button is enabled.


To resume a suspended notification of any type:


Step 1 Select Administration > Notifications > Notification Criteria.

The Notification Group Summary page appears.

Step 2 Select the check box next to each notification group that you want to resume.

Step 3 Click Resume.

A confirmation dialog box appears.

Step 4 Click Yes to confirm.


Mapping Device Types to Values that Display in Events Sent by Devices

The device types that appear in Prime UOM are listed in Table 15-9. The device type seen in the device report is different from the device type seen in the notification. "Device Type" indicates the primary capability of a device in notifications, and is more granular than the device list information).

These device types appear as "Device type (MANAGED OBJECT)". For example, [12] cenAlarmEntry.cenAlarmManagedObjectClass.0 (OctetString): VoiceGateway.

For the most up-to-date list of devices, see the Supported and Interoperable Devices and Software Table for Cisco Prime Unified Operations Manager.

The Device Type information is categorized into three types of notification:

Device-Based Notification

Service Quality-Based Notification

Phone-Based Notification

Table 15-9 Notification Device Type Categories

Notification Category
Device Type 1

Device-Based Notification

Media Server

Voice Gateway

Router

IPPhone

Switch

Cisco Unified Communications Manager/Unified CM

PhoneAccessSwitch

IPCC

CUE/Unity Express

Customer

Gatekeeper

Cisco Unified Communications Manager or Cluster

Hub

Host

Firewall

MSFC

Bridge

RSM

Service Quality-Based Notification

Endpoint

Phone

Phone-Based Notification

IPPhone

Unified CM

Unified CM Express

1 Device types are transmitted directly from the devices and may be subject to change. Please see your device documentation for details if you do not understand your notification message.


Notifying Users About EPM Log Updates

The following EPM log files updates are included as part of notification:

NMSROOT\log\CUOM\EPM\EPMDroppedEvents.log

NMSROOT\log\CUOM\EPM\ClearedDroppedEvents.log

NMSROOT\log\CUOM\EPM\FloodDroppedEvents.log

To send an email notification when the EPM logs are updated:


Step 1 Edit the NMSROOT\objects\nots\config\nots_epmFloodLog.properties file using your favorite editor.

Step 2 Enable notification of EPM logs updates, by changing the default value of notifyEpmDrop property from No to Yes.

Step 3 Add the email address to which the notifications should be sent in the receiver email address in the emailID property.

To change other optional settings do the following:

To change the poll time, you can set a minimum of 30 minutes to a maximum 7 days in the confCheckInterval property. The value must be set in milliseconds. The default is 2 hours (7,200,000 milliseconds).

To change the email message that is sent upon notification, update the emailMsg property.

Step 4 Specify the SMTP Server in the Administration > Preferences > SMTP Server.

Step 5 Save and close the file.


Any changes you make in the nots_epmFloodLog.properties file are reflected after a two hour delay (default time) and based on the time interval specified in the confCheckInterval setting.

For example, after you change the notifyEpmDrop setting to Yes, you will start receiving emails for EPM log updates only after the second cycle starts.

To immediately reflect the changes in Prime UOM, you must restart the NOTSServer. For details on restarting this process, see Starting and Stopping Prime UOM Processes.

The following EPM log files updates are included as part of notification:

NMSROOT\log\CUOM\EPM\EPMDroppedEvents.log

NMSROOT\log\CUOM\EPM\ClearedDroppedEvents.log

NMSROOT\log\CUOM\EPM\FloodDroppedEvents.log