I try to free some memory on a ACe module because I get the resource in use message.
I spotted 2 contexts with the default RC, however when I try to assign a resource class with a lower percentage to these contexts I get the "Error: resouce in use" message even though these RC have a lower resource allocation.
Did anybody come accress this situation and fixed it?
The default resource class allows a context to operate within a range that can vary from no resource access (0%) to complete resource access (100%).So there is no guaranteed minimum reserved by default RC.
If you are assigning a RC that guarantees x% resource (x might be a small amount but it tries to reserve some % of resource for that context) and there is no resource available to allocate then you will get this error.
As resources are allocated the minimum value is tallied to prevent oversubscription of guaranteed resources.
Show resource usage all command will give you a clear picture of available and allocated resources.
Do you have any other RCs configured and currently in use by other contexts? If so, the total RCs in use should not exceed 100%.
For example if you have two RCs configured each of 45% and both allocated to contexts, this means you have already allocated 90% of your resources. You cannot in this case create a new RC of 20% and allocate it to another context, as it exceeds the RC allocation available.
I hope that helps. If not, please provide more details as to the number of RCs you have configured, the percentage allocations per RC and the RC allocation per context.
limit-resource all minimum 5.00 maximum equal-to-min
i know i'm "short" of memory there but how could I resize the memory allocation if the command to allocate less memory does not go through.
I guess in order to assigne that Rc to the context i should have at least the same percentage of free memory as the percentage I want to allocate to the context.
Looks like the only way to change this is to configure a more detailed memory allocation wihtin the RC (syslog, bandwidth, acl, ...) so I would assign less memory to various resources within the context.
But then again, I guess the fact that I ran out of memory will prevent me from changing the existing resource allocation. sounds to me like a dead end at this stage.
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
In the Previous articles of ACI Automation, we are using Postman/Newman as the Rest API tool to automate the ACI Configuration.
In this article I’m going to discuss on usin...
One of the first steps in building your ACI Fabric is to go through Fabric Discovery. While Fabric Discovery is usually a straightforward process, there are various issues that may prevent you from discovering an ACI switch. This article wil...