Guest

Cisco Unified Service Statistics Manager

Release Notes for Cisco Unified Service Statistics Manager 1.2

  • Viewing Options

  • PDF (251.5 KB)
  • Feedback
Release Notes for Cisco Unified Service Statistics Manager 1.2

Table Of Contents

Release Notes for Cisco Unified
Service Statistics Manager 1.2

New Features

Product Documentation

Related Documentation

Known Problems

Resolved Problems

Ensuring That You Have the Correct Service Statistics Manager Build ID Installed

Obtaining and Installing the Correct Service Statistics Manager 1.2 Build

Useful Information About Integration with Operations Manager and Service Monitor

What to Do when You Receive a Database Table Size Exceeded E-mail

Documentation Updates

User Guide—Chapter 7, Using Administration

Quick Start Guide

Notices

OpenSSL/Open SSL Project

License Issues

Obtaining Documentation and Submitting a Service Request


Release Notes for Cisco Unified
Service Statistics Manager 1.2


Revised: November 17, 2009

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

New Features

Product Documentation

Related Documentation

Known Problems

Resolved Problems

Documentation Updates

Notices

Obtaining Documentation and Submitting a Service Request

New Features

The following changes and enhancements are included in Service Statistics Manager 1.2:

New reports for the following devices and data:

Network Analysis Module (NAM) sensor-based call quality

Cisco Unified Communications Manager Express (CME) performance reports

New monitors:

Call quality by NAM

CME performance

System Utilization for Unity Connection

Upgrade from Service Statistics Manager 1.1—Data collected using Service Statistics Manager 1.1 is preserved.

Changes from Service Statistics Manager 1.1:

Call Volume monitor—New attributes for MGCP and SIP gateways.

Port usage—Different ports are used in Service Statistics Manager 1.2 than those used in previous releases. For the ports that are used, see Quick Start Guide for Service Statistics Manager 1.2.

Launching Service Statistics Manager—Include the HTTP web server port to launch the product as shown:

http://<servername>:11101

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 Statistics Manager 1.2

PDF on the product CD.

On Cisco.com at

http://cisco.com/en/US/docs/net_mgmt/
cisco_unified_service_statistics_manager/1.2/release/notes/
ReleaseNotesforCiscoUnifiedServiceStatisticsManager1_2.html

Quick Start Guide for Cisco Unified Service Statistics Manager 1.2

PDF on the product CD.

On Cisco.com at

http://cisco.com/en/US/docs/net_mgmt/
cisco_unified_service_statistics_manager/1.2/quick/guide/
QuickStartGuideCiscoUnifiedServiceStatisticsManager1_2.html

User Guide for Cisco Unified Service Statistics Manager

PDF on the product CD.

On Cisco.com at

http://cisco.com/en/US/docs/net_mgmt/
cisco_unified_service_statistics_manager/1.2/user/guide/
UserGuideforCiscoUnifiedServiceStatisticsManager.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


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
Cisco.com URL Where Document Is Available

Release Notes for Cisco Unified Service Monitor 2.2

http://www.cisco.com/en/US/docs/net_mgmt/cisco_unified_service_monitor/2.2/
release/notes/ReleaseNotesforCiscoUnifiedServiceMonitor2_2.html

Cisco Unified Service Monitor 2.2 Compatibility Matrix

http://cisco.com/en/US/docs/net_mgmt/
cisco_unified_service_monitor/2.2/sdt/
CiscoUnifiedServiceMonitorCompatibilityMatrix22.html

Installation Guide for Cisco Unified Service Monitor 2.2

http://cisco.com/en/US/docs/net_mgmt/
cisco_unified_service_monitor/2.2/installation/guide/
InstallationGuideforCiscoUnifiedServiceMonitor22.html

User Guide for Cisco Unified Service Monitor

http://cisco.com/en/US/docs/net_mgmt/
cisco_unified_service_monitor/2.2/user/
guide/UserGuideforCiscoUnifiedServiceMonitor2_2.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


Known Problems

Table 3 lists problems known to exist in Service Statistics Manager. 1.2. 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.


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 1.2 

Bug ID
Summary
Explanation

CSCtc59091

