Cisco CSU-2.3-UG Datasheet download pdf (Page 17)

xvii

CiscoSecure ACS 2.3 for UNIX User Guide

78-5222-02 Rev. A0

Upgrading CiscoSecure at Sites with a Non-Updatable Replicated Database

Upgrading from CiscoSecure ACS 2.x to 2.3

Step 9 (Optional) After installation, if you saved your old CSU.cfg file as described in step 3, you can cut and

paste your old settings from your old CSU.cfg file to the new CSU.cfg file to restore your original ACS

debug level, TACACS+ NAS configurations, and supported authentication methods settings. See the

section “Server Control File” in the chapter “Tuning CiscoSecure ACS Performance and Configuration”

in the CiscoSecure ACS 2.3 for UNIX User Guide for a listing of CSU.cfg settings.

Alternatively, you can simply reenter these settings through the new CiscoSecure ACS AAA General and

AAA NAS web pages.

Caution Do not copy the old CSU.cfg file over the new CSU.cfg file. The new CSU.cfg file contains important

new settings specific to CiscoSecure ACS 2.3 for UNIX.

Step 10 (Optional) After installation, if you saved your old DefaultProfile file as described in Step 4, you can use

the CiscoSecure ACS 2.3 CSImport utility to import your old unknown_user default profile settings into

your new ACS installation. Enter:

$BASEDIR/CSimport -c -p /

hold_dir

-s DefaultProfile

where:

$BASEDIR is the directory where you installed CiscoSecure ACS.

hold_dir is the holding directory where you stored the old DefaultProfile file.

Note After you successfully upgrade to CiscoSecure ACS 2.3 for UNIX, you can activate the optional DSM

module. Obtain the CiscoSecure ACS Distributed Session Manager Option product to license and enable

the DSM module. See “Activating the DSM Module on an Existing CiscoSecure ACS 2.3,” page xviii

for details.

Upgrading CiscoSecure at Sites with a Non-Updatable Replicated Database

If you are attempting to upgrade from CiscoSecure 2.x in an existing replication environment and your

environment includes non-updatable sites, when you upgrade the CiscoSecure software on such sites,

you will receive an error message at the end of the upgrade process stating that the installation failed.

This occurs because the CiscoSecure tables that were set up for replication cannot be written to except

by the replication process.

The workaround for this problem is to make sure that you have successfully upgraded CiscoSecure on

your Master Definition site. Ignore the error message received on the non-updatable site(s). When you

replicate, the replication process will update these tables from the Master site.

1 2 ... 12 13 14 15 16 17 18 19 20 21 22 ... 33 34

No comments

Cisco CSU-2.3-UG Datasheet Page 17