OK hope this is an easy one. I got 2 real servers (primary and backup) that need to be load balanced on port 443. Technically, it's not really load balancing, I only want to send http requests to the primary server.
Now on those servers, I also have port 22022. But only the primary server listens to this port. The standby server will have this port shutdown.
The clients don’t care about port 22022 and they are not going to send any requests to this port. Only 443 traffic will traverse end to end. But the LTM should care about the status of port 22022 because I don’t want the F5 to send http requests to the standby server while port 22022 is in a failed state even when 443 is good.
What would be a good way of doing it? Any one been doing this before?
You can do exactly what you want and a lot more with the Advanced Monitors features in the BIG-IP platform.
So, first configure you monitors:
Manual Chapter: Monitors Settings Reference.
Monitoring TCP Applications #01
Then assign your monitors to your pool members and check your availability requirements.
Local Traffic ›› Pools : Pool List ›› example.pool
Change in Members -> Configuration: Advanced -> Health Monitors -> Member Specific -> Select your monitor
I hope this helps!
I guess you don't understand my question Pedro. I'm not asking how to monitor individual ports. I came from a Brocade ADC where it allows you to put all the ports that you want to monitor into a group then you bind this group to individual real server. That way, if one of the ports fails health checks, it will mark the real server down even the remaining ports are good.
That's what I'm looking for. Hope I've explained it a little better this time.
I'm very aware of what you are trying to do.
And in my example I'm not showing you how to monitor individual ports only.
Please take a look at the first image: This is how and where you will configure each monitor you want to assign, later to a resource (Pool/Pool Member).
The second image shows the option "Select monitors" and here is where you can select any monitor you have created before and "bind/link" them to one or more specific resources. By default, monitors are inherited by all members of a pool. But then, you can change that to adapt the configuration to your needs.
So remember, if you want to monitor multiple ports at once, instead of creating a group of monitors, individual monitors must be created and then grouped into the pool/pool member configuration.
I hope this helps.
OK if I understand you correctly, I would need to create 2 monitors individually, one for each port. Once that is done, come back to my pool configuration and bind those 2 individual monitors that I've created earlier to the pool under the "Select Monitors" option?
You need not create 2 monitors. Here's how monitors work.
Monitors by default perform monitoring on the pool members (188.8.131.52:443), but if you assign an alias here. The monitoring is being done on the 22022 port. It overrides the actual service port 443 for monitoring. So just have 1 monitor created and bind that monitor to the pool.