Cisco Cisco Prime Unified Service Monitor 9.0 Weißbuch
White Paper
© 2007 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information.
Page 22 of 26
Data purge need not run continuously for 4 hours. You can configure more than one data purge
period as long as:
period as long as:
●
The total time adds up to 4 hours
●
Data purging occurs during low-volume schedule
●
No data purging occurs from midnight through 2 a.m.
Here are some examples:
datapurge-Mon=2-5;22-23;
datapurge-Tue=2-3;4-6;23-24
Note: Do not edit the properties files using Wordpad as it introduces a carriage return. Use
Notepad to edit the file instead.
Notepad to edit the file instead.
The data retention period determines the number of days that data is retained in the Service
Monitor database before being purged. The default value depends on the deployment scenario:
Monitor database before being purged. The default value depends on the deployment scenario:
●
Service Monitor alone on a server: 7 days
●
Any coresident server: 3 days.
Troubleshooting
This section provides a few troubleshooting tips.
Q.
A.
I don’t see any service quality alerts in the Operations Manager dashboard. What could
be the problem?
Before debugging this problem, do the following:
Before debugging this problem, do the following:
●
Go to the Service Monitor application and verify that the probes are registered and visible in
the Service Monitor GUI.
the Service Monitor GUI.
●
Go to the Service Monitor setup page and verify that Operations Manager is entered as a
trap recipient, even if Service Monitor is on the same machine.
trap recipient, even if Service Monitor is on the same machine.
●
In Operations Manager, go to Administration > Service Quality and add Service
●
Monitor, even if it is on the same machine.
●
If all of the previous are correct, then only calls that fall below the Service Monitor threshold
will be shown in the Alerts and Activities page.
will be shown in the Alerts and Activities page.
◦
When all of the previous have been done, debug the problem by doing the following:
●
Check syslog.log under:
◦
NMSROOT\CSCOpx\syslog.log in IPCOM 1.0
◦
NMSROOT\CSCOpx\log\qovr\syslog.log in CUOM 1.X/ CUSM 2.X
Check if you see recent syslogs. Check the D=<value>. This is the MOS score multiplied by a
factor of 10. Check to see whether this value is below the threshold multiplied by 10.
factor of 10. Check to see whether this value is below the threshold multiplied by 10.
●
If this is true, check NMSROOT\log\qovr\trapgen.log. This file should contain the traps that
are being generated by the system. If traps are available in this file, then it means that the
Service Monitor portion is functional and ready. If not, then check for exceptions in
probemanager.log and datahandler.log.
are being generated by the system. If traps are available in this file, then it means that the
Service Monitor portion is functional and ready. If not, then check for exceptions in
probemanager.log and datahandler.log.