Cisco Prime Collaboration Assurance Guide - Standard, 10.5

Transcription

1 Last Modified: May 09, 2014 Americas Headquarters Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA USA Tel: NETS (6387) Fax: Text Part Number: OL

2 2014 Cisco Systems, Inc. All rights reserved.

3 PART I Introduction Overview of Cisco Prime Collaboration Assurance, page 3 Concepts, page 15

4

5 CHAPTER 1 Overview of Cisco Prime Collaboration Assurance Cisco Prime Collaboration is a comprehensive video and voice service assurance and management system with a set of monitoring, troubleshooting, and reporting capabilities that help ensure end users receive a consistent, high-quality video and voice collaboration experience. Prime Collaboration is available in the following flavors: Advanced Mode - It enables you to choose between the Enterprise and Managed Service Provider (MSP) modes. For more information, see Enterprise and Managed Service Provider (MSP) Modes. Standard Mode - It supports only the Enterprise mode. Prime Collaboration Standard Features, page 3 Standard and Advanced Prime Collaboration Assurance, page 4 Device Inventory Management in Standard, page 13 Monitoring and Fault Management in Standard, page 13 What's New in Prime Collaboration Assurance Standard, page 14 Device Support in Prime Collaboration Assurance Standard, page 14 Prime Collaboration Standard Features Prime Collaboration Standard provides basic assurance features that help you manage Unified Communications 10.0 and TelePresence components. You can monitor only one cluster per product for a single installation of Prime Collaboration Standard. The features include: Support for Unified Communications 10.0 components including Cisco Unified CM, Unity Connection, and Cisco IM and Presence Fault monitoring for core Unified Communications 10.0 components (Unified CM 10.0, Unity Connection 10.0) Pre-canned and customizable performance metrics dashboards that display term trends for core Unified Communications 10.0 components OL

6 Standard and Advanced Prime Collaboration Assurance Support for TelePresence components including Cisco TelePresence Management Suite (TMS), Cisco TelePresence Video Communication Server (Cisco VCS), Cisco TelePresence MCU, TelePresence Server, Cisco TelePresence System MXP Series, and Cisco TelePresence Conductor Contextual cross launch of serviceability pages of Unified Communications 10.0 components Single-level RBAC. Support for Single sign-on Standard and Advanced Prime Collaboration Assurance Prime Collaboration Assurance is available in the following flavors: Prime Collaboration Assurance Standard - Enterprise mode Prime Collaboration Assurance Advanced - Enterprise and MSP mode Prime Collaboration Assurance Standard is a simplified version of Prime Collaboration Assurance Advanced. It provides basic assurance features that help you manage Unified Communications 10.0 and TelePresence components. You can monitor only one cluster per product for a single installation of Prime Collaboration-Standard. For installing Standard and Advanced Assurance, see the Cisco Prime Collaboration 10.5 Quick Start Guide. Prime Collaboration Advanced Assurance is a comprehensive video and voice service assurance and management system with a set of monitoring, troubleshooting, and reporting capabilities that help ensure you receive a consistent, high-quality video and voice collaboration experience. The table below lists the features available in Prime Collaboration Assurance Standard and Advanced. Feature Standard Advanced See Cisco Prime Collaboration Assurance Guide - Advance Supported Modes It supports Enterprise mode only. It supports both the Enterprise and MSP modes. For more information on Advanced features see the section Enterprise and Managed Service Provider modes - Prime Collaboration Assurance Advanced. License Requirement Does not require a license. Requires license after evaluation expiry. For more information on Advanced features see the section Managing Licenses. 4 OL

7 Standard and Advanced Prime Collaboration Assurance Role Based Access Control Supports Super Administrator role only. Supports five roles to provide multiple levels of authorization: Super Administrator System Administrator Network Administrator Operator Helpdesk For more information on Advanced features see the section Managing Users. Single Sign-On Support Yes Yes For more information on Advanced see the section Managing Users. Cluster Management Manages only one cluster of Cisco Unified Communications Manager, one cluster of Cisco Unity and Cisco IM and Presence.. Manages multiple clusters with mixes of cluster revisions and cluster associations. For more information on Advanced features see the section Setting Up Clusters. OL

8 Standard and Advanced Prime Collaboration Assurance Discovery You can discover and manage endpoints that are registered to Cisco TMS and Cisco VCS. You can add and manage Cisco Unified Communications Manager (including Cisco Unified IM and Presence)10.x and Cisco Unity Connection 10.x applications. You can discover and manage all endpoints that are registered to Cisco Unified Communications Manager (phones and TelePresence), Cisco VCS (TelePresence), CTS-Manager (TelePresence) and Cisco TMS (TelePresence). In addition to managing the endpoints, you can also manage multipoint switches, application managers, call processors, routers, and switches that are part of your voice and video collaboration network. Provides multiple discovery modes such as Auto Discovery, Import, and Add Device features. Supports Logical Discovery, Ping Sweep, CDP-based discovery for discovering devices. Provides the option to perform rediscovery. For more information on Advanced features see the section Discovering Devices. 6 OL

9 Standard and Advanced Prime Collaboration Assurance Inventory Management Provides limited inventory information via the Current Inventory Table. Provides a concise summary information for a device through the Device 360 view. For more information on Advanced features see the section Managing Inventory. Provides exhaustive Inventory details. Fault Management Provides an Alarms and Events browser. Supports setting up notifications for Alarm Sets. Supports creation of custom events for Unified Communications Performance Counters. Supports set up of custom alerts based on selected metrics and corresponding thresholds. Once a threshold is violated, an alert is seen in the alarm browser. Support for initiating troubleshooting via quick views. Supports Alarm Correlation rules. Supports Alarm Correlation rules. Supports customization of events at the device, and global level. Provides configuration of thresholds for: TelePresence Endpoints Infrastructure Device Call Quality Device Pool For more information on Advanced features see the section Monitoring Alarms and Events. OL

10 Standard and Advanced Prime Collaboration Assurance Voice and video Reports NA Provides the following predefined reports and customizable reports: Cisco Unified Communications Manager /Cisco Unified Communications Manager Express Phone Inventory Reports For more information on Advanced features see the section Dashboards and Reports. Voice Call Quality Event History Reports Voice Call Quality Reports TelePresence Reports Cisco Unified Communications Manager /Cisco Unified Communications Manager Express Activity Reports Administrative Reports 8 OL

11 Standard and Advanced Prime Collaboration Assurance Dashboards Provides predefined dashboards for Cisco Unified Communications Manager, IM and Presence, and Cisco Unity Connection. Supports creation of custom dashboards based on the desired performance counters for Cisco Unified Communications Manager, IM and Presence, and Cisco Unity For more information on Advanced features see the section Dashboards and Reports. OL

12 Standard and Advanced Prime Collaboration Assurance Provides the following dashboards: End-Users Impact - Information about sessions and alarms. Endpoints Utilization - Information about endpoints and their utilization. Infrastructure - Information about conferencing devices, management devices, call and session devices, and video ports. Topology - This dashboard provides a logical top-level view of your IP telephony network. This view focuses on call control relationships. You can add customized dashboards in the home page. You can also do the following: Add the existing dashlets to a 10 OL

13 Standard and Advanced Prime Collaboration Assurance different dashboard. Move the dashlets around under a dashboard by dragging and dropping them. Voice and Video Endpoint Diagnostics NA Provides a detailed analysis of the end-to-end mediapath, including specifics about endpoints, service infrastructure, and network-related issues. Uses Cisco Medianet technology to identify and isolate video issues. Provides mediapath computation, statistics collection, and synthetic traffic generation. Uses the IP SLA to monitor the reachability of key IP phones in the network. Predicts service outage using scheduled synthetic and IP SLA tests For more information on Advanced features see the section Performing Diagnostics. Job Management Enables to view job status. Enables to view, schedule and delete jobs. For more information on Advanced features see the section Managing Jobs. Cross Launch to UC Application Yes Yes - OL

14 Standard and Advanced Prime Collaboration Assurance Device Search UC Cluster Components Search and Status Capability - Enables to define the search criteria to select specific cluster components, such as phones, H.323 gateways, Computer Telephony Integration (CTI) devices, voice mail devices, media resources, SIP trunks, or hunt lists that are associated with a Cisco Unified Communications Manager cluster. Global Search - Provides filtered search for TelePresence, endpoints, phones, other devices, locations, and users. For more information on Advanced features see the section Global Search Options for Prime Collaboration Assurance. Prime Collaboration Analytics NA Helps you to identify the traffic trend, technology adoption trend, over utilized resources, and under utilized resources in your network. You can also track intermittent and recurring network issues and address service quality issues using the Analytics Dashboards. The Analytics dashboards are: Technology Adoption Asset Usage Traffic Analysis Capacity Analysis Service Experience Prime Collaboration Analytics is a licensed software, which has to be purchased separately with Prime Collaboration Assurance. See Cisco Prime Collaboration 10.5 Analytics Guide. 12 OL

15 Device Inventory Management in Standard NB API NA NB API is supported for the following: Managing devices Viewing and deleting device credentials Listing all video sessions Troubleshooting video sessions To access the NB API documentation, log in to the Prime Collaboration Assurance server with the administrator privilege and enter htp:/<pc-server-ip>/emsam/nbi/nbidocumentation in the browser URL. Where, pc-service-ip is the Prime Collaboration Assurance server IP address. Device Inventory Management in Standard You can add and monitor Cisco Unified Communications Manager (phones and TelePresence), Cisco VCS (TelePresence), CTS-Manager (TelePresence) and Cisco TMS (TelePresence). As part of the discovery, the device details are also retrieved and stored in the Prime Collaboration database. After the discovery is complete, you can perform the following device management tasks: Add or remove Cisco Unified CM or Cisco Unity Connection Manage device credentials. This applies to Cisco TMS and associated devices only Discover devices. This applies to Cisco TMS and associated devices only Monitoring and Fault Management in Standard Service operators need to quickly isolate the source of any service degradation in the network for all voice and video sessions in an enterprise. Prime Collaboration provides a detailed analysis of the service infrastructure, and network-related issues. Prime Collaboration periodically imports information from the managed devices based on the polling parameters you configure. The Home page includes several pre-canned dashlets that help you monitor system performance, device status, device discovery, CTI applications, and voice messaging ports. These dashlets enable you to monitor a set of predefined management objects that monitor the health of the system. From the dashlets you can launch contextual serviceability pages. Prime Collaboration ensures near real-time quick and accurate fault detection. Prime Collaboration allows to monitor the events that are of importance to you. You can set up Prime Collaboration to send notifications for alarms. In addition to the faults that are present in the Cisco TelePresence Management System and Unified Communications applications, it also displays the custom tickets that are raised on Cisco TMS. OL

16 What's New in Prime Collaboration Assurance Standard Using the Alarm browser, you can view the alarms and events in the system. You can also configure Prime Collaboration to send fault notifications. You can also view call connection/disconnection details related to the Cisco TMS applications, in the Call Events UI. What's New in Prime Collaboration Assurance Standard Cisco Prime Collaboration Assurance - Standard provides the following new features: Troubleshooting Enables you to collect logs of Unified Communications components for troubleshooting. See Collecting Logs From Unified Communications (UC) Components. Provides analysis and visualization of call signaling for quicker isolation of faults in the call. See Analyzing Call Signaling. Customizing Alarms and Events Enables you to add thresholds for events. In the Basic tab, you can only create thresholds, based on the device type. In the Advanced tab, you can create events and also add rules for the thresholds that you create. See Threshold Rules, on page 59. Device Support in Prime Collaboration Assurance Standard Prime Collaboration Assurance Standard supports the following devices: Cisco Unified Communications Manager (version 10.0 and later) Cisco Unity Connection (version 10.0 and later) Cisco IM and Presence (version 10.0 and later) Cisco TelePresence System Codec C Series Cisco E20 IP Video Phone Cisco TelePresence ISDN Link Cisco TelePresence MCU Cisco TelePresence System MXP Series Cisco TelePresence Management Suite (TMS) Cisco TelePresence Server Cisco TelePresence Conductor Cisco TelePresence Video Communication Server (VCS) See Supported Devices for Cisco Prime Collaboration Assurance 10.5 for the details about the supported versions of these devices. 14 OL

17 CHAPTER 2 Concepts This chapter explains the concepts that are key to Prime Collaboration. Note Some of the concepts like alarm correlation rules are not applicable to Prime Collaboration Standard mode. See Standard and Advanced Prime Collaboration Assurance, on page 4for information about feature support in Standard and Advanced modes. Event, page 15 Event Creation, page 16 Alarm Creation, page 17 Event and Alarm Association, page 17 Event and Alarm Correlation, page 18 Event Aggregation, page 18 Event Masking, page 19 Alarm Status, page 19 Event Severity, page 20 Event and Alarm Database, page 20 Alarm Notifications, page 20 Event An event is a distinct incident that occurs at a specific point in time. An event is a: Possible symptom of a fault that is an error, failure, or exceptional condition in the network. For example, when a device becomes unreachable, an Unreachable event is triggered. Possible symptom of a fault clearing. For example, when a device state changes from unreachable to reachable, an event is triggered. OL

18 Event Creation Examples of events include: Port status change Node reset Node becoming reachable for the management station Connectivity loss between routing protocol processes on peer routers Events are derived from incoming traps and notifications, detected status changes (by polling), and user actions. It is important to understand that an event, once it occurs, does not change its status even when the conditions that triggered the event are no longer present. Event Creation Cisco Prime Collaboration Assurance maintains an event catalog and decides how and when an event has to be created and whether to associate an event with an alarm. Multiple events can be associated to the same alarm. Cisco Prime Collaboration Assurance discovers events in the following ways: By receiving notification events and analyzing them; for example, syslog and traps. By automatically polling devices and discovering changes; for example, device unreachable. By receiving events when the status of the alarm is changed; for example, when the user clears an alarm. Cisco Prime Collaboration Assurance allows you to disable monitoring of events that may not be of importance to you. The events that are disabled will not be listed in the Alarms and Events browser. Also, Cisco Prime Collaboration Assurance will not trigger an alarm. Incoming event notifications received as syslogs or traps are identified by matching the event data to predefined patterns. An event is considered supported by Cisco Prime Collaboration Assurance if it has matching patterns and can be properly identified. If the event data does not match with predefined patterns, the event is considered as unsupported and it is dropped. The following table illustrates the Cisco Prime Collaboration Assurance behavior while it deals with event creation: Time 10:00AM PDT June 7, :30AM PDT June 7, :45AM PDT June 7, :00AM PDT June 7, 2012 Event Device A becomes unreachable Device A continues to be in the unreachable state. Device A becomes reachable. Device A stays reachable Cisco Prime Collaboration Assurance Behavior Creates a new Unreachable event on device A. No change in the event status. Creates a new Reachable event on device A. No change in the event status. 16 OL

19 Alarm Creation Time 12:00AM PDT June 7, 2012 Event Device A becomes unreachable. Cisco Prime Collaboration Assurance Behavior Creates a new Unreachable event on device A. Alarm Creation An alarm represents the life cycle of a fault in a network. Multiple events can be associated with a single alarm. An alarm is created in the following sequence: 1 A notification is triggered when a fault occurs in the network. 2 An event is created, based on the notification. 3 An alarm is created after checking if there is no active alarm corresponding to this event. An alarm is associated with two types of events: Active events: Events that have not been cleared. An alarm remains in this state until the fault is resolved in a network. Historical events: Events that have been cleared. An event changes its state to an historical event when the fault is cleared. See Alarm Status to know how an alarm is cleared. The alarm life cycle ends after an alarm is cleared. A cleared alarm can be revived if the same fault recurs within a preset period of time. For Prime Collaboration, the preset period is 60 minutes. Event and Alarm Association Prime Collaboration maintains a catalog of events and alarms. The catalog contains the list of events managed by Prime Collaboration, and the relationship among the events and alarms. Events of different types can be associated to the same alarm type. When a notification is received: 1 Prime Collaboration compares an incoming notification against the event and alarm catalog. 2 Prime Collaboration decides whether an event has to be raised. 3 If an event is raised, Prime Collaboration decides whether the event should trigger a new alarm or associate it to an existing alarm. A new event is associated with an existing alarm, if the new event triggered is of the same type and occurs on the same source. An active interface error alarm is an example. All interface error events that occur on the same interface, are associated to the same alarm. If any event is cleared, its severity changes to informational. OL

