[Top] [All Lists]

Re: [nv-l] Flag smartset membership at TEC ???

To: nv-l@lists.us.ibm.com
Subject: Re: [nv-l] Flag smartset membership at TEC ???
From: James Shanks <jshanks@us.ibm.com>
Date: Fri, 14 Apr 2006 12:33:50 -0400
Delivery-date: Fri, 14 Apr 2006 17:34:01 +0100
Envelope-to: nv-l-archive@lists.skills-1st.co.uk
In-reply-to: <20060414155551.GA26322@localhost.localdomain>
Reply-to: nv-l@lists.us.ibm.com
Sender: owner-nv-l@lists.us.ibm.com
I see no simple nor easy way to way to do this.  It's the same case as the
guy who wanted to have the Interface Name added to the threshold traps from

That information is not in the trap that netmon sends, so it's not in the
trap that trapd gets and passes on the TEC adapter, tecad_nv6k.
And there is no user exit in the tecad code to allow you to do your own

So to add it on the NetView side, you'd have to intercept the NodeUp and
NodeDown events, run  a script as a hidden command out of trapd.conf which
determined smartset membership (using smartsetutil) or read the object
database record for that object (using ovobjprint) and then issued a new
trap (using snmptrap) with that information.  You'd change the CDS to send
that trap rather than the standard NodeUp and  NodeDown.  Or you could just
send the event to TEC using postemsg in that script.

On the TEC side you could build a file from the NetView smartsetutil  or
ovobjprint output file which identified all your key devices by type, and
then you'd create a TEC rule to add that slot.   I know that is not dynamic
but it's an option.

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

             Michael D Schleif                                             
             Sent by:                                                   To 
             owner-nv-l@lists.         nv-l mailing list                   
             us.ibm.com                <nv-l@lists.us.ibm.com>             
             04/14/2006 11:55                                      Subject 
             AM                        [nv-l] Flag smartset membership at  
                                       TEC ???                             
             Please respond to                                             

NV v7.1.4; FP04; Windows Server 2003; SP1

We have several specific smartsets to identify various types of objects
(e.g., printers, switches, &c.)

When we receive in TEC TEC_ITS_NODE_STATUS events, we want to know
_which_ type of object generated that event.

We do NOT want to change nor modify any existing behaviors; rather, we
want to develop TEC rules that will do specific tasks, based on whether
that "NODE" is a printer, or a switch, or whatever ...

How can we do this?

What do you think?

Best Regards,

mds resource
Dare to fix things before they break . . .
Our capacity for understanding is inversely proportional to how much
we think we know.  The more I know, the more I know I don't know . . .
(See attached file: signature.asc)

Attachment: signature.asc
Description: Binary data

<Prev in Thread] Current Thread [Next in Thread>

Archive operated by Skills 1st Ltd

See also: The NetView Web