Guest

Cisco Prime Unified Service Monitor

Release Notes for Cisco Unified Service Monitor 2.0

  • Viewing Options

  • PDF (315.4 KB)
  • Feedback
Release Notes for Cisco Unified Service Monitor 2.0

Table Of Contents

Release Notes for Cisco Unified
Service Monitor 2.0

New Features

Product Documentation

Related Documentation

Supported Versions of Cisco Unified CallManager

Required Cisco Unified CallManager Patches and Workarounds

Supported Cisco IP Phone Models and Phone Protocols

Supported Cisco 1040 Binary Image Files

Known Problems

Fixing the DHCP Option 150 Issue for Cisco 1040 Sensors

Documentation Addenda

Configuring the Service Monitor Client to Allow Popup Windows

Disabling Virus Scanning on the Databases Directory

Ensuring Successful Reinstallation

Documentation Errata

Activating the AXL Web Service on Unified Communications Manager (Appendix B)

Obtaining Documentation and Submitting a Service Request


Release Notes for Cisco Unified
Service Monitor 2.0


Revised: April 22, 2009

Cisco Unified Service Monitor is a product from the Cisco Unified Communications Management Suite. These release notes provide:

New Features

Product Documentation

Related Documentation

Supported Versions of Cisco Unified CallManager

Supported Cisco 1040 Binary Image Files

Known Problems

Documentation Errata

Obtaining Documentation and Submitting a Service Request

New Features

The following changes and enhancements are included in Service Monitor 2.0:

Cisco Unified CallManager support—Service Monitor can monitor calls from Cisco Unified CallManager clusters only, or in conjunction with sensors. For more information, see Supported Versions of Cisco Unified CallManager.

Cluster and sensor management—You can suspend and resume monitoring of clusters and sensors.

Reports—Service Monitor reports display Mean Opinion Score (MOS), endpoints involved in voice activity, and other details obtained from sensors and clusters during the last 30 days.

Threshold for each codec—Service Monitor supplies a set of global thresholds that enable you to set a MOS threshold value for each supported codec. You can selectively override global thresholds by creating sensor threshold groups and Cisco Voice Transmission Quality (CVTQ) threshold groups.

If you upgraded to Service Monitor 2.0 from an earlier version, you will notice changes in the following:

Licensing—Specifies the number of phones that Service Monitor can monitor instead of the number of sensors that can register with Service Monitor.

MOS violation SNMP trap definition—Specifies whether the trap was generated for sensor-based data or cluster-based data in the TT field. The trap definition also includes additional fields for each type of data.

Cisco 1040 Sensor management:

TFTP servers—Instead of just one TFTP server, multiple TFTP servers can be added to Service Monitor. Service Monitor now automatically copies any updated sensor configuration files to the TFTP servers if permitted by the security settings on them. After successfully copying the sensor configuration files, Service Monitor resets affected sensors to load the new configuration.


Note You can still manually copy configuration files to the TFTP servers and then reset the sensors from the Service Monitor user interface.


Sensor IDs—MAC addresses replace the Annn naming scheme formerly used for sensor IDS; in addition, you can add a descriptive name for a sensor.

Sensor-calculated MOS—Sensors send data to Service Monitor every 60 seconds without determining whether a threshold has been violated. That determination is made by Service Monitor which stores the sensor data in the database, where it is available for reporting.

Trap suppression—Service Monitor 2.0 introduces a setting to reduce the number of traps that Service Monitor sends for each endpoint, sending a a trap every n minutes with a minimum value of 5. Additional traps for that endpoint during that time are suppressed (not sent).

Failover from Primary Service Monitor—Sensor failover to a secondary Service Monitor is still supported; the ability to define and fail over to a tertiary Service Monitor is no longer supported.

Product Documentation


Note The originally published printed and electronic documentation is included with your product. Any changes after original publication are reflected on Cisco.com, where you will find the most up-to-date documentation.


Table 1 describes the product documentation that is available.

Table 1 Product Documentation 

Document Title
Available Formats

Release Notes for Cisco Unified Service Monitor 2.0

PDF on the product CD-ROM.

