User Guide for Cisco Unified Service Monitor
Configuring Service Monitor
Downloads: This chapterpdf (PDF - 225.0KB) The complete bookPDF (PDF - 2.11MB) | Feedback

Configuring Service Monitor

Table Of Contents

Configuring Service Monitor

Configuring Trap Receivers

Understanding and Setting Data Source Credentials

Understanding Last Contact Status and When to Verify Credentials

Supported Data Source Software Versions

Adding Data Source Credentials

Adding Credentials for NAM 4.x and Later

Adding Credentials for Unified Communications Manager 5.x and Later

Adding Credentials for Unified Communications Manager 4.x

Editing Data Source Credentials

Deleting Data Source Credentials

Managing the Phone Count

Suspending and Resuming a Cluster or Sensor from Monitoring

Suspending a Cluster or Sensor

Resuming a Cluster or Sensor

Updating the Total Known Phone Count for a Cluster

Configuring Settings for Most-Impacted Endpoints Reports

Configuring and Viewing Other Settings

Configuring Diagnostic Report Search and CSV Export Limit Settings


Configuring Service Monitor


The following topics are included:

Configuring Trap Receivers

Understanding and Setting Data Source Credentials

Managing the Phone Count

Configuring Settings for Most-Impacted Endpoints Reports

Configuring and Viewing Other Settings


Note For more information, see Managing Cisco 1040s, page 4-1 and Configuration Checklists and Tips, page A-1.


Configuring Trap Receivers

For the SNMP traps that Service Monitor sends, see MIBs Used and SNMP Traps Generated, page D-1.

Procedure


Step 1 Select Configuration > Trap Receivers. The Trap Receiver Parameters page appears.

Step 2 Enter the data described in the following table.

GUI Element
Description/Action

SNMP Community String

Enter the SNMP community string for each trap receiver.

Trap Receiver n and Port fields (where n is a number from 1 to 4)

Enter up to 4 trap receivers:

Trap Receiver n—Enter the IP address or DNS name of a server. If you want to use Operations Manager to act on and display data from Service Monitor—for example to use the Service Quality Alerts dashboard—specify the IP address for the system with Operations Manager.

Port—Enter the port number on which the receiver listens for SNMP traps. The default is 162; however, a different port might be used for this purpose on this server.

When Service Monitor generates SNMP traps, it forwards them to these receivers.


Step 3 Click OK.


Related Topics

Configuring Service Monitor

Configuration Checklists and Tips, page A-1

Understanding and Setting Data Source Credentials

Service Monitor collects data from Unified Communications Manager clusters and sensors (Cisco 1040s and NAMs). You do not need to enter credentials for Cisco 1040s; to enable data collection for them, see Managing Cisco 1040s, page 4-1. However, you must:

Provide Service Monitor with credentials for NAMs and Unified Communications Manager publisher servers.

Keep the credentials up-to-date. (Any time you update credentials on a NAM or on a Unified Communications Manager publisher server, you must also update the corresponding credentials in Service Monitor.)

To view the Data Source Credentials page, select Configuration > Data Source Credentials. The Data Source Credentials page displays the information in the following table.

Columns or Buttons
Description/Action

As of

Date and time

SMTP server message

A message is displayed if no SMTP server is configured for Service Monitor. For more information, see Enabling E-Mail Notifications, page 6-7.

Display Name

The name that you entered when you added the credentials to Service Monitor.

IP Address

IP address of the cluster or the NAM. To go to the NAM software login page, click the IP address for the NAM.

Type

One of these:

CCM—Unified Communications Manager cluster.

NAM—Network Analysis Module.

Version

Unified Communications Manager or NAM software version.

For more information, see Supported Data Source Software Versions.

ID

Depends on the type:

For NAM—IP address.

For cluster—ID assigned to the cluster by Unified Communications Manager.

Last Contact Status

 

The status for each credential that Service Monitor uses to contact the data source (Unified Communications Manager cluster or NAM).

These credentials are applicable to the CCM type:

