You may want to
look at migrating to version 7.1.3 soon as version 6.x is no longer a
supported release.
Gareth Holl
Staff Software
Engineer
gholl AT us.ibm DOT com
IBM Software Group - Tivoli
Brand
Research Triangle Park, North Carolina.
|
| "Lemire, Mark"
<mlemire AT jhancock DOT com>
05/20/2003 03:42 PM
|
To:
"'nv-l AT lists.tivoli DOT com'"
<nv-l AT lists.tivoli DOT com>
cc:
"Kenney, Jack" <jkenney AT jhancock DOT com>, "Hughes, Tom P."
<thughes AT jhancock DOT com>
Subject:
[nv-l] Netview SNMP/Discovery Issue
|
We have
encountered a situation where Netview is auto-deleting objects from its
database almost immediately after discovering them.
This only appears to happen with Unix servers
running Solaris 2.8; it's not a problem with our NT servers or with older
versions of Solaris.
Here's our configuration:
(1) We're running Netview v6.0 on Solaris
2.6.
(2) Netmon is configured to use a seedfile that contains a
statement: !@oid 0 to block auto-discovery of devices that are not running
SNMP -- mainly workstations.
(3) Netview SNMP configuration does not have any
specific or wildcard overrides in terms of this issue. It uses a default
community string that is configured on all routers and switches, which *do*
get autodiscovered as expected.
(4) NT servers run an SNMP service but do not use
the default community string. These devices are not auto-discovered.
To manage these devices, we add their IP address to the seedfile once
they are active on the network. This works OK - once discovered, they
stay managed.
(5)Unix servers running older versions of Solaris
(i.e. 2.6) work the same way as NT; these servers do not run an SNMP daemon
normally.
The problem is with Unix Servers running 2.8.
These do not use the default community string defined to Netview.
When we add the IP address to the seedfile, they do not get discovered.
When we explicitly add them in the read/write map, they initially get
discovered but get auto-deleted 5 minutes later, apparently as part of the
next polling cycle. The only way to successfully get Netview to manage
these servers (using the non-default community string), is to add a specific
override in the Netview SNMP configuration. We could also get around the
problem by configuring netmon with the "-h" alternate community string option,
but have rejected this solution since it would need to be left in place most
of the time and adds to Netview's overhead.
We would expect this "auto-delete feature" of
Netview to at least act in a consistent manner, affecting both NT and Unix
servers alike.
Before opening a problem with support, we first
just wanted to see if anyone out there has seen this or can offer an
explanation.
Thanks!!
Mark Lemire
Sr. Consultant
John Hancock
Financial Services ---------------------------------------------------------------------
To
unsubscribe, e-mail: nv-l-unsubscribe AT lists.tivoli DOT com
For additional
commands, e-mail: nv-l-help AT lists.tivoli DOT 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)
