Our security guy that works with our ACS boxes has gone home for the day, so I won't be able to give you a bug ID, but we hit a bug in ACS 5.3 that sounds exactly like what you are describing. If the custom attributes field contained certain values it would barf. I'll post the bug id in question tomorrow if someone doesn't get it up before.
TAC said a patch was imminent, but to roll back to 5.2 if we had to have it up before the patch hit. Hope this helps and isn't a red herring. -Luke =-=-=-=-=-=-=-=-=-=-=-= Luke Jenkins Network Engineer Weber State University On Feb 21, 2012, at 5:22 PM, Nelson, Edward wrote: > Hello, > > We're in the process of migrating from Cisco WCS to NCS and are having an > issue getting tacacs+ configured on the NCS using TAC Plus. It appears that > it may be an issue with "service = " setting in TAC Plus. With the WCS and > TAC Plus configuration, service was set to "Wireless-WCS". Using both this > and "Wireless-NCS", we can't seem to get it to work. The configuration > includes the proper tasks for role0=Admin and checked all of the usual things > like communications between the server running TAC Plus and the NCS appliance. > > Has anyone successfully configured TAC Plus with Cisco NCS? Any suggestions? > > Thanks, > Ed > > -- > Edward R. Nelson > Sr. Network Services Engineer, Information Services & Technology > Boston University > T (617)353-8271 > F (617)353-6260 > [email protected] > http://www.bu.edu/tech > > ********** > Participation and subscription information for this EDUCAUSE Constituent > Group discussion list can be found at http://www.educause.edu/groups/. ********** Participation and subscription information for this EDUCAUSE Constituent Group discussion list can be found at http://www.educause.edu/groups/.
