> Source: [sk101875](https://support.checkpoint.com/results/sk/sk101875) # sk101875 - Policy installation fails with "Load on module failed - no memory" error | Property | Value | |----------|-------| | Solution ID | sk101875 | | Date Created | 2014-08-07 | | Last Modified | 2023-04-26 | | Technical Level | General | | Products | Security Gateway, Security Management Server, Multi-Domain Security Management Server | | Versions | R82.10, R82, R81.20, R82.20 | ## Solution ### Introduction This article describes different scenarios when policy installation fails with "**`Load on module failed - no memory`** " error. Each scenario has its own cause and solution. **Table of Contents:** 1. Rule name field contains a non-ASCII character 2. Insufficient memory for the current number of connections 3. The same IP address is assigned to several Security Gateways 4. IP address of cluster object is identical to one of the member's IP addresses 5. Value of URL Filtering parameter 'cache_max_hash_size' is higher than 25000 6. Traditional Anti-Virus is enabled on R75.40 Security Gateway 7. 'vmalloc' memory exhaustion on Security Gateway R65 / R70 / R71 8. Security Gateway R75.40 / R75.40VS / R75.20.X for SMB appliances 9. Virtual System on 60000 / 40000 chassis in VSX mode 10. Connectra NGX R62, R66 11. Related documents Show the Entire Article ### 1. Rule name field contains non-ASCII character {#Scenario 1} **Symptoms:** * Security policy installation fails with error message "`Load on module failed - no memory`". Show / Hide solution **Additional Symptoms:** * Checking the maximal size of the kernel table *string_dictionary_table* ([sk61541](https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails=&solutionid=sk61541)) with the command "`fw tab -t string_dictionary_table | grep limit`", and then checking the current number of entries in this kernel table with the command "`w tab -t string_dictionary_table -s`" (per [sk66342](https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails=&solutionid=sk66342)) shows that this kernel table is full - the "`limit`" value equals the value in the "`#VALS`" column. *Example* : ``` [Expert@GW-R77.20:0]# fw tab -t string_dictionary_table | grep limit dynamic, id 8135, attributes: keep level 2, expires never, , hashsize 4096, limit 65536 [Expert@GW-R77.20:0]# [Expert@GW-R77.20:0]# fw tab -t string_dictionary_table -s HOST NAME ID #VALS #PEAK #SLINKS localhost string_dictionary_table 8135 65536 65536 65536 ``` **Issue:** * 00193332 * 00592562 **Cause:** > * The code that handles logging of rule UIDs does not support non-ASCII characters in comments, object names or rule names. When non-ASCII characters are used, a kernel routine that verifies strings returns an error causing the entire policy installation process to fail with the "no memory" message. > > The other reason is that the default size of the kernel table*string_dictionary_table* is too small to handle the current large rulebases for tracking UIDs. **Solution:** > The message actually does not have anything to do with memory in 99% of the cases. > > By default, the ***rulebase_uid_in_log*** parameter is set to '*true* '. When this parameter is set to '*true*', each rule in the rulebase is logged during the Security policy installation, and this can intermittently cause memory problems, particularly with large policies. > > By setting this parameter to '*false* ', these logs are no longer generated during the security policy installation, and consequently, the memory usage on the Security Gateway is no longer affected during the policy installation. > > To make the change to the ***rulebase_uids_in_log*** property: > > 1. Open the SmartDashboard. > 2. Go to '*Policy* ' menu - *Global Properties* - *SmartDashboard Customization* - under *Advanced Configuration* , click on '*Configure...* ' button - expand the '*FireWall-1* ' - go to '*General*'. > 3. Clear the box ***rulebase_uids_in_log*** . > [![](https://sc1.checkpoint.com/sc/SolutionsStatics/sk66342/rulebase_uids_in_log.png)](https://sc1.checkpoint.com/sc/SolutionsStatics/sk66342/rulebase_uids_in_log.png "Click the image to see it in full size in a new tab/window") > 4. Click '*OK*' to close all windows. > 5. Install the security policy. > > **Warning:** Disabling the *rulebase_uid_in_log* parameter disrupts the SmartReporter / Eventia Reporter function. > > **Note:** After the *rulebase_uid_in_log* parameter is disabled, the following columns will be empty in the Security Gateway's logs in SmartView Tracker - '*Current Rule Number* ', '*Rule Name* ' and '*Rule UID*'. Also, the Hit Count for the Security rulebase in SmartDashboard will show 0. > > This error can also be corrected by: > > * Updating the SmartDefense / IPS signatures. > > * Removing the non-ASCII character(s) such as "�" or "�" from the rule name and re-installing the security policy (refer to [sk105708 - How to check Check Point objects and rules for non-ASCII characters](http://supportcontent.checkpoint.com/solutions?id=sk105708)). > > > > * Make sure to remove the long hyphen character ' ? ' as well from rule names and/or comments , which is created automatically by Microsoft Word. > * To verify whether the problem is caused by the non-ASCII (international) character, follow these steps: > > 1. On a Security Gateway, run: *fw ctl zdebug filter \> /var/log/debug.txt*. > 2. Install the security policy in SmartDashboard. > 3. Analyze the */var/log/debug.txt* file. > > If this error is indeed caused by the non-ASCII (international) character, the the following message will appear in the output file: > ***fw_rules_uid_handle_uid: couldn't allocate dictionary string id for rule no. \*** > > **Workaround:** > > * Clear the strings dictionary table by running the following command on the Security Gateway: > *\[Expert@HostName\]# fw tab -t string_dictionary_table -x* > * This does not require a reboot or downtime, but it may reset the Hit Count in SmartDashboard. > > **If the issue persists** , [contact Check Point Support](http://www.checkpoint.com/services/contact/index.html) to get a Hotfix for this issue (Issue ID 00193332 and Issue ID 00592562). A Support Engineer will make sure the Hotfix is compatible with your environment before providing the Hotfix. For faster resolution and verification please collect [CPinfo](https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails=&solutionid=sk92739) files from the Security Management and Security Gateways involved in the case. ### 2. Insufficient memory for the current number of connections {#Scenario 2} **Symptoms:** * Security policy installation fails with error message "`Load on module failed - no memory`". Show / Hide solution **Additional Symptoms:** * When trying to allocate kernel debugging buffer on the Security Gateway, the following errors appear: ``` [Expert@HostName]# fw ctl debug -buf 32000 kiss_debug_all_vs_ioctl: ioctl failed to kernel : Cannot allocate memory Failed to allocate kernel debugging buffer ``` * Increasing the value of the '`vmalloc`' attribute in '`/boot/grub/grub.conf`' file on the Security Gateway does not resolve the issue. **Cause:** > * The amount of required machine's memory for the current number of connections is very high. In addition, the more CoreXL FW instances are running, the more memory is consumed. **Solution:** > **Important Notes:** > > * Schedule a maintenance window. The procedure will require a reboot. > * In cluster environment, the procedure must be performed on all members of the cluster. > > * Member with higher number of CoreXL FW instances will change its state to '`Ready`' (refer to [sk42096](http://supportcontent.checkpoint.com/solutions?id=sk42096)) > * Member with higher kernel edition will change its state to '`Ready`' (refer to [sk42096](http://supportcontent.checkpoint.com/solutions?id=sk42096)) > > **Procedure:** > > * If a 64-bit kernel mode can be used, then change the kernel edition from 32-bit to *64-bit*: > > * In Gaia Portal: > > 1. Go to `System Management` section -\> `System Configuration` page. > 2. In the `Edition` section, select '`64-bit`' and click `Apply`. > 3. Reboot the Security Gateway. > * In Gaia Clish: > > 1. Run these commands: > *HostName\> set edition 64-bit > HostName\> save config* > 2. Reboot the Security Gateway. > >
> >
> > * If only a 32-bit kernel mode can be used, then *decrease* the number of CoreXL FW instances via the '`cpconfig`' menu: > > `[Expert@HostName]# cpconfig` > 1. Select the option '`Check Point CoreXL`'. > 2. Select the option '`Change the number of firewall instances`'. > 3. Type the desired number of firewall instances and press the Enter key. > 4. Exit from CoreXL configuration sub-menu. > 5. Exit from '`cpconfig`' menu. > 6. Reboot the Security Gateway. ### 3. The same IP address is assigned to several Security Gateways {#Scenario 3} **Symptoms:** * Security policy installation fails with error message "`Load on module failed - no memory`". Show / Hide solution **Additional Symptoms:** * Error messages on the console and in /var/log/messages file on Security Gateway: * `FW-1: Attempting to create an already existing table: ...` * `FW-1: Warning: atomic loading failed during ...` **Issue:** * 01175810 **Cause:** > * The same IP address is assigned to several different Security Gateways. > * In some cases, assigning the IP address of Security Gateway object "A" to another Security Gateway object "B", and then changing the IP address of Security Gateway object "A", still results in this error. **Solution:** > This problem was fixed. The fix is included in: > > * [Check Point R75.47](https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails=&solutionid=sk93448) > > If you do not wish to upgrade, then follow these steps: > > * On single Security Management Server: > > Resolve the IP address conflict by assigning a different IP address to the Security Gateway object, on which the policy installation has failed. > If the old and the new objects have different IP addresses, but the error persists, then remove the old object. > * On Multi-Domain Security Management Server: > > A Security Gateway may be enabled for Global use. Therefore, its removal can harm the Provider-1 / Multi-Domain environment. > > To assign a different IP address to the Security Gateway: > 1. Connect with SmartDashboard to Security Management Server / Domain Management Server. > 2. Edit the Security Gateway object. > 3. In the "`IP address`" field, enter a non-conflicting IP address. > 4. Click '`OK'`. > 5. Save the changes: go to '`File`' menu - click on '`Save`'. > 6. Install the policy on the problematic Security Gateway. ### 4. IP address of cluster object is identical to one of the member's IP addresses {#Scenario 4} **Symptoms:** * Security policy installation fails with error message "`Load on module failed - no memory`". Show / Hide solution **Additional Symptoms:** * Error messages on the console and in /var/log/messages file on Security Gateway: * `FW-1: Attempting to create an already existing table: ...` * `FW-1: Warning: atomic loading failed during ...` **Cause:** > * IP address configured as the main IP address of the cluster object is identical to one of the cluster member's IP addresses. **Solution:** > 1. Connect with SmartDashboard to Security Management Server / Domain Management Server. > 2. Edit the cluster object. > 3. In the "`IP Address`" field of the cluster object, enter a Virtual IP address. > 4. Click '`OK'`. > 5. Save the changes: go to '`File`' menu - click on '`Save`'. > 6. Install the Security Policy on the problematic cluster. ### 5. Value of URL Filtering parameter 'cache_max_hash_size' is higher than 25000 {#Scenario 5} **Symptoms:** * Security policy installation fails with error message "`Load on module failed - no memory`". Show / Hide solution **Additional Symptoms:** * Error messages on the console and in /var/log/messages file on Security Gateway: * `FW-1: Attempting to create an already existing table: ...` * `FW-1: Warning: atomic loading failed during ...` **Issue:** * 01175810 **Cause:** > * Value of URL Filtering parameter 'cache_max_hash_size' (refer to [sk90422](https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails=&solutionid=sk90422)) was configured to a number higher than 25000. **Solution:** > This problem was fixed. The fix is included in: > > * [Check Point R75.47](https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails=&solutionid=sk93448) ### 6. Traditional Anti-Virus is enabled on R75.40 Security Gateway {#Scenario 6} **Symptoms:** * Security policy installation fails with error message "`Load on module failed - no memory`". Show / Hide solution **Additional Symptoms:** * Kernel debug ('`fw ctl debug -m CI + error fatal`') on R75.40 Security Gateway during policy installation shows: * `ci_module_load: [ERROR]: trying to enable AV legacy mode while its set to 2;` * `ci_module_load: [FATAL ERROR]: failed loading ci_module;` **Cause:** > * Traditional Anti-Virus is enabled in R75.40 Security Gateway object. > Traditional Anti-Virus is intended only for Security Gateways R75.30 and older. **Solution:** > 1. In SmartDashboard, open the object of R75.40 Security Gateway. > > 2. Go to '`Other`' pane - '`More Settings`' - clear the '`Enable Traditional Anti-Virus`' checkbox: > > ![](https://sc1.checkpoint.com/sc/SolutionsStatics/sk89050/More_Settings.png) > > 3. Go to '`General Properties`' pane - '`Network Security`' tab - select the box '`Anti-Virus`': > > ![](https://sc1.checkpoint.com/sc/SolutionsStatics/sk89050/General_Properties.png) > > 4. Click on '`OK`' to close the Check Point Gateway properties window. > > 5. Save the changes: '`File`' menu - '`Save`'. > > 6. Install the policy onto R75.40 Security Gateway object. ### 7. 'vmalloc' memory exhaustion on Security Gateway R65 / R70 / R71 {#Scenario 7} **Symptoms:** * Security policy installation fails with error message "`Load on module failed - no memory`". Show / Hide solution **Additional Symptoms:** * */var/log/messages* files on Security Gateway show the following errors: * `kernel: allocation failed: out of vmalloc space - use vmalloc='NUMBER' to increase size` * `kernel: FW-1: fwdynlog_prepare: fw_kmalloc_ex(`*N*`) failed` * `kernel: FW-1: Warning: atomic loading failed during policy replacement (preparation stage)` * Kernel debug ('`fw ctl debug -m fw + dynlog`') on Security Gateway during policy installation shows: ` ;FW-1: fwdynlog_prepare: fw_kmalloc_ex(`*N* `) failed;` ` ;fwk_atomic_load: fwdynlog_prepare failed;` ` .................` ` ;FW-1: Warning: atomic loading failed during policy replacement (preparation stage); ` * Policy installation fails with either of the following errors: * `Installation failed. Reason: Load on Module failed - no memory` * `Failed to Load Security Policy: Cannot allocate memory` * `Failed to Load Security Policy: Kernel memory allocation failed` * `Fetching Security Policy Failed` * `Memory allocation failed: out of vmalloc space - use vmalloc='NUMBER' to increase size` **Issue:** * 00503171 **Cause:** > * 'vmalloc' memory exhaustion because the table containing the rule name and UID has filled up. **Solution:** > This problem was fixed. The fix is included in: > > * Check Point VSX NGX R67 GA > * [Check Point R71.50](https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails=&solutionid=sk69720) > * [Check Point R75](https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails=&solutionid=sk58362) ### 8. Security Gateway R75.40 / R75.40VS / R75.20.X for SMB appliances {#Scenario 8} **Symptoms:** * Security policy installation fails with error message "`Load on module failed - no memory`". Show / Hide solution **Additional Symptoms:** * Kernel debug on Security Gateway ('`fw ctl debug -m fw + filter`') during policy installation / fetch shows: `;fwk_atomic_blade_get_curr_policy: fw_mal_get_curr_policy() failed;` * Debug of policy fetch on Security Gateway shows ('`fw -d fetchlocal -d $FWDIR/state/__tmp/FW1`'): ` ... ...` ` [`*PID*` ...]@HostName[`*Date Time* `] fw_atomic_cmi_read_pattern: Decoding CMI patterns for context id `*XXX* ` [`*PID*` ...]@HostName[`*Date Time* `] fw_atomic_cmi_compile_context_sigs: Error: Failed to add signature `*NNN*` for context id `*XXX* ` Failed to read Database for context id `*XXX* ` [`*PID*` ...]@HostName[`*Date Time* `] fw_atomic_add_cmi_contexts: Failed to create signatures buffer.` ` [`*PID*` ...]@HostName[`*Date Time* `] fw_atomic_ips_cmi_add_signatures_cb: fw_atomic_add_cmi_contexts() failed` ` [`*PID*` ...]@HostName[`*Date Time* `] fw_atomic_cmi_add: cmi_loader_install_policy failed.` ` [`*PID*` ...]@HostName[`*Date Time* `] fw_atomic_download: unlocking mutex: install_policy_mutex` ` ` ` Failed to Load Security Policy: No such file or directory` ` [`*PID*` ...]@HostName[`*Date Time* `] fw_rfetchx_local_ex: failed to load Security Policy` ` [`*PID*` ...]@HostName[`*Date Time* `] update_load_connection: no connection` ` [`*PID*` ...]@HostName[`*Date Time* `] In fwa_vrfy_db restore = -1` ` [`*PID*` ...]@HostName[`*Date Time* `] logo_directory_restore: dir=/opt/CPsuite-R75.40/fw1/state/__tmp/FW1` ` Failed to Load Security Policy: No such file or directory` ` Fetching Security Policy Failed ` * Debug of CPD daemon on Security Gateway (per [sk86320](http://supportcontent.checkpoint.com/solutions?id=sk86320)) during policy installation / fetch might show: ` Failed to Load Security Policy: Kernel memory allocation failed` ` Commit_exec_cb : Executable Failed, returned Load on Module failed - no memory. ` **Issue:** * 00909368 **Cause:** > * The way in which the configuration of the IPS protection "[`HTTP on Non Standard ports`](https://www.checkpoint.com/defense/advisories/public/2005/cpsa-2005-01.html)" is processed during policy installation was changed in R75.40 Security Gateway. **Solution:** > This problem was fixed. The fix is included in: > > * [Check Point R75.45](https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails=&solutionid=sk82740) > * [Check Point R75.20.40 for SMB Appliances](http://supportcontent.checkpoint.com/solutions?id=sk97186) > > For **R75.40 and R75.40VS versions** , [Check Point Support](http://www.checkpoint.com/services/contact/index.html) can supply a **Hotfix** (Issue ID 00909368). > A Support Engineer will make sure the Hotfix is compatible with your environment before providing the Hotfix. > For faster resolution and verification, please collect [CPinfo files](http://supportcontent.checkpoint.com/solutions?id=sk92739) from the Security Management Server and Security Gateways involved in the case. > > **Note:** This hotfix (Issue ID 00909368) and hotfix from [sk86961 - Policy installation after IPS update fails with 'Reason: Load on Module failed - failed to load Security Policy'](http://supportcontent.checkpoint.com/solutions?id=sk86961) do *not* conflict with each other and can be installed on the same Security Gateway. ### 9. Virtual System on 60000 / 40000 chassis in VSX mode {#Scenario 9} **Symptoms:** * Security policy installation on a specific Virtual System on 60000 / 40000 chassis in VSX mode fails with error message "`Load on module failed - no memory`". * Loading the policy under debug from the Management Server shows: `[Expert@HostName:0]# fwm -d load $FWDIR/conf/.W ` ` IP_mgmt_dg_handler: received datagram of type 16` ` OPSEC_SET_ERRNO: err = 15 Datagram length is too short for reading (pre = 0)` ` IP_mgmt_dg_handler: Target = XXX Commit Status = 14 (0: no additional string)` ` CPTA_InstallFailReasonTranslate: error number 14 Ip = XX.XX.XX.XX` ` Installation failed. Reason: Load on Module failed - no memory` Show / Hide solution **Additional Symptoms:** * Chassis's uptime is several months. **Solution:** > 1. Connect to command line on the SMO blade on the chassis > (connect over SSH to the IP address defined in the 60000 / 40000 chassis object in SmartDashboard). > > 2. Switch to the context of the relevant Virtual System. > > 3. Restart the CPD daemon per [sk97638](https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails=&solutionid=sk97638): > > `[Expert@HostName:]# cpwd_admin stop -name CPD -ctx -path "$CPDIR/bin/cpd_admin" -command "cpd_admin stop" -env inherit` > > `[Expert@HostName:]# cpwd_admin start -name CPD -ctx -path "$CPDIR/bin/cpd" -command "cpd" -env inherit` ### 10. Connectra NGX R62, R66 {#Scenario 10} **Symptoms:** * Security policy installation fails with error message "`Load on module failed - no memory`". Show / Hide solution **Additional Symptoms:** * Multiple users and "Access to Applications" rules are configured. **Issue:** * 00442435 * 00427631 **Cause:** > * The memory allocation depends also on the number of allowed concurrent VPN tunnels - the default is 10000. > Memory allocation can fail when the number of configured rules is very large. **Solution:** > 1. Connect with [GuiDBedit Tool](http://supportcontent.checkpoint.com/solutions?id=sk13009) to Security Management Server / Domain Management Server. > > 2. In the upper left pane, go to ***Table*** - ***Network Objects*** - ***network_objects*** . > > 3. In the upper right pane, select the relevant Connectra Gateway object. > > 4. Press CTRL+F (or go to ***Search*** menu - ***Find*** ) - paste ***max_concurrent_vpn_tunnels*** - click on ***Find Next*** . > > 5. In the lower pane, right-click on the ***max_concurrent_vpn_tunnels*** - select ***Edit...*** - change the value to something smaller (for example, 2000) - click on ***OK*** . > > **Note** : The value of *max_concurrent_vpn_tunnels* attribute affects the number of users that can connect to Connectra using a VPN client. Make sure not to lower the number below the expected number of users. > > 6. Save the changes: go to ***File*** menu - click on ***Save All*** . > > 7. Close the GuiDBedit Tool. > > 8. Connect with SmartDashboard to Security Management Server / Domain Management Server. > > 9. Install the policy on the Connectra Gateway. ### Related documents {#Related documents} * Security Management Server Administration Guide ([R60](http://supportcontent.checkpoint.com/documentation_download?id=5510), [R60A](http://supportcontent.checkpoint.com/documentation_download?id=5578), [R61](http://supportcontent.checkpoint.com/documentation_download?id=6392), [R62](http://supportcontent.checkpoint.com/documentation_download?id=6825), [R65](http://supportcontent.checkpoint.com/documentation_download?id=7256), [R70](http://supportcontent.checkpoint.com/documentation_download?id=8745), [R70.20](http://supportcontent.checkpoint.com/documentation_download?id=10510), [R71](http://supportcontent.checkpoint.com/documentation_download?id=10315), [R75](http://supportcontent.checkpoint.com/documentation_download?id=11667), [R75.20](http://supportcontent.checkpoint.com/documentation_download?id=12277), [R75.40](http://supportcontent.checkpoint.com/documentation_download?id=13953), [R75.40VS](http://supportcontent.checkpoint.com/documentation_download?id=16301), [R76](http://supportcontent.checkpoint.com/documentation_download?id=22920), [R77](http://supportcontent.checkpoint.com/documentation_download?id=24830), [R80](http://supportcontent.checkpoint.com/documentation_download?id=46534) / [R80](http://supportcontent.checkpoint.com/documentation_download?id=46535)) * Multi-Domain Security Management Administration Guide ([R65](http://supportcontent.checkpoint.com/documentation_download?id=7251), [R65.4](http://supportcontent.checkpoint.com/documentation_download?id=8694), [R70](http://supportcontent.checkpoint.com/documentation_download?id=8741), [R71](http://supportcontent.checkpoint.com/documentation_download?id=10311), [R75](http://supportcontent.checkpoint.com/documentation_download?id=11683), [R75.20](http://supportcontent.checkpoint.com/documentation_download?id=12273), [R75.40](http://supportcontent.checkpoint.com/documentation_download?id=13950), [R75.40VS](http://supportcontent.checkpoint.com/documentation_download?id=16201), [R76](http://supportcontent.checkpoint.com/documentation_download?id=22916), [R77](http://supportcontent.checkpoint.com/documentation_download?id=24807), [R80](http://supportcontent.checkpoint.com/documentation_download?id=46532) / [R80](http://supportcontent.checkpoint.com/documentation_download?id=46535)) * Command Line Interface Reference Guide ([R60](http://supportcontent.checkpoint.com/documentation_download?id=5518), [R61](http://supportcontent.checkpoint.com/documentation_download?id=6354), [R62](http://supportcontent.checkpoint.com/documentation_download?id=6836), [R65](http://supportcontent.checkpoint.com/documentation_download?id=7239), [R70](http://supportcontent.checkpoint.com/documentation_download?id=8713), [R71](http://supportcontent.checkpoint.com/documentation_download?id=10324), [R75](http://supportcontent.checkpoint.com/documentation_download?id=11657), [R75.20](http://supportcontent.checkpoint.com/documentation_download?id=12264), [R75.40](http://supportcontent.checkpoint.com/documentation_download?id=13944), [R75.40VS](http://supportcontent.checkpoint.com/documentation_download?id=16262), [R76](http://supportcontent.checkpoint.com/documentation_download?id=22909), [R77](http://supportcontent.checkpoint.com/documentation_download?id=24833)) * Firewall Administration Guide ([R60](http://supportcontent.checkpoint.com/documentation_download?id=5716), [R61](http://supportcontent.checkpoint.com/documentation_download?id=6359), [R62](http://supportcontent.checkpoint.com/documentation_download?id=6821), [R65](http://supportcontent.checkpoint.com/documentation_download?id=7247), [R70](http://supportcontent.checkpoint.com/documentation_download?id=8738), [R71](http://supportcontent.checkpoint.com/documentation_download?id=10309), [R75](http://supportcontent.checkpoint.com/documentation_download?id=11660), [R75.20](http://supportcontent.checkpoint.com/documentation_download?id=12267), [R75.40](http://supportcontent.checkpoint.com/documentation_download?id=13088), [R75.40VS](http://supportcontent.checkpoint.com/documentation_download?id=16261), [R76 Firewall Admin Guide](http://supportcontent.checkpoint.com/documentation_download?id=22913) / [R76 Security Gateway Tech Admin Guide](http://supportcontent.checkpoint.com/documentation_download?id=23622) , [R77 Firewall Admin Guide](http://supportcontent.checkpoint.com/documentation_download?id=24832) / [R77 Security Gateway Tech Admin Guide](http://supportcontent.checkpoint.com/documentation_download?id=24836), [R80](http://supportcontent.checkpoint.com/documentation_download?id=46528) / [R80](http://supportcontent.checkpoint.com/documentation_download?id=46524)) * VSX Administration Guide ([VSX NGX R65](http://supportcontent.checkpoint.com/documentation_download?id=7944), [VSX NGX R67](http://supportcontent.checkpoint.com/documentation_download?id=10165), [VSX NGX R68](http://supportcontent.checkpoint.com/documentation_download?id=13188), [R75.40VS](http://supportcontent.checkpoint.com/documentation_download?id=16383), [R76](http://supportcontent.checkpoint.com/documentation_download?id=22932), [R77](http://supportcontent.checkpoint.com/documentation_download?id=24802), [R80](http://supportcontent.checkpoint.com/documentation_download?id=46537)) --- # Agent Instructions This content is from the Check Point Support Center (https://support.checkpoint.com), the official knowledge base for Check Point cybersecurity products. ## Navigating This Knowledge Base - **Complete index**: [llms.txt](https://support.checkpoint.com/llms.txt) - **All SK articles**: [SecureKnowledge Sitemap](https://support.checkpoint.com/sitemaps/secureknowledge-sitemap-index.xml) - **SK article URL pattern**: `https://support.checkpoint.com/results/sk/{skId}` - **Markdown responses**: AI bot User-Agents automatically receive `text/markdown` content