I am fairly new to content switching. I have a relatively simple requirement ... I need some type of front-end to a farm of Web servers. The front-end should load balance and be aware of back-end failures. It should also be highly-available itself, and be accessible by a single ip address (a la HSRP).
Is a content switch overkill for this application ? Caching is not very important, but high availability is.
Is there a better tool? I suppose NAT can be used, but there are other issues with that.
Yes, if you have a 6500 code (12.2 13E) you can use ip slb in dispatch mode with out having to buy cisco CSM or CSS. with dispatch mode you create a serverfarm and enter the real ip of the server part of the server farm. second you specify a VIP address for the server farm and also do nat server option. you must also perform loopback interface with the vip address on the server farm.
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...