|
I'm afraid that don't see what your complaint is about. What is it that you are looking for? What is the TEC guy expecting?
If you supply the baroc file, then all the TEC guy has to do is load it.
The default TEC setup is that every trap is a subset of EVENT (ISA EVENT). NetView comes along and introduces the ITS_BASE structure, so that
vendor traps become subclasses of TEC_ITS_BASE, and the NetView rule base defines TEC_ITS_BASE as a subclass of EVENT. That's how mib2trap defines each trap in the baroc file he creates. But mib2trap will take an optional parameter to specify an base class you want.
So if you want all your Cisco traps to have a base class of CISCO you can specify that. Then you'll have to provide an additional baroc definition which says that CISCO ISA EVENT, of course, or that CISCO ISA TEC_ITS_BASE. How you do it, is up to you. You can make your traps fit any hierarchy you want. It's not exactly rocket science. But it does require planning and effort, though once you have settled on your event schema, you should only have to do it once.
The mib2trap utility cannot be all things to all people; it just provides a starting point. And since TEC customization is totally up to the user, if you want something beyond what it gives you, then yes, you'll have to edit the addtrap and baroc files. But where is it written that you would never have to do that?
That's a lot easier than doing them all from scratch.
And incidentally, mib2trap in 7.1.5 offers even more customizing options than does 7.14 when you specify a baroc file. It will define all the MIB variables as slots in the event, and add STRING defs for them in the baroc, so that you can use them in TEC rules for correlation and duplicate detection. But you'll still have to examine the baroc and see whether it does what you want it to do. There's no free lunch.
James Shanks
Level 3 Support for Tivoli NetView for UNIX and Windows
Network Availability Management
Network Management - Development
Tivoli Software, IBM Corp
 Michael_Noonkesser@bluecrossmn.com
Michael_Noonkesser@bluecrossmn.com
Sent by: nv-l-bounces@lists.ca.ibm.com
01/04/2007 10:25 AM
Please respond to
Tivoli NetView Discussions <nv-l@lists.ca.ibm.com> |
|
|
Lists-
I am running NV 7.13 FP04 Sol9 soon to be 7.15 Sol10
I have a set of vendor supplied mibs that once compiled with mib2trap etc, yield 1400 individual TEC_CLASS defined in the .baroc file. The TEC admin does not want to see 1400 different CLASS defs.
Is there a way to handle situation such as this or am I stuck with a manual edit of the baroc to remedy this? This is becoming more and more frequent as we implement vendor/application specific mibs, so a repeatable process would be very useful if one exists.
Thx-
Regards,
Mike N.
----------------------------
Important news about email communications:
If our business rules identify sensitive information, you will receive a ZixMail Secure Message with a link to view your message. First-time recipients will be asked to create a password before they are granted access. To learn more about ZixMail, ZixCorp Secure Email Message Center, and other ZixCorp offerings, please go to http://userawareness.zixcorp.com/secure4/index.php ----------------------------
The information contained in this communication may be confidential, and is intended only for the use of the recipient(s) named above. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this communication, or any of its contents, is strictly prohibited. If you have received this communication in error, please return it to the sender immediately and delete the original message and any copy of it from your computer system. If you have any questions concerning this message, please contact the sender.
Unencrypted, unauthenticated Internet e-mail is inherently insecure. Internet messages may be corrupted or incomplete, or may incorrectly identify the sender._______________________________________________
NV-L mailing list
NV-L@lists.ca.ibm.com
Unsubscribe:NV-L-leave@lists.ca.ibm.com
http://lists.ca.ibm.com/mailman/listinfo/nv-l (Browser access limited to internal IBM'ers only)
_______________________________________________
NV-L mailing list
NV-L@lists.ca.ibm.com
Unsubscribe:NV-L-leave@lists.ca.ibm.com
http://lists.ca.ibm.com/mailman/listinfo/nv-l (Browser access limited to
internal IBM'ers only)
|