CUSSM 1.2 remains in evaluation mode with purchased license

After a purchased license is applied, Service Statistics Manager 1.2 license remains in evaluation mode.

Conditions:

This has been observed on VMware and non-VMware installations.

Workaround:

1. Delete the evaluation license file, cussm.lic, from this location:

<Installation directory>pw/licenses/cisco/etc/licenses/

2. Restart Service Statistics Manager: from the Start menu on the server, select Start > Programs > Cisco Unified Service Statistics Manager > Start Server.

CSCta34541

Lag in storing records (CDR or CMR) retrieved from Service Monitor

A delay can occur between the retrieval of the CDR and CMR information from Service Monitor and the insertion of this information into Service Statistics Manager. The delay might happen when the Service Statistics Manager CDR and CMR table sizes are too large (a few million rows) and if the pruning of the data in those tables is occurring or has occurred. The delay can result in the Service Statistics Manager tables and the Service Monitor tables becoming out of sync.

To address this issue, a Service Statistics Manager script runs every day at 7:15 p.m. The script sends an e-mail notification when the table sizes exceed 2.5 million records for the CDR table and 5 million records for the CMR table; the e-mail notification tells you to contact the Cisco Technical Assistance Center (TAC).

The e-mail notification contains the following information:

Reporting time

Current record count

Record count limit

Existing prune period (in hours)

Last time pruner executed

Data older than <Min. Time Stamp> are pruned

Message to contact Cisco TAC

When you receive an e-mail notification, you can decrease the data retention days to 20 or 15 days (default is 30 days), and run the pruner with the help of Cisco TAC to bring database table sizes within limits. Determine the new period to use for data retention based on the call volume observed in the deployment. Typically, the higher call volumes that cause the database table sizes to grow beyond the default limit happen in deployments of 30,000 or more phones. To change the data retention days and to reduce database table sizing, see What to Do when You Receive a Database Table Size Exceeded E-mail.

To ensure that you receive e-mail notifications, you must set the administrator e-mail ID and the SMTP hostname and port number. They are usually set during installation; however, you can still update them.

CSCta34541 (continued)

Lag in storing records (CDR or CMR) retrieved from Service Monitor (continued)

If the administrator e-mail ID was not set, set it as follows:

1. Log in to the Service Statistics Manager server and edit this file:

<Installation Directory>pw\etc\hosts\admin_user

2. Include a single entry (<e-mailID@domain.com>) in the file. For example:

jbgrayse@cisco.com

If the SMTP hostname and port number were not set, see "Updating the SMTP Server and Port Number" section in User Guide for Cisco Unified Service Statistics Manager.

Service Statistics Manager has been tested with a rate of 200 calls/minute and a data retention period of 30 days. This scenario does not cause the Service Statistics Manager database tables to become out of sync with the Service Monitor database tables. With this call rate, the out-of-sync condition appears when the Service Statistics Manager CDR table size exceeds 2.5 million records and the Service Statistics Manager CMR table size exceeds 5 million records.

However, if the call rate is greater than 200 calls/minute, the out-of-sync condition can occur with fewer records in the CDR and CMR tables. In such situations, Cisco TAC can configure Service Statistics Manager to send e-mail notification when there are fewer records than the default in the CDR and CMR tables.

Note A daily call volume of 200 calls/minute for 8 hours and 100 calls/minute for 2 hours generates approximately 2.37 million rows in the tables in 22 days.

CSCta03506

 

How to clean up after failed installation or uninstallation

If Service Statistics Manager installation fails part-way through, or if uninstallation fails, your system can be left in a state where 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\ASANYe_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.

CSCsq70177

 

Not all Operations Manager devices included in reports

The following was observed. More than 10 instances of Unified Communications Manager were added to Operations Manager. There were instances of Unified Communications Manager in each of these 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 1.2 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:

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

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

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

CSCsz20537

 

No Data Available shown on Voicemail views with Unity Connection

If you have Cisco Unity Connection (and not Cisco Unity), you see No Data Available for voicemail on the initial pages of these views:

Performance—Detailed Performance-Daily-VoiceMail Port Utilization for All Elements

This report includes Cisco Unity data only.

