Cisco Support Community
Showing results for 
Search instead for 
Did you mean: 

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. If you'd prefer to explore, try our test area to get started. And see here for current known issues.

New Member

Real Time Monitoring Tool Error


I got the following error messages in RMTM.

Directory replication failed .

Monitored precanned object has value of 0.

Is this message really means an error as there is no sigh of it. There is nothing in the event viewer or in the SQL replication monitor.

Processor load over 90 Percent.

BARS (72 percent) uses most of the CPU.

Is it normal that BARS use so much the CPU?



Re: Real Time Monitoring Tool Error

This Alert triggered for Ex: when your CCM Cluster is not upgraded in the proper order. It shouldnt be much of concern if this Alert is triggered once a day (its my opinion). And Yes BARS need much memory during the Backup, this is why Cisco recommend scheduling BARS during off-peak hours.

Re: Real Time Monitoring Tool Error

CSCsc85141: RTMT generates directory connection and replication alarms


RTMT generates directory replication and connection alerts in a Call Manager cluster when

directory replication appears to be functioning normally.

The following RTMT alerts are seen while the directory service is up and running.

[RTMT-ALERT] DirectoryReplicationFailed

Directory replication failed .

Monitored precanned object has value of 0.

[RTMT-ALERT] DirectoryConnectionFailed

Directory connection failed .

Monitored precanned object has value of 0.


A Call Manager 4.1(3) cluster running RTMT with more than one subscriber will attempt to

test replication status by creating the following object.

"ou=zTestReplStatus--(, ou=CCN,"

All servers will attempt to create and delete the same object, creating a race condition.

RTMT generates alerts regarding the failed replication tests caused by this condition.


This is a cosmetic issue. Directory functionality is not actually broken.

One possible workaround is to disable RTMT alerts for directory replication and connection

errors until an upgrade is available to a version that has been fixed for this issue. This

workaround has the limitation of not being notified when actual directory replication

errors exist.