Running CLI Commands in Automation Scripts

In This Section: Introduction to Automation Scripts Working with dbedit Using XML to Export Settings for a Domain Management Server

Introduction to Automation Scripts

Use these CLI commands and tools to create automation scripts:

• dbedit - Creates and configures objects and rules in the database for the Security Policy (see skI3301).
• fwm load - Installs the specified Security Policy on Security Gateways. The Security Policy is validated, and only valid Policies are installed.
• send_command - Runs functions, which are not included with standard Check Point CLI commands and tools.

We recommend that you use a separate SmartConsole administrator account for automation scripts. This additional account lets you easily monitor automatic changes and ones made by system administrators.

Creating a Domain Management Server

Prerequisites

• Name or Identifier of the domain, for example MyDomain
• Name or Identifier of the new Domain Management Server, for example MyDMS
• IPv4 address for the new Domain Management Server
• IPv4 Address for the Multi-Domain Server
• The Multi-Domain Server username and password for a Multi-Domain Superuser who has permission to create the new Domain Management Server.

To create a new Domain Management Server:

1. Open a terminal emulation program (such as PuTTY).
2. Open an SSH connection to the Multi-Domain Server.
3. Log in with the superuser credentials.
4. Enter expert mode.
5. Run these commands.

   mdscmd addmanagement <domain_name> [-n <domain_server> | -i <ipv4> | -a <ipv6>]

   > mdscmd addcma Cust_ID -n Cust_CMA -i 192.0.2.61 -t 192.0.2.50 -m 192.0.2.50 -u admin -p vpn123

   > mdscmd startcma Cust_ID -n Cust_CMA -m 192.0.2.50 -u fwadmin -p vpn123

   The Domain Management Server is created. Log in to 192.0.2.61 to configure the settings.