Users Guide

NOTE: For additional details on SNMP configuration, see the operating system documentation.
Sever Administrator SNMP Install Actions
Server Administrator SNMP communicates with the SNMP agent using the SMUX protocol. When Server Administrator SNMP
connects to the SNMP agent, it sends an object identifier to the SNMP agent to identify itself as a SMUX peer. To support
SMUX the object identifier must be configured with the SNMP agent. In order to Server Administrator work with SMUX
protocol you need to enable by following the below steps to the SNMP agent configuration file.
● Open the SNMP agent configuration file./etc/default/snmpd.
● The default option available in the configuration file is: SNMPDOPTS='-Lsd -Lf /dev/null -u snmp -g snmp -I
-smux,mteTrigger,mteTriggerConf -p /run/snmpd.pid'
● With the above default configuration the SMUX module is disabled.
● To support snmpd to support SMUX change the configuration as : SNMPDOPTS='-Lsd -Lf /dev/null -u snmp -g
snmp -p /run/snmpd.pid'
Add in the SNMP agent configuration file ./etc/snmp/snmpd.conf
smuxpeer .1.3.6.1.4.1.674.10892.1
● To enable the SNMP configuration changes, restart SNMP agent by using: systemctl restart snmpd.
Changing The SNMP Community Name
Configuring the SNMP community name determines which management stations are able to manage your system through
SNMP. The SNMP community name used by management applications must match the SNMP community name configured
on the system running Server Administrator, so the management applications can retrieve the management information from
Server Administrator.
To change the default SNMP community name used for retrieving management information from a system running Server
Administrator:
1. Open the SNMP agent configuration file, /etc/snmp/snmpd.conf.
2. Find the line that reads: rocommunity public 127.0.0.1.
3. Edit this line by replacing public with the new SNMP community name. When edited, the new line should read:
rocommunity community_name 127.0.0.1.
4. To enable SNMP configuration changes, restart the SNMP agent by typing: systemctl restart snmpd .
Configuring the SNMP agent on systems running supported VMware ESXi
6.X operating systems
Server Administrator supports SNMP traps on VMware ESXi 6.X. If a stand-alone license is only present, SNMP configuration
fails on VMware ESXi operating systems. Server Administrator does not support SNMP Get and Set operations on VMware
ESXi 6.X as the required SNMP support is unavailable. The VMware vSphere Command-Line Interface (CLI) is used to configure
systems running VMware ESXi 6.X to send SNMP traps to a management station.
NOTE: For more information about using the VMware vSphere CLI, see vmware.com/support.
Configuring Your System To Send Traps To A Management Station
Server Administrator generates SNMP traps in response to changes in the status of sensors and other monitored parameters.
One or more trap destinations must be configured on the system running Server Administrator for SNMP traps to be sent to a
management station.
To configure your ESXi system running Server Administrator to send traps to a management station:
1. Install the VMware vSphere CLI.
2. Open a command prompt on the system where the VMware vSphere CLI is installed.
3. Change to the directory where the VMware vSphere CLI is installed. The default location on Linux is /usr/bin. The default
location on Windows is C:\Program Files\VMware\VMware vSphere CLI\bin.
Setup And Administration
21