HTTP/S—Indicates status of authentication to Unified Communications Manager Administration on the publisher server; applicable to Unified Communications Manager 4.x and later. (N/A appears in this column if the data source type is NAM.)

CDR/CDRM DB—Indicates status of authentication to one of these databases:

CDR—Applicable to Unified Communications Manager 4.x.

CDRM—Applicable to Unified Communications Manager 5.x and later. Service Monitor should gain access to the credentials for this database after providing the correct HTTP/S credentials.

(N/A appears in this column if the data source type is NAM.)

This credential is applicable to the NAM type:

NAM HTTP/S—Indicates the status of authentication to the NAM. (N/A appears in this column if the data source type is CCM.)

Click any of the following statuses to open a dialog box with more information about the credential:

Success

Verifying

Waiting for Data

Failure

N/A

Note N/A indicates that the credential is not applicable for the type.

For more information, see Understanding Last Contact Status and When to Verify Credentials.

Buttons

Add—See Adding Data Source Credentials.

Edit—See Editing Data Source Credentials.

Delete—See Deleting Data Source Credentials.

Verify—Verify credentials for a selected Unified Communications Manager cluster. See Understanding Last Contact Status and When to Verify Credentials.

Refresh—Refresh the page.

Note Do not add, edit, or verify Unified Communications Manager 4.x credentials while Cisco Unified Provisioning Manager (Provisioning Manager) synchronizes with Unified Communications Manager. For more information, see Avoiding Credential Failure When Provisioning Manager Synchronization Runs in Your Network.


Related Topics

Deleting Data Source Credentials

Unified Communications Manager Configuration, page 3-1

Supported Data Source Software Versions

Understanding Last Contact Status and When to Verify Credentials

The Data Source Credentials page displays the status of the last contact between Service Monitor and each data source. The status is a clickable link that opens a dialog box with more information that:

Includes the last time Service Monitor tried to contact the data source and the last time Service Monitor was successful in making contact.

Might indicate that Service Monitor is discarding data. Service Monitor discards data when receiving old data from Unified Communications Manager 5.x and later. This can happen after the connection between Service Monitor and Unified Communications Manager is reestablished after a break. Unified Communications Manager first sends older files to Service Monitor.


Note For Unified Communications Manager 7.x and later, you can prevent older data from being sent to Service Monitor. For more information, see Adding Service Monitor to Unified Communications Manager 5.x and Later as a Billing Server, page B-4. For Unified Communications Manager software versions that Service Monitor supports, see Cisco Unified Service Monitor 2.2 Compatibility Matrix.


If the last contact status is not Success:

For a NAM—Check whether the:

Credentials on a NAM have changed; if so, update the credentials in Service Monitor.

NAM is reachable; ensure that the NAM is reachable.

Then verify the credentials.

For a CCM—Service Monitor needs one or more credentials to obtain Unified Communications Manager data successfully. The dialog box that is available from the clickable status might contain information that will help you to resolve the problem. Some potential issues to consider are:

Service Monitor must be able to resolve the IP address for Unified Communications Manager to obtain the correct name. Verify that DNS parameters are specified correctly on the Service Monitor server and the Unified Communications Manager hostname has been added to DNS.

Known problems might exist that prevent successful data exchange between a cluster and Service Monitor. Check whether any have been identified in Release Notes for Cisco Unified Service Monitor 2.2.

In a few cases, you might need to correct credentials on Unified Communications Manager and then verify the credentials from Service Monitor:

When the last contact status is Success, in some cases, Service Monitor might not be receiving data, but simply waiting to receive data. To see when the last successful contact occurred, click the status link. If the last contact was not recent, correct any problem with credentials on Unified Communications Manager and verify the credentials from Service Monitor.

Credentials that Service Monitor relies upon might change on Unified Communications Manager platform. If this happens, check with your Unified Communications Manager administrator to obtain the correct credentials. If necessary, update the credentials in Service Monitor. Otherwise, verify the credentials.

After you make corrections, verify the credentials.


