Forum Discussion
HTTPS VS inbound and :Port to Pool Selection
This is almost never a good idea, as Cory stated you're much better off using multiple VS and attaching the pools appropriately. By default the LTM will drop traffic that doesn't match, you can do the reject if you really want by doing
VS_8080 x.x.x.x:8080 -> type standard, pool mytestlabtest.com-8080
VS_8081 x.x.x.x:8081 -> type standard, pool mytestlabtest.com-8081
VS_8082 x.x.x.x:8082 -> type standard, pool mytestlabtest.com-8082
VS_0 x.x.x.x:0 -> type reject
That lets you put the appropriate profiles (like independent clientssl profiles) on each VS. It's more efficient than using an iRule and easier to read.
If you want to log the rejects you would attach an iRule with a log statement to VS_0, or use a logging profile, or AVR.
If you really, really want to do this with the port 0 VS and iRule then you can do it with a switch as you have above.
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