Configuration Checklists and Tips
The following topics are included:
•Initial Configuration Checklist
•Call Classification Configuration Checklist
•Server and Client Configuration Checklist
•When You Can Expect to See Results
•Optional Configuration Checklist
Initial Configuration Checklist
Note To configure security for Service Monitor using Cisco Secure ACS, see Installation Guide for Cisco Prime Unified Service Monitor 9.0. Otherwise, configure security for Service Monitor using Common Services; for more information, see Common Services online help.
The Common Services online help is only available through the Common Services pages, which are located in the Administration tab.
To access the Common Services Online Help, you can use the following procedure:
1. Select Administration > Server Administration (Common Services) > Security. The Setting up Security page appears.
2. Click Help. The online help opens.
Table A-1 lists configuration tasks that you must complete before Service Monitor can start to monitor MOS and send traps.
For Service Monitor to supply categorized call data to Service Statistics Manager (if present in your network), you must configure call classification; see Call Classification Configuration Checklist.
To launch Operations Manager—for the purpose of obtaining more information about endpoints that appear in Service Monitor reports—you must first enter the Operations Manager server IP address in Service Monitor. For more information, see Configuring and Viewing Other Settings.
Call Classification Configuration Checklist
Call classification configuration enables Service Monitor to categorize call data and accomplish the following:
•Provide categorized call data to Service Statistics Manager to support reports by call category.
Note If Service Statistics Manager is present in your network, you must configure call classification in Service Monitor.
•Apply user-defined call categories in the CDR Call Report.
Note Only system-defined call categories are used unless you configure call classification. System-defined call categories are listed in Table 3-3.
To configure call classification, perform the following tasks:
•Configure at least one dial plan. See Configuring User-Defined Dial Plans.
•Assign a dial plan to each cluster. See Assigning a User-Defined Dial Plan to a Cluster.
•Configure gateway codes. See Configuring Gateway Codes.
Server and Client Configuration Checklist
Perform the following tasks:
•On the Service Monitor server, exclude the NMSROOT\databases directory from virus scanning. Problems can arise if database files are locked because of virus scanning.
Note NMSROOT is the directory where Service Monitor is installed on your system. If you selected the default directory during installation, it is C:\Program Files\CSCOpx.
•On Service Monitor clients, you must disable any software that you use to prevent popup windows from displaying. Service Monitor must be able to open multiple windows to display information.
When You Can Expect to See Results
After you complete the tasks in Table A-1, Service Monitor starts to receive, analyze, and present data as follows:
•Sensor records contain data for a 60-second period. Sensors, therefore, report MOS that is calculated while a call is in progress.Therefore, Service Monitor can start to generate traps while the call ensues. Similarly, sensor data can be displayed in Service Monitor reports while the call is in progress.
•CDRs are only written by Unified Communications Manager after a call has completed. Although Service Monitor might obtain data from Unified Communications Manager every 60 seconds, Service Monitor cannot generate traps until the call is over. Similarly, CVTQ data cannot be displayed in Service Monitor reports until a call has completed.
Optional Configuration Checklist
These tasks enable you to:
•Update and override the default global thresholds—one per codec—that Service Monitor uses to trigger trap generation.
•Generate most-impacted endpoint reports automatically on a nightly and weekly basis.