Cisco Cisco Prime Infrastructure 3.0 White Paper

 

 

© 2015 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public Information. 

Page 13 of 83 

When the issues on the server which host the primary Cisco Prime Infrastructure server have been resolved, 

failback can be manually initiated. Once this is done, the screen is displayed on the secondary Cisco Prime 

Infrastructure server. When you initiate failback, the Cisco Prime Infrastructure database on the secondary Cisco 

Prime Infrastructure server and any other files that have changed since the secondary Cisco Prime Infrastructure 

server took over Cisco Prime Infrastructure operation are synchronized between the secondary and the primary 

Cisco Prime Infrastructure servers. Once database synchronization has been completed, the primary Cisco Prime 

Infrastructure JVM is started by the primary Health Monitor (HM). When the primary Cisco Prime Infrastructure JVM 

is running, the preceeding screen is displayed on the secondary HM. 

 

Automatic failover is a much simpler process. The configuration steps are the same except that automatic failover 

is selected. Once automatic failover is configured, the network administrator does not need to interact with the 

secondary HM in order for the failover operation to take place. Only during failback is human intervention required. 

In this example, the secondary Cisco Prime Infrastructure server was configured with manual failover. For 

example, the network administrator is notified through email that the primary Cisco Prime Infrastructure server has 

experienced a down condition. The Health Monitor on the secondary Cisco Prime Infrastructure server detects the 

failure condition of the primary Cisco Prime Infrastructure server. Because manual failover has been configured, 

the network administrator needs to manually trigger the secondary Cisco Prime Infrastructure server to take over 

Cisco Prime Infrastructure functionality from the primary Cisco Prime Infrastructure server. This is done if you log in 

to the secondary HM. Even though the secondary Cisco Prime Infrastructure server is not running, you can 

connect to the secondary HM using the following syntax: 

https://<Secondary_PI_IP_Address>:8082/ 

The secondary HM displays messages in regard to events that are seen. Because manual failover has been 

configured, the secondary HM waits for the system administrator to invoke the failover process. Once manual 

failover has been chosen, the message is displayed as the secondary Cisco Prime Infrastructure server starts. 

Once the failover process has been completed, which means that the Cisco Prime Infrastructure database 

replication process is completed and the secondary Cisco Prime Infrastructure JVM process has started, then the 

secondary Cisco Prime Infrastructure server is the active Cisco Prime Infrastructure server.