In order to migrate your CiscoWorks Management Center for Cisco Security Agents (CSA MC) to a new server, complete these steps:
Note: These steps also serve as a disaster recovery plan.
Setup the new machine. Install the operating system and SQL with the service packs.
Assign the same IP address and machine name as the old server.
If you used Full SQL, or Microsoft SQL Desktop Edition (MSDE), use the same exact version on the new machine.
Install the same exact version of CiscoWorks VPN/Security Management Solution (VMS).
Install the same exact version of CSA MC, for example, if it was version 4.5.1(615), make sure it is the same exact version.
When it is done, it reboots the server, so wait until it reboots.
Immediately stop the CSA agent, and stop CiscoWorks. CSA MC stops. This occurs only if CSA Agent is installed on the server already.
Stop MSQL server, which is the database.
In the new machine, choose the CSA45/db folder and rename this folder.
From the old machine, choose the CSA45/db folder and copy the entire folder to a CD or network drive.
In the new machine, copy this entire folder to the CSA45/db folder that you saved from the old machine.
Reboot the server. This ensures that the licenses are activated.
Do a full backup of the server. This ensures that a backup is in place in case something goes wrong during this turnover stage.
The server is ready to use now.
This procedure also carries over the licenses, which is why the last reboot is necessary. The restart of the CSA MC service does this as well. After the server is successfully migrated, add additional VMS modules as needed.
Note: If the IP address of CSA MC server is to be changed, then no changes are required, but if the name of the CSA MC is changed, it is necessary to regenerate the certificates, because CSA agents communicate through the name.
Hi team I planning the upgrade from ise 2.3 to ise 2.4 in a two nodes deployment to a new HW. Already read the upgrade document and I think this is the procedure. ise01a = ise 2.3 primary node (3415)ise02a = ise 2.3 secondary node (3415)ise...
Im trying to restrict access through my ASA from several countries. When I test the ACL using my IP I lose ping ability and access to resources as I should. However I can still ping the outside interface and initiate an anyconnect connection. access-list ...
I have seen the error message "The VPN client agent was unable to create the interprocess communication depot" linked to Windows installs and Internet Connection Sharing turned on. I have AnyConnect version 4.8.01090 installed on a late 2014 Mac&nbs...
I'm upgrading our ISE deployment this weekend. I was planning to go to 2.4, but with Cisco changing the recommended to 2.6, I'm wondering if I should go to 2.6, or stick with 2.4 plan for now. Has anyone seen major bugs in 2.6?We use our deployment f...