Guest

Cisco Prime Unified Service Monitor

Release Notes for Cisco Unified Service Monitor 2.2

  • Viewing Options

  • PDF (172.9 KB)
  • Feedback
Release Notes for Cisco Unified Service Monitor 2.2

Table Of Contents

Release Notes for Cisco Unified
Service Monitor 2.2

New Features

Product Documentation

Related Documentation

Compatible Phones, Gateways, and Software Versions

Required Unified Communications Manager Patches and Workarounds

Known and Resolved Problems

Ensuring That You Have the Correct Service Monitor Build ID Installed

Obtaining and Installing the Correct Service Monitor 2.2 Build

Documentation Updates

Finding the Build ID for an Installed Service Monitor

Obtaining Documentation and Submitting a Service Request

SUPPLEMENTAL LICENSE AGREEMENT


Release Notes for Cisco Unified
Service Monitor 2.2


Revised: October 8, 2009, OL-16482-01

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

New Features

Product Documentation

Related Documentation

Compatible Phones, Gateways, and Software Versions

Known and Resolved Problems

Documentation Updates

Obtaining Documentation and Submitting a Service Request

SUPPLEMENTAL LICENSE AGREEMENT

New Features

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

Support Cisco Network Analysis Modules (NAMs) as sensors.

Correlate sensor data—RTP streams from Cisco 1040s and NAMs— and CVTQ data, the call detail record, if available. (Launch the Sensor Stream Correlation window from the Sensor Diagnostics report).

Automate time synchronization between Cisco 1040s and Service Monitor.

Update support for Cisco Unified Communications Manager (Unified Communications Manager):

Added support for software version 7.1(2a).

Removed support for software version 3.3; it is no longer sold.

Upgrade the Service Monitor framework to use Common Services 3.2.

Update the binary image for Cisco 1040s.

Resolve problems listed in Table 5.

Support upgrade. Configuration data—such as data source credentials, threshold settings, and so on—migrates automatically during upgrade. You can optionally migrate report data using a separate tool before you perform the upgrade. For more information about the Call Migration Tool, see Installation Guide for Cisco Unified Service Monitor 2.2.

User documentation upgrade—Cisco Unified Service Monitor 2.2 Compatibility Matrix 2.2 is a new document. Quick Start Guide for Cisco Unified Service Monitor 2.2 is replaced by Installation Guide for Cisco Unified Service Monitor 2.2.

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

Release Notes for Cisco Unified Service Monitor 2.2

Within the Documentation folder on the product CD-ROM

On Cisco.com at
http://cisco.com/en/US/docs/net_mgmt/cisco_unified_service_monitor/2.2/
release/ReleaseNotesforCiscoUnifiedServiceMonitor2_2.html

Cisco Unified Service Monitor 2.2 Compatibility Matrix

Within the Documentation folder on the product CD-ROM

On Cisco.com at
http://www.cisco.com/en/US/docs/net_mgmt/cisco_unified_service_monitor/2.2/
sdt/CiscoUnifiedServiceMonitorCompatibilityMatrix2_2.html

Installation Guide for Cisco Unified Service Monitor 2.2

Within the Documentation folder on the product CD-ROM

On Cisco.com at
http://cisco.com/en/US/docs/net_mgmt/cisco_unified_service_monitor/2.2/
installation/guide/InstallationGuideforCiscoUnifiedServiceMonitor2_2.html

User Guide for Cisco Unified Service Monitor

Within the Documentation folder on the product CD-ROM

On Cisco.com at
http://cisco.com/en/US/docs/net_mgmt/cisco_unified_service_monitor/2.2/user/
guide/UserGuideforCiscoUnifiedServiceMonitor2_2.html

Context-sensitive online help

Click the Help link in the upper-right hand corner of the window or the help button in any dialog box.


Related Documentation


Note The originally published printed and electronic documentation was 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
Available on Cisco.com at These URLS

Quick Start Guide for Cisco 1040 Sensor

http://cisco.com/en/US/docs/net_mgmt/cisco_unified_service_monitor/2.1/quick/guide/1040qs21.html

Release Notes for Cisco Unified Operations Manager 2.2

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

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

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

User Guide for Cisco Unified Operations Manager

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

Release Notes for CiscoWorks Common Services 3.2

http://www.cisco.com/en/US/docs/net_mgmt/ciscoworks_common_services_software/3.2/release/notes/cs32rel.html

User Guide for CiscoWorks Common Services 3.2

http://www.cisco.com/en/US/docs/net_mgmt/ciscoworks_common_services_software/3.2/user/guide/cs32ug.html


Compatible Phones, Gateways, and Software Versions

For supported phones, software versions, and, where applicable, configuration notes and hardware models, see Cisco Unified Service Monitor 2.2 Compatibility Matrix. It includes information for the following:

Cisco Unified Communications Management Suite products

Cisco Unified Communications Manager

