There is no tool to move all custom configuration from one EMS to another, so you have to export the custom policies and custom signature libraries one at a time and copy the exported XML files to the new EMS for import. The "master" policies and signature libraries need not be touched, as the Live Update process will keep these up to date.
One small detail I forgot to mention is that after copying files into the importFiles directory of the new EMS, they need to have ownership and/or permissions changed so that they can be read by the EMS process. From the /opt/dragon directory, you can run ./install/fixperms.pl to verify/set file permissions correctly for all files on the system. Regards, Patrick -----Original Message----- From: Tom Keren [mailto:[email protected]] Sent: Monday, June 03, 2013 5:57 PM To: Enterasys Customer Mailing List Subject: RE:[enterasys] EMS Policy Migration Patrick, Does Enterasys have a migration tool to execute this task? Or, do we need to export the database to the other EMS Server. The configuration guide does not appear to have any guidance on the Main Policy/Signature Migration. It does have a section on the Import/Export wizard for the custom Polices and Signatures. Thanks Again --- To unsubscribe from enterasys, send email to [email protected] with the body: unsubscribe enterasys [email protected] --- To unsubscribe from enterasys, send email to [email protected] with the body: unsubscribe enterasys [email protected]
