GTM - Lingo translated from an LTM perspective (and monitoring)

I'd like to add some info on generic-host [non-F5 product] monitoring.

Generic host - it's an object, representing some device which can host services [virtual-servers]. It's like a container for non-F5 virtual-servers.

Prober pool - an ordered list of F5 GTM devices that determines where probes are sourced from. It is also a way to create redundancy for probing. (there are many other scenarios, that's just one of them)

Guidelines I use when working with generic-hosts:

1. If you create a new data-center, always assign a prober pool to it. Choose the closest one to your generic-host server among available. If you don't, all F5 devices (LTMs, GTMs) within the data-center hosting that generic-host server will start sending probes to virtual-servers hosted by it. This will ultimately cause firewall drops / monitor flaps / chaos.
2. Make a generic-host server inherit prober-pool from the DC.
3. Do not assign monitor to a generic-host server. We are more interested in status of virtual-servers rather then a box itself.
4. Assign monitor to ALL virtual serves which are “hosted” by generic-host server . Choose the monitor based on application type running.
5. Always adjust firewall rules so that ALL GTM’s in your prober-pool could reach your virtual servers.
6. When building a GSLB pool, there is no need to apply any monitors to a pool consisting of virtual-servers, which are hosted by a generic-host server. It will be automatically marked red/green based on virtual-servers' state.

This approach allowed me standardize / simplify my work with generic-hosts.

Cheers