Mibs, Communities & Users

The "Mibs, Communities & Users" tab lets you configure which MIB files to load, which communities to accept as well as configure any SNMP v3 users.

In order for OIDs to be interpreted correctly, you will need to specify the matching MIBs for the SNMP daemon. Which MIBs to load depends on which devices the daemon will be receiving traps from. Standard MIBs can be downloaded from the Internet, whereas vendor-specific MIBs are usually obtained from the vendor, e.g. the vendor's web site.

You can specify up to 64 MIB files, and multiple MIB files can be selected when adding MIBs.

Make sure that any MIB files added are located on a physical drive, and not a network drive, and that the account the "Network Services" service is running under ("LocalSystem" by default) has permissions to read the file(s).

SNMP v1 and v2c traps use community names for authentication. While inherently insecure, you will need to specify any community names with which v1 or v2c traps are sent. If a v1 or v2c traps is received, and no matching community is listed, the trap will be discarded.

Incoming v3 traps need to be authenticated or authenticated in order to be accepted.

clip0596

When adding SNMP v3 users, you can specify the following:

- Username (required)

- EngineID (optional, a usually unique identifier from the network device)

- Authentication password and algorithm

- Encryption password and algorithm

Authentication and Encryption

When transmitting SNMP v3 traps over a network, you can choose to authenticate to ensure authenticity of the sender, and/or encrypt the trap to ensure that the contents of the trap are not visible to a third party. Encrypting traps is particularly important when transmitting traps over an insecure media like the Internet. The following authentication and encryption algorithms are currently supported:

Authentication: MD5, SHA

Encryption: DES, AES, 3DES