Last Modified: Oct 07, 2023
Affected Product(s):
BIG-IP ASM
Known Affected Versions:
11.5.0, 11.5.1, 11.5.2, 11.5.3, 11.5.4, 11.5.5, 11.5.6, 11.5.7, 11.5.8, 11.5.9, 11.5.10, 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.0.0, 12.0.0 HF1, 12.1.0 HF1, 12.0.0 HF2, 12.1.0 HF2, 12.0.0 HF3, 12.0.0 HF4, 12.1.1 HF1, 12.1.1 HF2, 12.1.2 HF1, 12.1.2 HF2, 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, 13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1
Fixed In:
13.1.0
Opened: Apr 05, 2016 Severity: 3-Major Related Article:
K22971309
ASM add_del_internal script does not sync across blades on the VIPRION platform. The changes are not carried over to the secondary slots. The bd.log contains messages similar to the following: ---- BD_MISC|NOTICE|Apr 04 00:54:28.139|18395|temp_func.c:1899|CHANGED INTERNAL PARAM: [cookie_secure_attr][1] ----
This results in an inconsistent config and state between the primary blade and the secondary blades, which can cause inconsistent responses to the same traffic across blades.
This occurs when the following conditions are met: - Add the following internal parameter: 1.# /usr/share/ts/bin/add_del_internal add cookie_secure_attr 2. Run the following command on the primary slot: bigstart restart asm.
Use clsh to set the value using the following command: # clsh /usr/share/ts/bin/add_del_internal add cookie_secure_attr 1.
The VIPRION platform now syncs across blades the internal parameter 'add_del_internal add cookie_secure_attr' after running 'bigstart restart asm' on the primary blade, so inconsistent configurations and traffic handling no longer exist.