I tried to do an upgrade of my bigip 1600 from v10.2 to v11.4.1. I used HD1.2 to load the base 11.4 iso then I upgraded it to v11.4.1 via hotfixes. I made HD1.2 the boot partition however the F5 did not boot after that. It claimed that my license needs to be renewed. AFter reading this thread (https://devcentral.f5.com/questions/bigip-ltm-failed-to-start-with-config-after-upgrade) I performed a switchboot from the F5 console and went back to the v10.2 version. I want to try to re-activate the license before doing the upgrade. However, I can't seem to figure out how to do that. Does anyone have an idea? Or a thread that walks through the process?

Hi Danny, the license need to be reactivated to reflect a current service check date. The service check date must be younger than the software release you try to implement. The reactivation can be done through WebUI > System > License [Reactivate (manual)] or via CLI using the "get_dossier" utility: grep -iE 'reg.*key' /config/bigip.license | awk '{print "get_dossier -b", $NF}' | bash -x The dossier file needs to be posted to https://activate.f5.com/license/dossier.jsp and a new license with updated service check date will be provided. The license will be imported through WebUI or simply by replacing the current /config/bigip.license. (Avoid windows line breaks in the license file!) If you are using command line tools to replace the license, it will be required to run the command "reloadlic" afterwards. This command will restart the services. Make sure, to run it on the standby unit only. It´s best practice to create a backup archive as fallback. If you got a new license installed, you can use the tool "cpcfg" to copy the current configuration including the new license to the target volume (i.e. HD1.2) followed by switchboot and reboot: cpcfg HD1.2 switchboot -b HD1.2 reboot Thanks, Stephan

If I understand your reply, I can use the WebUI or dossier method to get a reactivated license. This will update the license on the existing v10.2 on HD1.1. Afterwards, when I run the "cpcfg HD1.2" the config on HD1.1 (including the reactivated license) will be copied to HD1.2. After the switchboot and reboot, the HD1.2 will boot and there will be no license errors. Also all my settings will have transferred over (because of the cpcfg). Please let me know if I misunderstood anything. Also will HD1.1 continue to operate with the reactivated license? Note. The way F5 objects (ie. VS, Pools, Nodes, etc) are stored in the bigip.conf file differs between v10.2 and v11.4.1. Will the cpcfg make the necessary adjustments? If not, can I copy a bigip.conf file that has been manually updated to the v11.4.1 format to HD1.2?

Hi Danny, yes, you can use the WebUI or the get_dossier utility to create a new dossier file. You need to upload the dossier to the F5 site to receive a new license file. Yes, cpcfg copies the current configuration including new license to the target volume. The import procedure on the target volume will extract the configuration after the reboot and convert it. Due to changed behaviour (check release notes for details) you may expect issues. Plan a maintenance window. Personally I prefer to import the configuration to a virtual edition in v10 and to run the upgrade to v11, adjust configurations if required and do several tests before touching the production unit. Thanks, Stephan

My recommendation is to do the following: from 10.2.4 to 11.2.1 then upgrade to 11.4 I had to upgrade in this manner as I was told by my SE not to do direct upgrade from 10.2.4 to 11.4

Thanks guys. So I followed Stephans instructions and it worked. The F5 booted up normally but it says its "Online (Active)" and "Standalone". Is this normal, or did I do something wrong.

How do I upgrade my F5 from v10.2 to v11.4.1

12 Replies

StephanManthey
Nacreous
Mar 03, 2015
Hi Danny, the license need to be reactivated to reflect a current service check date.

The service check date must be younger than the software release you try to implement.

The reactivation can be done through WebUI > System > License [Reactivate (manual)] or via CLI using the "get_dossier" utility:

grep -iE 'reg.*key' /config/bigip.license | awk '{print "get_dossier -b", $NF}' | bash -x

The dossier file needs to be posted to https://activate.f5.com/license/dossier.jsp and a new license with updated service check date will be provided.

The license will be imported through WebUI or simply by replacing the current /config/bigip.license.

(Avoid windows line breaks in the license file!)

If you are using command line tools to replace the license, it will be required to run the command "
reloadlic
" afterwards. This command will restart the services. Make sure, to run it on the standby unit only.

It´s best practice to create a backup archive as fallback.

If you got a new license installed, you can use the tool "cpcfg" to copy the current configuration including the new license to the target volume (i.e. HD1.2) followed by switchboot and reboot:

cpcfg HD1.2 switchboot -b HD1.2 reboot

Thanks, Stephan
Danny_Arroyo
Cirrus
Mar 03, 2015
If I understand your reply, I can use the WebUI or dossier method to get a reactivated license. This will update the license on the existing v10.2 on HD1.1. Afterwards, when I run the "cpcfg HD1.2" the config on HD1.1 (including the reactivated license) will be copied to HD1.2. After the switchboot and reboot, the HD1.2 will boot and there will be no license errors. Also all my settings will have transferred over (because of the cpcfg).

Please let me know if I misunderstood anything. Also will HD1.1 continue to operate with the reactivated license?

Note.

The way F5 objects (ie. VS, Pools, Nodes, etc) are stored in the bigip.conf file differs between v10.2 and v11.4.1. Will the cpcfg make the necessary adjustments? If not, can I copy a bigip.conf file that has been manually updated to the v11.4.1 format to HD1.2?
- StephanManthey
  Nacreous
  Mar 03, 2015
  Hi Danny, yes, you can use the WebUI or the get_dossier utility to create a new dossier file. You need to upload the dossier to the F5 site to receive a new license file. Yes, cpcfg copies the current configuration including new license to the target volume. The import procedure on the target volume will extract the configuration after the reboot and convert it. Due to changed behaviour (check release notes for details) you may expect issues. Plan a maintenance window. Personally I prefer to import the configuration to a virtual edition in v10 and to run the upgrade to v11, adjust configurations if required and do several tests before touching the production unit. Thanks, Stephan
jgranieri
Nimbostratus
Mar 04, 2015
My recommendation is to do the following:

from 10.2.4 to 11.2.1 then upgrade to 11.4

I had to upgrade in this manner as I was told by my SE not to do direct upgrade from 10.2.4 to 11.4
Danny_Arroyo
Cirrus
Mar 04, 2015
Thanks guys.

So I followed Stephans instructions and it worked. The F5 booted up normally but it says its "Online (Active)" and "Standalone". Is this normal, or did I do something wrong.
- StephanManthey
  Nacreous
  Mar 04, 2015
  Hi Danny, it will be necessary to build the v11 device cluster. Was your logical configuration (virtual servers, pools etc.) migrated properly? Thanks, Stephan
Danny_Arroyo
Cirrus
Mar 04, 2015
Yes the VS, pools, etc migrated properly (really happy about that). I will build the v11 device cluster. However, I probably have to upgrade the other node before I do, correct?

I'm a bit confused about my current situation because both nodes are active and have the same VS, pools, nodes, etc configured. Is my network about to explode?
- StephanManthey
  Nacreous
  Mar 04, 2015
  Go into Device menu and select the device and bring it into forced offline. This way you avoid duplicated IP addresses. Next step will be to assign device specific settings for sync, heartbeat and mirroring. This is a per-requisite to build the device cluster afterwards. Are you familiar with the necessary steps regarding v11 device clustering?
Danny_Arroyo
Cirrus
Mar 04, 2015
Yes I am familiar with the necessary steps for v11 device clustering. Ill Force the upgraded node offline and run through the clustering process.

However, don't I have to upgrade the other node to v11 before I re-create the cluster?
- StephanManthey
  Nacreous
  Mar 04, 2015
  Hi Danny, v10 and v11 cannot run in a device cluster. It would be necessary to upgrade it to v11 and establish the cluster. Both machines have to be on same hotfix level: 1. define local sync, failover and mirroring addresses on both machines in device settings. 2. verify connectivity between both units on the failover network (port lockdown in "allow default" - that´s why I prefer a dedicated VLAN 3. have specific device certificates for both machines (not mandatory but that´s best practice) 4. configure the remote peer on one machine in the device trust settings 5. verify both machines are listed on each device including the TMOS version in description 6. configure device group on one machine (select "sync-failover", "network failover" and get both devices into the new device group) 7. now you should be ready for the initial sync Make sure to configure ha-group settings according to your failover criteria. Thanks, Stephan
Danny_Arroyo
Cirrus
Mar 04, 2015
After following your instructions Stephan, both nodes are upgraded and happy in their new cluster. Very much appreciate your help.
- StephanManthey
  Nacreous
  Mar 04, 2015
  Thanks for the feedback!