Passing Pool Member Port using Custom TCP Monitor

You can do this with alias address and alias service port. Thus you can associate a monitor to a pool member, but the monitor could be monitoring another server. For example let's say you have a pool member 192.168.12.32:80, but it relies on an app component on a server 192.168.1.22:22222 TCP that is not behind the LTM.

 

 

Then you can set up the alias address as 192.168.1.2 with alias service port 22222. Then you associate the monitor to the pool member. This basically tells the LTM that 192.168.12.32:80 is dependent on the health of 192.168.1.22:22222

 

 

 

If you want to simply monitor a different port on the same pool member that is not being load balanced then simply leave the alias address to "* All Addresses" and change the Alias port to what you want to monitor. This will then monitor a different port then what you are load balancing.

 

 

 

Thanks,

 

CB