How to disable OAM when an existing APM policy is assigned to the same VIP

Hi Aaron,

 

 

I agree that having a separate OAM VIP (whether is called internally via an irule or redirected to via 302) seems the most logical way to go and one that would allow the customer to gradually migrate services from the current APM policy to OAM which is the customer ultimately wants to be! The issue with that would be duplication of administrative points where the logic would have to be implemented:

 

A list of URLs/URIs to make decisions based on would have to have maintained on OAM as well as APM -- true this could be mitigated by using a sideband connection to query the OAM api from the BIGIP but from what I gather the limitation seems to be political more than architectural. The customer rolled out the design with two policies applied to the same virtual and steering away from that would take time and cost more in governance (even if it would actually simplify the task from a technical standpoint).

 

 

Anyway I have made my reccomendations based on the above and raised an RFE as sugegsted, ball - as they say - is now firmly in their court :)

 

 

Thanks for your help in confirming this.

 

 

 

Claud