Monitors determine the availability and performance of devices, links, and servi

ces on a network.
Health monitors check the availability. Performance monitors check the performan
ce and load.
If a monitored device, link, or service does not respond within a specified time
out period, or the status indicates that performance is degraded or that the loa
d is excessive, the BIG-IP system can redirect the traffic to another resource.
To check :
-helth
-performance
-load
Monitors gather information about your network. The information that monitors ga
ther is available for you to view. You can use this information to troubleshoot
problems and determine what resources in your network are in need of maintenance
or reconfiguration.
Methodes of monitoring:
LTM, GTM & Link controller provide 3 methodes of montoring
Simple monitoring:
--Simple monitoring determines whether the status of a resource is up or down. T
he system contains three
--simple monitors, Gateway ICMP, ICMP, and TCP_ECHO.
An active monitor can check for specific responses for configured time period, a
nd run with or without client traffic.
Note: An active monitor also creates additional network traffic beyond the clien
t request and server response
and can be slow to mark a pool member as down.
Each active monitor checks the status of a particular protocol, service, or appl
ication.
-ex: http, wmi etc
Active monitors fall into two categories:
1-Extended Content Verification (ECV) monitors for content checks,
2-Extended Application Verification (EAV) monitors for service checks, path chec
ks, and application checks.
Passive Monitor:
There is only one passive monitor, called an Inband monitor.
Passive monitoring occurs as part of a client request. If, after the specified n
umber of attempts within the defined interval, the system cannot connect to the
server or receive a response, or if the system receives a bad response, the syst
em marks the pool member as down.
A passive monitor creates no additional network traffic beyond the client reques
t and server response. It
can mark a pool member as down quickly, as long as there is some amount of netwo
rk traffic.
Note: A passive monitor cannot check for specific responses and can potentially
be slow to mark a pool
member as up.
bigtop -n

bigpipe pool show, bigpipe node show

tmsh show /ltm pool <pool_name>
tmsh show /ltm node <node_IP>