Forum Discussion
Robert_Pagano_7
Nimbostratus
Sep 25, 2006how to ensure that 'client' requests which orginate from a load-balanced server are sent to itself by the load balancer
I'm not sure I understand why our apps people need this but here it is...
We have a pool of two servers (let's call them 'S1' and 'S2') which support an 'all-ports' virtual server ('VS').
Apparently, not only 'end-users' access the virtual server; the servers (which support the virtual server) themselves send requests to the virtual server.
The application owners have stated that they need requests which originate from the servers to be 'load-balanced' to the same server which made the request. In other words...
[A] S1 telnets to VS
[B] LTM gets the request and (should) send the connection to S1
Similarly, if S2 telnets to VS, the LTM should send the connection back to S2.
Presently, the VS is configured with the 'least-connections' load balancing algorithm; so S1's telnet request may or may not get sent to S1.
Is there a way to achieve this without disrupting the load-balancing of 'client' machines (which should continue to be load-balanced by the least-connections algorithm)?
We are running version 9.2.3 on 6400s.
Any help will be greatly appreciated.
Thank you.
- Deb_Allen_18Historic F5 AccountHi Rob -
(substitute the real pool name and the correct port if it is not 23).when CLIENT_ACCEPTED { if { [matchclass [IP::remote_addr] equals $::serverIPs] }{ if { [LB::status pool myPool member [IP::remote_addr] 23] ne "down"}{ pool myPool member [IP::remote_addr] 23 } } else { pool myPool } }
Recent Discussions
Related Content
DevCentral Quicklinks
* 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
Discover DevCentral Connects