| To: | nv-l@lists.us.ibm.com |
|---|---|
| Subject: | RE: [nv-l] How to Deal BadOID's-FINALLY |
| From: | James Shanks <jshanks@us.ibm.com> |
| Date: | Tue, 7 Jun 2005 09:07:46 -0400 |
| Delivery-date: | Tue, 07 Jun 2005 14:07:30 +0100 |
| Envelope-to: | nv-l-archive@lists.skills-1st.co.uk |
| In-reply-to: | <OFC34E8997.881D2792-ON45257019.00379C84-45257019.00379C8C@s-iii.com> |
| Reply-to: | nv-l@lists.us.ibm.com |
| Sender: | owner-nv-l@lists.us.ibm.com |
Well if you add the Enterasys sysOId to oid_to_type and oid_to_sym, then newly discovered Enterasys devices will not be part of the BadOID smartset, but old ones will remain until you delete and rediscover them. I'm glad the delete function worked for you. 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] ovtopofix -m -> nonstandard objects, Paul |
|---|---|
| Next by Date: | RE: [nv-l] How to discover VPN & Remote Router?, James Shanks |
| Previous by Thread: | RE: [nv-l] How to Deal BadOID's-FINALLY, usman . taokeer |
| Next by Thread: | [nv-l] ISDN interface deleted /added problem, Nicolai Kildal |
| Indexes: | [Date] [Thread] [Top] [All Lists] |
Archive operated by Skills 1st Ltd
See also: The NetView Web