you said the csm is not connected to the server vlan. So, you should not configure a vlan 12 on the CSM. Especially if you want your traffic to go through a firewall. Connecting the csm to vlan 12 would be a way to bypass the firewall.
So, what you need is a route on an existing csm vlan to reach the servers via the firewall.
Then, your customer clearly asked to have .51 as a backup of .50.
So you need 2 serverfarms.
One with onle server .50 and one with only server .51.
You then configure the serverfarm .50 with serverfam .51 as backup.
The 2nd would kick in only if .50 is down.
You need predictor leastconn or roundrobin so destination nating can occur.
The 'replicate' commands are used when you need stateful redundancy. They tell the CSM to replicate the information to the standby.
Finally, bridge mode is not related to the ip addresses used for vip and real.
You are in bridge mode when the CSM is configured with the same ip on 2 different vlans. In this case, the CSM will BRIDGE between those 2 vlans.
The only url pointer I could give is the csm documentation guide. You may want to read it through to get yourself familiar with all the possible functions like backup serverfarm or replicate.
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...