This was discussed in detail in the last couple of months, so you might
want to review that in the archives. But the upshot, I think, was that if
the
alternate community names file is present in /usr/OV/conf, Netview will
assume that 'public' is in it, and try to use it. If it works, it adds an
entry to
the ovsnmp configuration. I believe some users affirmed that you could
prevent this by removing the file, if you are attempting to prevent
discovery
of nodes by forcing failure of snmp access. The alternate community
names file is a new feature in Netview V6. I, for one, love it.
Cordially,
Leslie A. Clark
IBM Global Services - Systems Mgmt & Networking
Detroit
Sergio Cardona <scardona@visiontech.com.co>@tkg.com on 12/12/2000 02:54:29
PM
Please respond to IBM NetView Discussion <nv-l@tkg.com>
Sent by: owner-nv-l@tkg.com
To: IBM NetView Discussion <nv-l@tkg.com>
cc:
Subject: [NV-L] SNMP Configuration feature
Hi All:
Our client has, netview 6.0 & AIX 4.3.2.
The NetView is making something that I never have seen
before, when the NV discover a new box that is SNMP
configured with the public community, NV is feeding
the snmp configuration with the Ip name or Ip adress of
this node.
If I deleted the node entry in the SNMP configuration,
the entry reappear.
no one comunity is defined in NV as public even global
default.
Is this behavior normal ?
There is any way to deactite this feature ?
Thanks in advance,
Sergio.
-----------------------------------------------------
El contenido de este correo es completa responsabilidad del Autor.
VisionTech Colombia
_________________________________________________________________________
NV-L List information and Archives: http://www.tkg.com/nv-l
|