Guest

Cisco Unified Service Statistics Manager

Release Notes for Cisco Unified Service Statistics Manager 8.6

Table Of Contents

Release Notes for Cisco Unified
Service Statistics Manager 8.6

Product Documentation

Related Documentation

Known and Resolved Problems

Useful Information About Integration with Operations Manager and Service Monitor

Obtaining Documentation and Submitting a Service Request


Release Notes for Cisco Unified
Service Statistics Manager 8.6


Revised: August 18, 2011

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

Product Documentation

Related Documentation

Known and Resolved Problems

Useful Information About Integration with Operations Manager and Service Monitor

Obtaining Documentation and Submitting a Service Request

Product Documentation

Table 1 describes the product documentation that is available.

Table 1 Product Documentation 

Document Title
Available on Cisco.com at this URL

Release Notes for Cisco Unified Service Statistics Manager 8.6

http://www.cisco.com/en/US/products/ps7285/prod_release_notes_list.html

Quick Start Guide for Cisco Unified Service Statistics Manager 8.6

http://www.cisco.com/en/US/products/ps7285/prod_installation_guides_list.html

User Guide for Cisco Unified Service Statistics Manager 8.6

http://www.cisco.com/en/US/products/ps7285/products_user_guide_list.html

Context-sensitive online help

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


Related Documentation

Table 2 describes the additional documentation that is available.

Table 2 Related Documentation 

Document Title
Cisco.com URL Where Document Is Available

Release Notes for Cisco Unified Service Monitor 8.6

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

Cisco Unified Service Monitor 8.6 Compatibility Matrix

http://www.cisco.com/en/US/products/ps6536/products_device_support_tables_list.html

Installation Guide for Cisco Unified Service Monitor 8.6

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

User Guide for Cisco Unified Service Monitor 8.6

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

Release Notes for Cisco Unified Operations Manager 8.6

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

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

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

User Guide for Cisco Unified Operations Manager 8.6

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


Known and Resolved Problems

Table 3 lists problems known to exist in Service Statistics Manager 8.6. Some known problems occur due to changes made in Operations Manager and Service Monitor systems after integration with Service Statistics Manager; these are summarized in Useful Information About Integration with Operations Manager and Service Monitor. Table 4 lists problems that have been resolved in Service Statistics Manager 8.6.


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 3 Known Problems in Service Statistics Manager 8.6 

Bug ID
Summary
Explanation

CSCto49905

Call volume data is lost for one day.

When Service Statistics Manager has already discovered the system-defined call categories available in Service Monitor, if you add user-defined call categories and rediscover Service Statistics Manager, the first day after discovery, data for Call Volume By Cluster and Call Volume by Device Pool is not available.

Starting the next day, the data is collected.

Workaround:

As an alternative, you can use the Traffic Summary - Hour of the Day report to view the data.

CSCtn87053

User-defined call categories are not discovered.

User-defined call categories are not discovered after upgrade. This occurs because the user-defined call categories are not immediately available to Service Statistics Manager. After a few minutes, they become available.

Workaround:

Wait one hour, then run discovery.

CSCtn80063

Some locations display no data.

Some locations show no data for CAC location bandwidth utilization.

Workaround:

If CUSSM is deployed in co-residing mode, then restart SSM Agent on the SSM server. If CUSSM is installed in co-existence mode, then restart the SSM Agent on the CUOM server.

CSCtn41399

SIP trunk information is not collected.

Some trunks display no data for trunk utilization.

Workaround:

If CUSSM is deployed in co-residing mode, then restart SSM Agent on the SSM server. If CUSSM is installed in co-existence mode, then restart the SSM Agent on the CUSM server.

CSCtn89719

Operations Manager SSL port is not preserved during an upgrade of Service Statistics Manager.

When upgrading Service Statistics Manager on a system where Operations Manager is also installed, the https port entry for Operations Manager in the pronet.conf file is changed to 443. The result is that you cannot log into Service Statistics Manager.

Workaround:

Do one of the following:

Before upgrade—Add the following entry to the <CUSSM Installation folder>\pw\custom\conf\pronet.conf file:

pronet.ssm.om.port.https=CustomerOMSSLPortNum

After upgrade—Add the following entry to the <CUSSM Installation folder>\pw\custom\conf\pronet.conf file:

