Forum Discussion

xmcrexap_245551's avatar
xmcrexap_245551
Icon for Nimbostratus rankNimbostratus
Apr 01, 2016

Config migration v10 to v11 (1500 to 2000s)

Hello everybody,

 

I have a question concerning a futur installation. I have to migrate LTM 1500 Platform to a 2000S Platform.

 

The 1500 Platform is actually in v 10.2.4 HF7 and the new Platform must be in v11. My question is the following, if i put bigip.conf and bigip_base on the new LTM and I'll do a load sys conf, it will work or i have to put the new Platform in v10, import configuration and after that upgrade in v11?

 

Thank you .

 

MC

 

application delivery
BIG-IP
LTM

2 Replies

Sort By
  • Colin_Rogers_17's avatar
    Colin_Rogers_17
    Historic F5 Account
    Apr 01, 2016

    Hello MC, The 2000 platform doesnt run v10 code. https://support.f5.com/kb/en-us/solutions/public/9000/400/sol9476.html You will need to upload the 10.2.4 UCS to the v11.x 2000 platform, and then restore it there. I recommend restoring the ucs through tmsh so you can specify 'no-platform-check' since you are on different hardware. If you have a new license for the 2000 device you can specify the 'no-license' flag as well.

     

    https://support.f5.com/kb/en-us/solutions/public/13000/100/sol13132.html

     

    Hope this helps!

     

  • IanB's avatar
    IanB
    Icon for Employee rankEmployee
    Apr 01, 2016

    You can load the 10.2.4 UCS file on the 11.x device. That's essentially what happens when you do a 10 to 11 upgrade anyway. When the BigIP detects 10.x config, it will upgrade to to 11.x style, and then attempt to load it.

    Make sure you load the UCS from the commandline, as you'll need to use the no-license and no-platform-check options to prevent the 1500's license being restored onto the 2000.

    tmsh load sys ucs 1500config.ucs no-license no-platform-check

    If there are problems and the config does not load, then try to load it manually from the commandline to see what the error is.

    tmsh load sys config

    You'll then need to edit the bigip.conf and/or bigip_base.conf files to fix the error, then load the config again.

    Note that the management address will change to that of the 1500 as a result of successfully restoring the UCS file.