{"id":246,"date":"2009-06-11T15:59:41","date_gmt":"2009-06-11T15:59:41","guid":{"rendered":"https:\/\/fir3netwp.gmsrrpobkbd.com\/2009\/06\/11\/migrate-a-provider-1-cma-to-a-smart-centre-server\/"},"modified":"2023-02-24T13:09:25","modified_gmt":"2023-02-24T13:09:25","slug":"migrate-a-provider-1-cma-to-a-smart-centre-server","status":"publish","type":"post","link":"https:\/\/www.fir3net.com\/Firewalls\/Check-Point\/migrate-a-provider-1-cma-to-a-smart-centre-server.html","title":{"rendered":"Check Point: Migrate Provider-1 R55 CMA to R65 Smart Centre Server"},"content":{"rendered":"
Log into the Provider-1 via SSH and remove the following Links, <\/span> #mdsenv [cma] \u00a0Delete the links, (you can find the CMA name\/IP using mdsstat) and then run:<\/span> #mdsenv \u00a0If you want to continue to use the CMA you will need to restore the links. Here are the steps to restore your CMA,<\/span> #mdsstop_customer [cma] 2.\u00a0Change the Object Name to that of the Smart Centre`s hostname. Below are the steps required to migrate a Provider-1 CMA to a Smart Centre Server. This tutorial was based on exporting and migrating from R55 to R65 and will involve the following steps, \u00a0 1.\u00a0Export the CMA on the Provider-1 2.\u00a0Import the CMA into Smart Centre 3.\u00a0Export and detach license 4.\u00a0Update the Smart Centre Object … Read more<\/a><\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[17],"tags":[],"yoast_head":"\n
\n<\/span><\/p>\n
\n#rm $FWDIR\/conf\/cp-admins
\n#rm $FWDIR\/conf\/cp-gui-clients
\n#rm $FWDIR\/conf\/packages.c\u00a0<\/span><\/p>\n<\/div>\n
\n<\/span><\/p>\n
\n#mdsstop_customer [cma]
\n#mdsenv [cma]
\n#mcd bin (note the path)
\n#cd upgrade_tools
\n#.\/upgrade_export \/var\/tmp<\/span><\/p>\n<\/div>\n
\n<\/span><\/p>\n
\n#mdsenv [cma]
\n#mcd conf
\n#ln -s \/opt\/CPmds-R55\/conf\/mdsdb\/cp-admins.C cp-admins
\n#ln -s \/opt\/CPmds-R55\/conf\/mdsdb\/cp-gui-clients.C cp-gui-clients
\n#ln -s \/opt\/CPmds-R55\/conf\/mdsdb\/packages.c packages.c
\n#mdsenv
\n#mdsstart_customer [cma]\u00a0<\/span><\/p>\n<\/div>\n
\n2. Import the config by using <\/span>$FWDIR\/bin\/upgrade_tools\/upgrade_import [exported_cma].tgz<\/strong>
\n<\/span>3. When asked about the licensing select \u201cNo\u201d.
\n4. Once the import is complete you will find that you receive an error when trying to run cpconfig.
\n5. Run the command <\/span>cd<\/strong> $CPDIR\/conf ; mv inst.conf inst.conf.bak<\/strong><\/span>
\n6. Run cpstart<\/span><\/div>\n
\n2.\u00a0Export the license as a file and detach from the Smart Centre Server Object.
\n<\/span><\/div>\n
\n<\/strong><\/span><\/div>\n
\n<\/span><\/p>\n<\/div>\n
\n1.\u00a0Using cpconfig select the \u201cCertificate Authority\u201d option.
\n2.\u00a0Select \u201cYes\u201d to Reinitialise the CA and use the Smart Centre Object name as the internal CA name.
\n<\/span><\/div>\n
\n1.\u00a0Re-import the license into the repository and reattach to the Smart centre server.
\n<\/span><\/div>\n
\n<\/strong><\/span><\/div>\n
\n2.\u00a0If this option is greyed out, a missing symlink could be missing.
\nTroubleshooting steps can be found by selecting (from toolbar) Packages > Get Data From All.<\/span><\/div>\n
\n<\/span><\/div>\n
\n2. Then re-push the policy from your new manager to your firewalls.
\n<\/span><\/div>\n