I'm trying configure and test proximity based responses on the GSS (v3.2) and I'm having trouble understanding how the decisions are being made. As far as I can tell, it doesn't seem to be working. For the test, I've configured three websites at three locations, one in the western US, one in the eastern US, and one in Hong Kong. I also have DRP agents running on internet edge routers at each location. The GSS is located at the EasternUS site, and is configured to probe all three websites for status. I'm trying to use http://whatsmydns.net to verify that the proximity rules are working, but it seems like the same answer keeps being sent out to all of the sites, regardless of location. First I noticed that all three answers were being used in order, and once I changed the balance method from round-robin to ordered list, that behavior went away. But now, even though I can observe the DRP queries being processed at each router, I'm not seeing the DNS requests going to the server I think it should.
I've been reading these docs during my setup, so I feel like I'm doing everything right -- can anyone help shed light on the odd results?
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...