Forum Discussion
jdewing
Cirrus
CirrusAPM Import error: config version 15.1 is not compatible with BIGIP version 16.1
I would like to migrate all of our APM policies from old F5 platform (v15.1) to newer F5 platform (v16.1). I can migrate most of the objects, except for APM.
I get an error message "Import error: config version 15.1 is not compatible with BIGIP version 16.1" when import on the newer F5.
I noticed there is a file called ng-export.conf inside the exported .tar file.
Can I modify the following setting to correct version like this? I'm not sure if there will be bunch of other settings that may be not compatible between version.
#F5[Version:15.1]
#F5[Build:15.1.10.3-0.0.12.0]
To
#F5[Version:16.1]
#F5[Build:16.1.5-0.0.3.0]
Have anyone done like this before?
The best way to do this is to perform the normal upgrade process:
1- Install the old version on a BIG-IP.
2- Load the config.
3- Upgrade the device: https://my.f5.com/manage/s/article/K84205182
In some cases, you can just edit that top line to change the version ID string. As long as you're not using any objects that have changed in the newer version it might work OK. But there's normally no reason to skip the standard upgrade process.
jdewingThanks.. We ended up re-creating APMs (copy-n-paste) on the newer F5. There wasn't much APM policies anyway.
- Lucas_Thompson
Employee
The best way to do this is to perform the normal upgrade process:
1- Install the old version on a BIG-IP.
2- Load the config.
3- Upgrade the device: https://my.f5.com/manage/s/article/K84205182
In some cases, you can just edit that top line to change the version ID string. As long as you're not using any objects that have changed in the newer version it might work OK. But there's normally no reason to skip the standard upgrade process.
- Aswin_mk
Cumulonimbus
You can upgrade all F5 to 16.x rt. What is the issue in upgrading old F5?
Br
Aswin
