Details
-
Bug
-
Status: Resolved (View Workflow)
-
Minor
-
Resolution: Fixed
-
29.0.1, Meridian-2021.1.9
-
None
-
Security Level: Default (Default Security Scheme)
-
None
-
OpenNMS Horizon on CentOS 8.5
OpenNMS Meridian on RHEL 8.2
-
2
-
Horizon 22 - Jan 19 - Feb 2, Horizon 22 - Feb 2 - Feb 16, Horizon 22 - Feb 16 - Mar 2, Horizon 22 - Mar 2 - 16, Horizon 22 - March 16 - 30
-
Backlog CM
Description
I noticed that a few values of trap parameters are incorrectly stored in the database.
Example 1 :
snmptrap -v 1 -c public 127.0.0.1 '1.3.6.1.4.1.9.9.215.2' '172.24.1.121' 6 1 '55' 1.3.6.1.4.1.9.9.215.1.1.8.1.2.1 x 0200140020d229e6e6000100 1.3.6.1.4.1.9.9.215.1.1.8.1.3.1 i -663291219
If you use this trap, the parameter value is correct in the event, but incorrect in the database (see the attached file, where you get the parameters from the database).
The parameter value is converted from 0x0200140020d229e6e6000100 to AgAUACDSKebmAAE.
Example 2 :
If you send a trap with the parameter value s "/var: less than 5% free (= 3%)" The parameter value is converted from /var: less than 5% free (= 3%) to /var: less than 5% free (%61 3%).
