Bug 1973252

Summary: net-snmp engineTime values remains zero when sending traps.
Product: Red Hat Enterprise Linux 8 Reporter: Sam Wachira <swachira>
Component: net-snmpAssignee: Josef Ridky <jridky>
Status: CLOSED ERRATA QA Contact: Evgeny Fedin <efedin>
Severity: high Docs Contact:
Priority: unspecified    
Version: 8.4CC: efedin
Target Milestone: betaKeywords: Patch, Triaged, Upstream
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Fixed In Version: net-snmp-5.8-22.el8 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-11-09 19:48:29 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Sam Wachira 2021-06-17 13:49:15 UTC
Description of problem:
When sending traps on SNMP v3 using net-snmp-5.8-20 in RHEL 8.4, the engineTime value remains zero.
This is a problem as the receiving agent does not accept engineTime with a zero value, it expects engineTime and engineBoots values to progress.

snmptrap by default runs the code below to set session.engineBoots and session.engineTime for SNMP v3 traps (not inform).
         session.engineBoots = 1;
     if (session.engineTime == 0)    /* not really correct, */
         session.engineTime = get_uptime();  /* but it'll work. Sort of. */

Version-Release number of selected component (if applicable):

How reproducible:
Reproduced by customer

Steps to Reproduce:
1. Sending traps on SNMP v3 using net-snmp-5.8-20 in RHEL 8.4
2. If receiving agent does not accept engineTime with a zero value, it will fail

Actual results:
Unable to send SNMP traps.

Expected results:
Should be able to send SNMP traps.

Additional info:
Upstream patch is already in place for snmptrap binary. It resolves the issue by setting the library engineBoots and engineTime values before sending.

Comment 8 errata-xmlrpc 2021-11-09 19:48:29 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (net-snmp bug fix and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.