Forum Discussion

Steve_M__153836's avatar
Steve_M__153836
Icon for Nimbostratus rankNimbostratus
Jul 18, 2014

We recently upgraded a pair of lesser appliances from 10.2.2 HF3 (Partitions) to 11.4.1 HF3. Our high-level procedure that was reviewed and modified by F5 consulting services was this:

 

  1. Disconnect Standby Device

     

  2. Rebuild Standby Device with v10.2.2 media (Volumes)

     

  3. Renew device certificate with expiration of 10 years.

     

  4. Load volume 1.2 with 10.2.2 HF3 and load volume 1.3 with 11.4.1 HF3

     

  5. Boot to volume 1.2 and import config from UCS file (fall-back volume)

     

  6. Boot to volume 1.3 and migrate config from volume 1.2 (dropdown menu selection)

     

  7. Disable interfaces on active device; enable interfaces on newly rebuilt device (essentially a manual failover).

     

  8. Rebuild device that is now standby using same procedure, EXCEPT when you boot to volume 1.3 you DO NOT migrate the config.

     

  9. When offline/standby device boots to 11.4.1 HF3 build network components manually to match required configuration.

     

  10. Renew device certificate with expiration of 10 years.

     

  11. Build device trust/peer list from scratch and create device group for sync/failover.

     

I've never seen anyone say they migrated from v10.2.2 or earlier to v11.x without having to completely rebuild the device trust and pair the devices up from scratch. Hope this helps. If you have specific questions about the device trust/device group/peer list process what are they?

 

  • JG's avatar
    JG
    Icon for Cumulonimbus rankCumulonimbus
    Jul 19, 2014
    Thanks very much for sharing this. I wonder what the purpose of 2 is? What specific benefits does that step bring? It seems that the strategy is to create a volume for each of v10.* and v11.4.1 with the default configuration. What is meant by "load" in 4? Is that simply to apply v10.2.2 HF3 and install v11.4.1 (with HF3) each to another volume without running "switchboot"? And is it a new feature in v11.4.1 that one can migrate the config of a previous version from a non-active boot volume?
  • Steve_M__153836's avatar
    Steve_M__153836
    Icon for Nimbostratus rankNimbostratus
    Jul 19, 2014
    Apologies, I for some reason used some odd verbiage. "Load" should be "Install". For step 2 we had devices that were built with Partitions instead of Volumes so we had to rebuild them from scratch. Otherwise it would just been a matter of installing to other volumes. We wanted to create a vanilla 10.2.2 volume, a 10.2.2 HF3 volume to match our existing configuration and import the config there as a fall-back volume, and then the 11.4.1 HF3 was our migration volume. When you boot into a v11 from a v10 volume via the GUI you have no option, but the config is migrated to the v11 volume whether you want it to or not. There are probably command-line ways around that, but we wanted it to migrate our config. Hope this clarifies my post a bit.
  • HR_38560's avatar
    HR_38560
    Icon for Nimbostratus rankNimbostratus
    Aug 12, 2014
    We have the same issue, did you manage to fix it?