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 21 of 26
In Service Monitor standalone servers, it is recommended to use the Common Services backup
and restore process only when the database is less than 6 GB. For large Service Monitor
databases, it is recommend to do backup manually (saving database password and copy database
files) as documented in the user guide.
and restore process only when the database is less than 6 GB. For large Service Monitor
databases, it is recommend to do backup manually (saving database password and copy database
files) as documented in the user guide.
Configuring Low-Volume Schedule and Database Purging
Service Monitor needs 8 hours of low-volume time during a day. During a low-volume schedule,
Service Monitor handles roughly 20 percent of the number records that are processed during a
peak period and performs database maintenance. For sensor data, during regular call volume the
maximum segment rate allowed is 1500 per minute. Anything over this rate will be discarded.
During low call volume, the maximum segment rate allowed is 25 percent of the maximum regular
call volume. Throttling of sensor data is based on the total amount of data received in any 5-minute
interval; it is not per minute. This allows accommodation of temporary spikes in traffic while
blocking continuous high-rate traffic that is over the supported limit. There is no throttling of Cisco
Voice Transmission Quality data. Service Monitor standalone server has been tested to support a
maximum rate of 500 Cisco Voice Transmission Quality calls per minute.
Service Monitor handles roughly 20 percent of the number records that are processed during a
peak period and performs database maintenance. For sensor data, during regular call volume the
maximum segment rate allowed is 1500 per minute. Anything over this rate will be discarded.
During low call volume, the maximum segment rate allowed is 25 percent of the maximum regular
call volume. Throttling of sensor data is based on the total amount of data received in any 5-minute
interval; it is not per minute. This allows accommodation of temporary spikes in traffic while
blocking continuous high-rate traffic that is over the supported limit. There is no throttling of Cisco
Voice Transmission Quality data. Service Monitor standalone server has been tested to support a
maximum rate of 500 Cisco Voice Transmission Quality calls per minute.
The default low-volume schedule is 10 p.m. through 6 a.m. To change the schedule, on the Service
Monitor server, change the values of these properties in the NMSROOT\qovr\qovrconfig.properties file:
Monitor server, change the values of these properties in the NMSROOT\qovr\qovrconfig.properties file:
lowcallvolume-Mon=0-6,22-24
lowcallvolume-Tue=0-6,22-24
lowcallvolume-Wed=0-6,22-24
lowcallvolume-Thu=0-6,22-24
lowcallvolume-Fri=0-6,22-24
lowcallvolume-Sat=0-20,22-24
lowcallvolume-Sun=0-20,22-24
You can configure more than one low-volume period as long as the total time adds up to 8 hours
and it covers midnight to 1 a.m. Here are some examples:
and it covers midnight to 1 a.m. Here are some examples:
lowcallvolume-Mon=1-7,21-23
lowcallvolume-Tue=0-6,21-22,23-24
To put changes into effect after you edit qovrconfig.properties, you must stop and start the QOVR
process. While logged on to the server where Service Monitor is installed, from the command line,
enter these commands:
process. While logged on to the server where Service Monitor is installed, from the command line,
enter these commands:
pdterm QOVR
pdexec QOVR
Service Monitor needs 4 hours data purge time. Data purging must occur during the low-volume
schedule and must not run from midnight to 2 a.m. The default schedule is 2 a.m. to 6 a.m. To
change the schedule on the Service Monitor server, change the values of these properties in the
NMSROOT\qovr\qovrconfig.properties file:
schedule and must not run from midnight to 2 a.m. The default schedule is 2 a.m. to 6 a.m. To
change the schedule on the Service Monitor server, change the values of these properties in the
NMSROOT\qovr\qovrconfig.properties file:
datapurge-Mon=2-6;
datapurge-Tue=2-6;
datapurge-Wed=2-6;
datapurge-Thu=2-6;
datapurge-Fri=2-6;
datapurge-Sat=2-6;
datapurge-Sun=2-6;