サポートと今すぐチャット
サポートとのチャット

Foglight for VMware 5.7.7 - Release Notes

Resolved issues and enhancements

Resolved issues and enhancements

This 5.7.7 release of the Foglight for VMware accompanies the 8.8.5 release of Foglight for Virtualization, Enterprise Edition. It includes fixes for  the following issues.

Defect ID Description
VM-6363 Virtual Machine performance report
VM-6364  Create a standard report that will return uptime availability for monitored devices on Foglight
VM-6365 Retrieve VM OS name from config.guestFullName
VM-6366  Add disable option for History event collection
VM-6367 Make the history event collection cancelable
VM-6368 Change the VMware Performance agent to support Fglam HA
VM-6369 Change the agent package name of VMware Performance agent
VM-6370 Save the state of change events to ASP instead of store to disk
VM-6371 Save the state of history data collection to ASP instead of store to disk
VM-6374 Carry on with submitting disk utilization metrics when NPE occurs due to incorrect affinity rule
VM-6378  VM dashboard "VM Count by Top 5 Alarms" has duplicated VMs when calculate VM counts
VM-6380 There is no I/O Distribution on ESX host -> Storage tab
VM-6381   IndexOutOfBoundsException when calculate VMWVirtualMachineHostCPUs, totalHz
VM-6384 Rule VMW Agent Data Updates cannot effect for Performance collection
VM-6385 Add snapshot type files to VM->files
VM-6390 Unit conversion is incorrect for Disk Growth Rate of Virtual Machines Utilization report
VM-6391 CPU utilization in summary and monitoring dashboard should keep consistent
VM-6396 ClassCastException if the VM backing a virtual disk using a raw device mapping
VM-6362 Duplicate templates for VM creation and deletion report
VM-6372 VMware car should not reference this function from Perspectives
VM-6373 There has a script error for VM Performance Score
VM-6375 VMware should not reference the Virtual Switch icon from Hyper-V Cart

Known issues

Known issues

The following is a list of issues known to exist at the time of this release.

Defect ID

Known Issue

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
VFOG-6727

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:

  1. Locate the following entry in the <fglam_home>/jre/lib/security/java.security file: 

    jdk.certpath.disabledAlgorithms=MD2, RSA keySize < 1024

  2. Modify it as follows: 

    jdk.certpath.disabledAlgorithms=MD2, RSA keySize < 512

  3. Deactivate and activate the VMware Performance Agent.
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.
Workaround: Using the Data Management dashboard, navigate to VMware Model > Virtual Centers, and delete the Virtual Center host that no longer collects data.

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.

Management Server dashboards

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.

 


Third party known issues

Third party known issues

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.
For more information, visit: http://pubs.vmware.com/vsphere-60/index.jsp?topic=%2Fcom.vmware.wssdk.apiref.doc%2Fvim.host.VsanInternalSystem.html

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:
https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2052917

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:
http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2119264
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.
Workaround: Since NICs are connected physically, they receive broadcast messages, which results in the display of data transmission rates rate for these NICs. However there is no actual loss of data transmit. To prevent this data from appearing, physically remove such NICs.

VFOG-8486

The total command latency is collected for monitored datastores, but cannot be collected for NFS (network file system) storage.
Workaround: The total command latency is based on disk-based calculations, and is only available for a disk/LUN that uses SCSI commands. Not all types of datastores are disk-based (NFS for example is not), and sometimes a disk can create multiple datastores. As an alternative, the datastore total latency metric can be used.

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
VFOG-5438

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
throughput.usage.vmotion
throughput.usage.ft
throughput.usage.iscsi
throughput.usage.nfs
throughput.usage.hbr

On ESXi version 4.1 network usage counters are not available, so this feature is not supported.
ESXi versions 5.0 and 5.1 includes network usage counters, and they can be configured as required.
The counters were removed from ESXi versions 5.5, 5.5.0a, and 5.5.0b, so traffic type utilization metrics are not collected.

For more information, see the following article: http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2083590.

 


Upgrade and compatibility

Upgrade and compatibility

Foglight for Virtualization EE 8.8 includes a new version of Foglight for VMware 5.7.7. This new version of Foglight for VMware provides new capabilities to Foglight for Virtualization EE.

Foglight for VMware supports VMware vSphere and VMware vCenter Server versions 5.x and 6.x.

Important: The VMware Performance Agent uses a Virtual Center account to log in to the monitored Virtual Center. The administrative role associated with that account must be granted the Performance > Modify intervals privilege. When collecting traffic-type network metrics from the monitored ESX hosts, this privilege enables the VMware Performance Agent to change the performance metric counter levels in order to collect this data.

 

vCenters in Linked Mode: Linked Mode is supported, however an agent monitoring one vCenter does not gather data from other linked vCenters. Each vCenter requires its own dedicated agent.

The following version of the Cisco Nexus 1000V Switch for VMware vSphere is supported:

  • On vSphere 5.x, version 4.2(1)SV2(2.2) is supported. At the time of this release, this is the latest version of the Cisco Nexus 1000V Switch supporting vSphere 5.0, 5.1, and 5.5.

Note: The extended support for VirtualCenter 2.5 ended on May 21, 2013. Foglight for VMware is no longer tested with or supported for VirtualCenter 2.5. 

Foglight for VMware is not compatible with the VirtualCenter for VMware Server.

Important: If you install or upgrade to this version of Foglight for VMware on the Management Server (outside of the Foglight for Virtualization EE or Foglight for Storage Management product families), and you also have the Foglight for Storage Management cartridge installed on the server, you must ensure that the Foglight for Storage Management cartridge is at least version 3.1.4. Using an earlier version will prevent the Storage Management data collections and dashboards from working as expected.

The following Foglight product versions and platforms are compatible with this release.

Product Name

Product Version

Platform

Foglight Management Server 5.9.4 All platforms supported by this version of the Foglight Management Server
Foglight Agent Manager 5.9.4 All platforms supported by this version of the Foglight Agent Manager
Foglight For Virtualization, Enterprise Edition 8.8.5 All platforms supported by this version of the Foglight For Virtualization, Enterprise Edition
To upgrade to the latest version of Foglight for VMware:
  1. Deactivate all VMware Performance agent instances.
  2. On the Cartridge Inventory dashboard, install the following cartridge files. Do not remove the older version of these cartridges. Install version 5.7.7 over the older version.
    • DRP-5_7_7.car
    • Virtual-VMware-5_7_7.car
    • Virtual-VMware-Admin-5_7_7.car
  3. On the VMware Environment dashboard, on the Administration tab, update all of the existing VMware Performance agent instances.
  4. Important. If you increased the JVM memory allocation in a previous cartridge installation (as described in System Requirements), you need to repeat this process after deploying the new agent package and before activating the agents.
  5. Activate all VMware Performance agent instances.

Note: Extra minutes will be needed if you upgrade to the latest version in the environment where is deployed with more than 4,000 virtual machines.

For more information, see the Foglight Upgrade Guide.

 


関連ドキュメント

The document was helpful.

評価を選択

I easily found the information I needed.

評価を選択