FieldServer FS-8704-09 SNMP instruction manual

Page 15

FS-8704-09 SNMP Driver Manual

Page 15 of 39

Appendix A.1.3. Receiving SNMP Traps – Storing using a Lookup Table

Some devices send trap messages with the same OID’s irrespective of the causal events. The OID contents provide event specific information such as event origin and state. Consider a trap containing 3 OID’s. One has an integer value (event state) and the other two have strings reporting the event source. The SNMP driver is capable of using the two string OID’s to form a search string to search a lookup table. The driver uses the index value associated with a matching entry to determine a Data Array location to store the event state. Thus a single trap message can be used to populate a Data Array in such a way that the location in the DA indicates the event source and the value found at that location indicates the event state.

Example:

In the trap below ;

1.3.6.1.4.1.290.1.0 contains the event state

1.3.6.1.4.1.290.2.0 contains the 1st part of identifier of the event source

1.3.6.1.4.1.290.3.0 contains the 2nd part of identifier of the event source

Simple Network Management Protocol

Version: 1 (0)

Community: public

PDU type: TRAP-V1 (4)

Enterprise: 1.3.6.1.4.1.290 (SNMPv2-SMI::enterprises.290)

Agent address: 10.32.6.3 (10.32.6.3)

Trap type: ENTERPRISE SPECIFIC (6)

Specific trap type: 70000000

Timestamp: 0

Object identifier 1: 1.3.6.1.4.1.290.1.0 (SNMPv2-SMI::enterprises.290.1.0)

Value: INTEGER: 4

Object identifier 2: 1.3.6.1.4.1.290.2.0 (SNMPv2-SMI::enterprises.290.2.0)

Value: STRING: "CROSSTWN_KDA"

Object identifier 3: 1.3.6.1.4.1.290.3.0 (SNMPv2-SMI::enterprises.290.3.0)

Value: STRING: "EMS_84_900MHZ_RADIO_B"

Object identifier 4: 1.3.6.1.4.1.290.4.0 (SNMPv2-SMI::enterprises.290.4.0)

Value: STRING: "EMS 84 900MHZ RADIO B"

Object identifier 5: 1.3.6.1.4.1.290.5.0 (SNMPv2-SMI::enterprises.290.5.0)

Value: INTEGER: 0

When configured correctly the driver will concatenate the values of the two source OID’s to form a search string for a lookup table. An offset value extracted from a matching entry is used to determine the location to store the event state value.

The example below illustrates how to configure the FieldServer to achieve this:

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

Image 15
Contents Applicability & Effectivity Driver Manual FS-8704-09 Snmp VersionTable of Contents Integer Octetstream Timerticks String FS-8704-09 Snmp Driver Manual Snmp DescriptionMax Nodes Supported Required 3rd Party Hardware 3rd Party Client FS-8704-09 Snmp Driver Manual Hardware ConnectionsStation 3rd Party Nodes non-SNMPSnmp Traps Data Arrays/DescriptorsSnmp FS-8704-09 Snmp Driver Manual Client Side Node Descriptors Snmpoid Driver Related Map Descriptor ParametersTiming Parameters RDBC, WRBC, WrbxOID FS-8704-09 Snmp Driver Manual Map Descriptor ExampleDAAI3 Rdbc DAAI3 WrbxServer Side Data Arrays SNMPDA1SNMPDA2 Server Side Map Descriptors Server Side Node DescriptorsAppendix A.1.1. Trap Source IP Address DAAI3 Page FS-8704-09 Snmp Driver Manual Snmpoid 192.168.1.174 Status Normal Status LO Alarm Status HI Alarm Status Normal Status AlarmSNMPDA2 Snmptrap Appendix A.2.2. Polling for Integer bound DataTrap Map Descriptors are then configured as below Page TRAP-TYPE from RFC-1215 FIELDSERVER-MIB Definitions = BeginSnmp Comparison of Style2 to Style3 Comparison of Style1 to Style3 Sample Configuration File Style1 MIB File based on above configuration Style2 MIB File based on above configuration Style3 MIB File based on above configuration Style3 Traps Description Page Trap INTFYI FYI MIBERR SnmptypeseqFS-8704-09 Snmp Driver Manual State=%s FS-8704-09 Snmp Driver Manual UINT32