How to use a different port for HTTPS monitor

Thank you. Do you by any chance knows the TMSH cli syntax for creating this alias service port. I looked at the tmsh reference guide, but couldn't find anything relating to the alias service port.

Yes aure, you can use the option "destination *:8080" in the tmsh cli. Change 8080 by the port you need to apply

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".

Thank you. Do you by any chance knows the TMSH cli syntax for creating this alias service port. I looked at the tmsh reference guide, but couldn't find anything relating to the alias service port.

Yes aure, you can use the option "destination *:8080" in the tmsh cli. Change 8080 by the port you need to apply

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".