[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: Thu, 2 Jun 2005 14:55:35 +0500
Delivery-date: Thu, 02 Jun 2005 10:54:20 +0100
Envelope-to: nv-l-archive@lists.skills-1st.co.uk
In-reply-to: <BAY19-DAV1969EBCFCE5EAC608CDA1986050@phx.gbl>
Reply-to: nv-l@lists.us.ibm.com
Sender: owner-nv-l@lists.us.ibm.com


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