Cisco Prime Collaboration Assurance Guide - Advanced, 10.0
Customizing Alarms and Events
Downloads: This chapterpdf (PDF - 1.43MB) The complete bookPDF (PDF - 8.14MB) | Feedback

Customizing Alarms and Events

Contents

Customizing Alarms and Events

This section explains how to customize alarms and events to suit your business needs.

Configuring Thresholds

You can configure the devices to generate events when certain parameters cross pre-defined thresholds. These settings are to be done at Administration > Alarm & Event Configuration > Threshold Settings.

You can view and configure thresholds for:

  • TelePresence Endpoint
  • Infrastructure Device
  • Device Pool
  • RTMT Synchronization
  • Global Call Quality
  • Sensor Call Quality
  • CDR Call Quality

Prime Collaboration does not need to install the RTMT plug-in to poll the device data (for example, memory usage) through RTMT. Prime Collaboration uses the default settings for these events. If you want to configure the threshold settings for specific events, you must install the RTMT plug-in.

Configuring TelePresence Endpoint Thresholds—Global

You can set up Prime Collaboration to have events generated when the threshold value exceeds the configured limit for Rx packet loss, jitter, or latency.

To configure thresholds for TelePresence endpoints:


Note


The changes you make here applies to all TelePresence devices. See Configuring TelePresence Endpoint Threshold - Device Level for information about how to modify thresholds at a device-level for video endpoints.



    Step 1   Choose Administration > Alarm & Event Setup >Threshold Settings >Telepresence Device.
    Step 2   From the Threshold Settings drop down list, choose TelePresence Endpoints.
    Step 3   Click the row to edit the Average Period Jitter, Average Period Latency, or Rx Packet Loss.
    Step 4   Modify the values for Minor, Major, and Critical thresholds, then click Save.

    Configuring TelePresence Endpoint Threshold—Device Level

    You can configure the thresholds for TelePresence endpoints at a device level, if you do not want to have the thresholds to be applied at a global level.

    To do this:


      Step 1   Choose Operate > Device Work Center.
      Step 2   From the Device Groups pane, choose the video end point for which you need to modify the threshold.
      Step 3   Click Threshold Settings.
      Step 4   Check the check box corresponding to Average Period Jitter, Average Period Latency, or Rx Packet Loss, then click the row to enable editing.
      Step 5   Modify the values for Minor, Major, and Critical thresholds, then click Save.

      Enabling Automatic Troubleshooting for TelePresence Endpoints

      You can enable automatic troubleshooting of a session when the threshold value exceeds the limit, for packet loss, jitter, and/or latency.

      To enable automatic troubleshooting:


        Step 1   Choose Administration > Alarm & Event Configuration.
        Step 2   From the Threshold Settings drop down list, choose TelePresence Endpoints.
        Step 3   Check the check box corresponding to Average Period Jitter, Average Period Latency, or Rx Packet Loss, then click the row to enable editing.
        Step 4   From the drop down list under Automatic Troubleshooting, and choose from Minor, Major, or Critical, then click Save.

        To disable, choose Disable from the drop down list.


        Configuring Infrastructure Device Thresholds

        You can set up Prime Collaboration to generate alarms when devices cross the threshold you configure. When you configure thresholds, the values get associated with groups, not with individual devices, device pools, ports, or interfaces.

        To configure thresholds for a selected device group:


          Step 1   Choose Administration > Alarm & Event Configuration.
          Step 2   Choose Infrastructure Device.
          Step 3   Choose a device group for which you can set thresholds.

          Generally, this is a device group that does not contain subgroups.

          Step 4   Click the Edit button and enter the appropriate information in the Managing Thresholds: Edit dialog box.
          Step 5   Click Save.
          Step 6   Repeat Step 4 and Step 5 until you are done editing thresholds for the selected group.
          Caution   

          Your changes will be lost if you select another threshold category or parameter type before you click Save.

          Although the changes to polling parameters are saved in the database, they are not yet applied to the IP fabric.

          Step 7   Click Save, then click Apply.
          Step 8   In the confirmation message box, click Yes.

          Parameter Types, Device Groups, and Polling Settings

          This section provides information on polling settings for each parameter type:

          • Data Settings
          • Voice Health Settings
          • Voice Utilization Settings

          Data Settings—Polling

          Data settings enable you to poll for device reachability, environment, ports and interfaces, and processor and memory utilization. The following table lists all data settings and polling intervals for each setting.

          Data Polling Settings Intervals (in seconds) Usage Notes
          Access Port Settings
          • 30 minimum.
          • 3600 maximum.
          • 1200 default —You can adjust the default polling interval in 1-second increments.

          To enable polling for Access Port Settings, you must enable polling for Connector Port and Interface Settings.

          The same timeout and retry values are used for Access Port Settings and Connector Port and Interface Settings. When you update the timeout and retry value for either of these settings, polling updates the values for both.

          Customer Voice Portal devices have access port and connector port and interface settings disabled by default.

          Connector Port and Interface Settings
          • 60 minimum.
          • 3600 maximum.
          • 240 default —You can adjust the default polling interval in 1-second increments.
          Environment Settings

          Environment Settings and Processor and Memory Utilization Settings are not available for all device groups.

          Some voice-enabled device groups have similar settings available for Voice Health Settings parameter type.

          Processor and Memory Utilization Settings
          Reachability Settings

          Note


          Polling for voice-enabled ports and interfaces is controlled by voice health settings.


          Polling is enabled by default for user-defined groups.

          Voice Health Settings—Polling

          Voice health settings control polling for voice-enabled devices, device pools, ports, interfaces, and Cisco Unified Communications Applications. Data that is collected includes Cisco Unified CM cluster connectivity and processor and memory utilization on Media Convergence Servers (MCS) and on voice gateways. Voice health settings default polling intervals (in seconds) are:

          • Minimum:
            • 240—For clusters in the Cisco Unified Communications Manager or Cluster device group.
            • 30—For all other device groups.
          • Maximum—3600.
          • Default—240. You can adjust the default polling interval in 1-second increments.

          Note


          Polling is enabled by default for user-defined groups.


          Voice Utilization Settings—Polling

          Voice Utilization Settings control performance polling. Performance polling collects utilization and capacity planning data from supported devices.

          Performance polling is enabled by default.

          When performance polling is enabled, Prime Collaboration collects performance and capacity data that:
          • Is accessible from monitoring dashboards in the form of performance graphs.
          • Is stored in data files on disk for further analysis; for information about data files.
          • Is measured against Voice Utilization Settings thresholds.

          When thresholds are violated, Prime Collaboration generates events related to performance and capacity problems in an application, on an interface, or on a device.

          For example, high utilization of ports, channel, and resources of a device.

          Voice Utilization Settings default polling interval values (in seconds) are:

          • 60 minimum.
          • 3600 maximum.
          • 240 default —You can adjust the default polling interval in 1-second increments.

          The following table lists the types of ports and resources that are polled on each device group.

          Device Group Analog Ports Digital Ports Other Ports Resources
          CommunicationManager Express IP phone registered
          Cisco Unified Communications Manager or Cluster Location bandwidth
          Gatekeeper Total and Interzone bandwidth
          Media Server FXS FXO T1/E1 PRI, T1 CAS BRI Unity inbound and outbound CommunicationManager MOH Multicast/Unicast, MTP, Transcoder, HW/SW conference
          Meeting Place Audio/Video Port
          Unity Express Session, Capacity, Orphaned mailbox
          VoiceGateway FXS FXO E&M T1/E1 PRIT1/E1 CASBRI DSP
          VoiceMailGateway PBX, VM

          Customizing Infrastructure Device Threshold Settings

          You can selectively disable threshold settings, moving them from an active settings list to an inactive settings list. Prime Collaboration does not monitor threshold parameters for threshold settings that are on an inactive settings list.

          To customize infrastructure device threshold:


            Step 1   Choose Administration > Alarm & Event Configuration.
            Step 2   Choose Infrastructure Device from the Threshold Settings drop down list.
            Step 3   Choose a device group for which you can set thresholds.

            Generally, this is a device group that does not contain subgroups.

            Step 4   Click the Customize Settingsbutton.
            Step 5   To update the Active Settings list for a particular parameter type:
            1. Scroll to the parameter type and update the inactive and active settings lists.
            2. Scroll to the bottom of the window and click Save.

              To reset all parameter types with Prime Collaboration default settings:

            3. Click Revert to Default.
            4. Click Yes.
            5. Click Cancel to close the Managing Thresholds: Edit dialog box.
              Note   

              The settings are stored in the database, but not yet applied to the IP fabric.

            Step 6   Click Save, then click Apply.

            Overview of Device Pool Thresholds

            A device pool is a logical group of devices. Device pools provide a convenient way to define a set of common characteristics that can be assigned to devices, for example, the region in which the devices are located. You can view and edit device pool thresholds using Prime Collaboration.

            Within Prime Collaboration, device pools are displayed only after a cluster discovery is completed. If no device pools display in the thresholds window, schedule the inventory to run. By default, cluster device discovery is not scheduled.

            The device pool threshold settings in Prime Collaboration allow the user to configure the amount of aggregated events.

            • If you raise the default or current percentage settings for any of the device pool thresholds, you decrease the amount of aggregated events you will receive.
            • If you lower the default or current percentage settings for the device pool threshold, you will receive more aggregated events from this device pool.

            If the number of impacted phones is equal to the threshold value, Prime Collaboration raises one service quality event.

            For example, if the device pool contains 100 phones and 10 phones are impacted with a network problem, when the device pool threshold is set to 10% you will receive one aggregated event about this device pool.

            After an aggregated event is raised, no other aggregated events will be sent until this event is cleared. To clear an aggregated event, all individual device or service quality events must be cleared first.

            Prime Collaboration considers these device pool threshold events as device events and not service level events.

            Editing Device Pool Thresholds

            You can view and edit device pool thresholds using Prime Collaboration.

            To view or configure device pool thresholds:


              Step 1   Select Administration > Alarm & Event Configuration.
              Step 2   Select Device Pool from the Threshold Settings drop down list.

              If no device pools appear in this window, schedule the cluster inventory to run.

              Step 3   Click the check box next to the device pool you want to view or edit.
              Step 4   Click Edit.
              Step 5   To edit the current default thresholds:
              1. Select a group, change the default threshold, and click Edit.
              2. In the Phone Unregistration/Service Quality Thresholds dialog box edit the threshold% and click Update.

                To revert any settings back to the default settings, check a check box and click Revert to Default Settings.

                To reset all parameter types with Prime Collaboration default settings:

              3. Check the check box for All Device Pools/CMEs and click Revert to Default Settings.
              4. Click Yes.

                Although the changes are saved in the database, they are not yet applied to the IP fabric.

              Step 6   Click Save, then click Apply

              To be notified automatically when you receive this type of aggregated event, you can set up a notification to have an email sent when this event is raised. For details on how to set up a notification email, see Configuring Alarm and Event Notification section in Cisco Prime Collaboration 10.0 Assurance - Advanced.


              Restoring Default Device Pool Thresholds

              Use this procedure to reset the values of parameters in all active threshold settings in all threshold categories for a selected group. For information on active threshold settings, see Configuring Infrastructure Device Thresholds.

              To see default threshold values before you apply them, view the Thresholds report.

              To restore default thresholds:


                Step 1   Choose Administration > Alarm & Event Configuration.
                Step 2   Choose Device Pool from the Threshold Settings drop down list.
                Step 3   Click the Revert to Default Settings button.
                Step 4   Click Yes.

                The settings are stored in the database, but not yet applied to the IP fabric.


                Generating an RTMT Thresholds Report

                You can view real-time monitoring threshold (RTMT) parameters for Unified CM devices. You can export the RTMT thresholds report as a PDF or CSV file.

                To view RTMT Thresholds


                  Step 1   Choose Administration > Alarm & Event Setup > Threshold Settings > RTMT Synchronization.
                  Step 2   Choose a voice cluster for which you can view thresholds.
                  Step 3   Click the View button.

                  The thresholds report window opens and displays the following information for all clusters or Unified Communications Manager devices. The information is updated each hour.

                  Step 4   When you are done viewing the threshold report, close the window.

                  Synchronizing RTMT Thresholds

                  You can synchronize real-time monitoring tool (RTMT) threshold parameters for clusters and Unified CM devices. You may want to do this when you do not want to wait for the next scheduled polling.

                  To synchronize RTMT thresholds:


                    Step 1   Choose Administration > Alarm & Event Configuration.
                    Step 2   Choose RTMT Synchronization from the Threshold Settings drop down list.
                    Step 3   Click the Synchronize thresholds with RTMT now icon in the RTMT Threshold: Select Voice Cluster window to update the information in all clusters.

                    Synchronizing the thresholds with RTMT may take a few minutes to complete. There is no option to synchronize individual voice clusters.


                    Overview of Call Quality Thresholds and Threshold Groups

                    Prerequisite - To proceed with determination of MOS, you must have good knowledge of voice quality of calls. To know more about voice call quality, see the “Monitoring the Voice Quality of Calls” section in the Cisco Unified IP Phone Administration Guide for Cisco Unified Communications Manager.


                    Note


                    For information about configuring voice quality metrics for phones, refer to the "Phone Features" section in the "Cisco Unified IP Phone" chapter in Cisco Unified Communications Manager System Guide.

                    For more information on call quality grades calculated from MOS value, see Voice Call Quality Reports.

                    Prime Collaboration uses thresholds to determine when a MOS value—reported from a sensor or included in CDRs from a Unified Communications Manager cluster—has fallen to an unacceptable level. When MOS falls below a threshold, Prime Collaboration sends a QoVMOSViolation trap to up to four trap receivers.

                    Prime Collaboration supplies global thresholds and provides default values for them. Prime Collaboration can use global thresholds to compare against MOS values reported from sensors or clusters. Since the MOS threshold values might vary depending upon the codec being used in a call, global thresholds include separate values for commonly used codecs such as these:

                    • AAC
                    • G711Alaw 56k
                    • G711Alaw 64k
                    • G711Ulaw 56k
                    • G711Ulaw 64k
                    • G722 48k
                    • G722 56k
                    • G722 64k
                    • G722.1 24k
                    • G722.1 32k
                    • G723.1
                    • G726 16K
                    • G726 24K
                    • G726 32K
                    • G728
                    • G729
                    • G729AnnexA
                    • G729AnnexAwAnnexB
                    • G729AnnexB
                    • GSM
                    • GSM Enhanced Full Rate
                    • GSM Full Rate
                    • GSM Half Rate
                    • iSAC

                      Note


                      The iSAC codec applies to CVTQ data only.


                    • NonStandard

                      Note


                      For more information about codecs, see Understanding Codecs: Complexity, Hardware Support, MOS, and Negotiation at this URL: 
