F5 IP-SLA like functions

Found some possibilities here

AskF5 | Manual Chapter: Monitoring BIG-IP System Traffic with SNMP

but those possibilities seem to be TCL scripts you could create to make info available via SNMP polls.

From the same link, it looks like you can create traps and use OIDs from this range:

.1.3.6.1.4.1.3375.2.4.0.300 through .1.3.6.1.4.1.3375.2.4.0.999

Nothing specifically on IPSA...closest I saw was DoS detection.  Unless there is a more current document somewhere listing more possiblilites.  You could always create IPSLA in F5 and then SNMPwalk the F5 and see if the IPSLA can be seen.

Thanks for that. I'd prefer to use an IP SLA, but i can't find any instructions on how to make one. Even going through the Configuration Guide for F5 BIG-IPs, there's no reference to making them, but i've seen other posts online about how they have been made.  Do you know if they're called something different in the F5 world?

You're not looking for ICMP health monitors of load balanced servers are you?  Seeing documentation for that, but not for IPSLA functionality proper.  Not seeing anything analogous to Cisco IPSLA--and no personal experience with that use case.

At this point we'd be fine with just a test that can see if the F5 can ping 8.8.8.8, and alert if it can't ping that.  I know with SAM we could do a Custom Script monitor. But we don't have access the license for that right now. So no, not the ICMP health monitors of the load balaced servers, but if those servers can ping google.com.

Hmmm...you can validate whether F5 can reach an IP out on the internet:

https://devcentral.f5.com/questions/virtual-server-using-external-site-as-pool-member-routing-problem​

iRule to ping host

Can you add 8.8.8.8 as a virtual server and set up a ping health check?  (Wonder if that would respond to pings...)

Not that you would want 8.8.8.8 to receive any load-balanced traffic, but I don't see why you couldn't health-check it:

Virtual Server using external site as pool member, routing problem?