The Sybase CEP Engine supports sending V1 traps.
The adapter's Properties View for V1 traps appears as:
The properties derive from the Net-snmp sendtrap utility. The syntax for this command corresponds closely to the adapter Properties View settings. The uptime in the sendtrap utility is determined from internal values and represents an approximation to the uptime of the system hosting Sybase CEP Server. The Generic Trap Number corresponds to the commonly used enterprise trap.
The variable length list in the "OIDs, Type and Value" field contains data sent with the trap. This list must conform to the schema definition. Since there are three OID/types in this list, there should be three data items in the schema. The actual data is converted to a string and appended to the OID list item. There is an assumption that the schema types maps into the Net-snmp types. This mapping is:
Abbreviation |
Datatype |
i |
integer |
u |
unsigned32 |
c |
counter32 |
t |
Time ticks 1/100 second |
a |
IP address |
o |
OID |
s, x, d |
Octet string |
n |
Null |
b |
bit string |
U |
ASN_OpaqueU64 |
I |
ASN_OpaqueI64 |
F |
ASN_Opaque_Float |
D |
ASN_Opaque_Double |
The datatype to be used depends on the datatype on the host machine of the OID. If numeric datatypes are used, it is not necessary to provide a valid MIB OID; a made-up OID as illustrated in the screenshot can suffice. A made-up OID places the burden of processing on the trap daemon on the host machine. This can be convenient as this corresponds closely to a "name value" pair on the host machine.
Using a symbolic OID requires the proper correspondence of datatypes.
The Sybase CEP schema should closely approximate the Net-snmp datatype. Since all data is first converted to a string before calling the Net-snmp libraries, this allows flexibility in datatype matching.