pronet.ssm.om.port.https=CustomerOMSSLPortNum

Then restart the Service Statistics Manager server.

CSCtj84199

The Busy Hour information displayed in reports is incorrect.

The Busy Hour information displayed in the time aggregation reports is incorrect.

Workaround:

Use a custom graph to view the Busy Hour information.

CSCta03506

How to clean up after failed installation or uninstallation

If Service Statistics Manager installation fails part of the way through, or if uninstallation fails, your system can be left in a state in which retrying the installation or uninstallation fails.

Workaround:

To workaround this problem, you must clean up your system as follows:

1. From the command line, enter this command: pw sys stop

2. Close all applications running on the server.

3. Edit the registry (using Regedit) to delete the following keys:

Uninstall keys for the SSM Administration Console, Service Statistics Manager server, and SSM agent:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{A57EBAA8-A035-483D-A0BA-3CB667CE5214}

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{B69A9D81-31FD-4B39-A4C7-9F0F0F774E0A}

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{DCD3461A-7AA6-44D3-9DC2-FE7B28DC7189}

Application key:

HKEY_LOCAL_MACHINE\SOFTWARE\CUSSM

Entries for the database service, agent service, server service, and Apache service:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\
Services\SQLANYe_CussmDB

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\
Services\ProNetAgent

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\
Services\ProNetServer

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\
CUSSMApache

4. Remove entries from the startup menu:

StartupMenuDirectory\Programs\Cisco Unified Service Statistics Manager

5. Delete the CUSSM folder now or after you complete step 6.

6. Restart the system.

CSCsz57462

Instance aggregation report limited to 25 trunks

When defining an Instance Aggregation report, you can include no more than 25 trunks. This limit applies even when the data will be displayed in a table (that is, when Show Only Table is selected in the report definition).

Workaround:

Do either of the following to produce a report with more than 25 trunks:

Create a Time Aggregation report; from this report, drill down to an Instance Aggregation report. When you configure the Time Aggregation report:

1. Include more than 25 trunks.

2. Select Show Only Table to accommodate the display of a large number of trunks.

From the command line on the Service Statistics Manager server, increase the limit:

1. Edit the pronet.conf file (located in the Installation Directory\pw\pronto\conf directory).

2. Look for this entry:

# Entries for configurations in reports graph display
pronet.report.display.noOfxValues=25

3. Replace the value "25" with a greater value and save the pronet.conf file.

4. Add the same property (from above) to the <Installation Directory>\pw\custom\conf\pronet.conf file.

5. Reload the properties for the Java server by entering this command:

pw j r 

CSCsx60244

Apostrophe in global comment distorted in graph or report

