Over the last month, we've been having some major issues with our ACS. For no apparent reason, it just quits accepting RADIUS/TACACS requests. As you can imagine, our wireless users, as well as our network admins can't sign into wireless, or onto the network devices, due to this. It seems as though the processes fail. I can't even log into the ACS CLI to see which processes fail. The only way around this is to log into the vSphere client, power off the ACS instance, and then power it back on. I'd like to log into the shell, to see if we're having file system issues with directory sizes, etc. How can I log into the shell, from the CLI, to see the directory structure? I remember when I was upgrading from 5.2.x to 5.3.x, I was able to get into the shell, but can't for the life of me remember how. Can anyone shed any light on this? Thanks!
We have configured the outside and inside Interface with official ipv6 adresses, set a default route on outside Interface to our router, we also have definied a rule , which also gets hits, to permit tcp from inside Interface to any6.
In Syslog I also se...