Utilization—Voicemail Port Utilization Over Time- Monthly, Weekly and Daily

This report includes data for Cisco Unity and Cisco Unity Connection. However, you must drill down to see that No Data Available is displayed for Cisco Unity and that data is available for Cisco Unity Connection.

Workaround:

Note that the Detailed Performance-Daily report does not include Cisco Unity Connection data.

Persist in drilling down from the initial pages of the Voicemail Port Utilization Over Time- Monthly, Weekly and Daily reports to the Unity Connection information.

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 an apostrophe in a global comment.

CSCsz26825

 

dbsrv and java_cntl process conflict

The database server was observed to shut down during a stress test due to a port conflict with another Service Statistics Manager process, pronet_cntl (java_cntl.exe).

Workaround:

Restart the SSM server:

1. Log into the Service Statistics Manager server.

2. Select Start > All Programs > Cisco Unified Service Statistics Manager Server > Stop Server.

3. Select Start > All Programs > Cisco Unified Service Statistics Manager Server > Start Server.

CSCsz57462

 

Instance aggregation report limited to 25 trunks

When defining an Instance Aggregation report, you can include up to 25 trunks only. This is so even when the data will be displayed in a table (that is, Show Only Table is selected in the report definition).

Workaround:

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

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

1. You can 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. Reload the properties for the Java server by entering this command:

pw j r 

CSCsz44590

 

Call Quality Summary shows incorrect average

The average value for good calls and fair calls is incorrect. If you add the data points shown on the graph and average them, the result does not match the average value displayed on the graph.

Workaround:

There is no workaround.

CSCsy58383

 

Headings not aligned with data in e-mailed reports

Reports that are received and read using e-mail look misaligned. Column headings do not line up with data. This problem occurs when using Outlook 2003.

Workaround:

1. In Outlook 2003, select Tools > Options.

2. On the Security tab, click Change automatic download settings. A dialog box opens.

3. Uncheck the option Don't download pictures or other content automatically in HTML.

4. Click OK.

CSCta07283

 

No abandoned calls reported

Zero (0) abandoned calls are shown in these default reports:

Call Completion Rate Across Clusters—Monthly

Failed Calls Across Clusters—Monthly

and in any report based on the Call Volume monitor type when you select the abandoned calls attribute.

There is no recommended workaround for this problem.

CSCsr62218

 

Discovery fails with invalid session exception

You trigger discovery and it fails. Service Statistics Manager does not discover Operations Manager because the IP address used in the login registration and the subsequent calls are different. An invalid session exception occurs.

To determine whether this is the case, look in the <Installation Directory>\pw\pronto\logs\ProactiveNet.log file for the following exception:

com.cisco.nm.nbi.cwcs.nbifw.InvalidSessionException

Workaround:

If you find that the invalid session exception occurred, resolve it by doing the following:

1. Log in to the Operations Manager server.

2. Edit the <NMSROOT>\lib\classpath\ss.properties file and set the SS_CHECKIP property to false:

SS_CHECKIP=false

3. Restart the daemon manager as follows:

From the command prompt, enter this text:

net stop crmdmgtd


Wait 15 minutes.

From the command prompt, enter this text:

net start crmdmgtd

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 > Stop Server

On a remote system where SSM Agent is installed:

1. Change the paths as needed in both of these 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.

CSCso85594

Service Statistics Manager no longer accessible if Operations Manager admin user password changes

 

The problem happens in this scenario:

1. From Service Statistics Manager:

a. Enter a username and password for Operations Manager.

b. Perform discovery.

2. After Service Statistics Manager discovers Operations Manager, change the password for the admin user in Operations Manager.

3. Restart the Service Statistics Manager server.

4. Try to log in to Service Statistics Manager.

5. An error occurs: "Unable to validate CUSSM license information. Please check the OM licensing info..."

Workaround:

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

runjava scripts.ssm.UpdateOMPassword

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

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

CSCso33613

 

ApacheCore_dll service errors

After restarting SSM Server, a window pops up repeatedly with this message: "Apache.exe encountered a problem and needs to close."

No functional impacts occur due to this pop-up.

