Cisco Cisco Prime Infrastructure 3.0 Weißbuch

 

 

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

Page 12 of 83 

The Cisco Prime Infrastructure High Availability (HA) implementation allows one primary Cisco Prime Infrastructure 

server to failover to one secondary (backup) Cisco Prime Infrastructure server. A second server is required that 

has sufficient resources (CPU, hard drive, network connection) in order to take over Cisco Prime Infrastructure 

operation in the event that the primary Cisco Prime Infrastructure system fails. In Cisco Prime Infrastructure, the 

only HA configuration is supported is 1:1 - 1 primary system, 1 secondary system. 

The size of the secondary server must be larger than or equal to that of the primary server; for example, if the 

primary Cisco Prime Infrastructure server is the medium OVA, then the secondary Cisco Prime Infrastructure 

server must be the medium or large OVA. 

The primary and secondary server can be a mix of a physical and a virtual appliance. For example, if the primary 

Cisco Prime Infrastructure server is a physical appliance, the secondary server can be either a physical appliance 

or a large OVA virtual appliance; for example, the server configuration and sizing of large OVA is the same as the 

physical appliance. Customers must be running the same version of Cisco Prime Infrastructure on both the primary 

and secondary Cisco Prime Infrastructure servers. The Cisco Prime Infrastructure HA feature is transparent to the 

wireless controller, that is, there is no software version requirement for the Cisco Wireless LAN Controller (WLC), 

access points (APs), and the Cisco Mobility Services Engine (MSE). 

An RTU (right-to-use) license is required to deploy Cisco Prime Infrastructure in an HA implementation. Apart from 

this, only one Cisco Prime Infrastructure server license needs to be purchased. There is no need to purchase a 

license for the secondary Cisco Prime Infrastructure server. The secondary server will use the license from the 

primary when a failover occurs. The secondary node will simulate the UDI information of the primary; thus the 

secondary server will be able to use the synchronized license from the primary server when the secondary server 

is active. The same Cisco Prime Infrastructure license file resides on both the primary and secondary Cisco Prime 

Infrastructure servers. Since the Cisco Prime Infrastructure Java Virtual Machine (JVM) is only running on the 

primary or secondary (not both), the license file is only active on one system at a given point in time. 

Cisco Prime Infrastructure HA can also be deployed with geographic separation of the primary and secondary 

servers. This type of deployment is also known as disaster recovery or geographic redundancy. 

There are two HA mo

des: failover and failback. Let’s take a look at each of them in detail. 

After initial deployment of Cisco Prime Infrastructure, the entire configuration of the primary Cisco Prime 

Infrastructure server is replicated to the host of the secondary Cisco Prime Infrastructure server. During normal 

operation (that is, when the primary Cisco Prime Infrastructure server is operational), the database from the 

primary server is replicated to the secondary Cisco Prime Infrastructure server. In addition to the database 

replication, application data files are also replicated to the secondary Cisco Prime Infrastructure server. Replication 

frequency is 11 seconds (for real-time files) and 500 seconds (for batch files).