Guest

Cisco Prime Unified Service Monitor

Frequently Asked Questions and Troubleshooting Scenarios for Cisco Unified Service Monitor 2.2

  • Viewing Options

  • PDF (236.1 KB)
  • Feedback
Cisco Unified Service Monitor 2.2 FAQ and Troubleshooting Scenarios

Table Of Contents

Cisco Unified Service Monitor 2.2 FAQ and Troubleshooting Scenarios

Frequently Asked Questions

General

Installation

Upgrade and License

Configuration

General Questions

Cisco 1040 Sensor Management

Unified Communications Manager Credentials

Monitored Phones

Thresholds

Reports

Diagnostic Reports—Sensors

Diagnostic Reports—CVTQ

General

Most Impacted Report

Troubleshooting Scenarios

Obtaining Documentation and Submitting a Service Request


Cisco Unified Service Monitor 2.2 FAQ and Troubleshooting Scenarios


This document includes the following:

Frequently Asked Questions

Troubleshooting Scenarios

Obtaining Documentation and Submitting a Service Request

Frequently Asked Questions

General

Installation

Upgrade and License

Configuration

Unified Communications Manager Credentials

Monitored Phones

Thresholds

Reports

General

What ports does Service Monitor use?

22—SFTP. Service Monitor uses SFTP to obtain data from Unified Communications Manager versions 5.x and later. (TCP)

53—DNS. (UDP)

67 and 68—DHCP. (UDP)

2000—SCCP. Service Monitor uses SCCP to communicate with Cisco 1040s. (TCP)

43459—Database. (TCP)

5666—Syslog. Service Monitor receives syslog messages from Cisco 1040s. (UDP)

5665-5680—Interprocess communication between the user interface and back-end processes. (TCP)

On Unified Communications Manager 4.x publishers:

1433—SQL Server (TCP)

On TFTP servers:

69—Service Monitor uses TFTP to find the configuration file for a given Cisco 1040.

Under what circumstances does Service Monitor send e-mail to an administrator?

After either of the following occurs:

A Service Monitor process restarts

Service Monitor cannot verify credentials after restarting

Service Monitor sends e-mail only if you have configured an SMTP server and a recipient for e-mail. See User Guide for Cisco Unified Service Monitor 2.2.

Can the Service Monitor server be deployed in a Service Provider type of environment?

The Service Monitor server assumes that the following are unique:

IP addresses of devices and Unified Communications Managers

Cluster IDs (in Credential Management).

Can I back up Service Monitor data using Common Services backup procedures?

Only for this very limited set of data:

Files in this folder—C:\PROGRA~1\CSCOpx\qovr\mavericksshd

These 2 configuration files:

C:\PROGRA~1\CSCOpx\qovr\qovrconfig.properties

C:\PROGRA~1\CSCOpx\qovr\qovrExport.properties


Note Common Services backup procedures do not back up the Service Monitor database or any other configuration files apart from the above.


How does Service Monitor handle synthetic calls made by Operations Manager?

Service Monitor drops them. They are not stored in the database nor are traps generated on violation.

I received this e-mail:
Possible causes for a restart are:
* Server process was not responsive.
* AXL communication with at least one Cisco Unified Communication Manager was disrupted.
What should I do now?

The e-mail indicates that a monitoring process restarted the core Service Monitor server. Although the server might now be functional, contact Cisco TAC at the earliest.

I received an e-mail telling me that verification of one or more credentials failed. What should I do now?

If Cisco Unified Provisioning Manager is installed, it could be running a massive sync operation with Unified Communications Manager. Try selecting the cluster from the Data Source Credentials page and clicking Verify. If verification fails, you must wait until the sync completes and re-verify.

Installation

I just installed Service Monitor fresh. Why is the database so big (25 GB on a server standalone and 10 GB on a server with Operations Manager and Service Monitor)?

The database size is pre-allocated to enhance performance. The large database size does not mean that the database is full of information.

I just installed Service Monitor standalone. How long should I wait for the system to be functional?

It can take up to 15 minutes for Service Monitor to complete the pre-allocation of 25 GB of database space. If you access the user interface before the pre-allocation completes, the screens will be very slow and unresponsive and might even display errors. This is normal. Things will work fine after the database has finished pre-allocation. Subsequent restarts of the Service Monitor server will be quick.

Upgrade and License

The License Information page displays a cusm 2.0 license. Do I need a new license to upgrade to 2.2?

