Upgrade ACS 3.1.1(27) to 3.2

[ED CARMODY]

Hello,

I've a customer that needs to upgrade their existing ACS to 3.2.

This is a high-volume production environment, providing TACACS+, LEAP & MAC address authentication for WLAN, and dial-up VPN authentication with a redundant offsite ACS pulling its configuration database from the primary ACS. Another vendor set up the two ACS's, but my company is supporting them now...

What I need to know is if I can upgrade from 3.1.1(27) to 3.2, and maintain all configuration databases completely. Are the configuration databases compatible? Release notes for 3.2 show that upgrading from 3.1.1(28) is supported, but the customer is one build level below that, so they're not explicitly supported, and this makes me worry.

I have a fair amount of experience with ACS, but I've never dealt with database replication issues before, and have never upgraded an ACS server. Customer claims they are doing one-way database replication from the primary to the backup. Is there any order in which I should upgrade the boxes?

Any help is greatly appreciated.

[drolemc]

To the best of my knowledge, an upgrade from 3.1(1)-27 to 3.2 should be possible. To upgrade the ACS without loosing the configuration or the database, see the procedure outlined at http://www.cisco.com/univercd/cc/td/doc/product/access/acs_soft/csacs4nt/acs32/win32sig.htm#wp9934. You should also have a look at Q11 in the QandA document at http://www.cisco.com/warp/customer/480/csntfaq.html#Q11