Optical Prime Excel Field Definitions – Live Optics Support

Overview

This article provides definitions of the terminology used in the Excel output of an Optical Prime Project.

Details Worksheet

This worksheet provides some summary information about the project.

Field	Description
Project ID	The Live Optics project ID number. This is a unique identifier for the project data that was used to generate the spreadsheet.
Project Name	The name of the project. This name can be edited in the online project viewer.
Date	The date when the project was created. This is always in the MM/DD/YYYY format.
Collector Build Version	The version of the collector used to gather the information used in this project. If more than one collector was used for this project, this is the version of the first collector in the project.

ESX-Hosts Worksheet

Each row in this worksheet represents a VMware ESXi hypervisor and displays basic inventory and configuration information for that host.

Column	Description
Hostname	The name of the ESXi hypervisor. Note: Usually the DNS name, but sometimes an IP address.
Datacenter	The name of the virtual datacenter that contains this ESXi server belongs.
vCenter	The version of vCenter that is monitoring this ESXi host.
Cluster	The name of the cluster that contains this ESXi host. Note: If the host is not in a cluster, then this field will be blank.
OS	The version of ESXi (or ESX if old enough) that this host is running.
Manufacturer	The manufacturer of the physical server (hardware) of this host.
Model	The model number of the physical server (hardware) of this host.
Serial No.	The service tag or serial number of the physical server (hardware) of this host. Note: If this is a blade server, this should be the service tag for the blade server itself (not the chassis).
CPU Sockets	The total number of CPU sockets (CPU packages) running on this host. Note: This only represents the running CPU sockets. If a socket is not equipped with a CPU or is otherwise disabled in the BIOS, then that socket will not be included in this count.
CPU Cores	The total number of CPU cores running on this host.
CPU Description	The manufacturer and model information of the CPU type installed on this host.
Net Clock Speed (GHz)	The sum of the clock speed for each CPU core running on this host measured in GHz.
CPU Clock Speed (GHz)	The clock speed of each individual CPU core running on this host measured in GHz.
CPU Threads	The total number of threads (e.g. hyper-threading) supported for all running CPUs and cores on this host.
Memory (KB)	The server RAM memory in kilobytes.
Local Capacity (GB)	The total size of any disk storage local to this server. Note: This includes local datastores, local RDM devices, local backup drives, and any disk storage not shared with other hosts in this project.
Free Capacity (GB)	The unused portion of disk storage local to this server as defined in Local Capacity.
Used Capacity (GB)	The used portion of disk storage local to this server as defined in Local Capacity.
Guest VM Count	The total number of guest virtual machines that are on this host. Note: This includes running and non-running guest virtual machines.
Number of NICs	The total number of network interface connection ports on the physical hypervisor host.
Number of HBAs	The total number of storage host bus adapters installed on the physical hypervisor host.
IP1	The first IP address assigned to this host.
IP2	The second IP address assigned to this host (if any).
IP3	The third IP address assigned to this host (if any). Note: ESXi hypervisors can obviously be configured with more than 3 IP addresses, but this report only will show the first three. IPv4 addresses are shown over IPv6 addresses.
Config Status	The overall status of the ESXi host as known by vCenter. gray - the status is unknown to vCenter green - the host is connected to vCenter red - the host is connected to vCenter and is reporting some kind of problem yellow - the host is connect to vCenter and might be reporting a problem
Boot Time	The date and time when the hypervisor host was last booted.

ESX-Performance Worksheet

Each row in this worksheet represents a VMware ESXi hypervisor and displays performance information for that host based on the real-time data collected.

