Many thanks to Duncs for the reply.
I downloaded mib file (it contains references to other mibs) specifically for the application I use to generate traps. I copied it to "all" directory, and after "promoting mib", the file was copied to "load" as expected. Trap name changed to reference new mib file, however, I still get "Trapname not fully translated". Here is full contents of the trap: Hostname_xxx UDP: [127.0.0.1]:666 DISMAN-EVENT-MIB::sysUpTimeInstance 7:13:54:12.67 SNMPv2-MIB::snmpTrapOID.0 SM10-R2-MIB::sm10-R2.0.2 SM10-R2-MIB::deviceHostIPType unknown SM10-R2-MIB::deviceHostIPAddr " " SM10-R2-MIB::deviceHostName SM10-R2-MIB::deviceUserLabel xxxx SM10-R2-MIB::deviceErrorCode SM10-R2-MIB::eventTime Nov 6, 2009 1:34:43 AM SM10-R2-MIB::trapDescription The persistent monitor running on Host Hostname_xxx can now reach th SM10-R2-MIB::componentType SM10-R2-MIB::componentLocation It seems like the trap is fully translated, or do I miss something? Another thought, do all mibs referenced in my sm10-R2.0.2 should also be copied to "load" directory? Because that's not happening, and all I have in "load" dir is sm10-R2.0.2 mib file. Please let me know. Thanks! From: opsview-users-boun...@lists.opsview.org [mailto:opsview-users-boun...@lists.opsview.org] On Behalf Of Duncan Ferguson Sent: Wednesday, November 04, 2009 1:01 PM To: Opsview Users Subject: Re: [opsview-users] promoting MIB On 29 Oct 2009, at 12:19, <rsneide...@krafteurope.com> < rsneide...@krafteurope.com> wrote: I've read several posts in this mailing list regarding this same issue, and found no solutions. The problem is that I get "Trapname not fully translated" in SNMP TRAP Exceptions page, but clicking "Promote MIB" and Re-processing don't help [ cut ] Next trap "Trapname not fully translated" again... Restarting snmpd and snmptrapd don't help as well as restarting sever itself :/ I also coppied MIB files from /usr/share/snmp/mibs to /usr/local/nagios/snmp/all/ but still the same problems.... did anyone find the solution to this? Please let me know! This is generally due not having an accurate enough MIB to cope with the trap. THe mosst specific MIB found is used, which in your case isn't specific enough. Use a MIB search site to find a better MIB and put onto the correct directory on the master http://docs.opsview.org/doku.php?id=opsview3:faq#how_can_i_load_extra_mi b_s_into_opsview Duncs -- Duncan Ferguson Senior Developer Opsera Limited | Unit 69 Suttons Business Park Reading | Berkshire | RG6 1AZ | UK Phone: +44 (0) 845 057 7887 Mobile: +44 (0) 7968 148 748 Skype: duncan_j_ferguson Email: duncan.fergu...@opsera.com www.opsera.com <http://www.opsera.com/> Opsera Limited is registered in the UK under Company Number 5396532. Our registered office is Gorse View, Horsell Rise, Woking, Surrey, GU21 4RB.
<<image001.gif>>
_______________________________________________ Opsview-users mailing list Opsview-users@lists.opsview.org http://lists.opsview.org/lists/listinfo/opsview-users
