I did a web search on converting Windows events to traps and a few hits came up. You may have a look at those.  But I've never tried it.  I'm not sure how the traps would be (or not be) formatted unless there is a MIB from MS on this.  

Let me know if you get something like this working :)

Rob

Thank you for your answer,

I know how to convert the events from the log to SNMP traps and theres no MIBS from Microsoft for that  and my question came for that reason. Theres no MIBs from MS and I wondered whether OME can manage those types of traps in any way, giving OME the way to identify the Unkown traps.

For instance, I'd like to tell OME what to do when those traps come in, if you receive the traps with OID x.x.x and ID x, you have to tag it as Warning...

Thank you.

There is no MIB from Microsoft for all of the events that can be generated in Windows.

This is an opportunity to add a feature to OME, that allows the creation of a single trap using the enterprise OID and trap specific ID. Currently only allowing the import of MIB files to add traps isn't very flexible, and writing custom MIBs is a very time consuming process. Allowing the addition of a custom trap would be very helpful.

Yes, I would also appreciate this. Also editing of traps would be great.

With IT Assistant this was possible....

(but not native MIB import).

Guys,

Thanks for the suggestion.  I will pass it along to the product team for consideration.  Not sure if there is anything on mibdepot.com for the Win events, but you might take a look.

Regards,

Rob

hello i tried adding a trap yesterday after using evntwin.exe to get the details of a windows event, i had a problem entering the Specific id in the "Add trap" function of the MIB tool. The Specific id was 1073748860, which obviously is an integer but the error states that the specific id must be an integer.

Screenshot showing the error is attached.

Hi JARV061,

Looks like you found a bug.

This is a bug in Add Trap validation logic where we are validating for Specific ID to be valid integer. Due to the bug we are limiting the Specific ID maximum value to be 32767 (Int16) which is not correct.

Working on fixing for the next OME release.  I don't have an ETA at the moment.

Thanks,

Rob

Ok, so i tried another one with a smaller specific id, now i get "string or binary data would be truncated." The statement has been truncated.

Any ideas?  

Hello Vijay, details here:

OID: .1.3.6.1.4.1.311.1.13.1.35.77.105.99.114.111.115.111.102.116.45.87.105.110.100.111.119.115.45.83.101.99.117.114.105.116.121.45.65.117.100.105.116.105.110.103

Specific trap:

4728

Format string:

A member was added to a security-enabled global group.%n%nSubject:%n%tSecurity ID:%t%t%6%n%tAccount Name:%t%t%7%n%tAccount Domain:%t%t%8%n%tLogon ID:%t%t%9%n%nMember:%n%tSecurity ID:%t%t%2%n%tAccount Name:%t%t%1%n%nGroup:%n%tSecurity ID:%t%t%5%n%tGroup Name:%t%t%3%n%tGroup Domain:%t%t%4%n%nAdditional Information:%n%tPrivileges:%t%t%10 

fyi, i have added a trap successfully this morning, but this one above produces the error as described.

Thank you.

Thanks for sharing your problem with us. Can you pl. send the details for the fields for the trap you are trying to add? This will help us in identifying the problem and propose a solution.

Hello,

Thanks for this information. The reason for the failure to add the above mentioned trap is because of the length of the OID which is 157. The supported maximum length of Enterprise OID in OME is 128 characters.

Thanks

Thank you, are there any plans to increase the length of the OID??

I passed this along for review and consideration.  

It's the first time we'd seen it, so they will take a look at it.

Hopefully, using the shorter OID will get you moving.

Rob