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 nc the 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/K60677941 and 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"?
You can try connecting another monitor to the computer to test it against the monitor in question. Use the same cables your monitor used, connect only the new monitor to the computer and reboot the computer to test it. If the new screen turns on and works correctly, your monitor is likely blown.
I beleve that's impossible. If I try to create another monitor in another partition with the same name fails ("monitor already exists").
Anyways, that's not the problem. The tests shouls expect a monitor acording to documentation, but it fails bc it founds it
Better also check your version in the bug tracker and software release notes if it is having a bug for FQDN nodes.
example release note:
The "The requested monitor instance ... already exists" could be cosmetic as https://cdn.f5.com/product/bugtracker/ID726319.html or related to the issues