Column	Definition
Hostname	The name of the ESXi hypervisor. Note: Usually the DNS name, but sometimes an IP address.
Datacenter	The name of the virtual datacenter that contains this ESXi server belongs.
vCenter	The version of vCenter that is monitoring this ESXi host.
Cluster	The name of the cluster that contains this ESXi host. Note: If the host is not in a cluster, then this field will be blank.
Peak CPU %	The peak CPU used by the ESXi host reported as a percentage of all of the CPU cores running on the host covering the entire duration of the real-time collection. Notes: 100% indicates that all CPU cores on the host were completed saturated. This field should fall within a range of 0 - 100%.
Peak CPU (GHz)	The peak CPU used by the ESXi host measured in GHz clock cycles covering the entire duration of the real-time collection.
Average CPU %	The average CPU used by the ESXi host reported as a percentage of all of the CPU cores running on the host covering the entire duration of the real-time collection.
Average CPU (GHz)	The average CPU used by the ESXi host measured in GHz clock cycles covering the entire duration of the real-time collection.
Peak Memory %	The peak memory usage by the ESXi host as a percentage of all of the available RAM memory installed on the host covering the entire duration of the real-time collection. Notes: 100% would indicate that at one time during the collection, all of the physical RAM was allocated by the ESXi host.
Peak Memory (MB)	The peak memory used by the ESXi host measured in megabytes covering the entire duration of the real-time collection.
Average Memory %	The average memory usage by the ESXi host as a percentage of all of the available RAM memory installed on the host covering the entire duration of the real-time collection. Notes: 100% would indicate that at one time during the collection, all of the physical RAM was allocated by the ESXi host.
Average Memory (MB)	The average memory used by the ESXi host measured in megabytes covering the entire duration of the real-time collection.
Peak IOPS	The peak IO operations per second (combining read and write operations) for this ESXi host to and from all storage attached to this host for the entire duration of the real-time collection.
Average IOPS	The average IO operations per second (combining read and write operations) for this ESXi host to and from all storage attached to this host for the entire duration of the real-time collection.
Average Read/Write Ratio	The average read and write ratio as a percentage covering the time records when the IOPS for the ESXi host were >= to the 90th percentile IOPS. Notes: This is not the average read/write ratio for the entire duration of the real-time collection. It is only the average for the top 10% of records by IOPS. In other words, when the ESXi host was at it’s busiest, this is the read/write ratio.
Peak Throughput MB/s	The peak (read and write) disk data rate from the ESXi host measured in megabytes per second for the entire duration of the real-time collection.
Avg. Throughput MB/s	The average (read and write) disk data rate from the ESXi host measured in megabytes per second for the entire duration of the real-time collection.
Peak Read Latency	The peak latency reported in milliseconds for reads issued by the ESXi host for the entire duration of the real-time collection. Notes: This latency is calculated at the system level of the ESXi host as an average of operations for each 2 minute sampling period. Therefore, it is possible that an individual datastore might have encountered a higher or lower peak latency for the period for a given operation.
Peak Write Latency	The peak latency reported in milliseconds for writes issued by the ESXi host for the entire duration of the real-time collection. Notes: This latency is calculated at the system level of the ESXi host as an average of operations for each 2-minute sampling period. Therefore, it is possible that an individual datastore might have encountered a higher or lower peak latency for the period for a given operation.
Avg. Read Latency	The average latency reported in milliseconds for read operations issued by the ESXi host for the entire duration of the real-time collection.
Avg. Write Latency	The average latency reported in milliseconds for write operations issued by the ESXi host for the entire duration of the real-time collection.

Host-Devices Worksheet

Each row represents a storage device connected to an ESXi host. The storage device usually is a datastore. However, it could also be a RDM LUN, backup LUN, or other disk attached to the system.

Column	Description
Server Name	Name of the ESXi host attached to this disk.
Device Name	Name of the storage device (usually a datastore name).
Device Type	Either Cluster, indicating that this storage device is shared between more than one ESXi host (and is almost certainly a datastore,) or Local, indicating that this is a disk that only locally accessible by this ESXi host.
Capacity (GB)	The advertised capacity of this device measured in gigabytes. Note: This device might be thin provisioned under the hood. In such cases, vCenter and the Optical Prime collection would be unaware of the real provisioned sized of this device.
Free Capacity (GB)	The unused space on this device measured in gigabytes.
Used Capacity (GB)	The used space on this device measured in gigabytes.
Vendor	The manufacturer of the storage device. Note: If the device is a datastore that consists of multiple disk extents, the vendor will be for the first disk extent listed in the datastore.
Model	The model name of the storage device.
Lun Type	One of these possible values: disk, tape, cdrom, communications, enclosure, mediaChanger, opticalDevice, printer, processor, scanner, storageArrayController, unknown, or worm.
SCSI Level	The supported SCSI protocol level version for SCSI primary commands (an integer value ranging from 2 - 6).
vStorageSupport	vStorage hardware acceleration support status. If a storage device supports hardware acceleration, the ESXi host can offload specific virtual machine management operations to the storage device. With hardware assistance, the host performs storage operations faster and consumes less CPU, memory, and storage fabric bandwidth.
Datacenter	The name of the virtual datacenter that contains this ESXi host.
vCenter	The version of the vCenter system monitoring this ESXi host.
VM Count	If this storage device is a datacenter, this is the number of guest virtual machines contained inside this datastore.

