Difference between revisions of "SNMP Agent"
Jimhogenson (talk | contribs) |
Jimhogenson (talk | contribs) |
||
(10 intermediate revisions by the same user not shown) | |||
Line 1: | Line 1: | ||
+ | == Overview == | ||
+ | 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. | ||
+ | |||
+ | The branches of the IoTServer MIB are as follows: | ||
+ | |||
+ | {| class="wikitable" | ||
+ | |- | ||
+ | | 1.3.6.1.4.1.3815.1.5.1.1 || Integer, signed, 32-bit representation of local objects | ||
+ | |- | ||
+ | | 1.3.6.1.4.1.3815.1.5.1.2 || Integer, unsigned, 64-bit representation of local objects | ||
+ | |- | ||
+ | | 1.3.6.1.4.1.3815.1.5.1.3 || Floating point representation of local objects | ||
+ | |- | ||
+ | | 1.3.6.1.4.1.3815.1.5.1.4 || Character string representation of local objects | ||
+ | |- | ||
+ | | 1.3.6.1.4.1.3815.1.5.1.5 || Trap send rule parameters included in trap messages | ||
+ | |- | ||
+ | | 1.3.6.1.4.1.3815.1.5.1.6 || Trap send data included in trap messages | ||
+ | |- | ||
+ | | 1.3.6.1.4.1.3815.1.5.1.7 || Trap OID identifying a trap message | ||
+ | |} | ||
== Status == | == Status == | ||
− | === | + | === [[SNMP Agent MIB-Int32 Data]] === |
− | === | + | === [[SNMP Agent MIB-Uint64 Data]] === |
− | === MIB | + | === [[SNMP Agent MIB-Real Data]] === |
− | === MIB | + | === [[SNMP Agent MIB-Char Data]] === |
− | === | + | === [[SNMP Agent Trap Status]] === |
− | === | + | === [[SNMP Agent Device Status]] === |
== Configuration == | == Configuration == | ||
− | === | + | |
− | === | + | 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. |
− | === MIB | + | |
− | === MIB | + | === [[SNMP Agent MIB-Int32 Mapping]] === |
− | === | + | === [[SNMP Agent MIB-Uint64 Mapping]] === |
− | === | + | === [[SNMP Agent MIB-Real Mapping]] === |
− | === Config File === | + | === [[SNMP Agent MIB-Char Mapping]] === |
− | === Snmpd.conf === | + | === [[SNMP Agent Trap Send Rules]] === |
+ | === [[SNMP Agent Trap Send Rule Edit]] === | ||
+ | === [[SNMP Agent Trap Destination Devices]] === | ||
+ | === [[SNMP Agent Device Edit]] === | ||
+ | === [[SNMP Agent Config File]] === | ||
+ | === [[SNMP Agent Snmpd.conf File]] === | ||
+ | == Reference Information == | ||
+ | ==== [[SNMP Agent XML Files]] ==== | ||
+ | ==== [[SNMP Agent CSV Files]] ==== |
Latest revision as of 22:53, 22 April 2019
Contents
- 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
Overview
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.
The branches of the IoTServer MIB are as follows:
1.3.6.1.4.1.3815.1.5.1.1 | Integer, signed, 32-bit representation of local objects |
1.3.6.1.4.1.3815.1.5.1.2 | Integer, unsigned, 64-bit representation of local objects |
1.3.6.1.4.1.3815.1.5.1.3 | Floating point representation of local objects |
1.3.6.1.4.1.3815.1.5.1.4 | Character string representation of local objects |
1.3.6.1.4.1.3815.1.5.1.5 | Trap send rule parameters included in trap messages |
1.3.6.1.4.1.3815.1.5.1.6 | Trap send data included in trap messages |
1.3.6.1.4.1.3815.1.5.1.7 | Trap OID identifying a trap message |
Status
SNMP Agent MIB-Int32 Data
SNMP Agent MIB-Uint64 Data
SNMP Agent MIB-Real Data
SNMP Agent MIB-Char Data
SNMP Agent Trap Status
SNMP Agent Device Status
Configuration
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.