Forum Discussion
Yann_Desmarest
Cirrus
Hi,
you create a new health monitor (type https) and change the "Alias Service Port" setting of the health monitor to fit your port requirement.
tatmotiv
Jun 15, 2016Cirrostratus
BTW, since I'm not sure if this is clear to you: You only need to specify the non-default port in the monitor if monitoring a different port than the one the pool member is configured for. So, if the non-default port to be monitored (e.g. 8443) is also configured in your pool member definition (meaning that load balanced traffic is directed to that port), you do not need to define the destination as described above. Leaving the destination of the monitor defined as "*:*" would be OK in this case, since it means: "use the same port for monitoring that is configured in the pool member definition".