Forum Discussion
Viprion Upgrade - How to make sure existing config is copied
I realize that this is an older post, but I just went through this with viprion and vcmps. When the vcmps have the new image copied to their boot location, the current configuration is copied over. However, in my situation, that was a few weeks back. During my maint window when I went to make the new boot partition active, the configuration was not copied again. I'm now in a situation where my older configuration (vips, pools, nodes, etc) is as it was the day that I installed the image to the new boot location. I'm having to boot to the older boot location and clsh cpcfg from current boot to new boot manually to correct this.
Hi,
yes, this is expected behaviour. When activating a slot for the first time, the config is copied. Subsequently, as you have found, it is /not/ copied.
I use
clsh cpcfg ...
As per https://support.f5.com/csp/article/K14724
John
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