Kenan,
this is even worst if we access the vip from the same subnet as the server.
What is happening is that client C connect to the vip V.
ACE loadbalances the request rserver R1 which responds to client C.
Since R1 and C are on the same subnet, R1 does not have to go through the ACE and instead it goes directly to C.
So, C receives a response from R1.
But C sent a request to V and therefore does not expect a response from R1.
You get a connection failure and a RESET.
You need to force the traffic from the server to go through the ACE.
With your initial design in bridge mode, it was mandatory for the servers to go through ACE.
In one-armed the servers will just bypass ACE.
I don't even see how your SIP loadbalancing can work.
You can do client nat to make it work.
But client and NAT is not a good idea with the ACE - too many problems that will only be addressed end of this calendar year.
Therefore I would suggest to go back to a bridge design or a routing mode.
But it is mandatory to have the servers on one side of ACE and the client on the other side if you want to keep it simple.
The other option is policy-routing or client nat.
Gilles.