Note Do not verify credentials for Unified Communications Manager 4.x while Provisioning Manager synchronization is running. See Avoiding Credential Failure When Provisioning Manager Synchronization Runs in Your Network.


Procedure


Step 1 Select Configuration > Data Source Credentials. The Data Source Credentials page appears.

Step 2 Select the data source for which you want to verify credentials.

Step 3 Click Verify.


Related Topics

Editing Data Source Credentials

Adding Data Source Credentials

Deleting Data Source Credentials

Unified Communications Manager Configuration, page B-1

Understanding and Setting Data Source Credentials

Supported Data Source Software Versions

For the list of Unified Communications Manager and NAM software versions that Service Monitor supports, see Cisco Unified Service Monitor 2.2 Compatibility Matrix.

Adding Data Source Credentials

For Service Monitor to obtain and analyze voice data from supported versions of Unified Communications Manager and NAMs, you must:

1. Perform configuration tasks for:

Unified Communications Manager—See Unified Communications Manager Configuration, page B-1.

NAM—See NAM Configuration, page C-1.

2. Add Data Source Credentials to Service Monitor using the procedure for the appropriate software version:

Adding Credentials for NAM 4.x and Later

Adding Credentials for Unified Communications Manager 5.x and Later

Adding Credentials for Unified Communications Manager 4.x


Note Each cluster that you add to Service Monitor must have a unique cluster ID. You can view the cluster IDs in Service Monitor on the Data Source Credentials page. To view the cluster ID for a Unified Communications Manager that you plan to add, see Setting Unified Communications Manager Enterprise Parameters, page B-4.


Adding Credentials for NAM 4.x and Later

For the specific NAM hardware platforms and software versions that Service Monitor supports, see Cisco Unified Service Monitor 2.2 Compatibility Matrix.

Procedure


Step 1 Select Configuration > Data Source Credentials. The Data Source Credentials page appears.

Step 2 Click Add. The Add Credential dialog box appears.

Step 3 Enter the data described in the following table.

Field
Description

Display Name

Enter a name—up to 20 characters—to describe the NAM.

Version

Select NAM 4.x

Note For more information, see Supported Data Source Software Versions.

IP Address

You must enter one of these:

IP address for the NAM

DNS-resolvable hostname for the NAM.

If you enter both an IP address and a hostname, Service Monitor uses the IP address and stores the hostname without verifying or updating it.

Host Name

Protocol

Select the radio button that corresponds to the web server that is configured on the NAM:

HTTP—If selected, select one of these:

Default Port—Port number is displayed.

Custom Port—Enter the port number.

HTTPS—If selected, select one of these:

Default Port—Port number is displayed.

Custom Port —Enter the port number.

HTTP/S User Name/Password/Re-enter Password

Enter a username and password for a web administrator for the NAM. (For more information, see Enabling http or https Server and Configuring a Web Administrator User, page C-1.)


Step 4 Click OK.

Step 5 If an error message is displayed, do the following:

Ensure that you have the correct credentials for the NAM.

Ensure that Service Monitor supports the NAM hardware platform and software version; see Cisco Unified Service Monitor 2.2 Compatibility Matrix.


Adding Credentials for Unified Communications Manager 5.x and Later


Caution Before adding credentials for a Unified Communications Manager 5.x and later software version cluster, confirm that the cluster ID does not include a space. For more information, see Release Notes for Cisco Unified Service Monitor 2.2.


Note For Unified Communications Manager 5.x and later, in addition to adding credentials using the following procedure, you must also provide an SFTP password. See Configuring and Viewing Other Settings. For supported Unified Communications Manager software versions, see Supported Data Source Software Versions.


Procedure


Step 1 Select Configuration > Data Source Credentials. The Data Source Credentials page appears.

Step 2 Click Add. The Add Credential dialog box appears.

Step 3 Enter the data described in the following table.

Field
Description

Display Name

Enter a name—up to 20 characters—to describe the cluster.

Version

Select this version: CM 5.x and above

Note For more information, see Supported Data Source Software Versions.

Publisher IP Address

You must enter one of these:

Publisher IP address—Enter the IP address for the publisher in the cluster.

