nv-l
[Top] [All Lists]

Re: [nv-l] Using @limit_discovery in a seedfile

To: nv-l@lists.us.ibm.com
Subject: Re: [nv-l] Using @limit_discovery in a seedfile
From: Jane Curry <jane.curry@skills-1st.co.uk>
Date: Tue, 29 Mar 2005 21:01:25 +0100
Delivery-date: Tue, 29 Mar 2005 21:02:03 +0100
Envelope-to: nv-l-archive@lists.skills-1st.co.uk
In-reply-to: <D61DF45BFD62304689F621F93CBF0AA810ABAD3F@aus0010mb01.ausc.irs.gov>
References: <D61DF45BFD62304689F621F93CBF0AA810ABAD3F@aus0010mb01.ausc.irs.gov>
Reply-to: nv-l@lists.us.ibm.com
Sender: owner-nv-l@lists.us.ibm.com
User-agent: Mozilla Thunderbird 0.5 (X11/20040208)
Paul's presentation is available from the Tivoli Support Technical Exchange website - it has document reference 1201287. I simply went to:
http://www-306.ibm.com/software/sysmgmt/products/support/supp_tech_exch.html
and searched for this document number.

Cheers,
Jane

McGuire Larry G wrote:


Was there any documentation presented during this exchange?


-----Original Message-----
From: owner-nv-l@lists.us.ibm.com [mailto:owner-nv-l@lists.us.ibm.com] On Behalf Of Jane Curry
Sent: Tuesday, March 29, 2005 1:09 PM
To: NetView mailing list
Subject: [nv-l] Using @limit_discovery in a seedfile


Following on from Paul's excellent Tivoli Support Technical Exchange
presentation on NetView discovery, I asked a question about the use of
@limit_discovery in a netmon seedfile.  Does anyone know definitively
what it does??

My understanding goes like this:
There is a "master" auto-discovery on/off switch that can be applied on
a Unix NetView from Options -> Topology status Polling.  If
auto-discovery is set to off then netmon only discovers EXPLICIT entries
in the seedfile; wildcards and ranges will have no effect.

If auto-discovery is on then wildcards and ranges can be used in the
seedfile.  The IMPLICIT imperative in a seedfile with any wildcard or
range is that anything OUTSIDE the explicit entries, wildcards and
ranges will NOT be discovered.  As Paul pointed out, a wildcard or range
does not actively go out and find anything - it simply means that if the
auto-discovery process finds a node that is included in a wildcard or
range, then it will be permitted into the NetView object database.

If these 2 understandings are correct, why use @limit_discovery?  Either
turn the "master" auto-discovery switch off and simply find explicit
entries in the seedfile, or, if you want to use ranges with the master
switch on, how does @limit_discovery in the seedfile limit discovery
beyond the normal exclusion of objects as described above?

If we get a good thread running on this, perhaps we could move it to the
NetView Tivoli User Group website for more in-depth discussions?

Cheers,
Jane

--
Tivoli Certified Consultant & Instructor
Skills 1st Limited, 2 Cedar Chase, Taplow, Bucks, SL6 0EU, UK
Tel: +44 (0)1628 782565
Copyright (c) 2005 Jane Curry <jane.curry@skills-1st.co.uk>. All rights reserved.


--
Tivoli Certified Consultant & Instructor
Skills 1st Limited, 2 Cedar Chase, Taplow, Bucks, SL6 0EU, UK
Tel: +44 (0)1628 782565
Copyright (c) 2005 Jane Curry <jane.curry@skills-1st.co.uk>.  All rights 
reserved.


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

Archive operated by Skills 1st Ltd

See also: The NetView Web