6.5.1
Table Of Contents
- vSphere Monitoring and Performance
- Contents
- About vSphere Monitoring and Performance
- 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
- Data centers
- Datastores and Datastore Clusters
- Disk Space (Data Counters)
- Disk Space (File Types)
- Disk Space (Datastores)
- 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
- Streaming Events to a Remote Syslog Server
- Retention of Events in the vCenter Server Database
- 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 Use 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
- View System Log Entries
- View System Logs on an ESXi Host
- System Logs
- Export System Log Files
- ESXi Log Files
- Upload Logs Package to a VMware Service Request
- Configure Syslog on ESXi Hosts
- Configuring Logging Levels for the Guest Operating System
- Collecting Log Files
- Viewing Log Files with the Log Browser
- Enable the Log Browser Plug-In on the vCenter Server Appliance
- Enable the Log Browser Plug-In on a vCenter Server Instance That Runs on Windows
- Retrieve Logs
- Search Log Files
- Filter Log Files
- Create Advanced Log Filters
- Adjust Log Times
- Export Logs from the Log Browser
- Compare Log Files
- Manage Logs Using the Log Browser
- Browse Log Files from Different Objects
- Index
Here, port is the port the SNMP agent uses to listen for polling requests.
N The port you specify must not be already in use by other services. Use IP addresses from the
dynamic range, port 49152 and up.
2 (Optional) If the ESXi SNMP agent is not enabled, run the following command:
esxcli system snmp set --enable true
Configure ESXi for SNMPv1 and SNMPv2c
When you congure the ESXi SNMP agent for SNMPv1 and SNMPv2c, the agent supports sending
notications and receiving GET requests.
In SNMPv1 and SNMPv2c, authentication is performed by using community strings. Community strings are
namespaces which contain one or more managed objects. This form of authentication does not secure the
communication between the SNMP agent and the management system. To secure the SNMP communication
in your environment, use SNMPv3.
Procedure
1 Congure SNMP Communities on page 154
To enable the ESXi SNMP agent to send and receive SNMP v1 and v2c messages, you must congure
at least one community for the agent.
2 Congure the SNMP Agent to Send SNMP v1 or v2c Notications on page 155
You can use the ESXi SNMP agent to send virtual machine and environmental notications to
management systems.
Configure SNMP Communities
To enable the ESXi SNMP agent to send and receive SNMP v1 and v2c messages, you must congure at least
one community for the agent.
An SNMP community denes a group of devices and management systems. Only devices and management
systems that are members of the same community can exchange SNMP messages. A device or management
system can be a member of multiple communities.
If you run ESXCLI commands through vCLI, you must supply connection options that specify the target
host and login credentials. If you use ESXCLI commands directly on a host using the ESXi Shell, you can use
the commands as given without specifying connection options. For more information on connection options
see vSphere Command-Line Interface Concepts and Examples.
Prerequisites
Congure the ESXi SNMP agent by using the ESXCLI commands. See Geing Started with vSphere Command-
Line Interfaces for more information on how to use ESXCLI.
Procedure
u
Run the esxcli system snmp set command with the --communities option to congure an SNMP
community.
For example, to congure public, East, and West network operation centers communities, run the
following command:
esxcli system snmp set --communities public,eastnoc,westnoc
Each time you specify a community with this command, the seings you specify overwrite the previous
conguration. To specify multiple communities, separate the community names with a comma.
vSphere Monitoring and Performance
154 VMware, Inc.