[ZBX-20537] Wrong SNMP OID used for pfSense system uptime Created: 2022 Feb 04  Updated: 2024 Apr 10  Resolved: 2022 Feb 18

Status: Closed
Project: ZABBIX BUGS AND ISSUES
Component/s: Templates (T)
Affects Version/s: None
Fix Version/s: 5.0.21rc1, 5.4.11rc1, 6.0.0beta3, 6.0.1rc1, 6.2.0alpha1

Type: Problem report Priority: Trivial
Reporter: Øyvind Møll Assignee: Vyacheslav Khaliev
Resolution: Fixed Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Zabbix 5.4.10, pfSense 2.4.x

Attachments: File pfsense_snmp_uptime.diff    
Team: Team INT
Sprint: Sprint 85 (Feb 2022)
Story Points: 0.25

 Description   

Steps to reproduce:

  1. Add monitoring of a pfSense host using the app/pfsense_snmp template
  2. Wait for data
  3. Compare value of system uptime in Zabbix and what's shown in the pfSense GUI

Result:
**

System uptime data in Zabbix shows how long the snmpd on the pfSense host has been running.

Expected:

System uptime data in Zabbix should show how long it has been since the pfSense host booted.

The solution is to use HOST-RESOURCES-MIB::hrSystemUptime.0 instead of DISMAN-EVENT-MIB::sysUpTimeInstance.

Patch against master is attached.

 

 Comments   
Comment by Øyvind Møll [ 2022 Feb 04 ]

Example showing the disparity after having recently done a minor reconfiguration of the SNMP service on the pfSense host:

$ snmpwalk -v 2c -c XXXX a.b.c.d | grep -i uptime | grep -v SNMPv2
DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (203266) 0:33:52.66
HOST-RESOURCES-MIB::hrSystemUptime.0 = Timeticks: (1240989259) 143 days, 15:11:32.59

This causes a "has been restarted" trigger which is misleading. 

Comment by Vyacheslav Khaliev [ 2022 Feb 18 ]

Available in:

Generated at Sat Dec 13 22:27:33 EET 2025 using Jira 10.3.13#10030013-sha1:56dd970ae30ebfeda3a697d25be1f6388b68a422.