Cisco Application Deployment Engine OS Build Version: 188.8.131.52.
Cisco ACS Version 184.108.40.206.
Unfortunately, turning on debug-log hasn't shown anything useful neither during 20sec delay, nor after it. Though, I might have done something wrong. I'll try logging via console.
If it can give any hint: when I press Ctrl-C during delay, I get the following message: "Your ACS config session has failed. It is possible that you have exceeded the maximum number of allowed ACS config CLI sessions. Close any open sessions and try again."
Hmmm, your "hint" reminds me of behavior I have seen in network devices where there was an automated system logging into - and not properly terminating sessions with - devices' vty lines. It ended up exhausting the available vty lines and one could not log in remotely until they had timed out.
Session idle timeout for ACS however is configurable at the lower end at 5 minutes. So that doesn't correlate to the 20 second behaviour you are seeing.
Does the GUI present this anomaly as well?
TAC would probably suggest upgrading to the current release (ACS 5.3) but I don't see any resolved caveats that allude to the behavior you are seeing.
Hi everyone, I would like to thank you in advance for any help you can provide a newcomer like myself!
Im studying the 100-105 book by Odom and am currently on the topic of Port security. I purchased a used 2960 and I'm trying to follow a...
While deploying a number of 18xx/2802/3802 model access points (APs), which run AP-COS as their operating platform. It can be observed on some occasions that while many of their access points were able to join the fabric WLC withou...
I am going to design and build an LAN network under a tunnel underground with long distance between the switches.
I will have 2 Catalyst switches and 8 Industrial IE3000, and they will be connected with fiber.
For now I am planning on use Layer-2 s...