cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
2291
Views
0
Helpful
3
Replies
Highlighted
Beginner

PI 2.2 to 3.0 Upgrade (Virtual Machine)

Hi

I am bit confused with the upgrade reference (Quick Reference Link)) - we have prime 2.2 running on VM, as per the upgrade guide I must install new VM for inline upgrade? if so,

  1. Which OVA i should use for new VM ?
  2. What about licenses ? 
  3. Can i just do inline upgrade without deploying new 3.0 virtual machine ?

Thanks

Rajesh

2 ACCEPTED SOLUTIONS

Accepted Solutions
Highlighted
Hall of Fame Guru

Wow that section of the guide is really poorly written. I believe they omitted telling you that the upgrade image was originally intended for use with the physical appliance. I believe Cisco changed that after it was initially released and hasn't adequately addressed the required documentation updates.

Even the downloads page has it labeled ambiguously:

"Cisco Prime Infrastructure 3.0 Upgrade Installer for Physical (for Gen2 Appliance only) and Virtual Appliance 
PI-Upgrade-3.0.0.0.78.tar.gz.zip"

The one "upgrade" that I did was done by deploying a new VM. I used the non-upgrade PI 3.0 image (PI-VA-3.0.0.0.78.ova.zip).

Once it was bootstrapped with the basic setup done so that it was live on the network, I restored a backup from the 2.2 server onto the new VM. That carries the licenses over onto the new host along with all the maps, device information, historical data etc.

View solution in original post

Highlighted

Thanks Marvin for the reply

I took the other way around, directly upgraded the code to 3.0, off-course with a TAC backup :). 

Here are the steps what TAC Suggested

Indeed the first note in the document you shared for inline upgrade on Virtual server a bit confusing , please discard it as you can go directly from your PI 2.2 to 3.0 as below :

 

+Make sure you don’t have FIPs mode enabled in "show security-status".

 

+Take backup from current setup (just in case) :

 

Admin#backup <backup name> repository defaultRepo application NCS.

 

+Remove any HA configurations as stated below if any :

 

http://www.cisco.com/c/en/us/td/docs/net_mgmt/prime/infrastructure/3-0/quickstart/guide/cpi_qsg.html#pgfId-120990

 

+Get the needed bundle software from : PI-Upgrade-3.0.0.0.78.tar.gz.zip https://software.cisco.com/download/release.html?mdfid=286285348&softwareid=284272932&release=3.0.0&flowid=76142 and make sure the md5sum for the file matches on PI after transferring the package to the server. Unzip the package before move it to PI server.

 

+Upgrade to 3.0 :

 

admin# application upgrade PI-Upgrade-3.0.0.0.78.tar.gz defaultRepo

 

for more details : http://www.cisco.com/c/en/us/td/docs/net_mgmt/prime/infrastructure/3-0/quickstart/guide/cpi_qsg.html#pgfId-120990

 

for the licenses they will be transferred automatically nothing is needed from your side.

 

It worked very well, all licenses and devices appeared back. 

Once again thanks for your support

Rajesh

View solution in original post

3 REPLIES 3
Highlighted
Hall of Fame Guru

Wow that section of the guide is really poorly written. I believe they omitted telling you that the upgrade image was originally intended for use with the physical appliance. I believe Cisco changed that after it was initially released and hasn't adequately addressed the required documentation updates.

Even the downloads page has it labeled ambiguously:

"Cisco Prime Infrastructure 3.0 Upgrade Installer for Physical (for Gen2 Appliance only) and Virtual Appliance 
PI-Upgrade-3.0.0.0.78.tar.gz.zip"

The one "upgrade" that I did was done by deploying a new VM. I used the non-upgrade PI 3.0 image (PI-VA-3.0.0.0.78.ova.zip).

Once it was bootstrapped with the basic setup done so that it was live on the network, I restored a backup from the 2.2 server onto the new VM. That carries the licenses over onto the new host along with all the maps, device information, historical data etc.

View solution in original post

Highlighted

Thanks Marvin for the reply

I took the other way around, directly upgraded the code to 3.0, off-course with a TAC backup :). 

Here are the steps what TAC Suggested

Indeed the first note in the document you shared for inline upgrade on Virtual server a bit confusing , please discard it as you can go directly from your PI 2.2 to 3.0 as below :

 

+Make sure you don’t have FIPs mode enabled in "show security-status".

 

+Take backup from current setup (just in case) :

 

Admin#backup <backup name> repository defaultRepo application NCS.

 

+Remove any HA configurations as stated below if any :

 

http://www.cisco.com/c/en/us/td/docs/net_mgmt/prime/infrastructure/3-0/quickstart/guide/cpi_qsg.html#pgfId-120990

 

+Get the needed bundle software from : PI-Upgrade-3.0.0.0.78.tar.gz.zip https://software.cisco.com/download/release.html?mdfid=286285348&softwareid=284272932&release=3.0.0&flowid=76142 and make sure the md5sum for the file matches on PI after transferring the package to the server. Unzip the package before move it to PI server.

 

+Upgrade to 3.0 :

 

admin# application upgrade PI-Upgrade-3.0.0.0.78.tar.gz defaultRepo

 

for more details : http://www.cisco.com/c/en/us/td/docs/net_mgmt/prime/infrastructure/3-0/quickstart/guide/cpi_qsg.html#pgfId-120990

 

for the licenses they will be transferred automatically nothing is needed from your side.

 

It worked very well, all licenses and devices appeared back. 

Once again thanks for your support

Rajesh

View solution in original post

Highlighted

Rajesh,

You're welcome.

Thanks for sharing the TAC guidance and your experience.

Content for Community-Ad