Re: SNMP'ing

• Previous message: Nelson Rodriguez: "Re: Please, WMI on W98"
• In reply to: resident_eagle: "SNMP'ing"
• Messages sorted by: [ date ] [ thread ]

Date: Sat, 1 Jan 2005 19:31:14 -0800

Hi,
eXc Software (www.eXcSoftware.com) has a way to display SNMP traps (and can
also do SNMP Get and Set requests) into MOM2005 without having to deal with
MIBS and/or WMI. The end result is that you get your traps (from any snmp
cabable device) into MOM with meaniful trap information (i.e. not a varbind
list dump). Hope this helps.

"resident_eagle" <resident_eagle@yahoo.com> wrote in message
news:2ff596a8.0412302322.4ef6c0c6@posting.google.com...
> Greetings.
>
> I've been advised that I should post the message to this group and so
> I hope it's the right one. I have a few questions about compiling
> MIB's on Windows Server 2003 (even 2000 will do) and using traps for
> alert notification in MOM 2005. This issue is not stricty related to
> MOM (in my humble opinion), but is more network, WMI and OS oriented.
> So I think.
>
> I'll try to make a long story short (I doubt though). I am trying to
> make the server (w2k3), on which MOM resides, listen and translate
> traps that the networking device (configurable via telnet), that is
> connected to UPS, sends. I need to compile some vendor MIB's so that
> MOM 2005 can collect events using WMI SNMP Provider.
>
> I've been trying some trap-listening software out that I've found on
> the Net. It's mostly freeware, shareware or free-trial-period
> software. Those applications have their own MIB loaders and, even
> though they tend to report some warnings and/or errors, they succeed
> to compile them. I figure that they have advanced parsing/compiling
> capabilities and are able to recover from non-critical errors.
>
> On the other hand, by using SMI2SMIR (w2k) and MIBCC (w2k & w2k3) I
> don't get satisfying results. SMI2SMIR adds objects to the namespace
> while MIBCC creates a binary file. It seems to me that the main reason
> why these programs cannot compile those third-party MIB's is the
> dependency. I received five enterprise MIB's which all import
> RFC1155-SMI (that is contained within smi.mib), RFC1213-MIB
> (mib_ii.mib), RFC-1212 and RFC-1215. They cannot be compiled because
> there are syntax errors (where other loaders didn't have problems)
> like the following:
>
> <235,Warning>: (line 28, col 3): Unrecognized character in input,
> ignored. "(null)" (SMI2SMIR output)
> SYNTAX ERROR on line: 28, Last token read is "man" (MIBCC output)
>
> and the line reads:
>
> ups_man OBJECT IDENTIFIER ::= { enterprises 5491 }.
>
> I'm not familiar with the syntax so there's a possibility that
> underscores are not allowed. But I'm almost positive that they knew
> the rules when they were writing it. I also received two MIB's named
> RFC1628.mib and RFC1628A.mib which contain UPS-MIB definition. They
> have the same dependencies and a few more (RFC1316-MIB, SNMPv2-TC and
> SNMPv2-SMI), but they pass through SMI2SMIR successfully with a bunch
> of warnings. I'm aware that some RFC MIB's are loaded by default and
> others have to be included in command line. I don't have RFC's 1212,
> 1215 and 1316. I've dug the first one out in some reference article,
> but it dates from 1991 or something like that. I'm unable to compile
> the RFC1155-SMI (smi.mib), too. And that one is crucial.
>
> OK, this story was not short. Maybe I'm thinking totally wrong and
> going blindly in wrong direction. I've stopped a few times to ask for
> a direction, but only so much help did I receive.
>
> Please, people, help!
>
> Many thanks in advance. Best regards.

• Previous message: Nelson Rodriguez: "Re: Please, WMI on W98"
• In reply to: resident_eagle: "SNMP'ing"
• Messages sorted by: [ date ] [ thread ]