On Cisco.com at the following URL:

http://cisco.com/en/US/products/ps6536/
prod_release_notes_list.html

Quick Start Guide for Cisco Unified Service Monitor 2.0

Note This quick start guide explains how to install and upgrade Service Monitor.

Printed document that was included with the product.

PDF on the product CD-ROM.

On Cisco.com at the following URL:

http://cisco.com/en/US/products/ps6536/
prod_installation_guides_list.html

User Guide for Cisco Unified Service Monitor

PDF on the product CD-ROM.

PDF accessible from online help.

On Cisco.com at the following URL:

http://cisco.com/en/US/products/ps6536/
products_user_guide_list.html

Context-sensitive online help

Available by clicking one of the following:

Help link in the upper right-hand corner of the window.

Help button in the dialog box.


Related Documentation


Note The originally published printed and electronic documentation is included with your product. Any changes after original publication are reflected on Cisco.com, where you will find the most up-to-date documentation.


Table 2 describes the additional documentation that is available.

Table 2 Related Documentation 

Document Title
Description and Available Formats

Release Notes for Cisco Unified Operations Manager 2.0

On Cisco.com at the following URL:

http://cisco.com/en/US/products/ps6535/
prod_release_notes_list.html

Quick Start Guide for Cisco 1040 Sensor

Describes how to install a Cisco 1040 and provides regulatory compliance and safety information. This document is available on Cisco.com at the following URL:

http://cisco.com/en/US/products/ps6536/prod_installation_guides_list.html

Quick Start Guide for Cisco Unified Operations Manager 2.0

On Cisco.com at the following URL:

http://cisco.com/en/US/products/ps6535/prod_installation_guides_list.html

Installation Guide for Cisco Unified Operations Manager (Includes Service Monitor)

On Cisco.com at the following URL:

http://cisco.com/en/US/products/ps6535/prod_installation_guides_list.html

User Guide for Cisco Unified Operations Manager

On Cisco.com at the following URL:

http://cisco.com/en/US/products/ps6535/products_user_guide_list.html

Release Notes for CiscoWorks Common Services 3.0.3 (Includes CiscoView 6.1.2) on Windows

On Cisco.com at the following URL:

http://www.cisco.com/en/US/products/sw/cscowork/ps3996/
prod_release_note09186a00805af53a.html

Readme for Common Services 3.0.4 on Windows

On Cisco.com at the following URL:

http://www.cisco.com/en/US/partner/products/sw/cscowork/ps3996/
prod_installation_guide09186a00805f7d64.html

Installation and Setup Guide for Common Services 3.0.3 (Includes CiscoView) on Windows

On Cisco.com at the following URL:

http://www.cisco.com/en/US/partner/products/sw/cscowork/ps3996/
products_installation_guide_book09186a00805305cb.html

Printed document available by order (part number DOC-7817184=)1

User Guide for CiscoWorks Common Services 3.0.3

On Cisco.com at the following URL:

http://www.cisco.com/en/US/products/sw/cscowork/ps3996/
products_user_guide_book09186a008053eabf.html

Printed document available by order (part number DOC-7817182=)1

1 See the "Obtaining Documentation and Submitting a Service Request" section.


Supported Versions of Cisco Unified CallManager

When properly configured, Service Monitor can report on voice activity from these versions of Cisco Unified CallManager.

Cisco Unified CallManager Version
Information Available from this Version

3.3

The following information is available for Service Monitor to include in reports:

Cluster ID

Call endpoints

Time stamp

Call duration

Call termination cause

Codec

Milliseconds of jitter

Percent of packet loss

4.0

4.1

4.2

In addition to the information provided by earlier versions, MOS is available for Service Monitor to use in determining whether a threshold has been violated and, if so, send a trap. Other data, such as concealment ratio and severely concealed seconds, is also available for inclusion on reports and in traps.

MOS is calculated using the CVTQ algorithm on specific phones. To make CVTQ data available, you need to:

Ensure that you have applied any required patches to Cisco Unified CallManager.

