Forum Discussion
Loadbalancing issue
- Oct 27, 2020
You can do something like:
One virtual server (Ex. 4.4.4.4:*), with one pool with two wildcard pool members (1.1.1.1:* Priority 2, 1.1.1.2:* Priority 1).
The pool will need several settings like Action on Service Down set to Reject, and Priority Group Activation set to 'Less than 1'.
Last but not least you will need to create and assign the pool three custom monitors (one per port, 80, 3151, 8090).
Hope that helps.
What i want, is lets say i have two servers in a poot member listening on below ports
Ports: 80, 8090 and 3151
Node: 1.1.1.1
Node: 1.1.1.2
Lets say first node with a priority of 1 (1.1.1.1) stop listening on port 80 but other ports are working ex: 3151 and 8090
automatically i want the f5 to consider the node 1.1.1.1 down on all ports and start shifting the traffic to the standby node 1.1.1.2
- wlopezOct 27, 2020Cirrocumulus
You can do something like:
One virtual server (Ex. 4.4.4.4:*), with one pool with two wildcard pool members (1.1.1.1:* Priority 2, 1.1.1.2:* Priority 1).
The pool will need several settings like Action on Service Down set to Reject, and Priority Group Activation set to 'Less than 1'.
Last but not least you will need to create and assign the pool three custom monitors (one per port, 80, 3151, 8090).
Hope that helps.
- jaikumar_f5Oct 30, 2020MVP
At Op, you didn't you needed a wildcard VS, I was under the impression that you had a 443 VS and Pool member on port 80. But those pool members had dependencies on other ports you mentioned.
If that was the case, a simple VS with pool member on port 80, with 3 monitors in AND condition and PG setting would have done the job. NM, as long as you've got a solution, we are good.
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