Publisher hostname—If you enter only the hostname, it must be DNS-resolvable.

If you enter both an IP address and a hostname, Service Monitor uses the IP address and stores the hostname without verifying or updating it.

Publisher Host Name

HTTP/S User Name/Password/Re-enter Password

Enter a username and password that can be used to log in to Unified Communications Manager Administration on the publisher server. The user role must have Standard AXL API Access privilege.


Step 4 Click OK.


Note If Service Monitor fails to add the Unified Communications Manager credentials because a duplicate cluster ID exists, change the cluster ID as described in Setting Unified Communications Manager Enterprise Parameters, page B-4 and add the Unified Communications Manager credential again. Every cluster added to Service Monitor must have a unique cluster ID.



Adding Credentials for Unified Communications Manager 4.x

Before you can add credentials to Service Monitor, you must configure the credentials in Unified Communications Manager. See Configuring Database Authentication on Unified Communications Manager 4.x Systems, page B-6.


Note Every cluster that you add to Service Monitor must have a unique cluster ID. You can see the cluster IDs already in use on the Data Source Credentials page. To view the cluster ID for the Unified Communications Manager that you plan to add, see Setting Unified Communications Manager Enterprise Parameters, page B-4.


When you add credentials to Service Monitor, you must select the database authentication mode that corresponds to the one configured in Unified Communications Manager. See Determining Authentication Mode in Use on a Unified Communications Manager 4.x System, page B-7.


Note Do not add credentials for Unified Communications Manager 4.x while Provisioning Manager synchronization is running. For more information, see Avoiding Credential Failure When Provisioning Manager Synchronization Runs in Your Network.


Procedure


Step 1 Select Configuration > Data Source Credentials. The Data Source Credentials page appears.

Step 2 Click Add. The Add Communications Manager dialog box appears.

Step 3 Enter the data described in the following table.

GUI Element
Description/Action

Display Name

Enter a name—up to 20 characters—to describe the cluster.

Version

Select CM 4.x

Note For more information, see Supported Data Source Software Versions.

Publisher IP Address

You must enter one of these:

Publisher IP address—Enter the IP address for the publisher in the cluster.

Publisher hostname—If you enter only the hostname, it must be DNS-resolvable.

If you enter both an IP address and a hostname, Service Monitor uses the IP address and stores the hostname without verifying or updating it.

Publisher Host Name

CDR Database

(Displayed when you select version CM 4.x)

Select the authentication mode that corresponds to the one used on Unified Communications Manager—see Determining Authentication Mode in Use on a Unified Communications Manager 4.x System, page B-7—and enter any required data:

Windows Authentication

SQL Authentication—When selected, you must also enter data in the SQL User Name and SQL Password/Re-enter SQL password fields. The usernames and passwords that you enter must match those entered for the Microsoft SQL Server account on the Unified Communications Manager publisher node; the account must have access to the CDR database.

HTTP/S User Name/Password/Re-enter password

(Displayed when you select version CM 4.x)

Enter a username and password that can be used to log in to Unified Communications Manager Administration on the publisher server.


Step 4 Click OK.


Note If Service Monitor fails to add the Data Source Credentials because a duplicate cluster ID exists, change the cluster ID as described in Setting Unified Communications Manager Enterprise Parameters, page B-4 and add the Unified Communications Manager credential again. Every cluster added to Service Monitor must have a unique cluster ID.



Avoiding Credential Failure When Provisioning Manager Synchronization Runs in Your Network

If Provisioning Manager runs in your network, check with your Provisioning Manager administrator to obtain the schedule for synchronization, which is a planned activity. During synchronization, do not add, edit, or verify Unified Communications Manager 4.x credentials in Service Monitor. Otherwise, credentials fail (last contact status displays Failure), data is not collected, and you cannot successfully verify credentials until synchronization completes.

Editing Data Source Credentials

You can change the display name and the HTTP/S username and password for any data source. Otherwise, the information that is displayed and the changes that you can make depend on whether the data source is a cluster or a NAM.


