Support Center > Search Results > SecureKnowledge Details
Policy installation flow process Technical Level

Policy installation flow:

  1. Assuming the initiation was made by the SmartDashboard, as opposed to using command line options, such as fwm load (on Management Server) or fw fetch (on Security Gateway), the Web Service policy installation command is sent to the Check Point Management (CPM) on the Management Server, which then sends the command to the FWM process where the verification and compilation take place. (In case of failure, debug messages of cpm can be found in $MDS_FWDIR/log/install_policy.elg file.)

  2. FWM process is responsible for code generation and compilation.

  3. FWM process invokes the Check Point Policy Transfer Agent (CPTA) command that sends the policy to all applicable Security Gateways.

  4. CPD process on the Security Gateway receives the policy and verifies its integrity.

  5. FWD process on the Security Gateway updates all of the user-mode processes responsible for enforcement aspects. These include VPND process for VPN issues, FWSSD processes for Security Server issues, and so on. Once complete, the CPD process then initiates the update for Check Point kernel.

  6. The new policy is prepared, and the Check Point kernel holds the current traffic and starts queuing all incoming traffic.

  7. The Atomic Load takes place. This process should take a fraction of a second.
    Note: During Atomic Load, SecureXL is disabled and re-enabled afterwards.

  8. The traffic queue is released, and all of the packets are handled by the new security policy.

For R80.10:

When Policy Installation is initiated from SmartConsole:

  1. The cpmi policy installation command is sent to fwm on the Management server.
    Clarification: The CPMI connection is internal to the Management Server, from CPM to FWM. The install command is sent to the CPM server via web service.
  2. fwm performs verification and conversion of the database information for the installation targets for which policy installation is requested.
  3. After conversion, fwm invokes fw_loader to perform code generation, compilation, transfer to all applicable gateways and commit.
  4. cpd on the Security Gateway listens for install policy connections and receives the files.
  5. cpd invokes fw_fetchlocal to load the new policy into the kernel. 
  6. cpd waits for fw_fetchlocal to complete the process and then informs the Management server of the command's status (installation succeeded or failed).

To debug policy installation issues, refer to these solutions:

This solution has been verified for the specific scenario, described by the combination of Product, Version and Symptoms. It may not work in other scenarios.
Applies To:
  • Also relevant for R80.10

Give us Feedback
Please rate this document