Use the specified models of Cisco IP phones with the specified protocol and firmware; these phones must be registered with Cisco Unified CallManager 4.2, 5.0, or 5.1.

See the information in the following sections.

5.0

5.1


Required Cisco Unified CallManager Patches and Workarounds

Problems with CVTQ data can occur due to known problems with certain versions of Cisco Unified CallManager. Table 3 documents these problems.

Table 3 Circumstances that Can Affect Data 

Description
Circumstances

Service Monitor CVTQ reports show many calls for a Cisco Unified CallManager 5.x cluster during a period of 10 to 12 hours, followed by no calls

After pushing huge numbers of Call Detail Records (CDRs) and Call Management Records (CMRs) to external servers, Cisco Unified CallManager 5.x stops pushing CMRs and CDRs.

Bug ID: CSCsg50434

This problem has been fixed in Cisco Unified CallManager 5.1.

To work around this problem if you are monitoring a Cisco Unified CallManager 5.0 cluster, restart the CDR Repository Service as follows:

1. From Cisco Unified CallManager Serviceability, select Tools > Control Center - Network Services.

2. Select Publisher  > Stop / Start or Restart Cisco CDR Repository Manager.

Service Monitor CVTQ reports do not show any calls in a Cisco Unified CallManager 5.0 cluster

If a space is included in the cluster ID, an error occurs in a component of Cisco Unified CallManager, and CDRs and CMRs are not pushed.

Bug ID: CSCsd81400

This problem has been fixed and verified in Cisco Unified CallManager 5.0(3.9911.35).

Workaround: If you do not have the Cisco Unified CallManager 5.0(3.9911.35) image or later, do the following.

1. Change the cluster ID to a name that doesn't include a space; from Cisco Unified CallManager Administration:

a. Select System > Enterprise Parameters. The Enterprise Parameters Configuration page appears.

b. Change the cluster ID.

c. Click Update.

2. Repeat this step for each Cisco Unified CallManager:

a. From Cisco Unified CallManager Serviceability select Tools > Control Center - Feature Services.

b. Select the Cisco Unified CallManager server.

c. Click the Restart button.

3. Remove old files from the Cisco Unified CallManager 5.0 server:

a. Log in to the server.

b. Go to the /var/log/active/cm/cdr directory.

c. Remove all files that start with cdr_old cluster name_ and cmr_old cluster name_.


Supported Cisco IP Phone Models and Phone Protocols

The following Cisco IP phone models support the Cisco Voice Transmission Quality (CVTQ) algorithm in SCCP mode if they have the 8.0(3) firmware which can be downloaded from Cisco Unified CallManager versions 4.2 and 5.x:

7940

7941

7960

7961

7970

7971

All other Cisco IP phone models, including 7985, do not support CVTQ. All SIP-based phones do not support CVTQ.


Note The 8.0(3) phone firmware should also be accessible from this URL: http://www.cisco.com/cgi-bin/tablebuild.pl/ip-7900ser.


Supported Cisco 1040 Binary Image Files

Only the following binary image files are supported for use on Cisco 1040 Sensors while using Service Monitor 2.0:

SvcMonAA2_34.img—Installed in the NMSROOT\ImageDir folder when you install Service Monitor 2.0.

SvcMonAA2_37.img—Available from Cisco TAC by request; for more information, see Fixing the DHCP Option 150 Issue for Cisco 1040 Sensors.


Caution Installing binary image files other than SvcMonAA2_34.img and SvcMonAA2_37.img can cause severe problems.


Note For the Cisco 1040 binary images that are supported while using Service Monitor 2.0.1, see Release Notes for Cisco Unified Service Monitor 2.0.1 at this URL: http://www.cisco.com/en/US/partner/docs/net_mgmt/cisco_unified_service_monitor/2.0.1/release/
notes/SrvMonRN.html
.


Known Problems


Note To obtain more information about known problems, access the Cisco Software Bug Toolkit at
http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. (You will be prompted to log into Cisco.com.)


Table 4 describes problems known to exist in this release. For circumstances under which a Cisco 1040 Sensor becomes unable to find the TFTP server, see Fixing the DHCP Option 150 Issue for Cisco 1040 Sensors. For additions to Service Monitor documentation, see Documentation Addenda.

