Bug ID 507586: Changing access policy on vs (created through wizard) doesnt become active immediately until tmm restart

Last Modified: Nov 22, 2021

Bug Tracker

Affected Product:  See more info
BIG-IP APM(all modules)

Known Affected Versions:
11.4.1

Opened: Feb 17, 2015
Severity: 3-Major

Symptoms

Changing access policy attached on vs (created through apm wizard) does not become active immediately --- need to restart tmm or reboot box. It continue using the originally attached access policy to the VS even though the cli/gui shows the changed access policy. Only after tmm restart the change takes place effectively.

Impact

Even though the cli/gui shows the changed access profile. It continues using the originally attached access profile to the VS Customer requires a tmm reboot for the access profile change to be effective in VS.

Conditions

1. Create an access profile & vs using wizard. 2. For troubleshooting convenience: put some debugging string into VPE action items: Start -> Message -> Logon -> ... 3. Access vs using browser, observe that "Message" or "Logon" action items are observed correctly. 4. Now, create another access profile and put some debug string into VPE action items: Start -> Message -> Logon -> ... 5. Change access profile from the vs created in step 1. to this newly created access profile. Update. 6. Access vs using browser, observe that browser still gets items from previous access profile (*not* from newly assigned access profile.)

Workaround

The issue is not seen when changing the access profile created manually to the VS. It only happens when the access policy and VS is created through APM wizard.

Fix Information

None

Behavior Change