Forum Discussion
Looking for Setup Advice
- Feb 12, 2023
You need a first match strategy here. And while it is technically possible to forward to another VS, forwarding directly to the pool member is sufficient here unless you have reasons to forward to a secondary VS.
The flow is: client --> VS (with policy attached) --> pool (selected by policy)
Example:
Hello Amine,
Could you give me an example?
I have tired setting a polices "Match all... HTTP Host>host>is>any of>mysite1.domain.com>request". Then "Do the follow...Forward traffic>virtual server >"VIP I created>request. I am trying to figure out how to create another rule that when it hit "mysite2.domain.com that it goes to the correct pool.
My thought process is this. VIP that's accessible externally, then it redirects it the correct pool but I am lost on creating a default rule that denies traffic or forwards it to a default pool. Thank you for the help an explantion. I'm trying to wrap my head around F5.
Try searching for f5 vip targetting vip.
In theory you should see this,
Vip Targeting Vip Solutions - YouTube
It's basically what you are trying to do.
A LTP (local traffic policy) is all you need, linked to a front virtual service. That hold your extneral IP.
And then internal virtual servers are linked by that policy.
when creating the internal virtual servers they need a IP, that can be any ip it doesn't need to be routable/accessable if you don't want it to be, But you can't create a Virtual server without a ip.
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