Forum Discussion

Sukumar_121924's avatar
Sukumar_121924
Icon for Nimbostratus rankNimbostratus
Feb 22, 2015

Migration from version version 9.4.5 or 9.4.8 to version 11.1.0 or 11.4.1

How to Migration from version version 9.4.5 or 9.4.8 to version 11.1.0 or 11.4.1 and steps and preparation to be taken

 

3 Replies

  • Which device are you using.so that we can check the compatibility for the upgrade

     

  • Hi Sukumar,

     

    most times I´m using a virtual edition to migrate configurations for clients.

     

    I guess you are migrating to new hardware and cannot touch the v9 implementation as it is still in production, right?

     

    My approach (done it a couple of times for several clients for LTM migrations v9 > v11) involves importing keys/certs/external monitors/external datagroups manually to a v10 installation running as virtual edition.

     

    After removing interface/trunk definitions from the v9 bigip_base.conf I import it to the plain v10 installation and merge the v9 bigip.conf file.

     

    At this point you should check for necessary modification due to changed behaviour (includes modified monitor request strings, usage of matchclass/findclass commands (to be replaced by new "class" syntax) in iRules, declaration of global static variables and array definitions in iRules, usage of httpclass (to be replaced by policy rules since TMOS v11.4+) and other aspects listed in the changed behaviour documents.

     

    Now you can try to upgrade your VE to v11 and after assigning interfaces to VLANs you can run tests.

     

    If everything works as expected you are ready to import keys/certs/external monitors/external datagroups to the new appliance, import the network configuration elements via merging the bigip_base.conf and add interface/trunk definitions, build the v11 device-group and finally merge the bigip.conf.

     

    Even I´m using the CLI for most import tasks this can take a couple of hours or even longer depending on the number of modifications due to changed behaviour.

     

    Be aware, that default settings in ssl and tcp profiles were changed.

     

    Depending on the complexity of your setup you may consider to involve F5 Professional Services folks.

     

    This is very likely not something to handle in a maintencance window during night shift.

     

    Thanks, Stephan