A great solution to interconnect SNMP Devices on other protocol Networks like Modbus (Modbus RTU, Modbus TCP, Modbus ASCii), BACnet (BACnet IP, BACnet MSTP, BACnet Ethernet), Lonworks, Metasys N2 and M-Bus, KNX.
|
Downloads
Protocol Datasheets
SNMP
Hardware Datasheets
QuickServer
FS-3510
Configuration Manuals
SNMP
|
FieldServer’s SNMP Gateway is a great solution to enable two way communication between:
- Between an SNMP network/device and a different protocol network like Modbus RTU, Modbus TCP, Modbus ASCii, BACnet MSTP, BACnet IP, Lonworks, Metasys N2,M-Bus or KNX.
- FieldServer SNMP Gateway models have multiple RS-485 ports, Ethernet ports and Lonworks ports (depending on the model). Hence it is possible to interconnect devices on different serial, Ethernet and Lonworks protocols together.
Sending and Receiving SNMP Traps
SNMP Traps Introduction:
SNMP traps are asynchronous notifications from the SNMP Agent to the SNMP Manager. Traps are a method by which an SNMP Agent can notify the SNMP management station of significant events using unsolicited SNMP messages. Traps can be:
- Granular Traps: These type of Traps can be distinguished from one another because each has a unique identification number . The unique identification number is the Object Identifier or OID assigned to the Trap. When an SNMP Manager receives a granular type trap from an SNMP Agent it looks up the OID (of the Trap received) in the transaction file called the Management Information Base or MIB. Since each Granular Trap has a unique OID associated with it no actual alarm data need be sent with Trap. It can be looked up by the Manager from the MIB. This characteristic of Granular Traps helps save bandwidth because redundant information need not be sent with the trap and can be looked up the SNMP Manager.
- Traps with bound variables: It is possible for an SNMP agent to send Traps for various events using the same OID. In other words, the same OID is used for the different trap messages. The trap message itself contains data pertaining to the Trap in a simple key-value pair configuration. Each key-value pair is known as variable binding.
FieldServer Gateway can Send and Receive SNMP Traps
In the image below: FieldServer gateway configured to receive Traps from SNMP Agents
In the image below: FieldServer gateway configured to Send Traps to SNMP Manager
Popular combinations for SNMP gateways
FieldServer Hardware platforms supporting SNMP protocol
How to configure the FieldServer Gateway?
- We will configure the Gateway for you based on your requirement and support you during commissioning of the Gateway, so you do not have to worry about configuring the FieldServer Gateway.
- However, it is very helpful to know how to configure the devices. All the required tools and supporting product manuals with be provided completely free of cost with your purchase.
- Configuration of the FieldServer is done using a '.csv' file. This file can be edited using any text editor (example Microsoft excel).
- In this file we need to enter information for the Client and Server side interfaces of the FieldServer. This includes but is not limited to:
- Node ids of the slave devices
- MSTP addresses/device address of the slave devices
- Baud rate, parity, stop bits for serial communication
- Scan rates
- And finally we need to create an internal mapping that would map each data value read on the client side to a data value on the server side.
- For detailed information on configuration please get in touch with us and review the configuration manual on top of this page
Device type
|
RS 485/232 ports
|
Lonworks Ports
|
Available Ethernet ports
|
Base Point count capacity
|
Extended Point count capacity
|
QuickServer
|
2
|
0
|
1
|
250
|
1000
|
QuickServer Lonworks
|
1
|
1
|
1
|
250
|
1000
|
Enhanced QuickServer
|
2
|
0
|
1
|
500
|
1000
|
Enhanced QuickServer Lonworks
|
1
|
1
|
1
|
500
|
1000
|
FS-B2010
|
1
|
0
|
1
|
500
|
5000
|
FS-B2011
|
1
|
1
|
1
|
500
|
5000
|
FS-B2510
|
2
|
0
|
1
|
500
|
5000
|
FS-B3510
|
5
|
1
|
2
|
1000
|
10000
|