Cisco 1040 Sensor binary image

Cisco Unified IP Phones

Voice gateways

Cisco Network Analysis Module software (and hardware)

Required Unified Communications Manager Patches and Workarounds

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

Table 3 Circumstances that Can Affect CVTQ Data 

Description
Circumstances

After 1-3 days, no new CVTQ data from Unified Communications Manager 7.0(1)

This happens when Service Monitor runs in VMware and makes simulated calls to Unified Communications Manager 7.0(1). After the problem occurs, report data (such as device type and directory number) also starts to be missing for Unified Communications Manager versions earlier than 7.0(1).

The problem does not occur when Service Monitor runs outside of a virtual environment. The problem also does not occur when Service Monitor runs in a virtual environment and simulates calls against Unified Communications Manager 6.x.

Bug ID: CSCsx63386

This problem has been fixed in Unified Communications Manager:

7.0(1.39000.100)

7.0(1.21021.001)

7.1(1.39151.4) (verified)

Service Monitor CVTQ reports do not show any calls in a Unified Communications Manager 5.0 cluster

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

Bug ID: CSCsd81400

This problem has been fixed and verified in Unified Communications Manager 5.0(3.9911.35).

Workaround: If you do not have the Unified Communications Manager 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 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 Unified Communications Manager:

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

b. Select the Unified Communications Manager server.

c. Click the Restart button.

3. Remove old files from the Unified Communications Manager 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_.


Known and Resolved 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 resolved problems, see Table 5 and Table 6.

Table 4 Known Problems in Service Monitor 2.2 

Bug ID
Summary
Explanation

CSCta62868

Data exported from sensor report differs from what is displayed

This problem occurs when you view a trap on the Operations Manager Service Quality Alerts display, launch a Service Monitor sensor report for the trap, and export a range of rows from the sensor report. The resultant CSV file contains data that does not match what is displayed in the sensor report.

Workaround

To obtain an export file with the correct data:

1. In Service Monitor, select Reports > Diagnostics > Sensor.

2. Enter the endpoints and time range that are shown in the existing report.

3. Generate the report and export the data.

CSCsx97730

Most-Impacted Sensor report incorrect when multiline phone

When calls are made from a single-line phone to directory numbers on a multiline phone, the Most-Impacted Sensor report includes only one of the directory numbers on the multiline phone.

For example:

Phone 1—Single-line phone (directory number: 48003)

Phone 2 —Multiline phone (directory numbers: 48006 and 48007)

From Phone 1 (48003), make two calls: to 48006 and to 48007.

In Most-Impacted Sensor report, only 48007 is displayed as an endpoint.

Workaround:

There is no workaround.

CSCsx21444

CUSM and CUPM interop: AXL request conflict on CUCM



Do not add or edit credentials for Unified Communications Manager while Provisioning Manager performs synchronization.

CSCsy01378

Apache error on local machine

When you log in to the Windows system where Service Monitor is installed, you might see a few dialog boxes that show Apache errors. This happens on initial reboot of the system.

Workaround:

The errors are harmless and you can close the dialog boxes.

Monitored phone count can lag device discovery

There might be a lag of up to one minute between the time that Service Monitor discovers devices and the time when the monitored phone count is updated.

Workaround:

There is no workaround for this problem.


Table 5 describes problems resolved since the previous release of Service Monitor.

Table 5 Problems Resolved in Service Monitor 2.2 

Bug ID
Summary

CSCsi66458

Cluster deleted in verifying state doesn't get deleted

CSCsj45638

Editing Cisco 1040 Sensor configuration files causes problems

CSCso79022

Device type is N/A when CVTQ report generated after 30 minutes

CSCso79417

Device type and name are N/A in sensor report after changing IP address

CSCsr54308

MOH streams erroneously reported as calls with packet loss

CSCsr87157

Partial data in Top N report after QOVR restart

CSCsi71681

CVTQ, Sensor Reports don't show latest data when > 2000 records match

CSCsi86375

Diagnostic report data incorrect for some nondirect calls


Table 6 describes additional problems that existed in Service Monitor 2.2 Build ID NT_SM2_2_20090708_1229 (available July 2009) and were resolved in Service Monitor 2.2 Build ID NT_SM2_2_20090925_1028 (available October 2009).


Note If Service Monitor 2.2 Build ID NT_SM2_2_20090708_1229 is installed on your system, you must reinstall Service Monitor 2.2 using Build ID NT_SM2_2_20090708_1229. For more information, see Ensuring That You Have the Correct Service Monitor Build ID Installed.


Table 6 Problems Resolved in Service Monitor 2.2 Build ID NT_SM2_2_20090925_1028 

Bug ID
Summary

CSCtb37913

Service Monitor stops processing CDR data in certain circumstances

CSCta45794

QOVR SMDBMonitor restarting in loop due to duplicate cluster IDs


