The following is a list of issues addressed and enhancements implemented in this Foglight for VMWare release.
Issue ID |
Resolved Issue |
Domain |
FOG-4557 |
Improved performance of VMWare environment top VMs dashboard |
VMWare |
FOG-3932 |
Tag collection for VMWare is now optional |
VMWare |
This 6.3.0 release of Foglight for VMWare includes the following known issues at the time of this release.
Defect ID |
Known Issue |
VM-6572 |
There are no VMware tags services displayed on the Foglight Management Server with FIPS-compliant mode enabled. |
VFOG-11752 |
The Virtual Machines Network Performance - Service report is missing units when exported as an Microsoft Excel spreadsheet. |
VFOG-11219 |
Too many vCenter sessions are detected, due to the agents not disconnecting properly when done. This leaves many idle sessions on the vCenter. |
VFOG-10849 |
When forwarded, the vSphere Alarm Virtual machine CPU usage displays null values. |
VFOG-10796 |
vCenter alarms are not collected by default. To enable their collection, set the Alarms Collection Enabled property of the VMware Performance Agent to True. |
VFOG-10217 |
A number of Warning messages are found in the log, indicating a big time difference between the monitored vCenter and Management Server. |
VFOG-10171 |
Incorrect virtual CPU ratio values are found in custom reports. |
VFOG-9390 |
The table on the Top CPU Consuming Virtual Machines view cannot be sorted. |
VFOG-9067 |
VMware cartridge creates duplicate VMware Performance agents with the ID -1. |
VFOG-9042 |
The vCenter Certificate's public key length has to be 1024-bits or higher and could not use MD5. This is because vCenters are configured to use a 512-bit long certificate keys. The Foglight Agent Manager JRE is updated to version 1.7.0.40 (1.7u40) or higher, which restricts the certificate key length to 1024 bits or higher. Workaround:
|
VFOG-6302 |
The IP address of ESX host cannot be collected and presented in the dashboard. |
VFOG-8973 |
If there are multiple virtual machines with the same name running in different virtual centers, their performance data may be incorrect. |
VFOG-8515 |
Upgrading to Foglight for Virtualization, Enterprise Edition 8.0 causes the Virtual Environment Overview tiles to show zero objects. Workaround: Update the VMware Performance agent on the VMware Environment Administration tab, as instructed. For upgrade instructions, see Upgrade and Compatibility. |
VFOG-3421 |
When the IP or host name of the monitoring host changes, this results in two Virtual Center instances, one that collects data, and another that does not. |
VFOG-2198 |
After exporting the CPU Utilization graph to Excel, incorrect labels appear in the resulting file. |
N/A |
For large virtual infrastructure environments, the performance of the browser interface can be affected by the amount of memory allocated to the Java Virtual Machine (JVM) on the Management Server. |
Defect ID |
Known Issue |
VFOG-9887 |
On the All Hosts dashboard, accessible by clicking Homes > Hosts in the browser interface, Disk Current and Network Current columns for any ESX hosts or virtual machines show "n/a" instead of the actual metric values. This behavior does not apply to physical hosts collecting OS metric data. This table shows disk and network utilization percentages for ESX hosts or virtual machines which are not collected by Foglight for VMware. Hovering over these columns shows the related disk and network throughputs, which appear in units other than percentages. Workaround: There is no workaround available for this issue. |
This 6.3.0 release of Foglight for VMWare includes the following known issues at the time of this release.
Defect ID |
Known Issue |
VM-6572 |
There are no VMware tags services displayed on the Foglight Management Server with FIPS-compliant mode enabled. |
VFOG-11752 |
The Virtual Machines Network Performance - Service report is missing units when exported as an Microsoft Excel spreadsheet. |
VFOG-11219 |
Too many vCenter sessions are detected, due to the agents not disconnecting properly when done. This leaves many idle sessions on the vCenter. |
VFOG-10849 |
When forwarded, the vSphere Alarm Virtual machine CPU usage displays null values. |
VFOG-10796 |
vCenter alarms are not collected by default. To enable their collection, set the Alarms Collection Enabled property of the VMware Performance Agent to True. |
VFOG-10217 |
A number of Warning messages are found in the log, indicating a big time difference between the monitored vCenter and Management Server. |
VFOG-10171 |
Incorrect virtual CPU ratio values are found in custom reports. |
VFOG-9390 |
The table on the Top CPU Consuming Virtual Machines view cannot be sorted. |
VFOG-9067 |
VMware cartridge creates duplicate VMware Performance agents with the ID -1. |
VFOG-9042 |
The vCenter Certificate's public key length has to be 1024-bits or higher and could not use MD5. This is because vCenters are configured to use a 512-bit long certificate keys. The Foglight Agent Manager JRE is updated to version 1.7.0.40 (1.7u40) or higher, which restricts the certificate key length to 1024 bits or higher. Workaround:
|
VFOG-6302 |
The IP address of ESX host cannot be collected and presented in the dashboard. |
VFOG-8973 |
If there are multiple virtual machines with the same name running in different virtual centers, their performance data may be incorrect. |
VFOG-8515 |
Upgrading to Foglight for Virtualization, Enterprise Edition 8.0 causes the Virtual Environment Overview tiles to show zero objects. Workaround: Update the VMware Performance agent on the VMware Environment Administration tab, as instructed. For upgrade instructions, see Upgrade and Compatibility. |
VFOG-3421 |
When the IP or host name of the monitoring host changes, this results in two Virtual Center instances, one that collects data, and another that does not. |
VFOG-2198 |
After exporting the CPU Utilization graph to Excel, incorrect labels appear in the resulting file. |
N/A |
For large virtual infrastructure environments, the performance of the browser interface can be affected by the amount of memory allocated to the Java Virtual Machine (JVM) on the Management Server. |
Defect ID |
Known Issue |
VFOG-9887 |
On the All Hosts dashboard, accessible by clicking Homes > Hosts in the browser interface, Disk Current and Network Current columns for any ESX hosts or virtual machines show "n/a" instead of the actual metric values. This behavior does not apply to physical hosts collecting OS metric data. This table shows disk and network utilization percentages for ESX hosts or virtual machines which are not collected by Foglight for VMware. Hovering over these columns shows the related disk and network throughputs, which appear in units other than percentages. Workaround: There is no workaround available for this issue. |
The following is an issue known to exist at the time of this release.
Defect ID |
Known Issue |
VFOG-11632 |
Performance metrics cannot be collected for VSAN 5.5 because of its limited API. Workaround: Upgrade to VSAN version 6.0. |
VFOG-11599 |
A known issue in vCenter 5.1, 5.5 and 6.0 leads to wrong packet loss values, causing the VMW Virtual Machine Packet Loss rule alarms to be triggered. For more information, visit: Workaround: If you monitor version 5.1/5.5, install the latest patch. At the moment, there is no solution for version 6.0. |
VFOG-10311 |
If a monitored VM is using a vmxnet3 adapter, networking data cannot be collected. This is a known issue in vCenter 6. For more information, visit: |
VFOG-10301 |
The VM Network Performance data was lost when moving a virtual machine between vCenters. |
VFOG-9632 |
The VMware Explorer displays logical disk information for RHEL 6 virtual machines, but not for RHEL 7 virtual machines. This is due to the limitation of the default open-vm-tools version 9.4.0, included with RHEL 7 and CentOS 7, which does not support the XFS file system. |
VFOG-8579 |
vSwitch topology views display incorrect utilization and packet loss values, showing data for unused and standby NICs. |
VFOG-8486 |
The total command latency is collected for monitored datastores, but cannot be collected for NFS (network file system) storage. |
VFOG-8455 |
The virtual machine guest OS boot time is only collected in vCenter 5 or higher. |
VFOG-8278 |
Cluster CPU utilization is currently calculated using Hypervisor CPU usage. vCenter calculates the same values using only the available memory for virtual machines. |
VFOG-5139 |
Collection of traffic type utilization metrics is only possible if vCenter network usage counters are available and configured properly. These metrics illustrate how different types of data traffic are represented in the overall network traffic managed by a virtual switch. In a default installation network usage counters (listed below) are set to 3. To enable the collection of traffic type utilization metrics, each of these counters must be set to 1: throughput.usage.vm On ESXi version 4.1 network usage counters are not available, so this feature is not supported. For more information, see the following article: http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2083590. |
© ALL RIGHTS RESERVED. Feedback Termini di utilizzo Privacy Cookie Preference Center