You can use the backed up ICAP Client configuration file from the R77.30 Security Gateway as a reference only.
You must explicitly confirm the disclaimer (run the script IcapDisclaimer.sh in the Expert mode).
To inspect the HTTPS traffic with the ICAP Client, enable the HTTPS Inspection and configure the HTTPS Inspection rules.
Install the Access Control policy on the R80.20 Security Gateway.
Note: If one of the ICAP configuration parameters is not configured correctly, SmartConsole shows an error with the name of the applicable parameter.
When you perform a clean install of an R80.20 on top of an existing previous version, the following error might appear after the keyboard layout selection screen:
Warning: /dev/sda contains GPT signatures, indicating that it has a GPT table. However, it does not have a valid fake msdos partition table, as it should. Perhaps it was corrupted - possibly by a program that doesn't understand GPT partition tables. Or perhaps you deleted the GPT table, and are now using an msdos partition table. Is this a GPT partition table?
In such case, select "Yes" several times to continue with the installation.
PMTR-32183, PRHF-2532, PRHF-2618
Upgrading Multi-Domain Servers in High Availability to R80.20 may fail with synchronization errors when a Domain exists on primary Multi-Domain Server but does not exist on secondary Multi-Domain Server, or when a Domain exists only in Secondary Multi-Domain Server (no High Availability in Domain level)
Resolved in R80.20 Jumbo HotFix Take 47. We recommend to run an advanced upgrade with latest Jumbo HF to avoid upgrade failure.
In the same MDM scenario, similar issues may occur post-upgrade when launching SmartUpdate in R80.20 without the resolution in Jumbo HotFix Take 47.
Interface that uses the tg3 driver is not able to set the speed to 1000 Mbit/sec in the following scenario:
The interface is connected to a 1000 Mbit/sec switch port
Disable auto-negotiation of the speed on the interface
Manually configure the speed on the interface to 10 Mbit/sec or 100 Mbit/sec
The speed on the interface is set at 10 Mbit/sec or 100 Mbit/sec
Enable the auto-negotiation again
The speed on the interface stays at the previous value of 10 Mbit/sec or 100 Mbit/sec
On oVirt virtual platforms, it is not supported to use the "kvm-clock" as the clock source (/sys/devices/system/clocksource/clocksource0/current_clocksource). This can cause the management processes to stuck in an endless loop with a very high CPU usage (almost 100%).
If the backup schedule is changed to an invalid date or time, all backup schedules are lost and "Backup schedule failed. The backup will not be scheduled" error message is displayed.
GAIA-3267, GAIA-2907, GAIA-2909
Hardware Diagnostic Tool is not supported using Disk on Key (USB).
If you change the members of a Gaia Cloning Group with many members down, you are logged out of the Gaia Portal with an incorrect error message: "Unable to connect to server". The correct message is: "An error occurred while applying configuration change to all cloning group members" - the operation was successful only for online members. This is the normal behavior of the cloning group. This error does not indicate a critical failure.
In some scenarios, when umounting an ext3 file system, Security gateway crashes with vmcore.
02559704, 02561586; 02561478, 02561588, PRHF-864
After adding the RBA roles Gaia commands (add rba role TACP-0 virtual-system-access all), the lines are missing from the "show configuration" command output, but the values can be seen in Expert mode (/config/active). Refer to sk119394.
In some scenarios, unable to create snapshots. Refer to sk123612.
Snapshot creation reaches 93% and stops, although there is enough space. Refer to sk119675.
Newly configured user (with UID that is not 0) is not able to log in from Gaia Clish to Expert mode on VSX Gateway. Refer to sk115221.
To upgrade an R77.30 Security Gateway with ICAP Server to an R80.20 Security Gateway:
Back up the current ICAP Server configuration files (to use as a reference only):
Important: You can use the backed up ICAP Server configuration files from the R77.30 Security Gateway as a reference only. In R80.20, the ICAP Server configuration is stored in the Management Database (for each Security Gateway object and the related Threat Prevention profile).
When Using a rule with legacy object, in or below a rule with one of the new features that are integrated in the unified policy, install policy on a Security Gateway fails with a verification message.
Workaround: change the order of the rules so that rules with legacy objects are above rules with new features.
"Get Interfaces" action on gateway returns error "Failed to save cpmi interfaces" if interface name includes space. Gateway interface names must not include spaces.
Once the Log server is down for a long period of time, the gateways do not try to reconnect to it and logs are being saved locally. Refer to sk116233.
When using the 'Drop' action in a layer for SMTP, HTTP, and FTP protocols with the Application Control and URL Filtering or Content Awareness blades enabled on the layer: if the Security Gateway matches a connection not on the first packet (for example, on a rule with an application) the gateway rejects the packet instead of silently dropping it. The gateway sends a TCP reset for HTTP/FTP or sends a '554 error message' for SMTP. The client already received some packets from the server before the rejection.
01593807, 02728705, 01683689, PRHF-66
SAM rules generate large amount of "fwsam_v1_filter: matched rule is not found" messages. Refer to sk105347.
TCP traffic fails to return from static NAT host when using ISP Redundancy and SecureXL. Refer to sk113236.
Logging session does not switch to the backup logging server after connectivity loss. Refer to sk118697.
Cannot create events based on "sys_message:" filter. Refer to sk119995.
In some scenarios, Security Gateway sends wrong format BSD Syslog logs. Refer to sk122952.
Threat Prevention / Threat Extraction
Threat Emulation blade, MTA and UserCheck do not apply Threat Prevention layer policy according to the strictest rule, but according to the order of layers.
On pre-R80.10 gateways managed by R80.x Security Management server, Access Roles and CloudGuard are not supported in all Threat Prevention and IPS rules on the gateway. This limitation does not apply to R80.x gateways.
02452806, 02454286, 02454288
The "Message-ID:" header of the original email is capitalized differently when Threat Extraction is enabled. Refer to sk115954.
02703712 02703689 02702724
AD testing generates core dumps. Refer to sk122472.
CRL validation is not supported in pure IPv6 environments (when IPv4 addresses are not configured on the Security Gateway's interfaces).
Application Control & URL Filtering
After upgrade, services defined in the Application Control rulebase are overridden with the Application's recommended services. Refer to sk109711.
The following apply to the "Archive File" Data Type: The Content Awareness blade inspects the "Archive File" Data Type. The "Archive File" Data Type is extracted, and its inner files are separately inspected together with the Data Type. Therefore, during the policy configuration, administrator has to pay attention when using the "Archive File" Data Type in a Compound/Group Data Type and in an Inline layer parent rule.
Using a Compound/Group of "Archive File" with, for example, "PCI - Credit Card Numbers", does not match the archive that contains a file with the credit card numbers. You can use a specific File Type with "PCI - Credit Card Numbers" in this rule.
Using the "Archive File" in a rule that leads to Inline Layer does not match the Data Type inside that layer. You can use a specific File Type in this rule.
If the "Archive File" is located above other Data Types, the lower rule can be matched for some of the inner files, in addition to the rule that contains the "Archive File".
Content Awareness supports HTML forms using URL encoding (also known as Percent-encoding). HTML traffic, encoded (binary to text encoding) as Base64 and NCR, is not properly inspected for content.
Content Awareness can inspect different types of files, of any size. A Web browser or FTP client may use several connections to upload or downloaded a file. For web browser this typically happens when downloading large PDF files from the Internet. In those cases, the Security Gateway inspects each connection separately. This may affect its ability to inspect text inside the file.
Binary Certificate *.cer files are not properly matched to the 'Certificates and Private Keys' Data Type.
02467456, 02338194, 02330606
Content Awareness supports HTTP, HTTPS, SMTP and FTP protocols on any ports and it is fully integrated with the Access Control unified rule base. Traffic over QUIC and WebSocket is not inspected. However, it is possible to use 'Quic protocol' / 'WebSocket protocol' in a new Application rule to either block or allow this traffic. Google Drive has its own internal methods within its protocol, therefore file downloads and uploads, from and to Google Drive are not properly scanned by Content Awareness. However, it is possible to use Google Drive in a new Application rule to either block or allow this traffic.
Content Awareness supports more than 60 character sets for text files, including Japanese, Korean, Greek, and Arabic. If the inspected traffic does not include a supported character set, Content Awareness uses UTF-8 for decoding. To see the list of supported charsets, and to learn how to change the default charset, see sk116155.
Content Awareness supports Data Types based on file name. In specific HTTP traffic where the file name is not part of the URL or content-disposition header, the file name may be incorrect.
IPS is not supported on Dynamic IP Gateways after upgrading to R80.10 or R80.20 GA.
Core Protections are activated according to the Confidence/Severity/Performance impact and not according to IPS tags.
Some IPS protocols from early releases are discontinued. If these are mistakenly included in the Firewall Rule Base, policy installation will fail. For the list of Deprecated protocols and services that are no longer used by the IPS blade, refer to sk103766.
For pre-R80.10 gateways, when configuring a Threat Prevention rule to save packet captures, the packets are saved only for Anti-Virus and Anti-Bot. Packet capture is not activated on IPS.
Use the IPS Protections window to configure packet capture for individual IPS protections.
IPS blade is automatically enabled on R7X Security Gateway during policy installation from R80.X Management Server, although IPS blade is disabled in the Security Gateway object. Refer to sk121152.
Thresholds for 'IPS Bypass under load' are not tunable in Full HA environment. Refer to sk112659.
"Internal error occured" message when trying to assign/reassign a Global Configuration at the same time that an IPS update is running on a local Domain.
Workaround: First run the IPS update on the local Domain. Then assign/reassign the Global configuration.
DLP can apply visible or hidden Watermark (for forensic tracking) to Office Open XML formats (DOCX, PPTX and XLSX) as a rule action in a DLP rule base. Refer to sk117413 if DLP Watermark is used.
In some scenarios, DLP fals to synchtonize a very large files between cluster members, causing failover. Refer to sk122258.
In R80.20, SAM is supported only for non-accelerated usage. Traffic connected to the Acceleration-ready 10G Interface Card (CPAC-ACCL-4-10F-21000) will be handled by the host. 10G Ports on the CPAC-ACCL-4-10F-21000 cannot be assigned as SAM ports in R80.20.
02541089, 02551724, 02541431
Security Gateway freezes / crashes in rare scenario when SecureXL is enabled and multicast routing is configured. Refer to sk119299.
R80.20 ClusterXL does not support Load Sharing mode. Therefore, R80.20 SmartConsole blocks such configuration with a warning message.
This limitation is planned to be resolved during H2 2019.
The ICAP Server feature is not supported in VSX mode deployment.
If you enabled the ICAP Server or MTA feature in the Security Gateway / Cluster object, then to disable all the Threat Prevention blades (IPS, Anti-Virus, Anti-Bot, Threat Emulation and Threat Extraction), you must first disable the ICAP Server or MTA feature.
Otherwise, SmartConsole shows this validation error: "One of the targets specified in a Threat Rule 'Install On' field doesn't comply with the field's conditions. Either enable one of the Threat-Prevention blades on the gateway, or remove it from Threat-Prevention policy, see usages using 'Where Used'"
In PIM Dense Mode, when a new PIM router joins the existing network, it may take up to two cycles of PIM prune timer and/or downstream IGMP report interval, for the intended multicast traffic to start flowing.
To improve the PIM-DM responsiveness, user can enforce the local-groups / static-groups configuration.
PIM is not supported on a Security Gateway / Cluster, when Route Based VPN is configured.
When advertising IPv4 routes over an IPv6 BGP session, one of the following needs to be true:
Routemap is used to set the nexthop of the IPv4 routes
The interface used for the BGP session needs to have an IPv4 address
When advertising IPv6 routes over an IPv4 BGP session, one of the following needs to be true:
Routemap is used to set the nexthop of the IPv6 routes
The interface used for the BGP session needs to have an IPv6 address
On a Security Gateway that is configured with DHCP relay and automatic Hide NAT for the network(s) that the DHCP requests come from, DHCP offers are dropped at the gateway. This message shows: fw_log_drop_ex: Packet proto=17 18.104.22.168:67 -> 22.214.171.124:67 dropped by fw_conn_inspect Reason: post lookup verification failed;
Workaround: before the Hide NAT rule, add a NAT rule that prevents the translation when traffic is on port 67, and is going to the DHCP server. Make the NAT similar to this:
Original Packet: Source = Source network(s) for DHCP requests Destination = DHCP server Service = UDP_bootp
Translated Packet: Source = Original Destination= Original Service = Original
Fast failback with OSPF GR is not supported. A restart or failover during GR results in traffic outage.
To prevent: wait for OSPF GR to finish. Use "show ospf interfaces" or "show ospf summary" commands to see the status.
BGP routes cannot be used to establish connections to Multi-hop peers.
If the interface is deleted from the SmartDashboard without deleting the associated cluster VIP, the routing daemon has no way to delete the VIP later on.
Do not delete an interface before deleting the associated cluster VIP from the SmartDashboard.
IPv6 ECMP is not supported.
Workaround: disable ECMP for BGP when using IPv6.
In VRRP mode, the OSPF state is not synchronized and a new master cannot take the helper responsibility from the previous master.
To prevent: do not fail over members if an OSPF neighbor is in the process of restart.
A change in topology can cause an unsuccessful exit of OSPF GR.
To prevent: make sure there are no route or topology changes during the process.
In VSX, BGP Multihop does not work correctly when configured on a Virtual Router. Do not configure it.
RouteD with BGP Multi-hop consumes 100% CPU. If RouteD gets a route to the BGP peer from the peer itself and that route has a lower rank than the route used to establish the BGP connection then this route becomes active and routed starts using it to connect to the peer. This causes the BGP peer route to be deleted and return back to the original route since in BGP Multi-hop routed cannot use BGP routes to connect to peers. This scenario repeats endlessly and causes the high CPU utilization.
To prevent: make sure that self-routes do not become active in a BGP Multi-hop deployment.
DHCP Relay traffic is dropped when running Unicast load-sharing cluster. Refer to sk121347.
If you use Outlook Anywhere application with Mobile Access Reverse Proxy, and then want to disable Outlook Anywhere or Reverse Proxy, perform:
Delete Outlook Anywhere rule from reverse proxy.
Run "cvpnrestart --with-pinger" to close all Outlook Anywhere open connections. If you do not perform step 2, open connections of Outlook Anywhere will not be closed and users can still work with it.
When using Mobile Access file shares with VSX, the DNS resolving of the hostname might not work correctly with file shares.
Make sure that the /etc/resolve.conf file is configured properly or use this workaround: Change the value of 'vsxMountWithIPAddress' property in $CVPNDIR/conf/cvpnd.C file from 'false' to 'true'. The file share will use the host IP address for the mount instead of the hostname.
After upgrading a Standalone (Management and Gateway) or VSX deployment with Mobile Access blade enabled, the "Allow Dynamic ID for mobile devices" option might be enabled by default, even if Dynamic ID was not configured prior to the upgrade.
If you do not want Dynamic ID authentication for Capsule Workspace users, disable it in: Gateway Properties -> Mobile Access -> Authentication -> Compatibility with Older clients -> Settings -> Capsule Workspace section -> clear Enable DynamicID.
For VSX, this configuration is done per Virtual System.
The Mobile Access Portal does not support Web-Form SSO for Citrix StoreFront Web interface.
Mobile Access Portal users who use Outlook Web Access 2013 in the portal with NTLM authentication get authentication messages similar to: "Authentication Required https://mab-portal-addr requires a username and password". Refer to sk115936.
Internet Explorer 9 does not allow the HTML5-based new user interface of Mobile Access File Sharing. If you attempt to use IE9, the Security Gateway uses the old UI for File Sharing.
When users are connected to the Mobile Access Gateway with SSL Network Extender in Application Mode, Downloaded-from-Gateway applications do not work inside Endpoint Security On Demand Secure Workspace.
Multiple authentication schemes or realms that were configured in GuiDBedit do not persist after an upgrade to R80.10/20. Refer to sk115856.
When Mobile Access is included in the Unified Access Policy, in Mobile Access Authorization logs -> Log Details -> Matched Rules, the Mobile Access Application name and Category do not show.
Mobile Access Portal supports Outlook Web App 2013 / 2016 only with the Path Translation (PT) method. The Hostname Translation (HT) method is supported when cookies on the endpoint machine are configured. The URL Translation (UT) method is not supported.
Occasionally on Windows XP, the desktop background inside SecureWorkspace might appear distorted.
Untranslated links in iNotes Web Application when using Hostname Translation. Refer to sk118037.
01184657, 01356327, 01913441
Disabling the Floating Navigation Bar (FNB) via GuiDBedit Tool does not disable the FNB in the Web Application. Refer to sk109254.
Mobile Access does not support viewing or editing files with 'Office Online apps', Microsoft's browser-based Office applications. Outlook Web Access is supported, however you cannot open or edit Office Online app files from emails.
Granular IPsec encryption range tables subnet_for_range_and_peer and max_subnet_for_range, may not be enforced after gateway upgrade to R80.20. Refer to sk144094.
Communication errors occur between the Security Gateways managed by R80.20 M1 Multi-Domain Server and participating in Global VPN Communities when there are more than one certificate for the same Internal CA. Refer to sk136972.
If a Remote Access VPN client roams from a NATT tunnel (which the Security Gateway accelerates) to a TCPT tunnel (which the Security Gateway does not accelerate), all the existing accelerated connections from the Remote Access VPN client are terminated on the Security Gateway. New connections from the Remote Access VPN client are established as expected.
When using Trusted links, encrypt and decrypt logs are issued even though the traffic on the links is not encrypted.
The VPN client shows as "Not Compliant" when it is not compliant according to the local.scv file, even if SCV is disabled.
Workaround: Configure the VPN site again on the client.
NAT-T initiator is not supported on VSX Gateways.
Convert Traditional VPN to Simplified is not supported.
01311326, 01455241, 01357377
When using a VPN client, activity logs are not generated for ICMP traffic.
R77.30 and lower gateways do not support R80.10 gateways that are configured as NAT-T initiators. The R77.30 and lower gateways only recognize 3rd-party devices for NAT-T initiation.
02514005; 02534915; 02529275
DAIP devices deployed as VPN Satellite gateways, do not support VPN link fail-over between a static link (using permanent IP address) to the DAIP link, and vice-versa.
Trusted interfaces are not supported for DAIP devices.
Client Setting "Calculate IP based on topology" breaks when using host. Refer to sk120121.
02564111, 02565222, 02590209
MTU on VPN traffic is limited by MTU of 1500. Refer to sk120122.
Unable to connect with SHA-512 user certificate on Windows Capsule. Refer to sk121418.
Security Gateway accepts an other Diffie-Helman group then is configred. Refer to sk122438.
RADIUS authentication fails for LDAP users as the gateway uses sAMAccountName and not UPN when UPN is needed. Refer to sk122477.
The HP ProLiant DL380 Gen10 does not detect all USB devices, including various USB flash drives (regardless of its content). This is not a software issue. If a bootable USB device (with Check Point Gaia, CentOS or any other OS) is not recognized by this server, try a different USB device vendor.
Policy verification fails if the policy contains GTP or Diameter services, and you install it on an R80.20 Security Gateway. Refer to sk120141.
SCTP or Diameter objects cannot be the service of a manual NAT rule. Static NAT will still be applied for rules that match SCTP if the service is set to "Any". All NAT methods can be applied for Diameter over TCP traffic if the service is set to "Any".
Explicit conversion is not supported.
01298013, 01347319, 01356763
The "vsx_util reconfigure" command fails with "Failed to fetch configuration information from". Refer to sk98001.
An upgraded cluster member goes into Ready state after the reboot, even before the rest of the cluster members are upgraded.
Run the cphaprob state command to verify that all the Virtual Systems are in Ready state.
Run the ps -elL | grep fwk command to verify that fwk process is running on every Virtual System.
In SmartView Monitor, Firewall History and System History system counters do not show any data.
The "vsx_util change_mgmt_subnet" command does not support IPv6.
"CLINFR0699 Invalid command" error when a user with read-only Gaia OS role runs the "set virtual-system" command on VSX Gateway. Refer to sk118693.
VTI interfaces are not supported in VSX mode.
If a Virtual System is the Hub of a Star VPN Community, it cannot support SmartLSM gateways as satellites.
"vsx_util reconfigure" command on Security Management Server / Domain Management Server fails to resume with "Error: Interface 'Interface_Name' exists in the management database, but not on the gateway". Refer to sk105441.
Convert QoS from Express to Traditional is not supported.
02563501, 02567776, 02567790
No warning is displayed if an empty network group object appears in the source or destination column.
Avaya VoIP calls with Avaya Call Manager fail through Check Point Security Gateway. Refer to sk104786.
02721664, 02724294, 02726397
Several OIDs are in DisplayString format, while representing numbers. Refer to sk123452.
SNMP is not supported on Multi-Domain Management / Multi-Domain Log servers.
"No Such Instance currently exists at this OID" error message after installing R77.30 Jumbo Hotfix Take_225. Refer to sk117353.
Output of the "snmptranslate" command returns different OIDs for objects in "chkpntTrap" branch. Refer to sk108697.
List of R80.20 Security Management Products Known Limitations
Table of Contents
Installation and Upgrade
Multi-Domain Security Management
Management High Availability
SmartConsole / Management Console
Logging / SmartLog
Endpoint Security (SmartEndpoint)
CloudGuard for NSX
Enter the string to filter the below table:
Found in version
Installation and Upgrade
After you upgrade Management Server, or dedicated Log Server / SmartEvent to R80.20.M1:
Only logs from the last 24 hours indexed. You can see all previous logs by opening the log file in SmartConsole.
New logs are indexed as expected according to the settings in the Management Server or Log Server / SmartEvent object -> Logs.
It is not supported to perform a Clean Install of R80.20.M1 Security Management Server or Multi-Domain Security Management Server in CloudGuard for Amazon Web Services (AWS), Microsoft Azure, Google Cloud Platform (GCP), or any other cloud providers.
It is not supported to upgrade to R80.20.M1 a Security Management Server or Multi-Domain Security Management Server that runs in CloudGuard for Amazon Web Services (AWS), Microsoft Azure, Google Cloud Platform (GCP), or any other cloud providers.
To upgrade a Secondary Multi-Domain Server from R80.20.M1 to the next version, users must perform a clean install of the next version on their Secondary Multi-Domain Server and connect it to their next version Primary Multi-Domain Server.
To upgrade a Multi-Domain Log Server from R80.20.M1 to the next version, users must perform a clean install of the next version on their Multi-Domain Log Server and connect it to their next version Multi-Domain Server.
To upgrade a secondary Security Management Server from R80.20.M1 to the next version, users must perform a clean install of the next version on their Secondary Management Server and connect it to their next version Security Management Server.
Database Revisions are not kept when upgrading from R80.20.M1 to the next version. Refer to sk137677.
To upgrade an R80.20.M1 Multi-Domain Management Server with configured Global Policies to the next available version:
Connect with SmartConsole to the Global Domain on your R80.20.M1 Multi-Domain Server.
Reassign all Global Policies to all applicable Domains.
Do not publish any changes in the Global Domain until you complete the upgrade to the next available version. Note: This is necessary to avoid any potential issues caused by different policy revisions on the Global Domain and on the Domains.
Perform the upgrade from the R80.20.M1 to the next available version.
After upgrading to R80.20.M1 with CPUSE on Smart-1 525/5050/5150 appliance, in order to downgrade to R80.10, revert to the snapshot taken before the upgrade. Users MUST manually take a Gaia OS Snapshot before upgrading to R80.20 M1 on Smart-1 525/5050/5150 appliances.
R80.10 supports only ext3 & ext4 file systems on Red Hat Enterprise Linux.
02411778, 02421533, 02421989
After upgrading a Full HA deployment, policy installation fails due to SIC problem with the secondary member.
To resolve, re-establish SIC between the active and standby members.
After upgrade, the "Gateways & Servers" view does not show version numbers in the Version column.
To see the version numbers, open the gateway object for editing, make sure the correct version is selected and click OK.
After upgrading to R80.10, there is no visible way to switch between Classic mode and Wizard mode to create a Security Gateway object. New gateways can only be created depending on the setting in Global Properties -> SmartDashboard customization prior to upgrade. To restore both options:
Close all SmartConsole windows.
Connect to Security Management / Domain Management Server with GuiDBedit Tool.
On the Tables tab, open Global Properties -> Properties.
Select the firewall_properties object.
In the Field Name column, select "hide_use_CP_GW_wizard".
Change the value to false.
After upgrade, SmartConsole disconnects from the server during the first policy install.
Before a first policy installation on Standalone servers, allow the CPM service in the Services & Applications column of the rulebase.
Importing a large SmartEvent database can take a long time to complete. Check the upgrade status for progress.
Database Revisions are not upgraded to R80.x Security Management Server during the upgrade process from Pre-R80 versions.
In R80.x, indexing is done by a new process called Indexer. Indexer works similar to SmartLog R77.xx but has its own configuration files stored in $INDEXERDIR. Customers who defined manually indexing configuration from remote log servers (via LEA) in SmartLog R77.x or below, should manually move them to the new configuration files.
To copy settings from SmartLog R77.x configuration files to the new Indexer process configuration files: For SmartLog servers only: After upgrading to R80.x, copy the remote log servers configured in $SMARTLOGDIR/smartlog_settings.txt file to $INDEXERDIR/log_indexer_custom_settings.conf.
For SmartEvent with SmartLog server: Remote log servers configured in $SMARTLOGDIR/smartlog_settings.txt are not automatically upgraded. Manually configure the log servers in SmartEvent GUI -> correlation unit policy.
"Database is locked" error message when running the migrate_export command on a R7x Security Management.
Run cpstop or mdsstop and attempt the export again to resolve.
SmartEvent blade disabled after advanced upgrade to R80.20 M1 Management.
On the Security Management server, run "evconfig" to enable the SmartEvent server.
Gaia OS: Clean install from USB device fails on Open Server because the installation process (anaconda) includes the USB installation media as part of the installation target. Refer to sk100566.
After upgrading, the Gateway Properties -> HTTP inspection page shows "Failed to load Plug-in Page: SSLInpectionPage".
To resolve, perform the following on the Security Management server:
Delete the $FWDIR/conf/newDleSchema.xsd file
If you have gateways of different R77 versions and GX is enabled on a R77.30 Security Gateway only, policy installation will fail.
Use the "Install On" column for the GTP rules.
The Linux "iotop" utility might stop working when pressing the "i" key in the following rare scenarios:
Working in virtual environments (such as Hyper-V)
Terminal application uses specific virtual terminal settings (such as specific SecureCRT terminal settings)
The "scponly" shell (a limited shell for secure file transfers) is not included in R80.20.M1. Other shells can be used instead - see the /etc/shells file.
"[Firmware Bug]: the BIOS has corrupted hw-PMU resources" message may appears in the output of "dmesg" command on any HP ProLiant Server running Gaia R80.20.M1.
You can safely ignore this message - it does not indicate an issue with the functionality or performance of the Operating System or the server. For details, see Hewlett Packard Enterprise Customer Advisory c03265132.
Intel 10Gbps Network Interface Cards might not be visible during OS installation however they will be available once OS installation completes.
Saving the Hardware Diagnostic Tool logs to a USB stick is not supported if the USB stick is formatted as NTFS.
Configuring Static ARP entries in R80.20.M1, either in Gaia Portal or Gaia Clish, is not supported.
R80.20 Management Feature Release does not support SAN card.
The Maintenance -> Maintenance page in the Gaia Portal was removed.
When connecting to the network interfaces page in the Gaia Portal, an "Unable to connect to server" error shows.
To resolve, disable the Adblock EasyPrivacy extension of the Adblock plus add-on and try again.
External NIC is not detected after upgrade to R80.x / clean install of R80.x. Refer to sk116587.
If you refresh the browser while running the First Time Configuration Wizard, or try to run the wizard twice, one of these messages will show:
"Cannot install Check Point Security Management Server. Incompatible hardware"
"Internal Error: Cannot install Check Point Security Management Server"
"Cannot install Check Point Security Management Server. Please contact Check Point Technical Support."
After seeing one of these messages, you must reinstall the device or revert to the factory image.
Gaia Clish "load configuration <file>" command fails to load some RADIUS and SNMP configuration commands. Refer to sk120459.
In Gaia Portal, PPPoE interfaces cannot be used as an SNMP agent interface. In Clish, if the user runs the command "add snmp interface", the operation does not succeed but the user does not see a message that it failed.
The last stage of the First Time Configuration Wizard takes a long time on some machines. To see the progress of the First Time Configuration Wizard, the user must check if these files were created on the machine:
/etc/.wizard_accepted - means that the First Time Configuration Wizard has finished.
/var/log/ftw_install.log - means the First Time Configuration Wizard has started and the user must wait until the file /etc/.wizard_accepted is created.
RADIUS user with special characters in a class attribute field is stuck on the spinning icon when logging into the WebUI.
02490383, 02491329, 02491797
Multicast PIM traffic register packets are sent with checksum 0xd63f that non-compliant with RFC (should be 0xdeff).
The "show asset" command does not display the network information. Refer to sk123342.
Gaia OS sets the timezone to "UTC" when the zone is entered with a space character in the "sysconfig" menu. Refer to sk117737.
The "show message motd" Clish command output is corrupted. Refer to sk122199.
01816080, 01822237, 01822236
DHCP Relay and DHCP Server do not function when configured together on the same Gaia OS.
Between DHCP Relay (routed) process and DHCP Server (dhcpd) process, the last process to start up will receive all the UDP unicast traffic. The first process sees no unicast traffic.
Both DHCP Relay (routed) process and DHCP Server (dhcpd) process will see UDP broadcasts.
If DHCP Server (dhcpd) process starts first, then this joint configuration will work, because dhcpd process only cares about UDP broadcasts. If DHCP Relay (routed) process starts first, then this joint configuration would fail to work, because the replies from DHCP Server that should be relayed are UDP unicasts.
Setting state of interface to "off" on Gaia OS does not turn off the link on that interface. Refer to sk112598.
"WARNING The following features: NameOfFeature, , provide a privilege level equivalent to that of 'adminRole'" message in Clish when adding some read-only commands to RBA role. Refer to sk110772.
The /var/log/messages file is filled with Audit Logs for Gaia Clish commands: clish[PID]: user logged from admin clish[PID]: cmd by admin: Start executing : xxx (cmd md5: ...) clish[PID]: cmd by admin: Processing : xxx (cmd md5: ...) clish[PID]: cmd by admin: Start executing : exit (cmd md5: ...) Refer to sk113897.
Hardware Diagnostic Tool test fails on "Self-test" for 1GbE expansion cards when an SFP transceiver for RJ45 (Copper) is connected to the appliance. Refer to sk112857.
01111060, 02356903, 01309032
Saving the configuration on Gaia OS times out with "NMSCFD0026 Timeout waiting for response from database server" error. Refer to sk113746
Syslog Protocol version is not sent in syslog packets as per RFC 5424. Refer to sk100727.
If you restore a Security Management Server from a backup, all hotfixes installed after the backup was created will not be included on the restored server. Refer to sk91400.
These products do not support the new licensing visibility features:
Network Security: Advanced Networking and Clustering, Capsule Cloud and Capsule Workspace.
Security Management: Endpoint Policy Management, SmartPortal, User Directory (LDAP).
Multi-Domain Management: Security Domain
Remote Access & Endpoint
"Licensing status not available for current OS" message shows in the Logs & Monitoring view. SmartConsole does not support licensing information for Windows, SecurePlatform and Virtual Systems. Use the licenses tab in SmartUpdate to see the licensing information for the OS.
If the SmartEvent Software Blade is activated, but only the SmartEvent Intro license is installed, the License Status shows "N/A".
The Device and License Status of Threat Emulation is incorrect. Use the Logging -> License Status view.
When loaded for the first time, web components such as the licensing or monitoring view can take up to thirty seconds to show.
In the License Status View, the Additional Info column, quota information and quota statuses are not available for pre-R80 gateways and servers.
Automatic license activation on Check Point appliances is not available on pre-R80 appliances.
On pre-R80 gateways, license information is updated every 20 minutes. To force a license update, perform one of the following actions:
Either install security policy on the pre-R80 gateway
Or on the R80.10 Management Server, run the following command in Expert mode:
On Security Management Server:
[Expert@HostName]# $CPDIR/bin/esc_db_complete_linux_50 bc_refresh <Name of Target Object>
On Multi-Domain Security Management Server:
[Expert@HostName]# mdsenv <Name of Domain Management Server> [Expert@HostName]# $CPDIR/bin/esc_db_complete_linux_50 bc_refresh <Name of Target Object>
Automatic license activation on a Multi-Domain Management Server machine works only on the MDS level and not on the Domain level. Add licenses manually for each Domain.
Login to primary Domain SmartConsole fails with "Database is locked by another application" error.
To resolve, run the cprestart command on the Management Server.
After installation, the Device License Status shows N/A and the Device License View is not accessible until policy or database are installed. When blades are enabled or disabled, the changes are not visible in the Device License Views and Status until policy or database are installed.
The proxy that synchronizes license information with the User Center, must be at least R80 server.
On a Pre-R80 SmartEvent NGSE dedicated machine, license information is not automatically updated when Installing Database.
When you enable or disable a blade, one of the following will update the license information with the change:
If you force a license update, changes occur immediately. To force a license update: On the R80.10 Security Management Server, run the following command in Expert mode: [Expert@HostName]# $CPDIR/bin/esc_db_complete_linux_50 bc_refresh <Name of Target Object>
Automatic update at midnight
If you manually change a license or contract on a dedicated machine, changes take effect within 20 minutes
"cat: /proc/self/vrf: No such file or directory" message is displayed for a short period of time when running cpview.
This is a cosmetic issue and has no affect on the system.
Exporting R80.20 database using migrate_server export may result with a "Failed to export: Export failed." or "Failed during export process" error message. For details see sk142752.
Login to the Secondary Management Server can fail if the SIC certificate is pushed to the Secondary Management Server before its CPM server is up. In this case, the SIC is established, but the login to the Secondary Management Server fails until the CPM server is restarted and reloads the new certificate.
To resolve, wait until the CPM server is up, before you establish trust with the Secondary Management Server. This way, the CPM Server restarts automatically due to the SIC establishment and the login succeeds.
R80.20 Management Server does not support R75.40VS Security Gateways (other R75.X versions are still supported as described in the R80.20 Release Notes).
An administrator fails to log in with SmartConsole after another user was configured in SmartConsole with a name identical to that administrator's name and the session was published. Refer to sk133273.
R80.20 Gateways cannot be managed by R80.20.M1 Management Server.
"Publish failed" error on Publish / Discard operation failure after switching the Primary Management Server from Active to Standby and back to Active in Management HA deployment. Refer to sk129952.
If a connection is matched on a limit action rule, and the connection is not configured to be rematched (the 'Keep all connections' option is selected in the Security Gateway object, or the 'Keep connections open after the policy has been installed' option is selected in the Service object), a new policy installation will cause the limit on the connection not to be enforced.
Memory leak in fw_commandline_cmd_sig function.
Management High Availability is supported only between Management High Availability servers with the same build number. To see the build number, run cpinfo -y FW1
Policy installation using management API partially succeeds when it should fail. Refer to sk122211.
After upgrading to R80.x, SmartConsole login fails if there is an internal user with the same name as the administrator login name.
To resolve the conflict:
Open a command prompt on the Management server
Run cpconfig to create a new administrator account with a unique name
When the trial license is expired, and after adding a new license, the Security Management server does not accept any connections.
Workaround: stop and start the server (run cpstop;cpstart) after adding the new license.
In some scenarios, re-assign or removal of global assignments succeeds, but changes that were not yet published at the Domain become conflicted. The SmartConsole for the Domain becomes unstable and can show: "Could not load selected policy".
In this situation, Discard the changes that were not published in SmartConsole.
When removing Threat Prevention from a Policy package, SmartConsole disconnects from the Security Management Server.
Workaround: delete the rules from the Threat Prevention policy before removing Threat Prevention from the policy package.
"Revert exception" error and log of: "ManagementPlg.RevertToRevisionCommand - Unable to extract targetWorkSessionId from parameter" when removing a blade that is used in rules from an Ordered Layer, and then reverting revisions.
Policy installation fails with "Policy installation failed on gateway 0-2000040" error and log: "fw_atomic_add_spii_parameter: Failed to get object named <object_name>".
Workaround: for all hosts with a server configuration, unselect the servers. Publish the session, then select the servers again, and publish again. For details refer to sk131192.
If you create an administrator in cpconfig, you must run cpstop and cpstart, as instructed by cpconfig. After cpstart, no administrators are shown in cpconfig. Administrators configured before the upgrade to R80 are also not shown in cpconfig.
Manage administrator accounts through SmartConsole.
Internal user names must contain only English characters. Names in other languages (unicode) will show as question marks in the Users and Administrators window.
If you create or delete Domain servers of the same Domain from many Multi-Domain Servers, the Domain can become corrupted, with recovery from Check Point Support required.
"Check your connection settings (Proxy, DNS and gateway)" error shows after IPS and Application Control & URL Filtering update fails if there is no proxy defined.
To resolve the problem, run cpstop and cpstart and try again.
Fail to add a VSX objects (router, switch, or system) from the secondary Multi-Domain Management Server when the primary server is powered off. The creation wizard fails to open and an "Operation finished successfully message" shows.
To resolve the issue, power on the primary Multi-Domain Management Server and try again.
When selecting the "Use Gaia administrator: admin" option in the First Time Wizard, it lets to reuse the Gaia administrator password for SmartConsole. If you later change this password in SmartConsole, the Gaia administrator password remains unchanged.
The Revisions View is not updated for changes in Trusted Clients and some environment settings in Management & Settings.
These commands are not supported in the SmartConsole's CLI: login, logout, discard and publish. Use the SmartConsole GUI instead.
Applications like Provider.exe and Fwpolicy.exe (SmartDashboard) cannot be used to connect directly to the Security Management server or the Multi-Domain Security Management server.
Workaround: use SmartConsole.exe
It is not possible to convert a Standalone deployment (Security Gateway and Security Management on one computer) to a cluster member of a Full HA deployment - or vice versa.
SIC is not allowed by default with upgraded OPSEC applications (OPSEC applications not compiled with SHA-256 support). To fix:
On the Security Management server, run: cpca_client set_sign_hash sha1 (refer to sk103840)
Changing the Security Management server's time, for example using an NTP server, while there are SmartConsole clients connected, may cause the client to disconnect from the server.
For Gateways below R80, 2nd layer behaves like Application Control policy.
Security Gateway / VSX gateway conversion, or conversion in the opposite direction, is not supported.
lvm_manager fails to resize partitions with "ERROR :Cannot kill process (id XXXXX)".
Workaround: Boot the machine into Maintenance Mode and then run lvm_manager.
"Internal error occurred during the verification process" during policy installation after reverting to a previous policy revision that has a disabled rule with an object that has been deleted since then. Refer to sk110614.
The CLI command fwm dbexport is not supported. After running the command to export the user database, the process finishes successfully but the file contains only headers, no data.
Workaround: Use migrate export
Global assignment removal fails with "Object could not be deleted because it is referenced by other objects" error. If the search fails to locate the object in the domain, check each application object in the Domain for a reference to the permission profile specified in the error message. Refer to sk110630.
In some scenarios, CPD process stops working on Security Management server.
Creating secondary CMA/Domain overrides files in $FWDIR/lib/ directory оn the primary CMA/Domain. Refer to sk122538.
"Authentication to server failed" error shows when logging in to the SmartEvent server using the local administrator account (created in cpconfig).
Create a new administrator account with a name not used on the remote Security Management server or the Multi-Domain Management server managing the SmartEvent server.
If you upgrade a Security Management Server to R80.10 with a user.def file that has been edited manually, make sure that the file name includes each gateway version that is managed by the server. Refer to sk98239 for the user.def naming convention. Refer to sk30919 for more information about the user.def file.
00419335, 01134550, 01648694
The $CPDIR/tmp/ directory is filled with 'CKP_mutex::_opt_CPsuite-RXX_fw1_log__...' files.. Refer to sk36754.
02167186, 02169523, 02483407, 02496644
The "URL" field shows "*** Confidential ***" in HTTPS Inspection logs on 3rd party LEA OPSEC client. Refer to sk101570.
Policy installation fails on Security Gateways R76 and above, if the "RTP-RTCP" service exists in the Security Management Server database.
To resolve, delete this service completely from the Management database (in SmartConsole, go to Objects menu -> Object Explorer -> Services).
Multi-Domain Security Management
Upgrading a Multi-Domain Management Server with a Global VPN Community from R80.20.M1 to R80.20, from R80.20.M1 to R80.20.M2, and from R80.20 to R80.20.M2, is not supported.
Upgrade of a Multi-Domain Server from R80.20 GA to R80.20.M2 is not supported if Install Policy Presets are used. Refer to sk142132.
When reverting a Multi-Domain Server / Multi-Domain Log Server from the version R80.20 GA to R80.20 M1, it will cause reindexing of the logs based on the value of "days_to_index" (default is 1 day; see sk127652 and sk111766). The reindexing will cause duplicated entries for some of the records in the index.
In Multi-Domain Servers Management HA environment, if Administrator installs policy from the Active Domain on the Security Gateway / Cluster object and performs Management HA from the Active Domain to the Standby Domain, Administrator must install policy from the new Active Domain on the Security Gateway or Cluster object. Otherwise, when upgrading the Multi-Domain Servers to R80.20, SIC communication can be lost with the Security Gateway or Cluster Members.
Workaround: Change the state of the Standby Domain to the Active, and manually synchronize the Domains.
Before upgrading Multi-Domain Management Servers in High Availability deployment, all Domain Management Servers on the Primary Multi-Domain Management Server must be in the Active state.
PMTR-21282, PMTR-27321, PMTR-21709, PMTR-21787
CPView is not supported on Multi-Domain Security Management environments.
"Can not start the operation. You should disconnect all GUI Clients from this Security Management Server." error message when runing the MDS backup. Refer to sk142534.
To perform "Enable Global Use" on a Security Gateway, you must set the Domain, which manages this Security Gateway, and the Global Domain to the "Active" state on the same Multi-Domain Management Server.
R80.20.M1 and R80.20 GA Multi-Domain Security Management does not support IPv6 address configuration.
Threat Prevention policy fails to open with the "Rulebase initialization failed" and "One or more errors occurred" error message after upgrade of Multi-Domain Server to R80.20.M1.
Assign the Global Policy (without assigning or installing other policies).
Open the Threat Prevention policy.
Remove the assignment of the Global Policy.
In case of license expiration on one of the servers of a Multi-Domain Management High Availability setup, a full sync is required after applying the new license.
"Failed to save object....Server error is: An internal error has occured. (Code: 0x8003001D, Could not access file for write operation)" error when creating a Security gateway object on the Domain Management Server that is currently active on the secondary Multi-Domain Management server.
To resolve, run the "mdsstop ; mdsstart" commands on the secondary Multi-Domain Management Server.
When running Global Domain Assignment on one Multi-Domain Server for a Domain that is active on a different Multi-Domain Server, the task can stall at 5%. After a few minutes a message shows : "timeout during task progress: Could not get information regarding task completion from MDS_1 'MDS_2'.
Workaround: Run Reassign Global Assignment on the Domain from the first or second Multi-Domain Management Server.
If two administrators create an admin account with the same name, after the first admin publishes a session, the second admin will not be able to publish or edit the admin account.
To fix, the session changes must be discarded.
If you have a tag on the local host object of a global Dynamic object, you cannot assign or re-assign Global Policy.
Workaround: remove the tag from the local object, assign or re-assign Global Policy, and then add the tag again.
For Global SmartEvent connected to Multi-Domain Management Server, search suggestions from SmartConsole appear only for a Super user (Multi-Domain Super User and Domain Super user).
The ability to edit the list of additional information fields that can be added to a Domain, administrator, and gateway is not supported in R80.10.
The ability to find and unify similar Permission Profiles is not supported.
A Security Management server cannot be installed as a secondary Management for a Domain server.
Domain Super User profile cannot be cloned.
There is no cross-Domain search for network objects. Search in each Domain for the specific network object.
After a Global policy has been assigned to a Domain, the revert option in the Domain "Network Layer -> History" window no longer functions.
You cannot assign only the Global objects used in a specific Access Control policy or Threat Prevention policy. All the global objects are assigned to the Domain.
After you upgrade a Multi-Domain Server with a IP address change, you must remove the license with the old IP address. If you do not do this, failures will occur in the License view and on some Management Blades.
In a High Availability environment that includes more than two Multi-Domain Management servers, a synchronization problem between 2 specific Multi-Domain Management servers only shows when connected to one of those servers. The problem does not show when connected to a different Multi-Domain Management server in the environment.
For Multi-Domain Log Servers, Remote Log Servers that are not defined as Domain Log Servers are not supported.
Private sessions are not synchronized between Multi-Domain Management Servers. A session that is open on one Multi-Domain Management Server cannot be seen or moved to a different Multi-Domain Management Server.
An administrator with Manage Session permissions on a Multi-Domain Management Server but not on a specific Domain, can manage the session from Sessions view in the MDS level. Session publish may fail.
You cannot add licenses from the Multi-Domain Management Server or Domain Management configuration windows or wizards. To add licenses, click "Manage Licenses and Packages" in the SmartConsole main menu.
You can use only one Global Domain, which is created automatically during installation.
Administrator groups and Domain groups are not supported in R80 and cannot be viewed or used in the SmartConsole.
In Multi-Domain Management Server, OPSEC application permission profiles are not visible on the Domain's object bar. Use the OPSEC application editor to change the permissions.
During mds_import, the incorrect "Failed to open file 'obsolete_objects.C' " message shows.
This message can be ignored.
The same system object (administrator, domain, permission profile, trusted client or Multi-Domain Server) cannot be managed from multiple peers. It can create sync failures between Multi-Domain servers.
If there is a sync failure, make sure sessions on a different peers do not lock the same object.
From a secondary Multi-Domain Management Server, cma_migrate gets stuck.
Run cma_migrate on the server with the active global policy.
When upgrading a Multi-Domain Security Management environment, you can change the IP address of the primary MDM, but not the IP address of secondary MDMs.
Each database can be migrated only once with cma_migrate. If you try to migrate the same database to another Domain Server, migration fails with the "Internal runtime error"... "The folder in the dleObject can't be null." error.
After you define the SmartEvent object in the global database, first you must assign Global Policy to Domain Servers in order the Domain Level Only administrators can log in to SmartEvent.
After an upgrade, the global assignment fails with an error regarding multiple objects with the same name. If the search fails to locate the object in the domain, the object might be an unused OPSEC application permission profile and it can be deleted or modified using dbedit. Refer to sk116059.
The cma_migrate tool fails with "Command completed with error code 4" error due to a missing "No Global Access Policy" option on one of the Domains.
Management High Availability
To move a Secondary Multi-Domain Management Server from one Multi-Domain Management HA environment to another, install the Secondary Multi-Domain Management Server from scratch in the new environment as a Secondary Multi-Domain Management Server and synchronize it with the Primary Multi-Domain Management Server.
In a High Availability environment, if an administrator is locked on the Standby Management Server, the administrator is not locked and does not show as locked on the Active Management Server. Therefore, you cannot unlock the administrator from the Active Management Server.
To unlock the administrator, run the CLI command unlock-administrator on the Standby Management Server.
In a Management High Availability environment which includes an invalid license, sync fails with "Failed to apply shared licenses" message.
Workaround: remove the invalid license according to the signature that appears in the error message.
Management High Availability is supported only between Management High Availability servers with the same build number. To see the build number, run cpinfo -y FW1
Administrator created using SmartConsole connected to the Primary Security Management Server in a Management HA environment are unable to log in to the secondary Management Server until full sync is performed.
When a secondary Management server is added, the initial synchronization task starts automatically. Until it completes, the secondary peer status shows as "Failed to communicate with peer". Wait for the initial synchronization task to complete. The peer status in the High Availability Status window will then show that the synchronization was successful.
Sync failure between primary and secondary servers in a Management High Availability deployment.
To prevent this, make sure the interfaces are enabled before starting the processes (cpstart, mdsstart).
The initial full synchronization of a new High Availability server, either Security Management or Multi-Domain, can take a long time in large environments.
Login to the Secondary Management from the Management High Availability window fails. Make sure the SmartEvent Server and SmartEvent Correlation Unit blades are not be enabled on the secondary Management object.
High Availability CLI commands like 'set standby' and 'set active' that are part of the send_command tool, are no longer available.
In a High Availability deployment of Multi-Domain Security Management Servers, until the MDS that hosts the active Domain server has been upgraded, it is not possible:
To edit an administrator assigned to that Domain
To edit a client assigned to that Domain
To view global assignments of that Domain
SmartConsole / Management Console
The "Groups" page / tab is not shown if you edit a predefined service.
PMTR-25778, PMTR-25825, PMTR-25790
When using Global VPN Community with permanent tunnel gateways list (matrix / permanent tunnel gateways), upgrade from R7x fails.
Password configuration in SmartEndpoint for FDE preboot users, WebRH administrators and client uninstall password is limited to a maximum of 12 characters.
PMTR-24135, PMTR-29511, PMTR-24135
Missing visual indication for Trusted CA update although automatic updates are enabled and update is successfully downloaded to the Management server.
R80.x SmartConsole is not supported for case-sensitive installation folder. Installation of SmartConsole complets successfully, but SmartConsole fails to start with this error message: [Window Title] C:\Program Files (x86)\CheckPoint\SmartConsole\R80.20\PROGRAM\SmartConsole.exe [Content] C:\Program Files (x86)\CheckPoint\SmartConsole\R80.20\PROGRAM\SmartConsole.exe The application has failed to start because its side-by-side configuration is incorrect. Please see the application event log or use the command-line sxstrace.exe tool for more detail.
Desktop Policy tab does not appear in the following scenario:
Open the SmartConsole in Read-Only mode, or log in with Read-Only credentials.
In the left navigation panel, click Security Policies.
In the Access Control section, click Desktop -> Open Desktop Policy in SmartDashboard.
Legacy SmartDashboard opens without the Desktop Policy tab.
The "Lockout administrator's account after X failed authentication attempts" setting affects only the main SmartConsole application. For Legacy GUI client applications, SmartEvent servers and Log Servers, administrator accounts are not locked out after multiple failed login attempts.
When creating a new Cluster object in SmartConsole with the Wizard Mode, if you do not add Cluster members or do not initialize SIC with the Cluster members, the "Optimizations" -> "Capacity Optimization" setting in the cluster object may set to "Manually", instead of the default "Automatically". The "Automatically" option is grayed out, if the OS of the Cluster object is unknown. Refer to sk141933.
In Full HA cluster, the "Install Database" operation is supported only on the Cluster object (and not on the individual cluster members objects).
Domain Management Server and Domain Management Log Server must be removed form a policy package before deleting their representing objects.
For R77.30 Gateway, the ICAP server is supported only from CLI and not in the SmartConsole GUI, although the ICAP Server tab is displayed in the Gateway properties.
Configuration of colors and icons in some Service objects does not survive upgrade from R77.x versions to R80.x versions
Cannot find the "Override categorization" object in the objects bar search.
After a Security Management server upgrade from R80 to R80.10, 0 applications appear in object bar although all applications appear in the rule base picker.
Workaround: Perform Application Control & URL Filtering update.
A Remote Access community object is not supported in the parent rule of an inline layer where the action is "Inline Layer".
Workaround: use "Any" instead of the Remote Access community object. You can use the Remote Access community object in the rules in the inline layer.
The Device and License Status of Threat Emulation is incorrect when there is a trial license on the Security Gateway.
Use the Logging -> License Status view.
This procedure for renewing an expired HTTPS Inspection certificate does not work:
Open the SmartDashboard GUI client
Renew the HTTPS Inspection certificate.
Install the Policy in SmartConsole.
SmartConsole shows the certificate is still expired, and the certificate is not renewed.
Workaround: After following the procedure, close and reopen SmartConsole.
Policy installation includes an implicit database install operation. As a result, the policy installation task in SmartConsole only completes after the end of the database installation task. This does not delay policy enforcement on the gateway.
When connected to a machine that runs both Security Management and Security Gateway (Standalone deployment) and has less than 6GB of RAM, SmartConsole will perform slowly and disconnections may occur during policy installation or an IPS update. Running R80.10 Standalone configuration requires at least 6GB RAM. Running this configuration with less than 6GB RAM is not supported. Specifically, 4400-12400 appliance models do not support Standalone with their default RAM (4GB), and require a memory upgrade to 8GB.
Cannot log into SmartConsole after changing the time in the Gaia Portal.
To resolve, restart the Management server using cpstop;cpstart commands or, for Multi-Domain Security Management, run mdsstop;mdsstart
In SmartConsole, when creating a new object in a second Object Editor, the new object is not in the list in the original Object Editor.
Workaround: After you close the second Editor, click OK in the IF-MAP server editor. Open the IF-MAP server editor again.
When session details enforcement is configured, publishing a remote session is not blocked even if session details are not provided.
SmartConsole does not display one of cluster interfaces because of case sensitive name uniqueness. Refer to sk108264.
The SmartConsole package cannot be installed in a directory whose path includes non-English characters.
Creating new services in R80.x is not supported via Embedded Dashboard. New service creation can be done only from SmartConsole.
When you create an SMB cluster using the Wizard mode, SmartConsole automatically assigns an incorrect IP "0.0.0.X" as the cluster main IP address.
Workaround: The admin must first publish the new cluster object, then configure the correct IP address before enabling any blade. If the cluster is created via 'Classic' mode, there is no issue.
SmartConsole installed on a computer without access to the Internet cannot open Help files. Refer to sk110774.
Slow rendering of SmartConsole and reaction to user interactions. Slow rendering can be a result of:
Running SmartConsole through Remote Desktop (RDP) sessions. See sk123734.
Environments with lower-end graphic hardware drivers. Typical environments include Windows-Server 2012 and Virtual Machines. In this case, consider upgrading your DirectX driver or Graphics Card hardware.
The 'Where used' feature does not show the Limit objects.
Disconnecting the SmartConsole session while creating or configuring VSX objects, can cause the management database corruption and Administrator will be unable to do any changes with VS. "Internal Error: Cannot get object XXX from table vs_slot_object" message pops-up.
After a failure in the VSX cluster creation wizard, if Cancel is clicked, the wizard closes, but the VSX cluster and VSX cluster member objects are not deleted.
Workaround: Delete the VSX cluster and VSX cluster member objects manually.
The Tasks tab -> Script Results supports up to 10,000 characters only.
In R80 and higher, multiple administrators can connect to the management with SmartConsole in write mode, at the same time. Therefore, switching between Read only and read-write mode, which was often used in previous versions, is not an option in SmartConsole.
When publishing remote session, through the Sessions View, there is no option for updating the session name and the description. Before you can publish a session, you must connect to it and set the session name and description.
When trying to rename a time object in SmartConsole, this error message might show: "Failed to revert object. Server error is : N/A (Code: 0x800415A1, Object Not Found) . Please contact technical support". Refer to sk126052.
Gateway packages do not show for Domain gateways, when you open SmartUpdate from the SmartConsole Multi-Domain view. You must connect to SmartConsole for each Domain to see the packages for its gateways.
SmartConsole is not disconnected after time specified in SmartConsole -> Manage & Settings -> Permissions & Administrators -> Administrators -> Idle Timeout.
A customized role that has no write permissions, does not appear as read-only in the session view, although it is actually read-only.
Administrators with Customized permission profile cannot manage VSX objects.
Workaround: Use Read/Write all permission.
A query that refers to "Scan result" and "Destination DNS Hostname" fields will not be resolved.
The version of a dedicated SmartEvent Server has to be the same or higher than the version of the Security Management Server. Refer to sk133954.
SmartEvent Intro is not supported.
SIC problem with the global SmartEvent object managing a Global SmartEvent object from the Domain/CMA that has the global object assigned to it.
SmartEvent cannot be enabled on a 5400 Security Appliance.
Events Grid is missing from SmartEvent.
The Ticketing feature is missing from SmartEvent.
For SmartEvent connected to R77.x Security Management Server or Multi-Domain Management Server: If an object is not listed in the Log Servers table in the Correlation Unit settings, change the object from the SmartConsole (for example, its color). This will cause the re-synchronization of the object.
After disabling Firewall sessions in the SmartEvent policy, the records of Firewall sessions disappear from reports and views. If you enabled Firewall sessions in order to see Firewall data in reports or views, generate the report or examine the view *before* disabling Firewall sessions.
For Global SmartEvent connected to a Multi-Domain Management Server: Search suggestions from SmartConsole appear for Super Users only (Multi-Domain Super User and Domain Super User).
02551294, 02569029, 02556817
Legacy SmartEvent GUI crashes with core dump file at 65% "Getting list of active products..." when connecting directly and not with SmartConsole R80.10. Refer to sk120076.
Upgrade of SmartEvent server from R80 to R80.10 fails with "Internal error in a hook script: fw1/bin/hook_fw1_wrapper_HOTFIX_R80_10. Contact Check Point Technical Services for future assistance." error. Refer to sk123013.
SmartEvent stability problem while connecting to Multi-Domain Management. Refer to sk112238.
On a R80.10/20 dedicated SmartEvent server which assigned to MDS, when you enable or disable a blade, the license information is not immediately updated. An automatic updates takes place at midnight. To update immediately:
On server's command line, run: $CPDIR/bin/esc_db_complete_linux_50 activation_data entitlement_data.
If you manually change a license or contract, the changes take effect immediately.
Mail alerts that contain IPv6 show 0.0.0.0 instead of the real IP address. Refer to sk119714.
Not possible to generate separate report for each Domain Management Server in R80.x SmartEvent. Refer to sk113494.
"Update CONF failed: The plug-ins that are installed on the Security Management server do not match the plug-ins that are installed on the Log Server" error when installing database from pre-R80 Security Management server on SmartEvent or Correlation Unit running R80 and above. Refer to sk110894.
In R80.x, you can only define SmartEvent at the global level and then configure it to read logs from one Domain or a number of domains. SmartEvent cannot be defined in a specified domain.
Logging / SmartLog
After upgrade to R80.20, the Log Exporter does not start automatically.
After you revert from R80.20 GA to a R80.10 or R80 version, the log files and log indexes that were created on the R80.20 will be lost. If you upgrade again to R80.20 GA, all logs will be visible again with one exception - the log index created on the day of the revert (from R80.20) may be partial.
After upgrading from R80.10 to R80.20 M1, the log indexes from R80.10 are unusable, but remain on the disk. If a maintenance routine to delete log files was running when the version is still M1, the R80.10 indexes are not deleted. When upgrading to R80.20 GA, this may cause empty lines on Smart Log.
To resolve, delete the R80.10 log indexes after upgrading to R80.20 M1. Refer to sk127652.
When you right-click in an Anti-Virus or Anti-Bot log from R77.30 Security Gateways and select "Save as Packet Capture...", it opens an email file with the attached packet capture file, instead of saving it. This is the same behavior as in the option "View Packet Capture".
During upgrade, the Log Exporter configuration is not transferred on R80.20.M1 or not fully updated on R80.20.
Recommended solution: Rebuild the Log Exporter configuration from scratch using sk122323.
Alternative solution: Follow sk127653 to save the configuration manually before the upgrade, and then restore it after the upgrade.
For R80.20, follow the "R80.20" section in sk127653, to fully update the Log Exporter.
Reading logs through LEA which were configured manually on the SmartLog custom settings file is not available in R80.10.
On Security Management Server with "Enable Log Indexing" option not selected, and a dedicated Log Server with "Enable Log Indexing" option selected: When you connect with SmartConsole to the Security Management Server, the Logs view shows the logs of individual log files. It is not possible to get a unified view of all the logs.
SAM rules are not supported from SmartConsole.
Purge, log switch and fetch file are not supported from SmartConsole.
When using the Check Point Management Server as an external log server for a locally managed Small Office appliance, SmartLog is not supported. Only SmartViewTracker is supported for this configuration.
In Management High Availability, the indexing mode should be the same on both primary and secondary servers.
Correlated "Web Browsing" events are not shown by default.
To see: in SmartEvent, go to Event Policy -> Legacy ->Web Browsing, right-click and select "Event Format". Replace the field "URL" with the field "Resource".
In a Multi-Domain Management environment, you cannot have a dedicated Log server for a specific Domain/CMA.
Workaround: configure a Multi-Domain Log servers with only one CLM.
"Save As" to a log file is not supported.
Fetch local files from a remote machine is available from command line only.
SmartView graphics do not display properly in Internet Explorer. Accessing SmartEvent server from the web (SmartView) is supported only from Google Chrome and Mozilla Firefox.
Correlation units can be added to a remote Log server in this way only:
In SmartConsole, edit the Correlation unit object and configure it as a Log server.
On the SmartEvent server, go to the Correlation unit policy configuration and configure the Correlation unit on the SmartEvent server to read the logs from the remote Log server configured in Step 1.
SmartLog Indexing mode is not enabled by default after upgrade or new installation, on Smart-1 205, Smart-1 210, or Open Servers with less than 4 cores.
To change SmartLog mode from Indexing to Non-Indexing on a Domain Management Server or Domain Log Server, edit the Domain Server object on the Domain level. There is no option to change the entire Multi-Domain Server or Multi-Domain Log Server to Non-Indexing mode.
In SmartLog Non-Index mode: free text search is applied only on specific fields like source, destination, service, etc. , there is no Top results pane, and the Threat Prevention Rulebases and Profiles logs tab do not show log results.
Users connected with SmartConsole to specific Domain, will not be able to see Global objects assigned to this Domain in SmartLog logs results, and cannot search by Global objects (but can search by IP address).
Block Intruder (SAM) is not supported.
"Top QoS Rules" view in SmartView Monitorshows that almost all traffic matches the "No Match" rule when SecureXL is enabled on Security Gateway. Refer to sk118720.
When changes to a ROBO Gateway object are not published, unexpected shutdown of the Security Management Server or SmartProvisioning GUI client might leave the ROBO Gateway object in a locked state.
When working with LSM managed Security gateways in a Management High Availability environment, creating and working with LSM gateways must be consistent, they can only be used in the Security Management server they are created in. Using the secondary Security Management server might lead to inconsistent actions/status related to LSM objects.
It is not possible to configure internet connection over DSL for 1100, 1430, 1450 appliances using SmartProvisioning.
After a major upgrade of the Multi-Domain Management Server, opening the SmartProvisioning client fails, displaying "SmartProvisioning was not enabled on the Security Management Server or no valid license was found..." error.
To resolve, enable LSM on each relevant Domain Management server by running the "LSMenabler on" command.
SmartProvisioning R80.20.M1 does not support LSM Profiles of type "Check Point Appliance/Open Server Gateway" with version "R80.10" (lower versions are supported).
After a major upgrade to a Security Management Server, LSM profiles lose their installed policy and new devices attached to them are not able to fetch a policy.
To resolve, install policy on the LSM profiles.
Endpoint Security (SmartEndpoint)
When you enable the Endpoint Policy Management blade on a Security Management Server, the connection to these services automatically changes from the default port 443 to port 4434:
SmartView Web Application
Management API Web Services
If you disable the Endpoint Policy Management blade, the services connection port automatically changes back to the default 443.
"An internal server fault has occured" server error is shown when logging in to the SmartEndpoint GUI client with a custom administrator created in SmartConsole with the name "endpoint".
Workaround: Create an administrator with a different name.
In some scenarios, assignment to Virtual Group does not apply properly.
After upgrading to R80.20 M1, you must install Access Policy before installing Threat Prevention Policy. Otherwise, the Threat Prevention Policy installation may fail.
A QoS policy cannot be prepared in advance for R75.20 1100 appliances, to be fetched later. QoS policies must be installed and cannot be pulled.
When installing policy on a Small Office Appliance without establishing SIC, an incorrect warning message is shown for the Threat Prevention policy: "Installation pending, waiting for first connection".
Establishing SIC resolves the issue and policy installation can be performed.
In Small Office appliance policy installation, services that are manually configured with INSPECT code including the definition "CALL_XLATE_FOLD_FUNC (..." will cause a policy installation failure.
Workaround: remove the "_FUNC" from the definition and use "CALL_XLATE_FOLD (..."
R80.x Security Management cannot manage Security Gateway 80 appliance with a firmware version that is lower than R75.20.
"Commit function failed" error on policy installation failure on 1100 series appliance. Refer to sk105217.
"SIC error" status might occur when the gateway object is defined in a "Management first" scenario before it is deployed, but the device's IP address is already accessible. The Security Management tries to create SIC with the gateway's IP address. Instead of the policy ending in a "waiting for first connection" status, an error message states the SIC status must be rectified first.
On Smart-1 25B, Smart-1 50, and Smart-1 150 appliances, it is not supported to run "set ip" and "add users" commands from Gaia Clish. These commands are still available directly in LOM UI.
IPv6 addresses for management interface are not supported on R80.20 Security Management Server.
After an upgrade of a Management Server with enabled Compliance blade from R77.20 or lower versions to R80.x:
The "Dev Mode: ON - Syntax error: Unable to get property 'icon' of undefined or null reference at line: undefined" error can appear in the Compliance blade reports.
"Compliance Statuses" contains the words "Low" instead of "Poor" and "High" instead of "Good".
In a Multi-Domain Management environment, in the local domain policy, some Compliance best practices, which validate the status of rules in the policy, incorrectly identify the section header, "Parent section for domain rules," as a rule, and report it as not valid.
Workaround: manually exclude this result from the Best Practices view. In the Best Practices view, select the practice. In the bottom pane -> Relevant Object section -> double-click the desired rulebase object and disable the rule/section from the list.
In the Compliance blade, if you deactivate a relevant object of a best practice and then make a change in the relevant object, the relevant object changes to be active.
Workaround: deactivate the relevant object again.
In a Multi-Domain environment, policy changes in the Global Compliance Policy do not trigger a partial Compliance scan.
When there is more than one policy, and a rule changes, Application Control and URL Filtering Best Practices will show incorrect scores until a full scan is run.
Compliance Blade does not contain Compliance Overview Report.
To have the Compliance Overview Report, deploy a SmartEvent server and enable SmartEvent. Then find it at Logs & Monitoring -> new tab -> Reports -> Compliance Blade.
The SmartConsole client is not aware of license or quota changes in real time - Alert for 'License quota Exceeded' does not pop-up immediately when the license quota is exceeded.
Reopen SmartConsole in Compliance blade to see the license changes. Quota data changes in the entitlement or Compliance will be updated after:
Compliance midnight scan
Compliance Blade regulation reports do not contain the Best Practices themselves.
To see the Best Practices, deploy a SmartEvent Server, enable SmartEvent and create a customized report.
CloudGuard for NSX
Topology is missing in the CloudGuard for NSX Cluster object after upgrading the Security Management Server from R80.10 to R80.20.M2. Refer to sk141955.
For R80.20 CloudGuard Controller Known Limitations, refer to sk128612
Give us Feedback
Thanks for your feedback!
Are you sure you want to rate this stars?