Table 4 Known Problems in Service Monitor 2.0 

Bug ID
Summary
Explanation

CSCsj91958

SM does not report endpoint properly for intercluster call

In CVTQ reports, you will see the following as endpoints:

Cisco Unified Communications Manager

Cisco Unified Customer Voice Portal

Cisco Unified Presence Server

even though the RTP media stream does not flow to the them as they are used only for signaling.

This occurs in Cisco Unified Service Monitor 2.1 and earlier versions.

There is no workaround.

CSCso65632

Installation sometimes corrupts because DEP is not suppressed

Installation sometimes fails. This happens when Windows Data Execution Prevention (DEP) is enabled.

To work around this problem:

1. Disable DEP:

a. Log in to the machine on which you will install Service Monitor as an administrator or a member of the Administrators group.

Note If your computer is connected to a network, network policy settings might prevent you from completing this procedure.

b. Open System Properties by right-clicking the My Computer icon on your desktop and selecting Properties.

c. Click the Advanced tab; then, under Performance, click Settings.

d. Click the Data Execution Prevention tab. If Turn on DEP for all programs and services except those I select is selected, DEP is enabled.

e. Select Turn on DEP for essential Windows programs and services only.

f. Click OK.

2. Install Service Monitor.

3. Install the DST patch by following the instructions for CSCsh81265.

Note Install the DST patch whether or not you have previously installed it.

4. If desired, re-enable DEP:

a. Perform steps 1a-1d.

b. Select Turn on DEP for all programs and services except those I select.

CSCsh81265

Daylight Savings Time (DST) change in US

In the United States beginning in March 2007, DST starts earlier—on the second Sunday in March—and ends later—on the first Sunday in November—than in previous years. During DST, Service Monitor user interface and reports will be an hour off.

To work around this problem:

Apply the US Daylight Saving Time (DST) Patch for Cisco Unified Service Monitor 1.1 and 2.0:

1. Enter this URL into your browser: http://www.cisco.com/cgi-bin/tablebuild.pl/servmon
and follow instructions to log in.

2. Download and read "Readme for US Daylight Saving Time (DST) Patch for Cisco Unified Service Monitor 1.1 and 2.0" (cusmdst_win.readme.pdf). This document includes the amount of time required to install, installation instructions, and steps to complete after installing the patch.

3. Download and install "Daylight Saving Patch for Cisco Unified Service Monitor 1.1 and 2.0 " (cusmdst_win_k9.zip).

4. Sun Alert 102836 describes a bug in the latest JDK releases when using EST, MST, and HST abbreviations. To work around this problem for Service Monitor, complete either one of these workarounds:

Workaround Alternative 1

a. From the command line on the Service Monitor system, stop the daemon manager using this command:

net stop crmdmgtd

b. Delete three time zone data files: EST, MST, and HST from the NMSROOT\lib\jre\lib\zi directory (or <JRE_HOME>/lib/zi).


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


c. Start the daemon manager using this command:

net start crmdmgtd

Workaround Alternative 2

a. From the command line on the Service Monitor system, stop the daemon manager using this command:

net stop crmdmgtd

b. Download and extract the tzupdater tool from this URL:

http://java.sun.com/javase/downloads/index.jsp


Note This website is Copyright © 1994-2008, Sun Microsystems, Inc.


CSCsh81265

(continued)

Daylight Savings Time (DST) change in US

c. From the command line, execute this command:

<NMSROOT>\CSCOpx\lib\jre\java.exe -jar tzupdater.jar -f -bc 


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


d. Start the daemon manager using this command:

net start crmdmgtd

CSCsh01863

New Cisco CallManager with same cluster ID corrupts info for previously added cluster

Adding two Cisco Unified CallManager clusters with the same cluster ID to Service Monitor causes data corruption in Service Monitor.

Note Cisco Unified CallManager 3.3 and later use the default cluster name StandAloneCluster. If you are managing multiple Cisco Unified CallManager clusters, you must change the default cluster name.

