VM Server Detail
Detail reports are related to a specific enterprise object, such as a backup job or SAN fabric. You can only access detail reports through a link presented in the context of a main report, providing additional information that augments the main report. Detail reports cannot be generated, customized, or saved, as they are specific to the report from which they were derived. They are not available in search results.
Explore your data center using APTARE StorageConsole customizable report templates or by using parts of your IT infrastructure as entry points. Use Search to find reports, templates and dashboards across the portal.
Use the Reports tab to examine the APTARE StorageConsole catalog of templates, dashboards and reports - organized by products along with user-created, and system folders. The main report is located here:
Virtualization Manager > Administration Reports > VM Server Summary
Click the Name link.
Note: VMware Tools (VM Tools) must be installed to enable collection of the IP address, host name, mount points, disk path, available space on VM guest volumes, and guest operating system of the VM.
VM Server Detail Data
Name | Name of the VM Server that is hosting the virtual server; for example, the ESX host |
Host Name | Hostname of the guest; value is displayed only if VMware Tools is installed; links to Host Details |
IP Address | IP address of the Virtual Machine; value is displayed only if VMware Tools is installed |
Data Center | The data center in which the server resides. |
State | Network adapter connection state: Connected, Not Responding, Disconnected, None |
Status | White=Status Unknown, Green=Normal, Yellow=Warning, Red=Alert, a definite problem |
Hardware Health | Indicates the overall health of the host’s hardware: None, Unknown, Green=Normal, Yellow=Warning, Red=Alert |
System Vendor | Host vendor |
System Model | Model of the host system |
Total Memory | Total memory available as a resource to the VMs on this host |
Total CPU | Total CPU available as a resource to the VMs on this host |
CPU Vendor | Processor’s vendor |
CPU Description | Type of processor |
CPU Speed | Processor speed |
# HBAs/Ports | Number of host bus adapters and ports on the VM Server |
# NICs | Number of physical network interface cards |
NIC Speed | Speed of the interface cards |
Cluster Name | Name of the cluster associated with the VM Server |
# Total VMs | Number of VMs configured on this host and in the inventory |
# Active VMs | A VM is active when it is in the inventory and powered on; it is inactive if it is in the inventory, but powered off. |
# Datastores | Number of datastores that this VM Server is using |
Datastore Usage | Amount of storage in the datastore that this VM Server is using |
# Disks | The number of disks that the VM Server can access, either internal disks or LUNs. Drill down to the Datastore Utilization Summary. |
Unallocated Disk | Mouse over the thermometer bar to view the total disk capacity, the amount used, and the % of the total used. Drill down to the Datastore Utilization Summary. |
Version | Version of the virtual server software, such as ESX |
Last Updated | Timestamp of last data collection |
Performance & Forecast
CPU | Average and Maximum usage graphed over time for the number of samples taken within that time frame. |
Largest VMs
Click the link to access the full list of the largest VMs, listed in descending order, with the top storage-consuming VMs at the top of the list.
Note: VMware Tools (VM Tools) must be installed to enable collection of the IP address, host name, mount points, disk path, available space on VM guest volumes, and guest operating system of the VM.
For a description of these fields, see
VM Summary.
Datastores
For a description of the fields in this table, see
Datastore Usage Breakdown.
Disks
These are the physical disks that are available to the VM Server.
For a description of the fields in this table, see
Datastore Utilization Summary.
Host Details by Source
Hosts can be collected by any number of sources such as vendor products. This table lists the details that have been collected by a vendor product so that you can validate the collected details.
Display Name | Name that is displayed in reports. |
Host Name | Name of the host as it was collected by the vendor product. |
IP Address | IP address of the host. |
Product Group | The product group, such as Capacity, for which the host data was collected. |
Source | A specific source such as vendor product (subsystem) from which host data was collected; for example, VMware. |
Date Created | The date and time the host was created in the Portal database. |
Last Updated | The date and time the host data was updated in the Portal database. |
OS Platform | Operating system of the host, as collected from this vendor product; for example, Windows Server 2008 R2. |
OS Version | The host’s specific operating system version, as collected from this vendor product; for example, 6.01. |
Make | The host’s make, as collected from this vendor product; for example,Windows-x64. |
Model | The host’s model, as collected from this vendor product; for example, PowerEdge 2950. |
Backup Server Type | The host’s role in a backup relationship, client or server. |
Data Collection Options and VM Server Detail
If this report is accessed via a drilldown from another report, the values shown represent the type of data collection that was configured to collect this data.
A Virtualization Manager data collection policy can be configured to gather data as follows:
• Inventory (default option): Collect only the data associated with the VMs in the inventory.
• Collect all files in datastore: Perform a full scan of the datastore to discover files that are resident on the datastore, but not associated with a VM in the inventory. This option finds files that may be invisible to VMware, but that are consuming space on the datastore.
When the Inventory option is configured in the data collector policy, it has the following impact on fields shown in this report:
• VM Not In Inventory will be zero.
• Total VM Used will be reduced by the amount that would have been collected as VM Not In Inventory if an all files collection had been done.
When the Collect all files in datastore option is configured in the data collector policy, it has the following impact on fields shown in this report:
• The Last Modified date will be missing for files not found in the datastore scan.