20 Event and Alarm Correlation Note Some events have default severity as informational. For these events, alarms will not be created. If you want Prime Collaboration to create alarms for these events, you must change the severity of these events. Event and Alarm Correlation Event correlation is the process of relating one event to other events. Prime Collaboration distinguishes two event relationship types: An event sequence. Events that have the same type and the same source are considered part of an event sequence, or an alarm. An alarm represents the complete lifecycle of a fault. An event sequence hierarchy (alarms), representing causality. Prime Collaboration associates a new event to an existing alarm if the existing alarm has the same event type and source as the new event. Prime Collaboration raises an alarm, if the number of related events received (by fault management system) from the device element exceeds a specified threshold in a specified unit of time, based on predefined correlation rules. Example use cases: Call Manager location goes out-of-resource for more than five times over the last one hour. CPU usage of a device is over 80% for the last 15 minutes. You can modify these rules and configure the number of event occurrences to set the trigger. This can vary from two to 100. You can also set the time interval. You can modify these rules at Administration > Alarm & Event Configuration > Rules Settings. If an administrator does not specify a time interval, maximum time period, or a count for a specific alarm, the default values for the time interval, maximum time period, and count is attached on an alarm, device type, or device class basis. Event Aggregation If the number of same event received from a set of elements exceeds a specified threshold, Prime Collaboration creates an alarm. Example use cases: Number of unregistered phones on a device pool / Unified CM location is more than 5%. Number of service quality issues experienced on a device pool / Unified CM location is more than 5% All the call quality events raised against a single poor-quality call are grouped. 18 OL

21 Event Masking Event Masking Prime Collaboration automatically masks the hierarchy of events when the top-level component is the cause for the issue, and raises an alarm against the top level component while masking all the downstream events. Example use cases: When a Call Manager goes down, Prime Collaboration masks all its component (such as powersupply, interface, fan) events. When a switch card goes down, Prime Collaboration masks all the contained port level events. Alarm Status The following are the supported statuses for an alarm: Table 1: Alarm Status Status Not Acknowledged Acknowledged Cleared Description When an event triggers a new alarm or an event is associated with an existing alarm. When you acknowledge an alarm, the status changes from Not Acknowledged to Acknowledged System-clear from the device The fault is resolved on the device and an event is triggered for the same. For example, a device-reachable event clears the device-unreachable alarm. Alarms are also triggered during the session because of packet loss, jitter, and latency. These alarms are auto-cleared after the session ends. Manual-clear from Prime Collaboration users: You can manually clear an active alarm without resolving the fault in the network. A clearing event is triggered and this event clears the alarm. If the fault continues to exist in the network, a new event and alarm are created subsequently based on the polling. Auto-clear from the Prime Collaboration server Prime Collaboration clears all session-related alarms, when the session ends. If there are no updates to an active alarm for 24 hours, Prime Collaboration automatically clears the alarm. Note Certain alarms might get cleared automatically before 24 hours. See Supported Events and Alarms for Prime Collaboration. OL

22 Event Severity Event Severity Each event has an assigned severity, and can be identified by its color in Prime Collaboration. Events fall broadly into the following severity categories: Flagging Indicates a fault: Critical (red), Major (orange), Minor (yellow), or Warning (sky blue). Informational Info (blue). Some of the Informational events clear the flagging events. In a sequence of events, the event with the highest severity determines the severity of the alarm. Prime Collaboration allows you to customize the settings and severity of an event. The events that are of importance to you can be given higher severity. See the Customizing Events and Alarms section to know how to customize the event settings. The event settings and severity predefined in the Prime Collaboration application is used if you have not customized the event settings and severity. Event and Alarm Database All events and alarms, including active and cleared, are persisted in the Prime Collaboration database. The relationships between the events are retained. The Alarm and Event Browser lets you review the content of the database. The purge interval for this data is four weeks. Note Events are stored in the form of the Prime Collaboration event object. The original notification structure of incoming event notifications (trap or syslog) is not maintained. Alarm Notifications Prime Collaboration allows you to subscribe to receive notifications for alarms. Prime Collaboration sends notifications based on user-configured alarm sets and notification criteria. See the Configuring Alarm and Event Notifications section for details about how to configure for notifications. 20 OL

23 PART II Setting Up the Server Managing Users, page 23 Configuring System Parameters, page 33 Integrating Prime Collaboration Servers, page 37

24

25 CHAPTER 3 Managing Users Prime Collaboration supports creation of user roles. A user can be assigned the Super Administrator role. A Super Administrator can perform tasks that both system administrator and network administrator can perform. Prime Collaboration is preconfigured with a default web client administrator user called globaladmin; globaladmin is a superuser who can access both the Prime Collaboration Assurance UIs. Specify a password for globaladmin when you configure your virtual appliance. You need to use these credentials when you launch the Prime Collaboration web client for the first time. Prime Collaboration Assurance servers support these CLI users: admin and root. You cannot create CLI users using the web client UI. CLI users are created during OVA configuration. By default, the username is admin; the password is specified during OVA configuration and is used to log into the CLI to check the application status and perform backup and restore. Caution We recommend that you write down the root password as it cannot be retrieved. CLI users are not listed on the Prime Collaboration User Management page. globaladmin and root follow same set of password validation rules, but the rules for admin are different. See the Cisco Prime Collaboration 10.5 Quick Start Guide for password validation rules for these users. Prime Collaboration Provisioning User Roles, page 23 Adding, Editing, and Deleting a User, page 26 Configuring an LDAP Server, page 26 Resetting Prime Collaboration Assurance Passwords, page 28 Changing Passwords, page 29 Single Sign-On for Prime Collaboration, page 29 Prime Collaboration Provisioning User Roles Two types of global Provisioning user roles are available: global and domain specific. OL

26 Prime Collaboration Provisioning User Roles The global Provisioning user is typically an IP telephony expert who configures Prime Collaboration Provisioning business abstractions for voice applications. The domain-specific Provisioning user can be an administrator for a single domain but can be a user for multiple domains. The user roles for Prime Collaboration Provisioning are explained in Table 2: Authorization Roles. Table 2: Authorization Roles Authorization Role Global Roles Administration Maintenance Description Has access to all Provisioning functionality. Authorized to configure system cleanup activities. See Maintenance Mode. See Cisco Prime Collaboration Provisioning Guide, Roles for Domain In the drop-down list, select the Domain for which you are setting the authorization roles. The selected roles only apply to the selected Domain. To apply the same authorization role to all available domains, select Apply to all domains. Note Policy If the administrator selects Apply to all domains, existing roles of the user in all the domains will be overridden with the current selection. Authorized to view phone button templates, modify user roles, and add or update phone inventory. Infrastructure Configuration Management Permission Profiles Authorized to provision infrastructure configuration objects. When you select this role, you must also select a profile from the Permission Profile box. Sets the permissions for which infrastructure configuration object users assigned this authorization role can configure. (For information on setting permissions, see Cisco Prime Collaboration Provisioning Guide, SelfCare User Authorized to manage his own services; set up lines, manage services, and configure phone options quickly and easily. Note In the standalone Prime Collaboration Provisioning application, you can enable or disable Self-Care while adding both users. The Self-Care check box is not available while adding users. However, after creating a user, you can assign Self-Care role from the Manage User page. See Cisco Prime Collaboration Provisioning Guide, Ordering Roles Users assigned these roles are allowed to place orders for other users and themselves. 24 OL

27 Prime Collaboration Provisioning User Roles Authorization Role Ordering Description Authorized to: Add, delete, or update a user within a Domain. Add, delete, or update a user role within a Domain (if the rule for that Domain permits it). Add, delete, or update phones in the inventory within a Domain (if the rule for that Domain permits it). Search and view detailed user information within a Domain. Place an order for a user within a Domain. Advanced Ordering Advanced Assignment Authorized to access all the functionality specified by the Ordering role; can also access Advanced Order Options in the Order Entry page. Authorized to access all the functionality specified by the Ordering role, and to assign the MAC address for a phone product at the time of order entry. Activity Roles Users assigned one of these roles can perform activities assigned to the group during order processing. Approval Assignment Shipping Receiving Authorized to accept and complete the approval for orders. Authorized to accept the user activity for assigning the MAC address. Authorized to accept and complete shipping of orders. Authorized to accept and complete receiving of orders. Note globaladmin and domain admin can create Self-Care roles for any user. Self-Care role can be assigned to a user from the Manage Users page in the standalone Prime Collaboration Provisioning only. For more information, see "Creating a Self-Care Account" in the Cisco Prime Collaboration Provisioning Guide, In the converged mode, you cannot import a user associated with a Self-Care role into the Prime Collaboration Assurance application. The Managing Subscribers and Users chapter in Cisco Prime Collaboration Provisioning Guide, 10.5 provides detailed information on how to manage users. OL

28 Adding, Editing, and Deleting a User Adding, Editing, and Deleting a User You can add a user and assign the predefined static role. The user will have access to the Prime Collaboration web client only. If you are logging in for the first time to the Prime Collaboration Assurance, log in as globaladmin. You, as a globaladmin, must create other administrators using real user-ids. Caution You must not create a user with the name: globaladmin, pmadmin and admin. To add a user: Step 1 Step 2 Step 3 Step 4 Step 5 Choose Administration > User Management. On the User Management page, click Add. In the Add User window, enter the required user details. Select the role. Click Save. The users thus created via Add User feature are associated with the web client only and cannot log in to the Prime Collaboration Assurance server through the CLI. To edit user details, select a user at Administration > User Management and make the necessary changes. As part of your regular system administration tasks, you sometimes must delete users from the Prime Collaboration database. However, you cannot delete the Prime Collaboration web client default administrator globaladmin. To delete a user, select the user from Administration > User Management and click Delete. Any jobs that are scheduled in the deleted user name continue to run until canceled. Configuring an LDAP Server You can configure Prime Collaboration to connect to a Lightweight Directory Access Protocol (LDAP) server, to access user information stored in the LDAP server. In converged mode, the LDAP server specified in Prime Collaboration Assurance is used for authentication only; authorization and role-based access control (RBAC) functions are performed by Prime Collaboration. You must create an LDAP user from the User Management page to enable the user to log in using LDAP credentials. To add a user, see Adding a user and to edit or delete a user, see Modifying User Roles. Prime Collaboration supports one primary LDAP server and one backup LDAP server. To configure LDAP server: Step 1 Step 2 Choose Administration > System Setup > Assurance Setup > LDAP Settings. In the LDAP Settings page, enter values for all the fields. See LDAP Configuration Parameters for the field descriptions. 26 OL

29 Configuring an LDAP Server Step 3 Step 4 Note If Prime Collaboration must use SSL encryption, check the Use SSL check box and specify port 636. Click Test Connection to check the connectivity to the LDAP server. Upon successful connection, click Apply Settings and restart Prime Collaboration Assurance server to log in using LDAP. To restart Prime Collaboration Assurance Server, log in as admin user and execute the following commands: application stop cpcm application start cpcm The application stop cpcm command takes 10 minutes to complete execution and application start cpcm takes 10 to 15 minutes to complete execution. LDAP Configuration Parameters Table 3: LDAP Server Configuration Field Server IP address Description Enter the LDAP server name or IP address. Optionally enter the Backup LDAP server IP address. OL

30 Resetting Prime Collaboration Assurance Passwords Field Server Port Admin Distinguished Name Description Enter the Port number on which the LDAP requests for the server is received. Non-secure port: 389 Secure SSL port: 636 Optionally enter the Backup LDAP server Port number. Note If the LDAP server is configured to use a non-standard port, that port should be entered here as well. Admin Distinguished Name is the distinguished name to use. For example in the preceding image there is a user whose name is John Doe in the LDAP directory, so the Admin Distinguished Name will be as follows: CN = John Doe OU = Campus OU = AdminBLR OU = ABC DC = eta DC = com Admin Password LDAP User Search Base Enter the password for the LDAP server authentication and reconfirm the password. Enter the user search base. LDAP server searches for users under this base. Search Base is as follows: DC = eta DC = com Note LDAP authentication fails if you enter special characters in the search base. Resetting Prime Collaboration Assurance Passwords As a super administrator, system administrator or network operator, you can reset the password for other Prime Collaboration users. You can reset the Prime Collaboration Assurance web client globaladmin password using the following procedure. 28 OL

31 Changing Passwords To reset the Prime Collaboration Assurance globaladmin password: Step 1 Step 2 Step 3 Log in as a root user. Enter the "goemsam" command: Execute the following: su admin conf t username username password {hash plain remote} password role {admin user} Changing Passwords To change your own password, go to Administration > User Management, click Change Password, and make necessary changes. Single Sign-On for Prime Collaboration Prime Collaboration provides users with admin privileges to enable Single Sign-On (SSO) in Prime Collaboration Assurance and Prime Collaboration Provisioning using Security Assertion Markup Language (SAML). You can enable SSO in Prime Collaboration Provisioning to cross-launch the following UC applications: Cisco Unified Communications Manager Cisco Unity Connection Cisco Unified Presence Note To cross-launch the UC applications without the need for login credentials, ensure that SSO for those applications are configured on the same IdP server as that of Prime Collaboration. Ensure that the following prerequisites are met before you enable SSO: At least one LDAP Administrative user exists in the system through LDAP synchronization in Prime Collaboration Provisioning and by manually creating an LDAP administrative user in Prime Collaboration Assurance. For information on how to provide administrative privileges to a user in Prime Collaboration Provisioning, see "Managing Users" in the Cisco Prime Collaboration Provisioning Guide, An Identity Provider (IdP) server that enables you to use SSO to access many other applications from a single hosted application and a Service Provider. The Service Provider is a website that hosts the applications. Following are the supported third-party IdP servers: Open Access Manager (OpenAM) Ping Identity OL

32 Single Sign-On for Prime Collaboration Active Directory Federation Services (ADFS) Oracle Identity Manager For the steps to setup an IdP server, see the SAML SSO Deployment Guide for Cisco Unified Communication Applications, Release 10.0(1). Download the Identity Provider metadata file from the IdP server and save it in your local system. To enable Single Sign-on: Step 1 Step 2 Step 3 Step 4 Choose Administration -> Single Sign-on. Click Enable SSO. A warning message is displayed stating, Enabling SSO redirects you to the IdP server for authentication from the next login. To access the application, you will need to be authenticated successfully. Note Enable SSO is disabled if the above mentioned prerequisites are not met. Click Continue. Follow the steps provided in the SSO wizard to enable Single Sign-On. a) Locate the IdP metadata file from your local system and click Import IdP Metadata. b) Click Download Trust Metadata file. c) Launch the IdP server and import the downloaded Trust Metadata file. Note This is a manual step for Enabling SSO. You need to create a Circle of Trust (CoT) in the IdP server and log out before you proceed with the SSO testing. d) To run SSO Test Setup, select a username from the Valid Administrative Usernames drop-down. Note Using any other username to log in to the IdP server might lock the administrator account. e) Click Run SSO Test to test the connectivity among the IdP server, Prime Collaboration Applications, and Single Sign-On. If you are prompted with an error message, Unable to do Single Sign-On or Federation: Manually log in to the IdP server using the end user credentials and check if the authentication is successful. Verify if the Trust Metadata file is successfully uploaded in the IdP server. Verify if the Prime Collaboration server and the IdP server are part of the same Circle of Trust. f) Click Finish. In the converged mode, Prime Collaboration uses the Provisioning setup to cross launch the Cisco Unified CM, Cisco Unity Connection and Cisco Unified Presence applications. Troubleshooting and Logs for SSO When you are logged out of the Prime Collaboration server while enabling SSO, it is recommended that you close the browser and re-launch the Prime Collaboration application. Because, though your session expires in Prime Collaboration server, the IdP server session might still be active. You can find the log file (ssosp*.log) for Prime Collaboration Provisioning in the /opt/cupm/sep/logs directory and for Prime Collaboration Assurance in the /opt/emms/tomcat/webapps/emsam/log/sso directory. 30 OL