To work around this problem, you can turn off the Windows error reporting feature by doing the following while logged into the Service Statistics Manager server:

1. Open Control Panel.

2. Click System.

3. Click the Advanced tab.

4. Click the Error Reporting button.

5. Select both the Disable Error Reporting radio button and the But notify me when critical errors occur check box.

6. Click OK. The window closes.

7. Click OK on the remaining window.


Resolved Problems

Table 4 lists problems that are resolved in Service Statistics Manager 1.2.

Table 4 Problems Resolved in Service Statistics Manager 1.2 

Bug ID
Description

CSCsr04818

SSM advertises in reserve ports 1099, 1100 for JBoss

CSCsr52906

System error when generating custom graphs for longer term

CSCsq90690

Initial polling after midnight can result in No Response from Operations Manager

CSCsu95263

Error when starting discovery


Table 5 describes additional problems that existed in Service Statistics Manager 1.2 Build ID 207 (available July 2009) and were resolved in Service Statistics Manager 1.2 Build ID 227 (available October 2009).


Note If Service Statistics Manager 1.2 Build ID 207 is installed on your system, you must reinstall Service Statistics Manager 1.2 using Build ID 227. For more information, see Ensuring That You Have the Correct Service Statistics Manager Build ID Installed.


Table 5 Problems Resolved in Service Statistics Manager 1.2 Build 227 

Bug ID
Description

CSCtb28717

Users can edit Call Quality Ranges without configure rights

CSCta17818

SSM should collect data for both MGCP and H323 gateways

CSCtb90153

Duplicate monitor instances created after the upgrade to 1.2

CSCtb98364

Socket failure when SSM tries to connect to CUOM


Ensuring That You Have the Correct Service Statistics Manager Build ID Installed

Table 6 lists Service Statistics Manager 1.2 build IDs.

Table 6 Service Statistics Manager 1.2 Build IDs

Build ID
Description

207

The problems in Table 5 exist in this build.

227

This build resolves the problems listed inTable 5.


If Service Statistics Manager 1.2 Build ID 207 is installed on your system, you must reinstall Service Statistics Manager 1.2 using build 227.

To determine which build is installed on your system, click the About link in the upper-right corner of the Service Statistics Manager window. The product version and build ID are included in the display.

If Service Statistics Manager 1.2 Build ID 207 is installed on your system, follow the instructions in Obtaining and Installing the Correct Service Statistics Manager 1.2 Build.

Obtaining and Installing the Correct Service Statistics Manager 1.2 Build

If Service Statistics Manager 1.2 Build ID 207 is installed on your server, you must perform the following steps:

1. From the Download Software page for Service Statistics Manager 1.2, download the Cisco Unified Service Statistics Manager 1.2 executable file from Cisco.com to the server.

2. Before you start the reinstallation, back up the database manually. See Quick Start Guide for Cisco Unified Service Statistics Manager.

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

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 this information:

The username and password for a user with System Administrator and Network Administrator privilege 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. For a workaround to this problem, see bug ID CSCso85594.

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 Operations Manager or Service Monitor is installed when you reinstall or upgrade Operations Manager or Service Monitor. If you do so, Service Statistics Manager stops collecting data. For a workaround to this problem, see bug ID CSCsr21803.

What to Do when You Receive a Database Table Size Exceeded E-mail

Before performing any tasks in this section, you should contact Cisco TAC for assistance.

After receiving an e-mail alert regarding table sizing (see the explanation for CSCta34541 in Table 3), you should perform the following procedure (with the help of Cisco TAC):


Step 1 Determine an appropriate new prune interval based on call volume.

Step 2 Update the prune interval (the data retention days):

a. Run runjava scripts.PruneEntry -update <TableName> <NewDeltaHrs>.

For example, runjava scripts.PruneEntry -update SSM_CDR_TABLE 360.

changes the prune period (data retention) for SSM_CDR_Table to 360 hours (15 days).

b. Run runjava scripts.PruneEntry -update SSM_CMR_TABLE 360.

This changes the prune period (data retention) for SSM_CMR_Table to 360 hours (15 days).

