Migrate VM300 to VM500 using flexcredits

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements

Migrate VM300 to VM500 using flexcredits

L4 Transporter

Hi, 

Due to throughput limitation i need to change a cluster in VM300 to VM500. FW is currenting working.  What would it be the procedure? minimum impact

 

1 accepted solution

Accepted Solutions

Community Team Member

Hi @BigPalo ,

 

Find some time to get this done during an appropriate maintenance window for your org. In the mean time, you can spin up a VM-500 in parallel. Ensure the VM meets the system reqs of your hypervisor

During your window, deactivate the old VM-300 licenses. Since VM-Series licenses are tied to the VM's UUID and CPU ID, you must deactivate the licenses on the old VM-300 to release them. This will allow you to reuse the same authorization codes on the new VM-500. After deactivation, the old VM's serial number will typically show as "unknown". Go ahead and shutdown the VM-300 once this is complete. 

 

 Log in to the new VM-500's web interface and apply the VM-Series auth code. After activation, verify the license expiration date and that all expected subscriptions are applied on the device and on the CSP. Id also make sure to match the VM-500 panos version to the exact panos that is running on VM-300 as well as the dynamic update versions. The firewall dashboard should display a valid serial number if licensing is successful. 

 

At this point, go ahead and load up the config from the VM-300, verify the config, and commit when ready. Test dataflow and test it all before decommissioning the VM-300 during this maintenance window. 

LIVEcommunity team member
Stay Secure,
Jay
Don't forget to Like items if a post is helpful to you!

Please help out other users and “Accept as Solution” if a post helps solve your problem !

Read more about how and why to accept solutions.

View solution in original post

1 REPLY 1

Community Team Member

Hi @BigPalo ,

 

Find some time to get this done during an appropriate maintenance window for your org. In the mean time, you can spin up a VM-500 in parallel. Ensure the VM meets the system reqs of your hypervisor

During your window, deactivate the old VM-300 licenses. Since VM-Series licenses are tied to the VM's UUID and CPU ID, you must deactivate the licenses on the old VM-300 to release them. This will allow you to reuse the same authorization codes on the new VM-500. After deactivation, the old VM's serial number will typically show as "unknown". Go ahead and shutdown the VM-300 once this is complete. 

 

 Log in to the new VM-500's web interface and apply the VM-Series auth code. After activation, verify the license expiration date and that all expected subscriptions are applied on the device and on the CSP. Id also make sure to match the VM-500 panos version to the exact panos that is running on VM-300 as well as the dynamic update versions. The firewall dashboard should display a valid serial number if licensing is successful. 

 

At this point, go ahead and load up the config from the VM-300, verify the config, and commit when ready. Test dataflow and test it all before decommissioning the VM-300 during this maintenance window. 

LIVEcommunity team member
Stay Secure,
Jay
Don't forget to Like items if a post is helpful to you!

Please help out other users and “Accept as Solution” if a post helps solve your problem !

Read more about how and why to accept solutions.
  • 1 accepted solution
  • 142 Views
  • 1 replies
  • 0 Likes
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!

The LIVEcommunity thanks you for your participation!