Chapter 3 Installing the Management Center for Cisco Security Agents
Accessing Management Center for Cisco Security Agents
3-42
Installing Management Center for Cisco Security Agents 5.2
78-17916-01
Step 5 Next you copy the migration_data_export.xml and all the
migration_host_data<number>.dat
files from the V5.x or V4.x system to
your V5.2 system. These files must exist together in the same directory on the
V5.2 system (although the directory name and location does not matter).
Step 6 Then from the V5.2 system, run the webmgr import utility from a command
prompt to pull the data into the new MC. You cannot use the CSA MC UI Import
utility to do this. That utility does not allow you to import the .dat files that are
associated with the .xml file as one grouping.
From a command prompt window on the V5.2 system, cd to the Cisco
Systems\CSAMC\CSAMC52\bin
directory and run the following:
%system%Cisco Systems\CSAMC\CSAMC52\bin>webmgr import
%path_to_xml_file%\migration_data_export.xml
Because the host .dat files are associated with the .xml file, this command imports
both the configuration and host data with the migration_data_export.xml file.
Step 7 You must generate rules once the import is complete. If you do not generate rules
at this point, you cannot upgrade agent host software as described in the next
section.
Note CSA MC V5.2 ships with policies that contain new V5.2 functionality. This new
functionality does not match allV5.x or V4.x configurations. CSA MC
configuration item names are labeled with the release version number to
distinguish them from older (or newer) configuration items or items created by
administrators. When you import your older configuration, new V5.2 items are
not overwritten. You will likely have items from both versions in your CSA MC
V5.2. If the import process finds that two items have the exact same contents and
the only difference is the V5.2 appended name field, the older item is not imported
and the newer V5.2 item is used in its place.
Step 8 To upgrade migrated V5.x or V4.x agents to V5.2, schedule V5.2 software
updates for older agents. You schedule this upgrade from the V5.x or V4.x
system. (Running the
prepare_<version>_migration.exe file placed a V5.2
software update on the V5.x or V4.x machine.)
Once the older agents receive the scheduled software update, they will point to
and register with the new CSA MC V5.2. The update contains the appropriate new
certificates to allow this to occur. Once hosts register with V5.2, they will be
associated with the correct groups based on the host migration that you performed
earlier.
