How do you carve up your allocations for each vACE (context) - 4710
I've been looking into the most efficient way to carve up the allocations (in the resource-class's) for each context in a multi-tenanted environment.
I've been looking at deploying a resource-class per context. Each resource-class would allocate all resources at 20 to 30%. Within each context under the rserver I would rate-limit the bandwidth and connections to meet the requirements. And all other resources would be monitored. By having a resource-class per context allows you to increase or decrease resources should this be required depending on load.
What are your thoughts? Or would you create a context and allocate each resource a percentage based around the design requirements? For example, context B, requires 10Mb through put, 20,000 concurrent connections etc...
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...