Has anyone ever seen this in the TCS log on an ACS 3.0 NT box?
TCS 01/13/2003 15:38:05 A 1672 0081 Note: The maximum 40 sessions are busy. If the system is consistently under load you may wish to increase the number of sessions. (This is a registry configurable setting SOFTWARE\Cisco\CiscoAAAv3.0\CSTacacs\MaxSessions. The service will need to be restarted for the change to take effect.)
ANy pointers would help! What is the max value of this registry entry? 255?
Yep, seen this many times on a busy server. Basically the default number of threads the CSTACACS service gets is 40, which basically means there can be 40 outstanding sessions (authentication, authorization or accounting) going on at any one time.
I would double it first off and see how you go. Also, if you're using single-connection, take that off cause that holds open connections (threads) for a long time.
Hmmm, can't say I've seen that before. Did a searhc of old cases for "server too busy" and didn't find anything either, so doesn't look like it's to common. Just looking at it though it looks to be related to the similar problem you were having with the CSTACACS process.
There's similar registry keys for the CSRadius process under the same registry location (although replace CSTacacs with CSRadius), you could try changing AuthThreads and AcctThreads to something higher and see how that goes. Would it be possible that you have more than 50 Radius srequests coming in at once though? If not, then it's probably not necessary to do the registry fix and we'll need to look elsewhere.
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...