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...
Moquery is the command line cousin of Vizore, it's very helpful and efficient sometimes during the troubleshooting. This article aims to provide moquery cheat sheet to the users for some most common seen scenarios.
Here is the checklist before customers/partners contact Cisco TAC:
Firmware Version of APIC and Switch
Download Switch and APIC techsupport logs
Problem description (Symptoms with details)
Business impact (eg, what kind of services...
moquery usageAPIC moquerySwitchmoquery
This document discuss a common issue observed during the VMM integration & VM workload migration to ACI fabric.
VMware Virtual machines are hosted in Cisco UCS-B seri...