Re: [nv-l] trapd.conf and custom slot name

[James Shanks <jshanks@us.ibm.com>]

If I understand what you said, you added
a field to the object in the NetView database.  Well, there is no
mechanism provided in trapd to extract that field.  He has no way
of knowing about it.  What you can do in trapd.conf is manipulate
the varbinds that are sent with the trap itself, but you cannot add anything
new except fixed text, or combinations of existing varbinds using the PRINTF
syntax.

Either you will have to provide one
an extraction mechanism yourself and make it part of your TEC ruleset,
or you will have to find what you want in the trap varbinds.    


James Shanks
Level 3 Support  for Tivoli NetView for UNIX and Windows
Tivoli Software / IBM Software Group

"Per Lütkemeyer" <pel@dmdata.dk>
Sent by: owner-nv-l@lists.us.ibm.com

03/04/2004 06:23 AM

Please respond to
nv-l

To	nv-l@lists.us.ibm.com
cc
Subject	[nv-l] trapd.conf and custom slot name

Hi, 

A question when integrating  Netview 7.14 with TEC 3.9

Reason for my question is that we want to use short nodename i Netview
and a longer nodename i TEC. 
So we have added an extra field at each object i netview, called tec_nodename
where the long name is kept. 

Now I want to transfer the content of field "tec_nodename"  in
slot map "nv_var15"  to TEC 

So the big question is what syntax should I use in trapd.conf ???

I have tried 
        nv_var15 tec_nodename 
but the result is that nv_var15 contains the fixed text  "tec_nodename"

Any suggestions ........ 

Regards 
Per Lütkemeyer 
DMdata a/s 


Example from my trapd.conf : 
***********************************************************************************
IBM_NVNDWN_EV {1.3.6.1.4.1.2.6.3} 6 58916865 N 4 0 "Status Events"
$3 
EVENT_CLASS TEC_ITS_NODE_STATUS 
BEGIN_SLOT_MAPPING 
 nvhostname $NV_IPADDR 
 nv_var15 tec_nodename 
 msg $V3 
 nodestatus DOWN 
 iflist $V8 
END_SLOT_MAPPING 
SDESC 
This event is generated by IBM Tivoli NetView when
it detects a node is down 

The data passed with the event are: 
    1) ID of application sending the event
    2) Name or IP address 
    3) Formatted description of the event
    4) Timestamp of the event and objid of the node object
    5) Database name 
    6) Selection Name 
    7) (not used) 
    8) Interface list 
EDESC 
*******************************************************************************