SNMP Client Device Edit

From Control Solutions IoTServer Documentation
Revision as of 03:24, 21 April 2019 by Jimhogenson (talk | contribs)
Jump to navigation Jump to search

This page is where you set up the devices that will be polled (SNMP Get, Set, Get-Next) as defined by the read maps, write maps, and table walk rules. The full set of parameters required for each device is set up once here, and then referenced by device number in any number of maps and rules.

Snmp client device edit 1.jpg

Device Number – A number ranging from 1 to device table size, and is referenced in read and write maps, and table walk rules, as the device to which the map applies.

Snmp client device edit 2.jpg

Name – Simply provides a reference name for use in the web UI.

Snmp client device edit 3.jpg

Peer Name – Provides a definition of where on the network to find the device. The peername in simplest form will be an IP address as illustrated in the XML file example above. However, if the network has access to a DNS server and that server is configured in the network settings of the local device, then peername may be any name that can be found via DNS lookup.

Snmp client device edit 4.jpg

Version – Specifies what SNMP version should be used to send the SNMP Get or Set, which in turn determines certain aspects of how the message is formatted. Version may be 1, 2, or 3 where 2 means v2c.

Rate – Real or integer poll time in seconds, can be fractional. Used as default when read, write, or walk rule does not have a poll time specified.

Snmp client device edit 5.jpg

Timeout – Integer number of seconds for session timeout.

Retries – Number of times that the SNMP engine should automatically retry a Get or Set if it fails.

Snmp client device edit 6.jpg

Max Var Binds – Specifies the maximum number of varbinds that may be included in the same request. When multiple values are requested from the same device, the client will attempt to group them into a single SNMP Get or Set for efficiency (less network traffic). The client will group up to this many varbinds into the same request.

Poll Tolerance – Real or integer poll tolerance in seconds, can be fractional. Poll tolerance refers to the amount of time overlap permitted when the client is attempting to group varbinds into a single Get or Set. In other words, if a map or rule timeout is not quite zero but is less than the poll tolerance, it will be treated as zero and grouped into the Get or Set that is already under way.

SNMPv2 Configuration - The following parameters are used only for v1/v2c

Snmp client device edit 7.jpg

Max Receive Size – Provides a limit on the maximum message size that should be accepted, defaults to 1500 if omitted (recommended).

Max Send Size – Provides a limit on the maximum message size that should be sent, defaults to 1500 if omitted (recommended). The maxVarBinds should be set to 1 if the maxSendSize is reduced.

Community – The community string as defined for SNMP v1 and v2c.

SNMPv3 Configuration - The following parameters are used only for v3

Snmp client device edit 8.jpg

Security Level - Sets security level, 1=noAuthNoPriv, 2=authNoPriv, 3=authPriv. Those are the SNMP acronyms meaning (1) no authentication or privacy, (2) authentication required but privacy is not, (3) both authentication and privacy are required. The term “privacy” means encryption.

User Name - Sets the SNMP security name, analogous to username in SNMP terms.

Authentication Type - Sets the authentication type, may be “NOAUTH”, “MD5”, or “SHA”. It determines how the username (security name) is hashed when transmitted.

Authentication Phrase - Sets the authentication phrase, analogous to an SNMP password.

Privacy Type - Sets the privacy type, may be “NOPRIV”, “DES”, or “AES”. This determines which encryption algorithm will be used.

Privacy Phrase - Sets the privacy phrase which is used as the encryption key.

Note: For sending traps with SNMPv3, you must know the engine ID of the recipient. The SNMPv3 client, however, will query the remote agent to learn engine ID as well as engine time and boots. It will then use this information to do the actual data query.