6.0.1
Table Of Contents
- vSphere Monitoring and Performance
- Contents
- About vSphere Monitoring and Performance
- Updated Information
- Monitoring Inventory Objects with Performance Charts
- Performance Chart Types
- Data Counters
- Metric Groups in vSphere
- Data Collection Intervals
- Data Collection Levels
- View Performance Charts
- Performance Charts Options Available Under the View Menu
- Overview Performance Charts
- Clusters
- Datacenters
- Datastores
- Disk Space (Data Counters)
- Disk Space (File Types)
- Disk Space (Virtual Machines)
- Storage I/O Control Normalized Latency
- Storage I/O Control Aggregate IOPs
- Storage I/O Control Activity
- Average Device Latency per Host
- Maximum Queue Depth per Host
- Read IOPs per Host
- Write IOPs per Host
- Average Read Latency per Virtual Machine Disk
- Average Write Latency per Virtual Machine Disk
- Read IOPs per Virtual Machine Disk
- Write IOPs per Virtual Machine Disk
- Virtual Machine Observed Latency per Datastore
- Hosts
- Resource Pools
- vApps
- Virtual Machines
- CPU (%)
- CPU Usage (MHz)
- Disk (Average)
- Disk (Rate)
- Disk (Number)
- Virtual Disk Requests (Number)
- Virtual Disk Rate (KBps)
- Memory (Usage)
- Memory (Balloon)
- Memory (Swap Rate)
- Memory (Data Counters)
- Network (Usage)
- Network (Rate)
- Network (Packets)
- Disk Space (Data Counters)
- Disk Space (Datastores)
- Disk Space (File Types)
- Fault Tolerance Performance Counters
- Working with Advanced and Custom Charts
- Troubleshoot and Enhance Performance
- Monitoring Guest Operating System Performance
- Monitoring Host Health Status
- Monitoring Events, Alarms, and Automated Actions
- View Events
- View System Logs
- Export Events Data
- View Triggered Alarms and Alarm Definitions
- Live Refresh of Recent Tasks and Alarms
- Set an Alarm
- Acknowledge Triggered Alarms
- Reset Triggered Event Alarms
- Preconfigured vSphere Alarms
- Monitoring Solutions with the vCenter Solutions Manager
- Monitoring the Health of Services and Nodes
- Performance Monitoring Utilities: resxtop and esxtop
- Using the vimtop Plug-In to Monitor the Resource Usage of Services
- Monitoring Networked Devices with SNMP and vSphere
- Using SNMP Traps with vCenter Server
- Configure SNMP for ESXi
- SNMP Diagnostics
- Monitor Guest Operating Systems with SNMP
- VMware MIB Files
- SNMPv2 Diagnostic Counters
- System Log Files
- Index
Procedure
1 (Optional) If you are configuring informs, configure the remote users by running the esxcli system
snmp set command with the --remote-users option.
For example, run the following command:
esxcli system snmp set --remote-users userid/auth-protocol/auth-hash/priv-protocol/priv-
hash/engine-id
The command accepts the following parameters:
Parameter Description
userid The user name.
auth-protocol
The authentication protocol, none (for no authentication), MD5, or SHA1.
auth-hash
The authentication hash or - if the authentication protocol is none.
priv-protocol
The privacy protocol, AES128 or none.
priv-hash
The privacy hash, or - if the privacy protocol is none.
engine-id The engine ID of the SNMP agent on the remote system that will receive the informs.
2
Run the esxcli system snmp set command with the --v3targets option.
For example, run the following command:
esxcli system snmp set --v3targets hostname@port/userid/secLevel/message-type
The parameters of the command are as follows.
Parameter Description
hostname The host name or IP address of the management system that will receive the traps or informs.
port The port on the management system that will receive the traps or informs. If you do not specify a
port, the default port, 162, is used.
userid The user name.
secLevel
The level of authentication and privacy you have configured. Use auth if you have configured
authentication only, priv if you have configured both authentication and privacy, and none if you
have configured neither.
message-type
The type of the messages received by the management system. Use trap or inform.
3 (Optional) If the ESXi SNMP agent is not enabled, run the following command:
esxcli system snmp set --enable true
4 (Optional) Send a test notification to verify that the agent is configured correctly by running the esxcli
system snmp test command.
The agent sends a warmStart notification to the configured target.
Configure the Source of Hardware Events Received by the SNMP Agent
You can configure the ESXi SNMP agent to receive hardware events either from IPMI sensors or CIM
indications.
IPMI sensors are used for hardware monitoring in ESX/ESXi 4.x and earlier. The conversion of CIM
indications to SNMP notifications is available in ESXi 5.0 and later.
Chapter 9 Monitoring Networked Devices with SNMP and vSphere
VMware, Inc. 157