No.

How do I upgrade from Service Monitor 2.1 to Service Monitor 2.2?
How do I upgrade from Service Monitor 2.0.1 to Service Monitor 2.2?

For complete instructions, see Installation Guide for Cisco Unified Service Monitor 2.2.

How do I upgrade from Service Monitor 1.1 to Service Monitor 2.2?
How do I upgrade from Service Monitor 1.0 to Service Monitor 2.2?

Uninstall Service Monitor 1.0 or 1.1 before installing Service Monitor 2.2. (Direct upgrade to 2.2 is supported only from Service Monitor 2.0.1 and 2.1.)

After I upgrade to 2.2, the License Information page displays cusm 2.0. Where can I see evidence that I have upgraded to 2.2?

Display the installed version by selecting the About link from the upper-right corner of a Service Monitor window.

When I upgrade, will my report data be preserved?

To preserve your report data, run the Call Migration Tool before you upgrade. Download QOVR_CMT.zip from Cisco.com as follows:

1. Go to this URL: http://www.cisco.com/en/US/partner/products/ps6536/tsd_products_support_series_home.html.

2. If you have not already logged in to Cisco.com, log in.

3. Click the Download Software link.

4. Follow the instructions online to select the correct software product.


Note Read the instructions that are available with the Call Migration Tool to plan your upgrade accordingly.


I ran the Call Migration Tool. Now I don't see the device type for the old data.

Service Monitor 2.2 stores the device type per call, instead of globally against a device name, as in Service Monitor 2.1. Hence, this is a side-effect.

What can I expect if I reinstall Service Monitor 2.2?

The database (in which call data, credentials, and configuration data is stored) and files (sensor configuration files, and—if archiving is enabled—call metrics archive files) are preserved. However, the reinstallation procedure does not run a backup. To back up your data as a precaution, you must do so manually. See Installation Guide for Cisco Unified Service Monitor 2.2.

I installed the latest license, but, when I log in, I get a message such as "License Invalid" or "License not found".

This can happen when the clock on the server was turned back after installing the license. Check whether the license file in NMSROOT\etc\licenses has a timestamp later than the server clock. If so, do this:

1. Set the server clock ahead of when the license file was installed.

2. Restart the daemon manager by entering these commands:

net stop crmdmgtd
net start crmdmgtd

Note NMSROOT is the directory where Service Monitor is installed; its default location is C:\Program Files\CSCOpx.


Configuration

General Questions

Cisco 1040 Sensor Management

General Questions

I know that Cisco Unified Communications Manager must be configured correctly before Service Monitor can communicate with them, but Cisco Unified Communications Manager documentation is so extensive. How can I quickly find out what I need to do?

For brief, thorough instructions, see Unified Communications Manager Configuration in User Guide for Cisco Unified Service Monitor 2.2.

Is the Internet Explorer 8.0 browser supported?

No. Use Internet Explorer 6.0 or Internet Explorer 7.0.

Can I install Service Monitor on a system with two network interface cards (NICs)?

Dual homing—using 2 NICs with 2 different IP addresses—is not supported on Service Monitor. Using 2 NICs with a single IP address (a fail-over configuration, in case one of the NIC cards fails) is supported.

If multiple sensors (NAMs and Cisco 1040s)—report low MOS for the same RTP stream, how many traps does Service Monitor send?

1 trap per endpoint per 10 minutes

Cisco 1040 Sensor Management

How do I register my new Cisco 1040 Sensors with Service Monitor?

See Managing Cisco 1040 Sensors in User Guide for Cisco Unified Service Monitor 2.2.

I deleted a sensor from Service Monitor. Will it automatically register to Service Monitor again?

No. To add this sensor to Service Monitor again, select Configuration > Sensors > Show Deleted > Re-Add.

Is it OK to use the Service Monitor system as a TFTP server for sensors?

Yes. Check Windows Services to confirm that the Common Services TFTP service (CWCS tftp service) is enabled (as it is by default). Ensure that TFTP root is configure outside of the NMSROOT directory structure.

I have a TFTP server but it does not have write access enabled. What should I do?

1. Add the TFTP server to Service Monitor and create a default sensor configuration file:

Configuration > Sensor > TFTP Servers

Configuration > Sensor > Setup—Enter the image filename and primary Service Monitor.

2. Copy these files from NMSROOT\CSCOpx\ImageDir to the TFTP root on the TFTP server:

