Forum Discussion
AltocumulusWhy doesn't GTM poolmember monitor alert show where probe came from?
Most monitor alerts include the IP address of the device that performed the probing. In the example below you can see that GTM delegated to the prober at 52.40.245.229, and it reported back with a failure.
Apr 9 00:55:46 10.5.32.15 Apr 9 00:55:46 denbip2000gtm01 alert gtmd[14902]: 011a4003:1: SNMP_TRAP: Pool /Common/my.example.net member my_example_net_https_vs (ip:port=1.2.3.4:443) state change green --> red ( Monitor /Common/https_ecomdb_keepalive from 52.40.245.229 : connect: protocol mismatch search result false) host = 10.5.32.15 source = udp:514 sourcetype = syslog
But in some monitor alerts the probe source is not shown. Notice in the example below it only shows "from gtmd". Does anyone know what that means?
Apr 6 07:50:31 10.34.32.15 Apr 6 07:50:31 thwbip2000gtm01 alert gtmd[14695]: 011a4003:1: SNMP_TRAP: Pool /Common/token.example.com_lgt member token_example_com_lgt (ip:port=5.6.7.8:443) state change green --> red ( Monitor /Common/token_https from gtmd : state: timeout) host = 10.34.32.15 source = udp:514 sourcetype = syslog
3 Replies
Kevin_Davies_40Nacreous
GTM delegates monitoring where possible. If the server is a BIGIP it will defer to the monitoring provided by the LTM. When server is not it will delegate its monitoring to a BIGIP in the same data center. When GTM is initially setup, big3d software is installed to each BIGIP. GTM sends out monitoring requests to that software which then monitors non BIGIP servers on its behalf. If this is not available then finally GTM will do the monitoring itself. I suspect thats what you are seeing in the logs is monitor requests coming from GTM.
Brian_10532Is there any way to figure out which GTM did the monitoring? We have 4, so it is kind of ambiguous to just say GTM.
- Kevin_Davies_40
I dont know of any way.
