Forum Discussion
Software Upgrade Process (Viprion & vCMP)
- Mar 15, 2017
You need to upgrade both Viprion chesis n vcmp guest also. F5 v11.3 onwards you can directly upgrade guest n later update Viprion chesis.
I will recommend you to 1st upgrade Viprion chesis then vcmp guest because in Viprion chesis you need to re- licence Viprion before upgrade guest.
You need to upgrade both Viprion chesis n vcmp guest also. F5 v11.3 onwards you can directly upgrade guest n later update Viprion chesis.
I will recommend you to 1st upgrade Viprion chesis then vcmp guest because in Viprion chesis you need to re- licence Viprion before upgrade guest.
- SnlMar 15, 2017
Cirrostratus
I am having similar requirement for upgrade the F5 5250V ( ACTIVE/STANDBY)
is it better to upgrade the host first then guest , what is the best practice here
any advise appreciated
- Samir_Jha_52506Mar 15, 2017
Noctilucent
It's up to you but F5 recommedation is to upgrade 1st host then guest.
- SP_SINGH_279526Jul 07, 2017
Nimbostratus
Thanks you for your advice and recommendation.
- SP_SINGH_279526Jul 10, 2017
Nimbostratus
Can anyone tell me , while re-activating the VIPRION (due to service date and License date issue), do I need to use the same registration key or need new key from F5 ?
- Samir_Jha_52506Jul 10, 2017
Noctilucent
Same registration key will be used. After reactivate license service date will change.
- dragonflymrJul 28, 2017
Cirrostratus
Hi,
One note about reactivating vHost license (from https://support.f5.com/csp/article/K15930😞
Important: Reactivating the vCMP host license will result in a temporary traffic interruption on the guest systems while the license is reactivated on the host system.
I have as well one question. In the same article there is such statement:
Before upgrading a host system, you should gracefully shut down the guests by setting the requested state to Configured.
Is that only way? What is difference between doing
on vGuest and changing state to Configured?shutdown -h now
Piotr
- keithhubbJul 20, 2018
Employee
@Piotr,
 
Sorry, this is such a late response, but it may be useful for others. When you use the shutdown command on a Viprion, the vCMP guest will shutdown on the blade you are logged into. If the vCMP guest spans multiple blades the others will remain up.
 
To use the shutdown command for the entire cluster use "clsh shutdown -h now". The "clsh" command sends the command through the vCMP guest cluster IP, which sends it to each blade. Although, this may leave the guest in the 'Deployed' state on the vCMP host. You may still need to set it to Configured or Provisioned and back to Deployed to restart it.
 
The best way to gracefully shutdown a vCMP guest, as mentioned above, is to set it to the Configured state. Setting the vCMP guest to the Provisioned state also performs a graceful shutdown. The difference between the two is that, in the Configured state the host de-allocates system resources (CPU, memory, etc..), the virtual disk which remains provisioned in either state.
 
The following articles provide further reference on the upgrade process:
 
Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com