Forum Discussion
LTM Policy to select pool based on TCP port is not working
Hello Mahi.
It's not necessary to configure a policy.
You could configure 3 VS like this:
A.B.C.D:45000
A.B.C.D:45005
A.B.C.D:0
REF - https://support.f5.com/csp/article/K14800
KR,
Dario.
- MahiApr 01, 2020Cirrus
Thanks Dario, we tried that solution and its working.
For some reason, we need only one VIP and not use an iRule. Therefore, we decided to go via the policy route.
- Apr 02, 2020
Hello Mahi.
Configure 3 VS is faster than configure a policy.
Anyway, I've tested in my lab and it's working fine using forward to pool (with "local - external" and automap)
ltm policy Policy_Test { controls { forwarding } last-modified 2020-04-02:09:07:31 requires { http tcp } rules { redirect { actions { 0 { forward select pool P-WEB_80 snat automap } } conditions { 0 { tcp port local values { 80 } } } } } status published strategy first-match }
KR,
Dario.
- MahiApr 02, 2020Cirrus
Dario;
I checked the configuration and its exactly the same with difference of 'snat automap' and 'local' being not there. I guess the automap will be effective since its declared in the Virtual Server configuration.
I am seeing a 'Reset' packet from the virtual server with the reason 'No server selected' in the packet capture. Somehow the policy is not kicking in. Any thoughts?
- PeteWhiteApr 02, 2020EmployeeOk, local needs to be there. As you say, don’t worry about snat
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