Thanks for the info Colin.
I wasn't very clear - I have already imported the pET mib that I managed to
find, and then ran mib2trap and executed the .bat file afterwords. I can
see the traps in the trapd.conf file, but the actual traps that the HW is
generating don't match up.
I guess my question would be - does anyone know if these pET mibs are HW
specific? It seems that when I imported MIBs for IBM Director there where
pET mibs there - but nothing that matched the SUN HW..
Thanks again.
owner-nv-l@lists.us.ibm.com wrote on 10/03/2006 09:35:48 AM:
> Brett,
>
> You are going to have to create traps from the mibs that are loaded
> (NetView doesn't do it itself - unfortunately)
>
> The command is mib2trap - check out the man page. It creates traps from
> the mib file
>
> Good luck with this - I have had very little success as most mibs are
> incomplete (they rely on other mibs for definitions) and hence will not
> create all the required traps (unless you stack the mib files) - but it
> will get you started.
>
> Regs
>
> Colin M.
>
> -----Original Message-----
> From: owner-nv-l@lists.us.ibm.com [mailto:owner-nv-l@lists.us.ibm.com]
> On Behalf Of BGillett@symcor.com
> Sent: 10 March 2006 14:23
> To: nv-l@lists.us.ibm.com
> Subject: [nv-l] mib question/problem
>
>
> Hey everyone,
>
> Hope someone out there can give me a hand with this one. I have been
> trying to integrate Sun HW alerts (specifically x4200, v40z, and x2100)
> into Netview. Seems that when I generate some test messages (pull out a
> power cord, or use the test message generator) the host is sending a pET
> mib? Sun didn't provide any MIB that contains an OID close to what the
> machine is generating, so I downloaded a pET mib that I found on the
> Internet, but still no go - the specific traps don't exist in this
> generic MIB.
>
> An example of the OID is 1.3.6.1.4.1.3183.1.1...
>
> Can anyone shed some light on this for me?
>
> Thx,
>
> Brett
>
>
>
*********************************************************************************
> This e-mail and its attachments, is confidential and is intended for
> the addressee(s) only. If you are not the intended recipient,
> disclosure, distribution or any action taken in reliance on it is
> prohibited and may be unlawful. Please note that any information
> expressed in this message or its attachments is not given or
> endorsed by An Post unless otherwise indicated by an authorised
> representative independently of this message. An Post does not
> accept responsibility for the contents of this message and although
> it has been scanned for viruses An Post will not accept
> responsibility for any damage caused as a result of a virus being passed
on.
>
*********************************************************************************
>
|