Benutzer-Werkzeuge

Webseiten-Werkzeuge


snmp_en

Unterschiede

Hier werden die Unterschiede zwischen zwei Versionen gezeigt.

Link zu der Vergleichsansicht

snmp_en [09.02.2018 17:30] (aktuell)
Jochen Erwied angelegt
Zeile 1: Zeile 1:
 +====== SNMP ======
 +
 +The SNMP protocol driver allows communication with SNMP enabled devices.
 +SNMP v1 and v2 are supported. Sending and receiving of traps is possible.
 +
 +The driver'​s name is //snmp//\\
 +The routing address of the first SNMP-driver is //910//\\
 +The data point file for the first SNMP driver is //​snmp1.txt//​\\
 +The configuration file for global settings of the first SNMP driver is [[snmp_cfg|snmp1.cfg]]
 +
 +For the SNMP driver as well as all other gateway drivers the data point definitions are as follows:
 +
 +^Type  ^Description ​ ^
 +^  M  |Integer value (binary data points, counters) which can/shall only be read by the gateway ​ |
 +^  S  |Integer value which can be either read or written by the gateway. (to M-BUS writing is not possible) ​ |
 +^  X  |Floating point value (with decimal place) which can/shall only be read by the gateway ​ |
 +^  Y  |Floating point value (with decimal place) which can be either read or written by the gateway. (to M-BUS writing is not possible) ​ |
 +^  A  |String, is used e.g. with BACnet Trends and ESPA4.4.4 data points ​ |
 +
 +Addresses are defined as follows:
 +
 +<​type>​ <​agent>​ [<​OID>​]
 +
 +^Expression: ​ ^Range of values ​ ^Description ​ ^
 +^<​type> ​ |value\\ event\\ failure ​ |value: value\\ event: Trap\\ failure: communication failure with agent  |
 +^<​agent> ​ |0-9  |No. of SNMP agent (according to configuration in [[snmp_cfg|snmp1.cfg]]) ​ |
 +^<​OID> ​ |  |OID acc. MIB-file of the device separated by '​.'​ (value and event only). The OID is fixed if it starts with a '​.'​. The protocol driver modifies relative OIDs in fixed by adding the prefix '​ObjectRoot'​ defined in the [[snmp_cfg|snmp1.cfg]]. ​ |
 +
 +In order to make the protocol driver understand in which format the information located in the OID is given each data point needs a dedicated format information. See following format definitions.
 +
 +
 +format = <​format>​ [P:<​rate>​] [L:<​loc>​] [T:<​ver>​]
 +
 +Possible parameters:
 +
 +^Parameter: ​ ^Range of values ​ ^Description ​ ^
 +^<​format> ​ |INTEGER\\ COUNTER\\ GAUGE\\ TIMETICKS\\ UNSIGNED\\ STRING ​ |Type of variable ​ |
 +^<​rate> ​ |0-65535 ​ |Defines the polling cycles ​ |
 +^<​loc> ​ |0: received from remote device (default)\\ 1: locally defined ​ |Defines source of data |
 +^<​ver>​ |0: SNMP v1 Trap\\ 1: SNMP v2c notification |Defines which PDU-Type for sending an '​event'​ data point. is used. Only applicable for local '​event'​ data points. Default is '​NULL'​. ​ |
 +
 +Typical data point definitions:​
 +
 +  [M failure 1]
 +    name = communication failure with agent 1
 +    query = pe
 +  ​
 +  [M value 1 11.3.3.1.2.1]
 +    name = Net frequency L1 of agent 1 relative (OID = ObjectRoot from [[snmp_cfg|snmp1.cfg]] + <OID> = .1.3.6.1.4.1.818.1.1.11.3.3.1.2.1)
 +    query = pe
 +    format = INTEGER
 +
 +To ignore an ObjectRoot the complete path must be defined with a '​.'​ at the beginning
 +
 +To give the data point "Net frequency L1 of agent 1" fixed it must be defined as follows:
 +
 +  [M value 1 .1.3.6.1.4.1.818.1.1.11.3.3.1.2.1]
 +    name = Net frequency L1 of agent 1 fixed
 +    query = pe
 +    format = INTEGER
 +
 +For receiving a trap the definition must be as follows:
 +
 +If needed the trap must be reset at the gateway if  sending device does not send the reset.
 +
 +  [S event 3 .1.3.6.1.4.1.3711.15.1.1]
 +    name = Trap of agent 3 
 +    query = pe
 +    writecache = yes
 +    format = INTEGER T:0
 +    ​
  
snmp_en.txt · Zuletzt geändert: 09.02.2018 17:30 von Jochen Erwied