In CSS platform is was possible to have real servers configured several hops away from CSS itself, so traffic to them from CSS would be routed over the network. In this case we of course had to use Source NAT to force the returning traffic back to CSS.
I tried to do the same thing on ACE and was surprised to see that ACE reported ARP_FAILED condition for rserver and it obviously never came up. Is this ACE limitation to have rserver reachable through Layer2, so ACE can use ARP to rservers, or is there a way around it?
Rserver config is pretty simple and I do not see any option for that....
The idea behind it is that we can use one VLAN for Virtual IPs and loadbalance between various servers located on our LAN, but not on VLANs going through ACE, so no ARP to rservers from ACE would be possible in this case. ACE would get the traffic to VIP, NAT destination and source and send the traffic to rserver over Layer 3 routed network (only 1 or 2 hops away).
BTW, is CSM having the same "limitation" as ACE (if it is really limitation) or is it like CSS?
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
In the Previous articles of ACI Automation, we are using Postman/Newman as the Rest API tool to automate the ACI Configuration.
In this article I’m going to discuss on usin...
One of the first steps in building your ACI Fabric is to go through Fabric Discovery. While Fabric Discovery is usually a straightforward process, there are various issues that may prevent you from discovering an ACI switch. This article wil...