[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: usman.taokeer@s-iii.com
Date: Fri, 3 Jun 2005 20:46:23 +0500
Cc: "'nv-l@lists.us.ibm.com'" <nv-l@lists.us.ibm.com>, owner-nv-l@lists.us.ibm.com
Delivery-date: Fri, 03 Jun 2005 16:44:47 +0100
Envelope-to: nv-l-archive@lists.skills-1st.co.uk
In-reply-to: <200506031333.j53DXoht017926@e3.ny.us.ibm.com>
Reply-to: nv-l@lists.us.ibm.com
Sender: owner-nv-l@lists.us.ibm.com

Followed the steps, it again puts it there(BadOID smartset) :(



"Davis, Donald" <donald.davis@firstcitizens.com>
Sent by: owner-nv-l@lists.us.ibm.com

03-06-05 06:33 PM
Please respond to

"'nv-l@lists.us.ibm.com'" <nv-l@lists.us.ibm.com>
"'usman.taokeer@s-iii.com'" <usman.taokeer@s-iii.com>
RE: [nv-l] How to Deal BadOID's

I'll answer this one and give James a break.
NetView requires an exact match for the OID of a device, otherwise, in the Windows version, it is assigned to the BadOID smartest.
If NetView can determine via SNMP, that IPforwarding is turned on, it will draw a router symbol (diamond with 4 headed arrow), regardless if the OID matches a pre-defined record in oid_to_sym or not.
To get your Cisco3745 out of thr BadOID smartest add a record containing the exact OID of the device to oid_to_sym.
Adding it to oid_to_type is optional, since NetView already knows it is a router via SNMP, but do it anyway.
Don Davis.

From: usman.taokeer@s-iii.com [mailto:usman.taokeer@s-iii.com]
Friday, June 03, 2005 5:09 AM
Re: [nv-l] How to Deal BadOID's



You see, the NetView recongnizes the devices and also shows the appropriate symbol for e.g we have Cisco3745 Router and the symbol it shows is for a Router, but again it puts it in the BadOIDs smartset??? Why is it so when it is detecting the device with respect to its behaviour and then again puts it in the BadOID smartset, i am a bit confused??



James Shanks <jshanks@us.ibm.com>
Sent by: owner-nv-l@lists.us.ibm.com

02-06-05 06:47 PM

Please respond to

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



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!



This electronic mail and any files transmitted with it are confidential and are intended solely for the use of individual or entity to whom they are addressed. If you are not the intended recipient or the person responsible for delivering the electronic mail to the intended recipient, be advised that you have received this electronic mail in error and that any use, dissemination, forwarding, printing, or copying of this electronic mail is strictly prohibited. If you have received this electronic mail in error, please immediately notify the sender by return mail.

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

Archive operated by Skills 1st Ltd

See also: The NetView Web