Cisco Prime upgrade from 1.2.1.12 to 3.0 Step by Step.
This document could help someone looking to upgrade Cisco Prime from 1.2.1.12 to 3.0
To Start with :
I have created a VM level backup before starting the upgrade process. If you have any backup system please use that or you could download the VM’s vmdk,vmx and other files .
Make sure you shut down the VM and umount all mounted DVD/CD/Floppy drive.
Also write down your Licensed VUDI, Product ID, Serial number in case you need to do rehost.
Files needed:
PI_1_2_1_12-Update.1.0.tar.gz
PI-Upgrade-2.0.0.0.294-2.tar.gz
PI-Upgrade-2.1.0.0.87.tar.gz
PI-VA-2.2.0.0.158.ova
PI-Upgrade-3.0.0.0.78.tar.gz.zip
Please download those files and verify MD5 hash "ref https://supportforums.cisco.com/document/30321/verifying-ios-images"
All upgrade process must be done through console. And you need lots of coffee or Tea time.
Make sure your session does not timed out
# terminal sessin-timeout 0
And after every upgrade you need to Resync your WCL Configuration before going to next update or upgrade.
Resync WLC configurations
Choose Configuration > Network > ; Network Devices, then select Device Type > ; Wireless Controller.
Select the check box(es) of the applicable controller(s).
Click Sync.
Click Yes to proceed.
Throughout the upgrade process you need to make number of backup and restore.
I used an external FTP server to do that.
Below is the CLI example how to create a repository and do backup of your current Application.
Example FTP server IP: 1.2.3.4
Login to PI using admin account.
Create a repository: [ You need to do this in every fresh VM]
Conf t
(config)# repository FTPupgrade
(config-Repository)# url ftp://1.2.3.4/prime
(config-Repository)# user XXX password plain XXXXXXXX
(config-Repository)# exit
# show repository FTPupgrade
It will show you all existing files at ftp server’s Prime folder
Do a backup to external FTP [ Repository]:
# backup PI-backup_the_name_you_like repository FTPupgrade application NCS
% Creating backup with timestamped filename XXXXX
NCS is the name of the application you need to backup
It could take long time. My one took around 40 minutes. So DO NOT press ^c or restart the VM
To restore the backup
#restore PI-backup_the_name_you_likexxx.tar.gpg repository FTPupgrade application NCS
================ Main upgrade process=============
Step 1: Add patch to PI: 1.2.1.12. File name: “PI_1_2_1_12-Update.1.0.tar.gz”
a. Download the files from “https://software.cisco.com/download/release.html?mdfid=284396249&softwareid=284272933&release=1.2.1 “ Copy the file to your FTP server’s prime folder
b. #show repository FTPupgrade
c. #show application status NCS ß Verify the NCS is running
d. Backup your current NCS application . I preferred backup in every steps but it’s up to you e. #patch install PI_1_2_1_12-Update.1.0.tar.gz FTPupgrade
f. Now wait:D
g. # show version
h. Check the application status: “#show application ncs” or “#ncs status”
Step 4: Upgrade PI to 2.2 file needed “PI-VA-2.2.0.0.158.ova”
According to Cisco Documents:
http://www.cisco.com/c/en/us/td/docs/net_mgmt/prime/infrastructure/2-2/quickstart/guide/cpi_qsg.html#pgfId-113783
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 physical 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 2.1.0.0.87 < we are moving on from that version
Cisco Prime Infrastructure 1.4.2
Cisco Prime Infrastructure 1.4.1
Cisco Prime Infrastructure 1.4.0.45
a. Create a new VM from ova. It is pretty simple just follow the wizard.
b. Start the VM and when you got prompt type setup
c. Answer all the questions.
a. In my scenario. I used same IP and Host name of my current PI.
d. Say Yes or NO depends on your HA system
e. System will restart and it will take looooong time to start again. It says 10 minutes or more but my one took around 90 minutes.
After PI start successfully
At this stage, please shutdown your PI and make a VM clone and forget about that clone. We will use that clone again while we upgrade 2.2 to 3.0
f. Login as admin:
g. # show repository verify your backup files are there.
a. #restore PI-backup_2.1XXXX.tar.gpg repository FTPupgrade application NCS
b. This will reboot your system and after loooong time it will come back.
c. Verify the application “#ncs status”
d. #backup PI-backup_2.2 repository FTPupgrade application NCS
e. # show repo FTPupgrade
i. Verify the backup
f. #halt
g. Shutdown the VM
Step 5: Upgrade PI to 3.0 file needed PI-Upgrade-3.0.0.0.78.tar.gz.zip
According to Cisco
http://www.cisco.com/c/en/us/td/docs/net_mgmt/prime/infrastructure/3-0/quickstart/guide/cpi_qsg.html#19365
“If you are upgrading from a Prime Infrastructure 2.2.x virtual machine, you should create a new virtual machine with the same deployment configuration option you used previously (for example, Express, Express-Plus, Standard, or Professional), back up your existing virtual machine, and then restore it on the new virtual machine. Perform an inline upgrade from Prime Infrastructure 2.2.x, then delete the old virtual machine after the upgraded virtual machine is fully operational’
A. Unzip the downloaded PI-Upgrade-3.0.0.0.78.tar.gz.zip file . Why they zipped that!
B. Start the clone VM (2.2 fresh).
C. Login as admin
D. #show repo FTPupgrade
E. Verify the files you have at FTP server
F. #application upgrade PI-Upgrade-3.0.0.0.78.tar.gz FTPupgrade
g. Go for a run again.
h. After restart, Login as admin.
i. # ncs status verify the NCS is running.
j. # show repo FTPupgrade verify your backup files are there.
k. #restore PI-backup_2.2XXXX.tar.gpg repository FTPupgrade application NCS
It should be end of from 1.2.1.12 to 3.0
Thanks to:
http://justdowifi.blogspot.com.au/2013/11/upgrading-cisco-prime-12-to-30.html
https://mrncciew.com/2014/01/12/upgrade-prime-using-cli/
http://www.rabbibob.com/index.php/Upgrading_Prime_Infrastructure
And all other People, who posted their experience on Cisco support and various website.
To Start with :
I have created a VM level backup before starting the upgrade process. If you have any backup system please use that or you could download the VM’s vmdk,vmx and other files .
Make sure you shut down the VM and umount all mounted DVD/CD/Floppy drive.
Also write down your Licensed VUDI, Product ID, Serial number in case you need to do rehost.
Files needed:
PI_1_2_1_12-Update.1.0.tar.gz
PI-Upgrade-2.0.0.0.294-2.tar.gz
PI-Upgrade-2.1.0.0.87.tar.gz
PI-VA-2.2.0.0.158.ova
PI-Upgrade-3.0.0.0.78.tar.gz.zip
Please download those files and verify MD5 hash "ref https://supportforums.cisco.com/document/30321/verifying-ios-images"
All upgrade process must be done through console. And you need lots of coffee or Tea time.
Make sure your session does not timed out
# terminal sessin-timeout 0
And after every upgrade you need to Resync your WCL Configuration before going to next update or upgrade.
Resync WLC configurations
Choose Configuration > Network > ; Network Devices, then select Device Type > ; Wireless Controller.
Select the check box(es) of the applicable controller(s).
Click Sync.
Click Yes to proceed.
Throughout the upgrade process you need to make number of backup and restore.
I used an external FTP server to do that.
Below is the CLI example how to create a repository and do backup of your current Application.
Example FTP server IP: 1.2.3.4
Login to PI using admin account.
Create a repository: [ You need to do this in every fresh VM]
Conf t
(config)# repository FTPupgrade
(config-Repository)# url ftp://1.2.3.4/prime
(config-Repository)# user XXX password plain XXXXXXXX
(config-Repository)# exit
# show repository FTPupgrade
It will show you all existing files at ftp server’s Prime folder
Do a backup to external FTP [ Repository]:
# backup PI-backup_the_name_you_like repository FTPupgrade application NCS
% Creating backup with timestamped filename XXXXX
NCS is the name of the application you need to backup
It could take long time. My one took around 40 minutes. So DO NOT press ^c or restart the VM
To restore the backup
#restore PI-backup_the_name_you_likexxx.tar.gpg repository FTPupgrade application NCS
================ Main upgrade process=============
Step 1: Add patch to PI: 1.2.1.12. File name: “PI_1_2_1_12-Update.1.0.tar.gz”
a. Download the files from “https://software.cisco.com/download/release.html?mdfid=284396249&softwareid=284272933&release=1.2.1 “ Copy the file to your FTP server’s prime folder
b. #show repository FTPupgrade
c. #show application status NCS ß Verify the NCS is running
d. Backup your current NCS application . I preferred backup in every steps but it’s up to you e. #patch install PI_1_2_1_12-Update.1.0.tar.gz FTPupgrade
f. Now wait:D
g. # show version
h. Check the application status: “#show application ncs” or “#ncs status”
Step 2:
Upgrade PI to 2.0 file needed “PI-Upgrade-2.0.0.0.294-2.tar.gz”
a. Download the file from "https://software.cisco.com/download/release.html?mdfid=284422771&softwareid=284272932&release=2.0.0 " Copy the file to your FTP server’s prime folder
b.Shutdown your VM.
c. Increase your VM RAM to 12GB and add a 2nd HDD of 200GB.
You need 12GB Memory and 200GB free space into your /opt folder.
Check your current folder size.
administration > Appliance > ; Appliance Status:
look for /dev/mapper/smosvg-optvol.
If it is less than 200 GB, please add 2nd HDD to your VM. Cisco prime add 60% of added new HDD Space to /opt folder, so please calculate
d. After adding memory and 2nd HDD, Start the VM and go for a coffee. It will take long time to start the VM. do not shutdown the VM it will break your Prime [ My one DID , as I waited 1 hour and restart).
e.#show repository FTPupgrade < Verify the files is in your FTP server
f. Backup your current NCS application
g.#ncs stop
h # application upgrade PI-Upgrade-2.0.0.0.294-2.tar.gz FTPupgrade
i. Now go for your first Marathon, it could take time between 2 hours to 20 hours or more.
And it will restart your system.
j. After reboot VM takes another 1 hour or so to start . Do not restart, it will come up.
k. After login please check by “#ncs status”
Step 3: Upgrade PI to 2.1 file needed “PI-Upgrade-2.1.0.0.87.tar.gz”
a. Download the file from https://software.cisco.com/download/release.html?mdfid=284540974&softwareid=284272932&release=2.1
a. Download the file from "https://software.cisco.com/download/release.html?mdfid=284422771&softwareid=284272932&release=2.0.0 " Copy the file to your FTP server’s prime folder
b.Shutdown your VM.
c. Increase your VM RAM to 12GB and add a 2nd HDD of 200GB.
You need 12GB Memory and 200GB free space into your /opt folder.
Check your current folder size.
administration > Appliance > ; Appliance Status:
look for /dev/mapper/smosvg-optvol.
If it is less than 200 GB, please add 2nd HDD to your VM. Cisco prime add 60% of added new HDD Space to /opt folder, so please calculate
d. After adding memory and 2nd HDD, Start the VM and go for a coffee. It will take long time to start the VM. do not shutdown the VM it will break your Prime [ My one DID , as I waited 1 hour and restart).
e.#show repository FTPupgrade < Verify the files is in your FTP server
f. Backup your current NCS application
g.#ncs stop
h # application upgrade PI-Upgrade-2.0.0.0.294-2.tar.gz FTPupgrade
i. Now go for your first Marathon, it could take time between 2 hours to 20 hours or more.
And it will restart your system.
j. After reboot VM takes another 1 hour or so to start . Do not restart, it will come up.
k. After login please check by “#ncs status”
Step 3: Upgrade PI to 2.1 file needed “PI-Upgrade-2.1.0.0.87.tar.gz”
a. Download the file from https://software.cisco.com/download/release.html?mdfid=284540974&softwareid=284272932&release=2.1
b. Copy the file to your FTP server’s prime folder
c. #show repository FTPupgrade Verify the files is in your FTP server
d. #ncs stop
e. #application upgrade PI-Upgrade-2.1.0.0.87.tar.gz FTPupgrade
f. Go for a run or sleep.
g. After VM back please check “#ncs status”
h. #backup PI-backup_2.1 repository FTPupgrade application NCS
i. We will use this backup later to restore for PI-2.2
j. #halt
Step 4: Upgrade PI to 2.2 file needed “PI-VA-2.2.0.0.158.ova”
According to Cisco Documents:
http://www.cisco.com/c/en/us/td/docs/net_mgmt/prime/infrastructure/2-2/quickstart/guide/cpi_qsg.html#pgfId-113783
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 physical 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 2.1.0.0.87 < we are moving on from that version
Cisco Prime Infrastructure 1.4.2
Cisco Prime Infrastructure 1.4.1
Cisco Prime Infrastructure 1.4.0.45
a. Create a new VM from ova. It is pretty simple just follow the wizard.
b. Start the VM and when you got prompt type setup
c. Answer all the questions.
a. In my scenario. I used same IP and Host name of my current PI.
d. Say Yes or NO depends on your HA system
e. System will restart and it will take looooong time to start again. It says 10 minutes or more but my one took around 90 minutes.
After PI start successfully
At this stage, please shutdown your PI and make a VM clone and forget about that clone. We will use that clone again while we upgrade 2.2 to 3.0
f. Login as admin:
g. # show repository verify your backup files are there.
a. #restore PI-backup_2.1XXXX.tar.gpg repository FTPupgrade application NCS
b. This will reboot your system and after loooong time it will come back.
c. Verify the application “#ncs status”
d. #backup PI-backup_2.2 repository FTPupgrade application NCS
e. # show repo FTPupgrade
i. Verify the backup
f. #halt
g. Shutdown the VM
Step 5: Upgrade PI to 3.0 file needed PI-Upgrade-3.0.0.0.78.tar.gz.zip
According to Cisco
http://www.cisco.com/c/en/us/td/docs/net_mgmt/prime/infrastructure/3-0/quickstart/guide/cpi_qsg.html#19365
“If you are upgrading from a Prime Infrastructure 2.2.x virtual machine, you should create a new virtual machine with the same deployment configuration option you used previously (for example, Express, Express-Plus, Standard, or Professional), back up your existing virtual machine, and then restore it on the new virtual machine. Perform an inline upgrade from Prime Infrastructure 2.2.x, then delete the old virtual machine after the upgraded virtual machine is fully operational’
A. Unzip the downloaded PI-Upgrade-3.0.0.0.78.tar.gz.zip file . Why they zipped that!
B. Start the clone VM (2.2 fresh).
C. Login as admin
D. #show repo FTPupgrade
E. Verify the files you have at FTP server
F. #application upgrade PI-Upgrade-3.0.0.0.78.tar.gz FTPupgrade
g. Go for a run again.
h. After restart, Login as admin.
i. # ncs status verify the NCS is running.
j. # show repo FTPupgrade verify your backup files are there.
k. #restore PI-backup_2.2XXXX.tar.gpg repository FTPupgrade application NCS
It should be end of from 1.2.1.12 to 3.0
Thanks to:
http://justdowifi.blogspot.com.au/2013/11/upgrading-cisco-prime-12-to-30.html
https://mrncciew.com/2014/01/12/upgrade-prime-using-cli/
http://www.rabbibob.com/index.php/Upgrading_Prime_Infrastructure
And all other People, who posted their experience on Cisco support and various website.
Comments
Post a Comment