Note Do not edit Unified Communications Manager 4.x credentials while Provisioning Manager synchronization runs in your network. For more information, see Avoiding Credential Failure When Provisioning Manager Synchronization Runs in Your Network.


Procedure


Step 1 Select Configuration > Data Source Credentials. The Data Source Credentials page appears.

Step 2 Select a data source and click Edit. The Edit Credential dialog box appears.

Step 3 Enter the data described in the following table. The data that is displayed depends on the software version.

Field
Description

Display Name

Enter a name—up to 20 characters—to describe the data source.

Fields that Are Displayed for a NAM Sensor

IP Address

This field is grayed out because you cannot edit it.

Hostname

Service Monitor stores any change that you make to the hostname without verifying it.

Protocol

Select the radio button that corresponds to the web server that is configured on the NAM:

HTTP—If selected, select one of these:

Default Port—Port number is displayed.

Custom Port —Enter the port number.

HTTPS—If selected, select one of these:

Default Port—Port number is displayed.

Custom Port —Enter the port number.

HTTP/S Username, Password, Re-enter password

Enter a username and password for a web administrator for the NAM. (For more information, see Enabling http or https Server and Configuring a Web Administrator User, page C-1.)

Fields that Are Displayed for a Unified Communications Manager Cluster

Publisher IP Address

This field is grayed out because you cannot edit it.

Publisher Host Name

Service Monitor stores any change that you make to the hostname without verifying it.

Windows Authentication

SQL Authentication

(Displayed if version CM 4.x was selected when adding credentials)

Unified Communications Manager database authentication mode—Select either Windows Authentication or SQL Authentication.

Note If you are considering changing the authentication mode, see Determining Authentication Mode in Use on a Unified Communications Manager 4.x System, page B-7.

If SQL authentication is selected, the usernames and passwords that you enter must match those entered for Microsoft SQL Server accounts on the Unified Communications Manager publisher node:

SQL User Name and Password/Re-enter SQL Password—Enter the username and password for a Microsoft SQL Server account with access to the CDR database on the Unified Communications Manager version 4.x publisher node.

SQL CDR-DB User Name and SQLCDR-DB Password/Re-enter password—Enter the username and password for a Microsoft SQL Server account with access to the CDR database on the Unified Communications Manager version 3.3.x publisher node.

For more information, see Adding Microsoft SQLServer User Accounts for Unified Communications Manager 4.x, page B-9.

HTTP/S Username, Password, Re-enter password

Enter a username and password that can be used to log in to Unified Communications Manager Administration on the publisher server.

Note For Unified Communications Manager 5.x and later, the user role must have Standard AXL API Access privilege.


Step 4 Click OK.


For Unified Communications Manager software versions that Service Monitor supports, see Supported Data Source Software Versions.

Deleting Data Source Credentials

After you complete this procedure, Service Monitor can no longer obtain data for the cluster or the NAM. Additionally, the data source no longer appears on the Monitored Phones page. Call data for the data source remains in the database until it is purged. For more information, see Maintaining the Service Monitor Database, page 6-1.

Before you complete this procedure, delete the data source from any CVTQ or sensor threshold groups. See Editing a CVTQ Threshold Group, page 5-6 and Editing a Sensor Group, page 5-10.

Procedure


Step 1 Select Configuration > Data Source Credentials. The Data Source Credentials page appears.

Step 2 Select the check box by the cluster or NAM that you want to delete.

Step 3 Click Delete. One of the following occurs:

A confirmation dialog box appears.

An error message appears, displaying a list of CVTQ threshold groups to which the cluster belongs. You will need to remove the cluster from these CVTQ threshold groups and repeat this procedure.

An error message appears, displaying a list of sensor threshold groups to which the NAM belongs. You will need to remove the NAMs from these sensor threshold groups and repeat this procedure.

Step 4 Click OK.


Managing the Phone Count

On the Monitored Phones page, you can view the total number of phones that Service Monitor is monitoring. You can also view the names of all sensors (Cisco 1040s and NAMs) and Unified Communications Manager clusters known to Service Monitor to see whether each is monitored, and, if so, see the number of phones that Service Monitor manages in the cluster or for the sensor.


