Thank you ....using the command line allowed the mibs to be installed......so is this a bug in the gui application ?
Coming back to the remainder of the mibs and fixing the issues of non reporting into XI, but can be seen in NSTI, here is how my setup runs:
Because I have many Cisco and other manufacturer mibs installed, in my snmptt.ini file I referenced several snmptt.conf files as per below:
Code: Select all
[TrapFiles]
# A list of snmptt.conf files (this is NOT the snmptrapd.conf file). The COMPLETE path
# and filename. Ex: '/etc/snmp/snmptt.conf'
snmptt_conf_files = <<END
/etc/snmp/snmptt.conf
/etc/snmp/snmptt.conf.cisco_3
/etc/snmp/snmptt.conf.adtran
/etc/snmp/snmptt.conf.loop
I did this so that I could easily go through each individual file and edit the severity levels, or else if I used one snmptt.conf file, the file would have been huge and unmanageable.
So, according to tgriep's post on Wed 24th of June, he said....
The EXEC line is used to process a trap for Nagios XI.
That line is created when the MIB file is uploaded to the XI system and the Process Trap box is checked.
So here are the problems I am faced with and some options to make life easier would be greatly appreciated.....
1) If I delete the mibs and start over it will put everything in to one single snmptt.conf file....again a huge file.
2) It will take forever to go back and edit all the severity levels
3) I'm not sure any mores as to what were the original mibs supplied by Nagios so I may delete the wrong mibs
4) When i load mibs via the UGU, the user and group of the file is "apache" ....does that need to be changed or is that ok to lease as is ?
Your Thoughts ?