[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: Michael D Schleif <mds@helices.org>
Date: Thu, 3 Nov 2005 12:33:13 -0600
Delivery-date: Thu, 03 Nov 2005 18:33:46 +0000
Envelope-to: nv-l-archive@lists.skills-1st.co.uk
In-reply-to: <436A30D3.4010000@gmail.com>
Mail-followup-to: nv-l@lists.us.ibm.com
References: <20051103151703.GB6672@localhost.localdomain> <436A30D3.4010000@gmail.com>
Reply-to: nv-l@lists.us.ibm.com
Sender: owner-nv-l@lists.us.ibm.com
User-agent: Mutt/1.5.9i
* Paul Stroud <nvladmin@gmail.com> [2005:11:03:10:46:27-0500] scribed:
> Try this on for size:
> smartsetutil e '"IP Status"!=Unmanaged && isNode=TRUE"
> This shoud give you a list of all managed nodes on the map.
> Paul

O, the dreaded single vs. double quote windoze shell issue ...

This does not return and error ;>

    smartsetutil e "'IP Status'!=Unmanaged && isNode=TRUE"

However, it returns *EVERY* node it knows about, _including_ un-Managed
nodes ;<

In fact, the following returns _nothing_:

    smartsetutil e "'IP Status'=Unmanaged && isNode=TRUE"

As others have suggested, I created Smartsets with these two (2)

    ("IP Name" ~ "^P4.*$") AND ("IP Status" = "Unmanaged") AND (isNode = TRUE)

    ("IP Name" ~ "^P4.*$") AND ("IP Status" != "Unmanaged") AND (isNode = TRUE)

I am told that the convention at this customer is to prefix PC hostnames
with `P4', hence the "IP Name" criterion.

Once created, I display the submaps; and the results are identical to
your CLI: the un-Managed Smartset is *empty*; and the Managed Smartset
shows un-Managed nodes.  Yes, we display un-Managed nodes in a different
color; and when the icon is right-clicked, the topmost option is
`Manage', as opposed to `Unmanage' for Managed nodes.

What am I missing?

What do you think?

Thank you, all of you, for your attention to these issues ...

> Michael D Schleif wrote:
> >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
> >output.
> >
> >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 ;<

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

Attachment: signature.asc
Description: Digital signature

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

Archive operated by Skills 1st Ltd

See also: The NetView Web