Note Because it is possible for a Unified Communications Manager cluster and a sensor to report MOS for some of the same phones:

The total known phone count displayed on the Monitored Phones page might be less than the sum of known phone counts for clusters/sensors.

To decrease the total known phone count, you might need to suspend more than one cluster or sensor.


To manage the phone count, select Configuration > Monitored Phones. The Monitored Phones page appears, displaying the information in the following table.

GUI Element
Description

Total known phone count: (n)

Number of phones that Service Monitor is monitoring. If the number of phones equals the license size, the following message is displayed in red:

Total known phone count (n) has reached or exceeded licensed 
limit!

License limit: (n)

Number of phones allowed by license.

Cluster/Sensor List

Cluster/Sensor ID column

One of the following:

Cluster ID—The cluster ID is assigned by Unified Communications Manager.

Sensor ID—Sensor MAC address.

Version column

One of these:

Binary image filename for Cisco 1040.

Software version for NAM.

Type

One of the following:

CCM—Unified Communications Manager.

NAM—Network Analysis Module sensor.

1040—Cisco 1040 Sensor.

State column

One of these:

Monitored—Service Monitor is collecting and analyzing data from this cluster or sensor and sending traps when violations occur.

Suspended—Service Monitor is not collecting and analyzing data from this cluster or sensor for one of these reasons:

A user set the state of the cluster or sensor to Suspended. See Suspending and Resuming a Cluster or Sensor from Monitoring.

Service Monitor could not monitor any more newly created clusters or phones when data was received because the phone license count was reached.


Related Topic

Suspending and Resuming a Cluster or Sensor from Monitoring

Suspending and Resuming a Cluster or Sensor from Monitoring

Provided that Unified Communications Manager is configured properly and Service Monitor license limits are not exceeded, Service Monitor starts to monitor a cluster when it learns of the cluster. Service Monitor learns of a cluster when you add Unified Communications Manager credentials to Service Monitor. (For more information, see Adding Data Source Credentials.)

Service Monitor learns of a sensor when:

The Cisco 1040 sensor registers.

The NAM credentials are added to Service Monitor.

If you want to suspend a cluster or a sensor from monitoring—for example, to enable you to monitor phones from a different cluster or sensor—you can do so.

Related Topics

Suspending a Cluster or Sensor

Resuming a Cluster or Sensor

Updating the Total Known Phone Count for a Cluster

Suspending a Cluster or Sensor

When you suspend a cluster or sensor, the following occurs:

Data for the suspended cluster or sensor no longer appears in Service Monitor reports.

The cluster or sensor appears on the Monitored Phones page as Suspended and the known phone count for that cluster or sensor drops to zero (0). If, as a result, the total known phone count also decreases, you are free to monitor additional phones in other clusters or from other sensors (up to your license limit).

Procedure


Step 1 Select Configuration > Monitored Phones.

Step 2 Select the check box for the cluster or sensor that you want to suspend.

Step 3 Click Suspend. A confirmation dialog box appears.

Step 4 Click OK.


Related Topics

Resuming a Cluster or Sensor

Updating the Total Known Phone Count for a Cluster

Resuming a Cluster or Sensor

Procedure


Step 1 Select Configuration > Monitored Phones.

Step 2 Select the check box for a suspended cluster or sensor that you want to monitor.

Step 3 Click Resume. A confirmation dialog box appears.

Step 4 Click OK.


Related Topics

Suspending a Cluster or Sensor

Updating the Total Known Phone Count for a Cluster

Updating the Total Known Phone Count for a Cluster

Service Monitor monitors the first n phones that it finds in the data that it receives or obtains from the clusters. If a phone in a cluster fails and is replaced, Service Monitor is not notified and continues to include the failed phone in the total known phone count. To refresh the total known phone count for a cluster, suspend the cluster and resume it.


Note Suspending a cluster resets the phone count to zero for that cluster. The phone count then increases as and when calls come from a phone.


