And this is my primary concern with discovery. There just is no good way to do
discovery at this point. There are problems with all approaches:
1. Very very limited seedfile - i.e. ONLY the nodes you want to manage and
nothing else.
NetView runs GREAT in this arrangement but I work at a firm where people
add/subtract "production" devices with NO notification. Not only don't that
notify me but they don't even know they are being monitored. Routers are one
thing since our group knows about those, but switches, servers, UPS systems,
etc. totally escape our view unless we are told about them.
2. Limited discovery - i.e. Known hosts and some pattern matching by name and
OID
NetView suffers (under 7.1) if I use an OID discovery, the number of hints
added drives OVWDB to 50-75% CPU all the time and begins to consume more and
more memory. (I have a PMR open for this). I find all the new devices people
put on the network automagically.
3. Open Discovery - i.e. Seed file with devices but NO ranges to limit discovery
NetView runs okay, however the problem with workstations looking like DHCP
means that the map can never be kept very pretty and workstations are promoted
to routers periodically. I find all the devices I am worried about and the
database rises to about 3000 managed nodes. I also occasionally get phone calls
from clients wanting to know why I am knocking on their door with SNMP.
I still think the discovery engine is very powerful, but I am not happy with
any of these scenarios. #2 is preferred if support can get me a patch.
-----Original Message-----
From: Leslie Clark [mailto:lclark@us.ibm.com]
Sent: Wednesday, May 15, 2002 7:48 AM
To: nv-l@lists.tivoli.com
Subject: RE: [nv-l] Netview
You can make it think something is a router just by having two ip addresses
resolve to the same name, no snmp required. It will draw the diamond. I've
always assumed it was a more-or-less unintentional by-product of the
code required to support the loadhost function that lets you define
gateways the same way. In Netview for NT, there is a special character
used to indicate dhcp address ranges in the seedfile. This character
was used for another, more useful purpose in Unix, and resolving the two
functions is now problemmatic. My suspicion, no special knowledge.
As I always exclude dhcp address ranges from discovery, I have
managed to avoid this being a problem.
Cordially,
Leslie A. Clark
IBM Global Services - Systems Mgmt & Networking
Detroit
"Allison, Jason
(JALLISON)" To: "'nv-l'"
<nv-l@lists.tivoli.com>
<JALLISON@arinc.c cc:
om> Subject: RE: [nv-l] Netview
05/15/2002 07:39
AM
The plot thickens...
Not that it applies to me, but I would be interested to hear about the
outcome of this issue. It is still difficult for me to believe that NETMON
is somehow thinking those hosts are routers. I wonder what is triggering
it?
Weird...I am sure it is a M$ problem.
Jason Allison
Principal Engineer
ARINC Incorporated
Office: (410) 266-2006
FAX: (410) 573-3026
-----Original Message-----
From: Barr, Scott [mailto:Scott_Barr@csgsystems.com]
Sent: Tuesday, May 14, 2002 3:28 PM
To: nv-l@lists.tivoli.com
Subject: RE: [nv-l] Netview
Thats not entirely true. Windows DHCP machines if discovered will exhibit
this behavior when they do not have forwarding turned on or even have two
interfaces. I have an enhancement request to support discovery of devices
with this behavior pending. This comment is for Unix only by the way.
If the DHCP workstation is managed, and his IP address changes, NETMON will
add an additional interface and treat the device as a router. One interface
will be down, the other will be up. Packet forwarding was turned off in all
cases of this behavior. The PMR I have opened on this has already rolled
off
history, maybe someone in support (ARE YOU LISTENING PAUL!) can find it. We
discovered this because we attempted to run with all over our nodes managed
(and I do mean all, including 1500+ Windows DHCP workstations). We kept
having workstation icons promoted to routers and moved to top level map.
-----Original Message-----
From: James Shanks [mailto:jshanks@us.ibm.com]
Sent: Tuesday, May 14, 2002 6:36 AM
To: nv-l@lists.tivoli.com
Subject: Re: [nv-l] Netview
By definition, any device with at least two interface cards in different
networks, which also has IP forwarding turned on, is a router. That's what
NetView is telling you. You can turn off IP forwarding on that box and it
will no longer be a router, but you will probably have to delete and
rediscover it to get the map re-drawn. Or you can leave it one and
understand that it is NetView which is correct about what is, and what is
not, a router.
James Shanks
Level 3 Support for Tivoli NetView for UNIX and NT
Tivoli Software / IBM Software Group
Fission CC
Lin/Taiwan/IBM@IB To:
nv-l@lists.tivoli.com
MTW cc:
Subject: [nv-l] Netview
05/13/02 12:05 AM
Dear all,
The Netview will recognize some servers (two interface cards) as routers
but actually not. Why ? In what situation that Netview will recognize
something as routers ? for example multiple interface cards ? or any
others? How could I reset them to ordinary servers? Please help,
thanks...
Best Regards,
Fission Lin, 林倩全
I / T Specialist , Tivoli Professional Services,
ITS/SMBU/NSM, IBM Taiwan
206, Sec.1 Keelung Rd, Taipei, Taiwan, R.O.C.
Tel:886-2-2725-8872, Mobile:0935-558622
E-Mail: flin@tw.ibm.com
---------------------------------------------------------------------
To unsubscribe, e-mail: nv-l-unsubscribe@lists.tivoli.com
For additional commands, e-mail: nv-l-help@lists.tivoli.com
*NOTE*
This is not an Offical Tivoli Support forum. If you need immediate
assistance from Tivoli please call the IBM Tivoli Software Group
help line at 1-800-TIVOLI8(848-6548)
---------------------------------------------------------------------
To unsubscribe, e-mail: nv-l-unsubscribe@lists.tivoli.com
For additional commands, e-mail: nv-l-help@lists.tivoli.com
*NOTE*
This is not an Offical Tivoli Support forum. If you need immediate
assistance from Tivoli please call the IBM Tivoli Software Group
help line at 1-800-TIVOLI8(848-6548)
|