33 Single Sign-On for Prime Collaboration While enabling SSO, ensure that the hostname for Prime Collaboration is set and is part of DNS. When IdP server is down, you can: Use the recovery URL- IP address or host name that is part of DNS>/ssosp/local/login. Disable Single Sing-On from CMD Utility. To disable SSO from CMD utility in Prime Collaboration applications: Log in to Prime Collaboration Provisioning server using SSH with port 22, for Prime Collaboration Assurance it is 26. Navigate to the /opt/cupm/sep/build/bin directory for Prime Collaboration Provisioning and /opt/emms/emsam/bin directory for Prime Collaboration Assurance. Add <Operation> and <Value> entries for cpcmconfigsso.sh file based on the table below: Operations can be.. 1-To get the Single Sign-On status 2-To get the recovery URL status 3-To set the Single Sign-On status 4-To set the recovery URL status Values can be.. Not applicable Not applicable False Note True or False You cannot enable SSO through CLI. Use the UI procedure to enable SSO. To disable SSO, run the following command: cpcmconfigsso.sh 3 false Note By default, the recovery URL is enabled. If you want to disable it for security reasons, set it as false. OL

34 Single Sign-On for Prime Collaboration 32 OL

35 CHAPTER 4 Configuring System Parameters Prime Collaboration allows you to configure system parameters for both Prime Collaboration Assurance and Prime Collaboration Provisioning. To configure the following Prime Collaboration Assurance system parameters, navigate to Administration > System Setup > Assurance Setup. Configuring SMTP Server, page 33 SSL Certificate Authentication for Device Discovery, page 33 Configuring Prime Collaboration Assurance Server Time Zone, page 34 Configuring SMTP Server You can configure the SMTP server to send and receive notifications for alarms by specifying the SMTP server name and the sender AAA address. The value in the sender AAA address field helps you to identify the server you receive the from, in case of many servers. SSL Certificate Authentication for Device Discovery A Secure Socket Layer (SSL) certificate is primarily used to provide a secure connection between a server and a browser. The SSL certificate encrypts the sensitive information like login credentials, device credentials, and other details that you enter on the server. The encrypted information is communicated between the server and the respective browsers for authentication. In Prime Collaboration, when a device is added, the SSL certificates are exchanged for credential validation by accessing a protected resource using HTTPs. During exchange, the SSL certificate does not get stored in Prime Collaboration trust-store and communication to the device fails, at a later point of time. It is recommended that you manually import the SSL certificate to Prime Collaboration trust-store to access the device. Prime Collaboration enables you to check the authenticity of the SSL certificate during its communication with the devices or applications over HTTPs. However, this is not mandatory as you can still continue to discover the devices without authenticating the certificate. OL

36 Configuring Prime Collaboration Assurance Server Time Zone By default, Prime Collaboration does not validate the certificates from the devices or applications it communicates. To enable the SSL certificate authentication: Step 1 Step 2 Step 3 Step 4 Choose Administration > System Setup > Assurance Setup > General Settings. Check the Enable Certificate Authentication check box and click Save. Login as root to the Prime Collaboration Assurance server to import SSL certificates to the trust-store (use SSH with port 26 to login). Enter the following command if the certificate is already downloaded:./emsam_certificate_import.sh <dir_path> For example,./emsam_certificate_import.sh /root/cert Step 5 Enter the following command if the certificate needs to be downloaded and then imported:./emsam_certificate_import.sh <file> <dir_path> For example,./emsam_certificate_import.sh ip.txt /root/cert Step 6 Restart the Prime Collaboration server for the changes in trust manager to take effect. cpcmcontrol.sh restart Configuring Prime Collaboration Assurance Server Time Zone To configure the Prime Collaboration Assurance server time zone: Step 1 Step 2 Log in to the Prime Collaboration Assurance server with the account that you have created during installation. By default, it is admin. Enter the following command to see the list of supported time zones: Step 3 Example: cm/admin# show timezones Enter the following commands to set the time zone for the Prime Collaboration Assurance server: Step 4 Example: cm/admin(config)# config t cm/admin(config)# clock timezone US/Pacific cm/admin(config)# exit Enter the following command to copy running-configuration to startup-configuration: Step 5 Example: cm/admin# write memory Enter the following command to restart the Prime Collaboration Assurance server: 34 OL

37 Configuring Prime Collaboration Assurance Server Time Zone Step 6 Example: cm/admin# application stop cpcm cm/admin# show application status cpcm cm/admin# application start cpcm Wait for 10 minutes for the server to finish the restart process and enter the following command to check if the time zone is set to the new value: Example: cm/admin# show timezone US/Pacific To configure the time zones in Prime Collaboration Provisioning, see "Changing Time Zone Settings" in the Cisco Prime Collaboration Provisioning Guide. OL

38 Configuring Prime Collaboration Assurance Server Time Zone 36 OL

39 CHAPTER 5 Integrating Prime Collaboration Servers You can leverage capabilities of both Prime Collaboration Assurance and Prime Collaboration Provisioning systems if you choose to integrate Prime Collaboration Assurance and Prime Collaboration Provisioning applications in order to monitor voice endpoints, video endpoints, and provision the Unified Communications Systems. Note If you have deployed Prime Collaboration in MSP mode, Prime Collaboration Provisioning or Prime Collaboration Analytics cannot be integrated with Prime Collaboration Assurance. Attaching Prime Collaboration Provisioning, page 37 Viewing License Details, page 38 Cross Launching Cisco Prime Collaboration Deployment, page 40 Attaching Prime Collaboration Provisioning To integrate the servers: Step 1 Step 2 Step 3 Go to Administration > System Setup > Assurance Setup > Cisco Prime 360 Integration Under Prime Collaboration Provisioning Server Setup, specify the IP address and the globaladmin password of the Prime Collaboration Provisioning application server that you want to attach to. Enter the port details. The port used for Prime Collaboration Assurance over HTTPS is 443 and for Prime Collaboration Provisioning it is See Required Ports for Prime Collaboration for details on the ports used for data transfer. Step 4 Step 5 Test the connectivity of the Prime Collaboration Provisioning server. Click Attach. After you attach the Prime Collaboration Provisioning application to Prime Collaboration Assurance, you must refresh the UI to view the Design and Deploy tabs on the UI. OL

40 Viewing License Details After Integration: The Prime Collaboration Provisioning UI is converged with Prime Collaboration Assurance, and the Provisioning IP address is redirected to Prime Collaboration Assurance application even though you log in to Prime Collaboration Provisioning application. After you detach Prime Collaboration Provisioning from Prime Collaboration Assurance, the user roles that were applicable for Prime Collaboration Provisioning and Prime Collaboration Assurance in the converged mode also apply for the standalone applications. If you want to restart or shut down the Prime Collaboration Provisioning application, ensure you detach it from Prime Collaboration Assurance. You can then converge it after the restart process. Viewing License Details In the License Management page (Administration > License Management), you can view the following information: Type of license or Active Image License Installed Evaluation or Image. Total number of licenses allowed for the license categories and the number of licenses used currently. In Standard mode, the usage is shown as zero percentage. For more details about the total number of licenses for each category for the Advanced mode, see the License Count section. Expiration Date Date when the license expires. This value is applicable to Evaluation license only. Northbound Interface Licenses and Northbound Interface Expiration Date for Prime Collaboration Provisioning application. You must review the Cisco Prime Collaboration Quick Start Guide, 10.5 to learn how to register and obtain the license file for Prime Collaboration. Switching Between the Standard and Advanced modes in Prime Collaboration Prime Collaboration provides you the facility to switch from the Standard mode to the Advanced mode in both Prime Collaboration Assurance and Prime Collaboration Provisioning. The table below captures the different scenarios of switching: Installation Modes Standard to Advanced Evaluation Standard to Advanced (Purchase license) Advanced Evaluation to Advanced (Purchase license) Advanced Evaluation to Standard 38 OL

41 Viewing License Details Prime Collaboration Assurance Yes. (Click the Upgrade icon at the top right corner of the User Interface and click Start Evaluation.) Yes. (Click the Upgrade icon at the top right corner of the User Interface and click Add Licenses. In the License Management page, click Add and upload the license file for the advanced mode.) Yes. (Click the Upgrade icon at the top right corner of the User Interface and click Add licenses. In the License Management page, click Add and upload the license file for the advanced mode.) Yes. After the evaluation expiry, you are prompted with a message to either downgrade to the standard mode or to purchase a license file for advanced mode. If you choose to downgrade, the Cluster for Standard Mode dialog box pops-up. Select a cluster from the Unified Communications Manager drop-down, device type from the Cisco Unity Connection drop-down and click Select. Prime Collaboration Provisioning Not Applicable Yes. (Click the Upgrade icon at the top right corner of the User Interface and click Add Licenses. In the License Management page, click Add and upload the license file for the advanced mode) Yes. (Click the Upgrade icon at the top right corner of the User Interface and click Add licenses. In the License Management page, click Add and upload the license file for the advanced mode) Not Applicable In the converged mode, you have the provision to switch over from the standard to advanced mode. You can either upgrade: One application only - You can switch from the standard to advanced mode in Prime Collaboration Assurance only and continue to access the Prime Collaboration Provisioning in the same (installed) mode. Both the applications - You can switch from the standard or advanced evaluation mode to the advanced (purchase licensed) in both Prime Collaboration Assurance and Prime Collaboration Provisioning. OL

42 Cross Launching Cisco Prime Collaboration Deployment Viewing About Details This page displays the About details for Prime Collaboration Assurance. To launch this page, click at the top right corner of the User Interface. Click Assurance Information link to view the following system information details in a quick view. Build Version License Type Assurance Expiration Date (displayed in red for the last 15 days before expiry) Analytics Expiration Date (displayed in red for the last 15 days before expiry) IP Address MAC Address DB server IP Address DB server MAC Address Note DB server IP Address and DB server MAC Address fields are specific to Prime Collaboration Assurance very large OVA deployment model and does not appear in the Assurance Information link for Prime Collaboration Assurance small, medium, and large OVA deployment models. Click Licensing link to open the License Management page. Cross Launching Cisco Prime Collaboration Deployment You can manage the Unified Communication applications using Cisco Prime Collaboration Deployment. You can cross-launch to these applications to perform tasks such as migration, of old clusters to new virtual machines, fresh installs and upgrades on existing clusters. For more information, see Configuring Prime Collaboration Deployment. Configuring Prime Collaboration Deployment Cisco Prime Collaboration Deployment is an application designed to assist in the management of Unified Communication applications. It allows you to perform tasks such as migration, of old clusters to new virtual machines, fresh installs, and upgrades on existing clusters. For more information, see the Cisco Prime Collaboration Deployment Administration Guide. 40 OL

43 Cross Launching Cisco Prime Collaboration Deployment To configure the Prime Collaboration Deployment Manager, Step 1 Step 2 Step 3 Choose Administration -> System Setup -> Assurance Setup -> Cisco Prime 360 Integration. Enter the IP Address that you want to configure and click Save. Choose Administration -> Deployment Manager to launch the Deployment Manager page. OL

44 Cross Launching Cisco Prime Collaboration Deployment 42 OL

45 PART III Managing Devices in Prime Collaboration Assurance Managing Devices, page 45

46

47 CHAPTER 6 Managing Devices Revised: May 13, 2013 You need to get the devices in Managed state in Device Work Center for Prime Collaboration to display monitoring information about the devices. Before you can manage devices using Prime Collaboration, you need to discover devices in your network. After you add the device credentials, you can discover and manage the devices. To view the pre-canned dashboards and create custom dashboards, and to view the alarms associated with Unified CM and Unity Connection, you need to only add the Unified CM or Unity Connection cluster using the Add Device option in Device Work Center. To manage Cisco TMS applications, you need to first discover the devices using the auto discovery option. You need to configure device credentials for the Cisco TMS and associated devices that are managed using Cisco Prime Collaboration. Device credentials are required for discovering these devices and updating inventory. If the credentials vary for different devices, create separate credentials profiles. That is, if you want to manage two Cisco TMS with different credentials in Prime Collaboration, you must create two separate credentials profiles. Review Setting up Devices for Prime Collaboration Assurance to see whether you have completed the necessary configuration. Adding Cisco Unified CM and Unity Connection, page 46 Adding Cisco TMS and Associated Devices, page 46 Adding a Device Credentials Profile, page 46 Cloning a Device Credentials Profile, page 47 Credential Profiles Field Descriptions, page 47 Editing Device Credentials, page 50 Verifying Device Credentials, page 50 Discovery Lifecycle of a Cisco TMS, page 54 Current Inventory, page 55 OL

48 Adding Cisco Unified CM and Unity Connection Adding Cisco Unified CM and Unity Connection You can add single or multiple devices to Prime Collaboration manually using the Add Device option on the Device Work Center page. To add a new Cisco Unified CM or Unity Connection device: Step 1 Step 2 Step 3 Choose Operate > Device Work Center. In the Device Work Center page, click UCM/UC Devicesfrom the Adddrop-down list. Enter the HTTP(S) credentials and click Add Device. After the Cisco Unified Communications Manager or Cisco Unity Connection gets added, the pre-canned dashboards and the alarms can be viewed. Adding Cisco TMS and Associated Devices You must add and configure device credentials before discovering these devices. See Adding a Device Credentials Profile, on page 46 for details. To add Cisco TMS and associated devices: Step 1 Choose Operate > Device Work Center. Step 2 Step 3 In the Device Work Center page, click TMS and Associated device (Auto Discover) from the Adddrop-down list. Enter the IP address or hostname of the device. You can enter multiple IP addresses or hostnames using one of the supported delimiters: comma, colon, pipe, or blank space. Step 4 Click Run Now to run the discovery job. You can view the job status on the job management page. Adding a Device Credentials Profile You must add and configure device credentials before discovering devices. In your network, you may have configured the same SNMP credentials for all devices, but different CLI credentials. In such cases, first create a new profile and later clone the existing profile. Note JTAPI credentials are not required for Prime Collaboration Assurance Standard mode. 46 OL

49 Cloning a Device Credentials Profile To add a new credential profile: Step 1 Step 2 Step 3 Step 4 Choose Operate > Device Work Center. In the Device Work Center page, click Manage Credentials. In the Credentials Profile window, click Add and enter the necessary information. See the Credential Profiles Field Descriptions table. Click Save. Cloning a Device Credentials Profile To copy an existing credential profile: Step 1 Step 2 Step 3 Step 4 Choose Operate > Device Work Center. In the Device Work Center page, click Manage Credentials. In the Credentials Profile window, select an existing profile and click Clone. Click Add/Update. Credential Profiles Field Descriptions After the devices are discovered, you can check the current Inventory table to verify that the credentials have been updated in the Prime Collaboration database. Note JTAPI credentials are not required for Prime Collaboration Assurance Standard mode. The following table describes the fields on the Credential Profiles page. Table 4: Credential Profiles Field Descriptions Field Name Profile Name Description Name of the credential profiles. For example: CTS_MAN CUCM router_switches OL

