Required Software
The software required for communication between the monitoring server and the monitored server is described below.
Virtual Software | Communication Method | Software required for monitoring server | Software required for mMonitored server |
|---|---|---|---|
Hyper-V | telnet | - | telnet server |
VMware ESX VMware ESXi VMware vCenter | https | - | - |
VMware ESX Red Hat Virtualization function (KVM) Red Hat Virtualization function (Xen) Solaris Containers | ssh | - | ssh server (*1) |
*1: The following software is required to communicate by SSH:
SSH V2.0 or later
For VMware ESX (if ssh communication is being used), Red Hat Virtualization function (KVM), Red Hat Virtualization function (Xen), and Solaris Containers
Please use ssh installed as a standard function of UNIX.
Point
Conditions to collect performance information of the monitored server, refer to "Agent for Agentless Monitoring" of "Installation Conditions and Resource Estimation" in the Installation Guide for more information about required packages.
Conditions under which collection can be performed
VMware ESX(if https communication is being used)/ VMware ESXi/ VMware vCenter:
HTTPS communication must be able to be used.
Hyper-V:
The command for collecting performance information (typeperf) must be able to be used.
Red Hat virtualization function (KVM):
The command for collecting performance information (virt-top, virsh) must be able to be used.
Red Hat virtualization function (Xen):
The command for collecting performance information (xentop) must be able to be used.
Solaris Containers:
The command for collecting performance information (zonestat) must be able to be used.
Using ssh communication in VMware ESX (for compatibility with old versions):
The command for collecting performance information (esxtop) must be able to be used.
Note
In case of VMware ESX (ssh connection), the reports of following categories are not available because some items can not be collected.
VMware virtual machine relocation
VMware resource allocation optimization
VMware tuning guidance
In case of VMware ESX 3.5, the reports of following category are not available because some items can not be collected.
VMware tuning guidance
Resource estimation
The following explains the number of telnet/ssh connection sessions required on the monitored server so that performance information can be collected from the monitored server.
Platform of the monitored server | Number of telnet or |
|---|---|
VMware ESX (https connection) VMware ESXi VMware vCenter | - |
VMware ESX (ssh connection) | 1 |
Hyper-V | 5 |
Red Hat virtualization function (KVM) | 10 |
Red Hat virtualization function (Xen) | 10 |
Solaris container | 12 |
Note
If the total number of connection sessions is very large, it may take some time for the DCM services/daemons of the monitoring server to start or stop.
Communications by telnet or ssh may not be performed properly if the network status of the environment is not optimal (there are intermittent interruptions, etc.) or if the monitored server is busy. Perform monitoring in an environment with consistently reliable communications.
The default maximum number of sessions that can be connected simultaneously with Hyper-V (Windows) telnet is "2". Therefore it will be necessary to change the maximum number of sessions that can be connected simultaneously. Follow the steps in "2.2.2 Settings for Monitored Servers".
There is no limit to the maximum number of sessions that can be connected simultaneously by default with VMware ESX/ Red Hat Virtualization function (KVM)/ Red Hat Virtualization function (Xen)/ Solaris container(UNIX) ssh.
The following explains the disk space required on the monitored server so that performance information can be collected from the monitored server.
Disk space required on the monitored server: 1MB
