| Page 16 of 39 |
Step 1: Define the Lookup Table
The driver loads the table into memory and uses it when a new trap is received. If the search string is formed by concatenating two OID Sting fields then the driver places a colon, thus a colon should be placed between the two substrings. If the search string formed from the trap contents does not match an entry in the table the driver prints a message in the error log at an offset of zero. For this reason you cannot use a value of zero for the parameter called ‘SNMP_Lookup_Table_Offset’.
In the configuration file create a Driver Table section.
Driver_Table |
|
|
SNMP_Lookup_Table_Offset, | SNMP_Lookup_Table_String, | Protocol |
1, | Sandhill_KDA:24V_CHARGER, | SNMP |
2, | BIG_BEND_DVA_02_102:AC_POWER_FAILURE, | SNMP |
3, | CROSSTWN_KDA:EMS_84_900MHZ_RADIO_B, | SNMP |
|
|
|
Storage Offset:
If the lookup string matches a row in the table then the value of the parameter called ‘SNMP_Lookup_Table_Offset’ is used as an offset into the Data Array
Do not use values of zero. Take care to ensure that the offset will not result in an offset that is beyond the end of the Data Array.
Lookup String:
The String contents of up to two OID’s are concatenated to form a search string. Place a colon ‘:’ between each part of the search string if two OID’s are used to form the string.
Searches are case insensitive
There are some limitations to the table:
•it can hold a maximum of 200 entries.
•Each string entry can be a maximum of 59 characters.
•When the driver searches the table looking for a match it ignores the case of the entries.
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com Tel: (408) 262 2299 Fax: (408) 262 9042 Toll Free: (888) 509 1970 email: support@fieldserver.com