- 1 Overview
- 2 Status
- 3 Configuration
- 3.1 SNMP Agent MIB-Int32 Mapping
- 3.2 SNMP Agent MIB-Uint64 Mapping
- 3.3 SNMP Agent MIB-Real Mapping
- 3.4 SNMP Agent MIB-Char Mapping
- 3.5 SNMP Agent Trap Send Rules
- 3.6 SNMP Agent Trap Send Rule Edit
- 3.7 SNMP Agent Trap Destination Devices
- 3.8 SNMP Agent Device Edit
- 3.9 SNMP Agent Config File
- 3.10 SNMP Agent Snmpd.conf File
- 4 Reference Information
The local data objects within the IoTServer can be read and written as SNMP variables via the SNMP Agent. The local objects cannot be accessed directly - they need to be mapped to one of the branches of the IoTServer's MIB. The IoTServer supports four branches, each having a specific data format for sharing of data. The most universally accepted data format in SNMP is the simple integer. Regardless of the internal data format assigned to a local object, it will be converted to the data type associated with the corresponding MIB branch when an SNMP Get request is processed. Likewise when an SNMP Set is performed, the data will be automatically converted to the native internal data type assigned to the local object.
NOTE: Any time the definition of the MIB is changed by adding or removing variables in the MIB branches, it is necessary to restart SNMP to reload the new definition of the MIB. When the MIB is changed as illustrated in any of the "Mapping" sections below, go to the SNMP Agent Config File page and click the Restart SNMP button at the bottom of that page.