You can enter global comments to be displayed on graphs and reports. If you include an apostrophe (') in a global comment, it appears garbled in the graph or report.

Workaround:

Do not include apostrophes in global comments.

CSCsr21803

Service Statistics Manager stops collecting data

Service Statistics Manager stops collecting data from Operations Manager, Service Monitor, or both. This happens after Operations Manager, Service Monitor, or both are reinstalled to folders that are different from the those in which they were located when Service Statistics Manager performed discovery.

For example, the problem happens as follows:

1. Operations Manager is located in C:\Program Files\CSCOpx.

2. Service Statistics Manager performs discovery.

3. Operations Manager is reinstalled and, in place of C:\Program Files\CSCOpx, the following destination location is selected: C:\CSCOpx.

4. When polling for new data, the SSM agent continues to use the original path—C:\Program Files\CSCOpx—to look for the Operations Manager files and database.

Workaround:

Edit configuration files and update the path to Operations Manager, Service Monitor, or both on each system as follows:

On a system where Service Statistics Manager is installed with Operations Manager:

1. Change the paths as needed in both of these files:

Service Statistics Manager Installation Directory\pw\custom\conf\ciscodetails.conf

Service Statistics Manager Installation Directory\pw\custom\conf\pnagent.conf

2. Restart the server:

Select Start > Cisco Unified Service Statistics Manager > Stop Server

Select Start > Cisco Unified Service Statistics Manager > Start Server

On a remote system where SSM Agent is installed:

1. Change the paths as needed in both of the following files:

SSM Agent Installation Directory\Agent\custom\conf\ciscodetails.conf

SSSM Agent Installation Directory\Agent\custom\conf\pnagent.conf

2. On a system where SSM Administration Console is installed:

a. Log in to the SSM Administration Console.

b. Expand the Advanced Options and SSM Agent folders.

c. Right-click the IP address for the remote SSM agent and select Restart Agent.

CSCsq70177

Not all Operations Manager devices included in reports

In one case, more than 10 instances of Unified Communications Manager were added to Operations Manager. There were instances of Unified Communications Manager in each of the following device states:

Monitored

Partially Monitored

Unreachable

Data for fewer than 10 instances of Unified Communications Manager was included in Service Statistics Manager reports.

Circumstances:

Operations Manager does not produce performance data for devices unless they are in the Monitored device state. During discovery, Service Statistics Manager determines the devices for which data will be collected. Service Statistics Manager does not monitor each device in Operations Manager inventory. Of the devices that Service Statistics Manager supports, it monitors only those for which Operations Manager has collected data. (Much of the data that Service Statistics Manager uses is produced only when voice utilization polling is enabled for device groups in Operations Manager. By default, voice utilization polling is not enabled in Operations Manager.)

Workaround:

For Operations Manager (and Service Monitor) to provide the data that Service Statistics Manager relies upon, Operations Manager and Service Monitor must be configured correctly and devices must be reachable in the network. If you do not see particular Operations Manager devices in Service Statistics Manager reports:

Review the configuration information in Quick Start Guide for Cisco Unified Service Statistics Manager 8.5 and ensure that Operations Manager is configured to produce the data that Service Statistics Manager needs.

Become familiar with the type of data that Service Statistics Manager uses; see the "Devices, Monitor Types, and Attributes" appendix in User Guide for Cisco Unified Service Statistics Manager.

For any device that you do not see in Service Statistics Manager reports, do the following in Operations Manager:

Verify that the device state is Monitored. If it is not, perform any troubleshooting steps provided in the Operations Manager online help to ensure that the device goes to the Monitored state.

Confirm that data for the device exists in Operations Manager by creating a performance graph for it.

After devices in Operations Manager reach the Monitored state, retrigger discovery from Service Statistics Manager.

CSCts02051

Data for user defined call categories are not collected.

After upgrade from SSM version 8.5 to 8.6, the call volume by cluster and call volume by device pool data are not collected for the user defined call categories.

Workaround:

Restart the SSM agent.

CSCts25240

SSM data is not matching with SM data at 23:00 hrs in high load.

In co-existence performance system, when the call load is higher (500 calls/minute), at 23:00 hour of a day SSM data does not match the SM data.

Symptom:

Traffic Summary - Hour of Day report shows lower calls at 23:00 hours at high call volume.

Workaround:

Create a custom traffic summary report for the previous two days, after which, for the same day at 23:00 hrs, the data matches.


Table 4 Resolved Problems in Service Statistics Manager 8.6

Bug ID
Description

CSCtq89342

The average duration calculation formula was updated.

CSCtn83786

The Call Quality Summary report data did not matching the Call Quality Monitor.

CSCtn80047

The Traffic Summary and Call Quality monitors data did not match.


Useful Information About Integration with Operations Manager and Service Monitor

Service Statistics Manager relies on information that it stores about Operations Manager and Service Monitor. Changes that you make in Operations Manager and Service Monitor can disrupt Service Statistics Manager functioning. Service Statistics Manager relies on the following information:

The username and password for a user with System Administrator and Network Administrator privileges on Operations Manager—The default user admin has these privileges and can be used.

You might change the password for the admin user when you reinstall or upgrade Operations Manager. If you do, no one can log in to Service Statistics Manager.

To work around this problem,

a. From the command line on the Service Statistics Manager server, enter this command:

runjava scripts.ssm.UpdateOMPassword

You are prompted to enter and verify a password for the Operations Manager admin user. The admin user password for Operations Manager is updated in the Service Statistics Manager database.

b. From the Start menu, start and stop the SSM Server.

The installation directory for Operations Manager and for Service Monitor—When you run discovery, Service Statistics Manager stores the directory path for Operations Manager and for Service Monitor. You might change the directory in which one or the other is installed when you reinstall or upgrade either. If you do so, Service Statistics Manager stops collecting data. To work around this problem, see bug ID CSCsr21803.

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.