Forum Discussion
NimbostratusLTM Upgrade
Is it necessary to re-activate license every time you do IOS upgrade? I have two LTM 4200 boxes out of support and i want to upgrade them for testing. They are running on 11.6 and i want to go at 13.0..
Any suggestion or precautions to keep in mind while upgrading ?
Thanks
Jad_Tabbara__J1Cirrostratus
Hello,
It is not always necessary to re-activate the license.
To know if it is needed you should determine the "service check date" if it is older than the version release date you will need to re-activate it.
To determine the service check date connect via ssh and advanced shell:
grep -i "service check date" /config/bigip.license
I recommend you to check the following article that summarize in 7 steps the checklist before upgrading
https://devcentral.f5.com/codeshare/7-steps-checklist-before-upgrading-your-big-ip-1053
Hope it helps
Regards
Hectorm_262752Cirrus
You need to be careful when you upgrade from 11.6 to 13.0 If you are using IAPPS in 11.6 there is a bug that will stop the loading of version 13. I ran into this issue from 12.1 to 13.0
here is what the engineer told me BUG ID 666165. The work around to this is removing signatures and checksum from the iApps that had the script dependencies before the upgrade. The workaround is as follow In version 13 modify the tmpl-signature value(tmpl-signature none) and then save. The modifications to the iapps are not necessary. You can use vi to make the necessary changes on the bigip_script.conf(/config/bigip_script.conf).
Ashu_2116Yes we are using iapps. but i am wondering this bug didn't show up in i-health upgrade advisor...
Thanks
HectormYou need to be careful when you upgrade from 11.6 to 13.0 If you are using IAPPS in 11.6 there is a bug that will stop the loading of version 13. I ran into this issue from 12.1 to 13.0
here is what the engineer told me BUG ID 666165. The work around to this is removing signatures and checksum from the iApps that had the script dependencies before the upgrade. The workaround is as follow In version 13 modify the tmpl-signature value(tmpl-signature none) and then save. The modifications to the iapps are not necessary. You can use vi to make the necessary changes on the bigip_script.conf(/config/bigip_script.conf).- Ashu_2116
Yes we are using iapps. but i am wondering this bug didn't show up in i-health upgrade advisor...
Thanks
- Hectorm
I found out about this bug the hard way......I have two BIGIP systems. One has IAPPS and the other does not. The one without the IPAPPS was upgraded without no issue. The other well, I am still working on the BUG. I am schedule to upgrade the unit on August 19. I did the same thing, I health told me I was good to go to version 13
- Hectorm
Now about you original question since you are planning to go to version 13.0.0 probably HF2 you will need to reactivate your license since the version 13 HF2 was out two months ago.
