Cisco Cisco Unified Service Monitor 8.5 White Paper

 

White Paper 

 

© 2007 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information. 

Page 15 of 26

Cisco Unified Communications Manager 5.x or 4.2 can be used as the TFTP server. 

 If you use Cisco Unified Communications Manager as a TFTP server, Service Monitor cannot copy 
configuration files to Cisco Unified Communications Manager due to security settings on the latter. 
You will need to manually upload the configuration file. After uploading the configuration file, reset 
the TFTP server on Cisco Unified Communications Manager. For more information, see Cisco 
Unified Communications Manager documentation. 

Service Monitor can collect and analyze data from Cisco Unified Communications Manager. Follow 
the configuration steps described in the user guide in the “Cisco Unified Communications Manager 
Configuration” section or go to 

These are some important points that you should be aware of when you are configuring Cisco 
Unified Communications Manager:  

● 

If you don’t see call records in the Cisco Voice Transmission Quality reports, make sure 
CDR and CMR are enabled on all call manager nodes of a cluster. 

● 

Make sure that the cluster ID is unique in the system; System Monitor will generate an error 
when a duplicate cluster is entered. 

● 

Make sure that on the call manager Enterprise Parameter Configuration page the CDR File 
Time Interval is set to 1 (minute). This determines how frequently call manager generates 
CDRs. (Typically this is not changed.) 

● 

Check the owner of the sm_record_create_table in the CDR database after adding call 
manager to the Service Monitor server. Make sure the table owner is dbo. Caution: call 
manager cannot write CDRs to the database if the sm_record_create_table owner is not 
dbo 

This section describes the tasks that should be performed during Service Monitor installation. 

Perform the following checks before installing Service Monitor: 

● 

Dual homing (dual network interface cards [NICs]), using two different IP addresses, is not 
supported on Service Monitor. If, during installation, you receive a warning message to edit 
a file named gatekeeper.cfg, then your server is dual homed, and you must disable one of 
the network interface card (NIC) interfaces before adding any devices to Service Monitor. 
Using two NICs with a single IP address (a failover configuration, in case one of the NIC 
cards fails) is supported. 

● 

Make sure that you change the default call manager cluster ID setting (located at call 
manager Administration > Enterprise parameters). The default setting is Standalone Cluster. 
Unless you change this entry, all of the clusters will have the same cluster ID. This causes 
problems in Service Monitor. Changing the cluster ID requires a restart of RIS Collector 
service, Windows Simple Network Management Protocol (SNMP) service, and the 
CCMadmin service. Perform these restarts on the publisher and then on the subscribers.