VMs Worksheet

Each row in this worksheet represents a guest virtual machine observed in the collection.

Column	Description
MOB_ID	The Managed Object Identifier string which identifies this guest virtual machine within the scope of the vCenter server monitoring the virtual machine. Note: If the project contains data from multiple vCenter servers, then virtual machines with duplicate Managed Object Identifiers are to be expected as these IDs are not globally uniq.
VM Name	The name of the guest virtual machine as shown in vCenter. Note: This name is set by the administrator when the virtual machine is deployed and often is different from the actual host-name of the guest virtual machine.
Guest Hostname	The host-name of the guest virtual machine from the perspective of the operating system running on the virtual machine. Note: if VMware Tools is not installed or running properly, this field might be blank.
IsRunning	TRUE if the virtual machine was running at the time of discovery during the beginning of the collection and FALSE if otherwise.
Power State	One of these values: poweredOn, poweredOff, or suspended.
VM OS	The operating system installed on the guest virtual machine. Notes: If VMware Tools is installed and running properly, this value should be accurate, but in other cases, this value might be an estimation of the installed operating system.
Disks	The number of virtual disks connected to this guest virtual machine.
NICs	The number of virtual network interfaces connected to this guest virtual machine.
Virtual CPU	The number of vCPUs provisioned for this guest virtual machine.
Provisioned Memory (MB)	The memory provisioned to this guest virtual machine measured in megabytes.
Used Memory (active) (MB)	The active memory usage for this guest virtual machine as reported during the discovery phase of collection measured in megabytes. Notes: The discovery phase occurs at the beginning of a collection and the used memory reported here reflects that specific point in time. This value may differ with the peak and average memory values shown in the VM-Performance worksheet as those values are based on 24 hours of historical performance data. Active memory is an estimation calculated by the ESXi host of how much memory is currently being actively used by the guest virtual machine. We recommend that this active memory is used for sizing purposes.
Consumed Memory (MB)	Amount of guest physical memory consumed by the virtual machine measured in megabytes as reported during the discovery phase of collection. Notes: Consumed memory does not include overhead memory. It includes shared memory and memory that might be reserved, but not actually used. VMware recommends that this metric be used for charge-back purposes. We do not recommend that this memory be used for sizing purposes - use active memory instead.
Provisioned Memory (Bytes)	Same as above, measured in bytes.
Used Memory (active) (Bytes)	Same as above, measured in bytes.
Consumed Memory (Bytes)	Same as above, measured in bytes.
Guest VM Disk Capacity (MB)	The total capacity measured in megabytes of all drives on this guest virtual machine from the perspective of the guest operating system. Notes: This value is reported by VMware Tools and will be unavailable if either VMware Tools is not installed or running properly. In the case where this value is not available, it will be a copy of the Virtual Disk Size (MB) data.
Guest VM Disk Used (MB)	The used capacity measured in megabytes of all drives on this guest virtual machine from the perspective of the guest operating system. Notes: This value is reported by VMware Tools and will be unavailable if either VMware Tools is not installed or running properly. In the case where this value is not available, it will be a copy of the Virtual Disk Used (MB) data.
Guest VM % Occupancy	VM Occupancy % = GuestVMDiskUsed ----------------------- x 100 GuestVMDiskCapacity
Virtual Disk Size (MB)	The total size measured in megabytes of all virtual disks for this guest virtual machine from the perspective of the ESXi host.
Virtual Disk Used (MB)	The total used capacity measured in megabytes of all virtual disks for this guest virtual machine from the perspective of the ESXi host.
VMware Tools Version	The version of VMware Tools installed on this guest virtual machine (if installed at all). Notes: If VMware Tools is not installed, this field will be blank.
Connection State	Connected: vCenter has access to this guest virtual machine. Disconnected: vCenter is currently disconnected to the ESXi host and thus this virtual machine. Inaccessible: One or more of the virtual machine configuration files are inaccessible. For example, this can be due to transient disk failures. In this case, no configuration can be returned for a virtual machine. Invalid: The virtual machine configuration format is invalid. Thus, it is accessible on disk, but corrupted in a way that does not allow the server to read the content. In this case, no configuration can be returned for a virtual machine. Orphaned: The virtual machine is no longer registered on the host it is associated with. For example, a virtual machine that is unregistered or deleted directly on a host managed by VirtualCenter shows up in this state.
Template	TRUE if this virtual machine is a template.
Unshared (MB)	Total storage space, in megabytes, occupied by the virtual machine across all datastores, that is not shared with any other virtual machine.
Datacenter	The name of the virtual datacenter that contains this guest virtual machine.
vCenter	The version of vCenter monitoring this guest virtual machine.
Cluster	The name of the cluster that contains this guest virtual machine. Notes: If the ESXi host for this virtual machine does not belong to a cluster, then this field will be blank
UUID	A unique identifier for this guest virtual machine. Notes: If this guest virtual machine is configured with Fault Tolerance, then the UUID of this machine will match the virtual machine which is it’s fault tolerant partner. Use InstanceUUID for a globablly unique identified that represents this exact instance of this virtual machine.
Datastore	Name of the datastores (can be a comma separated list) where this guest virtual machine’s virtual disks reside.
Host	The name of the ESXi host that contains this guest virtual machine.
Guest IP1	The first IP address of this guest virtual machine.
Guest IP2	The second IP address of this guest virtual machine.
Guest IP3	The third IP address of this guest virtual machine.
Guest IP4	The fourth IP address of this guest virtual machine. Notes: A guest virtual machine may be configured with any number of IP addresses, but only the first four are shown in this report.
Boot Time	The date and time when this guest virtual machine was last booted.
Date Provisioned	The date and time when this guest virtual machine was provisioned. Notes: This value is not always available.
Image Backup	Not Found: indicates that the virtual machine has no custom properties which are typically used by backup software to tag the virtual machine’s backup status Yes: indicates that the virtual machine has one or more custom properties which are typically used by backup software to tag the virtual machine’s backup status. Note, the presence of a custom property does not guarantee that the virtual machine has been backed up recently (or even at any point). However, the presence of custom properties is a strong indicator that the virtual machine was backed up at some point in the past.

