Here's some specific things to keep in mind;
•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.
If using iRules check out any changes since v11.2.1;
For detailed information on iRule command, event and other changes for every version refer to this article on DevCentral (registration required): https://devcentral.f5.com/wiki/iRules.BIGIP_Commands_by_Version.ashx.
My standard advice;
•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.