This is my initial
install. I have tried using a number of wildcard solutions including ranges
(10.60.120-132 or 10.60.120.* or 10.60.120.1-255… etc).
I have rediscovered
the network each time I put a new seed file in place. The only time it
discovers new devices is when they are set in the seed file without any
wildcards.
I am only testing a
section of our network until I get things put together properly. So a
discovery is not that painful.
I have tried both vi
and the gui.
I am
stumped
-----Original
Message-----
From: Michael
Webb [mailto:mlwebb@us.ibm.com]
Sent: Thursday, January 29, 2004 5:22
AM
To:
nv-l@lists.us.ibm.com
Subject: RE: [nv-l] netmon.seed
file
Anything
is possible, including the fact that some traffic may be blocked at certain
routers in your network. However, have you ever been able to use NetView to
discover your network? I think you did say that if you put individuals entries
in the seed file that you can discover your network. So that may put to rest
any idea of the router causing the problem.
However, what about using ranges?
For example, did you have a previous release of NetView at one time that did
discover the network with the seed file that you have (using ranges)? Or,
using your current version of NetView, have you used a "different" seed file
with ranges that did discover the network?
Here is something else to
consider. How are you creating and updating your seed file? Are you using an
ASCII editor or are you using the NetView GUI seed file editor? I have seen
unexplained behavior when I do not use the NetView GUI editor to actually
"create" the seed file. It could be because I go back and forth between seed
files in my test environment.
Nevertheless, if you are not using the NetView GUI
editor to update your seed file, then use the editor to open the seed file,
make one update, and then save it. Clear databases and rediscover. This has
helped me a couple of times here in the lab.
Michael Webb, IBM Tivoli
Q1CA
Distributed NetView / ITSA SVT
Email:
mlwebb@us.ibm.com
Ext: (919) 224-1410, T/L: 687-1410
"Kevin Campbell"
<kcampbell@tgen.org>
|
|
"Kevin Campbell"
<kcampbell@tgen.org>
Sent by:
owner-nv-l@lists.us.ibm.com
01/28/2004 06:03 PM
Please respond to
nv-l |
To:
<nv-l@lists.us.ibm.com>
cc:
Subject: RE: [nv-l] netmon.seed
file
|
I have tried this and
numerous other wildcard entries. Nothing seems to work. Could the network
group be blocking any of this traffic at the routers?
What is the difference in the traffic
from discovery to specific IPs?
Thanks
-----Original
Message-----
From: Michael
Webb [mailto:mlwebb@us.ibm.com]
Sent: Wednesday, January 28,
2004 3:33 PM
To:
nv-l@lists.us.ibm.com
Subject: RE: [nv-l] netmon.seed
file
Try adding one specific IP address
per subnet as an initial seed entry such as:
10.60.180.x
where x
is a valid IP address (like a router)
If that does not help to get that
subnet discovered, then try a different syntax for your range,
like
10.60.180.1-255
instead of
10.60.180.*.
Regards,
Michael Webb, IBM Tivoli
Q1CA Distributed
NetView / ITSA SVT
Email: mlwebb@us.ibm.com
Ext: (919) 224-1410, T/L:
687-1410
"Kevin Campbell"
<kcampbell@tgen.org>
|
|
"Kevin Campbell"
<kcampbell@tgen.org>
Sent by:
owner-nv-l@lists.us.ibm.com
01/28/2004 05:24 PM
Please respond to
nv-l |
To:
<nv-l@lists.us.ibm.com>
cc:
Subject: RE: [nv-l] netmon.seed
file
|
Yes. I
have also added one and more of the routers into the seed file as well. Still
no luck
AIX 5.1
Netview 7.1.3 (fixpack 1 and 2)
-----Original
Message-----
From: Barr,
Scott [mailto:Scott_Barr@csgsystems.com]
Sent: Wednesday, January 28,
2004 2:48 PM
To:
nv-l@lists.us.ibm.com
Subject: RE: [nv-l] netmon.seed
file
Have you tried
pinging a router within one of those subnets while discovery is running?
-----Original
Message-----
From:
owner-nv-l@lists.us.ibm.com [mailto:owner-nv-l@lists.us.ibm.com]On Behalf Of Kevin Campbell
Sent: Wednesday, January 28, 2004
3:31 PM
To:
nv-l@lists.us.ibm.com
Subject: [nv-l] netmon.seed
file
I have tried a number of
configurations but can not get it to discover devices the way I want them to.
I have a number of subnets that I manage, lets say (10.60.180.*-10.60.190.*
and 10.60.120.*-10.60.132.*). I would lick to have netmon auto discover
anything on these subnets. The only way I can get the devices to show up is to
add each device into the seed file. How can I get the devices to be auto
discovered. I have tried what the config docs say making my netmon.seed file
look this:
10.60.180-190.*
10.60.120-132.*
But the only
thing that gets discovered is the Netview server and the default route. I have
tried a number of others for example:
10.60.180.*
10.60.181.*
10.60.182.*
…and so
on
But nothing other than
specific IPs seem to be working
Any advice would be
great
Thanks
KevinC