Cisco has released Prime Infrastructure 2.2 today, a version long awaited by many of us. ISE 1.3, IOS-XE3.7, AeroOS-8.0 is supported in this PI2.2 version. Here is the release notes of this version & you need to go through it for greater details.
So what is the upgrade procedure for PI 2.2 ? You would think you can upgrade existing version to this like any other upgrade. You are wrong in this case 😯 . Here is what PI2.2 Quick Start Guide says about it.
“This version of Prime Infrastructure does not offer an in-place upgrade. To upgrade to the latest version, you must instead install this version of Prime Infrastructure as a virtual appliance on a fresh server, or order it pre-installed on a fresh hardware appliance. You can then migrate your data from your old Prime Infrastructure installation to the new one, using an application backup from the previous installation.
If you are currently using one of the following versions of Prime Infrastructure, you can back up your existing data and then restore that data to a different server running Prime Infrastructure 2.2:
- Cisco Prime Infrastructure 2.1.2 (with the UBF patch)
- Cisco Prime Infrastructure 2.1.1 (with the UBF patch)
- Cisco Prime Infrastructure 188.8.131.52.87
- Cisco Prime Infrastructure 1.4.2
- Cisco Prime Infrastructure 1.4.1
- Cisco Prime Infrastructure 184.108.40.206
If you are using a version earlier than 220.127.116.11 or 18.104.22.168.87, you will need to upgrade your server to version 22.214.171.124.87 (or version 126.96.36.199) before taking the backup.”
So in this post we will see what it involved to go to PI2.2 from a previous release. In my case, I am running PI 188.8.131.52.87 where I can directly take backup & restore of a PI 2.2 server.
First of all you need to build your PI2.2 server using .ova files available on CCO page(Downloads Home-> Products-> Cloud and Systems Management-> Routing and Switching Management-> Network Management Solutions-> Prime Infrastructure-> Prime Infrastructure 2.2-> Prime Infrastructure Software-2.2).
Since I am using VM, I have used PI-VA-184.108.40.206.158.ova to build the VM. Depend on the scale of your network, you need to size the VM accordingly. Below shown the minimum server requirement & supported scale for each type of installation.
I have used remote-backup option where I can backup existing config onto a remote FTP server. You can configure a remote FTP repository as shown below. I have given a name called “ftpserver” & specify its IP address & username password.
prime2/admin(config)# repository ftpserver prime2/admin(config-Repository)# url ftp://x.x.y.214 prime2/admin(config-Repository)# user <username> password plain <ftp_password> prime2/admin(config-Repository)# exit
You can verify the remote ftp server using below command where it should listed all files available in that FTP server
prime2/admin# show repository ftpserver 10_14_7_247_140918_0230.cfg .
Then you can backup your Prime Application configuration onto that FTP server as shown below. Note that depend on the database size, time taken for the backup may vary. In my case it took around 50min to complete this backup process.
prime2/admin# backup PI-Backup ? repository Repository to store backup in prime2/admin# backup PI-Backup repository ? <WORD> Repository name (Max Size - 80) prime2/admin# backup PI-Backup repository ftpserver ? application Application-only backup, excludes OS system data <cr> Carriage return. prime2/admin# backup PI-Backup repository ftpserver application ? <WORD> Application name to be backed up (Max Size - 255) prime2/admin# backup PI-Backup repository ftpserver application NCS % Creating backup with timestamped filename: PI-Backup-141218-1452.tar.gpg Backup Started at : 12/18/14 14:52:29 Stage 1 of 7: Database backup ... Database size: 96G -- completed at 12/18/14 15:13:42 Stage 2 of 7: Database copy ... -- completed at 12/18/14 15:13:42 Stage 3 of 7: Backing up support files ... -- completed at 12/18/14 15:14:57 Stage 4 of 7: Compressing Backup ... -- completed at 12/18/14 15:15:26 Stage 5 of 7: Building backup file ... -- completed at 12/18/14 15:31:29 Stage 6 of 7: Encrypting backup file ... -- completed at 12/18/14 15:37:42 Stage 7 of 7: Transferring backup file ... -- completed at 12/18/14 15:40:29 Total Backup duration is: 0h:48m:0s
Note that I have shutdown the old VM & use same hostnames , IP for the new VM. Once new VM built,You can define a remote FTP repository specifying the same FTP server where config backed up.
prime2/admin(config)#repository ftpserver prime2/admin(config-Repository)# url ftp://x.x.y.214 prime2/admin(config-Repository)# user <username> password plain <ftp_password> prime2/admin(config-Repository)# exit prime2/admin# show repository ftpserver 10_14_7_247_140918_0230.cfg
Then you can restore the backed up configuration as shown below. Note that there are some important notes displayed where you have to pay attention. You have to be patient & it will take around 1.5 hours (again depend on your PI database size)
prime2/admin#restore PI-Backup-141218-1452.tar.gpg repository ftpserver application NCS * NOTE * If the system console is disconnected or got cleared on session timeout run 'show restore log' to see the output of the last restore session. Restore will restart the application services. Continue? (yes/no) [yes] ? yes DO NOT press ^C while the restoration is in progress Aborting restore with a ^C may leave the system in a unrecoverable state Initiating restore. Please wait... Restore Started at 12/18/14 16:22:42 Stage 1 of 9: Transferring backup file ... -- completed at 12/18/14 16:24:48 Stage 2 of 9: Decrypting backup file ... -- completed at 12/18/14 16:32:13 Stage 3 of 9: Unpacking backup file ... -- completed at 12/18/14 16:32:15 Stopping strongSwan IPsec... Stage 4 of 9: Decompressing backup ... -- completed at 12/18/14 16:42:23 Stage 5 of 9: Restoring Support Files ... -- completed at 12/18/14 16:42:27 Stage 6 of 9: Restoring Database Files ... -- completed at 12/18/14 16:42:45 Stage 7 of 9: Recovering Database ... -- completed at 12/18/14 17:04:49 Stage 8 of 9: Updating Database Schema ... Stage 1 of 5: Pre Migration Schema Upgrade ... -- completed at: 2014-12-18 17:24:06.287, Time Taken : 0 hr, 15 min, 21 sec Stage 2 of 5: Schema Upgrade ... : This could take long time based on the existing data size. -- completed at: 2014-12-18 17:34:56.075, Time Taken : 0 hr, 10 min, 49 sec Stage 3 of 5: Post Migration Schema Upgrade ... -- completed at: 2014-12-18 17:44:13.068, Time Taken : 0 hr, 9 min, 16 sec Stage 4 of 5: Enabling DB Constraints ... -- completed at: 2014-12-18 17:44:39.7, Time Taken : 0 hr, 0 min, 22 sec Stage 5 of 5: Finishing Up ... -- completed at: 2014-12-18 17:44:52.668, Time Taken : 0 hr, 0 min, 12 sec -- completed at 12/18/14 17:45:18 Stage 9 of 9: Re-enabling Database Settings ... -- completed at 12/18/14 17:45:18 Total Restore duration is: 01h:22m:36s INFO: Restore completed successfully. Starting PI Server... This may take some time Passwd reset alread in progress Starting Prime Infrastructure... This may take a while (10 minutes or more) ... Prime Infrastructure started successfully. Starting strongSwan 5.0.1 IPsec [starter]... prime2/admin# show application status NCS Health Monitor Server is running. Matlab Server Instance 1 is running Ftp Server is running Database server is running Matlab Server is running Tftp Server is running NMS Server is running. Matlab Server Instance 2 is running Plug and Play Gateway is running. SAM Daemon is running ... DA Daemon is running ...
If everything went well you should be able to log onto your PI2.2 & enjoy the features of new version 🙂 .