Forum Discussion
Adding new Rule breaks my LTM Policy.
Sure,
So I have a "forwarding" policy setup on my VIP to forward requests to pools. Each service I have for the policy, has its own rule on where to go when the URI pattern matches. When I add a new rule for a new service, I try to hit it externally, and it always sends it back to the "default pool" for my VIP. When I dissociate the ltm policy from the VIP, then re-associate it, it works fine. Unfortunately this is a no go since doing this "fix" breaks everyone temporarily when moving the LTM Policy back and forth.
The only thing I havent tried is reordering the rules before trying to hit the service to see if that fixes the issue.
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
