Error post F5 upgrade

raj_raut​ - your post was held in moderation for a while. Your best bet is still probably connecting with Support.
If you have a ticket already that's good, but if you are still waiting to hear back you may find some guidance here on DevCentral (which may also help clarify a few basic questions for Support and result in a quicker resolution)

Provide more detail about your question here (don't share private/secure info)?

Support 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!

Thank you, Lief, Cory, and Mayur, for your thoughtful responses. I truly appreciate the support, and I am pleasantly surprised by the level of engagement. I’m happy to confirm that the issue has been resolved.

It was related to license reactivation, and here, I am seeing one of the suggestions to reactivate the license.
Thank you once again for your assistance.

We mostly contact the support always, but yesterday's case was panic, so we were checking all the possible options. Good part is, I learnt new things and also, I came across Decentral Community.

Best, Raj