Failed to connect. "secondary management must be initially synced before connecting"

[scottikon]

I have a colleague who has taken an export from the active primary management server and after he has imported in to his lab management server is unable to log in with the following error displayed in SmartConsole: =

"Failed to connect. Secondary management must be initially synced before connecting."

Has anyone seen this before or ideas about resolving. Not sure if there is a flag or switch we can update so it thinks it synchronised. 

Kind Regards

Scott 

[Nick_Doropoulos]

Hello Scott,

Having difficulty finding an sk specific for the encountered error, I would say that the database had not been exported properly.

As such, please carry out the following pre-migration tasks and try reproducing the issue again:

1) Double-check you have downloaded the correct migration tools package.

2) Run fw logswitch.

3) Run cpstop to stop the services.

4) Run cpstat mg to ensure that no other administrators are logged into the SMS. Please take a screenshot of this command's output as well for future reference as it might be needed.

5) Export the database (yes | nohup ./migrate export [options] /<full path>/<name of exported file without any extension> )

6) Reproduce the issue and advise results.

I hope this helps.

[Vladimir]

Just resolved this for myself. The verdict is this: your colleague may have exported the Active, but not Primary.

There is a recovery procedure for this scenario with following caveats:

There are no licenses except local management in this server's database.

So for the lab, it'll work just fine, provided you/friend are not planning to manage anything with it, else, eval licenses.

R80.40 Security Management Admin guide has it described, but here's the summary:

[Expert@2ndMGMT:0]# $MDS_FWDIR/scripts/cpm_status.sh
Check Point Security Management Server is running and ready
[Expert@2ndMGMT:0]# $FWDIR/bin/promote_util
Binding to localhost...Done
Opening database...Done
Promoting, please wait...
[Expert@2ndMGMT:0]# cpstop
...
[Expert@2ndMGMT:0]# ls -la $FWDIR/conf/mgha
total 52
drwx------ 2 admin config 6 Feb 12 22:05 .
drwxrwx--x 45 admin root 36864 Feb 13 00:57 ..
[Expert@2ndMGMT:0]
[Expert@2ndMGMT:0]# mv $FWDIR/conf/mgha $FWDIR/conf/mgha_old
[Expert@2ndMGMT:0]# cpstart

...after SmartConsole cleanup:

[Expert@2ndMGMT:0]# ls $FWDIR/conf/ |grep mgha
mgha
mgha_old
[Expert@2ndMGMT:0]#

[Expert@2ndMGMT:0]# ls -la $FWDIR/conf/mgha
total 64
drwx------ 2 admin root 65 Feb 12 23:58 .
drwxrwx--x 45 admin root 36864 Feb 13 00:57 ..
-rw-rw---- 1 admin root 147 Feb 12 23:58 ca.jrnl
-rw-rw---- 1 admin root 53 Feb 12 23:58 journal_repository
-rw-rw---- 1 admin root 147 Feb 12 23:58 pgsql.jrnl
[Expert@2ndMGMT:0]#