MiVoice MX-ONE SNMP Configuration

SNMP must be properly configured on the MiVoice MX-ONE server for correct operation with Mitel Performance Analytics.

To verify the SNMP configuration on the MiVoice MX-ONE:

1.  Open the snmpd.conf file with the following command:

sudo vi /etc/snmp/snmpd.conf

The content of the file is displayed. The following is an example:

# Please see /usr/share/doc/packages/net-snmp/EXAMPLE.conf for a
# more complete example and snmpd.conf(5).
#
# Writing is disabled by default for security reasons.  If you'd like
# to enable it uncomment the rwcommunity line and change the community
# name to something nominally secure (keeping in mind that this is
# transmitted in clear text).

# don't use ' < > in strings for syslocation or syscontact
# Note that if you define the following here you won't be able to change them with snmpset
syslocation Server Room
syscontact Sysadmin (root@localhost)

# These really aren't meant for production use.  They include all MIBS
# and can use considerable resources.  See snmpd.conf(5) for information
# on setting up groups and limiting MIBS.
# rocommunity public
rwcommunity mysecret 127.0.0.1
# MX-ONE alarm traps uses agentx protocol
master agentx
AgentXSocket localhost:705
# number of responses allowed for a single varialbe in a getbulk request
maxGetbulkRequest 2
# number of responses allowed for a getbulk request
maxGetbulkResponses 20
# MX-ONE alarm traps can trigger snmptrapd to sent mail and textmessages
# trapcommunity: Default trap sink community to use
trapcommunity mysecret
# trap2sink: A SNMPv2c trap receiver
trap2sink 172.16.1.222

2.  Do one of the following:

Verify the rocommunitysetting and the trapcommunity setting. Ensure both the rocommunity and trapcommunity values are the same and set to public. Ensure that Mitel Performance Analytics is configured with this value.

To support emergency response notifications, verify the rwcommunity setting and the trapcommunity setting. In the previous example, they are highlighted in bold. Ensure both the rwcommunity and trapcommunity values are set to the same value. Ensure that Mitel Performance Analytics is configured with this value.

3.  Ensure that at least one trap2sink destination value is set to the IP address of the Mitel Performance Analytics Probe that is used to monitor the MiVoice MX-ONE server. In the previous example, it is highlighted in bold.

4.  For MiVoice MX-ONE version 7.5 and greater, set maxGetbulkResponses to 20 to ensure that the Interfaces dashboard panel correctly displays data.