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

[Paul <pstroud@bellsouth.net>]

Are they NetView traps or agent traps? If you look at the context
help available on that display, you will find you can set this variable
by using $V2. I would check that panel as I am going from memory,
but I think thats correct.

Paul



Per Lütkemeyer wrote:

> 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
> *******************************************************************************