50 Credential Profiles Field Descriptions Field Name Device Type IP VersionFootnote. IP Address Pattern Description (Optional) The credential fields (such as SNMP, CLI) are displayed, based on the device type that you have selected. To reduce rediscovery time, we recommend that you select the device type when you create the credential profiles. The default device type is Any, if you do not select a device type while creating a credential profile. See Cisco.com for the list of device types. For EX series, MX series, SX series, bare Codec devices, and all profiles with Codec, select the device type as Codec. For MSE devices, select Cisco MCU as the device type. You can enter any credentials (SNMP, HTTP, JTAPI, CLI, MSI) to create an Any credential profile. You must create an Any credential profile to run autodiscovery (Ping Sweep and CDP discovery). However, you can run logical discovery also. If your network has multiple subnets, then create an Any profile for each subnet. The IP address is version 4 or version 6. IP address of the devices for which the credentials are provided. You must: Separate multiple IP addresses by the delimiter pipe ( ). Not use or Not use question mark (?). We recommend that you: Enter the exact IP address for CTS-Manager, Cisco Unified CM, and Cisco TMS. Enter the exact IP address for either CTS or network devices. Do not use many wildcard expressions in the address patterns. For example: * * * * *.* *.* *.* *.* Avoid using patterns such as 150.*.*.*, ?, *.*/24. If you are unable to find a common pattern for the devices, enter *.*.*.*. See SNMPv2C to understand how the patterns are used. 48 OL

51 Credential Profiles Field Descriptions Field Name General SNMP Options Description SNMP Timeout - The default is 10 seconds. SNMP Retries - The default is 2. SNMP Version - Selecting an SNMP version is mandatory. SNMPv2C Used to discover and manage the device. SNMPv3 Used to discover and manage the device. SNMP Read Community String You can provide either SNMPv2C or SNMPv3 credentials. We recommend that you use different SNMP credentials for Cisco TelePresence systems and network devices. Prime Collaboration searches the credential profiles, based on the IP address pattern. Prime Collaboration then chooses a profile for which the SNMP credentials match. There can be multiple matching profiles, that is, profiles with the same SNMP credentials. In such cases, Prime Collaboration chooses the profile that matches first. Note If multiple profiles have the same SNMP credentials but different CLI credentials, Prime Collaboration might chose a profile that contains the correct SNMP credentials but incorrect CLI credentials for the device. If this occurs, the troubleshooting workflow might not work. SNMP Write Community String SNMP Security Name - Enter a security name. SNMP Authentication Protocol - You can choose either MD5 or SHA. CLI Used to access the device through CLI to discover media path for troubleshooting. SNMP Authentication Passphrase - Enter a passphrase. CLI Login Username and Password The CLI credentials are used during the troubleshooting workflow. If the credentials are not entered or if the entered credentials are incorrect, the troubleshooting workflow feature may not work. HTTP Used to access the device through HTTP to poll system status and meeting information. JTAPI Used to retrieve the session status information from the Cisco Unified CM. HTTP Username and Password Prime Collaboration first checks the access for HTTP. If the access attempt fails, then Prime Collaboration checks the access for HTTPS. If you log in to Cisco TMS using the <domain/username> format, then ensure that you add the same <domain/username> value in the HTTP(s) Username field. JTAPI Username and Password. Note Password must not contain a semicolon (;) or equals (=). JTAPI is optional. It is required only for TelePresence session monitoring. OL

52 Editing Device Credentials Field Name Description MSI Used to access the device through MSI to discover media path for troubleshooting. MSI Username and Password The MSI credentials are used during the troubleshooting workflow, to troubleshoot MSI enabled endpoints. MSI credentials remain the same as http credentials for TC 6.0 and TE 6.0 software versions. For TX 6.0 version, the default MSI username is msiuser and the password is cisco. 1 1 (1) For Prime Collaboration compatibility details with IPv6 devices, see Prime Collaboration Support for IPv6. Note Minimize the use of wildcard character (*), while defining the IP address patterns in the credential profiles (Operate > Device Work Center > Manage Credentials). Use of wildcard character may increase the discovery time. Editing Device Credentials If you have modified credentials for the devices that you are currently managing in the Prime Collaboration application, you must modify the relevant credential profiles in the Prime Collaboration database. If the credentials are incorrect, a major event, Device is not accessible from Prime Collaboration, is triggered (Operate > Alarms > Events. To edit a credential profile: Step 1 Step 2 Step 3 Choose Operate > Device Work Center. From the Device Work Center, select a device and click Edit Update the credentials and click Save. Prime Collaboration takes a few minutes to update its database with the modified credentials. After the credentials are updated, an informational event, Device is accessible from Collaboration Manager, is triggered. Prime Collaboration uses the updated credentials in the next polling job. Verifying Device Credentials If device discovery fails because of incorrect credentials, you can test the credentials for the failed devices and rediscover those devices. Choose Operate > Device Work Center > Discovery Jobs for a list of devices that were not discovered. 50 OL

53 Verifying Device Credentials Note Do not run this task when a discovery job is in progress. To verify device credentials: Step 1 Step 2 Step 3 Step 4 Step 5 Choose Operate > Device Work Center. From the Device Work Center, click Manage Credentials. From the Credential Profiles window, select the profile name to use for testing the credentials, and click Verify. Enter a valid device IP address to test the credentials. You can verify only one device at a time, and you cannot enter expressions such as *.*.*.*, *.*, and so on. Click Test. You can see an inprogress moving icon next to the test button till the task completes. The test results are displayed under the Test Credential Result pane. If the verification fails, see the possible reasons listed in Credential Verification Error Messages. Credential Verification Error Messages The credential verification error messages are tabulated below. Table 5: Credential Verification Error Messages Error Message SNMPv2 SNMP Request: Received no response from IP Address. Conditions Failed for one of the following reasons: Device response time is slow. Device is unreachable. Incorrect community string entered in the credential profile. Possible Solutions Verify the device connectivity. Update the credential profile with the correct community strings. SNMP timeout. Either the device response time is slow or the device is unreachable. Verify the device connectivity. Increase the SNMP Timeout and Retries values in the credential profile. Failed to fetch table due to: Request timed out. SNMPv3 Either the device response time is slow or the device is unreachable. Increase the SNMP Timeout and Retries values in the credential profile. OL

54 Verifying Device Credentials Error Message The configured SNMPv3 security level is not supported on the device. The SNMPv3 response was not received within the stipulated time. SNMPv3 Engine ID is wrong. SNMPv3 message digest is wrong. Conditions Device does not support the configured SNMPv3 security level. Either the device response time is slow or the device is unreachable. Incorrect engine ID entered in the credential profile. Failed for one of the following reasons: Either the SNMPv3 authentication algorithm or the device password is incorrect. Network errors. Possible Solutions Change the SNMPv3 security level to the supported security level in the credential profile. Verify the device connectivity. Enter the correct SNMPv3 engine ID in the credential profile. Verify that the correct SNMPv3 authentication algorithm and device password are set in the credential profile. Check for network errors. SNMPv3 message decryption error. Cannot decrypt the SNMPv3 message. Verify that the correct SNMPv3 authentication algorithm is entered in the credential profile. Unknown SNMPv3 Context. The configured SNMPv3 context in the credential profile does not exist on the device. Verify that the configured SNMPv3 context is correct in the credential profile. Unknown SNMPv3 security name. CLI Login authentication failed. Connection refused. Either the SNMPv3 username is incorrect in the credential profile or the SNMPv3 username is not configured on the device. Incorrect credentials entered in the credential profile. Either SSH or Telnet service may not be running on the device. Verify that the correct SNMPv3 username is set in the credential profile and on the device. Verify and reenter the device CLI credentials in the credential profile. 1 Verify the device connectivity for the supported CLI (port). 2 Verify whether the SSH or Telnet service is running on the device. HTTP 52 OL

55 Verifying Device Credentials Error Message Server returned HTTP response code: 401 for URL. Conditions Either the HTTP service is not running or the URL is invalid. Possible Solutions Verify whether the HTTP or HTTPS service is running on the device. Verify whether the URL is valid on the server. Connection refused. HTTP check failed. JTAPI Failed to access JTAPI. MSI Failed to access MSI. The HTTP or HTTPS service is not running. Incorrect HTTP credentials entered in the credential profile. Incorrect JTAPI credentials entered in the credential profile. Incorrect MSI credentials entered in the credential profile. Verify whether the HTTP or HTTPS service is running on the device. Verify and reenter the device HTTP credentials in the credential profile. Verify and reenter the device JTAPI credentials in the credential profile. Note Password must not contain a semicolon (;) or equals symbol (=). Verify and reenter the device MSI credentials in the credential profile. Note All the nodes in the cluster may not be running all the protocols. For example, JTAPI may not be running on all the nodes. As a result, the credential validation test may fail for some of your nodes. After fixing the credentials issue, test the device credentials again and run the discovery for that device. After the devices are discovered, you can verify if the access information is updated in the Prime Collaboration database in the current Inventory table. To know more about the inventory table, see the View Inventory Details section in the Cisco Prime Collaboration Assurance Guide Advanced, OL

56 Discovery Lifecycle of a Cisco TMS Discovery Lifecycle of a Cisco TMS The following figure shows the discovery lifecycle of a Cisco TMS. Figure 1: Discovery Life Cycle for a Cisco TMS 54 OL

57 Current Inventory Current Inventory The inventory table is available on the Device Work Center page; choose Operate > Device Work Center. You can use the show drop-down list on the inventory table to filter devices based on the device type and state. There are options such as Quick Filters and Advanced Filters to filter devices based on the device criteria. Not all columns of the inventory table appear by default. To see all the columns, click the Settings option on the top right corner. You can export the inventory table as a CSV or a PDF file by clicking the Export icon at the upper right corner of the inventory table. Field Descriptions for the Current Inventory Table Field Host Name Description Name assigned to the device for ease of identification Device Type Model IP Address Software Version Software Type State Status Reason Last Discovered Endpoint Name Extension The most applicable role or service of the device. Device model IP address used for managing the device. Click on the IP address to log into the device. For routers and switches, you must associate a terminal client application, such as Putty, to log into the device Software version running on the device. Software running on the device. Status of the device. Reason for the device status. Date and time when the device was last discovered. The time will be according to the time zone set in the Prime Collaboration server. Name assigned to the endpoint for ease of identification. Directory Number of endpoints. This number helps to identify a device uniquely. OL

58 Current Inventory 56 OL

59 PART IV Monitoring the Network Customizing Alarms and Events, page 59 Prime Collaboration Standard Dashboards, page 67 Monitoring Alarms and Events, page 85

60

61 CHAPTER 7 Customizing Alarms and Events This section explains how to customize alarms and events and set up notifications to suit your business needs. Threshold Rules, page 59 Configuring Polling Parameters, page 60 Configuring Alarm and Event Notification, page 61 Creating Custom Alerts, page 64 Threshold Rules The Threshold Rules page lists all the events in Prime Collaboration. This page contains two tabs - Basic and Advanced. The Basic tab in the Threshold Rules page lists the inline events in Prime Collaboration that you can raise or suppress. The Advanced tab in the Threshold Rules page lists all the available events and also allows you to create custom events. To create custom events, click Add Event, select a cluster from the drop-down, enter the required details, and click Save. For each of the events listed in both these tabs, you can add or edit custom threshold by expanding the event and clicking Custom Threshold. In the Basic tab, you can only create threshold based on the device type selected whereas in the Advanced tab, you can also set threshold rules, such as scheduling alerts, setting frequency, severity, and so on for the thresholds that you create. On clicking the Custom Threshold in the Advanced tab, the Add Alert Settings page is displayed. Select the Device Type, Cluster and click Next. In the Add Threshold Rules tab, enter the required details and click Save. Apart from adding events and thresholds, you can also perform the actions mentioned in the table below: Actions Basic Advanced Change Severity Yes Yes Check the box against Name - to select all the events; or check the boxes of the events of your choice and click Change Severity. Check the box against Name - to select all the events; or check the boxes of the events of your choice and click Change Severity. OL

62 Configuring Polling Parameters Raise or Suppress events Raise or Suppress thresholds Edit, Reset, and Delete existing thresholds Yes Check the box against Name - to select all the events; or check the boxes of the events of your choice and click Raise or Suppress. Yes Expand the event, select threshold, and select Raise, Suppress, or Conditional from the drop-down. No You can edit or reset the threshold settings, but cannot delete. To edit or reset the threshold, expand the event, edit the threshold settings, and click Save Changes. Yes Check the box against Name - to select all the events; or check the boxes of the events of your choice and click Raise or Suppress. Yes Expand the event, select threshold, and select Raise, Suppress, or Conditional from the drop-down. Yes To edit or reset the threshold, expand the event, edit the threshold settings, and click Save Changes. To delete a threshold, expand the event, select the threshold, and click Delete. Edit or Delete Events Cloning for events No No Yes Expand the event, edit the settings, and click Save. To delete an event, select the check box and click Delete. Yes Click Clone, fill in the details and click Save. Note: You can use the clone option only for CVP and UCCE devices. This option is disabled for events of the other device types such as Communication Manager, Media Sense, IM and Presence, Finesse, and so on. Configuring Polling Parameters The Prime Collaboration poller manager supports setting up polling intervals for TelePresence Monitoring Settings. System Status Polling Interval Prime Collaboration collects: CPU and memory utilization, and peripheral status for endpoints and multipoint switches, using SNMP and HTTP (HTTPS) for Cisco C and Ex series endpoints. 60 OL

63 Configuring Alarm and Event Notification CPU and memory data from call and session controllers. Service status from call and session controllers; and from multipoint switches and application managers, using HTTP (HTTPS). You can also set polling interval for generic events for Conferencing and TelePresence Applications. You can set up polling intervals at Administration > Polling & Threshold > TelePresence Monitoring Settings. Configuring Alarm and Event Notification For each alarms, Prime Collaboration compares the alarms, devices, severity, and state against the configured notification groups and sends a notification when there is a match. Matches can be determined by user-configured alarm sets and notification criteria. Notification criteria define what you want to monitor for the purpose of sending notifications. A notification criterion is a user-defined, named set of devices or phones, and events of a particular severity and status. You must specify notification criteria to configure a notification group. Prime Collaboration supports device-based notification criterion. You can configure Prime Collaboration to send notifications for only a subset of the alarms that it monitors. You can set the alarm that are of interest to you when you define the notification criterion by specifying an alarm set for a device-based notification criterion. You can create as many alarm sets as you would like. Adding an Alarm Set You can create alarm sets for which you can set up notifications. For a list of supported alarms and events, see Cisco Prime Collaboration Supported Alarms and Events, 10.0 To add and edit an Alarm set: Step 1 Step 2 Step 3 Choose Administration > Alarm & Event Setup > Notification > Assurance Notification Criteria > Alarm Set. Click Add and enter the details. Note When you create an alarm set that has several alarms, you might need to use multiple search criteria. In such situations, you need to use the Advanced Filtering option to enter multiple search criteria using the + icon, with Match selection as Any. Using the Quick Filter might not work as desired. Click Save to save your changes. To delete an Alarm Set, select the check box and click Delete. OL

64 Configuring Alarm and Event Notification Adding Notification Criterion To add and edit device notification groups: Step 1 Step 2 Step 3 Step 4 Step 5 Step 6 Step 7 Step 8 Step 9 Choose Administration > Alarm & Event Setup > Notification > Assurance Notification Criteria, then click Add. In The New Device-Based Criterion wizard add the information in the Define General Information page: Click Next. The Select Devices/Device Groups pane appears. If you check the check box for New devices that will be added to all the groups should automatically be a part of the group, the devices that are added to or deleted from Prime Collaboration, are also added to or deleted from the notification criterion. This happens when the notification criterion includes a device group that the devices belong to. Uncheck to maintain a static list of devices for any device groups included in the notifications criterion. Click Add. In the Select Device/Device Groups window, expand device group folders and check the check boxes for one or more devices or clusters. If you select a device group, the notification criterion will stay up-to-date when devices are added or deleted from Prime Collaboration only if you also check the check box. New devices that will be added to all the groups should automatically be a part of the group. Click Next. In the Set up Destination pane, add the following information: Click Next. Review the information in the summary, then click Save. General Information Field Descriptions Table 6: Add General Information GUI Element Criterion Name field Alarm Set Type list box Alarm Severity check boxes Enter a name for the notification criterion. Choose an alarm set. Check none, one, or more of the following: Critical. Major Minor Warning 62 OL

65 Configuring Alarm and Event Notification GUI Element Alarm Status check boxes Check none, one, or more of the following: Active Acknowledged Cleared User Cleared OperationInterval Click the Always radio button to schedules the notification group to always be active. Choose the hours of the day during which you want this notification group to be active: From: HH:MM Choose hour and minute that the subscription becomes active. To: HH:MM Choose the last hour and minute during which the subscription is active. By default, the values are from 00:00 to 00:00 and the subscription is active for 24 hours. Use this field, for example, to send notifications during one shift and not during another. Set up Destination Field Descriptions Table 7: Set Up Destination GUI Element Include Link to Notification Details check box Subscription Type radio buttons Check to include URLs in the notification from which users can directly open the relevant page in Prime Collaboration for more information. Uncheck to omit URLs from notifications. Enter data in the Subscription Type fields. Subscription Type fields OL

66 Creating Custom Alerts GUI Element SMTP Server field Sender Address field Recipient Address(es) field Send Recipient(s) Subject Only check box Enter a fully qualified DNS name or IP address for a Simple Mail Transfer Protocol (SMTP) server. (The name of the default SMTP server might already be displayed.) To select from any nondefault SMTP servers in use by existing subscriptions, click the SMTP Servers button. For instructions on how to configure a default SMTP server, see the Setting System-Wide Parameters Using System Preferences, page Enter the address that notifications should be sent from. If the sender s service is hosted on the SMTP server specified, you need enter only the username. You do not need to enter the domain name. Enter one or more addresses that notifications should be sent to, separating multiple addresses with either a comma or a semicolon. If a recipient s service is hosted on the SMTP server specified, you need to enter only the username. You do not need to enter the domain name. Check to include only the subject in the message. Uncheck to send a fully detailed message (default). 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 Step 2 Step 3 Choose Administration > Alarm & Event Setup > Event Customization > Threshold Rules. You can also add events directly from a custom dashboard that you created. Click Add Event. In the New Performance Counter Event Window: a) Specify the cluster and the server. b) Select the counter from the Available Counters drop-down list. If you have installed Prime Collaboration in MSP mode, public IP address is displayed when you select the server and counter. However, you cannot create/add a custom event for such nodes if a specific performance counter/device is not added or managed in Prime Collaboration. Also, in the Cluster drop-down list, only those products and clusters which belong to a specific customer (that is selected from the global filter drop-down) are displayed. c) Add a description and the recommended action. This is optional. d) Specify the threshold values, duration and frequency, and the schedule for monitoring. 64 OL

