Usually, people use virtualization when a context represent one customer or organization and you want to really separate them. They can't see each other configs. They are allocated resources so they can't deplate all resources for the box....
When playing with context, you need to find the correct parameters for resource allocation. Not enough resource and we will drop traffic... too much resource to one context then you don't have enough for the others.
Playing with virtualization is not easy and there is no magic solution that works for everybody.
You really need to understand the advantages and disadventages and see if it is what you need.
If you don't see what benefit you will get, then you should probably not use virtualization.
we're building a new DC and have the servers that would need to be load balanced in 3 separate DMZ's - Internet, Extranet and Intranet. Would this be a good situation for virtualizing the ACE and creating 3 separate contexts, one for each zone. Also, when we allocate the resources for each context, are they etched in stone or could be changed later on the fly as needed.
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...