Cisco Cisco Unified Service Statistics Manager 9.0 Release Notes
3
Release Notes for Cisco Unified Service Statistics Manager 9.0
OL-27657-01
Known and Resolved Problems
Table 1
Known Problems in Service Statistics Manager 9.0
Bug ID
Summary
Explanation
CSCty64488
Unified SSM does not work on a Windows 2008
R1 64-bit server if it is installed in C:\Program
Files (x86)\.
R1 64-bit server if it is installed in C:\Program
Files (x86)\.
If Unified SSM is installed in C:\Program Files (x86)\ on
a Windows 2008 R1 64-bit system, the processes do not
come up after installation. Unified SSM will not work if
it is installed in this particular location.
a Windows 2008 R1 64-bit system, the processes do not
come up after installation. Unified SSM will not work if
it is installed in this particular location.
Workaround:
Install Unified SSM in any folder other than Program
Files (x86).
Files (x86).
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.
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.
Hour of the Day report to view the data.
CSCtn80063
Some locations display no data.
Some locations show no data for CAC location
bandwidth utilization.
bandwidth utilization.
Workaround:
If SSM is deployed in co-residing mode, then restart
SSM Agent on the SSM server. If SSM is installed in
co-existence mode, then restart the SSM Agent on the
OM server.
SSM Agent on the SSM server. If SSM is installed in
co-existence mode, then restart the SSM Agent on the
OM server.
CSCtn41399
SIP trunk information is not collected.
Some trunks display no data for trunk utilization.
Workaround:
If SSM is deployed in co-residing mode, then restart
SSM Agent on the SSM server. If SSM is installed in
co-existence mode, then restart the SSM Agent on the
SM server.
SSM Agent on the SSM server. If SSM is installed in
co-existence mode, then restart the SSM Agent on the
SM server.
CSCtj84199
The Busy Hour information displayed in reports
is incorrect.
is incorrect.
The Busy Hour information displayed in the time
aggregation reports is incorrect.
aggregation reports is incorrect.
Workaround:
Use a custom graph to view the Busy Hour information.