Wednesday 26 October 2011

CMA Customer Export Script

Hello everyone,

From time to time a situation arises where a customer needs to be 'exported' from an MDS and moved to a standalone Smart Center (SCS). The reasons for this can vary, however the tools for doing this are nearly non-existant.

One would love to use the uprade_export tool for a situation like this, however it simply isn't supported in a Provider-1 environment. According to CheckPoint's sk33067, this isn't even supported.

As such, I've written up a quick script to collect the required files that I need to export a customer's configuration. Please feel free to use it and share at your discretion.

When utilizing it, you'll see the following:
--------------------------------
Please specify the name of the customer (no spaces)
expertmode
Please enter the IP address of the CMA you wish to export
10.80.80.55


Thank you

You have specified to use the following CMA:
|expertmode-cma-10.80.80.55

Is this correct (yes or no)
yes

Collecting the required files...
Collection complete

Compressing...

Compression complete

Cleaning up

Done
Your files are located at /var/tmp/expertmode_migrate.tgz
Goodbye
--------------------------------

You can find the script hosted on Google docs here

As to what the script is actually grabbing, it's pretty simple:
$FWDIR/conf
$FWDIR/database
$CPDIR/conf
$CPDIR/registry

Cheers,

6 comments:

  1. Hi Craig!

    Great job. Although this won't work on R7x, CMA migration tool has been changed since R65, completely

    ReplyDelete
  2. Hey Valeri - Thanks :)

    This was never really meant to interface with the CMA migration tool (although I suppose it would work on certain versions). This was always for a 'manual' migration back non-P1 infrastructure. IE -> replace the files manually etc.

    I should probably update it for R70x though :)

    Cheers,

    ReplyDelete
  3. Bah, apparently I can't edit my posts...

    Anyways, I meant to say I should update it for the R70x tools that 'do' exist - it works on any version as it is if you're game for manual migration :)

    ReplyDelete
  4. Hi - how does one then import these files to the new standalone management server?

    ReplyDelete
  5. Hi - how does one then import these files to the new standalone management server?

    ReplyDelete
  6. Hi - how does one then import these files to the new standalone management server?

    ReplyDelete