Users Guide

Setup and Administration 37
1 Add the following line to the file:
trapsink IP_address community_name
where IP_address is the IP address of the management station and
community_name is the SNMP community name.
2 To enable SNMP configuration changes, restart the SNMP agent by typing:
/etc/init.d/snmpd restart
Configuring the SNMP Agent on Systems Running Supported VMware
ESX 4.X Operating Systems to Proxy VMware MIBs
The ESX 4.X server can be managed through a single default port 161 using
the SNMP protocol. To do this, snmpd is configured to use the default port
161 and vmwarehostd is configured to use a different (unused) port, for
example, 167. Any SNMP request on the VMWare MIB branch is rerouted to
the
vmware-hostd using the proxy feature of the snmpd daemon.
The VMWare SNMP configuration file can be modified manually on the ESX
server or by running VMWare Remote Command-Line Interface (RCLI)
command
vicfg-snmp from a remote system (Windows or Linux). The RCLI
tools can be downloaded from the VMware website
(vmware.com/download/vi/drivers_tools.html).
Below are the required steps for the configuration.
1
Edit the VMWare SNMP configuration file ( /etc/vmware/snmp.xml )
either manually or run the following vicfg-snmp commands to modify the
SNMP configuration settings. This includes the SNMP listening port,
community string, and the trap target ipaddress/port and trap community
name and then enable the VMWare SNMP service.
a vicfg-snmp.pl --server <ESX_IP_addr> --username
root --password <password> -c <community name>
-p X –t <DMC_IP_Address>@162/<community name>
Where X represents an unused port. To find an unused port, check the
/etc/services file for the port assignment for defined system services. Also,
to make sure that the port selected is not currently being used by any
application/service, run the following command on the ESX server:
netstat –a command
NOTE: Multiple IP addresses can be entered using a comma-separated list.
book.book Page 37 Tuesday, July 6, 2010 12:01 PM