Thanks Andew for your post.

Can you send the details regarding the trap which you are trying to add using Add Trap functionality (Field details like Enterprise OID, format string, severity, etc.), so that we can try the same at our end and confirm what is going wrong in this case.

Need to confirm this but looks like some the entered fields are exceeding the limits set by OME database.

Thanks,

Vijay 

Thanks Andrew for the details.

So, there is a limitation currently in MIBImport Tool which allows maximum length of Enterprise OID not more than 128 characters. The Enterprise OID you entered is 157 characters long and hence this message.

We are aware about this limitation and fixing this soon.

BTW, from which particular MIB you are getting this long Enterprise OID? (Just for our information).

Thanks,
Vijay

Here are the values I entered into the fields:

 

Category Name: Other

Trap Name: Test

Description: Test

Enterprise 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

Generic ID: 6

Specific ID: 4625

Format String: $1

Severity: Critical

Interesting use case. Thanks much for sharing it here Andrew :).

Thanks,
Vijay.

This isn't from a specific MIB, I am using the "Search Unknown Traps" button to look up traps I've been sending from various servers.

The Enterprise OID is from the windows event to trap translator (evntwin.exe). I am setting up some critical systems of ours to send SNMP traps any time a user fails to log in (event number 4625). It's a very handy  way to keep track of who's attempting to access your systems.