Forum Discussion

madhuguru_31940's avatar
madhuguru_31940
Icon for Nimbostratus rankNimbostratus
Jul 21, 2017

best option to migrate config from 3600 to i2600

I am trying to replace a 3600 in HA with i2600 HA. what is the best way to migrate? Please suggest.

 

I took UCS backup from primary 36000 and restored in once i2600(host name same) with no- license and no-platform-check command then edited the bigip_base file to change the interface numbering ( 3600 interfaces is named as 1.1,1.2,1.3,1.4... and i2600 1.0,2.0,3.0 ...etc****) after then I ran load /sys config verify and I didn't get any error message . but after loading the config when I log in to the device on GUI I cannot see most of the configuration except interface and self-IP details and get an error message ( the configuration has not yet loaded ....) please help to resolve this. is this something to do with master key migration?

 

application delivery
BIG-IP
TMSH

4 Replies

Sort By
  • madhuguru_31940's avatar
    madhuguru_31940
    Icon for Nimbostratus rankNimbostratus
    Jul 21, 2017

    Is this something to do with the master key? I ran f5mku -f on 3600 devices, copy the key and tried to apply it on i2600 using f5mku -r key, but got an error message master key invalid ... I have some PFX certificate in the 3600 devices with password protect . Will it also be copied if we don't make the master key in i2600, same as in 3600? is this creating the problem? Please suggest.

     

  • Chris_Grant's avatar
    Chris_Grant
    Icon for Employee rankEmployee
    Jul 23, 2017

    Platform migrations are never easy. The master key is used to encrypt and decrypt the various passwords in the files. The easiest way to accomplish this would be to replace the encrypted passwords and passphrases with the plain text. You should be able to load the configuration

    tmsh load sys config partitions all

    Once the configuration is loaded, and assuming that you didn't get any errors, you will want to check the last few lines of the ltm file to make sure:

    tail /var/log/ltm

    Resolve the errors as they come up, repeating the above steps until your configuration really does load. At this point you will want to save the configuration.

    NOTE: If you save the config and it has not loaded properly, you will erase your on disk configuration and have to start over!

    tmsh save sys config

    When you save your configuration we will encrypt the plain text passwords and passphrases using the new unit's master key. You will want to take a new UCS at this point, as well as running a qkview and uploading it to iHealth. This will allow you to review for known issues.