nv-l
[Top] [All Lists]

[nv-l] BadOID for new enterprise device

To: nv-l@lists.tivoli.com
Subject: [nv-l] BadOID for new enterprise device
From: "Mrs Bigglesteeth" <mrsbigglesteeth@hotmail.com>
Date: Tue, 03 Aug 2004 21:35:12 +0000
Delivery-date: Tue, 03 Aug 2004 22:50:46 +0100
Envelope-to: nv-l-archive@lists.skills-1st.co.uk
Reply-to: nv-l@lists.us.ibm.com
Sender: owner-nv-l@lists.us.ibm.com
Hi,

My company has a developed a new SNMP agent that is discovered by NetView and placed in the expected network maps. However, the devices are also displayed in the BadOID smartset.

I searched the forum for situations like this and realized that we must modify some files so that NetView recognizes our sysObjectID. I've modified the oid_to_sym, oid_to_type, and snmp_fields files to do this. I then deleted all the associated symbols, cleared the database and then performed discovery again. Now our devices are no longer in the BadOID smartset but in the smartset I expect it to belong to. Everything worked fine.


My questions are as follows:
1. If one upgrades NetView (say from 7.1.3 to 7.1.4) will the modified files mentioned above be replaced and therefore, need to be modified again?

2. Is it necessary to manually remove symbols from the BadOID smartset and perform another discovery, or will the symbol be removed and updated on the next scheduled discovery?

3. Is there a way to get our Enterprise OID added to NetView's files so that future releases of the product will recognize our devices and assign the appropriate symbol to it? I imagine we have to contact Tivoli for this but I don't know what the procedure would be to do this.

Thank you very much for your assistance.

Regards,

_________________________________________________________________
MSN Toolbar provides one-click access to Hotmail from any Web page ? FREE download! http://toolbar.msn.click-url.com/go/onm00200413ave/direct/01/


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

Archive operated by Skills 1st Ltd

See also: The NetView Web