My first guess is that even though you can ping your VIP and services show as 'Alive' you are not getting anything back when you attempt to connect through the VIP address. I ran into this same problem when I tried to load-balance servers in the same subnet as the clients who would be connecting.
If I understand the CSS correctly, when a request is received from a client, it passes it on to one of the service hosts with the source information intact. This means that from the perspective of your server, the request is coming directly from the client. When the VIP and the servers are in the same subnet, you have to fool the servers into thinking the traffic originated from the CSS -- this is because for proper load-balancing, you have to have two-way traffic through the CSS. Whatever traffic hits the CSS needs to go back through the CSS to the client. You can do this using a 'group'.
In your case, you would define a group as follows:
vip address 172.18.12.25
add destination service www-Apps1
add destination service www-Apps2
This config makes all traffic appear as if it was sourced from the CSS, so the traffc flow goes client -> CSS -> server -> CSS -> client.
Topology & Design:
Two ACI fabrics
Stretching VLANs using OTV
Both fabrics are advertising BD subnets into same routing domain
Some BDs(or say VLANs) are stretched, but some are not.
Endpoints can move betwee...
VMware Trunk Port Group is supported from ACI version 2.1
VMM integration must be configured properly
ASA device package must be uploaded to APIC
ASAv version must be compatible with ACI and device package version
Topology &Design:Traffic flow within same fabric:Endpoint moves to Fabric-2Bounce Entry Times OutTraffic Black-holedSummarySolutionAppendix:
In the Previous articles of ACI Automation, we are using Postman/Newman a...