[Top] [All Lists]

RE: [nv-l] How to Deal BadOID's

To: "'nv-l@lists.us.ibm.com'" <nv-l@lists.us.ibm.com>
Subject: RE: [nv-l] How to Deal BadOID's
From: "Evans, Bill" <Bill.Evans@hq.doe.gov>
Date: Thu, 2 Jun 2005 09:59:05 -0400
Delivery-date: Thu, 02 Jun 2005 15:05:08 +0100
Envelope-to: nv-l-archive@lists.skills-1st.co.uk
Reply-to: nv-l@lists.us.ibm.com
Sender: owner-nv-l@lists.us.ibm.com
I'm assuming you're using NetView for Windows since the BadOID SmartSet is unique to the Windows version of NetView.  It helps if you preface your notes to the list with the operating system and version of the product you use. 
That said, the naming of the SmartSet as BAD is not well done but the true name "UnrecognizedOIDs" is a bit too long.  The SmartSet contains the devices which are not in the oid_to_type file and somewhere in the literature it recommends what Farrag recommended; add the OIDs for those devices to the oid_to_type file.  That was one of the items in the NetView for Windows for Administrators class back when I was teaching it. 
Other unfortunate things about the Windows version of the product are the missing features (Rule Set Editor is one) and the relatively sparse documents.  For a lot of the detail on administering the product you have to use the Unix publications. 
When you did your "Clean Installation" you put in the basic product package which includes OIDs for the most common switches and routers found in the US.  I might also add that many of the default entries are for obsolete switches and routers because the developers can never seem to keep up with the variety of new equipment constantly being released by manufacturers large and small around the world.  At my NetView for Unix installation we added about twenty entries for Cisco switches and IBM SAN devices.    
The easy part is adding the new OIDs since they are easily constructed from the data in the system branch of the MIB tree and the information in the header of the oid_to_type file.  Don't forget the companion file /usr/OV/conf/C/oid_to_sym and the device registration files if you want the icons to resolve to other than defaults. 

Bill Evans
Tivoli NetView Support for DOE

-----Original Message-----
From: owner-nv-l@lists.us.ibm.com [mailto:owner-nv-l@lists.us.ibm.com] On Behalf Of usman.taokeer@s-iii.com
Sent: Thursday, June 02, 2005 5:56 AM
To: nv-l@lists.us.ibm.com
Subject: Re: [nv-l] How to Deal BadOID's


But why do i need to do that, i havent made any changes, i did a clean installation and it puts the devices in that SmartSet. Why do i need to change the oid_to_Type file.?


"Alaa Farrag" <alaahelmy1@hotmail.com>
Sent by: owner-nv-l@lists.us.ibm.com

01-06-05 03:53 PM
Please respond to

Re: [nv-l] How to Deal BadOID's

Read about editing the oid_to_type file in the Netview Unix administrator's guide page 177.
To know the OID of a bad OID device querey the SNMP system variables
snmpwalk -c community_name hostname system

to reflect the changes you made to the oid_to_type you should do the following:
- restart the netmon daemon.
- issue a demand poll over the devices with bad OIDs.

Best regards,
Alaa Farrag
----- Original Message -----
From: usman.taokeer@s-iii.com
To: nv-l@lists.us.ibm.com
Sent: Tuesday, May 31, 2005 9:34 AM
Subject: [nv-l] How to Deal BadOID's


How can we deal with the BadOIDs smartsets, it has almost all the Routers and switches listed in there, what is wrong how can i fix it??

Help any one!



<Prev in Thread] Current Thread [Next in Thread>

Archive operated by Skills 1st Ltd

See also: The NetView Web