SNMP, or Simple Network Management Protocol, provides a set of operations and a protocol to permit remote management and remote monitoring of a network device and/or its services. This server currently offers support for remote monitoring via get requests and traps using both IPv4 and IPv6 protocols.
Under Configuration, click SNMP.
Set Service status to Enabled to support SNMPv1, SNMPv2c, and SNMPv3.
Complete the following fields as required and then click Save.
Field | Description |
---|---|
SNMPv2c community string for read-only access | Enter the community string that SNMPv2c clients use to monitor this server via get requests and traps. The community string defaults to "public". |
SNMPv2c network access setting |
Select the network access setting for SNMPv2 services:
|
SNMPv3 Settings |
To facilitate SNMPv3 communication, you must add a user account to the MSL server that matches an account on the SNMP manager. This "User-based Security Model" (USM) enables unique authentication and encryption settings to be configured for each account. For instructions, see Configure SNMPv3 Users. |
System contact address |
Specify the email address to which all system notifications should go.
|
System location | Enter a string that identifies the location of the system. (ie. Server room 2, rack 1) |
Vital process monitoring | To monitor the server's vital processes, like the web server, secure shell daemon, mail server (with the 6040 blade), and so forth, leave this option at its default of "Enabled". If any problems are detected, an error message and description will be added to the 1.3.6.1.4.1.2021.2.1.100 and 1.3.6.1.4.1.2021.2.1.101 MIB columns, respectively, available via a GET request. |
Monitor disk usage | To monitor disk space usage on your server's root partition, leave this option at its default of "Enabled". If any problems are detected, an error message and description will be set in the 1.3.6.1.4.1.2021.9.1.100 and 1.3.6.1.4.1.2021.9.1.101 MIB columns, respectively, available via GET request. |
Disk space threshold | If you are monitoring disk space usage on your server's root partition, you need to decide upon a threshold value at which the issue will be flagged at the predefined OID. You may leave this at the default value of 5%, or supply a value. If you supply a value of your own, it may be a numerical percentage of the overall disk space, followed by a percent sign (no spaces), or you may provide an absolute value in bytes. |
Monitor CPU usage | To monitor the server's use of the CPU, leave the following setting at "Enabled". If any problems are detected, and error message and description will be set in the 1.3.6.1.4.1.2021.10.1.100 and 1.3.6.1.4.1.2021.10.1.101 MIB columns, respectively, available via GET request. |
One minute CPU threshold | If you have CPU monitoring enabled, you must choose a threshold value for the one minute load average, above which this server will flag the error at the previously mentioned OID. The value must be a positive real number with no more than two decimal places of precision. |
Five minute CPU threshold | If you have CPU monitoring enabled, you must choose a threshold value for the five minute load average, above which this server will flag the error at the previously mentioned OID. The value must be a positive real number with no more than two decimal places of precision. |
Fifteen minute CPU threshold | If you have CPU monitoring enabled, you must choose a threshold value for the fifteen minute load average, above which this server will flag the error at the previously mentioned OID. The value must be a positive real number with no more than two decimal places of precision. |
Trap host or address | If you wish to send trap messages to a remote host or hosts, whenever the server boots, the snmpd daemon starts and for authentication failures with the snmpd daemon, enter the hostname or IP address of the host designated to receive these trap messages. If this is left blank, traps will not be sent. To send traps to more than one host, enter the hostnames and/or IP addresses separated by commas. |
SNMPv2c Trap community string | Enter the trap community string to use when sending trap messages. If you do not enter a trap community string, the community string for read-only access will be used. |
SNMPv3 Trap username | Enter the SNMPv3 trap user name to use when sending trap messages. If you leave this field blank, SNMP traps will be sent using SNMP v2c. |
Download Mitel enterprise MIBs |
If you have network management software that you would like to use to monitor this server via SNMP, and would like to import Mitel's enterprise MIBs into it, download them by clicking Download. Note: The file you receive is a zip file, so you require appropriate software to open it. Additionally, the MIB files are in Unix file format, so the MS Windows Notepad is not an appropriate application to use in opening them.
|
If you implement support for SNMPv3, you must add at least one user account that matches an account on the SNMP manager. As part of this configuration, you can enable authentication and encryption.
Under Configuration, click SNMP.
Under SNMPv3 Settings , click Configure SNMPv3 Users .
Complete the following fields as required and then click Add.
Field | Description |
---|---|
User name | Type a user name (also known as “securityname”) for the SNMPv3 user. |
Authentication Type |
Select the Authentication Type that matches SNMP manager/agent configuration:
|
Authentication Password | If you selected an Authentication Type (MD5 or SHA1), you must enter an authentication password (also known as “authentication passphrase”) at least eight characters long. |
Privacy Protocol |
Select the Privacy Protocol that matches SNMP manager/agent configuration:
|
Privacy Password | If you selected a Privacy Protocol (DES), you must enter a privacy password. |
Engine ID (Optional) | If the SNMP manager requires a hard-coded Engine ID, enter it here. Otherwise, leave this field blank and the SNMP manager will discover the Engine ID automatically. |