Virtual Server responds to TCP request

There's a little bit more to add to this discussion - what you're dealing with here is a standard virtual server type. Because of this you're seeing the LTM full proxy in its full glory. On a standard VS, BigIP will always respond with a handshake on the client side. Only when you push data will you get a reset - that's because the LTM is now trying to send data to the server side of the proxy and there's nothing listening behind it.

 

 

One way to accomplish what you're after iis to take advantage of what we know of the BigIP profiles: the fastl4 profile is 'packet based', and it'll attempt to send packets on to the backend immediately; therefore it'll throw your reset immediately. In other words, a performance l4 profile essentially disables the LTM's full proxy for that specific virtual server.

 

 

Now, you may not find this desirable - after all, when you go with a packet-based VS you're sacrificing a ton of functionality. If this is the case, you could always stand up a parallel VS on a different port and have your customer hit that VS as their failover test.

 

 

I hope this makes sense, and more importantly I hope it helps.

 

-Matt