
Running VMware ESX Server
130
www.vmware.com
SNMP uses community names somewhat like passwords. They are exchanged in clear
text in communications between the agent and its clients. All requests to the agent
must contain a community name, which the agent compares against the one set up
in the configuration file to determine what permissions and capabilities the request
has.
The VMware SNMP agent sets up a single default read-only community named
public. This means that, by default, all incoming requests must include public as
the community name. These read-only requests can only retrieve the values of
variables.
The trapcommunity parameter is also a community name. This community name
is used by the agent. It is included in trap messages that the agent sends.
Give these two parameters values that are appropriate for your site’s SNMP
management configuration. Remember that the rocommunity value must be used
when communicating with the agent to get responses, and your management
software should expect to see the value of trapcommunity in trap messages from
the agent.
Trap Configuration
# Trap destinations
# Multiple trapsinks can be configured; each must appear
# on a separate configuration line
# e.g.
# trapsink mercury.solar.com
# trapsink venus.solar.com
trapsink localhost
Set the trapsink configuration parameter to tell the agent where to send its trap
messages. You can configure multiple trapsink lines, as indicated in the
configuration file’s comments. Set the values for this variable to conform to the
management structure at your site. For instance, assign the managing workstation’s
host name as one of the values for this parameter.
Other Configuration File Entries
# VMware ESX Server SNMP modules -- Edit this section at
# your own risk
dlmod SNMPSystem /usr/lib/vmware/SNMPSystem.so
dlmod SNMPVMInfo /usr/lib/vmware/SNMPVMInfo.so
dlmod SNMPVMDisk /usr/lib/vmware/SNMPVMDisk.so
dlmod SNMPVMNet /usr/lib/vmware/SNMPVMNet.so
Comentarios a estos manuales