Forum Discussion
ST_Wong
Cirrus
Jul 28, 2009Pls help: monitor status flips
Hi all,
We're using BIG-IP 6400 (BIG-IP Version 9.4.7 320.1). We defined pools for all nodes' port 389 (ldap) and 0.
Each node is monitored by gateway-icmp. ldap pool members are monitored by ldap monitor while the "port 0" pool is monitored by gateway-icmp.
Although the services work properly, we note that in /var/log/ltm, monitor status flips regularly without marking the service status up/down respectively, e.g.
--------------- cut here ------------
Jul 28 17:05:47 big6 mcpd[1831]: 01070638:5: Pool member 192.168.18.95:0 monitor status down.
Jul 28 17:05:47 big6 mcpd[1831]: 01070640:5: Node 192.168.18.95 monitor status down.
Jul 28 17:05:47 tmm tmm[1759]: 01010028:3: No members available for pool caa4-pool
Jul 28 17:06:04 big6 mcpd[1831]: 01070638:5: Pool member 192.168.18.95:389 monitor status down.
Jul 28 17:06:12 big6 mcpd[1831]: 01070727:5: Pool member 192.168.18.95:389 monitor status up.
Jul 28 17:06:16 big6 mcpd[1831]: 01070727:5: Pool member 192.168.18.95:0 monitor status up.
Jul 28 17:06:16 big6 mcpd[1831]: 01070728:5: Node 192.168.18.95 monitor status up.
--------------- cut here ------------
I wonder if there is problem with our monitor setup. Would anyone please help?
Thanks a lot.
- dennypayne
Employee
Did you edit the default interval and timeouts on the monitors? I've found that anything much below the default of 5 seconds for interval and 16 seconds for timeout can result in nodes flapping up and down. - ST_Wong
Cirrus
We use default only and don't change the interval setting. - Tarek_89626
Nimbostratus
Hey man,
Recent Discussions
Related Content
DevCentral Quicklinks
* 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
Discover DevCentral Connects