Table Of Contents

Migrating from CiscoWorks Classic to CiscoWorks

Identifying Fully Transitioned Features

Identifying Partially Transitioned Features

Identifying Non-Transitioned Features

Migrating from CiscoWorks Classic to CiscoWorks

---

This appendix provides information about how CiscoWorks features and functionality are transitioned to services provided by the CiscoWorks Server:

•Identifying Fully Transitioned Features

•Identifying Partially Transitioned Features

•Identifying Non-Transitioned Features

---

Note Additional CiscoWorks Classic features may be provided by other CiscoWorks applications. To find information on migration for other application suites, refer to the migration section in the user guide for a specific CiscoWorks suite.

---

When replacing CiscoWorks Classic with CiscoWorks, consider that the CiscoWorks Server does not provide data migration from CiscoWorks Classic (see Table A-1).

Table A-1 CiscoWorks Data Migration 

CiscoWorks Data	Migrated?	Comments
AutoInstall	No	You can perform autoinstall manually, as described in IOS documentation.
Domains	No	Device Views provide equivalent functionality.
User- and application-level security	No	Security data is not migrated.

Identifying Fully Transitioned Features

Table A-2 shows the CiscoWorks features that are fully transitioned to the CiscoWorks Server.

Table A-2 Fully Transitioned Features

Feature	CiscoWorks Feature	CiscoWorks Server Feature
Application Help	Allows keyword and full-text searches.	Context-sensitive online help allows keyword, full-text, index and search.
cw_backup and cw_recover	Backs up and restores CiscoWorks database.	Backs up database from navigation tree and restores from command-line scripts.
Login/Logout	Performs single generic login and logout.	Administrative login and logout and a five-level user security system.
Process Manager	Displays CiscoWorks daemon status and start or stop processes.	Provides start and stop process options, and process status details.
Tool Box	GUI for starting CiscoWorks applications.	Navigation tree.

Identifying Partially Transitioned Features

Table A-3 shows the CiscoWorks features that are partially transitioned to the CiscoWorks Server. Partially migrated means that only some CiscoWorks functions are provided by the CiscoWorks Server.

Table A-3 Partially Transitioned Features 

Feature	CiscoWorks Feature Description	CiscoWorks Server Feature
Device- and Application-Level Security	Allows all application- and user-based security to be applied to groups of devices.	Uses a five-level security model that addresses application-level security on a user-role basis. CiscoWorks does not provide device-level security.
Security Manager (SA Password)	Authorizes users and defines capabilities.	Provides user access to CiscoWorks and its functions, based on five user groups.

Identifying Non-Transitioned Features

Table A-4 shows CiscoWorks features that are not transitioned to the CiscoWorks Server.

Table A-4 Non Transitioned Features 

CiscoWorks Feature	Description	Function Alternatives
TACACS Manager	Provides TACACS server to manage user access.	•The XTACACS protocol is replaced with the TACACS+ protocol. •The commercial version of TACACS+ is CiscoSecure. CiscoSecure's scripts will convert XTACACS data files to XTACACS+ data files. For information about CiscoSecure, refer to the following URL: http://www.cisco.com/warp/public/cc/pd/sqsw/index.shtml •You can also use public domain TACACS and XTACACS (Extended TACACS) software, available from CCO. –For information about these as is freeware items, refer to the following URL: http://www.cisco.com/pcgi-bin/tablebuild.pl/tacacs –A freeware daemon available from CCO also can help you migrate from XTACACS protocol to the TACACS+ protocol. For information about this as is freeware software, refer to the following URL: http://www.cisco.com/pcgi-bin/tablebuild.pl/tacacs_plus