To prevent this problem, before adding credentials for a Cisco Unified CallManager to Service Monitor, confirm that the cluster ID is unique.

To work around this problem:

1. Delete credentials from Service Monitor for each Cisco Unified CallManager with the same cluster ID.

Note For detailed instructions on configuring Cisco Unified CallManager, see the Cisco Unified CallManager documentation.

2. Update the cluster IDs to make them unique:

a. Log in to Cisco Unified CallManager Administration.

b. Select System > Enterprise Parameters. The Enterprise Parameters Configuration page appears.

c. In the Cluster ID field, enter a new cluster name.

d. Click Update.

3. Add the Cisco Unified CallManager credentials to Service Monitor again.

CSCsg86540

During reinstall, database backup continues indefinitely

When reinstalling Service Monitor on a system with a large database, the backup operation can go on indefinitely.

To work around this problem, skip the database backup during reinstallation (see step 2 in the following procedure). To also save the existing database, perform all of these steps:

1. Save the existing database to a temporary location outside of NMSROOT before reinstalling Service Monitor:

a. Stop the daemon manager using the following command:

net stop crmdmgtd

b. Change the qovr database password to something that you will remember. In this example, the new password is admin:

NMSROOT\C\bin\perl  dbpasswd.pl dsn=qovr npwd=admin


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


c. From NMSROOT\databases\qovr, copy these files—qovr.db and qovrx.log—to a location outside of NMSROOT.

2. Skip database backup while reinstalling Service Monitor:

a. From the command line, change directory to the drive with the product CD.

b. Issue this command:

Setup.exe nobackup 

To complete the reinstallation, follow the instructions online or consult Quick Start Guide for Cisco Unified Service Monitor.

3. After completing the reinstallation and rebooting your system, replace the newly created database with the database that you saved:

a. Stop the daemon manager using the following command:

net stop crmdmgtd

b. Set the password on the newly created database to match the password that you set on the database that you saved:

NMSROOT\C\bin\perl  dbpasswd.pl dsn=qovr npwd=admin

c. Copy the database files—qovr.db and qovrx.log—from the location outside of NMSROOT (see step 1.c.) to NMSROOT\databases\qovr.

d. Restart the daemon manager using the following command:

net start crmdmgtd

CSCsg67050

G711 Ulaw not in sensor report; G711 Ulaw threshold not applied to sensor data

Cisco 1040 sensors report a codec of G711 Alaw for calls that are actually G711 Ulaw. Therefore, no sensor records include G711 Ulaw. As a result, data from a sensor:

Cannot trigger global thresholds and sensor group thresholds for G711 Ulaw.

Does not appear in sensor diagnostic reports if you select G711 Ulaw (and not G711 Alaw) to generate the report.

To work around this problem:

Select G711 Alaw on the Sensor Filter Reports page to generate a report that includes G711 Ulaw in addition to G711 Alaw.

Keep in mind that G711 Ulaw thresholds are not applied to data from Cisco 1040 sensors. Instead, G711 Alaw thresholds—global or from a sensor threshold group—are applied.

CSCsb46108

Cisco 1040 sets syslog D field incorrectly for G711 Ulaw

When G711Ulaw codec is used, the Cisco 1040 sets the syslog D field value to 2, which indicates that the codec is G711 Alaw. The correct syslog D field value for G711 Ulaw is 4.

There is no workaround for this problem.

CSCsc31319

Service Monitor shows Cisco 1040 waiting to register while receiving syslog

The web interface on a Cisco 1040 displays status as operational and lists the Service Monitor to which the Cisco 1040 is registered. However, this Service Monitor shows the Cisco 1040 registered to Waiting while still receiving and processing syslog messages from this Cisco 1040.

This problem occurs after a user does either of the following:

Uses pdterm to stop the QOVR process, and, in quick succession, uses pdexec to start it again.

Changes the time on the system where Service Monitor is installed without subsequently stopping and restarting the daemon manager process.

To work around this problem, use one of these procedures:

Wait at least 5 minutes between stopping and starting the QOVR process. If you stopped and started the QOVR process in quick succession:

1. From the command line, stop the QOVR process again, by entering the pdterm command:

