| To: | nv-l@lists.us.ibm.com |
|---|---|
| Subject: | RE: [nv-l] How to Deal BadOID's |
| From: | James Shanks <jshanks@us.ibm.com> |
| Date: | Fri, 3 Jun 2005 11:58:30 -0400 |
| Delivery-date: | Fri, 03 Jun 2005 16:59:12 +0100 |
| Envelope-to: | nv-l-archive@lists.skills-1st.co.uk |
| In-reply-to: | <OFFF2D7008.4BFF6B29-ON45257015.00569DAD-45257015.0056A206@s-iii.com> |
| Reply-to: | nv-l@lists.us.ibm.com |
| Sender: | owner-nv-l@lists.us.ibm.com |
Show us the entry you put in oid_to_type, and the one in oid_to_sym, and
the results of doing this
snmpget system.sysObjectID.0 <target_box>
from a command window.
If the OIDs match, then it should be removed from the BadOID smartset
after you
1. delete the objects from all submaps (select it and do Edit --> All
submaps --> Cut)
2. ovstop netmon
3. ovtopofix (in a command window)
4. ovstart netmon
Worked for me on NetView for Windows with a United Linux OID this morning
James Shanks
Level 3 Support for Tivoli NetView for UNIX and Windows
Tivoli Software / IBM Software Group
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | RE: [nv-l] How to Deal BadOID's, usman . taokeer |
|---|---|
| Next by Date: | Re: [nv-l] FW: Jetty behavior, Francois Le Hir |
| Previous by Thread: | RE: [nv-l] How to Deal BadOID's, usman . taokeer |
| Next by Thread: | RE: [nv-l] How to Deal BadOID's, usman . taokeer |
| Indexes: | [Date] [Thread] [Top] [All Lists] |
Archive operated by Skills 1st Ltd
See also: The NetView Web