[Top] [All Lists]

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

To: nv-l@lists.us.ibm.com
Subject: Re: [nv-l] How to Deal BadOID's
From: James Shanks <jshanks@us.ibm.com>
Date: Thu, 2 Jun 2005 09:47:39 -0400
Delivery-date: Thu, 02 Jun 2005 14:48:07 +0100
Envelope-to: nv-l-archive@lists.skills-1st.co.uk
In-reply-to: <OFA82A5621.26CB8CDE-ON45257014.003666BC-45257014.003685DB@s-iii.com>
Reply-to: nv-l@lists.us.ibm.com
Sender: owner-nv-l@lists.us.ibm.com
oid_to_type, and it's sister, oid_to_symbol,  let NetView know what kind of
a device it is dealing with.  If you actually go look at these files it
will be obvious how they are used, because there extensive comments in the
front of the files which explain the parameters in them.  There are OIDs
from many vendors and their various boxes.  But there will always be some
that are not there.

That's where the BadOID smartset comes in.  On Windows, any device whose
OID is not in the oid_to_type gets put in this smartset by default, in
order to let you know that NetView does not know what kind of a device
(router/gateway, switch, bridge, etc) it is.

If your devices return an OID which is not in oid_to_type, then NetView
will just treat them as a simple workstation, and by oid_to_symbol, it will
represent them as generic boxes on the map.   If that is appropriate, or
you don't care, then you need do nothing with these files.     If however,
you have something which needs special handling or deserves a better
symbol, then you need to update those files accordingly.

All this is explaining in the NetView for Windows books that ship with the

James Shanks
Level 3 Support  for Tivoli NetView for UNIX and Windows
Tivoli Software / IBM Software Group

             Sent by:                                                   To 
             owner-nv-l@lists.         nv-l@lists.us.ibm.com               
             us.ibm.com                                                 cc 
             06/02/2005 05:55          Re: [nv-l] How to Deal BadOID's     
             Please respond to                                             


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                                     Subject 
           nv-l@lists.us.ibm.com                    Re: [nv-l] How to Deal 


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
- 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