DB
Mar 02, 2010Nimbostratus
What happens when LTM marks a node "down"
When my LTM (9.3.1) sees a node in a server pool go down because one of it's two health monitors fails, I would expect the server to no longer have traffic hitting it. However my server guys tell me that this occurance (see log entries below, which happen all the time) are nothing to worry about because during the "down" duration of 5-16 seconds, the server is still getting requests from clients through the LTM. Will LTM continue to send traffic to a node marked "down"?
Mar 1 12:39:11 mvhatp01 bigd[1196]: 01060001:4: Service detected DOWN for ::ffff:1.1.1.1:80 monitor DB_Down_sit-www.foo.com.
Mar 1 12:39:11 mvhatp01 mcpd[1200]: 01070638:3: Pool member 1.1.1.1:80 monitor status down.
Mar 1 12:39:19 mvhatp01 bigd[1196]: 01060001:4: Service detected UP for ::ffff:1.1.1.1:80 monitor DB_Down_sit-www.foo.com.
Mar 1 12:39:19 mvhatp01 mcpd[1200]: 01070638:3: Pool member 1.1.1.1:80 monitor status up.
My pool is setup like this (note that the third member is just a static Maintenance Page):
pool pool_sit-www.foo.com {
lb method member predictive
min active members 1
monitor all sit-www.foo.com-monitor and DB_Down_sit-www.foo.com
member 1.1.1.1:http priority 2
member 1.1.1.2:http priority 2
member 1.1.1.107.107:http monitor none