QOVDefault.cnf—Default configuration file.

SvcMonAB2_102.img—Sensor image file. (For the most up-to-date image filename, see Cisco Unified Service Monitor 2.2 Compatibility Matrix.)

Sensors register with Service Monitor using the default configuration file; Service Monitor then creates a MAC-specific configuration file (MACAddress.cnf) for the sensor also in NMSROOT\CSCOpx\ImageDir.

3. Copy the MAC-specific configuration files from NMSROOT\CSCOpx\ImageDir to the TFTP root on the TFTP server.

How do I use a Linux-based Unified Communications Manager as a TFTP server?

After you copy sensor image and configuration files to the TFTP server, perform this task during off hours:

1. Log into Unified Communications Manager Serviceability.

2. Restart the CM Service Cisco TFTP. For more information, see Cisco Unified Serviceability Administration Guide.

I get traps from Service Monitor every minute for the same endpoint for sensor-reported MOS violations. It's too much. What should I do?

Increase the number of minutes during which Service Monitor does not send traps for an endpoint. Select Configuration > Sensors > Setup and increase the number of minutes in the Send traps every xx minutes field.

What are some things that I need to be aware of when deleting a sensor from Service Monitor?

To delete a sensor, do one of the following:

If the goal is to move the sensor to a different Service Monitor, complete the move before deleting the sensor.

Before you delete the sensor, blank out the IP addresses for the primary and secondary Service Monitors in the MAC-specific and the default configuration files on the TFTP server. You can correct the IP addresses after the sensor has been moved or registered to the new Service Monitor. (This option is easier and preferable to the one that follows.)

Before you delete the sensor, shut the switch port that physically connects to the 10/100-1 Fast Ethernet port on the sensor.

If a sensor has been deleted from a Service Monitor, configuring that sensor to use the Service Monitor as a secondary receiver is not recommended. However, if you must do so:

1. Re-Add the sensor. (Select Configuration > Sensors > Show Deleted > Re-Add.)

2. Configure the sensor to use the Service Monitor as a secondary receiver.

Must I reset 1040s to sync the time for Daylight Saving Time?

It's not necessary. Service Monitor sends hourly time-syncs to 1040s. However, you can reset 1040s to prevent any data loss.

Unified Communications Manager Credentials

Service Monitor lost contact with Unified Communications Manager 5.x (or later). After re-establishing the connection, the Last Contact Status continues to display Discarding Data. What is going on and how can I see current data in CVTQ reports?

Unified Communications Manager 5.x and later resends backlogged data to application billing servers after reconnecting to them. Service Monitor must process this data and discard old data. Depending on the size of the backlog, the processing can take days. To prevent this processing from occurring, from Unified Communications Manager do the following:

