Forum Discussion

Rene_Bader_1308's avatar
Rene_Bader_1308
Icon for Altostratus rankAltostratus
Jul 10, 2014

Platform upgrade from 11.3 to 11.5 --> no configuration

All,

 

I recently did a platform upgrade to 11.5.1 HF3 on a running system.

 

After changing the boot partition to the new image the current configuration from 11.3 was not being moved to the new platform. Just the initial config (mgmt IP, admin pw etc.) are there.

 

I know from earlier upgrade (e.g. 11.2 to 11.3 ) that there was an option to also move the current configuration to the new boot image.

 

How can I get my old config now up and running on the new image?

 

Thanks

 

Rene

 

13 Replies

  • I'm going through this exact issue at the moment on a GTM I upgraded from v11.3.0 HF8 to v11.5.1 HF3. Does your BIG-IP contain a FIPS HSM? That appears to be the problem in our case. The syntax for denoting where keys are stored changed from 'use-fips yes/no' to 'use-fips no/internal/external'.

     

    After fixing this issue in the bigip_gtm.conf file though, other issues presented pertaining to keys already existing in the HSM and the config still wouldn't load. Waiting for support to figure it out.

     

  • Hi Cory,

     

    no, we do not have any FIPS HSM in place. It's a simple active-passive cluster.

     

    Thanks

     

    Rene

     

  • When you perform a 'load /sys config' from tmsh, what error are you receiving?

     

  • No error message when I load the config from tmsh. Actually there is a valid config but it's some initial config that has nothing to do with the one from the "old" image 11.3.

     

    When I switch the boot location I can see the following:

     

     

    I'm missing the row "install configuration --> yes/no"

     

  • Nope. No dialog after pressing "Activate".

     

    Funny thing is, when I switch back to the old image 11.3, I can select to install the config.

     

     

    • JG's avatar
      JG
      Icon for Cumulonimbus rankCumulonimbus
      Please let us know how Support resolved the issue, with Issue ID, etc. Thanks.
  • JG's avatar
    JG
    Icon for Cumulonimbus rankCumulonimbus
    What platform are you on? Also a GTM?
  • All,

     

    the case will be opened by our support guys and I'll let you know the ID soon.

     

    In the meantime I found some workaround that helped me upgrading my machine.

     

    I did I step by step upgrade:

     

    from 11.3 HF8 to 11.4.0 --> the "install config" option is still missing but at least the current config is moved to the new boot image

     

    from 11.4.0 to 11.5.1 HF3 --> the "install config" option is available and the configuration is moved to the new boot image.

     

    For the first step make sure that DB keys "LiveInstall.MoveConfig" and "LiveInstall.SaveConfig" are both set to "enable" (this is the default setting but better check before upgrading. You can find some info here http://support.f5.com/kb/en-us/solutions/public/13000/400/sol13438.print.html)

     

  • B_Torres_7729's avatar
    B_Torres_7729
    Historic F5 Account

    Hi Rene,

     

    The "Install Configuration" option is only available from v11.4.0 onwards as per the article below:

     

    SOL14704: Installing a configuration when activating a boot location http://support.f5.com/kb/en-us/solutions/public/14000/700/sol14704.html?sr=39471097

     

    Regards, Brian

     

  • Drew's avatar
    Drew
    Icon for Nimbostratus rankNimbostratus

    Hi folks

     

    This fixed the same issue for us. We upgraded from 11.3.0 to 11.4.0 and the config didn't go with the build.

     

    We checked using: [drew@vip1:/S2-green-P:Active:Standalone] ~ tmsh list /sys db liveinstall.moveconfig sys db liveinstall.moveconfig { value "enable" } [drew@vip1:/S2-green-P:Active:Standalone] ~ tmsh list /sys db liveinstall.saveconfig sys db liveinstall.saveconfig { value "disable" } As you can see the saveconfig was disabled.

     

    We changed it using: [drew@vip1:/S2-green-P:Active:Standalone] ~ tmsh modify sys db liveinstall.saveconfig value enable

     

    and checked using: [drew@vip1:/S2-green-P:Active:Standalone] ~ tmsh list /sys db liveinstall.saveconfig sys db liveinstall.saveconfig { value "enable"

     

    We built the boot location again and it worked a treat :-)

     

    Cheers

     

    Drew