Foglight™ for VMware 5.7.3
Developed for Foglight Management Server 220.127.116.11 / Foglight for Virtualization, Enterprise Edition 8.6
Welcome to Foglight for VMware
New in this release
Resolved issues and enhancements
Third party known issues
Upgrade and compatibility
Getting started with Foglight for VMware
Foglight for VMware is the first monitoring solution to truly understand the virtual infrastructure and its use—providing everything from high-level infrastructure summary views to detailed, highly-visual, diagnostic architectural representations.
These Release Notes cover the resolved issues, known issues, workarounds and other important information about the 5.7.3 release of Foglight for VMware. Review all sections before starting the installation.
This 5.7.3 release of Foglight for VMware accompanies the release of Foglight for Virtualization, Enterprise Edition 8.6. This release includes the following improvements:
The following is a list of issues addressed and enhancements implemented in this release.
|VFOG-12573||Fixed property churn issue for VMWResourcePool.|
|VFOG-12371||Improved the esxcli.bat file to be compatible with the paths that contain a space|
|VFOG-10849||Removed null values from alarm messages when enabling service level alarms to be forwarded via email.|
The following is a list of issues known to exist at the time of this release.
The "Password Required but not provided" error occurs if you try to release a
password-protected lockbox by editing VMware agent properties in the VMware
Environment > Administration dashboard.
Workaround: To resolve this issue, release the password-proteced lockbox in the Administration > Credentials > Manage Lockboxes dashboard, or do not set the password for the lockbox of the VMware agent.
|VFOG-12146||A mismatch in available space metrics between what the OS and Foglight for VMware report. This issue only affects Linux hosts. The difference between these values is about 5%, which may the amount of space reserved for the super user|
|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.|
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 18.104.22.168 (1.7u40) or higher, which restricts the certificate key length to 1024 bits or higher.
|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.|
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.
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.
After exporting the CPU Utilization graph to Excel, incorrect labels appear in the resulting file.
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.
Performance metrics cannot be collected for VSAN 5.5 because of its limited API.
Workaround: Upgrade to VSAN version 6.0.
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.
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.|
vSwitch topology views display incorrect utilization and packet loss values,
showing data for unused and standby NICs.
The total command latency is collected for monitored datastores, but cannot
be collected for NFS (network file system) storage.
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.|
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:
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.
Foglight for Virtualization EE 8.6 includes a new version of Foglight for VMware 5.7.3. This new version of Foglight for VMware provides new capabilities to Foglight for Virtualization EE.
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.
Foglight for VMware supports VMware vSphere and VMware vCenter Server versions 5.x, 6.0, and 6.5.
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:
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.
|Foglight Management Server||22.214.171.124 and above||All Platforms supported by these versions of the Foglight Management Server|
|Foglight Agent Manager||126.96.36.199 and above||All Platforms supported by these versions of the Foglight Agent Manager|
|Foglight For Virtualization, Enterprise Edition||8.5.5 and above||All Platforms supported by this version of the Foglight For Virtualization, Enterprise Edition|
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.
Before installing Foglight for VMware, ensure your system meets the following minimum hardware and software requirements:
Foglight for VMware can be installed on any supported Foglight Management Server configuration.
|Platform, Memory and Hard Disk Space||The platform, memory, and hard disk space requirements for the monitored servers must match the Agent Manager requirements. For complete information, see the System Requirements and Platform Support Guide.|
Note: 32-bit Windows and Linux Agent Manager installers are not included in the Foglight for Virtualization, Enterprise Edition installer. New installations should use 64-bit Agent Managers. If you are upgrading 32-bit agent hosts, you can obtain 32-bit Agent Manager Installers from Quest Support.
For a complete list of system requirements, refer to the Installing the Virtualization Management Capabilities guide.
On 64-bit hosts meeting the minimum system requirements, the embedded Agent Manager can be used to run VMware Performance Agents to monitor up to 500 virtual machines. If the total number of virtual machines to be monitored from a single agent host is greater than 500, an Agent Manager should be installed on a separate host.
Important: Foglight for Virtualization, Enterprise Edition Virtual Appliance comes pre-configured to support up to 4,000 virtual machines. If you are using this product, there is no need to follow the configuration procedure described in this section.
If additional cartridges and agents are added to the environment, product performance should be monitored and agents moved off of the embedded Agent Manager to reduce the load.
|Minimum CPU||Minimum Memory||Total Monitored VMs|
* Additional CPUs may be required for larger environments.
The Agent Manager JVM usually requires additional memory to monitor more than 4000 virtual machines. The total number of virtual machines is the total from all vCenters that will be monitored from all VMware Performance agents running on the Agent Manager.
The following calculations are guidelines, not hard and fast rules. Memory requirements can vary greatly from installation to installation with similar VM counts. If insufficient memory is configured, the failure mode is easily recognizable: all agents on the Agent Manager host will go into a broken state after the agent(s) were activated for a short period of time, usually within 24 hours. In addition, the Agent Manager log will contain a line similar to the following:
Caused by: java.lang.OutOfMemoryError: Java heap space
If this is the case, add memory greater than what is shown in the calculations below, in increments of 512 MB until the agents stabilize.
JVM memory requirements for VMware Performance agents are calculated using the following formula:
512 MB + 0.5 MB/VM
According to the above formula, monitoring 4000 virtual machines requires 2560 MB of memory:
512 MB + 2048 MB = 2560 MB
This is the default setting for agents deployed on 64-bit systems.
Similarly, monitoring 8000 virtual machines requires 4608 MB of memory:
512 MB + 4096 MB = 4608 MB
This requires the default Agent Manager settings to be changed.
When monitoring larger vCenters, the Agent Manager machine hosting the VMware Performance agents should be dedicated to this task. No other Foglight agent types should run on the host and the host should not run any other applications.
Regardless of the values set for JVM memory above, Agent Manager never allocates more than 80% of system memory. So the machine hosting the Agent Manager and VMware Performance Agents must have sufficient memory. Beyond the memory requirements of the Agent Manager, a minimum of 2 GB should be free for the operating system. In the example above for 8000 VMs and an Agent Manager memory requirement of 4608 MB, the host should have a minimum of 6656 MB - the greater of:
1.25 x 4608 MB = 5760 MB
2048 + 4608 MB = 6656 MB
If the Foglight Agent Manager is configured on a virtual machine, it is recommended that the VM use a memory reservation to ensure maximum performance.
CPU usage on the Agent Manager host is relatively low most of the time.
However, usage peaks dramatically during the performance metric collection. This
is normal and expected. CPU utilization consistently over 50% is an indication
that additional processing power is required. As with memory, usage can vary
between different installations with similar numbers of virtual machines. The
following guidelines should be followed:
|Up to 1000 VMs||
|1000 – 4000 VMs||
add 1 CPU per 1000 VMs – round up when necessary
When the Agent Manager and VMware Performance agents are running on a virtual machine, the VM should be configured with CPU reservation whenever possible to ensure best performance. Lack of processing power on the Agent Manager manifests in missed collections and gaps in the data usually noticeable in various graphs throughout the Foglight for VMware dashboards.
|# of virtual machines||Memory*
Foglight JVM settings
* Edit the Foglight Management Server JVM settings in the server.config file located under Quest\Foglight\config\. When running Foglight on a virtual machine, full memory needs be reserved at the hypervisor level.
Foglight includes a licensing capability that restricts access to those features that are defined in the license. Any Management Server installation requires a license that grants access to server-specific parts of the browser interface and the features associated with them. Foglight cartridges are also license-protected. While some cartridges are covered by the base Foglight license (such as Foglight Agent Manager cartridges and the Foglight for Infrastructure), others may require an additional license.
Foglight for VMware is covered by the Foglight for Virtualization, Enterprise Edition license. A separate additional license is required for installation in the base Foglight product. This license covers both Foglight for VMware and Foglight for vCloud Director.
To activate a trial or a purchased commercial license:
Foglight for VMware release package contains the following:
Foglight for Virtualization EE 8.6 includes a new version of Foglight for VMware 5.7.3. This new version of Foglight for VMware is installed with Foglight for Virtualization EE 8.6. To add Foglight for VMware to an existing Foglight 5.7.5.x installation, install it as you would a new cartridge.
Important: To enable the VMware Performance Agent to monitor your virtual environment, you must grant the agent privileges for accessing the Virtual Center and collecting data from it, as described in "Granting the VMware Performance Agent Privileges to Collect Data from a Virtual Center" in the Foglight for VMware Installation Guide. However, when you create an administrative role in the Virtual Center for that purpose, in addition to the Datastore > Browse Datastores and Sessions > View and Terminate Sessions privileges, that role must also include 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. Also, any existing Virtual Center accounts that the VMware Performance Agent already uses to log in to the monitored Virtual Center must be granted the Performance > Modify intervals privilege.
After installing all of the cartridge files, the following cartridges appear on the list of installed cartridges:
For more information, see the Foglight for VMware Installation Guide.
Additional information is available from the following:
This section contains information about installing and operating this product in non-English configurations, such as those needed by customers outside of North America. This section does not replace the materials about supported platforms and configurations found elsewhere in the product documentation.
This release is Unicode-enabled and supports any character set. In this release, all product components should be configured to use the same or compatible character encodings and should be installed to use the same locale and regional options. This release is targeted to support operations in the following regions: North America, Western Europe and Latin America, Central and Eastern Europe, Far-East Asia, Japan.
This release has the following known capabilities or limitations: This release is localized for English only but supports the Unicode character set.
We are on a quest to make your information technology work harder for you. That is why we build community-driven software solutions that help you spend less time on IT administration and more time on business innovation. We help you modernize your data center, get you to the cloud quicker and provide the expertise, security and accessibility you need to grow your data-driven business. Combined with Quest’s invitation to the global community to be a part of its innovation, and our firm commitment to ensuring customer satisfaction, we continue to deliver solutions that have a real impact on our customers today and leave a legacy we are proud of. We are challenging the status quo by transforming into a new software company. And as your partner, we work tirelessly to make sure your information technology is designed for you and by you. This is our mission, and we are in this together. Welcome to a new Quest. You are invited to Join the Innovation™.
Our logo reflects our story: innovation, community and support. An important part of this story begins with the letter Q. It is a perfect circle, representing our commitment to technological precision and strength. The space in the Q itself symbolizes our need to add the missing piece — you — to the community, to the new Quest.
For sales or other inquiries, visit http://quest.com/company/contact-us.aspx or call +1-949-754-8000.
Technical support is available to Quest customers with a valid maintenance contract and customers who have trial versions. You can access the Quest Support Portal at https://support.quest.com.
The Support Portal provides self-help tools you can use to solve problems quickly and independently, 24 hours a day, 365 days a year. The Support Portal enables you to:
Quest, the Quest logo, Foglight, and Join the Innovation are trademarks and registered trademarks of Quest Software Inc. in the U.S.A. and other countries. For a complete list of Quest Software trademarks, please visit our website at www.quest.com/legal. Red Hat, JBoss, the JBoss logo, and Red Hat Enterprise Linux are registered trademarks of Red Hat, Inc. in the U.S. and other countries. CentOS is a trademark of Red Hat, Inc. in the U.S. and other countries. Fedora and the Infinity design logo are trademarks of Red Hat, Inc. Microsoft, .NET, Active Directory, Internet Explorer, Hyper-V, Office 365, SharePoint, Silverlight,SQL Server, Visual Basic, Windows, Windows Vista and Windows Server are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries. AIX, IBM, PowerPC, PowerVM, and WebSphere are trademarks of International Business Machines Corporation, registered in many jurisdictions worldwide. Java, Oracle, Oracle Solaris, PeopleSoft, Siebel, Sun, WebLogic, and ZFS are trademarks or registered trademarks of Oracle and/or its affiliates in the United States and other countries. SPARC is a registered trademark of SPARC International, Inc. in the United States and other countries. Products bearing the SPARC trademarks are based on an architecture developed by Oracle Corporation. OpenLDAP is a registered trademark of the OpenLDAP Foundation. HP is a registered trademark that belongs to HewlettPackard Development Company, L.P. Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both. MySQL is a registered trademark of MySQL AB in the United States, the European Union and other countries. Novell and eDirectory are registered trademarks of Novell, Inc., in the United States and other countries. VMware, ESX, ESXi, vSphere, vCenter, vMotion, and vCloud Director are registered trademarks or trademarks of VMware, Inc. in the United States and/or other jurisdictions. Sybase is a registered trademark of Sybase, Inc. The X Window System and UNIX are registered trademarks of The Open Group. Mozilla and Firefox are registered trademarks of the Mozilla Foundation. IOS is a registered trademark or trademark of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries. Apple, iPad, iPhone, Mac OS, Safari, Swift, and Xcode are trademarks of Apple Inc., registered in the U.S. and other countries. Ubuntu is a registered trademark of Canonical Ltd. Symantec and Veritas are trademarks or registered trademarks of Symantec Corporation or its affiliates in the U.S. and other countries. OpenSUSE, SUSE, and YAST are registered trademarks of SUSE LCC in the United States and other countries. Citrix, AppFlow, NetScaler, XenApp, and XenDesktop are trademarks of Citrix Systems, Inc. and/or one or more of its subsidiaries, and may be registered in the United States Patent and Trademark Office and in other countries. PostgreSQL is a registered trademark of the PostgreSQL Global Development Group. MariaDB is a trademark or registered trademark of MariaDB Corporation Ab in the European Union and United States of America and/or other countries. Intel, Itanium, Pentium, and Xeon are trademarks of Intel Corporation in the U.S. and/or other countries. Debian is a registered trademark of Software in the Public Interest, Inc. OpenStack is a trademark of the OpenStack Foundation. Amazon Web Services, the "Powered by Amazon Web Services" logo, and "Amazon RDS" are trademarks of Amazon.com, Inc. or its affiliates in the United States and/or other countries. Infobright, Infobright Community Edition and Infobright Enterprise Edition are trademarks of Infobright Inc. POLYCOM®, RealPresence® Collaboration Server, and RMX® are registered trademarks of Polycom, Inc.All other marks and names mentioned herein may be trademarks of their respective companies.