[ZBX-24788] Issue with VPN discovery on Check Point Next Generation Firewall by SNMP template Created: 2024 Jul 04  Updated: 2025 Jan 07

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

Type: Problem report Priority: Trivial
Reporter: Julien Lacasse-Roger Assignee: Zabbix Support Team
Resolution: Unresolved Votes: 0
Labels: templates
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Ubuntu 22.04, Zabbix 7.0, Checkpoint 6700 R81.10


 Description   

Steps to reproduce:

  1. Assign Check Point Next Generation Firewall by SNMP template to 6700 appliance
  2. Observe VPN discovery become unsupported.
  3. Get value of vpn.tunnel.walk key item:
.1.3.6.1.4.1.2620.500.9002.1.1.7.7.7.7 = IpAddress: 7.7.7.7
.1.3.6.1.4.1.2620.500.9002.1.1.8.8.8.8.0 = IpAddress: 8.8.8.8
.1.3.6.1.4.1.2620.500.9002.1.1.9.9.9.9.0 = IpAddress: 9.9.9.9
.1.3.6.1.4.1.2620.500.9002.1.10.7.7.7.7 = Wrong Type (should be INTEGER): Gauge32: 1
.1.3.6.1.4.1.2620.500.9002.1.10.8.8.8.8.0 = Wrong Type (should be INTEGER): Gauge32: 1
.1.3.6.1.4.1.2620.500.9002.1.10.9.9.9.9.0 = Wrong Type (should be INTEGER): Gauge32: 1
.1.3.6.1.4.1.2620.500.9002.1.11.7.7.7.7 = Wrong Type (should be INTEGER): Gauge32: 1
.1.3.6.1.4.1.2620.500.9002.1.11.8.8.8.8.0 = Wrong Type (should be INTEGER): Gauge32: 1
.1.3.6.1.4.1.2620.500.9002.1.11.9.9.9.9.0 = Wrong Type (should be INTEGER): Gauge32: 1
.1.3.6.1.4.1.2620.500.9002.1.2.7.7.7.7 = STRING: "PEER_01"
.1.3.6.1.4.1.2620.500.9002.1.2.8.8.8.8.0 = STRING: "PEER_02"
.1.3.6.1.4.1.2620.500.9002.1.2.9.9.9.9.0 = STRING: "PEER_03"
.1.3.6.1.4.1.2620.500.9002.1.3.7.7.7.7 = Wrong Type (should be INTEGER): Gauge32: 3
.1.3.6.1.4.1.2620.500.9002.1.3.8.8.8.8.0 = Wrong Type (should be INTEGER): Gauge32: 3
.1.3.6.1.4.1.2620.500.9002.1.3.9.9.9.9.0 = Wrong Type (should be INTEGER): Gauge32: 3
.1.3.6.1.4.1.2620.500.9002.1.4.7.7.7.7 = STRING: "VPN_01"
.1.3.6.1.4.1.2620.500.9002.1.4.8.8.8.8.0 = STRING: "VPN_02"
.1.3.6.1.4.1.2620.500.9002.1.4.9.9.9.9.0 = STRING: "VPN_03"
.1.3.6.1.4.1.2620.500.9002.1.6.7.7.7.7 = STRING: ""
.1.3.6.1.4.1.2620.500.9002.1.6.8.8.8.8.0 = STRING: ""
.1.3.6.1.4.1.2620.500.9002.1.6.9.9.9.9.0 = STRING: ""
.1.3.6.1.4.1.2620.500.9002.1.7.7.7.7.7 = IpAddress: 0.0.0.0
.1.3.6.1.4.1.2620.500.9002.1.7.8.8.8.8.0 = IpAddress: 0.0.0.0
.1.3.6.1.4.1.2620.500.9002.1.7.9.9.9.9.0 = IpAddress: 0.0.0.0
.1.3.6.1.4.1.2620.500.9002.1.8.7.7.7.7 = Wrong Type (should be INTEGER): Gauge32: 0
.1.3.6.1.4.1.2620.500.9002.1.8.8.8.8.8.0 = Wrong Type (should be INTEGER): Gauge32: 0
.1.3.6.1.4.1.2620.500.9002.1.8.9.9.9.9.0 = Wrong Type (should be INTEGER): Gauge32: 0
.1.3.6.1.4.1.2620.500.9002.1.9.7.7.7.7 = Wrong Type (should be INTEGER): Gauge32: 0
.1.3.6.1.4.1.2620.500.9002.1.9.8.8.8.8.0 = Wrong Type (should be INTEGER): Gauge32: 0
.1.3.6.1.4.1.2620.500.9002.1.9.9.9.9.9.0 = Wrong Type (should be INTEGER): Gauge32: 0

