nv-l
[Top] [All Lists]

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

To: nv-l@lists.us.ibm.com
Subject: [nv-l] trapd.conf and custom slot name
From: "Per Lütkemeyer" <pel@dmdata.dk>
Date: Thu, 4 Mar 2004 12:23:12 +0100
Delivery-date: Thu, 04 Mar 2004 11:38:50 +0000
Envelope-to: nv-l-archive@lists.skills-1st.co.uk
In-reply-to: <6353E0AB365A984BADDD6ED03C3598E601EA88@tecnologia.tecsystem.com.ar>
Reply-to: nv-l@lists.us.ibm.com
Sender: owner-nv-l@lists.us.ibm.com

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
*******************************************************************************
<Prev in Thread] Current Thread [Next in Thread>

Archive operated by Skills 1st Ltd

See also: The NetView Web