http://www.cisco.com/en/US/tech/tk1077/technologies_tech_note09186a00800b6710.shtml


                    You can update the global threshold default values to reflect MOS values below the average MOS seen in your system. By monitoring Prime Collaboration reports, you can determine average MOS values and then adjust global thresholds accordingly. You can also easily restore global thresholds to the default values that Prime Collaboration supplies.

                    If you would like to use different threshold values for particular sensors, clusters, or groups of endpoints reported on by either sensors or clusters, you can override global thresholds by adding these threshold groups:

                    • CDR Groups—A CDR group includes one or more clusters, two sets of endpoints, and one or more threshold values for commonly used codecs.
                    • Sensor Groups—A sensor group includes one or more sensors, two sets of endpoints, and one or more threshold values for commonly used codecs.

                    You can create up to ten CDR groups and up to ten sensor groups. CDR groups are prioritized from highest (one) to lowest (ten), as are sensor groups. In cases where an endpoint is included in more than one CDR group or more than one sensor group, Prime Collaboration compares MOS for the endpoint against the highest priority group that it belongs to.

                    Configuring Global Thresholds

                    Prime Collaboration compares MOS reported from sensors and clusters against global thresholds when no CDR group or sensor group setting is applicable. You cannot delete or clear global thresholds. You can update them and you can restore them to default values. You can override global thresholds by creating user-defined threshold groups; for more information, see Overview of CDR Threshold Groups and Overview of Sensor Threshold Groups.


                    Note


                    Grading is based on the global threshold settings only.


                    To configure global thresholds:


                      Step 1   Choose Administration > Alarm & Event Configuration.
                      Step 2   Choose Global Call Quality Settings from the Threshold Settings drop down list
                      Step 3   Enter a new current value for any codec in the table and click Apply.

                      Restoring Global Thresholds to Default Values

                      You can restore global threshold values to the suggested default values that are displayed on the Global Thresholds page.

                      To do this:


                        Step 1   Choose Administration > Alarm & Event Configuration.
                        Step 2   Choose Global Call Quality Settings from the Threshold Settings drop down list.
                        Step 3   Click Revert to Suggested Defaults.

                        Overview of CDR Threshold Groups

                        A CDR group includes one or more Unified Communications Manager clusters, two sets of endpoints, and threshold values for one or more commonly used codecs. You can define up to ten CDR Threshold groups; Prime Collaboration prioritizes the CDR threshold groups from 1 (highest priority) to ten (lowest priority), initially reflecting the order in which you create the groups. (You can reprioritize them.) If an endpoint belongs to more than one CDR threshold group, Prime Collaboration uses the thresholds for the highest priority CDR threshold group.

                        To configure threshold groups, choose Administration > Alarm & Events Setup > Thresholds > CDR Call Quality Settings. The CDR Call Quality Settings page displays up to ten user-defined CDR threshold groups.

                        Adding a CDR Threshold Group

                        When you add a CDR threshold group, it is assigned the lowest priority among existing CDR threshold groups. To adjust its priority, see Updating CDR Threshold Group Priority.


                        Note


                        You can add up to ten CDR threshold groups.



                          Step 1   Choose Administration > Alarm & Event Setup > Thresholds  > CDR Call Quality Settings.
                          Step 2   Click Add.
                          Step 3   Do the following to enter data for each of the fields:
                          1. Click icon
                          2. Enter the appropriate information.
                          3. Click OK.
                          Step 4   After you finish entering the data, click OK.

                          The CDR Threshold Group displays the newest CDR threshold group last in the list (in the lowest priority position).


                          Editing a CDR Threshold Group


                          Note


                          To change CDR threshold group priority, see (Please check ) Updating CDR Threshold Group Priority, page 14-9.



                            Step 1   Choose Administration > Thresholds  > CDR Call Quality Settings
                            Step 2   Choose a group and click Edit
                            Step 3   Do the following to enter data for each of the fields
                            1. Click image (insert)
                            2. Enter the appropriate information.
                            Step 4   Click OK

                            Updating CDR Threshold Group Priority

                            If the directory number or IP address for an endpoint is included in more than one CDR group, Prime Collaboration applies the thresholds for the highest priority CDR threshold group.


                              Step 1   Choose Administration > Thresholds > CDR Call Quality Settings. The CDR Threshold Group page appears, displaying up to 10 user-defined CDR threshold groups.
                              Step 2   Enter any unique numbers—up to two digits—in the Priority column.
                              Step 3   Click Update Priority. Prime Collaboration reorders the CDR threshold groups and displays them in priority order.

                              Deleting a CDR Threshold Group


                                Step 1   Choose Administration > Thresholds > CDR Call Quality Settings. The CDR Threshold Group page appears, displaying up to 10 user-defined CDR threshold groups.
                                Step 2   Check the check boxes for the CDR threshold groups that you want to delete.
                                Step 3   Click Delete.
                                Step 4   Click Yes. Prime Collaboration displays any remaining CDR threshold groups in priority order.

                                Overview of Sensor Threshold Groups

                                A sensor group includes one or more sensors, two sets of endpoints, and threshold values for one or more commonly used codecs. You can define up to ten sensor threshold groups; Prime Collaboration prioritizes the sensor threshold groups from one (highest priority) to ten (lowest priority), initially reflecting the order in which you create the groups. You can reprioritize them.

                                If an endpoint belongs to more than one sensor threshold group, Prime Collaboration uses the thresholds for the highest priority sensor threshold group.

                                Adding a Sensor Group

                                When you add a sensor group, it is assigned the lowest priority among existing sensor groups. To adjust its priority, see Updating Sensor Group Priority.


                                Note


                                You can add up to 10 sensor groups.



                                  Step 1   Choose Administration > Alarm & Event Configuration.
                                  Step 2   Choose Sensor Call Quality Settings from the Threshold Settings drop down list.
                                  Step 3   Click Add.
                                  Step 4   Do the following to enter data for each of the fields:
                                  1. Click icon
                                  2. Enter the appropriate information.
                                  3. Click OK.
                                  Step 5   After you finish entering the data, click OK.

                                  The Sensor Threshold Group page appears, displaying the new sensor group threshold group last in the list (in the lowest priority position).


                                  Editing a Sensor Group

                                  You can edit the details for a sensor threshold group you created.


                                  Note


                                  To change sensor group priority, see Updating Sensor Group Priority.


                                  To edit the details:


                                    Step 1   Choose Administration > Alarm & Event Configuration.
                                    Step 2   Choose Sensor Call Quality Settings from the Threshold Settings drop down list.
                                    Step 3   Choose a group and click the Edit link for a sensor group.
                                    Step 4   Do the following to enter data for each of the fields:
                                    1. Click icon
                                    2. Enter the appropriate information.
                                    3. Click OK.

                                    Updating Sensor Group Priority

                                    If a sensor is included in more than one sensor group, Prime Collaboration applies the thresholds for the highest priority sensor threshold group.


                                      Step 1   Choose Administration > Alarm & Event Configuration.
                                      Step 2   Choose Sensor Call Quality Settings from the Threshold Settings drop down list.

                                      The Sensor Threshold Group page appears, displaying up to 10 user-defined sensor groups.

                                      Step 3   Enter any unique numbers—up to two digits—in the Priority column.
                                      Step 4   Click Update Priority. Prime Collaboration reorders the sensor groups and displays them in priority order.

                                      Deleting a Sensor Group

                                      You can delete a sensor threshold group.

                                      To delete a sensor threshold group:


                                        Step 1   Choose Administration > Alarm & Event Configuration.
                                        Step 2   Choose Sensor Call Quality Settings from the Threshold Settings drop down list.

                                        The Sensor Threshold Group page appears, displaying up to 10 user-defined sensor groups.

                                        Step 3   Check the check boxes for the sensor groups that you want to delete.
                                        Step 4   Click Delete. A confirmation dialog box is displayed.
                                        Step 5   Click Yes. Prime Collaboration displays any remaining sensor groups in priority order.

                                        Overview of Event Flooding Control

                                        When Prime Collaboration detects a flood of active events, it can reduce the number of active events processed by enabling event flood control. After event flooding stops, the events that were temporarily not monitored are again processed by Prime Collaboration.

                                        To understand more about event flood control, see the following topics:

                                        Event Flooding Rules

                                        Prime Collaboration detects event flooding using the following rules. If any of the following occurs, it is considered an event flood.

                                        • For a specific device, the same event occurs X number of times in Y number of minutes. The X and Y values are preconfigured in the system and stored in the database. Each event name has its own values. For example, if an InsufficientFreeMemory event occurs for a device 2 times 16 minutes, then it is considered an event flood.
                                        • For a specific device, different types of events occur X number of times in Y number of minutes. The X and Y values are preconfigured in the system and stored in the database. The global setting for all devices is 1,000 events in 4 minutes.

                                        After an event flood is detected for a given event, the subsequent events are not monitored until the device rule indicates that the event flood has stopped. Flood control is performed only for active events. The other event states (Cleared, UserCleared, and Acknowledged) are not considered flooding.

                                        When the event flood is detected in Prime Collaboration, events get dropped and are logged in to the CSCOpx\log\CUOM\EPM\FloodDroppedEvents.log file.

                                        An example of an event that violates the event flood rule:

                                        2012|11:36:18.437|ERROR|Flood|EventBinder|EventFloodController|checkFlood|null|Minute:20762286 Received 28 in last 16 minutes. To suppress la-ccm-11.cisco.com^#!$la-ccm-11.cisco.comServerUnreachable
