CH A P T E R
22
Configuring Notifications
Prime CM enables you to configure for:
•
E-mail notifications—Prime CM sends you an e-mail whenever a critical, major, or minor alarm is
triggered for endpoints, network devices, and service infrastructure devices.
You can configure to receive e-mails when the alarm status is updated. The alarm status can be
updated to Active, Acknowledged, or Cleared.
You have to configure to receive notifications, when the events are cleared.
•
SNMP trap notifications—Prime CM generate traps for alarms and events and sends notifications to
the trap receiver. These traps are based on events and alarms that are generated by the Prime CM
server. The traps are converted into SNMPv2c notifications and are formatted according to the
CISCO-EPM-NOTIFICATION-MIB.
With the SNMP trap notifications, you will receive a notification when the events are cleared, by
default.
If you are monitoring the traps using any of the trap receivers, such as HP OpenView, you can
configure the Prime CM server to send notifications.
Configuring for the E-Mail Notifications
You can choose the minimum severity for which you want to receive notifications. If you have selected
to receive notifications for the major events, you will receive notifications for all major and critical
events. Similarly for critical events, you will receive only the critical events and for minor events, you
will receive all severities.
To configure for the e-mail notifications:
Step 1
Choose Administration > System Configuration.
The System Configuration page appears.
Step 2
Check the category type in the Category pane.
Step 3
Choose the minimum alarm severity from the drop-down list in the Category pane.
Step 4
Check the alarm status in the Send Notifications for pane.
If you have not checked the alarm status, you will not receive notifications when an alarm is cleared,
acknowledged, or moved to active.
Cisco Prime Collaboration Manager 1.2 User Guide
OL-26267-01
22-1
Chapter 22
Configuring Notifications
Configuring for the E-Mail Notifications
Step 5
Enter e-mail addresses, separated by commas in the Notification E-mails pane.
You must configure the SMTP server to receive e-mail notifications. You can also configure the From
address for the notification e-mails that are sent from the Prime CM server.
E-mail Notification
The e-mail notification contains the following details:
Device Details
•
Device Name—Hostname of the managed device.
•
Device IP Address—IP address of the managed device.
•
Device Software—Software version running on the device.
Alarm Details
•
Alarm Time Stamp—Time when the alarm was triggered. The Prime CM client time zone is used.
•
Alarm Type Name—Type of the alarm; for example, Call Quality - Packet Loss, Device Access
Error, Interface Error.
•
Alarm Severity—Severity of the alarm; for example, MAJOR, MINOR.
•
Alarm Device Category—Type of device; for example, CTS, CTMS,
•
Alarm Description—Description of the alarm; for example, Call quality alarm, packet loss above
threshold.
•
Event Description—Description of the event; for example, audio rx packet loss on primary Codec
stream is 1.11% (> 1.00%).
•
Alarm Acknowledged—Status whether the alarm was acknowledged.
Session Details
•
Device in Session—Displays whether the device is active in a session.
•
Session Status—Displays the status of the session,
•
Session Type—Whether the session is a point-to-point or multipoint session.
•
Phone Number Dialed—Dialled endpoint phone number.
•
Session Duration—Duration of the session.
The session details are not applicable if you receive an endpoint alarm notification.
Cisco Prime Collaboration Manager Server Name: Hostname of the Prime CM server.
Cisco Prime Collaboration Manager 1.2 User Guide
22-2
OL-26267-01
Chapter 22
Configuring Notifications
Configuring for the SNMP Trap Notifications
Configuring for the SNMP Trap Notifications
The key features are:
•
Notifications are triggered for alarms and events for a specific severity (critical, major, or minor).
•
Notifications are sent to multiple trap receivers on port 162 using UDP.
•
Maximum of 5 trap receivers can be configured in the Prime CM server.
•
As the trap configurations are updated (changing severity-level, enabling alarms or events), the
Prime CM server dynamically changes its behavior at runtime to suit the new configurations.
To register the trap receiver with the Prime CM server the following parameters are required:
•
SNMP Community String—SNMP community string used for sending the SNMP notifications. The
community string can be different for different trap receivers.
Community string is a password that allows access to a SNMP agent running on the OSS client
(Netcool, MIB-Browser, or any other application, which is used to receive traps). SNMP agent can
ignore traps that do not contain specific predefined community string or password, avoid noise, and
refer to traps only from the authorized trap generator.
•
Trap Receiver IP—IP address of the trap receivers to which to send SNMP notifications.
You can configure up to five trap receivers in the Prime CM server.
If you have configured a network firewall between the Prime CM server and the trap receiver, ensure that
the port 162 (UDP) is opened on the trap receiver to receive notifications.
To configure trap receivers in the Prime CM server:
Step 1
Choose Administration > System Configuration.
The System Configuration page appears.
Step 2
Check Alarms and/or Events to receive traps in the Trap Configuration pane.
You cannot enable different notifications (alarms and/or events) for different trap receivers. The
notifications are the same for all trap receivers.
Step 3
Select the severity from the Choose minimum severity level that triggers notification drop-down list.
You cannot select different severity for different trap receivers. The severity is the same for all trap
receivers.
You can choose the minimum severity for which you want to receive notifications. If you have selected
to receive notifications for the major events. You will receive notifications for all major and critical
events. Similarly for critical events, you will receive only the critical events and for minor events, you
will receive all severities.
Step 4
Enter the Trap Receiver IP address and SNMP Community String.
Step 5
Click New to add the trap receiver details.
The trap receiver details are listed in the Trap Configuration table.
You can edit the Trap Receiver IP, SNMP Community String, severity, events, and alarms configuration
at any time, the Prime CM server dynamically changes its behavior at runtime to suit the new
configurations.
You can reset the trap receiver details, using the Reset to Default button.
Cisco Prime Collaboration Manager 1.2 User Guide
OL-26267-01
22-3
Chapter 22
Configuring Notifications
Configuring for the SNMP Trap Notifications
Step 6
Click Save to save the system configuration.
Cisco EPM Notification MIB
When an alarm or an event is received in the Prime CM server, it is converted to the trap format defined
in the CISCO-EPM-NOTIFICATION-MIB. Other MIB objects are not supported. All the trap receivers
receive the same traps in same trap format.
The CISCO-EPM-NOTIFICATION-MIB can be downloaded from Cisco.com.
Table 22-1 describes the mapping between the MIB OIDs to the relevant value that is assigned by
Prime CM for alarms.
Table 22-1
CISCO-EPM-NOTIFICATION-MIB Summary for Alarms
Trap Field Name
OID
Type
Prime CM Alarm Content as in Trap Forwarder (EPM MIB)
cenAlarmIndex
1.3.6.1.4.1.9.9.311. Unsigned32
0.2.1.1.2.1.1
—
MIB index
cenAlarmVersion
1.3.6.1.4.1.9.9.311. SnmpAdmin
0.2.1.1.2.1.2
String
—
The version of this MIB. The version
string will be of the form major
version.minor version.
Note
Always set to 1.1
cenAlarmTimestamp
1.3.6.1.4.1.9.9.311. Timestamp
0.2.1.1.2.1.3
Timestamp
The time when the alarm was triggered.
cenAlarmUpdatedTime
stamp
1.3.6.1.4.1.9.9.311. Timestamp
0.2.1.1.2.1.4
lastmodified
timestamp
The last time when the alarm was
modified.
cenAlarmInstanceID
1.3.6.1.4.1.9.9.311. SnmpAdmin
0.2.1.1.2.1.5
String
ID
The unique alarm ID generated by
Prime CM.
cenAlarmStatus
1.3.6.1.4.1.9.9.311. Integer32
0.2.1.1.2.1.6
lastcleartime
Indicates whether the alarm is active (1)
or cleared (2)
cenAlarmStatus
Definition
1.3.6.1.4.1.9.9.311. SnmpAdmin
0.2.1.1.2.1.7
String
lastcleartime
A short description of the status of the
alarm:
•
1—Active
•
2—Cleared
cenAlarmType
1.3.6.1.4.1.9.9.311. Integer
0.2.1.1.2.1.8
—
The alarm type is direct (2).
cenAlarmCategory
1.3.6.1.4.1.9.9.311. Integer32
0.2.1.1.2.1.9
category
The alarm categories. It is represented as an
integer value.
Cisco Prime Collaboration Manager 1.2 User Guide
22-4
OL-26267-01
Chapter 22
Configuring Notifications
Configuring for the SNMP Trap Notifications
Table 22-1
CISCO-EPM-NOTIFICATION-MIB Summary for Alarms (continued)
Trap Field Name
OID
Type
cenAlarmCategory
Definition
1.3.6.1.4.1.9.9.311. SnmpAdmin
0.2.1.1.2.1.10
String
Prime CM Alarm Content as in Trap Forwarder (EPM MIB)
category
This is a string representation of
AlarmCategory (number,description):
•
3,Endpoint—Hardware alarms
(peripheral errors) in all endpoints.
•
4,Network Devices—Hardware
alarms (interface errors) in all
network devices.
•
5,Service Infrastructure—Alarms in
call and session control (Cisco
Unified CM and VCS), management
(CTS-Manager and TMS), multipoint
switches (CTMS), and multipoint
control units (TPS, MCU).
•
6,Session—Endpoints alarms (that
are part of the session) and network
alarms (jitter, latency, or drop).
cenAlarmServer
AddressType
1.3.6.1.4.1.9.9.311. InetAddress
0.2.1.1.2.1.11
Type
—
The type of internet address at which the
server that is generating this trap, is
reachable. This value is set to 1 for IPV4
management.
cenAlarmServer
Address
1.3.6.1.4.1.9.9.311. InetAddress
0.2.1.1.2.1.12
—
Prime CM IP address or DNS name.
cenAlarmManaged
ObjectClass
1.3.6.1.4.1.9.9.311. SnmpAdmin
0.2.1.1.2.1.13
String
Source
Entity type of the source, such as CTS,
Cisco VCS, and so on.
cenAlarmManaged
ObjectAddressType
1.3.6.1.4.1.9.9.311. InetAddress
0.2.1.1.2.1.14
Type
Source
The type of internet address at which the
managed device is reachable. This value
is set to 1 for IPV4 management.
cenAlarmManaged
ObjectAddress
1.3.6.1.4.1.9.9.311. InetAddress
0.2.1.1.2.1.15
Source
IP Address or DNS name of the managed
object.
cenAlarmDescription
1.3.6.1.4.1.9.9.311. OctetString
0.2.1.1.2.1.16
Description
A detailed description of the alarm.
cenAlarmSeverity
1.3.6.1.4.1.9.9.311. Integer32
0.2.1.1.2.1.17
Severity
Indicates the severity of the alarm using
an integer value. The valid integers are 0
- 7 (see cenAlarmSeverity Definition).
Cisco Prime Collaboration Manager 1.2 User Guide
OL-26267-01
22-5
Chapter 22
Configuring Notifications
Configuring for the SNMP Trap Notifications
Table 22-1
CISCO-EPM-NOTIFICATION-MIB Summary for Alarms (continued)
Trap Field Name
OID
Type
cenAlarmSeverity
Definition
1.3.6.1.4.1.9.9.311. OctetString
0.2.1.1.2.1.18
Prime CM Alarm Content as in Trap Forwarder (EPM MIB)
Severity
Alarm severity string representation
(number,description):
•
0,critical
•
1,major
•
2,minor
•
3,warning
•
4,info
•
5,normal
•
6,unknown
•
7,cleared
cenAlarmTriageValue
1.3.6.1.4.1.9.9.311. Integer32
0.2.1.1.2.1.19
—
Not used.
cenEventIDList
1.3.6.1.4.1.9.9.311. OctetString
0.2.1.1.2.1.20
—
List of event IDs that led to this alarm.
cenUserMessage1
1.3.6.1.4.1.9.9.311. SnmpAdmin
0.2.1.1.2.1.21
String
isacknowledged Indicates whether the alarm is
acknowledged or unacknowledged.
cenUserMessage2
1.3.6.1.4.1.9.9.311. SnmpAdmin
0.2.1.1.2.1.22
String
previous
Severity
Previous severity of the alarm.
cenUserMessage3
1.3.6.1.4.1.9.9.311. SnmpAdmin
0.2.1.1.2.1.23
String
—
Not used.
cenAlarmMode
1.3.6.1.4.1.9.9.311. Integer
0.2.1.1.2.1.24
—
2—alert. Indicates this trap is either an
alarm or event notification.
cenPartitionNumber
1.3.6.1.4.1.9.9.311. Unsigned32
0.2.1.1.2.1.25
—
Not used.
cenPartitionName
1.3.6.1.4.1.9.9.311. SnmpAdmin
0.2.1.1.2.1.26
String
—
Not used.
cenCustomer
Identification
1.3.6.1.4.1.9.9.311. SnmpAdmin
0.2.1.1.2.1.27
String
ownerid
A user assigned to the alarm.
cenCustomerRevision
1.3.6.1.4.1.9.9.311. SnmpAdmin
0.2.1.1.2.1.28
String
—
Not used.
cenAlertID
1.3.6.1.4.1.9.9.311. SnmpAdmin
0.2.1.1.2.1.29
String
id
Same as cenAlarmInstanceID.
For example, assume that while the
session was in-progress, a major alarm
was triggered. After the session is
complete, the session alarm is
automatically Cleared. The alarm severity
displays Major because the previous
alarm severity for this session was Major.
Cisco Prime Collaboration Manager 1.2 User Guide
22-6
OL-26267-01
Chapter 22
Configuring Notifications
Configuring for the SNMP Trap Notifications
Table 22-2 describes the mapping between the MIB OIDs to the relevant value that is assigned by
Prime CM for alarms.
Table 22-2
CISCO-EPM-NOTIFICATION-MIB Summary for Events
Trap Field Name
OID
Type
Prime CM Event Content as in Trap Forwarder (EPM MIB)
cenAlarmIndex
1.3.6.1.4.1.9.9.311. Unsigned32
0.2.1.1.2.1.1
—
MIB index
cenAlarmVersion
1.3.6.1.4.1.9.9.311. SnmpAdmin
0.2.1.1.2.1.2
String
—
The version of this MIB. The version
string will be of the form major
version.minor version.
Note
Always set to 1.1
cenAlarmTimestamp
1.3.6.1.4.1.9.9.311. Timestamp
0.2.1.1.2.1.3
Timestamp
The time when the event was triggered.
cenAlarmUpdatedTime
stamp
1.3.6.1.4.1.9.9.311. Timestamp
0.2.1.1.2.1.4
—
Not used.
cenAlarmInstanceID
1.3.6.1.4.1.9.9.311. SnmpAdmin
0.2.1.1.2.1.5
String
ID
The unique event ID generated by
Prime CM.
cenAlarmStatus
1.3.6.1.4.1.9.9.311. Integer32
0.2.1.1.2.1.6
—
Not used.
cenAlarmStatus
Definition
1.3.6.1.4.1.9.9.311. SnmpAdmin
0.2.1.1.2.1.7
String
—
Not used.
cenAlarmType
1.3.6.1.4.1.9.9.311. Integer
0.2.1.1.2.1.8
—
The event type is direct (2).
cenAlarmCategory
1.3.6.1.4.1.9.9.311. Integer32
0.2.1.1.2.1.9
category
The event categories. It is represented as an
integer value.
cenAlarmCategory
Definition
1.3.6.1.4.1.9.9.311. SnmpAdmin
0.2.1.1.2.1.10
String
category
This is a string representation of
AlarmCategory (number,description):
cenAlarmServer
AddressType
1.3.6.1.4.1.9.9.311. InetAddress
0.2.1.1.2.1.11
Type
—
•
3,Endpoint—Hardware events
(peripheral errors) in all endpoints.
•
4,Network Devices—Hardware
events (interface errors) in all
network devices.
•
5,Service Infrastructure—events in
call and session control (Cisco
Unified CM and VCS), management
(CTS-Manager and TMS), multipoint
switches (CTMS), and multipoint
control units (TPS, MCU).
•
6,Session—Endpoints events (that
are part of the session) and network
events (jitter, latency, or drop).
The type of internet address at which the
server that is generating this trap, is
reachable. This value is set to 1 for IPV4
management.
Cisco Prime Collaboration Manager 1.2 User Guide
OL-26267-01
22-7
Chapter 22
Configuring Notifications
Configuring for the SNMP Trap Notifications
Table 22-2
CISCO-EPM-NOTIFICATION-MIB Summary for Events (continued)
Trap Field Name
OID
Type
Prime CM Event Content as in Trap Forwarder (EPM MIB)
cenAlarmServer
Address
1.3.6.1.4.1.9.9.311. InetAddress
0.2.1.1.2.1.12
—
Prime CM IP address or DNS name.
cenAlarmManaged
ObjectClass
1.3.6.1.4.1.9.9.311. SnmpAdmin
0.2.1.1.2.1.13
String
Source
Entity type of the source, such as CTS,
Cisco VCS, and so on.
cenAlarmManaged
ObjectAddressType
1.3.6.1.4.1.9.9.311. InetAddress
0.2.1.1.2.1.14
Type
Source
The type of internet address at which the
managed device is reachable. This value
is set to 1 for IPV4 management.
cenAlarmManaged
ObjectAddress
1.3.6.1.4.1.9.9.311. InetAddress
0.2.1.1.2.1.15
Source
IP Address or DNS name of the managed
object.
cenAlarmDescription
1.3.6.1.4.1.9.9.311. OctetString
0.2.1.1.2.1.16
Description
A detailed description of the event.
cenAlarmSeverity
1.3.6.1.4.1.9.9.311. Integer32
0.2.1.1.2.1.17
Severity
Indicates the severity of the event using
an integer value. The valid integers are 0
- 7 (see cenAlarmSeverity Definition).
cenAlarmSeverity
Definition
1.3.6.1.4.1.9.9.311. OctetString
0.2.1.1.2.1.18
Severity
Alarm severity string representation
(number,description):
•
0,critical
•
1,major
•
2,minor
•
3,warning
•
4,info
•
5,normal
•
6,unknown
•
7,cleared
cenAlarmTriageValue
1.3.6.1.4.1.9.9.311. Integer32
0.2.1.1.2.1.19
—
Not used.
cenEventIDList
1.3.6.1.4.1.9.9.311. OctetString
0.2.1.1.2.1.20
—
Not used.
cenUserMessage1
1.3.6.1.4.1.9.9.311. SnmpAdmin
0.2.1.1.2.1.21
String
—
Not used.
cenUserMessage2
1.3.6.1.4.1.9.9.311. SnmpAdmin
0.2.1.1.2.1.22
String
—
Not used.
cenUserMessage3
1.3.6.1.4.1.9.9.311. SnmpAdmin
0.2.1.1.2.1.23
String
—
Not used.
cenAlarmMode
1.3.6.1.4.1.9.9.311. Integer
0.2.1.1.2.1.24
—
3—event. Indicates this trap is either an
alarm or event notification.
cenPartitionNumber
1.3.6.1.4.1.9.9.311. Unsigned32
0.2.1.1.2.1.25
—
Not used.
cenPartitionName
1.3.6.1.4.1.9.9.311. SnmpAdmin
0.2.1.1.2.1.26
String
—
Not used.
Cisco Prime Collaboration Manager 1.2 User Guide
22-8
OL-26267-01
Chapter 22
Configuring Notifications
Sample SNMPv2 Trap Notifications
Table 22-2
CISCO-EPM-NOTIFICATION-MIB Summary for Events (continued)
Trap Field Name
OID
Type
Prime CM Event Content as in Trap Forwarder (EPM MIB)
cenCustomer
Identification
1.3.6.1.4.1.9.9.311. SnmpAdmin
0.2.1.1.2.1.27
String
—
Not used.
cenCustomerRevision
1.3.6.1.4.1.9.9.311. SnmpAdmin
0.2.1.1.2.1.28
String
—
Not used.
cenAlertID
1.3.6.1.4.1.9.9.311. SnmpAdmin
0.2.1.1.2.1.29
String
—
Not used.
Sample SNMPv2 Trap Notifications
The following SNMPv2 trap notifications are sent when an alarm and an event is triggered in the
Prime CM server.
•
Sample SNMPv2 Trap Notifications for Alarms, page 22-9
•
Sample SNMPv2 Trap Notification for Events, page 22-10
Sample SNMPv2 Trap Notifications for Alarms
In this sample:
•
Alarm 102882 is triggered by the events 102881 and 102883.
•
Alarm is still active and it is not acknowledged.
•
Alarm severity is major and it is triggered for a session because of packet loss above threshold (Call
quality alarm). The IP address of the endpoint (CTS) that triggered this alarm is 172.23.223.189.
•
The IP address of the Prime CM server is 172.23.223.148.
.iso.org.dod.internet.private.enterprises.cisco.ciscoMgmt.ciscoEpmNotificationMIB.ciscoEpmNotificationMIBObje
cts.cenAlarmData.cenAlarmTable.cenAlarmEntry.cenAlarmVersion: 1.2
.iso.org.dod.internet.private.enterprises.cisco.ciscoMgmt.ciscoEpmNotificationMIB.ciscoEpmNotificationMIBObje
cts.cenAlarmData.cenAlarmTable.cenAlarmEntry.cenAlarmTimestamp: Tue Aug 02 16: 10: 46 UTC 2011
.iso.org.dod.internet.private.enterprises.cisco.ciscoMgmt.ciscoEpmNotificationMIB.ciscoEpmNotificationMIBObje
cts.cenAlarmData.cenAlarmTable.cenAlarmEntry.cenAlarmUpdatedTimestamp: Tue Aug 02 16: 10: 46 UTC 2011
.iso.org.dod.internet.private.enterprises.cisco.ciscoMgmt.ciscoEpmNotificationMIB.ciscoEpmNotificationMIBObje
cts.cenAlarmData.cenAlarmTable.cenAlarmEntry.cenAlarmInstanceID: 102882
.iso.org.dod.internet.private.enterprises.cisco.ciscoMgmt.ciscoEpmNotificationMIB.ciscoEpmNotificationMIBObje
cts.cenAlarmData.cenAlarmTable.cenAlarmEntry.cenAlarmStatus: INTEGER: 1
.iso.org.dod.internet.private.enterprises.cisco.ciscoMgmt.ciscoEpmNotificationMIB.ciscoEpmNotificationMIBObje
cts.cenAlarmData.cenAlarmTable.cenAlarmEntry.cenAlarmStatusDefinition: 1,active
.iso.org.dod.internet.private.enterprises.cisco.ciscoMgmt.ciscoEpmNotificationMIB.ciscoEpmNotificationMIBObje
cts.cenAlarmData.cenAlarmTable.cenAlarmEntry.cenAlarmType: INTEGER: 2
.iso.org.dod.internet.private.enterprises.cisco.ciscoMgmt.ciscoEpmNotificationMIB.ciscoEpmNotificationMIBObje
cts.cenAlarmData.cenAlarmTable.cenAlarmEntry.cenAlarmCategory: INTEGER: 6
.iso.org.dod.internet.private.enterprises.cisco.ciscoMgmt.ciscoEpmNotificationMIB.ciscoEpmNotificationMIBObje
cts.cenAlarmData.cenAlarmTable.cenAlarmEntry.cenAlarmCategoryDefinition: 6,session
.iso.org.dod.internet.private.enterprises.cisco.ciscoMgmt.ciscoEpmNotificationMIB.ciscoEpmNotificationMIBObje
cts.cenAlarmData.cenAlarmTable.cenAlarmEntry.cenAlarmServerAddressType: INTEGER: 1
.iso.org.dod.internet.private.enterprises.cisco.ciscoMgmt.ciscoEpmNotificationMIB.ciscoEpmNotificationMIBObje
cts.cenAlarmData.cenAlarmTable.cenAlarmEntry.cenAlarmServerAddress: 172.23.223.148
.iso.org.dod.internet.private.enterprises.cisco.ciscoMgmt.ciscoEpmNotificationMIB.ciscoEpmNotificationMIBObje
cts.cenAlarmData.cenAlarmTable.cenAlarmEntry.cenAlarmManagedObjectClass: CTS
.iso.org.dod.internet.private.enterprises.cisco.ciscoMgmt.ciscoEpmNotificationMIB.ciscoEpmNotificationMIBObje
cts.cenAlarmData.cenAlarmTable.cenAlarmEntry.cenAlarmManagedObjectAddressType: INTEGER: 1
Cisco Prime Collaboration Manager 1.2 User Guide
OL-26267-01
22-9
Chapter 22
Configuring Notifications
Sample SNMPv2 Trap Notifications
.iso.org.dod.internet.private.enterprises.cisco.ciscoMgmt.ciscoEpmNotificationMIB.ciscoEpmNotificationMIBObje
cts.cenAlarmData.cenAlarmTable.cenAlarmEntry.cenAlarmManagedObjectAddress: 172.23.223.189
.iso.org.dod.internet.private.enterprises.cisco.ciscoMgmt.ciscoEpmNotificationMIB.ciscoEpmNotificationMIBObje
cts.cenAlarmData.cenAlarmTable.cenAlarmEntry.cenAlarmDescription: Call quality alarm, packet loss above
threshold.
.iso.org.dod.internet.private.enterprises.cisco.ciscoMgmt.ciscoEpmNotificationMIB.ciscoEpmNotificationMIBObje
cts.cenAlarmData.cenAlarmTable.cenAlarmEntry.cenAlarmSeverity: INTEGER: 1
.iso.org.dod.internet.private.enterprises.cisco.ciscoMgmt.ciscoEpmNotificationMIB.ciscoEpmNotificationMIBObje
cts.cenAlarmData.cenAlarmTable.cenAlarmEntry.cenAlarmSeverityDefinition: 1,major
.iso.org.dod.internet.private.enterprises.cisco.ciscoMgmt.ciscoEpmNotificationMIB.ciscoEpmNotificationMIBObje
cts.cenAlarmData.cenAlarmTable.cenAlarmEntry.cenAlarmTriageValue: not applicable
.iso.org.dod.internet.private.enterprises.cisco.ciscoMgmt.ciscoEpmNotificationMIB.ciscoEpmNotificationMIBObje
cts.cenAlarmData.cenAlarmTable.cenAlarmEntry.cenEventIDList: 102881, 102883
.iso.org.dod.internet.private.enterprises.cisco.ciscoMgmt.ciscoEpmNotificationMIB.ciscoEpmNotificationMIBObje
cts.cenAlarmData.cenAlarmTable.cenAlarmEntry.cenUserMessage1: unacknowledged
.iso.org.dod.internet.private.enterprises.cisco.ciscoMgmt.ciscoEpmNotificationMIB.ciscoEpmNotificationMIBObje
cts.cenAlarmData.cenAlarmTable.cenAlarmEntry.cenUserMessage2: not applicable
.iso.org.dod.internet.private.enterprises.cisco.ciscoMgmt.ciscoEpmNotificationMIB.ciscoEpmNotificationMIBObje
cts.cenAlarmData.cenAlarmTable.cenAlarmEntry.cenUserMessage3: not applicable
.iso.org.dod.internet.private.enterprises.cisco.ciscoMgmt.ciscoEpmNotificationMIB.ciscoEpmNotificationMIBObje
cts.cenAlarmData.cenAlarmTable.cenAlarmEntry.cenAlarmMode: INTEGER: 2
.iso.org.dod.internet.private.enterprises.cisco.ciscoMgmt.ciscoEpmNotificationMIB.ciscoEpmNotificationMIBObje
cts.cenAlarmData.cenAlarmTable.cenAlarmEntry.cenPartitionNumber: not applicable
.iso.org.dod.internet.private.enterprises.cisco.ciscoMgmt.ciscoEpmNotificationMIB.ciscoEpmNotificationMIBObje
cts.cenAlarmData.cenAlarmTable.cenAlarmEntry.cenPartitionName: not applicable
.iso.org.dod.internet.private.enterprises.cisco.ciscoMgmt.ciscoEpmNotificationMIB.ciscoEpmNotificationMIBObje
cts.cenAlarmData.cenAlarmTable.cenAlarmEntry.cenCustomerIdentification: not applicable
.iso.org.dod.internet.private.enterprises.cisco.ciscoMgmt.ciscoEpmNotificationMIB.ciscoEpmNotificationMIBObje
cts.cenAlarmData.cenAlarmTable.cenAlarmEntry.cenCustomerRevision: not applicable
.iso.org.dod.internet.private.enterprises.cisco.ciscoMgmt.ciscoEpmNotificationMIB.ciscoEpmNotificationMIBObje
cts.cenAlarmData.cenAlarmTable.cenAlarmEntry.cenAlertID: 102882
Sample SNMPv2 Trap Notification for Events
The following is the sample notification for the event 102881:
•
Event severity is major and it is triggered for a session because of audio rx packet loss on primary
Codec stream is 1.93% (> 1.00%).
•
The IP address of the endpoint (CTS) that triggered this alarm is 172.23.223.189.
•
The IP address of the Prime CM server is 172.23.223.148.
.iso.org.dod.internet.private.enterprises.cisco.ciscoMgmt.ciscoEpmNotificationMIB.ciscoEpmNotificationMIBObje
cts.cenAlarmData.cenAlarmTable.cenAlarmEntry.cenAlarmVersion: 1.2
.iso.org.dod.internet.private.enterprises.cisco.ciscoMgmt.ciscoEpmNotificationMIB.ciscoEpmNotificationMIBObje
cts.cenAlarmData.cenAlarmTable.cenAlarmEntry.cenAlarmTimestamp: Tue Aug 02 16: 10: 46 UTC 2011
.iso.org.dod.internet.private.enterprises.cisco.ciscoMgmt.ciscoEpmNotificationMIB.ciscoEpmNotificationMIBObje
cts.cenAlarmData.cenAlarmTable.cenAlarmEntry.cenAlarmUpdatedTimestamp: not applicable
.iso.org.dod.internet.private.enterprises.cisco.ciscoMgmt.ciscoEpmNotificationMIB.ciscoEpmNotificationMIBObje
cts.cenAlarmData.cenAlarmTable.cenAlarmEntry.cenAlarmInstanceID: 102881
.iso.org.dod.internet.private.enterprises.cisco.ciscoMgmt.ciscoEpmNotificationMIB.ciscoEpmNotificationMIBObje
cts.cenAlarmData.cenAlarmTable.cenAlarmEntry.cenAlarmStatus: INTEGER: -1
.iso.org.dod.internet.private.enterprises.cisco.ciscoMgmt.ciscoEpmNotificationMIB.ciscoEpmNotificationMIBObje
cts.cenAlarmData.cenAlarmTable.cenAlarmEntry.cenAlarmStatusDefinition: not applicable
.iso.org.dod.internet.private.enterprises.cisco.ciscoMgmt.ciscoEpmNotificationMIB.ciscoEpmNotificationMIBObje
cts.cenAlarmData.cenAlarmTable.cenAlarmEntry.cenAlarmType: INTEGER: 2
.iso.org.dod.internet.private.enterprises.cisco.ciscoMgmt.ciscoEpmNotificationMIB.ciscoEpmNotificationMIBObje
cts.cenAlarmData.cenAlarmTable.cenAlarmEntry.cenAlarmCategory: INTEGER: 6
.iso.org.dod.internet.private.enterprises.cisco.ciscoMgmt.ciscoEpmNotificationMIB.ciscoEpmNotificationMIBObje
cts.cenAlarmData.cenAlarmTable.cenAlarmEntry.cenAlarmCategoryDefinition: 6,session
.iso.org.dod.internet.private.enterprises.cisco.ciscoMgmt.ciscoEpmNotificationMIB.ciscoEpmNotificationMIBObje
cts.cenAlarmData.cenAlarmTable.cenAlarmEntry.cenAlarmServerAddressType: INTEGER: 1
Cisco Prime Collaboration Manager 1.2 User Guide
22-10
OL-26267-01
Chapter 22
Configuring Notifications
Sample SNMPv2 Trap Notifications
.iso.org.dod.internet.private.enterprises.cisco.ciscoMgmt.ciscoEpmNotificationMIB.ciscoEpmNotificationMIBObje
cts.cenAlarmData.cenAlarmTable.cenAlarmEntry.cenAlarmServerAddress: 172.23.223.148
.iso.org.dod.internet.private.enterprises.cisco.ciscoMgmt.ciscoEpmNotificationMIB.ciscoEpmNotificationMIBObje
cts.cenAlarmData.cenAlarmTable.cenAlarmEntry.cenAlarmManagedObjectClass: CTS
.iso.org.dod.internet.private.enterprises.cisco.ciscoMgmt.ciscoEpmNotificationMIB.ciscoEpmNotificationMIBObje
cts.cenAlarmData.cenAlarmTable.cenAlarmEntry.cenAlarmManagedObjectAddressType: INTEGER: 1
.iso.org.dod.internet.private.enterprises.cisco.ciscoMgmt.ciscoEpmNotificationMIB.ciscoEpmNotificationMIBObje
cts.cenAlarmData.cenAlarmTable.cenAlarmEntry.cenAlarmManagedObjectAddress: 172.23.223.189
.iso.org.dod.internet.private.enterprises.cisco.ciscoMgmt.ciscoEpmNotificationMIB.ciscoEpmNotificationMIBObje
cts.cenAlarmData.cenAlarmTable.cenAlarmEntry.cenAlarmDescription: audio rx packet loss on primary Codec
stream is 1.93% (> 1.00%)
.iso.org.dod.internet.private.enterprises.cisco.ciscoMgmt.ciscoEpmNotificationMIB.ciscoEpmNotificationMIBObje
cts.cenAlarmData.cenAlarmTable.cenAlarmEntry.cenAlarmSeverity: INTEGER: 1
.iso.org.dod.internet.private.enterprises.cisco.ciscoMgmt.ciscoEpmNotificationMIB.ciscoEpmNotificationMIBObje
cts.cenAlarmData.cenAlarmTable.cenAlarmEntry.cenAlarmSeverityDefinition: 1,major
.iso.org.dod.internet.private.enterprises.cisco.ciscoMgmt.ciscoEpmNotificationMIB.ciscoEpmNotificationMIBObje
cts.cenAlarmData.cenAlarmTable.cenAlarmEntry.cenAlarmTriageValue: not applicable
.iso.org.dod.internet.private.enterprises.cisco.ciscoMgmt.ciscoEpmNotificationMIB.ciscoEpmNotificationMIBObje
cts.cenAlarmData.cenAlarmTable.cenAlarmEntry.cenEventIDList: not applicable
.iso.org.dod.internet.private.enterprises.cisco.ciscoMgmt.ciscoEpmNotificationMIB.ciscoEpmNotificationMIBObje
cts.cenAlarmData.cenAlarmTable.cenAlarmEntry.cenUserMessage1: not applicable
.iso.org.dod.internet.private.enterprises.cisco.ciscoMgmt.ciscoEpmNotificationMIB.ciscoEpmNotificationMIBObje
cts.cenAlarmData.cenAlarmTable.cenAlarmEntry.cenUserMessage2: not applicable
.iso.org.dod.internet.private.enterprises.cisco.ciscoMgmt.ciscoEpmNotificationMIB.ciscoEpmNotificationMIBObje
cts.cenAlarmData.cenAlarmTable.cenAlarmEntry.cenUserMessage3: not applicable
.iso.org.dod.internet.private.enterprises.cisco.ciscoMgmt.ciscoEpmNotificationMIB.ciscoEpmNotificationMIBObje
cts.cenAlarmData.cenAlarmTable.cenAlarmEntry.cenAlarmMode: INTEGER: 3
.iso.org.dod.internet.private.enterprises.cisco.ciscoMgmt.ciscoEpmNotificationMIB.ciscoEpmNotificationMIBObje
cts.cenAlarmData.cenAlarmTable.cenAlarmEntry.cenPartitionNumber: not applicable
.iso.org.dod.internet.private.enterprises.cisco.ciscoMgmt.ciscoEpmNotificationMIB.ciscoEpmNotificationMIBObje
cts.cenAlarmData.cenAlarmTable.cenAlarmEntry.cenPartitionName: not applicable
.iso.org.dod.internet.private.enterprises.cisco.ciscoMgmt.ciscoEpmNotificationMIB.ciscoEpmNotificationMIBObje
cts.cenAlarmData.cenAlarmTable.cenAlarmEntry.cenCustomerIdentification: not applicable
.iso.org.dod.internet.private.enterprises.cisco.ciscoMgmt.ciscoEpmNotificationMIB.ciscoEpmNotificationMIBObje
cts.cenAlarmData.cenAlarmTable.cenAlarmEntry.cenCustomerRevision: not applicable
.iso.org.dod.internet.private.enterprises.cisco.ciscoMgmt.ciscoEpmNotificationMIB.ciscoEpmNotificationMIBObje
cts.cenAlarmData.cenAlarmTable.cenAlarmEntry.cenAlertID: not applicable
The following is the sample notification for the event 102883:
•
Event severity is major and it is triggered for a session because of video rx packet loss on primary
Codec stream is 2.78% (> 1.00%).
•
The IP address of the endpoint (CTS) that triggered this alarm is 172.23.223.189.
•
The IP address of the Prime CM server is 172.23.223.148.
.iso.org.dod.internet.private.enterprises.cisco.ciscoMgmt.ciscoEpmNotificationMIB.ciscoEpmNotificationMIBObje
cts.cenAlarmData.cenAlarmTable.cenAlarmEntry.cenAlarmVersion: 1.2
.iso.org.dod.internet.private.enterprises.cisco.ciscoMgmt.ciscoEpmNotificationMIB.ciscoEpmNotificationMIBObje
cts.cenAlarmData.cenAlarmTable.cenAlarmEntry.cenAlarmTimestamp: Tue Aug 02 16: 10: 46 UTC 2011
.iso.org.dod.internet.private.enterprises.cisco.ciscoMgmt.ciscoEpmNotificationMIB.ciscoEpmNotificationMIBObje
cts.cenAlarmData.cenAlarmTable.cenAlarmEntry.cenAlarmUpdatedTimestamp: not applicable
.iso.org.dod.internet.private.enterprises.cisco.ciscoMgmt.ciscoEpmNotificationMIB.ciscoEpmNotificationMIBObje
cts.cenAlarmData.cenAlarmTable.cenAlarmEntry.cenAlarmInstanceID: 102883
.iso.org.dod.internet.private.enterprises.cisco.ciscoMgmt.ciscoEpmNotificationMIB.ciscoEpmNotificationMIBObje
cts.cenAlarmData.cenAlarmTable.cenAlarmEntry.cenAlarmStatus: INTEGER: -1
.iso.org.dod.internet.private.enterprises.cisco.ciscoMgmt.ciscoEpmNotificationMIB.ciscoEpmNotificationMIBObje
cts.cenAlarmData.cenAlarmTable.cenAlarmEntry.cenAlarmStatusDefinition: not applicable
.iso.org.dod.internet.private.enterprises.cisco.ciscoMgmt.ciscoEpmNotificationMIB.ciscoEpmNotificationMIBObje
cts.cenAlarmData.cenAlarmTable.cenAlarmEntry.cenAlarmType: INTEGER: 2
.iso.org.dod.internet.private.enterprises.cisco.ciscoMgmt.ciscoEpmNotificationMIB.ciscoEpmNotificationMIBObje
cts.cenAlarmData.cenAlarmTable.cenAlarmEntry.cenAlarmCategory: INTEGER: 6
Cisco Prime Collaboration Manager 1.2 User Guide
OL-26267-01
22-11
Chapter 22
Configuring Notifications
Sample SNMPv2 Trap Notifications
.iso.org.dod.internet.private.enterprises.cisco.ciscoMgmt.ciscoEpmNotificationMIB.ciscoEpmNotificationMIBObje
cts.cenAlarmData.cenAlarmTable.cenAlarmEntry.cenAlarmCategoryDefinition: 6,session
.iso.org.dod.internet.private.enterprises.cisco.ciscoMgmt.ciscoEpmNotificationMIB.ciscoEpmNotificationMIBObje
cts.cenAlarmData.cenAlarmTable.cenAlarmEntry.cenAlarmServerAddressType: INTEGER: 1
.iso.org.dod.internet.private.enterprises.cisco.ciscoMgmt.ciscoEpmNotificationMIB.ciscoEpmNotificationMIBObje
cts.cenAlarmData.cenAlarmTable.cenAlarmEntry.cenAlarmServerAddress: 172.23.223.148
.iso.org.dod.internet.private.enterprises.cisco.ciscoMgmt.ciscoEpmNotificationMIB.ciscoEpmNotificationMIBObje
cts.cenAlarmData.cenAlarmTable.cenAlarmEntry.cenAlarmManagedObjectClass: CTS
.iso.org.dod.internet.private.enterprises.cisco.ciscoMgmt.ciscoEpmNotificationMIB.ciscoEpmNotificationMIBObje
cts.cenAlarmData.cenAlarmTable.cenAlarmEntry.cenAlarmManagedObjectAddressType: INTEGER: 1
.iso.org.dod.internet.private.enterprises.cisco.ciscoMgmt.ciscoEpmNotificationMIB.ciscoEpmNotificationMIBObje
cts.cenAlarmData.cenAlarmTable.cenAlarmEntry.cenAlarmManagedObjectAddress: 172.23.223.189
.iso.org.dod.internet.private.enterprises.cisco.ciscoMgmt.ciscoEpmNotificationMIB.ciscoEpmNotificationMIBObje
cts.cenAlarmData.cenAlarmTable.cenAlarmEntry.cenAlarmDescription: video rx packet loss on primary Codec
stream is 2.78% (> 1.00%)
.iso.org.dod.internet.private.enterprises.cisco.ciscoMgmt.ciscoEpmNotificationMIB.ciscoEpmNotificationMIBObje
cts.cenAlarmData.cenAlarmTable.cenAlarmEntry.cenAlarmSeverity: INTEGER: 1
.iso.org.dod.internet.private.enterprises.cisco.ciscoMgmt.ciscoEpmNotificationMIB.ciscoEpmNotificationMIBObje
cts.cenAlarmData.cenAlarmTable.cenAlarmEntry.cenAlarmSeverityDefinition: 1,major
.iso.org.dod.internet.private.enterprises.cisco.ciscoMgmt.ciscoEpmNotificationMIB.ciscoEpmNotificationMIBObje
cts.cenAlarmData.cenAlarmTable.cenAlarmEntry.cenAlarmTriageValue: not applicable
.iso.org.dod.internet.private.enterprises.cisco.ciscoMgmt.ciscoEpmNotificationMIB.ciscoEpmNotificationMIBObje
cts.cenAlarmData.cenAlarmTable.cenAlarmEntry.cenEventIDList: not applicable
.iso.org.dod.internet.private.enterprises.cisco.ciscoMgmt.ciscoEpmNotificationMIB.ciscoEpmNotificationMIBObje
cts.cenAlarmData.cenAlarmTable.cenAlarmEntry.cenUserMessage1: not applicable
.iso.org.dod.internet.private.enterprises.cisco.ciscoMgmt.ciscoEpmNotificationMIB.ciscoEpmNotificationMIBObje
cts.cenAlarmData.cenAlarmTable.cenAlarmEntry.cenUserMessage2: not applicable
.iso.org.dod.internet.private.enterprises.cisco.ciscoMgmt.ciscoEpmNotificationMIB.ciscoEpmNotificationMIBObje
cts.cenAlarmData.cenAlarmTable.cenAlarmEntry.cenUserMessage3: not applicable
.iso.org.dod.internet.private.enterprises.cisco.ciscoMgmt.ciscoEpmNotificationMIB.ciscoEpmNotificationMIBObje
cts.cenAlarmData.cenAlarmTable.cenAlarmEntry.cenAlarmMode: INTEGER: 3
.iso.org.dod.internet.private.enterprises.cisco.ciscoMgmt.ciscoEpmNotificationMIB.ciscoEpmNotificationMIBObje
cts.cenAlarmData.cenAlarmTable.cenAlarmEntry.cenPartitionNumber: not applicable
.iso.org.dod.internet.private.enterprises.cisco.ciscoMgmt.ciscoEpmNotificationMIB.ciscoEpmNotificationMIBObje
cts.cenAlarmData.cenAlarmTable.cenAlarmEntry.cenPartitionName: not applicable
.iso.org.dod.internet.private.enterprises.cisco.ciscoMgmt.ciscoEpmNotificationMIB.ciscoEpmNotificationMIBObje
cts.cenAlarmData.cenAlarmTable.cenAlarmEntry.cenCustomerIdentification: not applicable
.iso.org.dod.internet.private.enterprises.cisco.ciscoMgmt.ciscoEpmNotificationMIB.ciscoEpmNotificationMIBObje
cts.cenAlarmData.cenAlarmTable.cenAlarmEntry.cenCustomerRevision: not applicable
.iso.org.dod.internet.private.enterprises.cisco.ciscoMgmt.ciscoEpmNotificationMIB.ciscoEpmNotificationMIBObje
cts.cenAlarmData.cenAlarmTable.cenAlarmEntry.cenAlertID: not applicable
Cisco Prime Collaboration Manager 1.2 User Guide
22-12
OL-26267-01