by "intelligent ISP load balancing" I mean routing toward the two isps with load and delay in "mind", either for inbound and outbound connections.
What the "other" boxes do is to become an authoritative dns that distribute dns records in such a manner that the client requests will be load balanced across the two isps, but not in a round-robin fashion, rather using some sort of a "busy check".
However each internal service is bound to as many VIPs as the ISPs involved in the dance.
It doesn't matter if the return path is the same as the inbound one, as long as the path is the best one in that precise moment (at least up to the isps networks).
Do you think the CSS can do a work like that?
About the cpu issue, is there some rule in order to calculate the model in function of the bandwidth available?
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...