67 Creating Custom Alerts e) Click Save. Custom Alert Parameters Table describes the parameters you can specify for the custom alert. Setting Threshold Description 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 OL

68 Creating Custom Alerts Setting Trigger on every poll Trigger <> events within <> minutes Description 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. 66 OL

69 CHAPTER 8 Prime Collaboration Standard Dashboards Revised: May 13, 2013 The Prime Collaboration dashboards help you to monitor your network by providing near real-time information about the core Unified Communications and TelePresence components. The dashboards enable you to monitor the system health. UC Performance Monitor Dashboards, page 67 Creating Custom UC Performance Monitor Dashboards, page 81 Performing Device Search, page 82 UC Performance Monitor Dashboards The UC Performance Monitor page displays system-defined dashboards based on the performance counters. If you have deployed Prime Collaboration in MSP mode, the dashlets in the system-defined dashboard display the public IP for all devices which are managed in Prime Collaboration. However, private IP address is displayed only for a device that has not been managed in Prime Collaboration. Note You can monitor only one cluster per product for a single installation of Prime Collaboration Standard. To view the dashboards, select the product and cluster from the Cluster drop-down list and then select the required dashboard from the Dashboard drop-down list. If you have deployed Prime Collaboration in MSP mode, in the Cluster drop-down list, only those products and clusters which belong to a specific customer (that was selected from the Customer Summary page) are displayed. System Summary Displays information about CPU usage, Virtual Memory usage, Common Partition Usage, and the Critical Services status. OL

70 UC Performance Monitor Dashboards CPU Usage Displays the real time CPU usage and the maximum value in the past 3 minutes. Virtual Memory Usage Displays the real-time Virtual Memory usage and the maximum value in the past 3 minutes. Common Partition Usage Services Displays the real-time Common Partition Usage and the maximum value in the past 3 minutes. Displays the name of the service, the status (whether the service is up, down, activated, stopped by the administrator, starting, stopping, or in an unknown state), and the elapsed time during which the services existed in a particular state for the server or for a particular server in a cluster (if applicable). Note If the service status is displayed as Unknown State, the system cannot determine the state of the service. CallManager Summary Displays registered phones, calls in progress, and active gateway ports and channels. Registered Phones Displays the total number of phones that are registered and the delta of phones that are registered in the last minute. A negative value indicates that phones were unregistered; a positive value indicates new phones were registered. Calls in Progress Displays the total number of calls in progress and the delta calls in progress in the last minute. A negative value indicates that calls were completed or dropped; a positive value indicates new calls were established. Active MGCP Ports and Channels Displays the total number of active MGCP ports and channels and the delta of active MGCP ports and channels in the past minute. A negative value indicates that active MGCP ports and channels decreased; a positive value indicates that active MGCP ports and channels increased. Call Activity Call Activity Displays the call activity on Cisco Unified Communications Manager, including calls completed, calls attempted, calls in progress, and logical partition total failures. This includes all servers in the cluster, if applicable. 68 OL

71 UC Performance Monitor Dashboards Calls Completed Displays the total number of calls completed. Also displays the delta of calls completed in the past 1 minute. It can have positive or negative values based on the calls completed in the past minute. Calls Attempted Displays the total number of calls completed. Also displays the delta of calls completed in the past 1 minute. It can have positive or negative values based on the calls attempted in the past minute. Calls in Progress Displays the total number of calls in progress and the delta calls in progress in the past 1 minute. A negative value indicates that calls were completed or dropped; a positive value indicates that new calls were established. Logical Partition Failures Displays the total Logical Partition Failures. Also displays the delta of Logical Partition Failures in the past 1 minute. Gateway Activity Displays gateway activity on Cisco Unified Communications Manager, including active ports, ports in service, and calls completed. Gateway Activity includes all nodes in the cluster, if applicable. MGCP FXS Ports in Service: Displays the number of FXS ports that are currently available for use in the system. Ports Active: Displays the number of FXS ports that are currently in use (active) on this Unified Communications Manager. Calls Completed: Displays the total number of successful calls that were made from all the FXS port instances on the MGCP FXS device. MGCP FXO Ports in Service: Displays the number of FXO ports that are currently available for use in the system. Ports Active: Displays the number of FXO ports that are currently in use (active) on this Unified Communications Manager. Calls Completed: Displays the total number of successful calls that were made from all the FXO port instances on the MGCP FXO device. OL

72 UC Performance Monitor Dashboards MGCP T1 Spans in Service: Displays the number of T1 CAS spans that are currently available for use. Channel Active: Displays the number of T1 CAS voice channels that are in an active call on this Unified Communications Manager. Calls Completed: Displays the total number of successful calls that were made from all the instances of MGCP T1 CAS device. MGCP PRI Spans In Service: Displays the number of PRI spans that are currently available for use. Channel Active: This represents the number of PRI voice channels that are in an active call on this Unified Communications Manager. Calls Completed: Displays the total number of successful calls that were made made from all the instances of MGCP PRI device. Displays the trunk activity on Cisco Unified Communications Manager, including calls in progress and calls completed. This counter includes all nodes in the cluster, if applicable. H323 Calls In Progress: Displays the total number of calls currently in progress on all the instances of Cisco H323 device. Calls Completed: Displays the total number of successful calls made from all the instances of Cisco H323 device. SIP Trunk Calls In Progress: Displays the total number of calls that are currently in progress on all the instances of SIP device, including all active calls. When all calls that are in progress are connected, the number of calls in progress and the number of active calls are the same. Calls Completed: Displays the total number of calls that were actually connected (a voice path was established) from all the instances of SIP device. This number increments when the call is terminated. SDL Queue Displays SDL queue information, including the number of signals in queue and number of processed signals. 70 OL

73 UC Performance Monitor Dashboards Signals in SDL Queue High: Indicates the number of high-priority signals in the Unified Communications Manager queue. High-priority signals include timeout events, internal Unified Communications Manager KeepAlives, certain gatekeeper events, and internal process creation, among other events. A large number of high-priority events will cause degraded performance on Unified Communications Manager, resulting in slow call connection or loss of dial tone. Use this counter in conjunction with the Queue Signals Processed High counter to determine the processing delay on Unified Communications Manager. Normal: Indicates the number of normal-priority signals in the Unified Communications Manager queue. Normal priority signals include call processing functions, key presses, and on-hook and off-hook notifications, among other events. A large number of normal-priority events will cause degraded performance on Unified Communications Manager, sometimes resulting in delayed dial tone, slow call connection, or loss of dial tone. Use this counter in conjunction with the Queue Signals Processed Normal counter to determine the call processing delay on Unified Communications Manager. Remember that high-priority signals must complete before normal-priority signals begin to process, so check the high-priority counters as well to get an accurate picture of the potential delay. Low: Indicates the number of low-priority signals in the Unified Communications Manager queue. Low-priority signals include station device registration (except the initial station registration request message), among other events. A large number of signals in this queue could result in delayed device registration. Lowest: Indicates the number of lowest-priority signals in the Unified Communications Manager queue. Lowest priority signals include the initial station registration request message during device registration. A large number of signals in this queue could result in delayed device registration. Processed SDL Signals High: Indicates the number of high-priority signals that are processed by Unified Communications Manager for each 1-second interval. Use this counter in conjunction with the Queue Signals Present High counter to determine the processing delay on this queue. Normal: Indicates the number of normal-priority signals that are processed by Unified Communications Manager for each 1-second interval. Use this counter in conjunction with the Queue Signals Present Normal counter to determine the processing delay on this queue. Remember that high-priority signals are processed before normal-priority signals. Low: Indicates the number of low-priority signals that are processed by Unified Communications Manager for each 1-second interval. Use this counter in conjunction with the Queue Signals Present Low counter to determine the processing delay on this queue. The number of signals that are processed gives an indication of how much device registration activity is being processed in this time interval. Lowest: Indicates the number of lowest-priority signals processed by Unified Communications Manager for each 1-second interval. Use this counter in conjunction with the Queue Signals Present Lowest counter to determine the processing delay on this queue. The number of signals that are processed gives an indication of how many devices began the Unified Communications Manager registration process in this time interval. Cisco TFTP Displays Cisco trivial file transfer protocol (TFTP) status on the Cisco Unified Communications Manager node, including total TFTP requests, total TFTP requests found, and total TFTP requests aborted. OL

74 UC Performance Monitor Dashboards TFTP Requests This counter includes all nodes in the cluster, if applicable. This counter represents the total number of file requests (such as requests for XML configuration files, phone firmware files, and audio files) that the TFTP server handles. This counter represents the sum total of the following counters after the TFTP service has started: RequestsProcessed, RequestsNotFound, RequestsOverflow, RequestsAborted, RequestsInProgress. CPU and Memory Displays information about CPU usage, virtual memory usage, memory usage, and processors for the server. CPU Usage Displays the total CPU that is consumed, and the maximum CPU that is consumed in the last 3 minutes. Virtual Memory Usage Displays the total virtual memory that is consumed, and the maximum virtual memory that is consumed in last 3 minutes. Memory Usage Displays the following information: % VM Used: Represents the percentage of system virtual memory utilization on the system. The value of the % VM Used counter is equal to the value that is derived from either of the following two equations: (Total KBytes - Free KBytes - Buffers KBytes - Cached KBytes + Shared KBytes + Used Swap KBytes ) / (Total KBytes + Total Swap KBytes) Used VM KBytes / Total VM KBytes Total: Represents the total amount of memory in the system in kilobytes. Used Free Shared Represents the amount of system physical memory that is in use, in kilobytes, in the system. The value of the Used KBytes counter is equal to the value that is derived from the following equation: Total KBytes - Free KBytes - Buffers KBytes - Cached KBytes + Shared KBytes The Used KBytes value is different from the Linux Used value that is shown in top or free command output. The used value that is shown in Linux top or free command output is equal to Total KBytes - Free KBytes, and it also includes the sum of Buffers KBytes and Cached KBytes. Represents the total amount of memory that is available in the system, in kilobytes. Represents the amount of shared memory in the system, in kilobytes. 72 OL

75 UC Performance Monitor Dashboards Buffers Cached Represents the capacity of buffers in the system, in kilobytes. Represents the amount of cached memory, in kilobytes. Total Swap Represents the total amount of swap space, in kilobytes, in the system. Used Swap Represents the amount of swap space, in kilobytes, that is in use on the system. Free Swap Represents the amount of free swap space, in kilobytes, that is available in the system. Processors Displays the following information: Processor: Instance of the processor. For example, a a quad-core CPU has four processors: 0, 1, 2, and 3. % CPU: The processor's share of the elapsed CPU time excluding the idle time since last update, expressed as a percentage of CPU time. User: Displays the percentage of CPU utilization that the CPU spent executing at the user level (application). Nice: Displays the percentage of CPU utilization that the CPU spent executing at the user level with nice priority. System: Displays the percentage of CPU utilization that the CPU spent executing at the system level (kernel). Idle: Displays the percentage of time that the CPU or CPUs were idle and the system did not have an outstanding disk I/O request. IRQ: Displays the percentage of time that the processor spent executing the interrupt request, which is assigned to devices for interrupt, or sending a signal to the computer when it finished processing. Soft IRQ: Displays the percentage of time that the processor spent executing the software interrupt (softirq), which means that task switching is deferred until later to achieve better performance. IO Wait: Displays the percentage of time that the CPU or CPUs were idle, during which the system had an outstanding disk I/O request. Disk Usage Displays information about disk usage on the node. It has the following dashlets: Common Partition Usage, Swap Partition Usage, Spare Partition Usage, Shared Memory Partition Usage, Active Partition Usage, Boot Partition Usage. OL

76 UC Performance Monitor Dashboards Each of the dashlets displays the following information: Used Represents the percentage of disk space that is in use on this file system. Max Past 3 min Represents the percentage of disk space that is in use on this file system in the past 3 minutes. Used Space Represents the amount of disk space, in megabytes, that is in use on this file system. Total Space Represents the amount of total disk space, in megabytes, that is on this file system. The number in this counter may differ from other total size values for disk space that you may see on the system, because the value of the Total Mbytes counter is the sum of Used Mbytes performance counter and the Free value that is shown in the CLI (show status) output. The Total Mbytes value is less than this CLI output for Total, which includes the minfree percentage of reserved file system disk blocks. Keep a minfree reserved to ensure a sufficient amount of disk space for the file system to operate at high efficiency. CTI Manager Displays information about the devices and applications that interfaces with the CTI Manager. Its displays the following information Open Devices The number of devices open by all applications that are connected to CTI Manager. Open Lines The number of lines open by all applications that are connected to CTI Manager. CTI Connection The number of applications that are connected to CTI Manager. CM Links The active Unified Communication Manager link to CTI Manager. Heartbeat Displays heartbeat information for the Cisco Unified Communications Manager and Cisco TFTP service. CM Heartbeat Current Value represents the heartbeat of Unified Communications Manager. This is an incremental count that indicates that Unified Communications Manager is running. If the count does not increment, then Unified Communications Manager is down. Past 1 min displays the delta; a value of 0 indicates that Unified Communications Manager is down. 74 OL

