[ZBX-24267] Checkpoint NGFW firewall errors Created: 2024 Mar 26  Updated: 2024 Nov 20

Status: Confirmed
Project: ZABBIX BUGS AND ISSUES
Component/s: Templates (T)
Affects Version/s: 7.0.0beta2
Fix Version/s: None

Type: Incident report Priority: Trivial
Reporter: Ted Serreyn Assignee: Zabbix Development Team
Resolution: Unresolved Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File Screenshot 2024-03-26 at 11.07.13 AM.png     PNG File Screenshot 2024-03-26 at 11.11.14 AM.png    

 Description   

Steps to reproduce:

  1. create host for various active firewall models with active subscriptions.
  2. enable checkpoint NGFW template
  3. see generated errors

Result:

  1. Identifies problems with power supplies that don't exist.  Probably should discovery in the MIB to see if it exists before deciding the power supply is down.  My smaller firewall shows a problem with power supply, but it only has a single one.
  2. expiration of valid contract.  All contracts are showing as expired, I presume the logic for the calculation of expiration date is incorrect.  This device has valid contracts thru july 2024 (real contracts, not evaluations)

    3. Additionally, this throws errors on the checkpoint SMB side, maybe we should have a different template for Checkpoint SMB (1500,1900,2000) series devices as the MIB is quite different.  It also shows expired contracts when all are valid.
  3.  
  4. See log file...
    See memory dump...
    Expected:
    See screenshot....
    See attached patch file...


 Comments   
Comment by Victor Hugo Assunção [ 2024 Mar 27 ]

I believe that "(last(/Check Point Next Generation Firewall by
SNMP/svn.sw.license.exp_datelicensingExpirationDate.{#SNMPINDEX}) -
now()) / 86400 < now()" always activate the trigger.

Maybe expired contract could be the expression:
"(last(/Check Point Next Generation Firewall by
SNMP/svn.sw.license.exp_datelicensingExpirationDate.{#SNMPINDEX}) < now())"

Generated at Sat Apr 19 06:06:34 EEST 2025 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.