Forum Discussion
Tiaan_92076
Nimbostratus
NimbostratusWhen does PERSIST_DOWN fire
Is the PERSIST_DOWN event supposed to be triggered when a node is disabled or only when a monitor marks a node as down ?
PERSIST_DOWN is triggered when LTM is ready to send the request to a particular node or pool member via persistence and it has been marked down. This is usually because the server has been detected as unreachable (when no route to the target exists) or non-responsive (failed to respond to a connection request).
hoolioCirrostratus
Hi Tiaan,
Have you tested and found a problem? If so, could you elaborate on what you configured, tested and found?
As you quoted from the wiki page, I think PERSIST_DOWN will be triggered if the selected pool member has been "marked down". If a node is disabled, it will still accept requests from clients with a valid persistence record. So I wouldn't expect the PERSIST_DOWN event to be triggered. If the pool member is Forced Offline (Only active connections allowed), then I would think the event would be triggered.
Also, note that the solution describes a known issue with the triggering of this event:
PERSIST_DOWN is not triggered on failed persistence when cookie persistence or MSRDP persistence is the configured persistence method. F5 Product development is tracking this issue under CR104960 (SOL9115).
Aaron
Tiaan_92076I tested both disabling and forcing a node down, the PERSIST_DOWN does not fire in either case. I did not test if it fires when the node/member is marked down by a monitor though.
Thanks
Tiaan- hoolioEither the wiki is wrong or it sounds like there is a bug. you could open a case with F5 Support to determine which it is. If you can post back here with what you find, it would be helpful.
Thanks,
Aaron - Tiaan_92076Tested when the node/member is marked down by a monitor as well, the PERSIST_DOWN never fires.
Opened a case with F5 support.
Tiaan - hoolioWhich persistence method are you testing with?
Aaron - Tiaan_92076I'm using "Source Address Affinity"
Tiaan