To: | nv-l@lists.us.ibm.com |
---|---|
Subject: | Re: [nv-l] seed file question.. |
From: | Leslie Clark <lclark@us.ibm.com> |
Date: | Sun, 6 Feb 2005 14:46:01 -0500 |
Delivery-date: | Sun, 06 Feb 2005 19:46:41 +0000 |
Envelope-to: | nv-l-archive@lists.skills-1st.co.uk |
In-reply-to: | <000201c50b8a$e37a1b70$6400a8c0@domain.zen.com> |
Reply-to: | nv-l@lists.us.ibm.com |
Sender: | owner-nv-l@lists.us.ibm.com |
That entry can't do what the comment says it does. People often use a dummy range, like 1.1.1.*, to limit discovery. Having a range in the seedfile tells netmon only to discover nodes it finds out about that fall within that (or another) range, unless it is overridden by a specific node entry. That entry is a specific node entry, since it is an address. However, it is an invalid entry because it has a dot at the end of it. That's why netmon is complaining about it when it loads the seedfile. Cordially, Leslie A. Clark IBM Global Services - Systems Mgmt & Networking Detroit
Hi All.. I recently took over a ntview implementation and found the following entry in the seedfile. 9.29.1.1. #dummy to stop autodiscovery There is an error in netmon.log file sating this invalid.. Is there or should there be a vail ip address in seedfile to tell netmon that this is end of discovery? Thans John |
<Prev in Thread] | Current Thread | [Next in Thread> |
---|---|---|
|
Previous by Date: | RE: [nv-l] Netview does not update the object status, Evans, Bill |
---|---|
Next by Date: | Re: [nv-l] Netview does not update the object status, Alaa Farrag |
Previous by Thread: | [nv-l] seed file question.., John Sobrinho |
Next by Thread: | [nv-l] Jens Rohde/FinanzIT@FinanzIT istaußer Haus. [FinanzIT: Viruscheck], Jens . Rohde |
Indexes: | [Date] [Thread] [Top] [All Lists] |
Archive operated by Skills 1st Ltd
See also: The NetView Web