AltostratusWe are ready to upgrade from 11.5.4 hf2 to 13.1.0.4, but the jump is so high that I want to know if someone already done it and what are the gotchas you had encountered? What process did you follow?
Thank you in advance,
Erika Irene Garner
CumulonimbusHello Erika,
which module do you have?If you check the release notes of your future version (it is supported): https://support.f5.com/kb/en-us/products/big-ip_ltm/releasenotes/product/relnote-bigip-ve-13-1-0.html
Regarding the the potential problematic, All depends on your configuration and the modules you have (ASM, APM, LTM).
you just need to schedule a maintenance period and correct any problems. I made this type of upgrades several times and I already had some problems but nothing complicated: -> ASM policy corruption ( check a service that has ASM to validate that this module work fine if not look at the logs). I already had to redo entire policies. To validate that you have a problem in your ASM Policy, remove IT from your VS and test it...
-> LTM: if the configuration load in general it goes well thereafter. possibly some profile to modify but it is rare ...
I think the best is to manage this aspect during the upgrade and correct any problematic (the possible edge effects that you will have depend on your configuration)... but if you have time and you want a little more comfort you can do it in 2 steps through 11.6.2 then 13...
Regards
CumulonimbusWe recently upgraded our QA device which has APM module from 12.1.x to 13.1.x and device got crashed and we reverted the changes. We are working with F5 vendor to fix the issue.
Till now no success result for us with 13.1.x.
CumulonimbusHi,
What kind of problem have you met? did you implement custo on the APM pages?
can you tell me what logs you had during the upgrade? I suppose that the backup don't upload correctly? ...
regards.
AltostratusWe recently upgraded our QA device which has APM module from 12.1.x to 13.1.x and device got crashed and we reverted the changes. We are working with F5 vendor to fix the issue.
Till now no success result for us with 13.1.x.
CumulonimbusHi,
What kind of problem have you met? did you implement custo on the APM pages?
can you tell me what logs you had during the upgrade? I suppose that the backup don't upload correctly? ...
regards.
CumulonimbusWe are using APM policies for VPN connectivity. After we upgrade a device to 13.1.x TMM was crashing continuously.
We reverted the changes and presently waiting for a vendor update.
Cumulonimbusthis can comme from different issues. But without logs and device access is prety difficult to investigate in this issue. Have you notice a specific logs during TMM crash? int ltm, apm or liveinstall logs?
otherwise the most appropriated is to contact the support. Let me now if i can help you.
Regards,
AltostratusWe are using APM policies for VPN connectivity. After we upgrade a device to 13.1.x TMM was crashing continuously.
We reverted the changes and presently waiting for a vendor update.
Cumulonimbusthis can comme from different issues. But without logs and device access is prety difficult to investigate in this issue. Have you notice a specific logs during TMM crash? int ltm, apm or liveinstall logs?
otherwise the most appropriated is to contact the support. Let me now if i can help you.
Regards,
AltostratusWe are working with the vendor to fix this specific issue, my bet is 13.1.x still not stable version compare to 12.1.x
CirrusConfiguration files of release BIG-IP 11.5.4 are not readable using release 13, it is mandatory to pass via release 12 and to re-license the device Furthermore; using tmsh: the command structure has changed so scripts/commands used to configure the devices need to be adjusted
AltostratusOh wow, I did the Upgrade Advisor on the and didn't give me any errors. I'll make sure to try it out in our QA environment and verify everything works. Thank you for the comment, and it comes in great time. -Erika