[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: "Alaa Farrag" <alaahelmy1@hotmail.com>
Date: Wed, 1 Jun 2005 13:53:14 +0300
Delivery-date: Wed, 01 Jun 2005 11:54:36 +0100
Envelope-to: nv-l-archive@lists.skills-1st.co.uk
Organization: IBM
References: <OFAD376BF4.695ED577-ON45257012.00240600-45257012.002426A8@s-iii.com>
Reply-to: nv-l@lists.us.ibm.com
Sender: owner-nv-l@lists.us.ibm.com
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 -----
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