Usman,
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.
HTH,
Don Davis.
From:
usman.taokeer@s-iii.com [mailto:usman.taokeer@s-iii.com]
Sent: Friday, June 03, 2005 5:09
AM
To: nv-l@lists.us.ibm.com
Subject: Re: [nv-l] How to Deal
BadOID's
James,
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??
Regards,
~Usman
|
James Shanks
<jshanks@us.ibm.com>
Sent
by: owner-nv-l@lists.us.ibm.com
02-06-05 06:47 PM
|
Please
respond to
nv-l@lists.us.ibm.com
|
|
|
To
|
nv-l@lists.us.ibm.com
|
|
cc
|
|
|
Subject
|
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
product.
James Shanks
Level 3 Support for Tivoli NetView for UNIX
and Windows
Tivoli
Software / IBM Software Group
usman.taokeer@s-i
ii.com
Sent by:
To
owner-nv-l@lists.
nv-l@lists.us.ibm.com
us.ibm.com
cc
Subject
06/02/2005 05:55 Re: [nv-l] How to Deal
BadOID's
AM
Please
respond to
nv-l
Farrag,
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.?
Regards,
~Usman
"Alaa Farrag"
<alaahelmy1@hotmail.com>
Sent by: owner-nv-l@lists.us.ibm.com
To
<nv-l@lists.us.ibm.com
01-06-05 03:53 PM
>
cc
Please
respond to
Subject
nv-l@lists.us.ibm.com Re:
[nv-l] How to Deal
BadOID's
Hi,
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
Hi,
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!
Regards,
~Usman!