When using a single CSS11503, can the loadbalanced server default gateway be configured to route traffic to a router rather than the CSS inside interface? Most of the documentation suggests using the CSS inline to the traffic flow, are there options for 'on a stick' deployment.
Can the same solution be used if a pair of CSSs switches are configured for stateful failover, or do the CSSs need to record inside and outside traffic for stateful failover.
Can you provide information for configuring the CSS on a stick? so that the CSS is not a bottleneck?
Re: CSS deployment - server default gateway options
the CSS requires to see both side of a connection even if you don't need statefull failover.
There is no option for Direct Server Return (DSR).
You could have a different gateway on the server, so most of your traffic goes via the router, and then you need to use a client nat pool on the CSS so the server thinks the client is locally attached and respond to the CSS without going through the default gateway.
Only drawback is that the server will see connections coming from only 1 ip.
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...