Why configure L7 monitor in GTM for PCF applications load-balancing
I came across a GTM-LTM-GoRouter setup, where a common set of GoRouters are the pool-members for all the LTM VIPs and are monitored with TCP (L4) monitor. Whereas, GTMs which are configured with the FQDNs of the various applications have the VIPs of these LTMs as pool-members. However, as a monitor a HTTPS (L7) monitor is deployed. I am not sure why we have this kind of setup. Is it something needed for the PCF kind of deployment?
Create HTTPS Pool Monitor on LTM using Ansible
My team recently started testing Ansible functionality for building objects on our F5 LTMs. Part of the process that we would like to automate is the creation of pool monitors. I can successfully create HTTP and TCP monitors using the bigip_monitor_http and bigip_monitor_tcp modules but am having problems creating an HTTPS monitor. At first I thought I could use the bigip_monitor_http module and just set the type and parent options to https but the module doesn't appear to support an option for type and if I try to set parent to https, it fails since the parent doesn't match the monitor's default type which is http. Trusty google didn't seem to provide any help and I don't see a bigip_monitor_https module in the Ansible documentation. My guess is that this functionality is not supported based on the available modules/options in Ansible but I wanted to verify before I proceed with going down a different path.
HTTPS monitor suddenly stopped working. http works fine on same nodes. what could cause this, newbie here
I have a customer environment where the HTTP monitors are just fine, but the HTTPs monitors have suddenly stopped. it is using the default https monitor and the monitor is operating correctly on other https nodes. that seems to me that that would be on the customer side since the only thing specific about it is the individual node itself on port 443. if it was a monitor issue, especially a default one, it would seem the issue would be spread further. Does anyone have any insight to simple issues this could be or is everyone of the same mind that this looks like a customer side issue?
