Learn F5 Technologies, Get Answers & Share Community Solutions Join DevCentral

Filter by:
  • Solution
  • Technology
Answers

Upgrade BIG-IP Software From 11 to 13

Hi all,

need help, anyone have experience upgrade big-ip software major from 11.0 to 13.0,? can i upgrade the BIG-IP software from 11.0 to 13.0 used generally procedure software upgrade , just used hotfix version 13.0 and BIG-IP software version 13.0, or i must upgrade to BIG-IP software version 12.0 first before to version 13

Thanks

0
Rate this Question

Answers to this Question

placeholder+image
USER ACCEPTED ANSWER & F5 ACCEPTED ANSWER

Hi,

thats a tough question. Build up a lab and upgrade it there.

none the less, why do you already want to upgrade it to 13? Does it have any features, 12 doesnt have?

Also the F5 IHealth Upgrade Advisor should help.

Edit: I would update to 12, last HF, then 13. But its just my opinon.

Greetings, Maximilian Martin

0
Comments on this Answer
Comment made 4 months ago by lhutapea 54

Hi Martin,

Thanks for the response by the way, i have a lab environment but its already version 13 :) i used virtual Edition through VM Workstation, my reason upgrade the software to version 13.0 to avoid security vulnerability with latest patching, hm....i guess so, its secure if i upgrade first to version12 before to version 13.0, Thanks Martin :)

0
Comment made 4 months ago by Maximilian Martin 58

Hi lhutapea,

the question is, which version is more safe. 12, hotfixed or 13 with more vulnerabilities cause they havent fixed it yet. A question we have to ask ourselves on every software i guess. Business wise, i always prefer, older and more fixed than newer.

Going step by step should be the best choice.

Good luck!

Greetings, Maximilian

0
Comment made 4 months ago by lhutapea 54

Hi Martin,

Thanks for the advice.... i very appreciate it...

0
placeholder+image
USER ACCEPTED ANSWER & F5 ACCEPTED ANSWER

can i upgrade the BIG-IP software from 11.0 to 13.0 used generally procedure software upgrade

i understand we can upgrade right away from 11.x to 13.x according to 13.0 release note. anyway, i never did it in production.

Upgrading from version 11.x or later
https://support.f5.com/kb/en-us/products/big-ip_ltm/releasenotes/product/relnote-ltm-13-0-0.html

0
Comments on this Answer
Comment made 4 months ago by lhutapea 54

Hi Nitass,

First, Thanks for the response...i already read the note too.. :) im just buy new appliance for HA puposes, so first i must upgrade software old and new appliance to same version before i joined they as one group HA member, old appliance used software version 11.0 and its production :D, for the new appliance i can test it, but when the appliance come, what if the new appliance its already version 12 or version 13, downgrade the software i think its bad idea... :)

Thanks Nitass... you very help

0
Comment made 4 months ago by Maximilian Martin 58

"what if the new appliance its already version 12 or version 13, downgrade the software i think its bad idea... :)"

f5 should come without any, as far as i know.

Greetings, Maximilian

0
placeholder+image
USER ACCEPTED ANSWER & F5 ACCEPTED ANSWER

I realize that this is an older post, but I've made two attempts myself to go from 11.6.x HF1 to 13.x HF2 and have had issues during both attempts.

It would appear that the primary issue is with a contention issue between APM and ASM. In my specific case, I have some virtual servers that are internet facing and have APM policies in place for user authentication and also ASM policies in place. Also, during the last attempt, I found out the hard way that an ASM policy in Transparent mode isn't really that transparent and still can impact traffic. So, I'm now in the midst of surgically disabling ASM from the virtual servers that also have APM policies and getting ready to try this upgrade again at some point in the near future.

Now, as for the actual configuration copy and rebooting into 13.x, that part actually went well, although I've had to go into the system shell and run cpcfg to copy the configurations as I'm on a viprion chassis and when selecting the boot partition the option to copy the configuration is grayed out. Also, using the cpcfg allows me to ensure that the most current configuration is copied over to the 13.x boot partition so it doesn't spin up without a config.

0
Comments on this Answer
Comment made 3 weeks ago by MichealRP 56

I was finally able to upgrade from 11.6.x to 13.x HF2 without major incident. There are some things to note, starting in v12.x, if you're also using APM, apm policies now have a specific scope setting. Prior to version 12.x, these policies were all considered Global. Meaning someone authenticating to one APM policy on one virtual server, would also be authenticated to any other virtual server. Especially if you're using the same auth domain. Such as .auth.com. Whereas after upgrading, all profiles are set in the Profile scope, which will allow authentication to any over virtual server that uses that same apm policy.

This can cause some issues, at least in our case, as our apm policies were all set for .auth.com (sanatized), so if a virtual server such as test1.stage.auth.com and test2.auth.com use the same access policy, and are connected via the same browser, but different tabs, it can result in a page not found error due to inconsistencies in the fqdn, auth domain, and policy. The way around that is to create a duplicate apm policy, and specify .stage.auth.com on the policy applied to test1.stage.auth.com domain to maintain some separation.

1
Comment made 3 weeks ago by Jie 2141

Thanks for sharing your upgrade experience.

0