Function Overview
Virtual resource management collects performance information from physical and virtual servers of operating systems and virtualized software and centrally manages it.
By comparing the virtual server performance information collected with this function with performance information about the physical server, overarching decisions can be made to optimize the resources in the server and improve use efficiency.
Performance information for the physical server is displayed as a report. This allows usage of the physical server's CPU, memory, and disk to be seen.
The virtual server's performance information is stacked for display in reports for each guest. This allows usage of the CPU, memory, and disk to be seen for each guest.
Information that can be collected
Performance information for physical servers and virtual servers is collected by using the agent for Agentless Monitoring functions from virtualized software and connecting remotely through telnet, ssh or https.
Performance information that can be collected depends on the virtualization software to be monitored.
The methods for collecting the performance information of physical servers and virtual servers and the main types of performance information collected by the monitoring virtualized software are described below.
Virtualized software | Physical server | Virtual server |
|---|---|---|
VMware ESX | CPU, memory, and disk performance information is collected from VMware. | CPU, memory, and disk performance information is collected from VMware. |
VMware ESXi | ||
Hyper-V | CPU performance information is collected from Hyper-V. | CPU performance information is collected from Hyper-V. |
Red Hat virtualization function (Xen) | CPU, memory, and disk performance information is collected from the host OS (Linux). | CPU, memory, and disk performance information is collected from Red Hat virtualization function (Xen). |
Note
The performance information of the host OS (Windows) is also collected if you make Hyper-V the subject of monitoring.
The CPU performance information values collected from Hyper-V's host OS (Windows) are not correct, however. If it is necessary to check the CPU performance information of the physical server, look at the CPU performance information values collected from Hyper-V.
The performance information of the host OS (Linux) is also collected if you make the Red Hat virtualized function (Xen) the subject of monitoring.
The virtual server's resources are stacked for display in a report.
Threshold monitoring can be performed on the different pieces of information and notifications can be sent as alarms when a monitored item exceeds a defined value.
Information Collection Differences between VMware ESX and VMware ESXi
The values collected from VMware ESX by logging in the remote console by ssh and command execution on the virtual server. It causes the delay of displaying as shown at "Notes" in "3.2.4 Display".
Meanwhile, the values collected from VMware ESXi by SOAP API through https communication. So data is displayed in real time.
Collection interval
Collection interval is 5 minutes.
Procedure
Steps for setting an agent for Agentless Monitoring to manage virtual resources are described below.