77 UC Performance Monitor Dashboards TFTP Heartbeat Current Value represents the heartbeat of the TFTP server. This is an incremental count that indicates that the TFTP server is running. If the count does not increment, then the TFTP server is down. Past 1 min displays the delta; a value of 0 indicates the TFTP server is down. SIP Activity Displays SIP activity on Cisco Unified Communications Manager, including summary requests, summary responses, summary of failure responses in, summary of failure responses out, retry requests out, and retry responses out. SIP Activity includes all nodes in the cluster, if applicable. Summary Requests Displays the summation of total number of SIP request messages received by the SIP device, including retransmissions + the total number of SIP request messages sent out (originated and relayed) by the device. Where a particular message is sent more than once, for example as a retransmission or as a result forking, each transmission is counted separately. Summary Responses Displays the summation of total number of SIP response messages received by the SIP device, including retransmissions + the total number of SIP response messages sent (originated and relayed) by the SIP device, including retransmissions. Summary Failure Responses In Displays the summation of total number of 4xx class SIP responses received by the SIP device, including retransmissions. This class of responses indicates request failure by a SIP device that provides a client function + the total number of 5xx class SIP responses received by the SIP device, including retransmissions. This class of responses indicates failure responses received by a SIP device that provides a client function + the total number of 6xx class SIP responses received by the SIP device, including retransmissions. This class of responses indicates failure responses received by a SIP device that provides a client function. The responses generally indicate that a node has definitive information about a particular called party, not just the particular instance indicated in the Request-URI. Summary Failure Responses Out Displays the summation total number of 4xx class SIP responses sent by the SIP device, including retransmissions. This class of responses indicates request failure by a SIP device that provides a node function + the total number of 5xx class SIP responses sent by the SIP device, including retransmissions. This class of responses indicates failure responses sent by a SIP device that provides a node function + the total number of 6xx class SIP responses sent by the SIP device, including retransmissions. This class of responses indicates failure responses sent by a SIP device that provides a node function. The responses generally indicate that a node has definitive information about a particular called party, not just the particular instance indicated in the Request-URI. Retry Requests Out Displays the total number of Request retries that have been sent by the SIP device. OL

78 UC Performance Monitor Dashboards Retry Responses Out Displays the summation of the total number of Final Response retries that have been sent by the SIP device + the total number of non-final Response retries that have been sent by the SIP device. Process Displays information about the processes that are running on the node. Process PID & CPU Status Name of the process. The task's unique process ID, which periodically wraps, although it never restarts at zero. The task's share of the elapsed CPU time since the last update and is expressed as a percentage of total CPU time. The task's process status: 0: Running 1: Sleeping 2: Uninterruptible disk sleep 3: Zombie 4: Traced or stopped (on a signal) 5: Paging 6: Unknown Shared Memory Nice VmRSS The amount of shared memory, in kilobytes, that a task is using. Other processes could potentially share the same memory. The nice value of the task. A negative nice value indicates that the process has a higher priority while a positive nice value indicates that the process has a lower priority. If the nice value equals zero, do not adjust the priority when you are determining whether to run the task. The virtual memory (Vm) resident set size (RSS) that is currently in physical memory in kilobytes, including Code, Data, and Stack. 76 OL

79 UC Performance Monitor Dashboards VmSize The total amount of virtual memory, in kilobytes, that the task is using. It includes all code, data, shared libraries, and pages that have been swapped out: Virtual Image = swapped size + resident size. VmData The virtual memory usage of the heap for the task in kilobytes. Thread Count The number of threads that are currently grouped with the task. The negative value 1 indicates that this counter is currently not available because thread statistics (including all performance counters in the Thread object as well as the Thread Count counter in the Process object) have been turned off because the system's total processes and threads have exceeded the default threshold value. Datastack Size The stack size for task memory status. Page Fault Count The number of major page faults that a task encountered that required the data to be loaded into memory. Database Summary Provides connection information for the server, such as the change notification requests that are queued in the database, change notification requests that are queued in memory, the total number of active client connections, the number of devices that are queued for a device reset, the number of replicates that have been created, and the status of the replication. Change Notification Requests Queued in DB Displays the number of records from the DBCNQueue table. Change Notification Requests Queued in Memory Displays the number of change notification requests that are queued in memory. Total Number of Connection Clients Displays the number of change notification requests that are queued in memory. Replicates Created Displays the number of replicates that were created by Informix for the DB tables. Every table contains at least one replicate. This counter displays information during Replication Setup. OL

80 UC Performance Monitor Dashboards Replication Status Displays the state of replication: 0 = Initializing ReplTask thread 1 = Replication setup script fired from this node 2 = Replication is good; replication is set up correctly and most of the tables in the database should be in sync for all nodes of the cluster Note Run the CLI command utils dbreplication status to see if any tables are out of sync 3 = Replication data transfer is bad in the cluster Note When the counter shows a value of 3, replication is bad in the cluster. This value does not mean that replication is bad on that particular node. Run the CLI command utils dbreplication status find out where and what exactly is broken. 4 = Replication Setup did not succeed Phone Summary Displays information about the Cisco Unified Communications Manager node, including the number of registered phones, registered SIP phones, registered SCCP phones, partially registered phones, and the number of failed registration attempts. This includes all nodes in the cluster, if applicable. Registered Devices Displays the number of SIP phones, SCCP phones and total phones that are registered in Unified Communications Manager. The Past 1 Minute column displays the delta of phones that were registered or unregistered in the past 1 minute. Registration Issues Displays the registration issues of all the phones in Unified Communications Manager. The Failed Attempts tab displays the number of attempts that are failed to register phones; the Partial Registration tab displays the number of partial registrations of phones. The Past 1 Minute column displays the delta of values in the past 1 minute. Device Summary Displays information about the Cisco Unified Communications Manager node, including the number of registered phone devices, registered gateway devices, and registered media resource devices. Device Summary includes all nodes in the cluster, if applicable. 78 OL

81 UC Performance Monitor Dashboards Registered Phone Devices Displays the total phones registered in Call Manager cluster; Past 1 Minute displays the delta of total registered phones in the past 1 minute. Registered Gateway Devices Displays the total gateways (FXS, FXO, T1CAS and PRI) registered in Unified Communications Manager cluster; Past 1 Minute displays the delta of total registered gateways in the past 1 minute. Registered Media Resource Devices Displays the total media resources (MOH, MTP, XCODE and CFB) that are registered in Unified Communications Manager cluster; Past 1 Minute displays the delta of total registered media resources in the past 1 minute. Registered Other Station Devices Displays the total other station devices registered in Unified Communications Manager cluster; Past 1 Minute displays the delta of total other station devices in the past 1 minute. Device Services Displays the details of all different types of devices: Phones, Gateways, Media Resources, and Other Station devices. Details for each type are displayed separately. IM and Presence Summary PE Active JSM Sessions The Number of Active JSM Sessions performance counter contains the number of client emulation sessions between the Cisco Presence Engine and Cisco XCP Router. The value of this counter should always equal the number of licensed users on the box. Past 1 Minute displays the delta of counter value in the past 60 seconds. Active Calendar Subscriptions The Number of Active Calendar Subscriptions performance counter contains the number of calendar subscriptions that are currently active on the box. Past 1 Minute displays the delta of counter value in the past 60 seconds. Incoming SIP Subscriptions The Number of Active Inbound SIP Subscriptions performance counter contains the current number of active inbound SIP subscriptions that are maintained by the Cisco XCP SIP Federation Connection Manager service on the IM and Presence Service node. Monitor this counter if the IM and Presence Service node is configured for SIP Interdomain Federation or SIP Intradomain Federation. Past 1 Minute displays the delta of counter value in the past 60 seconds. OL

82 UC Performance Monitor Dashboards Outgoing SIP Subscriptions The Number of Active Outbound SIP Subscriptions performance counter contains the current number of active outgoing SIP subscriptions being maintained by the Cisco XCP SIP Federation Connection Manager service on the IM and Presence Service node. Monitor this counter if IM and Presence Service node is configured for SIP Interdomain Federation or SIP Intradomain Federation. The total combined count of SubscriptionsOut and SubscriptionsIn must not rise above 260,000 on any single IM and Presence Service node. Past 1 Minute displays the delta of counter value in the past 60 seconds. Total Ad Hoc Chat Rooms The Total Ad Hoc Group Chat Rooms performance counter contains the total number of ad hoc chat rooms that are currently hosted on the node. Note Ad hoc chat rooms are automatically destroyed when all users leave the room, so this counter rises and falls in value regularly. Past 1 Minute displays the delta of counter value in the past 60 seconds. Total Persistent Chat Rooms The Total Persistent Chat Rooms performance counter contains the total number of persistent chat rooms that are hosted on the node. The room owner must explicitly destroy persistent chat rooms. This counter can be monitored to identify whether the total number of persistent chat rooms is very large and also to help identify whether some persistent chat rooms are not being used regularly anymore. Past 1 Minute displays the delta of counter value in the past 60 seconds. Cisco Jabber Summary Jabber Login Failures Represents the number of failed login requests that were received by the Cisco Simple Object Access Protocol (SOAP) interface. After 1 minute, the counter displays the delta of counter value in the last 60 seconds. Current Connected Jabber or XMPP Clients Contains the current number of XMPP clients that are connected to the Cisco XCP Connection Manager on an individual IM and Presence Service server. This number rises and falls based on the usage patterns of your deployment. Further investigation may be required if this number is higher than expected for your user base. After 1 minute, the counter displays the delta of counter value in the last 60 seconds. IM Packets Since Last Restart Provides the total number of IM packets that are handled by the IM and Presence Service node across all users. After 1 minute, the counter displays the delta of counter value in the last 60 seconds. 80 OL

83 Creating Custom UC Performance Monitor Dashboards IM Packets in Last 60 Seconds The total number of IM packets that are handled by the IM and Presence Service node across all users in the past 60 seconds. This counter is reset to zero every 60 seconds. The same rules for counting IM packets apply as for TotalMessagePackets. Monitor this counter to help identify the busy IM hours in your organization. After one minute, the counter displays the delta of counter value in the last 60 seconds. Learned Patterns Learned Pattern reports and Service Advertisement Framework (SAF) forwarder reports support the Call Control Discovery feature. When you configure the Call Control Discovery feature, Cisco Unified Communications Manager advertises itself and its hosted DN patterns to other remote call-control entities that use the SAF network. Likewise, these remote call-control entities advertise their hosted DN patterns, which Unified Communications Manager can learn and insert in digit analysis. Column Pattern TimeStamp Status Protocol AgentID IP Address ToDID CUCMNodeId Description Displays the name of the learned pattern from the remote call-control entity. Displays the date and time that the local Unified Communications Manager marked the pattern as a learned pattern. Indicates whether the learned pattern was reachable or unreachable. Displays the protocol for the SAF-enabled trunk that was used for the outgoing call to the learned pattern. If the remote call-control entity has QSIG tunneling configured for the SAF-enabled trunk, the data indicates that QSIG tunneling was used; for example, EMCA is listed along with H.323 in this column. Displays the name of the remote call-control entity that advertised the learned pattern. Displays the IP address for the call-control entity that advertised the learned pattern; Displays the port number that the call-control entity uses to listen for the call. Displays the PSTN failover configuration for the learned pattern. Displays the ID from the local Unified Communications Manager node. Creating Custom UC Performance Monitor Dashboards You can add customized dashboards in the home page; either in the graphical view (limited to 6 counters) or tabular view (up to 50 counters). By default, the graphical view is enabled. The Min, Max, and Avg values for the custom dashboard are also displayed. OL

84 Performing Device Search In graphical view, the graph depicts the current values of a counter for every few seconds or minutes, as specified in the polling interval. You can also mouse over the various red points in the line to view the value of the counter as a tool tip. Note Click See Average to view the Min., Max., and Avg. values for the dashboard in the graphical view. You can also: Add events to the custom dashboard. Switch between the graphical and tabular views. Note When you create customized dashboards in the graphical view or when you switch from tabular view to graphical view using the edit option, ensure that the number of counters you select is less than or equal to 6. If the number of counters is more than 6, you need to remove the excess counters to view the dashboard in the graphical view. If you have deployed Prime Collaboration in MSP mode, all of the dashlets in the custom dashboard display public (managed) IP. Also, note that while creating a custom dashboard, all nodes/counters in the cluster display the public (managed) IP. To create custom dashboards: Step 1 Step 2 Step 3 Step 4 Step 5 Step 6 Step 7 Choose the product and the cluster from the Cluster drop-down list. Click the + button adjacent to the Dashboard drop-down list. In the Create Custom Dashboard window, enter the dashboard name and the polling interval. Select the desired performance counters from the Available Counters drop-down. Select the attribute for the counter you selected, from the attribute drop-down list. Add the instance value from the Instance drop-down, if the counter is instance-based. Select the server from the Server drop-down. Click Create. You can also edit or delete a custom dashboard you created, using the Edit and Delete buttons. For information about creating a new performance counter event, see Creating Custom Alerts, on page 64. When you create custom events from the custom dashboards, you need not provide the cluster details. Performing Device Search You can search for devices within a cluster, based on the search criteria you specify. If you have deployed Prime Collaboration in MSP mode, search results depend on the global customer selection. To, go to Operate > UC Cluster Status. You can view the devices based on the saved search criteria you select from the Saved Searched drop-down. 82 OL

85 Performing Device Search Note The table displays only 200 entries. Therefore, we recommend that you use the filter criteria to the best use to ensure that you get the desired result. To create a new search criteria: Step 1 Go to Operate > UC Cluster Status.. Step 2 Step 3 Click New Search. Enter the Criteria Name, Device Type, and Polling Interval If you choose the devices only configured in the DB option, you cannot specify the polling interval or the other parameters, except the device type. This option displays the devices in the Unknown state. The same user cannot use the same search criteria name for the same cluster. The same user can have the criteria name for a different cluster. Step 4 Step 5 For Custom Search, specify the status within call Manager, Device Model, and the Search with Name parameters. The search criteria available vary based on the device type you chose. Click Search. The search results are displayed in window. The results get refreshed based on the polling interval you specify. You can launch the Unified CM from the IP address link available in the IP Address column. The search results also provides the following information: App Info The information about the application. Configuration This applies to H.323 Gateways. Port/Channel Status Shows all the configured port or channels and their status. You can set the polling interval to refresh this view. This search does not get saved in the database and cannot be retrieved after you log out, unless you save the search. To save the search, click the save icon. You can also edit a search that you had saved. You can delete a search that you had created, even if it is unsaved. Use the edit or delete icon to edit/delete the search. Fields that you cannot edit are disabled. You can also view the destination status for SIP trunks. Select SIP Trunk from the Device Type drop-down, enter the Criteria Name, Polling Interval and click Search. Hover your mouse over the Name column and click the quick view icon to launch the Destination Details pop-up window. Note If you want to save the search criteria in Internet Explorer 9.0, you must enable Always Refresh from Server option in the browser. To enable this option, press the F12. In the Internet Explorer tool bar menu, choose Cache > Always refresh from server. OL

86 Performing Device Search 84 OL

87 CHAPTER 9 Monitoring Alarms and Events Choose Operate > Alarms & Events to access the Alarms & Events page appears. You can filter alarms and events based on groups, using the Device Group pane on the left of the page. The page provides information on the following: Alarms and Alarm Summary, page 85 Events, page 88 Viewing Call Events, page 89 Alarms and Alarm Summary You can view Alarms and Alarm Summary pages through Operate > Alarms & Events. The Alarms tab displays the following information for each alarm in the Alarm browser: Severity 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. To view events associated with an alarm, rest the mouse over the alarm severity, and click the quick view icon. The Events for Alarm appears, displaying the following details: Description Alarm description. Status Device that triggered the alarm. Time Date and time when the alarm occurred. This summary windows lists only the five latest events. To see the complete list, see Event History. In the Events for Alarm, you can click: The See Event History linkto display the events associated with the selected alarm. The Monitor Endpoint or Monitor Session link to launch the Endpoints Monitoring or Sessions Monitoring page. This link appears only for session and endpoint alarms. OL

