To: | nv-l@lists.us.ibm.com |
---|---|
Subject: | Re: [nv-l] Mib2trap error with Symantec-Sesa-Mib |
From: | James Shanks <jshanks@us.ibm.com> |
Date: | Thu, 12 Aug 2004 15:28:19 -0400 |
Delivery-date: | Thu, 12 Aug 2004 20:38:14 +0100 |
Envelope-to: | nv-l-archive@lists.skills-1st.co.uk |
In-reply-to: | <77B193C39550DE4995D34F2C567A2777217152@mddp-msg-004.aeth.aetna.com> |
Reply-to: | nv-l@lists.us.ibm.com |
Sender: | owner-nv-l@lists.us.ibm.com |
mib2trap only works on MIB files, not on the database, so it will have to drop definitions for things which are not fully contained in that one MIB file. If your MIB has other vendor MIBs given in the IMPORTS section, then you can almost expect that. But the proof is in the pudding. Did you get an addtrap script output? Does it work when you execute it and add traps to trapd? Then you can ignore the warning messages. If not, then you need to capture all the messages and look again because at least one of them is not a warning. James Shanks Level 3 Support for Tivoli NetView for UNIX and Windows Tivoli Software / IBM Software Group
Has anyone on this list successfully converted
Symantec Sesa Mib using Netview Mib2trap process. Warning: The mib description doesn't
seem to be consistent. The process proceeds to list the nodes or
trap definitions that were not applied. Thanks in advance.
This e-mail may contain confidential or privileged information.
If you
|
<Prev in Thread] | Current Thread | [Next in Thread> |
---|---|---|
|
Previous by Date: | [nv-l] Mib2trap error with Symantec-Sesa-Mib, Delaire, Patrick |
---|---|
Next by Date: | RE: [nv-l] Mib2trap error with Symantec-Sesa-Mib, Van Order, Drew \(US - Hermitage\) |
Previous by Thread: | [nv-l] Mib2trap error with Symantec-Sesa-Mib, Delaire, Patrick |
Next by Thread: | RE: [nv-l] Mib2trap error with Symantec-Sesa-Mib, Van Order, Drew \(US - Hermitage\) |
Indexes: | [Date] [Thread] [Top] [All Lists] |
Archive operated by Skills 1st Ltd
See also: The NetView Web