Step 3 Make sure that the pruner is running. Stop the Service Statistics Manager server if a very large amount of data needs to be pruned. This might occur on a system that was upgraded from Service Monitor 1.1.

Pruning might take a few hours to complete, depending on the amount of data to be purged.

Step 4 Examine the database to make sure that pruning has completed. Run the following commands:

a. runjava scripts.PruneEntry -list <tablename>.

For example, runjava scripts.PruneEntry -list ssm_cdr_table.

b. runjava scripts.PruneEntry -list ssm_cmr_table.

In the tables, look in the MinTimeStamp field. This field lists the time stamp of the oldest data present in the table. If a time exists that is older than the current time, the pruning is not complete.

Step 5 When the prune period is reduced, some of the reports (most notably the Traffic Summary - Day of Month report) will need to be updated because they are monthly reports based on the CDR tables.

To modify the frequency and reporting period of the report, perform the following commands:

a. runjava scripts.UpdateReportDetails <Report Title> <DB_COL_NAME> <DATATYPE> <NEWVALUE>

For example, runjava scripts.UpdateReportDetails "Traffic Summary - Day of Month" PERIODID NUM 5.

This sets the reporting period to the last 15 days.

b. runjava scripts.UpdateReportDetails "Traffic Summary - Day of Month" FREQUENCYID NUM 2.

This sets the frequency of the report generation to weekly.

Step 6 Restart the Service Statistics Manager server.

Step 7 (Optional) You can specify any number of tables and the corresponding limit through the settings in the <CUSSM_INSTALL_DIR>\pw\pronto\conf\pronet.conf file.

Following are the settings you might want to change:

pronet.rowcheck.tablecount = 2

pronet.rowcheck.table1.name = SSM_CDR_TABLE

pronet.rowcheck.table1.limit = 2500000

pronet.rowcheck.table2.name = SSM_CMR_TABLE

pronet.rowcheck.table2.limit = 5000000

If you change any of these settings, you must run the following command in a command prompt to reload these jserver properties:

pw j r


Documentation Updates

The following information is missing from the online help and the user guide that is available from online help. However, it is present in the documentation on Cisco.com.

User Guide—Chapter 7, Using Administration

The following section was added to the topic Understanding the Default Dial Plan.

How Service Statistics Manager Handles Special Characters in Directory Numbers

The data that Service Statistics Manager receives might include directory numbers that contain special characters. This is how Service Statistics Manager handles directory numbers that contain these special characters:

Plus sign (+):

If the initial character in a directory number is a plus sign, Service Statistics Manager drops the plus sign and continues to process the data.

If the plus sign appears in a position other than the initial character of a directory number, Service Statistics Manager does not process the data.