88 Alarms and Alarm Summary Clipboard icon/is Annotated Status Indicates the alarm has user notations. Indicates the status of the alarm. It shows the alarm clearing status details. Alarm Name Name of the generated alarm. Rest the mouse over the alarm name and the Quickview icon that appears, to view details of the alarm selected. Device Name Displays the name of the device that triggered the alarm. Device IP Displays the IP address of the device. You can launch the endpoint or the infrastructure device log in page using the link. Component Name Device name, or the name of component such as a device pool, an interface. Last Updated Owner Displays the date and time when the alarm occurred. Displays the name of the person to whom this alarm is assigned. (If a name was entered.) Description Category Displays a short description about the alarm. Displays the category of alarm. For example: session, endpoint, service infrastructure. Private IP address If you have installed Prime Collaboration in MSP mode, private IP address of the device is displayed. Note If you have installed Prime Collaboration in MSP mode, the customer that the device belongs to, is displayed for both Alarms and Alarm Summary. Overall, the alarm browser allows you to: 86 OL

89 Alarms and Alarm Summary View events associated with an alarm Rest the mouse over the icon next to alarm status for the pop-up 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. Delete Alarm Check the desired check box, click Delete. Set up Notification Check the desired check box, click Notification. Enter the recipient addresses, comments, and subject, then click Submit. See Cisco Prime Collaboration Supported Alarms and Events, 10.5 for a list of supported alarms and events. Alarm Summary Alarm Summary provides a summary of the alarms for each device. The following factors distinguish Alarm Summary from Alarms: You cannot launch Quickview in Alarm Summary 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: Severity Alarm severity icon. Indicates the severity of the alarm. Last 15 Minutes 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 Device name or IP address. Device IP Type Device IP. Click on the quick view icon to launch the Device 360 View. Device type. OL

90 Events Severity Columns Critical Total number of critical alarms. Major Total number of major alarms Minor Total number of minor alarms Warning Total number of warning alarms. Last Update Time 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. Private IP address If you have installed Prime Collaboration in MSP mode, private IP address of the device is displayed. Events The Events tab displays the following information: ID Event unique identification number. Severity Status 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. Device Name The name of the event. Rest your mouse over the event name to view the event details. Device IP Displays the IP address of the device. You can launch the endpoint or the infrastructure device using the link. Component Name Device name, or the name of component such as a device pool, an interface. 88 OL

91 Viewing Call Events Last Updated Displays the date and time when the event occurred. Category Displays the alarm assigned category, such as sessions, endpoints, and so on. Description Description of the event. Private IP Address If you have installed Prime Collaboration in MSP mode, the private IP Address of the device is displayed. Note Click the refresh icon to view the latest list of events raised. If you have installed Prime Collaboration in MSP mode, you can see the customer to which the device belongs to. At any point, to see the Alarm Browser or Alarm Summary, click the links available at the bottom right. Viewing Call Events 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. To view call events: Step 1 Step 2 Step 3 Choose Operate > Device Work Center. Select a device, and Click Call Events. Note Call events are displayed only for Cisco VCS, MXP, MCU devices, and codecs. The Call Events window displays the following details: For MXP and Codecs: Start Time The call start time Remote Site The site to which the call was made. OL

92 Viewing Call Events Call State Duration Call Direction Whether an incoming or outgoing call. Call Protocol H323/SIP Encryption Mode Cause Bandwidth Call ID For VCS: Time Source Address Source Alias Destination Address Destination Alias Duration Call State Call Protocol Bandwidth Call Type 90 OL

93 PART V Performing Diagnostics Collecting Logs From Unified Communications (UC) Components, page 93 Analyzing Call Signaling, page 99

94

95 CHAPTER 10 Collecting Logs From Unified Communications (UC) Components Prime Collaboration enables you to collect call logs to identify faults in the calls (for UC components). This feature enables you to troubleshoot issues in the calls. You can use the Call Signaling Analyzer feature to further zoom in on the collected calls and isolate faults in the messages. For more information on the Call Signaling Analyzer feature, see Analyzing Call Signaling, on page 99. It helps you to: Reduce cost of troubleshooting issues in calls. Reduce time for troubleshooting issues in calls. The following is required or supported by this feature: Maximum disk size required for this 25 GB for small, 50 GB for medium, and very large profiles feature. Maximum number of devices from 100 which log collection to be done at a time. Maximum number of log collection 3 jobs to be run at the same time Log Collection Center, page 93 Log Collection Center Prime Collaboration enables you to collect call logs from the Log Collection Center (LCC) available at Operate > Log Collection Center for the following Unified Communications (UC) components: OL

96 Log Collection Center Device Type Unified Contact Center Enterprise (UCCE) Cisco Voice Portal (CVP) Cisco Unified Communications Manager (CUCM) IOS Gateways (TDM, CUBE, VXML GWs) Supported Version in Advanced Mode 9.x and later 9.x and later 9.x and later 15.1(4)M and later Components/Type Of Log Router, and Peripheral Gateway All Call logs, and SDL logs Output of show logging command Note This feature is only available if you have deployed Prime Collaboration in Enterprise mode. If you are using the Prime Collaboration Assurance - Standard mode, you can add CVP and UCCE to Log Collection Center. Also, you can collect logs for a single cluster only. This feature also provides logs for devices which are not in Device Work Center. Devices Pane The following information is available in the Devices pane. Host Name - Host Name of the Device IP Address - IP Address of the Device Device Type Managed in DWC - Shows whether the device is in Managed state in Device Work Center or not. If the column value is No, it means that the device is not in Device Work Center and only added in Log Collection Center, or the device is not in Managed state in Device Work Center. Connectivity Status - Shows whether the device can be accessed with the credentials provided in LCC. Add a Device To add a device, click Add Device. Fill the following information in the Add Device dialog box: Field Name Host Name or IP Address Transport Protocol Port Number Time Zone Description - The transport protocol for IOS gateways is SSH and Telnet. The transport protocol for other devices is HTTPS. Ranges from 1 to By default a port number is added. You can modify it if required. Select the device time zone. If the time zone is not correct, then the time stamp of message is not shown correctly in analysis and for live log collection, the call records will not display correct results. 94 OL

97 Log Collection Center Field Name Credentials Description The associated protocol with a particular device type appears by default. You have to fill in the username and password. When CVP OAMP server is added, all associated devices are added to the Log Collection Center. When CUCM (8.x, 9.x, 10.x) is added its associated subscribers are also added. Log collection is not supported for the CVP OAMP server device itself, but it is supported for devices added through CVP OAMP server. Note Devices that are discovered through Device Work Center need not be added again as they are synced periodically or manually as required. Sync a Device with Device Work Center To add or update device(s) (UC components) of Device Work Center (DWC) to Log Collection Center, you can select a device, all devices of a device group and then click Sync with Device Work Center. The devices in the Log Collection Center and DWC are synced in the following ways: Automatically: Devices from DWC are synced every hour. Manually: When you click the Sync with Device Work Center button, the UC components from DWC are added to the list of devices in the Log Collection Center. Periodic sync happens every hour. Sync does not remove devices from LCC if the devices in DWC are deleted. If a new device is added in LCC or any update to a device happens then the Connectivity Status is updated after the sync. Note The direction of the sync is only from Device Work Center (DWC) to Log Collection Center. The credentials from LCC are overwritten by the credentials in DWC after a sync. Thus it is recommended to keep the credentials same across DWC and LCC. Only the devices in Managed state in DWC are synced. If a device in DWC is deleted but not deleted in LCC, you can still perform log collection in LCC. If the IOS gateway in DWC does not have CLI credentials, it will not be synced to LCC. Group a Device In order to collect log from the same type of UC components on a same-time, you can create custom group of UC components and collect call logs by selecting the device group. Predefined groups can not be added, edited, or deleted, and the devices in the groups cannot be modified too. You can create, edit or delete user defined groups. You can add or delete devices of the user defined groups. You can do the following: Task Create a Group Details Click Operate > Log Collection Center > Group > Create New. OL

98 Log Collection Center Task Edit a Group Delete a Group Add Devices to Group Delete Devices from Group View Devices in Group Details Click Operate > Log Collection Center, select a device or a group, and then click Group > Edit Group. Click Operate > Log Collection Center, select a device or a group, and then click Group > Delete Group. Click Operate > Log Collection Center, select device(s), and then click Group > Add to Group. Click Operate > Log Collection Center, select device(s), and then click Group > Delete from Group. Select a group from the Device Group Center. The devices of that group are displayed in the Devices pane. Other Tasks You can perform the following tasks from the Device pane on the Log Collection Center page. Select device(s) from the Devices pane for which you want to perform the task, and then do the following as required. Tasks Edit Device Details Modify Credentials Delete a Device Rediscover Modify Time zone Details Click the Edit button to edit any user-added information of the device. If the device is managed in DWC, that is, the value of the column "Managed in DWC" is "Yes" then you cannot edit the device. Click the Modify Credentials button to edit the port number, timezone, or credential details only of multiple devices. You cannot modify the device type. Click the Delete button to delete any device from LCC. If the device is managed in DWC, that is, the value of the column "Managed in DWC" is "Yes" then you cannot delete the device. Click the Rediscover button to update or add back any devices associated with the publisher. CUCM subscribers are populated with the same credentials as the publisher, if added in LCC using the rediscover button. Click the Modify Time Zone button to modify the device time zone. Prime Collaboration server time zone is shown by default. Test Connectivity of a Device Select a device and click the Test Connectivity button to test if the device is accessible with credentials provided. A message appears to notify you about the result. Also the value of the column "Connectivity Status" is updated accordingly. Troubleshooting Test Connectivity If test connectivity fails check the following: Port number Credentials of the device and ensure they are same as DWC. 96 OL

99 Log Collection Center Ping from the Prime Collaboration Assurance Server to the device is successful. Collect Call Logs Log collection is on-demand. Select a single device or devices in a group and click the Collect Logs button to collect logs. The Collect Logs dialog box appears. Fill the required information. The job name and file name are auto-populated, but you can modify it too. The time zone you select here will be used to collect the logs. Note Ensure that you do not modify the extension.zip in the file name. Sometimes the downloaded log files will have.gz and.gzo as extension. Winrar will not unzip.gzo files, thus you need to have a compatible conversion utility to unzip these files. Click Run. A message notifies you that the job is triggered or not. The job is listed under the Log Collection Jobs pane. The Progress Status column also shows the number of devices for which the logs are downloaded out of the total number of devices selected for log collection. For example 2 of 3. You can select the job and collect the logs by clicking the Download to local button. You can delete the job using the Delete button under the Log Collection Jobs pane. These jobs are also listed under the Job Management page (Administration > Job Management), however you cannot download the log file from this page. Note If you want more information on log collection jobs, see where IP address is the Prime Collaboration server IP address. This URL can be viewed by users with admin role and will help you troubleshoot issues related to log collection. OL

100 Log Collection Center 98 OL

101 CHAPTER 11 Analyzing Call Signaling The Call Signaling Analyzer enables you to isolate faults in calls in your deployment. Call Signaling Analyzer analyzes calls at a high level and then drills down to a lower level within the components themselves using the same tool. The Call Signaling Analyzer helps you to: View the high level view of the signaling path that includes originator, intermediate destination and final destination of calls to know the complete path of the call. View the signaling call ladder diagram to isolate any issues in the call. Drill down to individual components in that call to fix errors. View error messages, and possible root causes and recommendations. Automatically identify and highlight signaling errors and capability mismatches. Add any additional logs of UCCE to generate the Call Ladder Diagrams for UCCE deployments. It analyzes call logs received from the UC components: UCCE CVP CUCM IOS Gateway Note This feature is not available if you have deployed Prime Collaboration in MSP mode. The Advanced mode allows log analysis from any of supported devices (CUCM, CVP, IOS Gateway, UCCE) while the Standard mode allows CUCM devices from a single managed cluster only. Only SIP over TCP messages are parsed. For CUCM - If both SDL/SDI and Call Logs are available then calls are parsed from SDL/SDI logs. If data is not available from the SDL/SDI logs then call logs are used. OL

102 Supported Call Flows The following is required or supported by this feature: Maximum disk size required for this feature. Maximum file size that can be imported. Maximum number of calls that can be selected for ladder generation at a time. Maximum number of devices from which log collection to be done at a time. Maximum size of logs that can be parsed. Maximum number of call records displayed on the UI. 18 GB for small, 35 GB for medium, and very large profiles 0.5 GB for small, and 1 GB for other profiles GB for small, and 1 GB for other profiles. 10,000 Supported Call Flows, page 100 Creating a Call Ladder Diagram, page 102 Understanding a Call Ladder Diagram, page 103 Supported Call Flows The Call Trace feature enables you to analyze SIP-based calls. Note The correlation of analysis of all the call legs of the same call (end-to-end call analysis) is only supported for Call Flow 1 and 2. To support end-to-end call analysis for these calls (Call Flow 1 and 2), the CISCO-GUID (SIP Message property) should be same across different products. End-to-end call analysis is not supported for the other call flows except Call Flow 1 and OL

103 Supported Call Flows It supports the following call flows: Figure 2: Call Flow 1 Figure 3: Call Flow 2 Figure 4: Call Flow 3 Figure 5: Call Flow 3 A Figure 6: Call Flow 4 OL

104 Creating a Call Ladder Diagram Figure 7: Call Flow 5 Figure 8: Call Flow 5 A Figure 9: Call Flow 6 Creating a Call Ladder Diagram Step 1 Step 2 Select a data source. Choose from the following options: Live Log Collection - The Group Type field appears. Click on the drop-down arrow, and select a device group from the Device Group dialog box. The devices available for the selected device group appear. Select a device from the options that are listed. Note You can select a single or multiple devices. Local File System - You can select a log file from the options that appear. It includes log files collected from Log Collection Center and also from Live Log Collection. You can also click Import, to import the file(s) from your local file. Browse to the zipped log file through the Import dialog box. The imported file is updated in the options available under Log File System. For more information on Log Collection Center, see Log Collection Center, on page 93 (Optional) Filter Calls - You can search for a call from the files selected from the preceding data sources, using the following parameters: Field Calling Number/URI Called Number/URI Direction of Call Disconnect Code Call ID Description A SIP-URI is the SIP addressing schema to call another person through SIP. By default ALL listed. By default ALL listed. - The error code for that call, for example OK. An ID that uniquely identifies calls in a Cisco UC product. 102 OL

105 Understanding a Call Ladder Diagram GUI ID Time Zone Heartbeat Messages Time Range Device Type to Parse An ID that uniquely identifies calls across product. The Prime Collaboration server time zone. By default it displays the Prime Collaboration server time zone. This includes the heartbeat messages - OPTIONS, and NOTIFY. If you select this field, performance of this feature may be adversely affected. You can specify the time range. if you have selected the Local File System, the option of past time details will not be available to you. The device types that are part of the selected logs are listed here. You can select a particular device type to filter the calls that involve that device type. Step 3 Step 4 Click the Retrieve Calls button. If you have selected the Live Log Collection option, Log Parsing In Progress status bar appears. After the log parsing process in completed, the Log Download In Progress status bar appears, indicating the process completeness. If you have selected the Local File System option, the Log Download In Progress status bar appears directly. If you try to parse an uploaded or existing log file, the Log Analysis In progress status bar does nor appear as that file is already parsed. The IOS Gateways and CUCM call logs can have older data. You need to apply appropriate filters to get the specific time range call list. The Call List appears. Select the calls from this list, and click on Show Ladder Diagram for those calls. The Call Ladder diagram page appears displaying the Call Ladder diagram for the complete call. You can also click on the Show Transition Diagram button when the call list appears to view the transitions. Filter a Message in the Call Ladder Diagram You can further create a call ladder diagram for a specific message. Step 1 You can also filter a message in the call ladder diagram on the following parameters: Components - The IP addresses of the devices (senders and receivers) in the call. Key Value Pair - Attributes of the Call. Step 2 Select the parameters and click Apply. The diagram will be generated according to the filters you have applied. Understanding a Call Ladder Diagram The Call Ladder diagram helps to visualize the SIP signaling for selected calls (both line and trunk side). You can see the following: Direction of the messages OL

