Forum Discussion
AltostratusError post F5 upgrade
Hi raj_raut qq, may I ask whether you reactivated the license prior to performing the upgrade?
If not, I would recommend you reactivate the license and take a reboot of the instance. You might be facing this issue due to Service Date Problem.
If the service check date is missing or is earlier than the license check date, the system will fail to load the configuration when you attempt to boot the upgraded software. If you boot into your newly upgraded system and the configuration fails to load due to a service check date issue, you can resolve this by reactivating your license.
Also, I agree with LiefZimmerman , that you should contact Support for assistance in such situations. That said, the DevCentral Community is always available to help with any questions or clarifications you may have. I hope your issue has already been resolved by now.
Hope it helps!
Mayur
CirrusSupport is certainly the best path to remain on the safe side. If you like, you can run the following from a console to potentially call out the reason for the configuration not loading:
tmsh load sys config verify [partitions all]
Once the command completes the integrity check, with any luck you'll see an error in the standard output listed similar to below:
01071922:3: Policy '/Common/http-to-https-redirect_policy', rule 'http-to-https_rule'; Error in Tcl expression: 'undefined procedure: HTTP:uri: HTTP:uri'.
Unexpected Error: Validating configuration process failed.
In the above error, you'll see the system has identified a syntax error in a LTM Policy object called "http-to-https-redirect_policy" where HTTP:uri is listed and HTTP::uri is the proper syntax. In this example, there was no protection to keep you from making this mistake in the prior version, but there is now. This is why it failed directly after the upgrade.
In addition, there may be warnings within this output, which are just an FYI at that juncture. It will show you what has been deprecated in the new version that simply existed in the prior version.
If you are feeling ambitious, you can make a copy of the .conf file containing the object, manually update the error in the file itself, then load/save the configuration. Again, this would only be recommended if you have a good understanding of the products and the potential hazards in manually editing anything.
As a best practice, it is always good to run the "tmsh load sys config verify" command PRIOR to an upgrade to make sure the integrity of your configuration files at least matches the schema for the version you're currently running. It won't predict anything changing in the new version, hence the errors and warnings.
Reference: https://my.f5.com/manage/s/article/K53233552
I hope that helps!
