The SNMP driver allows the FieldServer to transfer data to and from devices over Ethernet using the
SNMP version 1 protocol. The FieldServer can emulate either a Server (SNMP Agent) or Client.
Max Nodes Supported:
FieldServer Mode Nodes Comments
Client 25 Each Node is specified by a unique IP address
Server 1 As a Server the SNMP driver can act as a single Node only
The Client can be configured to read values specified by their SNMP Object Identifiers (OID’s), which are
defined in the MIB file (Management Information Base) of the target device. When acting as an SNMP
Agent (Server), the driver makes the contents of specified integer data arrays available to any SNMP
Client. The FieldServer MIB file sets out the OIDs to use.
The current version of the driver can send and receive SNMP traps. The following SNMP data types are
supported:
• INTEGER
• OCTET_STREAM
• TIMER_TICKS
• STRING
The maximum number of traps currently supported is 255.
The FieldServer Enterprise ID is 6347. MIB files are generated automatically from the FieldServer
configuration files. A selection of standard MIB-2 OIDs are supported to allow interaction with popular
Network Management packages.
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com
The FieldServer is connected to the Ethernet using the UTP cable supplied. Two typical hardware
configurations are shown below:
1. FieldServer as SNMP Agent (Server)
Network
Management
Station
FieldServer SNMP
Agent/Server
2. FieldServer as SNMP Client
(3rd Party Client)
(SNMP Client)
TCP/IP Cloud
SCADA
FieldServer
TCP/IP Cloud
3rd
Party
Nodes
(non-SNMP)
Managed Nodes
(SNMP Agents)
3.1. Hardware Connection Tips / Hints
The FieldServer utility program Ruinet will connect to the FieldServer even if the Netmask setting on
the PC differs from the setting on the FieldServer. SNMP will only work between Nodes for which
these settings correspond, however, thus all Nodes required to communicate using SNMP must have
the same Netmask setting.
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com
For a detailed discussion on FieldServer configuration, please refer to the FieldServer Configuration
manual. The information that follows describes how to expand upon the factory defaults provided in the
configuration files included with the FieldServer (See “.csv” sample files provided with the FieldServer).
This section documents and describes the parameters necessary for configuring the FieldServer to
communicate with a SNMP Agent/Server. Please refer to Appendix A: for a discussion of how to receive
SNMP TRAPS.
4.1. Data Arrays/Descriptors
The configuration file tells the FieldServer about its interfaces, and the routing of data required. In
order to enable the FieldServer for SNMP communications, the driver independent FieldServer
buffers need to be declared in the “Data Arrays” section, the destination device addresses need to be
declared in the “Client Side Nodes” section, and the data required from the servers needs to be
mapped in the “Client Side Map Descriptors” section. Details on how to do this can be found below.
Note that in the tables, * indicates an optional parameter, with the bold legal value being the default.
Adapter Adapter Name N1, N22
Protocol Specify protocol used SNMP
If this parameter is omitted or set to 0 the short form of
encoding length will be used. If the parameter is set to
1 (and the Length is ≤ 127) the long form of encoding
length will be used. For Length >127 short form will
be used regardless of the setting.
Long form: an extra byte will be inserted to indicate
the number of following bytes which indicates the
length of the following section in message.
Short form: only length value will be inserted.
This parameter can be configured if it is required that
“Community” be a different name in order to receive
traps.
0 (default),
1
Any string up to
255 characters,
Public
2
Not all ports shown are necessarily supported by the hardware. Consult the appropriate Instruction
manual for details of the ports available on specific hardware.
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com
Identifies Node; needed only if Node Online/Offline
monitoring is used.
IP Address of remote Agent. Refer to Appendix A.1
for more information.
Controls how MIB file is formatted. Refer to
Appendix A.3 for more info.
Controls how traps are reported in MIB file. Refer to
Appendix A.3 for more info.
Controls whether a Node’s traps contribute to the
MIB file. Where duplicate traps are sent to more
than one Node, second and subsequent Nodes will
not contribute to the MIB file. Review the example
MIB files and configuration file in Appendix A.3.
0 – Node’s traps contribute to MIB File.
1 – Node’s traps do not contribute to MIB file.
If this parameter is set it is possible for the
FieldServer to sequentially read (walk) the SNMP
Server in the same way as the snmpwalk parameter
works on SNMP.
alphanumeric
characters
1-255
Legal 4 byte IP
address on the
same subnet.
‘Standard’;
‘Custom’;
‘NuDesign’
Style1; Style2;
Style3
0; 1
Walk, -
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com
5. Configuring the FieldServer as a SNMP Server/Agent
For a detailed discussion on FieldServer configuration, please refer to the FieldServer Configuration
Manual. The information that follows describes how to expand upon the factory defaults provided in the
configuration files included with the FieldServer. (See “.csv” sample files provided with the FieldServer).
This section documents and describes the parameters necessary for configuring the FieldServer to
communicate with a SNMP Client such as a Network Management application. Please refer to Appendix
A: for a discussion of how to configure SNMP TRAPS.
The configuration file tells the FieldServer about its interfaces, and the routing of data required. In order to
enable the FieldServer for SNMP communications, the driver independent FieldServer buffers need to be
declared in the “Data Arrays” section, the FieldServer virtual Node(s) needs to be declared in the “Server
Side Nodes” section, and the data to be provided to the clients needs to be mapped in the “Server Side
Map Descriptors” section. Details on how to do this can be found below.
Note that in the tables, * indicates an optional parameter, with the bold legal value being the default.
5.1. Server Side Data Arrays
A special Data Array naming convention is used to map FieldServer Data Arrays into the SNMP OID
addressing scheme. Any data arrays that are to be visible via SNMP have to be named in the
following way:
The Data_Format and Data_Array_Length may be freely chosen, but the name has to be in the
format SNMP_DA_x, where x is sequential from one Data Array to the next. The corresponding
entries in the automatically generated MIB file would appear as shown below.
Adapter Adapter Name N1, N23
Protocol Specify protocol used SNMP
This parameter can be
SNMP_Community*
Example
// Server Side Connections
Adapters
Adapter, Protocol
N1, SNMP
configured if it is required that
“Community” be a different name
in order to receive traps.
Any string up to 255 characters,
Public
5.3. Server Side Node Descriptors
Section Title
Nodes
Column Title Function Legal Values
Node_Name Provide name for Node
Protocol Specify protocol used SNMP
Example
// Server Side Nodes
Nodes
Node_Name, Protocol
Agent 1, SNMP
Up to 32 alphanumeric
characters
5.4. Server Side Map Descriptors
No Server Side Map Descriptors are required by SNMP for Get or Set requests, since the mapping of
FieldServer Data Arrays into the SNMP OID addressing scheme follows the method outlined in
Section 5.1 above. Server Side Map Descriptors are required to configure SNMP TRAPS as outlined
in Appendix A.
Scaling on Client side is per normal model but on Server side, normal model only applies if a Map
Descriptor is used.
3
Not all ports shown are necessarily supported by the hardware. Consult the appropriate Instruction
manual for details of the ports available on specific hardware.
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com