nv-l
[Top] [All Lists]

Re: [nv-l] Node down events.

To: <nv-l@lists.us.ibm.com>
Subject: Re: [nv-l] Node down events.
From: "Jon Austin" <JAustin@cms.hhs.gov>
Date: Thu, 11 Mar 2004 07:19:33 -0500
Delivery-date: Thu, 11 Mar 2004 12:31:51 +0000
Envelope-to: nv-l-archive@lists.skills-1st.co.uk
Reply-to: nv-l@lists.us.ibm.com
Sender: owner-nv-l@lists.us.ibm.com
The scripting from Fawad is a good idea. 
It does includes the overhead of the ovaction daemon and using
wpostemsg. 

Another approach to explore is DNS over-ride. Your node objects have
FQDN because
of how the IP address is resolved on the 1st interface of the device.
Place /etc/hosts
ahead of DNS lookups (in AIX, this is the hosts statement in
/etc/netsvc.conf), and then
add /etc/hosts entries on your NetView server with the short name. An
nmdemandpoll/config poll
afterwards will fix up the object automatically.

Of course this solution has all the complexity involved in maintaining
a hard-coded /etc/hosts
files admist a changing environment. And over TEC 3.8/3.9, the
direction seems clear through
the new TEC event slot fqhostname across many of the products that FQDN
is the direction
and standard that Tivoli is setting in future event processing/rules
development. 

Perhaps your TEC programmer could better handle this requirement where
it belongs, at TEC. 


Jon Austin




>>> Richard.Fernandez@msfc.nasa.gov 03/10/04 10:11AM >>>
Does anyone have an Idea how to forward the node down event to TEC with
just
the short name in the event.  Currently we are forwarding the FQDN.  
 
 
 

Thank You! 

Rick Fernandez 
Phone: 256-544-5106 
Computer Science Corporation 
Marshall Space Flight Center 

 

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

Archive operated by Skills 1st Ltd

See also: The NetView Web