Result:

Add replace processing steps to vpn.tunnel.walk key item:

Replace: IpAddress -> STRING
Replace: Wrong Type (should be INTEGER) -> INTEGER

So output becomes:

.1.3.6.1.4.1.2620.500.9002.1.1.7.7.7.7 = STRING: 7.7.7.7
.1.3.6.1.4.1.2620.500.9002.1.1.8.8.8.8.0 = STRING: 8.8.8.8
.1.3.6.1.4.1.2620.500.9002.1.1.9.9.9.9.0 = STRING: 9.9.9.9
.1.3.6.1.4.1.2620.500.9002.1.10.7.7.7.7 = INTEGER: Gauge32: 1
.1.3.6.1.4.1.2620.500.9002.1.10.8.8.8.8.0 = INTEGER: Gauge32: 1
.1.3.6.1.4.1.2620.500.9002.1.10.9.9.9.9.0 = INTEGER: Gauge32: 1
.1.3.6.1.4.1.2620.500.9002.1.11.7.7.7.7 = INTEGER: Gauge32: 1
.1.3.6.1.4.1.2620.500.9002.1.11.8.8.8.8.0 = INTEGER: Gauge32: 1
.1.3.6.1.4.1.2620.500.9002.1.11.9.9.9.9.0 = INTEGER: Gauge32: 1
.1.3.6.1.4.1.2620.500.9002.1.2.7.7.7.7 = STRING: "PEER_01"
.1.3.6.1.4.1.2620.500.9002.1.2.8.8.8.8.0 = STRING: "PEER_02"
.1.3.6.1.4.1.2620.500.9002.1.2.9.9.9.9.0 = STRING: "PEER_03"
.1.3.6.1.4.1.2620.500.9002.1.3.7.7.7.7 = INTEGER: Gauge32: 3
.1.3.6.1.4.1.2620.500.9002.1.3.8.8.8.8.0 = INTEGER: Gauge32: 3
.1.3.6.1.4.1.2620.500.9002.1.3.9.9.9.9.0 = INTEGER: Gauge32: 3
.1.3.6.1.4.1.2620.500.9002.1.4.7.7.7.7 = STRING: "VPN_01"
.1.3.6.1.4.1.2620.500.9002.1.4.8.8.8.8.0 = STRING: "VPN_02"
.1.3.6.1.4.1.2620.500.9002.1.4.9.9.9.9.0 = STRING: "VPN_03"
.1.3.6.1.4.1.2620.500.9002.1.6.7.7.7.7 = STRING: ""
.1.3.6.1.4.1.2620.500.9002.1.6.8.8.8.8.0 = STRING: ""
.1.3.6.1.4.1.2620.500.9002.1.6.9.9.9.9.0 = STRING: ""
.1.3.6.1.4.1.2620.500.9002.1.7.7.7.7.7 = STRING: 0.0.0.0
.1.3.6.1.4.1.2620.500.9002.1.7.8.8.8.8.0 = STRING: 0.0.0.0
.1.3.6.1.4.1.2620.500.9002.1.7.9.9.9.9.0 = STRING: 0.0.0.0
.1.3.6.1.4.1.2620.500.9002.1.8.7.7.7.7 = INTEGER: Gauge32: 0
.1.3.6.1.4.1.2620.500.9002.1.8.8.8.8.8.0 = INTEGER: Gauge32: 0
.1.3.6.1.4.1.2620.500.9002.1.8.9.9.9.9.0 = INTEGER: Gauge32: 0
.1.3.6.1.4.1.2620.500.9002.1.9.7.7.7.7 = INTEGER: Gauge32: 0
.1.3.6.1.4.1.2620.500.9002.1.9.8.8.8.8.0 = INTEGER: Gauge32: 0
.1.3.6.1.4.1.2620.500.9002.1.9.9.9.9.9.0 = INTEGER: Gauge32: 0

Expected:

Now VPN discovery works as expected, unless no VPN exist on appliance and then discovery remains unsupported (Failed: no data was found).
Generated at Thu Jun 05 22:59:19 EEST 2025 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.