Forum Discussion

1 Reply

  • Upgrade to v10 first and make sure you convert to volumes then;

     

    Upgrade Preparation

     

    Before you embark on an upgrade, particularly between major versions, I’d highly recommend you do some research and identify any potential issues or significant changes that may affect your environment, the following should be observed;

     

    • Perform an upgrade on a test platform if possible, ideally with same modules installed and using the production configuration (even if connectivity is not possible).
    • Read the release notes of the version you plan to move to (start from here: http://support.f5.com/kb/en-us/products/big-ip_ltm.html).
    • In particular note any behaviour changes in case they affect you, as well as the list of known issues – for all minor versions between your current one and what you plan to move to.
    • Check for known issues that may affect you by searching http://support.f5.com/ using the search term ‘upgrading’ and restricting results to Product: BIG-IP LTM / VE and Doc Type: Known Issue and browse through the results.
    • Check for known issues (not officially documented) that may affect you by searching DevCentral (https://devcentral.f5.com/) using the search term ‘upgrading’ and browse through the results.
    • Use iHealth to check your configuration
    • Don’t be afraid to use the help of F5 support and ask for advice specific to your environment.
    • Be aware of the impact of/to any additional modules you have installed and prepare in a similar fashion.
    • Consider any system changes you may have made (custom scripts, cron jobs etc.) that won’t survive an upgrade and backup and plan accordingly.

    Upgrading From v10 to v11

     

    Before you consider upgrading from v10 to v11 you should consider the following and change your configuration accordingly;

     

    • Replace the matchclass Command in any iRules with the class match Command.
    • Remove any global variable references using :: (double colon) or $:: as these are unnecessary in v10 and not supported in v11.
    • Note that Class/Data Group configuration formatting has changed; you shouldn’t have to do anything but keep this in mind as a possible troubleshooting target.
    • Note that Node configuration formatting has changed; you shouldn’t have to do anything but keep this in mind as a possible troubleshooting target, it seems to be a common cause of issues.
    • Ensure all service and protocol specifications in your configuration files use a port number, not a service name.
    • Anything configured in an Administrative Partition that doesn’t have the path specified in the v10 configuration files, needs that path to be specified in v11; edit your files as necessary.
    • The parent id command becomes parent name in v11 and may prevent the configuration from loading post upgrade.
    • Your existing v10 installation must use Volumes, not Partions, see SOL15459.
    • If upgrading from v10 to v11.2.1 see SOL14104.
    • If upgrading from v10 to v11.4 or v11.4.1 see SOL14832.
    • In v11.x ServerSSL profiles have a Secure Renegotiation value set to Require Strict. This may cause issues with Pool Members that do not support TLS Renegotiation Indication Extension. Should you find you encounter issues post-upgrade with server-side SSL connections failing, change this setting to Request.

    Upgrading to v11.4

     

    • HTTP Classes are replaced by Local Traffic Policies; you shouldn’t have to do anything but keep this in mind as a possible troubleshooting target.
    • iRule HTTP_CLASS_XXX events are replaced by POLICY commands; you should remove any rules using these events prior to the upgrade and then rewrite them accordingly and reapply them once the upgrade is complete.
    • Classes must be in the KVP format; without both a key and value the Class cannot be updated from the GUI. See SOL14671 for more information.

    Upgrading to v11.6