Forum Discussion
Best possible way to avoid creating large number of pools and virtual servers
You could create a VS with a wildcard port (
*) so all traffic to that IP will hit that VS, and within an iRule you could handle which ports you wanted to route traffic to (using things like datagroups to easily map port to a node, the TCP::local_port command, the node command, and selecting specific nodes as described here).
If you wanted to stay away from iRules, you could probably set up a Local Traffic Policy to handle it as well, but I don't think that'd be as good a choice as using a generic iRule that checks port against a datagroup and then specifies the node (and drops or rejects requests to any non-allowed port).
That would limit you VS to 1 and you pools to 0 (unless you want load balancing, at which point you'd need to use the pool command instead of the node command).
Hope this helps.
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