v12 APM, Profile scope
Hi new feature in v12, the possibility to define the Access Policy Profile scope (Profile / VS / global). Default is "profile" and is the same behaviour as in pre-12 releases. Anyone has played around with the VS+global scopes and could eventually provide concrete examples of how it does affect the behaviour? Unfortunately, this feature is still poorly documented. From v12 Release Notes: "From Session scope enhancement for increased security In this release, Profile Scope, a new setting in the access profile, establishes additional criteria to ensure that a user who has established a session on one virtual server cannot use that same session to access other virtual servers and the resources behind them." In the documentation, I've found : From the Profile Scope list, retain the default value or select another. Profile: Gives a user access only to resources that are behind the same access profile. This is the default value. Virtual Server: Gives a user access only to resources that are behind the same virtual server. Global: Gives a user access to resources behind any access profile that has global scope." But the use cases are not clear to me Thanks Alex
Is there a way to change which one of my F5s is the 'Active' server in my HA cluster?
Currently I have F5-A and F5-B. I want F5-A to be the active F5 in my HA cluster, however it is currently the standby. What I have: F5-B: Active F5-A: Standby What I want: F5-A: Active F5-B: Standby How can I achieve this without taking them out of the HA cluster? Or will I have to take them out of the cluster and then put them back in?