How to disable OAM when an existing APM policy is assigned to the same VIP
We have successfully deployed APM with OAM Support on V11.1 (via the tick box) on VIP with an existing APM Policy already assigned.
I have written an irule that disables the APM policy via ACCESS::disable based on source IP but there is a business requirement to disable OAM as well based on source IP.
Unfortunately we are forced to have OAM Support and a standard APM policy on the same VIP due to stringent architectural requirements so my suggestion to have two separate VIPs and issue a 302 redirect to the OAM VIP based on DGL lookups wasn't welcomed.
As far as I can tell there is no way to tell ACCESS::disable which policy to turn off?Any ideas if this is at all possible or in roadmap?