pdterm QOVR

2. Wait at least 5 minutes.

3. Enter the pdexec command:

pdexec QOVR

Stop and start the daemon manager after you change the time on the server where Service Monitor is installed, by issuing the following commands:

net stop crmdmgtd
net start crmdmgtd

CSCsc19066

Cisco 1040 does not generate syslog messages for Audio Codec G722

There is no workaround for this problem.


Fixing the DHCP Option 150 Issue for Cisco 1040 Sensors

A Cisco1040 Sensor does not correctly interpret DHCP Option 150 if the IP address includes an octet with the value of 32, such as 10.10.32.1, or an octet with the value of 92, such as 10.10.1.92.

This problem is fixed in binary image file, SvcMonAA2_37.img, which you can obtain from Cisco Technical Assistance Center (TAC). (For contact information, see Obtaining Documentation and Submitting a Service Request.) Until you load SvcMonAA2_37.img onto your sensors, use one of the workarounds.

Workarounds

Use the ASCII type when providing the Option 150 IP address.

Ensure that the IP address for the TFTP server does not include an octet with the value 32 or 92.

Loading SvcMonAA2_37.img onto Cisco 1040 Sensors

You will need to employ one of the workarounds to enable the sensors to find a TFTP server and download the SvcMonAA2_37.img from it. After SvcMonAA2_37.img is loaded onto the sensors, workarounds are no longer necessary.

1. Put one of the workarounds in place in your DHCP configuration.

2. Add any new TFTP server to Service Monitor.

3. On your TFTP servers:

a. Delete the default sensor configuration file, QOVDefault.CNF, the sensor-specific configuration files QOV<MACAddress>.CNF, and the earlier binary image file, SvcMonAA2_nn.img.

b. Copy SvcMonAA2_37.img into the root directory.

4. From Service Monitor, edit the default sensor configuration file, entering SvcMonAA2_37.img as the image filename.

5. Verify that the new default sensor configuration file, QOVDefault.CNF, has been copied to the TFTP servers. If not, copy it from the image file directory on the Service Monitor server (NMSROOT\ImageDir) to the root on the TFTP servers.

6. Reset the sensors. To reset a sensor, you can restart the SPAN or RSPAN port on the switch to which the sensor is connected.

7. If desired, remove the workaround from your DHCP configuration.

Documentation Addenda

The following information is missing from the hardcopy, online help, or PDF versions of the Service Monitor documentation. The documentation on Cisco.com has been updated with this information.

Configuring the Service Monitor Client to Allow Popup Windows


Note This topic has been added to Quick Start Guide for Cisco Unified Service Monitor 2.0.


When using Service Monitor, disable any software on your desktop that you use to prevent popup windows from displaying. Service Monitor must be able to open multiple windows to display information.

Disabling Virus Scanning on the Databases Directory


Note This topic has been added to Quick Start Guide for Cisco Unified Service Monitor 2.0.


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.


Ensuring Successful Reinstallation


Note This step has been added to Quick Start Guide for Cisco Unified Service Monitor 2.0.


If you uninstall Service Monitor from a system, you should delete any files left in the NMSROOT directory prior to installing Service Monitor again on the same system.

Documentation Errata

The following information is missing from the online help and from the PDF user guide included in the online help and on the product CD and has been added to the user guide on Cisco.com.

Activating the AXL Web Service on Unified Communications Manager (Appendix B)

Perform this procedure for Unified Communications Manager versions 5.x and later.


Step 1 Launch Unified Communications Manager Serviceability.

Step 2 Select Tools > Service Activation.

Step 3 Select a server.


Note Activate the AXL Web Service on the Publisher node only.


Step 4 Scroll down to Database and Admin Services and select Cisco AXL Web Service.

Step 5 Click Save.


Obtaining Documentation and Submitting a Service Request

For information on obtaining documentation, submitting a service request, and gathering additional information, see the monthly What's New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at:

http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html

Subscribe to the What's New in Cisco Product Documentation as a Really Simple Syndication (RSS) feed and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free service and Cisco currently supports RSS version 2.0.