23 Jun 2012|11:36:18.437|ERROR|Flood|EventBinder|EPMPluginImpl|processEventFilteration|null|Flood has occurred for device = la-ccm-11.cisco.com, component= la-ccm-11.cisco.com, eventName= ServerUnreachable, state= Active

                                        An example of a dropped event:

                                        2012|12:16:03.984|ERROR|Event|EventBinder|EventBinder|processNormalizedEvent|null| Event Dropped for component: 172.25.109.221 ; Reason :-> Exceeded limit for eventStatus = Active

                                        Event Flood Logs

                                        When event flooding occurs, the following files in CSCOpx\log\cuom\EPM provide details about the events:

                                        1. FloodDroppedEvents.log—When events violate the flood control rules an entry appears in this file.
                                        2. EPMDroppedEvents.log—When the events are huge in number and exceed the product limits an entry appears in this file.
                                        3. ClearedDroppedEvents.log—When the events are huge in number, exceed the product limits, and are Cleared events that cannot be processed, an entry appears in this file.

                                        Adding Dynamic Syslogs

                                        Prime Collaboration enables you to add unsupported syslogs. You must get the exact syslog details from the device before you use the syslog in Prime Collaboration; for example, you must enter the exact syslog name. The syslog name you enter is taken as the event name.

                                        You can set the severity and the time by which the syslog must be cleared.

                                        We recommend that you do not add:

                                        • Syslogs that are likely to create an excessive load on Prime Collaboration due to a possible flood of syslogs.
                                        • More than 20 syslogs.

                                        To add syslogs:


                                          Step 1   Choose Administration > Alarm & Event Configuration > Event Customization.
                                          Step 2   Click Add Event.

                                          The New Event window opens. Enter the following:

                                          • Syslog Name
                                          • Event Description
                                          • Event Severity
                                          • Event Clear Interval
                                          Step 3   (Optional) Check the Raise Event for Each Occurrence check box.

                                          Use this option judiciously. Prime Collaboration raises an event for each syslog. If syslogs are raised with unique details each time, this will be a feasible option.

                                          Step 4   Click Add.

                                          You can:

                                          • Use the Edit option to change the event name, severity, and check or uncheck the Raise Event for Each Occurrence check box.
                                          • Customize the syslog name or event severity. To do this, go to the Event Customization page. See the Customizing Alarms and Events section in the Cisco Prime Collaboration 10.0 Assurance - Advanced Guide for details.

                                          Example

                                          In this example, Prime Collaboration raises an alarm for the syslog 12E800E, triggered from a Cisco Unified Intelligent Contact Management (ICM) Enterprise, when you stop or recycle the Cisco CTI OS server

                                          Enter the following values:

                                          • Syslog Name - 12E800E
                                          • Event Description - ICM Event
                                          • Event Severity - Critical
                                          • Event Clear Interval - 24

                                          This is an example for syslog message, which is raised when an endpoint that has previously registered with Cisco Unified Communications Manager has unregistered:

                                          <190>761628: Apr 21 2014 22:11:24.260 UTC : %UC_CALLMANAGER-6-EndPointUnregistered: %[Device name=SEP44E4D94499EE][Device IP address=10.17.196.34][Protocol=SIP][Device type=493][Device description=SEP44E4D94499EE - 70012][Reason Code=8][IPAddressAttributes=0][LastSignalReceived=SIPRegisterInd][CallState=70012-active10][App ID=Cisco CallManager][Cluster ID=cucm-sj-cluster1][Node ID=cucm-sj-sub1]: An endpoint has unregistered

                                          Here, the syslog name is EndPointUnregistered.

                                          Customizing Events—Global

                                          You can enable or disable events or change the event severity globally for all the devices you manage.


                                          Note


                                          The customizations you make here are applicable to all the devices.


                                          To do this:


                                            Step 1   Choose Administration > Alarm & Event Configuration > Event Customization.
                                            Step 2   Check the check box corresponding to the Event, then select the desired option from the toolbar.
                                            Step 3   Click Save.
                                            Note   

                                            The customizations you make here are applicable to all the devices.

                                            To restore default event state and severity, select the desired check box, and click Reset to Defaults.


                                            Customizing Events—Device Level

                                            You can customize the events at a device level if you do not want to modify the events for all the devices.

                                            To customize events at a device level,


                                              Step 1   Choose Operate > Device Work Center.
                                              Step 2   Select a device from Device Groups pane.
                                              Step 3   Click Customize Events.
                                              Note   

                                              Device level customization takes precedence over global settings.

                                              Step 4   Check the check box corresponding to the Event, then choose the desired option from the toolbar.
                                              Step 5   Click Save.

                                              Correlation Rules

                                              When an event is raised from connected devices, Prime Collaboration applies correlation rules. In the following table, for a device, when event A and event B (or a single event) occurs at a certain frequency within a specified time window, Prime Collaboration correlates these events and raises an alarm. The alarm is auto-cleared within 24 hours.

                                              For example, whenever a Utilization threshold value changes, Prime Collaboration generates a High Utilization event. If the High Utilization event occurs thrice within the 20 minute time interval, High Utilization Detected alarm is raised.

                                              The following are the predefined correlation rules in Prime Collaboration:

                                              Correlation Rule Events Attributes Used Correlated Alarm Number of Occurrences Time Window (Min)
                                              Call Throttling Detected
                                              • CPUPegging
                                              • Code Yellow
                                              • eventName
                                              • deviceId
                                              Call Throttling Detected 1 20
                                              Interface Flapping OperationallyDown
                                              • eventName
                                              • deviceId
                                              • ComponentName
                                              InterfaceFlapping 3 20
                                              HighUtilization Detected HighUtilization
                                              • eventName
                                              • ComponentName
                                              • deviceId
                                              Repeated HighUtilization 3 20
                                              Repeated Location Bandwidth Out Of Resource Occurrences LocationBW

                                              OutOfResources

                                              • eventName
                                              • deviceId
                                              • ComponentName
                                              Repeated Location Bandwidth Out of Resource 3 20
                                              WAN Link Outage Detected
                                              Note    This rule cannot be edited or deleted from UI.
                                              Unresponsive
                                              • eventName
                                              • XGS_VD_
                                              • OBJECT_
                                              • GRAPH
                                              Wan Link Outage Detected NA 10

                                              Note


                                              The last two rules listed in the table above are threshold rules. Alarms for these rules are raised when the "phone unregistered" and "service quality" threshold values exceed the permitted limit.


                                              Creating Custom Alerts

                                              You can create custom alerts and also include the threshold and alert trigger parameters. See Custom Alert Parameters for details about the parameters.

                                              To create custom alerts:


                                                Step 1   Choose Administration > Alarm & Event Setup > Event Customization > Threshold Rules.

                                                You can also add events directly from a custom dashboard that you created.

                                                Step 2   Click Add Event.
                                                Step 3   In the New Performance Counter Event Window:
                                                1. Specify the cluster and the server.
                                                2. Select the counter from the Available Counters drop-down list.
                                                3. Add a description and the recommended action. This is optional.
                                                4. Specify the threshold values, duration and frequency, and the schedule for monitoring.
                                                5. Click Save.

                                                Custom Alert Parameters

                                                Table describes the parameters you can specify for the custom alert.
                                                Setting Description
                                                Threshold
                                                 
                                                Check the check box and enter the value that applies.
                                                • Over—Check this check box to configure a maximum threshold that must be met before an alert notification is activated. In the Over value field, enter a value. For example, enter a value that equals the number of calls in progress.
                                                • Under—Check this check box to configure a minimum threshold that must be met before an alert notification is activated. In the Under value field, enter a value. For example, enter a value that equals the number of calls in progress.
                                                Note   

                                                Use these check boxes in conjunction with the Frequency and Schedule configuration parameters.

                                                Value
                                                 
                                                Click the radio button that applies.
                                                • Absolute—Choose Absolute to display the data at its current status. These counter values are cumulative.
                                                • Delta—Choose Delta to display the difference between the current counter value and the previous counter value.
                                                • Delta Percentage—Choose Delta Percentage to display the counter performance changes in percentage.
                                                Duration
                                                • Trigger alert only when value constantly...
                                                • Trigger immediately
                                                • Trigger alert only when value constantly...—If you want the alert notification only when the value is constantly below or over threshold for a desired number of seconds, click this radio button and enter seconds after which you want the alert to be sent.
                                                • Trigger immediately—If you want the alert notification to be sent immediately, click this radio button.
                                                Frequency
                                                • Trigger on every poll
                                                • Trigger <> events within <> minutes
                                                Click the radio button that applies.
                                                • Trigger on every poll—If you want the alert notification to activate on every poll when the threshold is met, click this radio button. For example, if the calls in progress continue to go over or under the threshold, the system does not send another alert notification. When the threshold is normal (between 50 and 100 calls in progress), the system deactivates the alert notification; however, if the threshold goes over or under the threshold value again, the system reactivates alert notification.
                                                • Trigger <> events within <> minutes—If you want the alert notification to activate at certain intervals, click this radio button and enter the of alerts that you want sent and the number of minutes within which you want them sent.
                                                Schedule
                                                • Trigger immediately (Non-stop monitoring
                                                • Schedule between <> to <>
                                                Click the radio button that applies:
                                                • Trigger immediately (Non-stop monitoring)—If you want the alert to be triggered 24 hours a day, click this radio button.
                                                • Schedule between <> to <>—If you want the alert notification activated within a specific time frame, click the radio button and enter a start time and a stop time. If the check box is checked, enter the start and stop times of the daily task. For example, you can configure the counter to be checked every day from 9:00 am to 5:00 pm or from 9:00 pm to 9:00 am.