Last Modified: Sep 13, 2023
Affected Product(s):
BIG-IP APM
Known Affected Versions:
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
Fixed In:
12.1.0
Opened: Jan 07, 2016 Severity: 3-Major
Some or all profile licenses may be missing after failover or, in a chassis high availability (HA) setup, if some blades in the standby chassis are removed, followed by failover. As a result, sessions cannot be established and the following error message will show up in the APM log. -- err tmm8[16609]: 01490514:3: 00000000: Access encountered error: ERR_NOT_FOUND. File: ../modules/hudfilter/access/access.c, Function: access_process_state_client_get_license, Line: 7135. -- err tmm8[16609]: 01490514:3: 00000000: Access encountered error: ERR_NOT_FOUND. File: ../modules/hudfilter/access/access.c, Function: hud_access_handler, Line: 2487.
Session will be terminated due to ERR_NOT_FOUND error when acquiring profile license.
This failure may happen in a HA setup when 1. Failover happens, or 2. Changing multi-blade chassis HA blade configuration as follows: 2.1. Set mirroring to 'between'. 2.2. Leave the primary blade up and shut down the secondary blades in the standby chassis. 2.3 Change 'minimum numbers of blades up' to 1. 2.3. Force failover. The 1-blade chassis becomes active.
For failover case: -- Disassociate and then re-associate the APM profile with the virtual server after failover. For blade configuration change, there are two options: 1. After failover, disassociate and then re-associate the APM profile with the virtual server after the 1-blade chassis becomes active 2. 2.1. Change mirroring to 'within'. 2.2. Shut down the secondary blades one by one, waiting a few minutes in between each shutdown (waiting is important because SessionDB needs some time to create backup copies). 2.3. Force failover. 2.4. Change mirroring back to 'between'.
Profile licenses are now recreated if found missing due to failover or blade-configuration changes.