SNMP Agent Task
There are four branches in the IoTServer's MIB where you can map data objects. All four tables will be set to the same length that you specify as MIB Table Size here.
If you will be mapping floating point data in your MIB, you must select how you would like it to be encoded. There is no universally recognized representation of floating point in SNMP, but there are de facto standards to choose from. The floating point encodings available are included in the drop-down list. ASN Opaque refers to the Net-SNMP definition for floating point.
The maximum table sizes for the trap sender are defined here. Keeping the tables set to a range that you will actually use will improve efficiency.
The default XML configuration file is entered here. This is the file that the SNMP Agent will attempt to automatically load upon first time startup. After that, settings are retained in the database, and further file activity can be managed on the Config File page for the SNMP Agent.
Activity timeout is a form of watchdog. If the task manager does not see the SNMP Agent task update its activity indicator within this amount of time, the task manager will restart the SNMP Agent. If set to zero, the watchdog is disabled. The task manager itself is restarted by the Linux cron if it stops responding.
IMPORTANT: Do not set the activity timeout for SNMP to less than 120 seconds. While the SNMP functions will update their timers much faster during normal operation, they will time out during startup while waiting for all of the background SNMP tasks and daemons to start. Setting the activity timeout too short for SNMP tasks will result in a system that can never fully start up.