Cisco Cisco Prime Infrastructure 3.0 White Paper

 

 

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

Page 14 of 83 

Health Monitor on the secondary Cisco Prime Infrastructure server provides status information on both the primary 

and secondary Cisco Prime Infrastructure servers. Failback can be initiated through the secondary HM once the 

primary Cisco Prime Infrastructure server has recovered from the failure condition. The failback process is 

always initiated manually so as to avoid a flapping condition that can sometimes occur when there is a network 

connectivity problem. More details on how to deploy Cisco Prime Infrastructure 2.0 HA can be found at 

. 

Although it may sound trivial to upgrade from Cisco Prime Infrastructure 1.x, there are some instances where we 

still recommend users to continue using version 1.x. Please note that these recommendations are only specific to 

Cisco Prime Infrastructure 2.0, and may change once later versions are out in 2.x train. 

● 

If you have been using Cisco Prime Infrastructure 1.x Small OVA, an inline upgrade to Cisco Prime 

Infrastructure 2.0 is not supported. Recommendation in this case is to migrate instead; that is, back up 1.x 

after applying the relevant patch and then restore onto a freshly installed Cisco Prime Infrastructure 2.0 

Express OVA. You will most likely need to increase CPU/memory based on the new requirement for Cisco 

Prime Infrastructure 2.0 as mentioned in the preceding Server Sizing Matrix. 

Users can upgrade to Cisco Prime Infrastructure 2.1 only from the latest 1.3.x or 2.0 releases. Inline upgrade is 

supported from both of these versions. It is recommended to update existing 1.3 installations with the latest 

available patch on Cisco.com before attempting to upgrade to 2.1. 

Upgrading Cisco Prime Infrastructure from 1.4.x to 2.1 is NOT officially supported, but it may be possible to 

manually export the maps if desired. This implies that inline upgrade or migration using backup/restore techniques 

may not work, and are not tested. 

If you are currently running Cisco Prime Infrastructure 1.4.x and would like to move to 2.1, then you do have an 

option to copy site-maps independently. Other data from database cannot be migrated as with other previous 

versions. 

Follow the procedure below to import the maps into Cisco Prime Infrastructure 2.1 server: 

1.  Log in to the web GUI of Cisco Prime Infrastructure 1.4.x. 

2.  Navigate to Monitor > Site Maps (in the Classic View) and select the sites/buildings/floors that you would like 

to import into the Cisco Prime Infrastructure 2.1 server. 

3.  On the top right corner, select the Export Maps option in the drop-down list, and save this newly created 

maps tar.gz data file. 

4. 

Ensure that the controllers are already managed in Cisco Prime Infrastructure 2.1’s inventory. 

5.  On the Cisco Prime Infrastructure 2.1 server, browse to Monitor Site Maps and choose the Import Maps 

option in the drop-down list at the top right corner of the page and follow the next set of steps. 

 Tip: There is no Export Devices option in Cisco Prime Infrastructure 1.4, so theonly way to export device 

inventory out of Cisco Prime Infrastructure 1.4 is through the use of APIs.