Pool is up and member is disabled

Hi,

This is by design, not the best approach in my opinion but... You are using Receive Disable String, when it's matched monitor is setting member state to Disabled. This is not the same as Down status when there is not match for both Receive String and Receive Disable String. When member is disabled it is:

• Processing active connections until they are closed or Idle Timeout is over
• Accepting new connections for which there is persistence info related to disabled member

That is why F5 decided that Pool status should be still kept Enabled (green circle) instead of Down or Unavailable.

Personally I would like to have some indication of such state at pool level, but it is as it is right now. Would be nice to have some more advanced logic related to Disabled action initiated by monitor, like checking if member has active connections, checking if VS has enabled persistence and then accordingly mark pool Down. But I guess it could create a lot of overhead so...

You can check as well one of my posts

Member Disabled and persistence without Persistence Records

Piotr