VM-Performance

This worksheet will only be present if the user opted to collect individual guest virtual machine performance prior to beginning the collection. Each row represents a single guest virtual machine.

Column	Description
VM Name	The name of the guest virtual machine as shown in vCenter. Note: This name is set by the administrator when the virtual machine is deployed and often is different from the actual host-name of the guest virtual machine.
MOB_ID	The Managed Object Identifier string which identifies this guest virtual machine within the scope of the vCenter server monitoring the virtual machine. Note: If the project contains data from multiple vCenter servers, then virtual machines with duplicate Managed Object Identifiers are to be expected as these IDs are not globally unique.
Host	The name of the ESXi host.
Datacenter	The name of the virtual datacenter that contains this guest virtual machine.
Cluster	The name of the cluster that contains this guest virtual machine. Notes: If the ESXi host for this virtual machine does not belong to a cluster, then this field will be blank.
KB/sec %	The disk throughput on average that this virtual machine represents as a percentage of all virtual machines observed based on 24 hours of historical data.
vCPU %	The average vCPU usage of this virtual machine as a percentage of all virtual machines' total vCPU usage based on 24 hours of historical data.
Memory %	The average active memory used by this virtual machine as a percentage of all virtual machines' total active memory usage based on 1 hour of historical data.
Peak vCPU %	The maximum observed vCPU usage of this virtual machine based on 24 hours of historical data reported as a percentage where 100% equals a single vCPU core. Notes: 200% would be the equivalent of two vCPU cores being saturated.
Peak vCPU (GHz)	The maximum observed vCPU usage of this virtual machine based on 24 hours of historical data reported in CPU clock cycles measured in GHz.
Average vCPU %	The average observed vCPU usage of this virtual machine based on 24 hours of historical data reported as a percentage where 100% equals a single vCPU core. Notes: 200% would be the equivalent of two vCPU cores being saturated for the entire 24 hours.
Average vCPU (GHz)	The average observed vCPU usage of this virtual machine based on 24 hours of historical data reported in CPU clock cycles measured in GHz.
Peak Memory %	The maximum active memory usage observed for this virtual machine based on 1 hour of historical data reported as a percentage of the memory provisioned for this virtual machine. Notes: 100% would indicate that at one point during the hour, all of the provisioned memory for this virtual machine was in use. Active memory is an estimation calculated by the ESXi host of how much memory is currently being actively used by the guest virtual machine. We recommend that this active memory is used for sizing purposes.
Peak Memory (MB)	The maximum active memory usage observed for this virtual machine based on 1 hour of historical data reported in megabytes. Active memory is an estimation calculated by the ESXi host of how much memory is currently being actively used by the guest virtual machine. We recommend that this active memory is used for sizing purposes.
Avg Memory %	The average active memory usage observed for this virtual machine based on 1 hour of historical data reported as a percentage of the memory provisioned for this virtual machine. Notes: 100% would indicate that for the entire hour, all of the provisioned memory for this virtual machine was in use. Active memory is an estimation calculated by the ESXi host of how much memory is currently being actively used by the guest virtual machine. We recommend that this active memory is used for sizing purposes.
Avg Memory (MB)	The average active memory usage observed for this virtual machine based on 1 hour of historical data reported in megabytes. Active memory is an estimation calculated by the ESXi host of how much memory is currently being actively used by the guest virtual machine. We recommend that this active memory is used for sizing purposes.
Peak IOPS	The maximum observed combined read and write IOPS to and from the virtual disks connected to this virtual machine based on 1 hour of historical data. Notes: Since this IOPS data is only based on one hour of data, we do not recommend that it be used for sizing purposes.
Average IOPS	The average combined read and write IOPS to and from the virtual disks connected to this virtual machine based on 1 hour of historical data. Notes: Since this IOPS data is only based on one hour of data, we do not recommend that it be used for sizing purposes.
Avg. Read/Write Ratio	The average read and write mix to and from the virtual disks connected to this virtual machine based on 1 hour of historical data. Notes: Since this read/write mix is based only on one hour of data, we do not recommend that it be used for sizing purposes.
Peak Throughput MB/s	The maximum observed combined read and write data rate measured in megabytes per second from this virtual machine based on 24 hours of historical data.
Avg. Throughput MB/sec	The average observed combined read and write data rate measured in megabytes per second from this virtual machine based on 24 hours of historical data.
Peak Read Latency	The maximum read latency for this virtual machine observed measured in milliseconds based on 1 hour of historical data. Notes: Since this metric is based only on one hour of data, we do not recommend that it be used for sizing purposes.
Peak Write Latency	The maximum write latency for this virtual machine observed measured in milliseconds based on 1 hour of historical data. Notes: Since this metric is based only on one hour of data, we do not recommend that it be used for sizing purposes.
Avg. Read Latency	The average read latency for this virtual machine observed measured in milliseconds based on 1 hour of historical data. Notes: Since this metric is based only on one hour of data, we do not recommend that it be used for sizing purposes.
Avg. Write Latency	The average write latency for this virtual machine observed measured in milliseconds based on 1 hour of historical data. Notes: Since this metric is based only on one hour of data, we do not recommend that it be used for sizing purposes.
Peak Latency	The maximum observed latency for any read or write operation based on 24 hours of historical data.

Applications

This worksheet lists the VMware software licenses for each ESXi host in the project.

Column	Description
Server Name	The name of the ESXi host.
Software Title	The name of the VMware license that has been installed on this ESXi host.
OS	The operating system version installed on this ESXi host.