Table Of Contents

Configuration Checklists and Tips

Initial Configuration Checklist

Server and Client Configuration Tasks

Understanding when You Can Expect to See Results

Optional Configuration Checklist

Configuration Checklists and Tips

---

The following topics are included:

•Initial Configuration Checklist

•Understanding when You Can Expect to See Results

•Optional Configuration Checklist

Initial Configuration Checklist

Table A-1 lists configuration tasks that you must complete before Service Monitor can start to monitor MOS and send traps.

Table A-1 Initial Configuration Task Checklist

Tasks	Description and Reference
Configuring Service Monitor and Cisco Unified Communications Manager (when Present in your Network)
	Configure Cisco Unified Communications Manager (Unified Communications Manager) as described in Unified Communications Manager Configuration.
	Add credentials for Unified Communications Managers to Service Monitor; see Understanding and Setting Unified Communications Manager Credentials.
Configuring Service Monitor and Sensors (when Present in your Network)
	Add at least one TFTP server. See Configuring TFTP Servers for Sensor Configuration and Image Files.
	Set up the sensor default configuration file. See Setting Up the Sensor Default Configuration.
	Copy the binary image file to the root location on the TFTP server. See Copying the Binary Image File to the TFTP Server.
Configuring Trap Receivers
	Service Monitor can send generated SNMP traps to up to four trap receivers. See Configuring Trap Receivers.

Server and Client Configuration Tasks

On the Service Monitor server, you should 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.

Understanding 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:

•Sensors send a record to Service Monitor every 60 seconds, reporting calculated MOS 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.

•Call data records (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.

Table A-2 Optional Configuration Tasks 

Tasks	Description and Reference
Updating and Overriding Global Thresholds
	Update global threshold values. See Configuring Global Thresholds.
	Override global threshold values, providing values for selected sensors. See Configuring Sensor Groups.
	Override global threshold values, providing values for selected clusters. See Configuring CVTQ Groups.
Exporting Most-Impacted Endpoint Reports
	See Configuring Number of Endpoints and Export Settings for Impacted Endpoints Reports.
Updating Report-Related Settings and System Schedules
	Update the number of minutes that diagnostic reports search for data and the number of records to export to a CSV file. See Configuring Diagnostic Report Search and CSV Export Limit Settings.
	Update system schedules. See Configuring Low-Volume Schedule and Database Purging.