Migrating ACS 3.1.1 to ACS 5.1

[hogoqo]

I am migrating from ACS 3.1.1, which is not supported by the Migration Utility. So i am planning on importing the users and groups manually using the CSV files. I have generated a dump of the database using the csutil. My question is, How can i import the existing user passwords? I know when using the Migration Utility it migrates the internal user passwords as well. Anyone with an idea?

[Federico Ziliotto]

Hello,

Maybe the easiest/safest way would be to go through a TAC case to request assistance on upgrading your ACS 3.1.1 up until ACS 4.2, which is then supported by the migration utility:

http://tools.cisco.com/ServiceRequestTool/create/launch.do

Alternatively, if you are able to put all your users info in a CSV file, you could follow the instructions to import users in ACS 5 through CSV files:

http://www.cisco.com/en/US/docs/net_mgmt/cisco_secure_access_control_system/5.1/user/guide/net_resources.html#wpxref47311

For information on how to create the import files:

http://www.cisco.com/en/US/docs/net_mgmt/cisco_secure_access_control_system/5.1/sdk/cli_imp_exp.html#wp1055255

Regards,

Fede

--

If  this helps you and/or answers your question please mark the question as  "answered" and/or rate it, so other users can easily find it.

[hogoqo]

I have used teh CSV templates already and migrated the users. I need to maintain their passwords though. I need the migration to be seemless to teh end user. Any way of decoding the passwords from the dump file and manually input them on the CSV file for import.

[Federico Ziliotto]

Hello,

For security reasons, ACS 4.x has been designed to encrypt users passwords and there are currently no options to disable such an encryption.
The users list CSV dump obtained through the CSUtil command was implemented with the goal of generating a backup of the ACS users, but not to allow passwords to be read or modified for example.

At this stage, in case you could not change passwords for your users, it might be easier to proceed with the ACS 3.1.1 database upgrade to 4.2 (this can be done for example on a separate server) and then with the migration to ACS 5 through the corresponding utility:

1. Install another ACS 3.1.1 on a separate secondary Windows server.

2. On this secondary ACS, restore a database backup from your original ACS 3.1.1.

3. Upgrade the secondary ACS 3.1.1 all the way to 4.2 (you'd need to open a TAC case to obtain all the needed software releases).

4. Use the migration utility of ACS 5 to migrate the database from the secondary ACS, now upgraded to 4.2 and compatible with the migration utility.

Regards,

Fede

--
If  this helps you and/or answers your question please mark the question as  "answered" and/or rate it, so other users can easily find it.