In This Section: |
Large-scale deployment is supported in all centrally managed appliances in R77.30.
Make sure your version supports LSM. Currently, LSM is not supported in R80.
Notes for the 1400 appliances:
CP1400AS1100*
If you do not use the CP1400AS1100
, you cannot select the package in the view.
When you define a SmartLSM profile for a gateway or cluster in SmartDashboard, you can use SmartProvisioning to provision multiple gateways.
Workflow for large-scale deployments:
Or
Use a USB drive to quickly configure multiple appliances without the First Time Configuration Wizard. For more details, see Deploying from a USB Drive.
SmartLSM lets you manage a large number of Check Point Appliance gateways from one Security Management Server. When you use a SmartLSM profile, you reduce the administrative overhead as you define the gateway properties and policy per profile. The SmartLSM profile is a logical object that contains the firewall and policy components.
Use SmartDashboard to define a single SmartLSM profile for the Check Point Appliance.
To define a single SmartLSM profile Check Point Appliance:
The SmartLSM Security Profile window opens.
To open the online help for each window, click Help.
Note - To activate SmartProvisioning functionality, you must install a security policy on the LSM profile.
The SmartLSM Appliance Cluster Profile is a logical object like the SmartLSM Appliance Gateway profile. It contains the firewall and policy components but also requires logical topology configuration.
The topology table in the SmartLSM Cluster Profile is a template for all SmartLSM clusters that is created with this profile. The SmartLSM Cluster Profile automatically assigns the configuration settings and security policies to the SmartLSM cluster.
The SmartLSM Cluster Profile and its topology are configured in SmartDashboard. Then the SmartProvisioning SmartConsole GUI is used to connect and manage the appliances by the Security Management Server.
Before you do the procedure:
To create a SmartLSM Cluster profile:
For each SmartLSM cluster, you must define at least 3 networks:
The network addresses (for example, 1.1.1.194) for each interface are not the actual addresses for your SmartLSM Cluster environment. Those are used for the template. The actual network addresses are modified in the next configuration step in the SmartProvisioning application.
Important - The host octet for the Virtual IP addresses can be modified later. |
You can use SmartProvisioning to manage Check Point Appliance gateways with the SmartLSM profiles defined in SmartDashboard. Configure these appliances using the First Time Configuration Wizard or a USB drive configuration file before you manage them with SmartProvisioning.
For more information about large-scale deployment using SmartProvisioning, see the SmartProvisioning Administration Guide.
Use this procedure to prepare the policy for automatic installation when the gateway connects.
Note - If the Check Point Appliance is physically set up and configured, when you successfully complete this step, the policy is pushed to the gateway. For a list of possible statuses, see Viewing the Policy Installation Status.
At the end of the Install Policy process, the policy status for a Check Point Appliance that is not yet set up is "waiting for first connection." This implies that trusted communication is not yet established between the Security Management Server and the Check Point Appliance. When the gateway connects it establishes trust and attempts to install the policy automatically.
To install a security policy:
The Install Policy window opens.
By default, all gateways that are managed by the Security Management Server are available for selection.
The Installation Process window shows the status of the Network Security Policy for the selected target.
Important - If the Check Point Appliance object is defined by the appliance is not set up and it is in the "Waiting for first connection status", you see a message that says "Installation completed successfully". This means that the policy is successfully prepared for installation. |
Continue tracking the status of the Security Policy installation with the Policy Installation and the status bar.
You can see the installation status of managed gateways with the status bar that shows at the bottom of the SmartDashboard window. The status bar shows how many gateways are in Pending or Failed mode.
The status bar is updated dynamically each time a gateway tries to install a policy or tries to connect to the Security Management Server. The results of these actions are also shown in SmartDashboard popup notification balloons when such events occur. You can configure these notifications.
To monitor the status of the last policy installed on each gateway, you can use the Policy Installation Status window.
The window has two sections. The top section shows a list of gateways and status details regarding the installed policy. You can use the filter fields to see only policies of interest and hide other details by defining the applicable criteria for each field. After you apply the filtering criteria, only entries that match the selected criteria are shown. If the system logs trusted communication (SIC) attempts from unknown gateways, a yellow status bar opens below the filter fields.
The bottom section shows details of a row you select in the gateway list (errors that occurred, the date the policy was prepared, verification warnings). If there is a yellow status bar, click Show details to show the details of unknown gateways that try to connect to the Security Management Server.
These are the different statuses in this window:
Icon |
Policy status |
Description |
---|---|---|
Succeeded |
Policy installation succeeded. |
|
Succeeded |
Policy installation succeeded but there are verification warnings. |
|
Waiting for first connection |
A Check Point Appliance object is configured, but the gateway is not connected to the Security Management Server (initial trust is not established).
|
|
Waiting for first connection |
Same as above, with warnings that attempts to establish trust failed or there are verification warnings. |
|
Pending |
The policy remains in the pending status until the gateway successfully connects to the Security Management Server and retrieves the policy. This status is shown only if there was at least one successful policy installation. For example, when the Security Management Server has problems connecting to the Gateway (the Gateway is unavailable for receiving communication, as in behind NAT). |
|
Pending |
Same as above but there are verification warnings. |
|
Warning |
Warning. |
|
Information |
Information. |
|
Failed |
Policy not installed due to a verification error. |
|
Failed |
Policy installation failed. |
You can access the Policy Installation Status window in these ways: