Forum Discussion
bigipjr28_13978
Nimbostratus
NimbostratusHTTPS default health monitor
Hey guys,
What exactly does the default https health monitor preform? We have an application where it uses the default https health monitor but no longer works as its marking the nodes down in t...
AhmedMostafa_16Nimbostratus
NimbostratusI have the same issue I am using F5 to load balance Exchange 2013 CAS servers. The Node use the default monitor https_443, & the Node marked down. I create a new https monitor but when i try to add it to the node by selecting "Node Specific" monitor , i can not see my new created health monitor.
Any idea ?
- Hi Ahmed, please try to assign the monitor on pool level or on pool member level. Be aware, that with adding new pool members by default a member specific monitor would be assigned (and if not it will remain unchecked). Make sure to always use the advanced settings when adding a pool member and select the option "monitor: inherit from pool". In case you really would like to assign a newly created L4 (and higher) monitor on node level, it will be necessary to specify an "Alias" port in the monitor definition. The "Alias" port specifies the TCP-/UDP-port the monitor should target. (On node-level or with poolmembers configured with a wildcard port the monitoring demon simply doesnt know, where the monitor should connect to. And even it is an SSL-based service it can run on 443, 8443 ... whatever. The http_443 monitor has the "Alias" port already hard coded and that´s why shows up to be selected.) The "Alias" setting cannot be changed afterwards. It will be necessary to create a new monitor including the "Alias" setting. Thanks, Stephan
