You are right the NetView books don't go into detail about the TEC adapter
files. It was assumed that when NetView became part of TEC, anyone doing
TEC forwarding would already be familiar with how TEC and it's adapters
functioned. The information development folks declined to replicate
similar information found in the TEC Event Adapter Guide. Just take a
look at the OpenView adapter section and you'll see most of the same stuff.
When you see an attribute in the CDS file defined like this
ATTR(=, "nvObject" );
the quoted text is a name which is being used in place of an OID. The OIDs
are defined in the tecad_nv6k.oid file:
"nvObject" "1.3.6.1.4.1.2.6.3.1.1.3"
These are the variables discussed in the Appendix of the of the NetView
users Guide
"nvApplNbr" "1.3.6.1.4.1.2.6.3.1.1.2" varbind 1 an integer
representing the originating NetView process
"nvObject" "1.3.6.1.4.1.2.6.3.1.1.3" varbind 2 hostname
"nvEventDescr" "1.3.6.1.4.1.2.6.3.1.1.4" varbind 3 formatted
description of the event
"nvEventInfo" "1.3.6.1.4.1.2.6.3.1.1.5" varbind 4
additional information, typically timestamp, object id number from the
NetView database
"nvEventOptInfo" "1.3.6.1.4.1.2.6.3.1.1.6" varbind 5 fixed keyword
"openview"
Some events have more than 5 varbinds, so those are treated as special
cases in the CDS.
A typical TEC event usually looks like this:
TEC_ITS_NODE_STATUS;source=NV6K;sub_source=NET;origin=9.27.144.151;adapter_host=jshanks1.raleigh.ibm.com;hostname=ALBERT-T-30.raleigh.ibm.com;msg='Node
Down. ';category=2;nodestatus=2;nvhostname=9.27.131.176;END
origin should be the IP address of the host the trap is about; hostname is
what that IP address should resolve too
adapter_host should be the hostname of the NetView box, and somewhat
paradoxically, nvhostname should be its IP address.
If yours don't look this way, then their is a good chance you still have
some name resolution issues.
HTH,
James Shanks
Level 3 Support for Tivoli NetView for UNIX and Windows
Tivoli Software / IBM Software Group
|