ACE module (on C6509) is currently configured to support client/server connections to several application servers.
VIP#1 on ACE exists within a single client side subnet (int vlan111)
Real servers exist on a separate server side subnet (int vlan555)
ACE is configured with a single default route pointing to a router on the client side subnet (int vlan111)
Customer wants to add a new VIP#2 that will exist on a new client side subnet (int vlan222)
Customer wants this new VIP#2 to be load balanced to the same application servers, exactly the same as VIP#1.
The problem I suspect is that the ACE's existing default route (via int vlan111) will cause all VIP#2 server-to-client traffic flows to be forwarded via int vlan111 instead of int vlan222 and thereby break the VIP#2 server-to-client traffic flows.
Assuming I'm correct, is there an ACE based solution to this, or is this desired environment just not possbile.
NOTE: since both VIP#1 and VIP#2 clients will be any public IP addressed hosts, I cannot define multiple routes based on discrete destination network addresses; therefore a single default route is all that's possible to use.
A static route and your problem is solved. Worked for me back when I had to redesign my public facing webportals. I basically had three different subnets, each containing 15-20 VIPS that had to be consolidated onto one ACE-context. And my challenge was the excact same.