Related Topic

Suspending and Resuming a Cluster or Sensor from Monitoring

Configuring Settings for Most-Impacted Endpoints Reports

Use this procedure to configure:

The number of endpoints to be included in CVTQ and sensor most-impacted endpoint reports no matter when they run—daily, weekly, or on demand.

The most-impacted endpoints reports to export—CVTQ or sensor or both. Most-impacted endpoint reports can run daily and weekly, exporting the results to a comma-separated values file (CSV) or a portable document format (PDF) file. You can save the reports on the server and, optionally, automatically send them through e-mail.


Note The maximum number of records that can be exported to a PDF file is 2,000. The maximum number of records that you can export to CSV is configurable; the default is 30,000 with an upper limit of 64,000 records. For more information, see Configuring Diagnostic Report Search and CSV Export Limit Settings.


Procedure


Step 1 Select Configuration > Export Settings. The Export Settings (for Most-Impacted Endpoint) page appears, displaying the information described in the following table.

GUI Element
Description/Action

Number of Endpoints field

Enter the number of endpoints that you want to see on all—exported or directly launched—most-impacted endpoints reports.

Daily at 1:00 AM check boxes

To generate the report every day, select at least one of the following:

CSV check box—Save the report in CSV format.

PDF check box—Save the report in PDF format.

If neither is selected, Service Monitor does not generate the reports.

Weekly at 1:00 AM Monday check boxes

To generate the report every week, select at least one of the following:

CSV check box—Save the report in CSV format.

PDF check box—Save the report in PDF format.

If neither is selected, Service Monitor does not generate the reports.

Report Type

Select at least one of the following:

Sensor

CVTQ

Note Separate reports are generated for sensor and CVTQ data. For report filenames, see Table 3-1.

Save at

Enter a location for storing the reports on the server where Service Monitor is installed; a default location is displayed.


Caution If you configure export settings to save files outside of NMSROOT, be sure to also log into the Service Monitor server, create the folder that you entered on the Export Settings page, and provide write permission to the folder for the user casuser. If you do not, Service Monitor cannot create the export files. (NMSROOT is the location where Service Monitor is installed. If you used the default location, it is C:\Program Files\CSCOpx.)

E-mail to

(Optional) Enter one or more complete e-mail addresses separated by commas.

Note You should configure another e-mail address to which Service Monitor can send notifications for server process restarts. (Otherwise, Service Monitor sends notifications to the address defined in this field.) For more information, see Configuring a Recipient for E-Mail Notification, page 6-8.

SMTP Server

(Optional) Enter an SMTP server.


Step 2 Click Apply.


Depending on the reports and formats that you have selected, the following reports will be generated.

Table 3-1 Most-Impacted Endpoints Exported Reports 

Report Type
When Generated
Report Filenames

CVTQ

Daily

CVTQ_Daily_ddmmyyyy.csv

CVTQ_Daily_ddmmyyyy.pdf

Weekly

Note Generated on Monday.

CVTQ_Weekly_ddmmyyyy.csv

CVTQ_Weekly_ddmmyyyy.pdf

Sensors

Daily

Sensor_Daily_ddmmyyyy.csv

Sensor_Daily_ddmmyyyy.pdf

Weekly

Note Generated on Monday.

Sensor_Weekly_ddmmyyyy.csv

Sensor_Weekly_ddmmyyyy.pdf


Related Topics

Generating and Understanding the Sensor Most-Impacted Endpoints Report, page 2-20

Generating and Understanding the CVTQ Most-Impacted Endpoints Report, page 2-21

Configuring and Viewing Other Settings

Use this procedure to:

View some settings that are configured outside of the user interface. (See Configuring Diagnostic Report Search and CSV Export Limit Settings and Configuring Low-Volume Schedule and Database Purging, page 6-2.)

Configure SFTP settings if you are monitoring calls from Unified Communications Manager version 5.x or later. (For Unified Communications Manager software versions that Service Monitor supports, see Supported Data Source Software Versions.)

Procedure


