Forum Discussion
failed to set up cluster after upgrading from v10.2.4 to v11.4.1
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:
-
Disconnect Standby Device
-
Rebuild Standby Device with v10.2.2 media (Volumes)
-
Renew device certificate with expiration of 10 years.
-
Load volume 1.2 with 10.2.2 HF3 and load volume 1.3 with 11.4.1 HF3
-
Boot to volume 1.2 and import config from UCS file (fall-back volume)
-
Boot to volume 1.3 and migrate config from volume 1.2 (dropdown menu selection)
-
Disable interfaces on active device; enable interfaces on newly rebuilt device (essentially a manual failover).
-
Rebuild device that is now standby using same procedure, EXCEPT when you boot to volume 1.3 you DO NOT migrate the config.
-
When offline/standby device boots to 11.4.1 HF3 build network components manually to match required configuration.
-
Renew device certificate with expiration of 10 years.
-
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?
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