Looking at the output it seems device is running out of resource. Please use "show resource usage" and see if you have denied counter increasing. Please see current and peak connections and see if they have hit the max limit.
You might have to increase the resource for management of the device.using "limit-resource mgmt-connections".. You have to make that change in "Admin" context and since you can access Admin context you can give it a shot.
Thanks for your reply, but it doesn't work. I can't even see resource usage:
ACE1/Admin# sh resource usage
Error: Transport error
Maybe after I reset the ACE I'll see something, but as I mentioned in previous message, ACE works relatively long time after hardware reset. And regarding increasing resources for mgmt - actually there should be no mgmt connections at all, we log in only when we have to reconfigure load balancing.
A quick search internally regarding "Transport error" reveals that this error usually comes while configuring FT or some process related to it has shut down. But in your case you are unable to even execute basic show commands. It seems that we have no choice but reload to come out of this situation but i would also recommend opening a TAC case and get this investigated if you are facing this issue again and again. May be there is a known bug in a version you are running. I see some bugs here but cannot match symptoms exactly like you are facing.
Also, regarding the resource utilization if you haven't allocated a dedicated resource to management, then it means that if a resource is free you will be able to manage the device and if it is not , since it is being used by other traffic you will not get access. That's why it is always a good idea to have some dedicated resource allocated for management. We have seen this issue. Even a single connection to ACE would be denied or not work if ACE has no free resource.
When processing large configurations, subsequent commands may encounter an "API timeout" error, until the processing ends. The way to know when the processing ends is to perform a "show processor cpu" and verify that the load has reduced to low single-digits, or 0. The queue stall messages are harmless, unless they do not stop appearing.
Unfortunately i don't see any workaround to this problem and it is suggested to let the process complete and it should go away. If it doesn't then i would suggest opening a TAC case.
You might also consider to upgrade your device to latest code as the version you are running is pretty old.
Introduction This article will help you understand the steps on how to
download the UCS licenses from the Cisco Systems website and then
installing it on the UCS. The redacted (blue lines) just covers up
certain numbers for privacy please do not take them...
Introduction This article will help you understand and educate the
customer on how to clear their "expired licenses"
(license-graceperiod-expired) from their UCS-M. If a customer just
purchased a license and needs a step by step guide on how to download
Introduction Prepositioning is a powerful tools on the WAAS platform but
it is not always easy to figure out why your jobs are failing when
trying to retrieve the files.Here is a method that should help you to
figure out the reason why they are not succes...