Forum Discussion
Altostratusviprion chassis
Hello all,
I am planning to upgrade viprion chassis.one of the step of pre-requiste is to verify the license part before rebooting the chassis to a new volume. https://support.f5.com/csp/article/K7727
There are two viprion chassis in my environment .The service check date for both chassis is later than license check date. As per the above link if that is the case then re-activation of license can be skipped. i asked TAC but as per him his personal recommendation is to re-activate the license before reboot.
Has anyone upgraded and rebooted the chassis in the past like this scenario?will the licensing part be fine after reboot from different volume in case i dont reactivate the license ?
youssef1Cumulonimbus
Hello,
I advise you to re-activate license before upgra on the new volume. It does not take time and there are only advantages.
Each time I Upgrade Our Viprion I re-activate license before processing upgrade/reboot.
Just keep in mind that you have to do this step on Viprion that host Standby guest in order to not perturb production. More after the re-activate license don't forget to set all your guest on Configured mode.
Regards
RaghavendraSYPlease follow below procedure:
- Failover traffic from guests (active ones) on standby host to guests on the active host.
- Move Guests to Configure Mode on the Host standby.
- Relicense host standby.
- Upgrade to the new version.
- Move Guests to Deployed Mode on the Host Standby.
- Failover traffic from guests on active to guests on standby.
- Verify the traffic and then proceed with same steps for another host.
Jim_MCirrus
Is there a knowledge base article which gives the steps for upgrading a Vipirion pair? Especially with respect to "configure mode" and "deployed mode"?