To: | nv-l@lists.us.ibm.com |
---|---|
Subject: | Re: [nv-l] Wildcards in netmon.seed |
From: | Leslie Clark <lclark@us.ibm.com> |
Date: | Fri, 5 Dec 2003 01:00:16 -0500 |
Delivery-date: | Fri, 05 Dec 2003 06:10:47 +0000 |
Envelope-to: | nv-l-archive@lists.skills-1st.co.uk |
Reply-to: | nv-l@lists.us.ibm.com |
Sender: | owner-nv-l@lists.us.ibm.com |
You can, however, use name wildcards in the seedfile in the same way that you use IP address ranges. It does not force discovery, only allows it. And as Chris figured out, this is different than the location.conf file, which places only nodes specified by name or address. Cordially, Leslie A. Clark IBM Global Services - Systems Mgmt & Networking Detroit
Chris, This is correct, NetView will not actively try to discover devices in a range or wildcard entry in the seedfile. It will passively discover them when it finds them in the ARP cache of another device. What I generally suggest is that if you have a subnet that you would like to enter a range for, also enter the specific IP of the/a router on that subnet. That should make the discovery happen as you wish. Paul On Thursday 04 December 2003 13:35, you wrote: > According to the actual text found int he netmon.seed file for UNIX ver > 7.1.3 It shows the following > > Seed entries are single entries (no wildcards or ranges). > # IP addresses or hostnames can be specified for netmon to use as > starting > > # points for discovery when netmon is started. Netmon will always > attempt > > # to discover these nodes. > # > # Seed nodes must be reachable and should support SNMP. Routers > # make good candidates. If the node's name cannot be resolved by the > # name server, then the seed node is considered invalid and will be > # ignored. If an IP address cannot be resolved by the name server, a > # seed hint is still added and a warning is logged in the > # \usr\OV\log\nv.log file. > > > Is this actually true. We cannot use WIldcards in Discovery Process? > > ________________________________________________________________________ > This email has been scanned for all viruses by the MessageLabs SkyScan > service._______________________________________________________________ > > Note: Please update your email address for this user to reflect the > new MeadWestvaco Corporation. MeadWestvaco employee email addresses > are in the format of user@MeadWestvaco.com > > This electronic message contains information from MeadWestvaco > Corporation or subsidiary companies, which may be confidential, > privileged or otherwise protected from disclosure. The > information is intended to be used solely by the recipient(s) > named. If you are not an intended recipient, be aware that > any review, disclosure, copying, distribution or use of this > transmission or its contents is prohibited. If you have > received this transmission in error, please notify MeadWestvaco > immediately at postmaster@MeadWestvaco.com. > _______________________________________________________________________ |
<Prev in Thread] | Current Thread | [Next in Thread> |
---|---|---|
|
Previous by Date: | [nv-l] Setting netmon polling time intervals, John F |
---|---|
Next by Date: | RE: [nv-l] Seed file entries can't be seen via Network Monitor Se ed File Editor, Leslie Clark |
Previous by Thread: | Re: [nv-l] Wildcards in netmon.seed, Christopher J Petrina |
Next by Thread: | RE: [nv-l] Seed file entries can't be seen via Network Monitor Se ed File Editor, Evans, Bill |
Indexes: | [Date] [Thread] [Top] [All Lists] |
Archive operated by Skills 1st Ltd
See also: The NetView Web