Forum Discussion
POP3 Monitors fails
On GTM I'm running 10.2.0, the POP3 monitors against cisco load balancer keep flapping Up and Down.
I tried different configuration as below. Notice the time it takes the monitor to success after the failure. it's somehow consistent for each case..
//Interval 20 sec ,Timeout 120 sec, Probe Timeout 5 >>>> Time to success about 16 sec after failure.
Apr 19 12:05:04 local/glb01so alert gtmd[2156]: 011ae0f2:1: Monitor instance POP3-SIDC-vms017 192.168.50.11:110 UP --> DOWN from 192.168.12.144 (state: timeout)
Apr 19 12:05:20 local/glb01so alert gtmd[2156]: 011ae0f2:1: Monitor instance POP3-SIDC-vms017 192.168.50.11:110 DOWN --> UP from 192.168.12.144 (state: success)
Apr 19 12:15:24 local/glb01so alert gtmd[2156]: 011ae0f2:1: Monitor instance POP3-SIDC-vms017 192.168.50.11:110 UP --> DOWN from 192.168.12.144 (state: timeout)
Apr 19 12:15:39 local/glb01so alert gtmd[2156]: 011ae0f2:1: Monitor instance POP3-SIDC-vms017 192.168.50.11:110 DOWN --> UP from 192.168.12.144 (state: success)
Apr 19 12:16:44 local/glb01so alert gtmd[2156]: 011ae0f2:1: Monitor instance POP3-SIDC-vms017 192.168.50.11:110 UP --> DOWN from 192.168.12.144 (state: timeout)
Apr 19 12:17:00 local/glb01so alert gtmd[2156]: 011ae0f2:1: Monitor instance POP3-SIDC-vms017 192.168.50.11:110 DOWN --> UP from 192.168.12.144 (state: success)
// Interval 30 sec,Timeout 120 sec, Probe Timeout 5 >>> Time to success about 26 sec after failure
Apr 19 10:35:31 local/glb01so alert gtmd[2156]: 011ae0f2:1: Monitor instance POP3-SIDC-vms017 192.168.50.11:110 UP --> DOWN from 192.168.12.144 (state: timeout)
Apr 19 10:35:57 local/glb01so alert gtmd[2156]: 011ae0f2:1: Monitor instance POP3-SIDC-vms017 192.168.50.11:110 DOWN --> UP from 192.168.12.144 (state: success)
Apr 19 10:36:31 local/glb01so alert gtmd[2156]: 011ae0f2:1: Monitor instance POP3-SIDC-vms017 192.168.50.11:110 UP --> DOWN from 192.168.12.144 (state: timeout)
Apr 19 10:36:57 local/glb01so alert gtmd[2156]: 011ae0f2:1: Monitor instance POP3-SIDC-vms017 192.168.50.11:110 DOWN --> UP from 192.168.12.144 (state: success)
// Interval 10 sec,Timeout 120 sec, Probe Timeout 5>> Time to success about 5-6 sec after failure
Apr 19 10:53:42 local/glb01so alert gtmd[2156]: 011ae0f2:1: Monitor instance POP3-SIDC-vms017 192.168.50.11:110 UP --> DOWN from 192.168.12.144 (state: timeout)
Apr 19 10:53:48 local/glb01so alert gtmd[2156]: 011ae0f2:1: Monitor instance POP3-SIDC-vms017 192.168.50.11:110 DOWN --> UP from 192.168.12.144 (state: success)
Apr 19 10:54:42 local/glb01so alert gtmd[2156]: 011ae0f2:1: Monitor instance POP3-SIDC-vms017 192.168.50.11:110 UP --> DOWN from 192.168.12.144 (state: timeout)
Apr 19 10:54:48 local/glb01so alert gtmd[2156]: 011ae0f2:1: Monitor instance POP3-SIDC-vms017 192.168.50.11:110 DOWN --> UP from 192.168.12.144 (state: success)
Apr 19 11:07:02 local/glb01so alert gtmd[2156]: 011ae0f2:1: Monitor instance POP3-SIDC-vms017 192.168.50.11:110 UP --> DOWN from 192.168.12.144 (state: timeout)
Apr 19 11:07:08 local/glb01so alert gtmd[2156]: 011ae0f2:1: Monitor instance POP3-SIDC-vms017 192.168.50.11:110 DOWN --> UP from 192.168.12.144 (state: success)
//I Increased the Prob timeout to 20.
// Interval 20 sec,Timeout 120 sec, Probe Timeout 20>> Time to success about 1 sec after failure
Apr 19 15:02:37 local/glb01so alert gtmd[2156]: 011ae0f2:1: Monitor instance POP3-SIDC-vms017 192.168.50.11:110 UP --> DOWN from 192.168.12.144 (state: timeout)
Apr 19 15:02:38 local/glb01so alert gtmd[2156]: 011ae0f2:1: Monitor instance POP3-SIDC-vms017 192.168.50.11:110 DOWN --> UP from 192.168.12.144 (state: success)
Apr 19 15:14:17 local/glb01so alert gtmd[2156]: 011ae0f2:1: Monitor instance POP3-SIDC-vms017 192.168.50.11:110 UP --> DOWN from 192.168.12.144 (state: timeout)
Apr 19 15:14:18 local/glb01so alert gtmd[2156]: 011ae0f2:1: Monitor instance POP3-SIDC-vms017 192.168.50.11:110 DOWN --> UP from 192.168.12.144 (state: success)
//I Increased the Prob timeout to 21.
// Interval 20 sec,Timeout 120 sec, Probe Timeout 21>> Time to success about 20 sec after failure
Apr 19 15:51:48 local/glb01so alert gtmd[2156]: 011ae0f2:1: Monitor instance POP3-SIDC-vms017 192.168.50.11:110 UP --> DOWN from 192.168.12.144 (state: timeout)
Apr 19 15:52:08 local/glb01so alert gtmd[2156]: 011ae0f2:1: Monitor instance POP3-SIDC-vms017 192.168.50.11:110 DOWN --> UP from 192.168.12.144 (state: success)
Apr 19 15:59:48 local/glb01so alert gtmd[2156]: 011ae0f2:1: Monitor instance POP3-SIDC-vms017 192.168.50.11:110 UP --> DOWN from 192.168.12.144 (state: timeout)
Apr 19 16:00:08 local/glb01so alert gtmd[2156]: 011ae0f2:1: Monitor instance POP3-SIDC-vms017 192.168.50.11:110 DOWN --> UP from 192.168.12.144 (state: success)
Any idea?
Thanks
- How is the routing set up between the two boxes? Can you run some simple ping and traceroutes against the host to ensure consistent connectivity between the two? From there you can move on to troubleahooting pop3..
Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com