Other special characters (#, "," (comma), @)—If #, comma, or @ appear anywhere in a directory number, Service Statistics Manager does not process the data.

Configuring Service Statistics Manager to Connect with Operations Manager (Updated)

These are the updated instructions for running ConfigureSSMtoSSLOM:

1. Determine whether Operations Manager uses an SSL port other than 443 (the default SSL port).

2. If Operations Manager uses an SSL port other than 443, perform these steps:

Navigate to this directory: <Installation Directory>\pw\pronto\conf

Edit the pronet.conf file and, find this line: pronet.ssm.om.port.https=443

Replace 443 with the SSL port that Operations Manager uses

3. On your Service Statistics Manager system, navigate to this directory: <Installation Directory>/pw/pronto/bin and open a command prompt.

4. From the command prompt, type this: ConfigureSSMToSSLOM <servername> <OMSSLport> where:

servername is the IP address or DNS name of the Operations Manager server.

(Optional) OMSSLport is the SSL port that Operations Managers uses. If you do not provide a value, the default SSL port 443 is used.

5. Press Enter. Several messages are displayed.

6. Restart the Service Statistics Manager server. From the command prompt, type:
pw sys start

7. Close any existing browser sessions.

8. Start your browser again and log in to Service Statistics Manager.

Quick Start Guide

The following updated information is provided wherever instructions for running ConfigureSSMtoSSLOM are provided:

1. Determine whether Operations Manager uses an SSL port other than 443 (the default SSL port).

2. If Operations Manager uses an SSL port other than 443, perform these steps:

Navigate to this directory: <Installation Directory>\pw\pronto\conf

Edit the pronet.conf file and, find this line: pronet.ssm.om.port.https=443

Replace 443 with the SSL port that Operations Manager uses

3. On your Service Statistics Manager system, navigate to this directory: <Installation Directory>/pw/pronto/bin and open a command prompt.

4. From the command prompt, type this: ConfigureSSMToSSLOM <servername> <OMSSLport> where:

servername is the IP address or DNS name of the Operations Manager server.

(Optional) OMSSLport is the SSL port that Operations Managers uses. If you do not provide a value, the default SSL port 443 is used.

5. Press Enter. Several messages are displayed.

6. Restart the Service Statistics Manager server. From the command prompt, type:
pw sys start

7. Close any existing browser sessions.

8. Start your browser again and log in to Service Statistics Manager.

Notices

The following notices pertain to this software license.

OpenSSL/Open SSL Project

This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit (http://www.openssl.org/).

This product includes cryptographic software written by Eric Young (eay@cryptsoft.com).

This product includes software written by Tim Hudson (tjh@cryptsoft.com).

License Issues

The OpenSSL toolkit stays under a dual license, i.e. both the conditions of the OpenSSL License and the original SSLeay license apply to the toolkit. See below for the actual license texts. Actually both licenses are BSD-style Open Source licenses. In case of any license issues related to OpenSSL please contact openssl-core@openssl.org.

OpenSSL License:

Copyright © 1998-2007 The OpenSSL Project. All rights reserved.

Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

1. Redistributions of source code must retain the copyright notice, this list of conditions and the following disclaimer.

2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions, and the following disclaimer in the documentation and/or other materials provided with the distribution.

3. All advertising materials mentioning features or use of this software must display the following acknowledgment: "This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit (http://www.openssl.org/)".

4. The names "OpenSSL Toolkit" and "OpenSSL Project" must not be used to endorse or promote products derived from this software without prior written permission. For written permission, please contact openssl-core@openssl.org.

5. Products derived from this software may not be called "OpenSSL" nor may "OpenSSL" appear in their names without prior written permission of the OpenSSL Project.

6. Redistributions of any form whatsoever must retain the following acknowledgment:

"This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit (http://www.openssl.org/)".

THIS SOFTWARE IS PROVIDED BY THE OpenSSL PROJECT "AS IS"' AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE OpenSSL PROJECT OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

This product includes cryptographic software written by Eric Young (eay@cryptsoft.com). This product includes software written by Tim Hudson (tjh@cryptsoft.com).

Original SSLeay License:

Copyright © 1995-1998 Eric Young (eay@cryptsoft.com). All rights reserved.

This package is an SSL implementation written by Eric Young (eay@cryptsoft.com).

The implementation was written so as to conform with Netscapes SSL.

This library is free for commercial and non-commercial use as long as the following conditions are adhered to. The following conditions apply to all code found in this distribution, be it the RC4, RSA, lhash, DES, etc., code; not just the SSL code. The SSL documentation included with this distribution is covered by the same copyright terms except that the holder is Tim Hudson (tjh@cryptsoft.com).

Copyright remains Eric Young's, and as such any Copyright notices in the code are not to be removed. If this package is used in a product, Eric Young should be given attribution as the author of the parts of the library used. This can be in the form of a textual message at program startup or in documentation (online or textual) provided with the package.

Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

1. Redistributions of source code must retain the copyright notice, this list of conditions and the following disclaimer.

2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.

3. All advertising materials mentioning features or use of this software must display the following acknowledgement:

"This product includes cryptographic software written by Eric Young (eay@cryptsoft.com)".

The word `cryptographic' can be left out if the routines from the library being used are not cryptography-related.

4. If you include any Windows specific code (or a derivative thereof) from the apps directory (application code) you must include an acknowledgement: "This product includes software written by Tim Hudson (tjh@cryptsoft.com)".

THIS SOFTWARE IS PROVIDED BY ERIC YOUNG "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

The license and distribution terms for any publicly available version or derivative of this code cannot be changed. i.e. this code cannot simply be copied and put under another distribution license [including the GNU Public License].

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.