106 Understanding a Call Ladder Diagram Sender and Receiver Time Stamp of the individual messages. The Call Ladder diagram shows UTC time zone only. Message and the Message Label. You can click on the message arrow to launch the Call Details pop up window that displays the details of the call. You can see the following details: Call ID Call Trace ID Sender Receiver Timestamp (UTC) Device Timezone Device IP Address Port From Received Response Code Calling Number Message Type CSEQ You can click on Click here for log to see the exact logs of that message. Each Call Id is differently color coded and the schema is represented below the diagram. The time zone is also displayed below the diagram. The search call criteria is displayed on top of the diagram. You can zoom in and zoom out the diagram. 104 OL

107 PART VI Maintaining the Server Managing Jobs, page 107 Performing Backup and Restore, page 111 Setting Log Levels, page 117

108

109 CHAPTER 12 Managing Jobs Prime Collaboration allows you to view the details of all jobs in the Jobs pane. You cannot cancel or schedule a job, or change settings, and hence these buttons are disabled. The following table lists the details that are displayed on the Jobs page (Administration > Job Management). To get the latest information, refresh the page. Job Details Field Description Name Description of the job as defined in the Prime Collaboration Assurance server. Type Indicates the type of the job. Description Describes the job. Status Status of a job. It can be: Completed Job has completed. If a job has completed, it does not necessarily mean that the job has been successful. There may be instances, where the job might have failed to run on a few devices. You can view the job details in the Job Instances table by clicking the arrow on the far left of the page. Cancelled Job has been cancelled. You can cancel a scheduled job. However, you cannot cancel a running job or a system job (for example, a polling job). Scheduled- Job is scheduled to execute at a specific time. It can be scheduled to run at a single time or at several times-recurring job. Suspended- Job is halted temporarily and can be later resumed for execution. Running Job is in execution. Owner User, who created the job. If it is a predefined system job, the creator is displayed as SYSTEM. Job Start Time Time when the job is scheduled to run for the first time. OL

110 Predefined Quick Filters Field Job End Time Next Scheduled Time Schedule Type Description Time up to which the job remains active. The job becomes inactive after running all scheduled instances of the job. Start time of a subsequent job instance. This applies to a recurring periodic job. If it is either an immediate job or one-time job, the time displayed for Job Start Time and Next Scheduled Time is the same. Whether the job is scheduled to run at a periodic frequency or once. Job Details Pane Run ID Status Status Progress Results Start Time End Time Duration If it is a periodic job, it displays the job instances count. If it is not a periodic job, it displays zero. Status of the job instance of the same job. Hover the mouse over the quick view icon in this column to view the job instance results. Indicates the stage of the job and the percentage complete. Indicates the job was successful or a failure. Start time of a job instance of the same job. End time of a job instance of the same job. Time taken between the Start Time and End time of a job instance of the same job. Predefined Quick Filters, page 108 Predefined Quick Filters Prime Collaboration supports the following predefined quick filters: Note Not all of these options are applicable in Prime Collaboration Standard mode. All Discovery Jobs An example of a discovery job is DiscoveryFrmBackgroundPathtrace. Discovery jobs are listed when you perform device discovery or rediscovery or update inventory tasks, either by using Operate > Device Work Center > Auto Discovery > Discover Devices or by selecting a device and clicking Rediscover or Update Inventory. You can view the Job Instance Result - Total Device Summary and Endpoint Device Summary by resting your mouse pointer on values in the Run ID column on the Job Details pane and clicking the Quick View icon. For more information, see the section Discovering Devices in the Cisco Prime Collaboration Assurance Guide - Advanced. 108 OL

111 Predefined Quick Filters All Polling Jobs An example of a polling job is MCU_Session_Import. Polling jobs are automatically created at system setup. All Report Jobs Report jobs are listed when a report is run. All Session Import Jobs An example of a session import job is MNGD_Synch_CtsMAN-MEETING. Sessions are imported from CTS-Manager and Cisco TMS. A separate job is created for each of these management applications. All System jobs System-generated jobs such as discovery, polling, and so on. System-generated jobs are listed as soon as the system performs a job. All User Jobs An example of a user job is RediscoverDevices_ User jobs are listed as soon as a user runs a job. Jobs Run in Last 24 Hours An example of a job run in the last 24 hours is Discovery 2012-Sep-13 10:32:40 UTC. Lists all jobs whose last complete time (the last run instance) is within the last 24 hours (from the current time). OL

112 Predefined Quick Filters 110 OL

113 CHAPTER 13 Performing Backup and Restore Performing Backup and Restore, page 111 Performing Backup and Restore Prime Collaboration Assurance allows you to backup and restore your data. You can schedule periodic backups using the Prime Collaboration Assurance user interface, or run backup commands manually by logging in to the system as an admin user (CLI user). However, you must manually run restore commands by logging in to the system as an admin user. Note CLI is supported only through SSH; telnet is not supported. The port used for Prime Collaboration Assurance is 26. The application stop cpcm command takes 10 minutes to complete execution and application start cpcm takes 10 to 15 minutes to complete execution. Overview of Backup and Restore Although the Prime Collaboration Assurance and Prime Collaboration Provisioning applications (UI) are converged, you must perform backups on the respective Assurance and Provisioning servers. If you have installed Prime Collaboration Analytics, you must first perform the backup of the analytics data before backing up the assurance data. The same sequence has to followed while restoring the data. For information about Prime Collaboration Analytics backup and restore, see Backup and Restore for Prime Collaboration Analytics chapter in Cisco Prime Collaboration Assurance Guide. For information about Prime Collaboration Provisioning backup and restore, see "Provisioning Database Backup and Restore" chapter in Cisco Prime Collaboration Provisioning Guide. Note Not all information covered in this section is applicable to Prime Collaboration Assurance Standard mode. See Standard and Advanced Prime Collaboration Assurance, on page 4 for information about feature support in Standard and Advanced modes. OL

114 Performing Backup and Restore Prime Collaboration Assurance uses the following purge policy: All session and endpoint statistics data older than one day are purged. For more details, see the section Monitoring Sessions in the Cisco Prime Collaboration Assurance Guide - Advanced. All session and troubleshooting details older than 14 days are purged every hour. For more details see the section Diagnostics for Video Endpoints in the Cisco Prime Collaboration Assurance Guide - Advanced. Call quality event history and audio/video phone audit report data older than 30 days are purged. For more details, see the section Voice Reports in the Cisco Prime Collaboration Assurance Guide - Advanced. Cleared alarms and events that are older than 14 days are purged every hour. If an alarm is purged, all associated events are also purged. Active events and alarms are not purged. For more details, see the Concepts chapter in Cisco Prime Collaboration Assurance Guide - Advanced. Jobs that are older than 14 days and have a status of completed, failed, or cancelled are purged every hour. The backup and restore service allows you back up the database, configuration files, and log files to either a remote location or a local disk. Files in following folders are backed up by the backup service: Folder Name emms database cpcm/conf cpcm/export cpcm/logs and tomcat/logs jre/lib/security Type of Data Database Configuration files Troubleshooting and endpoint utilization reports Assurance application and Tomcat log files Keystore files Note The data backup may take a long time (up to12 hours), depending on the number of managed devices in the Prime Collaboration Assurance server. It is recommended that you schedule backups during the non-business hours, because, this operation will severely slow down the Prime Collaboration Assurance UI performance. 112 OL

115 Performing Backup and Restore Creating a Repository on FTP, Disk, SFTP, or TFTP Server You must create a repository before backing up the data. By default, the backup service creates a *.tar.gpg file under the configured repository. The backed-up file is in a compressed format. The repository can be on CD-ROM, disk, HTTP, FTP, SFTP, or TFTP. Step 1 Step 2 Log in to the Prime Collaboration Assurance server with the account that you created during installation. The default login is admin. Enter the following commands to create a repository on the local: admin# config t admin(config)# repository RepositoryName admin(config-repository)# url disk: admin(config-repository)# exit admin(config)# exit Enter the following commands to create a repository on FTP server: admin# config t admin(config)# repository RepositoryName admin(config-repository)# url ftp://ftpserver/directory admin(config-repository)# user UserName password {plain hash} Password admin(config-repository)# exit admin(config)# exit Where: RepositoryName is the location to which files should be backed up. This name can contain a maximum of 30 alphanumeric characters. ftp://ftpserver/directory is the FTP server and the directory on the server to which the file is transferred. You can also use SFTP, HTTP, or TFTP instead of FTP. UserName and {plain hash} Password are the username and password for the FTP, SFTP, or TFTP server. hash specifies an encrypted password, and plain specifies an unencrypted plain text password. For example: admin# config t admin(config)# repository tmp admin(config-repository)# url ftp://ftp.cisco.com/incoming admin(config-repository)# user john password plain john!23 admin(config-repository)# exit admin(config)# exit Scheduling Backup using Prime Collaboration User Interface You can schedule and run backup for both Assurance and Provisioning from the user interface. You can use SFTP, FTP, or local connection to create backup. You must be logged in as an administrator to perform backup. OL

116 Performing Backup and Restore To create a new backup job: Step 1 Step 2 Step 3 Step 4 Step 5 Choose Administration > Backups. In the Backup page, click New. Enter a name for the backup job. If backup name is not specified, the Backup Title field is defaulted with date stamp. Select the Backup Category. Enter the Connection settings. You can use SFTP, FTP, or local connection to create backup. If you select SFTP or FTP, provide the following details: IP address of the server where the backup files need to be saved Path to the backup location Note While backing up using SFTP, ensure you provide relative path. Port (for SFTP only) Username Password Click Test to test the SFTP or FTP connection using the credentials. If you select local, specify the location to save the backup files on your local machine. For a local backup, you can specify the number of backup files to be saved, using the Backup History drop-down list. By default, the last two backup files are saved. You can save upto nine backup files. Step 6 Step 7 Step 8 Specify the backup start time and recurrence interval. The time displayed in the date picker is the client browser time. (Optional) Enter the IDs to which the backup status notification needs to be sent. You must separate the IDs using comma. Click Save. The scheduled backup job is listed in the Backup Management page. You can click Run Now to run the backup immediately. Backup using CLI Backup and Restore using CLI can be performed in the following ways: Make backup of data in a system and restore it on the same system: For more information, see Restoring on the Same System. Make backup of data in a system and restore it on a different system: For more information, see Restoring on a New System. 114 OL

117 Performing Backup and Restore Restoring on the Same System The following sections describe the process of backing up data and restoring it on the same system. Backing up Data After creating the repository, log in to the Prime Collaboration Assurance server as admin and run the following command to back up the data: admin# backup Backupfilename repository RepositoryName application cpcm Where, Backupfilename Name of the backup file (without the extension-.tar.gpg). This name can be a maximum of 100 alphanumeric characters. RepositoryName Location to which the files are be backed up. This name can contain a maximum of 30 alphanumeric characters. The following message appears after the backup is complete: % Creating backup with timestamped filename: Backupfilename-Timestamp.tar.gpg The backup file is suffixed with the time stamp (YYMMDD-HHMM) and file extension.tar.gpg and saved in the repository. For example, in case of backup on the ftp server: admin# backup assurance repository myftp application cpcm where, myftp is a repository name. Restoring Data To restore the data, Log in to the Prime Collaboration Assurance server as admin and run the following command: Restoring on a New System admin# restore Backupfilename repository RepositoryName application cpcm Where, Backupfilename is the name of the backup file suffixed with the timestamp (YYMMDD-HHMM) and file extension.tar.gpg. For example, to restore on the ftp server: admin# restore assurance_sun_feb_09_14_20_30_cst_2014.tar.gpg repository myftp application cpcm Prime Collaboration allows you to back up the data of a system and restore the data in another system in the event of total system failure. To restore the backup from another system: Ensure that the system to which data is restored must have the same MAC address as that of the system that was backed up (IP address and the hostname can be different). In the case you are unable to assign the MAC address of the original system (that was backed up) to another system, contact Cisco TAC for information on a new license file (for a new MAC address). To restore the backup from another system, log in as administrator and perform restore as described in Restoring Data. See also, Creating a Repository on FTP, Disk, SFTP, or TFTP Server. OL

118 Performing Backup and Restore Note As a post requirement, you must rediscover all the devices after restoring the data. Listing the Repository Data You can list the data within a repository, Log in to the Prime Collaboration Assurance server as admin and run the following command: admin# show repository RepositoryName For example: admin# show repository myftp assurance_sun_feb_09_14_20_30_cst_2014.tar.gpg Checking the Backup History You can check the backup history. Log in to the Prime Collaboration Assurance server as admin and run the following command: admin# show backup history 116 OL

119 CHAPTER 14 Setting Log Levels Log Levels, page 117 Log Levels Prime Collaboration Assurance supports the following log levels: Debug Helps you to debug the application. Error Indicates that the application can still continue to run. Information Indicates the progress of the application. Warning Indicates potentially harmful situations. Fatal Indicates critical logs. You can set the log levels for the following features: Note All of the following features are not applicable to Prime Collaboration Assurance Standard mode. See Standard and Advanced Prime Collaboration Assurance, on page 4for details about feature support in Advanced and Standard modes. Fault management For fault management-related issues. Performance monitor For performance statistics-related issues. Server diagnostics For the Prime Collaboration Assurance server-related issues. Discovery, session monitoring and others For discovery, session management, and web server-related issues. The log level settings can be changed from the Log Settings page (Administration > System Setup > Assurance Setup > Log Settings). OL

120 Log Levels Caution You should not change the log level settings without assistance from the Cisco Technical Assistance Center (TAC) team. The log files are also included in the backup file. 118 OL

121 APPENDIX A User Interface Prime Collaboration is a thin-client, web-based application. Prime Collaboration Standard user interface (UI) components are visible throughout the UI and enable you to set up filters, see page details in a quick view, and perform searches. Filters, page 119 Quick View, page 120 Viewing About Details, page 120 Launching the Advanced Filter and Saving Filter Criteria, page 121 Filters You can use the Filter feature to display specific information on the Prime Collaboration user interface. The Filter icon is provided wherever the data is displayed in a tabular format. The following are the types of filters available on the Prime Collaboration client: Quick Filter Advanced Filter Preset Filter The quick filter and advanced filter are case-insensitive. For these filters, you can also use the following wildcard expressions: Question mark(?) Match any one character. Asterisk (*) Match zero or more characters. Quick Filter This filter allows you to narrow down the data inside a table by applying a filter to a specific table column or columns. The operator used with this filter is Contains. To apply different operators, use the Advanced Filter option. To launch the quick filter, choose Quick Filter from the Filter drop-down menu. OL

122 Quick View User Interface To clear the quick filter, click Filter. Advanced Filter This filter allows you to narrow down the data in a table by applying a filter using multiple operators, such as Does not contain, Does not equal, Ends with, Is empty, and so on. You choose the filter pattern (table column names) and operator from the drop-down menu. In addition, you must enter filter criteria based on data available in the Prime Collaboration database. Quick View The quick view icon appears when you rest your mouse pointer on a table, specific table columns, or a topology pane. You can use quick view to cross-launch a page that you want to view in detail. In Prime Collaboration Assurance, this option is not available for administrative tasks, reports, or diagnostic views. It is available for Prime Collaboration Provisioning when you order a product. Viewing About Details This page displays the About details for Prime Collaboration Assurance. To launch this page, click at the top right corner of the User Interface. Click Assurance Information link to view the following system information details in a quick view. Build Version License Type Assurance Expiration Date (displayed in red for the last 15 days before expiry) Analytics Expiration Date (displayed in red for the last 15 days before expiry) IP Address MAC Address DB server IP Address DB server MAC Address Note DB server IP Address and DB server MAC Address fields are specific to Prime Collaboration Assurance very large OVA deployment model and does not appear in the Assurance Information link for Prime Collaboration Assurance small, medium, and large OVA deployment models. Click Licensing link to open the License Management page. 120 OL