Larry,
The way events are handled in NetView for Windows bears little resemblance
to what is done in NetView for UNIX, because they were designed by
different design teams at different times. Going to Windows from UNIX is
a completely new learning experience.
The Windows TEC adapter is difficult for the novice to configure. It's
based on the NetView adapter that TEC shipped before 3.7, which originated
when Tivoli was a separate company. After Tivoli was acquired by IBM and
NetView got folded into TEC, they stopped shipping the UNIX version of that
adapter because nvserverd already did that job; and the old code was ported
to NetView for Windows, which did not have a TEC adapter originally. Since
it works like all the other TEC adapters, especially the current OpenView
one, the decision was made not to produce any special documentation for the
NetView for Windows adapter but point the user to the TEC Adapters Guide.
If I were you, I would go read what that manual says about the OpenView
adapter.
There is only one simple way to configure events for the NetView for
Windows TEC adapter, and that is with the mib2trap utility which ships with
NetView for Windows 7.1.5. It was enhanced to produce OID, CDS, and BAROC
files if the user added a prefix for them on the command:
mib2trap <mib_name> <addtrap>.bat <prefix>
Then you can cut-and-paste the OID file output into your tecad_nv6k.oid
file and the CDS file output into your teacd_nv6k.cds and then either rerun
the tecconfig.bat configurator or just edit the tecad_nv6k.conf file to
add Filter and FilterCache statements for the new classes. Obviously you
have to stop the daemon first and then restart him when your changes are
complete.
The trouble is, of course, that you need a MIB which defines all the traps
you need. If you don't have one, then the configuration is difficult
because you have to know what variables are sent with each trap and in what
order so you can select and map them. In that case, I would temporarily
change the definition of those traps in trapd.conf so that the Event
Description just says $*. Then each variable will be printed in the
trapd.log when the trap comes in and you can use that as a guide to
configure what the CDS and OID files should look like. After you are
finished you can change the trap definition back to whatever you had
before.
James Shanks
Level 3 Support for Tivoli NetView for UNIX and Windows
Network Availability Management
Network Management - Development
Tivoli Software, IBM Corp
_______________________________________________
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)
|