Re: NetView NT Smartset Problem.

1999-06-13 19:04:48
Subject: Re: NetView NT Smartset Problem.
From: Leslie Clark <lclark AT US.IBM DOT COM>
To: nv-l AT lists.tivoli DOT com
Date: Sun, 13 Jun 1999 19:04:48 -0400
The problem you are running into is that 'IP Address' is not a property of a
It is a property of an interface card, but not a node. Look at ovobjprint -s
If you were to take James' example and add the criteria 'isNode' is True (to use
the AIX form), you would come up empty.

The collection editor on AIX is arranged a little differently than on NT. On
you can choose between Attributes, Collections, Object lists, and Subnet
to specify the sort of criteria. The Attribute 'IP Addess' won't work for nodes.
But the Subnet WILL work for nodes. There seems to be some special
handling in there that checks all entries in the TopM Interface List of a node.

The question then becomes how that AIX functionality is mapped to the NT
Snartset dialog. I don 't have one in front of me, but maybe this is enough

When you use wildcards, use the 'LIKE, not the 'EQUALS'.

And who are you calling a tweak?


Leslie A. Clark
IBM Global Services - Systems Mgmt & Networking

I have seen IP Address wildcards work..

What failed for me was - when I try to pick up  vendor specific devices by
sysObjectId=* (Using the appropriate syntax), it doesnt come
up with a list.

Arent IBM tweaks shakey?

>From: "Boyles, Gary P" <gary.p.boyles AT INTEL DOT COM>
>Reply-To: Discussion of IBM NetView and POLYCENTER Manager on NetView
>        <NV-L AT UCSBVM.ucsb DOT edu>
>To: NV-L AT UCSBVM.ucsb DOT edu
>Subject: Re: NetView NT Smartset Problem.
>Date: Thu, 10 Jun 1999 15:02:10 -0700
>It seemed to work fine for a single selection (as you describe below),
>where the problem comes in... is if you try to AND it with something
>Question:  Did you try this to, or just the single condition?
>Gary Boyles
>-----Original Message-----
>From: James Shanks [mailto:James_Shanks AT TIVOLI DOT COM]
>Sent: Thursday, June 10, 1999 2:53 PM
>Subject: Re: NetView NT Smartset Problem.
>I don't know what to tell you guys.  I have 5.1.1 installed and I did just
>what Gary did and it works only too well for me.
>I  selected "IP Properties" and "Using Wildcards", clicked the IP Address
>radio button, and used the Tivoli subnet  146.84.*.*, and then hit APPLY.
>I got a huge number of hits.
>James Shanks
>Tivoli (NetView for UNIX) L3 Support
>Xu He <xuhe AT YAHOO DOT COM> on 06/10/99 04:49:59 PM
>Please respond to Discussion of IBM NetView and POLYCENTER Manager on
>cc:    (bcc: James Shanks/Tivoli Systems)
>Subject:  Re: NetView NT Smartset Problem.
>I tried this a while back, I don't think it worked for
>me either.  Because an IP address is normally
>associated with a NIC, and which is a subcomponent of
>a Node.  So if you AND the result of the IP Address
>search with isNode, it won't work.  Right now, I don't
>know of any way to create a smartset of Nodes using
>strictly IP Addresses.
>May be James and Leslie can enlighten us on how this
>can be done, or just tell us that it's impossible.
>--- "Boyles, Gary P" <gary.p.boyles AT INTEL DOT COM> wrote:
> > To anyone,
> > I ws wondering if anyone on NT has gotten this kind
> > of smartset example
> > to work  (mine doesn't seem to cut it).
> >
> > 1)  I'm trying to create a smartset using:
> > *       "IP Properties" (Using Wildcards) "IP
> > Address"
> > *       I put in the address such as   132.233.*
> >
> > 2) I do an "Add To Advanced", and then try to AND
> > this with
> > *       "Other Properties" (Type) "Node".
> >
> > The result is... I never get anything in my
> > smartset, even though
> > I have many nodes in the address-range, and it
> > doesn't find any of them.
> >
> > BTW -- I've tried using "132.233.*.*", and
> > "132.233*, and "132.233.*".
> >
> > Same results.
> >
> > Any suggestions?
> >
> > Thanks.
> >
> > Gary Boyles
> >
>Xu He
>Consulting Services Engineer
>Network Solutions, Inc
>Do You Yahoo!?
>Get your free @yahoo.com address at http://mail.yahoo.com

Get Free Email and Do More On The Web. Visit http://www.msn.com