[Top] [All Lists]

Re: [nv-l] Howto list only managed nodes ???

To: nv-l@lists.us.ibm.com
Subject: Re: [nv-l] Howto list only managed nodes ???
From: Francois Le Hir <flehir@ca.ibm.com>
Date: Thu, 3 Nov 2005 10:39:39 -0500
Delivery-date: Thu, 03 Nov 2005 15:40:13 +0000
Envelope-to: nv-l-archive@lists.skills-1st.co.uk
In-reply-to: <20051103151703.GB6672@localhost.localdomain>
Reply-to: nv-l@lists.us.ibm.com
Sender: owner-nv-l@lists.us.ibm.com

You could create a smartset that contain all the managed node (isNode=TRUE
and IP Status != unmanaged). You can then use nvUtil to get the list of
node contained in the smartset from a script.
You can also use nvdbformat to export a list of all the nodes with specific
parameters. I use Netview on Unix so I am not sure if nvUtil or nvdbformat
are available with the windows version. As the windows version is using a
standard database, you could probably make direct queries in the database
to get the list of node.

Salutations, / Regards,

Francois Le Hir
Network Projects & Consulting Services
IBM Global Services
Phone: (514) 964 2145

             Michael D Schleif                                             
             Sent by:                                                   To 
             owner-nv-l@lists.         nv-l mailing list                   
             us.ibm.com                <nv-l@lists.us.ibm.com>             
             11/03/2005 10:17                                      Subject 
             AM                        [nv-l] Howto list only managed      
                                       nodes ???                           
             Please respond to                                             

Netview/Window, v7.1.4, FP3

I am trying to automate un-managing discrete sets of nodes after
discovery finds them.  nvmaputil facilitates this; but, first, I need to
identify and list appropriate nodes.

I have not found necessary information from ovmapdump nor ovtopodump

Ideally, we will periodically dump a list of managed node, parse that
list for nodes to be un-managed, and un-manage them.  It is not
desirable to try to un-manage nodes that are already un-managed ;<

What am I missing?

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