Forum Discussion
vcmp ha pair resource (cpu/memory) upgrade procedure..
- Apr 09, 2021
As mentioned in the guide you will need to move the guest into the configured state before allocating resources.
Do a tail on ltm log and grep for vcmp then move the guest it to the configured state.
Look for VS_STOPPED->VS_INACTIVE, this indicates that the guest has stopped.
You can then allocate the resources.
There should not be any issues with regards to HA but as always take a UCS for both host and guest.
I also do not see why you will need to move it to forced offline.
You will not be changing any configuration of the configuration objects on the device.
Once resources are allocated move the guest back into the deployed state and you should be good to go
Again do a tail on ltm and grep for vcmp.
Look for VS_STARTING->VS_RUNNING, your guest should be up and running again.
Steps
- Backup host and guest UCS
- Tail ltm log on the host for vcmp (tail -f ltm | grep vcmp)
- Move guest that will be allocated more resources into configured state
- Look for VS_STOPPED->VS_INACTIVE in the ltm log (Shows guest is down)
- Assign resources
- Move guest to deployed
- Tail ltm log on the host for vcmp and look for VS_STARTING->VS_RUNNING (tail -f ltm | grep vcmp)
Hope this helps
*Please note that these are the steps that we followed on our Viprions*
As mentioned in the guide you will need to move the guest into the configured state before allocating resources.
Do a tail on ltm log and grep for vcmp then move the guest it to the configured state.
Look for VS_STOPPED->VS_INACTIVE, this indicates that the guest has stopped.
You can then allocate the resources.
There should not be any issues with regards to HA but as always take a UCS for both host and guest.
I also do not see why you will need to move it to forced offline.
You will not be changing any configuration of the configuration objects on the device.
Once resources are allocated move the guest back into the deployed state and you should be good to go
Again do a tail on ltm and grep for vcmp.
Look for VS_STARTING->VS_RUNNING, your guest should be up and running again.
Steps
- Backup host and guest UCS
- Tail ltm log on the host for vcmp (tail -f ltm | grep vcmp)
- Move guest that will be allocated more resources into configured state
- Look for VS_STOPPED->VS_INACTIVE in the ltm log (Shows guest is down)
- Assign resources
- Move guest to deployed
- Tail ltm log on the host for vcmp and look for VS_STARTING->VS_RUNNING (tail -f ltm | grep vcmp)
Hope this helps
*Please note that these are the steps that we followed on our Viprions*
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