Ensuring That You Have the Correct Service Monitor Build ID Installed

Table 7 lists Service Monitor build IDs.

Table 7 Service Monitor Build IDs

Build ID
Description

NT_SM2_2_20090708_1229

The problems in Table 6 exist in this build.

NT_SM2_2_20090925_1028

This build resolves the problems listed inTable 6.


If Service Monitor 2.2 Build ID NT_SM2_2_20090708_1229 is installed on your system, you must reinstall Service Monitor 2.2 using build NT_SM2_2_20090925_1028.

To determine which build is installed on your system, see Finding the Build ID for an Installed Service Monitor.

If Service Monitor 2.2 Build ID NT_SM2_2_20090708_1229 is installed on your system, follow the instructions in Obtaining and Installing the Correct Service Monitor 2.2 Build.

Obtaining and Installing the Correct Service Monitor 2.2 Build

If Service Monitor 2.2 Build ID NT_SM2_2_20090708_1229 is installed on your server, you must perform the following steps:

If Service Monitor 2.2 runs standalone on your server:

1. From the Download Software page for Service Monitor 2.2, download the Cisco Unified Service Monitor 2.2 executable file from Cisco.com to the server.

2. Before you start the reinstallation, back up the database manually. See Installation Guide for Cisco Unified Service Monitor.

3. To start the reinstallation, double-click the executable file and follow the online prompts. For more information, see Installation Guide for Cisco Unified Service Monitor.

If Service Monitor 2.2 and Operations Manager 2.2 run on the same server:

1. From the Download Software page for Operations Manager 2.2, download the Cisco Unified Operations Manager 2.2 executable file from Cisco.com to the server.


Note Service Monitor build ID NT_SM2_2_20090925_1028 is included with
Operations Manager build ID NT_OM22CS32_20090930_1223.


2. Before you start the reinstallation, perform a backup and stop the Health Monitor service.

3. To start the reinstallation, double-click the executable file and follow the online prompts. For more information, see Installation Guide for Cisco Unified Operations Manager 2.2 (Includes Service Monitor 2.2).

4. After the reinstallation completes, rediscover devices.

Documentation Updates

The following topic has been added to User Guide for Cisco Unified Service Monitor on Cisco.com; however, the topic is missing from the online help and user guide that are included with the Service Monitor product.

Finding the Build ID for an Installed Service Monitor

Occasionally for troubleshooting purposes, you might need to know which build of Service Monitor is installed. You can find the build ID as follows:

1. Click CiscoWorks from the upper-right corner on the Service Monitor home page. A new window opens.

2. Select Software Center > Software Update under Common Services. A new window opens.

3. Click the appropriate link (Cisco Unified Service Monitor n.n where n.n is the software release version) under Products Installed. A new window opens.

4. See the value labeled "Build Id" at the top of the page; for example, Build Id: NT_SM2_2_20090925_1028.


Note NT_SM2_2_20090925_1028 is an example that illustrates the build ID format.


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.

SUPPLEMENTAL LICENSE AGREEMENT

SUPPLEMENTAL LICENSE AGREEMENT FOR CISCO SYSTEMS NETWORK MANAGEMENT SOFTWARE: CISCO UNIFIED SERVICE MONITOR.

IMPORTANT-READ CAREFULLY: This Supplemental License Agreement ("SLA") contains additional limitations on the license to the Software provided to Customer under the End User License Agreement between Customer and Cisco. Capitalized terms used in this SLA and not otherwise defined herein shall have the meanings assigned to them in the End User License Agreement. To the extent that there is a conflict among any of these terms and conditions applicable to the Software, the terms and conditions in this SLA shall take precedence.

By installing, downloading, accessing or otherwise using the Software, Customer agrees to be bound by the terms of this SLA. If Customer does not agree to the terms of this SLA, Customer may not install, download or otherwise use the Software. When used below, the term "server" refers to central processor unit.


1. ADDITIONAL LICENSE RESTRICTIONS.

Installation and Use. The Software components are provided to Customer solely to install, update, supplement, or replace existing functionality of the applicable Network Management Software product. Customer may install and use the following Software components:

CiscoWorks Common Services: Contains shared resources used by other components in this bundle. In many cases, all components in this bundle can be installed on a single server.

Cisco Unified Service Monitor: May be installed on one (1) server in Customer's network management environment.

Number of IP Phones. For each Software license granted, Customer may install and run the Software on a single server to manage the number of IP phones specified in the license file provided with the Software, or as specified in the Software License Claim Certificate. Customers whose requirements exceed the IP phone limit must purchase upgrade licenses or additional copies of the Software. The IP phone limit is enforced by license registration.

Reproduction and Distribution. Customer may not reproduce nor distribute the Software.

2. DESCRIPTION OF OTHER RIGHTS AND LIMITATIONS.

Please refer to the Cisco Systems, Inc. End User License Agreement.