Ltm Upgrade 11.6 from 11.4.1

It is always worth to check the release notes regarding changes in behavior, known issues and make sure to parse your current configuration with this information in mind. In case of a pure LTM configuration I would especially look for iRule syntax elements (transferred over from v9/v10 configurations) that may cause issues in newer software releases. With v11.6 you will get new SSL ciphers and SSLv3 is disabled in the "default" cipher string alias. So SSL/TLS interoperability tests with your client base and perhaps with your poolmembers (in case of applied server-ssl re-encryption and https-based monitoring) should be mandatory after the upgrade.

 

Refresh both systems license in advance, put the unit to upgrade in forced offline mode before using cpcfg to transfer the configuration, license and state to the new installation volume after doing the installation.

 

The heartbeat will be interoperable between both versions.

 

After upgrading I would review the HA-group setup as new options on HA-group traffic-group mappings are provided since v11.5.