Forum Discussion
Smashytech_2187
Cirrus
CirrusUpgrade vCMP host via Big-IQ?
Hi,
We have a viprion chassis, and we manage all our loadbalancers via Big-IQ. However when we try to do a upgrade (minor upgrade 12.1.2 -> 12.1.3.2) via the Big-IQ, we cannot get the config to be synced to the new HD where we're installing the new firmware on.
I've read that you need to manually copy the config from the old HD to the new. But as we're using Big-IQ, shouldn't this be as an option to actually do this so we dont need to do any manual work on each loadbalancer? The whole idea behind Big-IQ i thought was to make things easier :)
We've found what was the cause of our issue.
We have enabled a few services on each virtual F5, like AFM, APM, LTM etc. However these worked fine on our old image. But when our F5 didn't have enough cores or memory assigned to handle the newer version. We did assign 4 cores instead along with more memory. After this was done the installations via Big-IQ worked as intended and everything came up the way it should :)
F5_Digger_13600What version of BIG-IQ do you use?
I have used BIG-IQ since the version 5.2 and started using BIG-IP upgrade through BIG-IQ with the version 5.3.
With 5.3 and 5.4(recently released), I have never had the manual config copy. One catch with BIG-IQ 5.3 and Viprion vcmp guest, it doesn't support pre- and post assessment feature where BIG-IQ provides pre- and post-upgrade configuration differences such as interface status, vlan, virtual server, pool, monitor and so on.However with BIG-IQ 5.4, now it is supported, which really decrease the administrative effort after the upgrade.
Smashytech_2187Right, We're using 5.4 now and we seem to get this after we've upgraded to the newest version I'm not sure if there are some kind of bug im hitting, but I'm leaning towards creating a ticket to F5.
- Smashytech_2187
We've found what was the cause of our issue.
We have enabled a few services on each virtual F5, like AFM, APM, LTM etc. However these worked fine on our old image. But when our F5 didn't have enough cores or memory assigned to handle the newer version. We did assign 4 cores instead along with more memory. After this was done the installations via Big-IQ worked as intended and everything came up the way it should :)