|
You are laboring under some kind of misapprehension here.
xnmloadmib2 and mib2trap use exactly the same code. If you can load your V2 MIB with xnmloadmib2, then mib2trap can parse it. So if you are getting mib2trap errors, then there is another issue there. Perhaps the error is that some prior definition is missing? We can help you get around that, if that's it. But no one can advise you unless you tell us all what MIBs you tried and exactly what error messages you received as a result.
Any time a trap has no configuration in trapd.conf you will get the "no fmt found" message. You need not do anything to get it.
When you do, it will tell you exactly what you have to do to avoid it in the future. It gives you the enterprise id, and the specific and generic ids you need to create your definition with xnmtrap, and it lists all the variables, so you can choose which ones are meaningful and which ones you want to display. Even with mib2trap, most users modify the default definition that mib2trap provides because it is clumsy and just displays everything, in exactly the same fashion as the "no fmt found" message. So using one rather than the other is often not much of a help.
If you configure just the enterprise id, you will still get "no fmt found" because the specific traps are missing. The only way around that completely is to define a single enterprise default trap. You can do with xnmtrap as well. Pull down the box which usually says "generic" and select the default value "-1" instead. Then trapd will use the same format for all traps for this enterprise, if that is what you want.
James Shanks
Level 3 Support for Tivoli NetView for UNIX and Windows
Tivoli Software / IBM Software Group
 "Christopher J Petrina" <cjp8@meadwestvaco.com>
|
|
To: nv-l@lists.us.ibm.com
cc:
Subject: [nv-l] Mib2trap alcatel AOS devices |
I saw a couple people out there with this issue but no resolution.
We have some new Alcatel devices that do not look like they support the old xylan mib structure. mibbrowsed to the ojectID and it returns 1.3.6.1.4.1.6486.800 on the new one where the old alcatels built off the xylan structure were 1.3.6.1.4.1.800. we have old one s as well. The xylan mibs contain NOTIFICATION-TYPE and TRAP-TYPE information, however a mib2trap will not work. They always report errors. Anyone else using alcatel devices especially those running the AOS 5.1.4. The only MIBS I have found for those are V2 MIBS that use the MODULE-IDENTITY structure that is not supported in the xnmloadmib file. it only works in the xnmloadmib2 which as we all know are not able to create traps for trapd to understand.
2nd question: I created in xnmtrap an enterprise identification of Alcatel and the enterpriseID of 1.3.6.1.4.1.6486.800 -> with just that and the devices configured to send traps I should at least receive a trap fromt he device should I not? even if I get the FMT no format for trap found?
Thanks
Chris Petrina
|