Yes, there are .baroc files required for TEC. TEC ships with a
netview.baroc file (and a netview.rls file) that must be imported into your
TEC rule base in order for the basic NetView events to be displayed and
correlated on the TEC server. If you add new events, these must also be
defined to TEC using a baroc (BAsic Recorder of Objects in C) file. TEC
requires that all events be classified as part of a class structure which
begins with his basic Event class, and all other must be subclasses of
that.
NetView provides a class structures of TEC_ITS-* for its events. Each one
is defined as a subclass of Event in the netview.baroc file shipped with
TEC. You can use the TEC_IT_BASE event class when you send your new events
to TEC and then no new baroc is needed, or you can use whatever class you
like but then you must provide a baroc to define it, either in terms of
TEC_IT_BASE, or some other subclass, or of Event itself.
So if you start sending new events to TEC, then you have TEC configuration
to do. NetView for UNIX will generate a simple baroc file from mib2trap.
But Windows users must devise one of their own, just as they have to devise
the proper entries for the tecad_nv6k oid, cds, and conf files, on their
own.
I'll wager that no one can answer your question about what baroc files must
be imported into TEC unless they know what parsing errors you are getting.
If all this is completely new to you, then I recommend a call to Support so
that specialist who is knowledgeable about both sides can help you.
NetView is currently a part of TEC, and the design assumption is that those
users who are sending events to TEC will be trained in TEC or at least
knowledgeable about how it works, since that is the bigger, and more
difficult product to set up.
James Shanks
Level 3 Support for Tivoli NetView for UNIX and Windows
Tivoli Software / IBM Software Group
|