# SNMP Connectivity

The communication driver for the SNMP protocol is implemented as an SNMP device. It provides high reading performance and supports various types of data.

### Key Features <a href="#h.33avvwqm4skg" id="h.33avvwqm4skg"></a>

* Communication with devices via SNMPv1 and SNMPv2 protocols.
* Data Types: BOOL, BYTE, DATETIME, DINT, DOUBLE, DWORD, FLOAT, INT, LONG, QWORD, STRING, WORD.
* Value conversion from OCTET STRING to an output data type (e.g. DOUBLE).
* Working in read and write modes.
* Block reading.

{% hint style="warning" %}
Please note that SNMP Trap is not supported in the current version of the server
{% endhint %}

### Block Reading Considerations <a href="#h.fqcp5zvvvgsf" id="h.fqcp5zvvvgsf"></a>

Before reading, the driver sorts the OID’s and organizes them into blocks. Typically, there are 25 OID’s per block (depending on the Items per Request parameter). With such mode of data reading, a negative effect may occur in the SNMPv1 protocol: if one of the OIDs is unavailable or does not exist, then the entire block will become inaccessible for reading, and the tags associated with it will go into the BadOutOfRange state. There is no such problem with the SNMPv2c protocol. In the case of SNMPv2c, only the OID that is unavailable or does not exist in the device will not be read, and the tag associated with it will go into the BadOutOfRange state.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.monokot.io/tags-and-devices/snmp-connectivity.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.