The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
You can view Alarms and Alarm Summary pages through .
The Alarms tab displays the following information for each alarm in the Alarm browser:
Indicates the severity of the alarm which can be, critical, major, minor, warning. The collapsible icon for an alarm displays the General Info of the alarm, Messages, Annotation, Recommended Actions for an alarm.
This summary windows lists only the five latest events. To see the complete list, see Event History.
Indicates the alarm has user notations.
Indicates the status of the alarm.
It shows the alarm clearing status details.
Name of the generated alarm. Rest the mouse over the alarm name and the Quickview icon that is displayed, to view details of the alarm selected.
If you have installed Cisco Prime Collaboration in MSP mode, the customer that the device belongs to, is displayed for both Alarms and Alarm Summary.
Displays the name of the device that triggered the alarm.
Displays the IP address of the device. You can launch the endpoint or the infrastructure device log in page using the link.
Device name, or the name of component such as a device pool, an interface.
Displays the date and time when the alarm occurred.
Displays the type of the device.
Displays the name of the person to whom this alarm is assigned. (If a name was entered.)
Displays a short description about the alarm.
Displays the category of alarm. For example: conference, endpoint, service infrastructure.
Indicates the name assigned to the endpoint for ease of identification. By default, the Endpoints Name column is hidden. To see all the columns, click the Settings option on the top right corner.
Displays the device model, such as ciscoEX90, ciscoCTS500, ciscoC20, and so on.
If you have installed Cisco Prime Collaboration in MSP mode, private IP address of the device is displayed. By default, the Private IP Address column is hidden. To see all the columns, click the Settings option on the top right corner.
View events associated with an alarm—Rest the mouse over the icon next to alarm status for the popup window to appear displaying all the events for the alarms.
Clear or acknowledge an alarm.
Assign the alarm—Check the desired check box, click Assign to me from the assign drop-down list.
Add Annotation—Check the desired check box, click the Annotate drop-down list to add notes.
Set up Email Notification—Check the desired check box, click Email Notification. Enter the recipient addresses, comments, and subject, then click Submit. See Supported Alarms and Events for Cisco Prime Collaboration for a list of supported alarms and events.
Alarm Summary provides a summary of the alarms for each device.
The following factor distinguishes Alarm Summary from Alarms: When you select a device, the alarms and events that correspond to the selections appear in the Alarms and Events for device pane at the bottom of the page. You can export the alarms as a CSV or PDF file. To export the alarms, select the desired alarms, and click the export icon on the top right of the Alarm Summary pane.
The Alarm Summary displays the following information:
Alarm severity icon. Indicates the severity of the alarm.
Indicates that this device is one of the most recent in the table (within the last 15 minutes). Devices are sorted based on the time of the most recent event status changes.
Device name or IP address.
Device IP. Click on the quick view icon to launch the Device 360° View.
Device type.
Time and date of alarm update (indicates activity, such as an alarm recurrence, alarm acknowledgment, the addition of a note, and so forth). Alarms are grouped by severity, and within severities, alarms with the latest change are listed first.
Indicates the name assigned to the endpoint for ease of identification. By default, the Endpoints Name column is hidden. To see all the columns, click the Settings option on the top right corner.
If you have installed Cisco Prime Collaboration in MSP mode, private IP address of the device is displayed. By default, the Private IP Address column is hidden. To see all the columns, click the Settings option on the top right corner.
Event unique identification number.
Event severities include: Critical, Major, Minor, Warning, and Informational. Click the title to sort the events list by severity (ascending or descending order). If any event is cleared, its severity changes to informational.
The current status of the event.
The name of the event. Rest your mouse over the quick view icon to view the event details. Click Customize Event to cross-launch to the Event Customization page, which displays the details of the selected event. Expand the event and click Custom Rule to edit the event details.
If you have installed Cisco Prime Collaboration in MSP mode, the customer that the device belongs to, is displayed in the Events pane.
The name of the event. Rest your mouse over the event name to view the event details.
Displays the IP address of the device. You can launch the endpoint or the infrastructure device using the link.
Device name, or the name of component such as a device pool, an interface.
Displays the date and time when the event occurred.
Displays the type of the device.
Displays the alarm assigned category, such as conferences, endpoints, and so on.
Description of the event.
Indicates the name assigned to the endpoint for ease of identification. By default, the Endpoints Name column is hidden. To see all the columns, click the Settings option on the top right corner.
Displays the device model, such as cat4506, ciscoMCS7828I, and so on.
If you have installed Cisco Prime Collaboration in MSP mode, the private IP Address of the device is displayed. By default, the Private IP Address column is hidden. To see all the columns, click the Settings option on the top right corner.
Cisco Prime Collaboration displays the Cisco TelePresence Management Suite (TMS) informational events. It displays call connected or disconnected information for Cisco TelePresence System Profile MXP Series devices, Cisco TelePresence Integrator C Series codecs, and Cisco TelePresence Video Communication Server (VCS).
Call events can be displayed for only one supported device at a time.
Alarms that are dependent on the polling interval, might have a situation where the alarm is raised and cleared before the next poll. Therefore, it is not being reported to Cisco Prime Collaboration Assurance.
Behaviour of SIPTrunk Out Of Service (OOS) Correlation Alarm :
SIP Trunk OOS : This correlation alarm is introduced to track and combine multiple SIPTrunk OOS Alarms and generate one single correlated Alarm at the Cluster level. Correlation happens in a span of 2 minutes time window.
Following are the conditions for the correlation alarms to get cleared :
SIPTrunk OOS Correlation alarm gets cleared when the associated individual SIPTrunk OOS alarms are cleared by processing InService Syslogs.
There is a time base clear as well, where the correlation alarms are cleared automatically after 24 hours.
Using the conditions mentioned above, correlation alarm is cleared in any one of the following scenarios :
Scenario 1:
SIPTrunk OOS alarms are raised in Cisco Prime Collaboration Assurance.
Individual SIPTrunk OOS alarms are correlated and Corresponding SIPTrunk OOS correlation alarm is raised at the cluster level.
SIPTrunk OOS gets cleared once the SIPTrunks are back and the SIPTrunk OOS also gets cleared with that.
Scenario 2:
SIPTrunk OOS alarms are raised in Cisco Prime Collaboration Assuarance.
Individual SIPTrunk OOS alarms are correlated and Corresponding SIPTrunk OOS correlation alarm is raised at cluster level.
SIPTrunk stays down for more than 24 hours.
SIPTrunk OOS gets cleared after 24 hours based on 24 hours time based clear and the SIPTrunk OOS individual alarms will clear once the SIPTrunk is back Inservice and syslog is processed for that.
Scenario 3 :
Individual SIPTrunk OOS alarms are raised and cleared rapidly within the 2 minutes correlation window.
Correlation engine will still run and raise the SIPTrunk OOS correlation alarm and now as the associated individual alarm has already cleared, the SIPTrunk OOS will be left alone.
Then the correlation alarm gets cleared automatically after 24 hours, based on 24 hours time based clear.