Print Download PDF Send Feedback

Previous

Next

Installing a VSX Gateway

Note - This procedure applies to both Check Point Appliances (except 1100, 1200R, and 1400 models) and Open Servers.

Workflow:

  1. Install the VSX Gateway.
  2. Configure the VSX Gateway object in SmartConsole.
  3. Configure the Virtual Devices on this VSX Gateway and their Security Policies in SmartConsole.

Step 1 of 3: Install the VSX Gateway

Step

Description

1

Install the Gaia Operating System:

2

Run the Gaia First Time Configuration Wizard.

3

During the First Time Configuration Wizard, you must configure these settings:

  • In the Installation Type window, select Security Gateway and/or Security Management.
  • In the Products window:
    1. In the Products section, select Security Gateway only.
    2. In the Clustering section, clear Unit is a part of a cluster, type.
  • In the Dynamically Assigned IP window, select the applicable option.
  • In the Secure Internal Communication window, enter the desired Activation Key (between 4 and 127 characters long).

Step 2 of 3: Configure the VSX Gateway object in SmartConsole

Step

Description

1

Connect with SmartConsole to the Security Management Server or Main Domain Management Server that should manage this VSX Gateway.

2

From the left navigation panel, click Gateways & Servers.

3

Create a new VSX Gateway object in one of these ways:

  • From the top toolbar, click the New (Star icon) > VSX > Gateway.
  • In the top left corner, click Objects menu > More object types > Network Object > Gateways and Servers > VSX > New Gateway.
  • In the top right corner, click Objects Pane > New > More > Network Object > Gateways and Servers > VSX > Gateway.

The VSX Gateway Wizard opens.

4

On the VSX Gateway General Properties (Specify the object's basic settings) page:

  1. In the Enter the VSX Gateway Name field, enter the desired name for this VSX Gateway object.
  2. In the Enter the VSX Gateway IPv4 field, enter the same IPv4 address that you configured on the Management Connection page of the VSX Gateway's First Time Configuration Wizard.
  3. In the Enter the VSX Gateway IPv6 field, enter the same IPv6 address that you configured on the Management Connection page of the VSX Gateway's First Time Configuration Wizard.
  4. In the Select the VSX Gateway Version field, select R80.30.
  5. Click Next.

5

On the Virtual Systems Creation Templates (Select the Creation Template most suitable for your VSX deployment) page:

  1. Select the applicable template.
  2. Click Next.

6A

On the VSX Gateway General Properties (Secure Internal Communication) page:

  1. In the Activation Key field, enter the same Activation Key you entered during the VSX Gateway's First Time Configuration Wizard.
  2. In the Confirm Activation Key field, enter the same Activation Key again.
  3. Click Initialize.
  4. Click Next.

6B

If the Trust State field does not show Trust established, perform these steps:

  1. Connect to the command line on the VSX Gateway.
  2. Make sure there is a physical connectivity between the VSX Gateway and the Management Server (for example, pings can pass).
  3. Run: cpconfig
  4. Enter the number of this option: Secure Internal Communication.
  5. Follow the instructions on the screen to change the Activation Key.
  6. On the VSX Gateway General Properties page, click Reset.
  7. Click Initialize.

7

On the VSX Gateway Interfaces (Physical Interfaces Usage) page:

  1. Examine the list of the interfaces - it must show all the physical interfaces on the VSX Gateway.
  2. If you plan to connect more than one Virtual System directly to the same physical interface, you must select VLAN Trunk for that physical interface.
  3. Click Next.

8

On the Virtual Network Device Configuration (Specify the object's basic settings) page:

  1. You can select Create a Virtual Network Device and configure the first desired Virtual Network Device at this time (we recommend to do this later) - Virtual Switch or Virtual Router.
  2. Click Next.

9

On the VSX Gateway Management (Specify the management access rules) page:

  1. Examine the default access rules.
  2. Select the applicable default access rules.
  3. Configure the applicable source objects, if needed.
  4. Click Next.

Important - These access rules apply only to the VSX Gateway (context of VS0), which is not intended to pass any "production" traffic.

10

On the VSX Gateway Creation Finalization page:

  1. Click Finish and wait for the operation to finish.
  2. Click View Report for more information.
  3. Click Close.

11

Examine the VSX configuration:

  1. Connect to the command line on the VSX Gateway.
  2. Log in to the Expert mode.
  3. Run: vsx stat -v

12

Open the VSX Gateway object.

13

On the General Properties page, click the Network Security tab.

14

Enable the desired Software Blades for the VSX Gateway object itself (context of VS0).

Refer to:

15

Click OK to push the updated VSX Configuration.

Click View Report for more information.

16

Examine the VSX configuration:

  1. Connect to the command line on the VSX Gateway.
  2. Log in to the Expert mode.
  3. Run: vsx stat -v

17

Install policy on the VSX Gateway object:

  1. Click Install Policy.
  2. In the Policy field, select the default policy for this VSX Gateway object.

    This policy is called: <Name of VSX Gateway object>_VSX.

  3. Click Install.

18

Examine the VSX configuration:

  1. Connect to the command line on the VSX Gateway.
  2. Log in to the Expert mode.
  3. Run: vsx stat -v

Step 3 of 3: Configure the Virtual Devices and their Security Policies in SmartConsole

Step

Description

1

Connect with SmartConsole to the Security Management Server, or each Target Domain Management Server that should manage each Virtual Device.

2

Configure the desired Virtual Devices on this VSX Gateway.

3

Configure the applicable Security Policies for these Virtual Devices.

4

Install the configured Security Policies on these Virtual Devices.

5

Examine the VSX configuration:

  1. Connect to the command line on the VSX Gateway.
  2. Log in to the Expert mode.
  3. Run: vsx stat -v

For more information, see the: