- Products
- Learn
- Local User Groups
- Partners
- More
Check Point Jump-Start Online Training
Now Available on CheckMates for Beginners!
Why do Hackers Love IoT Devices so Much?
Join our TechTalk on Aug 17, at 5PM CET | 11AM EST
Welcome to Maestro Masters!
Talk to Masters, Engage with Masters, Be a Maestro Master!
ZTNA Buyer’s Guide
Zero Trust essentials for your most valuable assets
The SMB Cyber Master
Boost your knowledge on Quantum Spark SMB gateways!
As YOU DESERVE THE BEST SECURITY
Upgrade to our latest GA Jumbo
CheckFlix!
All Videos In One Space
Hello!
I'm testing R80.10 in my lab and I noticed that the Status of the gateways and servers are unavailable. In R80 it's working fine. In all Columns (General, Health, Traffic, etc) there is no information. It shows a "Machine Status is not available" message.
See the screenshot.
Any tip on how to solve this?
Thanks!
Seen that issue before, try clearing the monitoring database as specified in this SK:
sk112058: Gateways & Servers view in R80 SmartConsole does not show statuses
This procedure seems to be the R80+ equivalent of clearing the SmartConsole cache files CPMILinksMgr.db* and applications.C* for the R7* SmartView Monitor when it displays incorrect status information about gateways as documented here:
--
My book "Max Power: Check Point Firewall Performance Optimization"
now available via http://maxpowerfirewalls.com.
Hi Tim,
I executed the script and it returned "ERROR: database "monitoring" does not exist". However the status started working, maybe was due the smartview stop/start procedures.
Thanks!
We are having a similar issue. The "Status" column is fine, it's all the health columns that are missing data. The health data is OK for our 2 R80.10 SMS, and our 1 cluster of 5600 appliances. Our 3 open server clusters and open server smartevent server are not reporting data.
I ran the script that was advised in your original post to no avail.
Can you post the steps from sk112058? My usercenter access is playing up
Generally the contents of SKs cannot be shared to CheckMates.
In this specific case, there's a script you need to download and run.
If you're having issues accessing SecureKnowledge because of entitlement level, please check with Account Services.
Hi,
I have similar issue.Gateways/Server status is not showing for 2 gateways. I have run the mentioned script and restarted mgmt server but still it is not showing the status.
Any idea, What action need to take further.
The gateway status as displayed on the Gateways & Servers tab (and SmartView Monitor) is reported by the cpd daemon running on the gateway. If this daemon is not running or impaired in some way, a status will not be reported for the gateway although things will continue working. Try restarting the cpd daemon on the affected gateways.
--
Second Edition of my "Max Power" Firewall Book
Now Available at http://www.maxpowerfirewalls.com
Hi Tim,
I have restarted CPD process but that did not help. Also set correct local time in gateway and again restarted CPD process but no luck.
Please open a support call, thanks
Hi Tim,
Is it normal that status of standby gateway of an HA cluster (R80.20) is not shown while status of the active one is shown?
Thanks,
Hiep.
If you can't retrieve the state of the standby member of your cluster but you can see the active, that generally indicates that monitoring traffic heading for the standby member is flowing asymmetrically through the cluster. So in essence traffic bound for the standby member arrives at the active first, who forwards it to the standby, who then tries to answer directly which won't work due to asymmetry. Make sure that the General or "Main" IP addresses defined for each cluster member are the IP address that "faces" or is closest to where the SmartConsole and/or SMS are located to avoid this. If this cannot be achieved, a static host-based route will need to be defined for the dedicated/fixed IP addresses of each cluster member on whatever adjacent Layer 3 device is transiting the traffic on behalf of the SmartConsole and/or SMS.
Since this is R80.20, it could also be related to kernel variable fwha_forw_packet_to_not_active as reported by @Danny in this thread:
It seems, in a multi-domain environment, that Checkpoint hosts created in the global context will have a "grey bar" as their status.
I had the same issue with SMB (1490 appliances) after upgrading management from R77.30 to R80.10. Did lot of cpd debugs with TAC, no luck.
Solutions that worked for me at the end was SIC reset on problematic gateways.
About CheckMates
Learn Check Point
Advanced Learning
YOU DESERVE THE BEST SECURITY