System information

Manual:SNMP

You can also specify administrative contact information in the above settings. All SNMP data will be available to

communities configured in community menu.

General Properties

Sub-menu: /snmp

This sub menu allows to enable SNMP and to configure general settings.

Property Description

contact (string; Default: "") Contact information

enabled (yes | no; Default: no) Used to disable/enable SNMP service

engine-id (string; Default: "") for SNMP v3, used as part of identifier. You can configure suffix part of engine id using this argument. If

SNMP client is not capable to detect set engine-id value then this prefix hex have to be used 0x80003a8c04

location (string; Default: "") Location information

trap-community (string; Default:

public)

Which communities configured in community menu to use when sending out the trap.

trap-generators (interfaces |

start-trap; Default: )

What action will generate traps:

•• interfaces - interface changes;

•• start-trap - snmp server starting on the router

trap-interfaces (string | all;

Default: )

List of interfaces that traps are going to be sent out.

trap-target (list of IP/IPv6;

Default: 0.0.0.0)

IP (IPv4 or IPv6) addresses of SNMP data collectors that have to receive the trap

trap-version (1|2|3; Default: 1) Version of SNMP protocol to use for trap

Note: engine-id field holds the suffix value of engine-id, usually SNMP clients should be able to detect the

value, as SNMP values, as read from the router. However there is a possibility that this is not the case. In

which case, the engine-ID value has to be set according to this rule: <engine-id prefix> + <hex-dump suffix>,

so as an example, if you have set 1234 as suffix value you have to provide 80003a8c04 + 31323334,

combined hex (the result) is 80003a8c0431323334

Community

Sub-menu: /snmp community

This sub-menu allows to set up access rights for the SNMP data.

There is little security in v1 and v2c, just Clear text community string („username“) and ability for Limiting access

by IP adress.

Since SNMP v3, better options have been introduced - Authorisation (User + Pass) with MD5/SHA1, Encryption

with DES.

[admin@MikroTik] /snmp community> print value-list

name: public

address: 0.0.0.0/0

security: none

read-access: yes

write-access: no

authentication-protocol: MD5