0% found this document useful (0 votes)
44 views

MiVoice MX-ONE SNMP Configuration

The document provides instructions for configuring SNMP on a MiVoice MX-ONE server for correct operation with Mitel Performance Analytics. It describes verifying the SNMP configuration file on the MX-ONE server and ensuring the rocommunity, trapcommunity, and trap2sink values are correctly configured to public and the IP address of the Mitel Performance Analytics Probe.

Uploaded by

Eid Cavalcanti
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
44 views

MiVoice MX-ONE SNMP Configuration

The document provides instructions for configuring SNMP on a MiVoice MX-ONE server for correct operation with Mitel Performance Analytics. It describes verifying the SNMP configuration file on the MX-ONE server and ensuring the rocommunity, trapcommunity, and trap2sink values are correctly configured to public and the IP address of the Mitel Performance Analytics Probe.

Uploaded by

Eid Cavalcanti
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 1

30/11/21, 11:29 MiVoice MX-ONE SNMP Configuration

You are here: Configuring MPA Devices > MiVoice MX-ONE Device Configuration > MiVoice MX-ONE SNMP
Configuration

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

# MX-ONE alarm traps can trigger snmptrapd to sent mail and textmessages

# trapcommunity: Default trap sink community to use

trapcommunity public

# trap2sink: A SNMPv2c trap receiver

trap2sink 172.16.1.222
2.  Verify the rocommunity setting and the trapcommunity setting. In the previous example, they are
highlighted in bold. Ensure both the rocommunity and trapcommunity values are the same and set to public.
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.

https://totalcomm.marwatch.net/help/Content/Config_Devices_Topics/H3MX-ONE_SNMP_Config.htm 1/1

You might also like