Forum Discussion
APM policy sets pool in second virtual
I have encountered some behaviour I don't understand. I've not done much with APM until recently, so am curious to know whether I misunderstand the behaviour and there is perhaps a bug.
I have two virtual servers (vs1 & vs2) with two Access Profiles (ap1 and ap2), sharing the same AAA server profile, SSO profile and domain cookie. ap1 may set the pool in the policy, ap2 never does.
If a user accesses and authenticates via vs1 and the pool is set, then accesses vs2, vs2 sends traffic to the pool set in vs1.
Is this expected behaviour? I can't imagine how this could be the case.
1 Reply
- Stanislas_Piro2
Cumulonimbus
Hi,
do you need to assign pool in VPE instead of Local traffic policy or irule?
Pool assignment form Access policy is shared if session is shared between VS.
If you want to assign pool based on user group, you can assign a cookie in ACCESS_POLICY_COMPLETED event containing a group ID and manage pool assignment based on this cookie.
Help guide the future of your DevCentral Community!
What tools do you use to collaborate? (1min - anonymous)Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com