Forum Discussion

gongya's avatar
gongya
Icon for Altocumulus rankAltocumulus
Feb 26, 2024

firmware upgrade and downgrade

I upgraded the firmware from 14.1.2.3 to 17.1.1. But the existing license does not support. So I need to revert it back 14.1.2.3.

My question is which configuration each version will use.

After I upgraded to 17.1.1, it seems it uses the configuration from 14.1.2.3. I can use the same IP to access the F5 management.

But when I reverted back to 14.1.2.3, it seemed it used the configuration older than 14.1.2.3. 

I like to understand the options in the attachment.

what is the difference between Yes and No for Install Configuration ?

How can I use the configuration the current 17.1.1 is using ?

 

thanks !!

devops

2 Replies

Sort By
  • Lucas_Thompson's avatar
    Lucas_Thompson
    Icon for Employee rankEmployee
    Feb 27, 2024

    Each partition maintains a separate config.

    BIG-IPs have 3 "configuration sources"

    • The "binary config" or "running config". This is held by MCPd and is what the actual TMM data-plane uses. Upon each boot, this config is read and used. This configuration can occasionally become corrupted.
    • The "config files", bigip.conf, bigip_base.conf, profile_base.conf, and bigip.confs in partitions. These are read by MCPd and transformed into the "binary config" when you do a mcp reload and when you do "load sys config all".
    • The REST configuration. This is held by restjavad and is used for iAppLX stuff (SSL Orchestrator, Access Guided Configuration, a few others)

    The bigip.conf has a line at the top that has the version in plain text. This text prevents MCP from trying to load a config from the wrong version. You can remove this line and MCP will try to load it anyway.

    F5 doesn't "support" (you can't open support cases on it) loading configs from older versions. However you can usually follow this procedure to make it work:

    1- copy the confs to the partition.

    2- load the config: tmsh load /sys config all

    3- Edit the config file to remove or fix areas that cause errors

    4- go to step 2