Hallo Leslie,
as I also had this problem, I would like to turn on bad-oid logging. Is
there a special tracemask for netmon for this purpose?
Thanks
Eva
-------------------------------------------------------------------------------
Eva-Maria Fettig e-mail: efettig@haitec.de
Haitec AG Tel. +49 89 35631 3438
Alois-Wolfmüller-Str. 8 Fax +49 89 35631 3300
80939 München Mobil +49 172 8592939
--------------------------------------------------------------------------------
"Leslie Clark/Southfield/IBM" <lclark@us.ibm.com>@tkg.com am 10.10.2000
23:28:55
Bitte antworten an IBM NetView Discussion <nv-l@tkg.com>
Gesendet von: owner-nv-l@tkg.com
An: IBM NetView Discussion <nv-l@tkg.com>
Kopie:
Thema: Re: [NV-L] Nodes with Bad OIDs
Think of that Smartset as your 'To Do' list to complete Netview's
awareness of all device types in your network. They are not bad,
just unknown.
For each type of device in there (each unique snmp sysObjectID),
you need to manually update the \usr\ovV\conf\oid_to_type file and
perhaps also the vendor list in \usr\ov\fields\c\ovw_fields, and the agents
list in \usr\ov\fields\c\snmp_fields.
What to put in? Turn on bad-oid logging for a while, and netmon will write
it down for you in \usr\ov\log\badoids.log or something like that. It will
tell you the snmp sysObjecId (like 1.3.6.1.4.1.9.1.185, etc), and the
snmp sysDescription. From this you decide on the vendor and the
agent. Check to see if there is something appropriate in the fields files.
If not, add them manually. If you change the fields files, run 'ovw_fields'
to get them re-read. Then edi the oid_to_type file. Read the information
at the top of the file. Add one entry for each unique oid, no wildcarding.
Include the vendor and agent EXACTLY as written in the fields files. For
network devices, include the flag (G for router, H for hub or switch, B for
bridge). G causes devices to be drawn at the top level of the map. H or B
causes devices to be drawn at the Network level of the map (with the
Segment). No flag causes it to be drawn at the Segment level, which is
where they are now. You can 'promote' them to the higher level with these
flags.
Then...close and open the map to get all of this information incorporate.
Stop netmon. Delete the devices in that Smartset from ALL submaps.
restart netmon, and they will all be rediscovered with the new information,
and should NOT reappear in the Badoids Smartset, if you did it all
correctly. And it is a badge of honor to have an empty Badoids Smartset!
Somebody should file this.
Cordially,
Leslie A. Clark
IBM Global Services - Systems Mgmt & Networking
Detroit
"LO GUIDICE, Yannick" <Yannick.LOGUIDICE@mane.com>@tkg.com on 10/10/2000
04:06:57 AM
Please respond to IBM NetView Discussion <nv-l@tkg.com>
Sent by: owner-nv-l@tkg.com
To: "'nv-l@tkg.com'" <nv-l@tkg.com>
cc:
Subject: [NV-L] Nodes with Bad OIDs
Hi all,
I work with Tivoli Netview for NT 6.0.1 Enterprise Edition with MS SQL 7.
I've got problems with nodes with Bad OIDs. They appear in the Bad OIDs
SmartSets and I don't know how to deal with them.
Is there some kind of maintenance operation recquired on the database ?
I think it is an easy question for you guys, so I can't wait to read your
answers.
Regards,
--
Societe V. MANE FILS
Yannick Lo Guidice
Poste 1366
Technicien reseau
yannick.loguidice@mane.com
+33 493 097 000
--
**************************************************************************
CONFIDENTIALITY:
This e-mail and any files transmitted with it are confidential and intended
solely for the use of the individual or entity to whom they are addressed.
If you are not the intended recipient or the person responsible for
delivering the e-mail to the intended recipient, you are advised that you
have received this e-mail in error and that any use, dissemination,
forwarding, printing or copying of this e-mail is strictly prohibited. If
you have received this e-mail in error please notify: postmaster@mane.com
**************************************************************************
_________________________________________________________________________
NV-L List information and Archives: http://www.tkg.com/nv-l
_________________________________________________________________________
NV-L List information and Archives: http://www.tkg.com/nv-l
|