disabled virtual server continues to serve - apparently!

By default, TMM will keep a connection open as long as neither the client or server close it and it's actively used before the TCP idle timeout expires. 300 seconds for an idle timeout is fairly high for production HTTP virtual servers. If your servers respond reasonably quickly to requests you could probably lower this.

 

 

Regardless, the idle timeout isn't really the issue here. If you disable the virtual server a client could continue sending requests over the same TCP connection as long as the server doesn't close the connection and they each request before the idle timeout expires. I think the simplest and most efficient solution for this is to delete the connection table entries after you disable the virtual server. If that's not appealing, you could try the iRule approach I outlined above.

 

 

If you think it would be useful to have an option to disable a virtual server, pool or node with active connections deleted automatically you could always open a case with F5 Support and ask them to consider a request for enhancement.

 

 

Aaron