On Netview for NT, this is done for you. It does this by (wierd) storing a
bogus oid and making a smartset based on that. On Unix, I always make
one myself based on  nodes that are snmp-supported but for which the
vendor field is not set. This will also catch nodes for which some
third-party app updated the oid_to_type file but which did not update the
vendors and agents lists, or which was not precise in matching references
to the vendors and agents list. (This happens with Cisco devices at
certain levels of products, as the vendor is sometimes listed with a lower
case c and sometimes with an upper case c.)

This smartset was added in NT as an aid, but on NT they do not have the
administrative function to update the oid_to_type file as we do on Unix.
So it has to be done manually. On Unix, after verifying your vendor and
agent lists, you can use the administrative functions to add oids and
select
from vendor, agent, and flags lists.

Cordially,

Leslie A. Clark
IBM Global Services - Systems Mgmt & Networking
Detroit

"Ray Westphal" <rwestphal AT erac DOT com>@tkg.com on 10/11/2000 09:28:38 AM

Please respond to IBM NetView Discussion <nv-l AT tkg DOT com>

Sent by:  owner-nv-l AT tkg DOT com


To:   "NV List (E-mail)" <nv-l AT tkg DOT com>
cc:
Subject:  [NV-L] Nodes with Bad OIDs



I'm curious. How did you create a SmartSet Collection of devices with Bad
OIDs? Or is a SmartSet created by default at installation?

Thanks

Ray Westphal
NMSA Systems Administrator
Phone: (314) 512-3867
Fax: (314) 512-5867
Pager: (314) 509-0036
mailto:rwestphal AT erac DOT com


_________________________________________________________________________
NV-L List information and Archives: http://www.tkg.com/nv-l