Step 1 Select Configuration > Other Settings. The Other Settings page appears.

Step 2 View settings and update SFTP settings as described in the following table.

Fields
Description/Action
Low-Volume Schedule Hours

<day> <timerange>; <timerange>

For example:

Mon 0-6; 22-24

For each day of the week, timerange indicates the hours during which Service Monitor processes fewer records, handling a number that is roughly 20% of records processed during a peak period. During the low-volume schedule, Service Monitor performs database maintenance.

Note A windows user with access to the Service Monitor server can configure this schedule. See Configuring Low-Volume Schedule and Database Purging, page 6-2.

Miscellaneous

Wait for Diagnostic Report (min)

Number of minutes that Service Monitor continues to search—when there is a large volume of data—before displaying the matching records found so far for a diagnostic report (a Sensor report or a CVTQ report). To configure this setting, see Configuring Diagnostic Report Search and CSV Export Limit Settings.

Report Data Retention Period (days)

Number of days that data is retained in the Service Monitor database before being purged. The default value depends on the configuration:

Service Monitor alone on a server—7 days.

Service Monitor and Operations Manager on a server—3 days.

On the Service Monitor server, a user can change the value of the data-retention-days property in the NMSROOT\qovr\qovrconfig.properties file. (NMSROOT is the location where Service Monitor is installed. If you used the default location, it is C:\Program Files\CSCOpx.) To put changes into effect after you edit qovrconfig.properties, you must stop and start the QOVR process. While logged in to the server where Service Monitor is installed, from the command line, enter these commands:

pdterm QOVR
pdexec QOVR

Operations Manager Server

Enter the IP address for the Operations Manager server that Service Monitor is registered to.

Note Even when Operations Manager and Service Monitor run on the same system, you must replace the default value, localhost, with the correct IP address.

Entering the IP address enables users to launch the Detailed Device View page or the Phone Detail window in Operations Manager from Service Monitor reports. (See Understanding Sensor Diagnostic Reports, page 2-7 and Understanding CVTQ Diagnostic Reports, page 2-15.)

Note To enable users to view Operations Manager windows without logging in to Operations Manager, you can configure single sign-on. For more information, see Enabling Single Sign-On in User Guide for CiscoWorks Common Services 3.2.

SFTP

Username

You cannot change the username from smuser.

This same username, smuser, must be configured in Unified Communications Manager. See Adding Service Monitor to Unified Communications Manager 5.x and Later as a Billing Server, page B-4.

Change password check box

Select to change password.


Caution The default password is smuser. If you change the password here, you must also change the password for smuser in Unified Communications Manager. See Adding Service Monitor to Unified Communications Manager 5.x and Later as a Billing Server, page B-4.

Password

Enter password.

Re-enter password

Re-enter password.


Step 3 Click Apply.


Related Topic

Configuring Diagnostic Report Search and CSV Export Limit Settings

Configuring Diagnostic Report Search and CSV Export Limit Settings

Table 3-2 lists properties that affect diagnostic reports. A windows user with access to the Service Monitor server can change the values of these properties in the NMSROOT\qovr\qovrconfig.properties file.


Note NMSROOT is the location where Service Monitor is installed. If you used the default location, it is C:\Program Files\CSCOpx.


Table 3-2 Diagnostic Report and Export Settings 

Property
Description and Limit

WaitForDiagReport

Number of minutes that Service Monitor continues to search—when there is a large volume of data—before displaying the matching records found so far for a diagnostic report (a Sensor report or a CVTQ report).

Default: 2.

Maximum: 4.

Note Service Monitor reports can display up to 2,000 records. To see additional records, you can export a diagnostic report to a CSV file.

ExportCSVLimit

Number of records that Service Monitor exports to a CSV file.

Default: 30000.

Maximum: 64000—This is approximately the maximum number of records that can be included in a CSV file that Excel can open.


After you edit qovrconfig.properties, to put changes into effect, you must stop and start the QOVR process. While logged in to the server where Service Monitor is installed, from the command line, enter these commands:

pdterm QOVR
pdexec QOVR