Sorry about the delay in responding. We're in Houston and our ISP was
flooded out on Saturday and didn't get power restored until last night.
THANK YOU!
When I first looked at the SmartSets (shortly after discovery started)
there was not BadOIDs SmartSet. But looking at it now, it's there. So
now I can update the lists.
-----Original Message-----
From: Leslie Clark [mailto:lclark@us.ibm.com]
Sent: Monday, June 11, 2001 9:15 PM
To: IBM NetView Discussion
Subject: Re: [NV-L] problem logging bad oids
Art, I have not noticed that one. No responses here, so you probably
should report it to Support.
On NT, Netview replaces the 'bad' (well, unrecognized) oid with a fake
number to give it something to base the SmartSet on. I take it you have
the SmartSet? The Smartset is a to-do list for you. The value of the log
is that it helps gather the information you need to acquaint Netview
with these oids, mostly the oid itself, and the sysDescription, from
which you can deduce the vendor and make up a nice Agent value. If it
has been broken, by all means report it and then get on with the job by
collecting the information the way we do it on Unix:
Use the information to update the
-- the vendor list in \usr\OV\fields\C\ovw_fields,
-- the agent list in \usr\OV\fields\C\snmp_fields,
-- run 'ovw_fields' (to let Netview know about your changes),
-- then update the entries in the \usr\OV\conf\oid_to_type file.
(Read the header info for syntax and flags available)
Then delete and rediscover the badoids nodes. When they come back they
will have good oids, vendors, agents, and the hubs and routers will have
the default hub and router pictures. For other device types you will
need to also update the \usr\OV\conf\C\oid_to_sym file to give the
appropriate symbols.
Cordially,
Leslie A. Clark
IBM Global Services - Systems Mgmt & Networking
Detroit
"Art Beane" <abeane@geonetservices.com>@tkg.com on 06/08/2001 11:06:14
AM
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] problem logging bad oids
I've just installed NV for NT 6.02 (first-time user) and can't seem to
get netmon to log bad oids. Everything in the network has been
discovered, but many of the devices have the "unknown" icon and have
"hasBadOID" checked on the Other General Attributes page. When we check
the box in Server Setup for netmon to log bad OIDs, we get an error
message:
can't read "netmonCheckMaxAddrForHscp": no such variable
I couldn't find any references in the documentation. Any ideas?
Thanks
Art Beane
GeoNet Services, Inc.
6575 West Loop South, Suite 180
Bellaire, TX 77401
________________________________________________________________________
_
NV-L List information and Archives: http://www.tkg.com/nv-l
________________________________________________________________________
|