Last Modified: Sep 13, 2023
Affected Product(s):
BIG-IP Install/Upgrade, PEM
Known Affected Versions:
11.6.0, 11.6.1, 11.6.2, 11.6.3, 11.6.3.1, 11.6.3.2, 11.6.3.3, 11.6.3.4, 11.6.4, 11.6.5, 11.6.5.1, 11.6.5.2, 11.6.5.3, 12.1.0, 12.1.1, 12.1.2, 12.1.3, 12.1.3.1, 12.1.3.2, 12.1.3.3, 12.1.3.4, 12.1.3.5, 12.1.3.6, 12.1.3.7, 12.1.4, 12.1.4.1, 12.1.5, 12.1.5.1, 12.1.5.2, 12.1.5.3, 12.1.6
Opened: Mar 19, 2016 Severity: 2-Critical
Upgrading from 11.6.0 to a newer version of the BIG-IP software removes the signatures that were installed using an IM signature package, and returns app signatures to the default version.
After rebooting into the new software volume, all the additional categories and applications are gone but the signature package is still showing as installed. This makes a simple re-installation of the new .im signature package impossible. The applications and categories are actually back to default settings for version 11.6.0.
- New '.im' signature package installed manually using the BIG-IP GUI or tmsh. This adds extra applications and categories to the default signatures. - TMOS software upgraded to a newer version, for example installing a rollup hotfix or an engineering hotfix.
For 11.6.x 1. After rebooting into the new software volume, open the bigip.conf file with a text editor and remove all the configurations from the 'ltm classification signature-version' stanza: ltm classification signature-version { }. 2. Manually remove the following files: /shared/lib64/libcec.so.11.6.0*. /shared/tmp/classification_update.conf*. /shared/lib64/libqmprotocols.so*. 3. Create the file /service/mcpd/forceload to force a reload of the mcpd binary database after the reboot by running the command: touch /service/mcpd/forceload. 4. Reboot the system. 5. Re-install the .im signature package. For 12.1.x There is no need to edit configuration in v12.1: After HF is installed reboot to new partition and apply latest signature update file manually or automatically
None