Testing monitor fails if monitor exist?
Hi! I recently started working with F5 and tmsh, and I'm having problems with a monitor. - The monitor and node are in the same partition. - The node is a fqdn node with 2 ephemeral ips (auto populate). - The monitor finds the URL Available, but the IPs are Offline. I already checked with curl and with ncthe IPs (as described in https://support.f5.com/csp/article/K81239024) and they respond 200 to the "Send String" The only test I'm missing is the monitor configuration test (https://support.f5.com/csp/article/K60677941and https://support.f5.com/csp/article/K13522220) but both gives an exception:"The requested monitor instance ... already exists". Is this an F5 bug or i'm missing something? Are other ways to test and understand why the monitor is failing to recognize the IP is Available? Edit: The original problem was solved. The auto populate node gets a ICMP monitor by default, even when you are setting a HTTP monitor. Behind the node was kubernetes and it didn't have ping enabled, so it failed. You can change the type of monitor in the Properties tab of the fqdn node, using "Node Specific" in "Health Monitors" The original problem is still unsolved. Why the test to check the configuration of the monitor fails with "The requested monitor instance ... already exists"?
Is it possible to Split Test ASM Policies?
Hi Guys, Is it possible to split test 2 asm policies? I know I cannot add more than 1 asm policy to the virtual server object, however I was wondering if it's possible in other way. One consideration that I had that is to create a second ASM policy to this one. Then to use a layer 7 policy on the LTM to direct the majority of traffic to the known and trusted policy and a small amount of traffic to the new stricter policy. Is there a better way to do this? If there is no other way to do this, would the method described above work? I'm using Ver 12.1.1 - are there new features I am not seeing that might allow for this? Thank you