For Unified Communications Manager 7.x, uncheck the Resend on Failure check box. (See instructions for adding Service Monitor as an Application Billing Server in User Guide for Cisco Unified Service Monitor 2.2.

For Unified Communications Manager earlier than 7.x, do this:

1. Remove the Service Monitor application billing server; doing so removes the associated list of backlogged files. See Installation Guide for Cisco Unified Service Monitor 2.2.

2. Restart the CDR Repository Manager service.

3. Add Service Monitor to Unified Communications Manager as an application billing server. (For more information, see User Guide for Cisco Unified Service Monitor 2.2.)

4. Restart the CDR Repository Manager service.

What happens if two Cisco Unified Communications Managers have the same cluster ID?

Service Monitor behaves unpredictably; avoid problems by ensuring that cluster IDs are unique. To change a cluster ID:

1. From Cisco Unified Communications Manager Administration:

a. Select System > Enterprise Parameters. The Enterprise Parameters Configuration page appears.

b. Change the cluster ID (to a name that doesn't include a space).

c. Click Update.

2. Repeat this step for each Cisco Unified Communications Manager:

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

b. Select the Cisco Unified Communications Manager server.

c. Click the Restart button.

How can I get the casuser password?

You need to know that casuser password only when Windows authentication is used. See Configuring Windows Authentication on a Unified Communications Manager 4.x System in User Guide for Cisco Unified Service Monitor 2.2.

Monitored Phones

When I total the Known Phone Count for all sensors and Cisco Unified Communications Managers, the sum does not always equal the "Total known phone count". Why is this so?

A Cisco Unified Communications Manager and a sensor might report on the same set of phones.

I made some calls, and I know that the phones are `new' (Service Monitor has not seen them earlier). Why doesn't the phone count go up when I hit Refresh?

As the database grows large (around 5-6GB), there may be up to 60 seconds of lag before the phone count is increased.

What is the purpose of suspending a cluster or sensor?

To refresh the total known phone count, removing phones that are no longer active because:

A cluster was set up for a pilot that has concluded—Suspending the cluster reduces the total known phone count, so that phones from another cluster can be monitored.

Phones were replaced—If the license limit has been reached, suspending and then resuming monitoring of the Cisco Unified Communications Manager to which the phone was registered allows new (replacement) phones to be accepted.

Sensors were relocated to a different switch or geographical location— If the license limit has been reached, suspending and then resuming monitoring of the sensor allows new phones seen by that sensor to be monitored by Service Monitor.

Does suspending a cluster or sensor wipe out report data for the corresponding cluster or sensor?

No. Report-related data is retained until daily purging removes it after:

7 days on a standalone Service Monitor

3 days on a system with both Service Monitor and Operations Manager

Thresholds

Will the system generate traps for bad calls right out of the box without worrying me to create groups?

Yes. Service Monitor generates traps for MOS scores that fall below preset global thresholds that are reasonable industry default values. (Of course, you must configure recipients for the traps).

What are some important reasons for creating groups?

To suppress unnecessary traps from a "known problem" area of the network.

To set different thresholds for the same codec. Executive staff phones could be put in a group with higher than usual threshold values.

To assign different thresholds to lines that span different geographical areas. A G729 call between San Jose and New York could have higher threshold than a G729 call between San Jose and Bangalore.

Reports

Diagnostic Reports—Sensors

Diagnostic Reports—CVTQ

General

Most Impacted Report

Diagnostic Reports—Sensors

I deleted a sensor from Service Monitor. Why can I still select it from the Sensor ID(s) filter?

The sensor remains as a filter until report data from the sensor is purged (after 7 days on a standalone Service Monitor system or after 3 days on a system with both Service Monitor and Operations Manager).

Why don't I see directory numbers in the Cisco 1040 Sensor Reports?

Cisco 1040 Sensors do not report directory numbers. Service Monitor correlates the data sent by sensors with data sent by Unified Communications Managers (CDRs and CMRs) to obtain the directory numbers. For Service Monitor to correlate directory numbers successfully:

The clusters to which the phones are registered must have been added to Service Monitor; (for each cluster, add credentials for the publisher to Service Monitor).

Phone calls must be complete, since CDRs and CMRs are generated at the end of the call.

Why is there sometimes no call record in the Sensor Stream Correlation Report?

Possible reasons:

The call is still going on; hence, Service Monitor has not yet received the CDR.

The Unified Communications Manager to which the endpoints signal has not been added to Service Monitor.

In some (rare) cases, such as IVR Call-Agent situations, the stream IP addresses might not match the IP addresses in the CDR.

Diagnostic Reports—CVTQ

I see Unavailable as the MOS value in some rows. Why?

One of the following:

Call duration was less than 8 seconds (short call).

Endpoint did not report MOS.

Cisco Unified Communications Manager version was earlier than 4.2.

I deleted a Unified Communications Manager from Service Monitor. Why can I still select it from the Cluster ID(s) filter?

The cluster ID remains as a filter until report data from the cluster is purged (after 7 days on a standalone Service Monitor system or after 3 days on a system with both Service Monitor and Operations Manager).

I made a call that lasted three minutes and then ran a CVTQ report. Why is there no data?

It takes 15 minutes before data is available to CVTQ reports.

General

Sensor Reports label endpoints as Listener and Speaker while the CVTQ Reports label them as Caller and Called. Why the discrepancy?

Sensors listen to RTP streams and do not process signaling traffic; therefore, sensors cannot distinguish the caller from the called party. When packets stream into a switch, the far end is the speaker and the near end is the listener and vice-versa. Cisco Unified Communications Manager is a call agent and recognizes Caller and Called endpoints.

Is there any indication if a 1040 goes into "Sampling Mode"?

Not in Service Monitor reports. However, in theory, sampling mode can be indicated in sensor traps in data field A. The value definition is "0=actual & 1=sample". If you can read trap messages directly, you should be able to see the value (like this: ...TT=1,01=001120FFE3AA,A=0,B=33.43.5.34,......). Sampling mode is not usually seen, because, if there is more traffic than a 1040 can handle, the 1040 might freeze and not unfreeze until power is reset.

Why is Device Type sometimes shown as Unavailable when the device is clearly managed by a Unified Communications Manager that is added to Service Monitor?

When Service Monitor processes many new devices, (as it does after initial installation) and must query Unified Communications Manager to obtain device types, Unified Communications Manager sometimes does not respond to the high rate of AXL queries. When this happens, Service Monitor misses the device type. However, the next time that the device appears in a record Service Monitor queries again ; eventually, the AXL query succeeds and Service Monitor obtains the device type.

Most Impacted Report

Why is there no Most Impacted Report?

On the first day of installation, since the information for the report is generated at 1AM the next day, there is no Most Impacted Report.

Most Impacted Reports are based on bad calls; if all calls are good, there is no report.

Can I run the Most Impacted Report automatically?

You can configure Service Monitor to automatically generate the report, save it to a specific location, and send it to one or more e-mail addresses from Configuration > Export Settings.

Troubleshooting Scenarios

Sensor state remains `Waiting...'.

1. Verify that the sensor is registered to the correct Service Monitor server:

If you know the IP address of the sensor, type http://IP. The web interface on the sensor opens and shows the TFTP server name and the Service Monitor server name.

If you do not know the IP address of the sensor, go to the TFTP server and look at the MAC-specific cnf file for the sensor.

2. Perform the following procedure if the sensor is:

Registered to the correct Service Monitor server—To ensure that an old cnf file is not loaded on the sensor.

Not registered to the correct Service Monitor server—To ensure that the current cnf file exists on the Service Monitor server and the TFTP servers, and is loaded on the sensor.

a. From the TFTP server, delete the MAC-specific (QOVMACAddress.cnf) cnf file and the default cnf file, QOVDefault.cnf.

b. Generate and copy the default cnf file over from the current Service Monitor server to the TFTP servers as explained in the FAQ I have a TFTP server but it does not have write access enabled. What should I do?

c. Power cycle the sensor physically.

3. As a last resort, reset the switch.

To verify that Service Monitor is receiving sensor data, look at the  NMSROOT\log\syslog.log file.

Why does Sensor Status say "Old Image"?

The Cisco 1040 image file is not up-to-date. Do the following:

1. On the TFTP servers, delete the SvcMon*.img file, default sensor configuration file, and MAC-specific configuration files.

2. From Service Monitor, update the default configuration file.

3. Copy the default configuration file and most up-to-date Cisco 104 0 image file to the TFTP server.

4. Reset the sensors to load the new image.

I entered all Communications Manager Credentials and the Last Contact Status is Success. I know that calls are happening. Why don't I see CVTQ report data yet?

Wait for 15 minutes after the first call.

Verify that CDR is enabled in Cisco Unified Communications Manager. For Unified Communications Manager configuration tasks that you must perform so that Service Monitor can obtain call data, see User Guide for Cisco Unified Service Monitor 2.2.

Cisco Unified Communications Manager 5.x is pushing data but, for the last few days, there is no report data.

On the Communications Manager Credentials page, click Success in the CDR/CDRM column. If the last contact time is two or more days old, Cisco Unified Communications Manager has stopped contacting Service Monitor. Confirm that Cisco Unified Communications Manager 5.x is still configured as required for Service Monitor. See Cisco Unified Communications Manager Configuration in User Guide for Cisco Unified Service Monitor 2.2.

Look for recent files in the SFTP root: NMSROOT\cscopx\qovr\preserve. If calls are occurring, but there are no files here, then Cisco Unified Communications Manager 5.x is not pushing data.

The global threshold for the G711codec is 4.4. I have two CVTQ groups, one of which overrides the G711 threshold, lowering it to 4. I don't see traps from Cisco Unified Communications Manager phones that I know are generating a MOS value of 3.8.

Check whether the other CVTQ group:

Overrides the G711 threshold, setting it to a value lower than 4

Has a higher priority (therefore taking precedence)

Ideally, you should not configure two groups to override the threshold for the same codec without ensuring that the same endpoints do not exist in both groups.

A sensor that used to be registered is no longer registered (doesn't show up in the Service Monitor UI).

If a sensor was previously:

Deleted—Re-Add it. (Select Configuration > Sensors > Show Deleted > Re-Add.). It is very strongly recommended that you re-add such a sensor before pointing the sensor to the Service Monitor again (as a primary or secondary receiver).

Registered to a Service Monitor 2.1 server—Make sure that the configuration files on the TFTP server in use by that sensor have been updated to match the new Service Monitor.

There is no data in CVTQ report.

1. Make sure that CDR is enabled on all Unified Communications Manager nodes (publisher and subscribers.) To do so:

a. Log into Unified Communications Manager Administration.

b. Select Service Parameter > Call Diagnostic Enabled.

2. For Unified Communications Manager 5.x and later, check the CSCOpx\qovr\preserve directory on Service Monitor server. Both cdr_xxxxx and cmr_xxxxx files should be pushed into this directory by Unified Communications Manager 5.x or later.

3. Wait for 15 minutes to see CVTQ report.

Service Monitor lost contact with Unified Communications Manager 5.x (or later). After re-establishing the connection, the Last Contact Status continues to display Discarding Data. What is going on and how can I see current data in CVTQ reports?

Unified Communications Manager 5.x and later resends backlogged data to application billing servers after reconnecting to them. Service Monitor must process this data and discard old data. Depending on the size of the backlog, the processing can take days. To prevent this processing from occurring, from Unified Communications Manager do the following:

1. Remove the Service Monitor application billing server; (doing so removes the associated list of backlogged files). (For more information, see Installation Start Guide for Cisco Unified Service Monitor 2.2.)

2. Restart the CDRM service.

3. Add Service Monitor to Unified Communications Manager as an application billing server. (For more information, see User Guide for Cisco Unified Service Monitor 2.2.)

4. Restart the CDRM service.

I don't see any data from Unified Communications Manager 5.x or later.

Select Configuration > Credential Management and click the Success status to view more information. If the last contact time is unreasonably old, that means the Unified Communications Manager is not pushing data. If the information indicates Discarding Data, that means the Unified Communications Manager is pushing backlogged data that Service Monitor is rejecting.

Could not add Service Monitor to Unified Communications Manager 5.x or later as a billing server.

1. Make sure that port 22 on Service Monitor is not blocked by a firewall so that Unified Communications Manager can send files to Service Monitor server:

a. Open a DOS prompt on Service Monitor server.

b. Type pdshow SSHD and note the Pid (shown in bold in the following example):

C:\>pdshow SSHD
Process= SSHD
State  = Program started - No mgt msgs received
Pid    = 7772
RC     = 0
Signo  = 0
Start  = 6/12/2007 6:32:17 PM
Stop   = Not applicable
Core   = Not applicable
Info   = Server started by admin request

c. Type netstat -a -b |more as shown in the following example:

netstat -a -b |more
Proto  Local Address          Foreign Address        State           PID
TCP    cusm-perf6:ssh         cusm-perf6:0           LISTENING       7772
[cwjava.exe] 

Port 22 (ssh) should be used by process SSHD (pid 7772 in this case). If port 22(ssh) is used by another ssh daemon process, stop that process and enter these commands:

pdterm SSHD
pdexec SSHD

Look in the SSHD_sterr.log file under \CSCOpx\log\qovr to confirm that SSHD is using port 22:

03-Jul-2007|16:04:54.218|ERROR|SSHD_sterr|main|Jul 3, 2007 4:04:54 PM 
com.maverick.sshd.SshDaemon startup
INFO: Binding server to /0.0.0.0:22
Jul 3, 2007 4:04:54 PM com.maverick.sshd.L run
INFO: Starting permanent ACCEPT thread id=1

2. Add Service Monitor to Unified Communications Manager 5.x or later as a billing server again. If the problem is still not resolved:

a. Open an SSH prompt to the Unified Communications Manager publisher server.

b. Open the known_host file under the /home/tomcat/.ssh directory. If there is an entry for Service Monitor, delete that entry.

3. Add Service Monitor to Unified Communications Manager again.

No new CDRs are added to the Unified Communications Manager CDR table after adding Unified Communications Manager 4.x to Service Monitor.

1. Log in to the system with the Unified Communications Manager publisher.

2. Check the database user account. Especially check the owner of table sm_record_create_table. The owner should be dbo. If the owner is not dbo, follow the steps in Adding Microsoft SQLServer User Accounts topic in online help or User Guide for Cisco Unified Service Monitor 2.2 to create the user for Service Monitor.

3. Delete the sm_record_create_table table.

4. Log in to Service Monitor, delete the cluster from Unified Communications Manager Credentials, and add the Unified Communications Manager credentials to Service Monitor again.

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.