Cisco Cisco Unified Operations Manager 8.0 White Paper

Page of 112
All contents are Copyright © 1992–2006 Cisco Systems, Inc.   All rights reserved. 
Page 62 of 112 
 
Essentially this creates a baseline for the Standby server. The Standby server would 
have the complete device list and all the configurations that are identical to the 
Active.  
 
 
This also means that Standby would poll the network in exactly the same way as the 
Active server. If you want to reduce the impact of polling on network bandwidth,  
 
1. Increase the polling interval to a very large value (1 hour) to reduce impact on 
network bandwidth. You can do this by going to Administration > Polling 
Parameters,
 select each group and editing the polling interval values. 
3. Go to Notifications > Notification Criteria. Select all notification criteria and 
Select “Suspend” 
4. Go to Diagnostics > Synthetic Tests. For each test select the “Stop” button. This 
will stop the Synthetic tests. 
5. Go to Diagnostics > Phone Status Tests. You will see a list of configured tests. 
For each test, click on “Edit” and make the schedule to run between “00:00” to 
“00:00”. This essentially stops the test.   
 
6. Suspend monitoring of SRST routers used in SRST tests: Go to Administration > 
SRST Poll Settings > SRST Operations
. You will see a list of SRST tests 
configured. Note down all the target routers. Go to Devices > Device Management.  
You will see the overview of all managed devices. Click on “Monitored Devices”.  
Click on the SRST router IP address in this report, Detailed Device View is launched. 
In this UI, suspend the device. This will automatically stop the SRST tests. 
 
7.3.4  Continuous data sync up  
 
Once the Active and Standby are in operation, any changes thereon to the Active 
server need to be propagated to the Standby. Different kinds of data that can change 
and recommendation for replication are listed below  
7.3.4.1 
Device List 
 
Changes to the device list can be propagated by using a central DCR. There are two 
possibilities 
 
a) Central LMS server as the source of device list for both Primary and Backup. In 
this case, LMS server acts as a Master repository of devices which pushes any 
additions or deletions to the device list to the two slaves – Active and the Standby 
server.