Forum Discussion
NimbostratusSteps required to upgrade 8900 to 10200 device
Greetings,
There are a number of ways to do this, for example the SCF file which requires some hand editing:K13408: Overview of single configuration files (11.x - 13.x)
https://support.f5.com/csp/article/K13408
My preferred method is to:
1) Ensure the devices run the same software version.
2) Run through the setup utility on the new device(s).
3) Put the new and old devices into a device trust / device group.
4) Perform a configSync to push the configuration to the new.
The procedures are detailed here:
K15496: Migrating new BIG-IP platforms to an existing device group
https://support.f5.com/csp/article/K15496
Both platforms share up to software version 12.1.2:
https://support.f5.com/kb/en-us/products/big-ip_ltm/releasenotes/product/relnote-ltm-12-1-2.html
Hope this is helpful!
KevinGreetings,
I believe these to be the better of the available options:(1)
K82540512: Overview of the UCS archive platform-migrate option
https://support.f5.com/csp/article/K82540512
Configure the base configuration on the 10200 devices.
Create a UCS on the 8900 devices.
Install the UCS using the platform-migrate option on the 10200 devices.
Load the configuration (tmsh load sys config).
Fix any errors.
With the complexity of your configuration, there will be errors. Most popular are:
Configuration objects such as Virtual servers being associated with missing vlans.
Virtual servers or pool members that are unreachable (no route exists).
Just keep tackling the errors one by one until the configuration finally loads successfully.
(2)
K13408: Overview of single configuration files (11.x - 13.x)
https://support.f5.com/csp/article/K13408
Create the SCF file on the 8900 devices.
Edit the file (interfaces, vlans, route domains).
Load the SCF file on the 10299 devices. (tmsh load sys config).
Fix any errors.
Same as above regarding fixing errors.
(3)
Hiring professional services:
https://f5.com/support/professional-services
Hope this is helpful!
Kevin
