Nagios Support Forum

The system is 5.8.4 on RHEL 7.8. and was updated 6/10/2021. I did a yum update sometime after that.
Now, whether I have dns_enable set to 0 or 1 in snmptt.ini, ILO traps are logged in snmptrapd.log, not in snmptt.log are in snmptt.debug, and are in the Admin, Unconfigured Objects page as UNKNOWN.

As recently as the end of June ILO traps were being processed correctly w/ dns_enable set to 1, and have been for many years.
ILOs aren't resolvable forward or reverse, and are a mix of IPv4 and IPv6l.
I see no new traps on any ILO, but have only looked at IPv4.
I am seeing tons of traps being processed constantly from a firewall, so traps generally work.
It looks like the snmptt version was bumped in the recent update.

I'm a bit confused since I see nothing set up incorrectly. Any ideas?

Thanks

For that issue, this fixed it after I posted and only then remembered to do a search. https://support.nagios.com/kb/article/s ... p-886.html

Unfortunately, I'm seeing snmptt using various creative ways to mangle IPv6. I found the following in my notes and added it:

Edit /usr/sbin/snmptt
Line:
:3256
$tempvar[0] =~ s/[^a-zA-Z0-9.\-_]//g; # Remove most non alphanumeric characters
You can try replacing that line with this:
if ($tempvar[0] =~ m/IPv6/) {
$tempvar[0] =~ s/UDP\/IPv6: \[//g;
$tempvar[0] =~ s/\%.*$//g;
} else {
$tempvar[0] =~ s/[^a-zA-Z0-9.\-_]//g; # Remove most non alphanumeric characters
}
systemctl restart snmptt; systemctl status snmptt


Here are examples from a 5.8.5 system in the admin, unconfigured objects today:
2001:4888:a06:381b:f1:180:0:701]:162
2001:4888:a06:381b:f1:9:0:2]:41632
2001:4888:a06:381b:f1:9:0:1]:34924

I guess I'll add to the block above a regex to remov everything from ] and let it wait for some traps.

Here is the last one:

https://support.nagios.com/forum/viewto ... 16&t=61627
https://support.nagios.com/forum/viewto ... 54#p325954

Hi,
Sorry about duplicating my months ago post about snmptt. I've been making the changes to snmptt as I upgrade systems and it seems fine now.
Feel free to close this one.
Thanks

No problem, glad it's working, locking it up.