Foglight® for Hyper-V 5.7.5

Developed for Foglight Management Server 5.9.2 / Foglight for Virtualization, Enterprise Edition 8.7.5

Release Notes

January 2018


Contents

Welcome to Foglight for Hyper-V

New in this release

Resolved issues and enhancements

Known issues

Upgrade and compatibility

System requirements

Product licensing

Getting started with Foglight for Hyper-V

About Us


Welcome to Foglight for Hyper-V

Foglight for Hyper-V allows you to monitor the health of your Hyper-V virtual infrastructure by tracking resource consumption such as CPU, network, and memory consumption for individual clusters, servers and virtual machines in your integrated environment.

These Release Notes cover the features, system requirements, and other important information about the 5.7.5 release of Foglight for Hyper-V. Review all sections before starting installation.

 


New in this release

This 5.7.5 release of Foglight for Hyper-V accompanies the release of Foglight for Virtualization, Enterprise Edition 8.7.5.

 

This release includes the following new features and improvements:

 


Resolved issues and enhancements

The following is a list of issues addressed and enhancements implemented in this release.

Defect ID

Resolved Issue

HV-1785

An error message was displayed on the Hyper-V Explorer dashboard if the ActionPack-Microsoft-HyperV cartridge was not installed.

HV-1764

Under the Hyper-V Administration > Rule Configuration dashboard, all rules are showing "Errors Check Logs" in the Severities columns.

HV-1773

Fixed issue where data collection was failed if the identity property "vMId" for SCVVM was empty.

VFOG-13170

Fixed the automation workflow issue for Hyper-V virtual machines running on Microsoft Windows Server 2012 R2.

 


Known issues

The following is a list of issues known to exist at the time of Foglight for Hyper-V release.

Defect ID

Known Issue

HV-1770 Due to permission issue, the Move operation will fail for virtual machines running on the Windows 2012 R2 Server and Windows 2016.
HV-1707 If a VHD file is deployed on SMB, its parent information cannot be collected.
HV-1273 If a VM is deployed on SMB share, its disk capacity cannot be collected.
VFOG-12141 The Virtual Switch Topology View does not display any data on the Federation Master.
VFOG-11608 Only powered on virtual machines are displayed on the virtual switch views in the Quick-View.
VFOG-8801

When a virtual machine running on a Windows 2008 R2, Windows 2012 or Windows 2012 R2 Hyper-V server creates a snapshot without shutdown, the virtual machine's disk I/O metrics are not collected.

Workaround: Restart the virtual machine.

VFOG-8550

If a virtual machine's disk is stored on an SMB (Server Message Block) share, disk I/O metrics are not collected.

HV-196

On the Hosts dashboard, the virtual machine disk and network utilization metrics are not populated. This happens because these metrics appear as percent values while the cartridge collects these values using different units.

Workaround: There is no workaround available for this issue.

 


Upgrade and compatibility

Foglight for Virtualization EE 8.7.5 includes a new version of Foglight for Hyper-V 5.7.5.

Each monitored server must be running Microsoft Windows Server 2008 R2, Windows Server 2012, or Windows Server 2012 R2. For complete information about the upgrade procedure, see the Foglight Upgrade Guide.

When upgrading from version 5.7.4 or earlier (included with Foglight for Virtualization 8.7 or earlier, or Foglight 5.6.7 or earlier), Hyper-V Agents are automatically transitioned to use credential management. This transition requires that all agents be upgraded through the Hyper-V Environment Administration tab.

Using other methods to upgrade Hyper-V Agents results in agents without configured credentials and requires additional configuration before collections can resume.

The following is a list of Foglight product versions and platforms compatible with this release.

Product Name

Product Version

Platform

Foglight Management Server 5.9.2 All platforms supported by this version of the Foglight Management Server
Foglight Agent Manager 5.9.2 All platforms supported by this version of the Foglight Agent Manager
Foglight For Virtualization, Enterprise Edition 8.7
8.7.5
All platforms supported by these versions of the Foglight For Virtualization, Enterprise Edition
To upgrade to the latest version of Foglight for Hyper-V:
  1. Deactivate all Hyper-V/SCVMM/SOFS 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.5 over the older version.
  3. To enable System Center Virtual Machine Manager (SCVMM) monitoring, install the SCVMM-5_7_5.car file.
  4. On the Hyper-V Environment dashboard, on the Administration tab, update all of the existing agent instances.
  5. Activate all agent instances.

For more information, see the Foglight Upgrade Guide.

 


System requirements

Before installing Foglight for Hyper-V, ensure your system meets the following minimum hardware and software requirements:

Operating System

Foglight for Hyper-V can be installed on any supported Foglight Management Server configuration.

Monitored Hyper-V servers must be running on Microsoft Windows Server 2008 R2, Windows Server 2012, Windows Server 2012 R2, or Windows 2016.

Monitored SOFS servers must be running on Microsoft Windows Server 2012 R2.

Monitored SCVMM servers must be SCVMM 2012 or SCVMM 2012 R2.

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 Hyper-V Management Capabilities guide.

Hyper-V Agent and Agent Manager configuration

On 64-bit hosts meeting the minimum system requirements, the embedded Agent Manager can be used to run Hyper-V 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.

Foglight Hyper-V Agent host system requirements

  Minimum CPU Minimum Memory Minimum Host Memory Total Monitored VMs
Windows 64-bit

2*

2 GB

4 GB

500

Linux 64-bit

2*

2 GB

4 GB

500

* Additional CPUs may be required for larger environments.

Deploying more than 10 Hyper-V agents

The following calculations are guidelines for setting the amount of connections required for the Agent Manager.

Note: The following sample is for the calculation of Hyper-V agents only. If there are additional agents to be monitored by the Agent Manager in your environment, update the existing connection quantity to add this number that is required for the Hyper-V agents.

To change the JVM settings:
  1. Determine the amount of connections required for the Agent Manager. Each agent requires 15 connections. For example, if 12 agents are deployed in the Agent Manager, the amount of required connections is 15 x 12 =180.
  2. On the agent machine, open the baseline.jvmargs.config file for editing. The file is located in the <Agent_Manager_home>/state/default/config directory.
  3. Configure the pool size by adding the following lines in the Settings section:

    vmparameter.0 = "-Dcom.quest.connection.regulator.percentAvailableConnectionsThreshold=40"
    vmparameter.1 = "-Dcom.quest.connection.regulator.maxActiveConnectionsCap=300"


    The pool size will be maxActiveConnectionsCap multiplies the value subtracted percentAvailableConnectionsThreshold from 100%. In the sample above, this is 300 x (100-40)% = 180 connections.

    Note: If this file has been previously edited, increase the numeric parameters accordingly.
  4. Delete the existing deployed negotiation configuration settings directory:

    <Agent_Manager_home>/state/default/config/deployments
  5. Restart the Agent Manager for these settings to take effect.

Monitoring more than 4000 virtual machines from a single agent host

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 Hyper-V Servers that will be monitored from all Hyper-V 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 Hyper-V agents are calculated using the following formula:

512 MB + 0.5 MB x VM#

According to the above formula, monitoring 4000 virtual machines requires 2560 MB of memory:

512 MB + 2048 MB = 2560 MB

The default setting for agents deployed on 64-bit systems is 2560 MB, which suffice this environment.

Similarly, monitoring 8192 virtual machines requires 4608 MB of memory:

512 MB + 4096 MB = 4608 MB

This requires the default Agent Manager settings to be changed.

To change the JVM memory settings:
  1. Determine the amount of additional memory required. This will be the total from the last step above minus the default value of 2560 MB. In the sample above, this is 4608 – 2560 = 2048 MB.
  2. On the agent machine, open the baseline.jvmargs.config file for editing. The file is located in the <Agent_Manager_home>/state/default/config directory.
  3. Add the following lines in the Memory Settings section:

    vmparameter.2 = "-Xms2048m";
    vmparameter.3 = "-Xmx2048m";


    Note: If this file has been previously edited, increment the numeric parameters accordingly.
  4. Delete the existing deployed negotiation configuration settings directory:

    <Agent_Manager_home>/state/default/config/deployments
  5. Restart the Agent Manager for these settings to take effect.
Host system recommendations
Dedication

When monitoring larger Hyper-V environments, the Agent Manager machine hosting the Hyper-V 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.

Memory

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 Hyper-V 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

Or:

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

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

2 CPUs

1000 – 4000 VMs

4 CPUs

4000+ VMs

add 1 CPU per 1000 VMs – round up when necessary

 

When the Agent Manager and Hyper-V 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 Hyper-V dashboards.

Foglight Management Server minimum memory requirements

# of virtual machines Memory* Foglight JVM settings
1000

Xms|Xmx=4G

2500 Xms|Xmx=9G
5000 Xms|Xmx=17G
10000 Xms|Xmx=32G
20000 Xms|Xmx=62G

* 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.

 


Product licensing

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 Foglight for Infrastructure), others may require an additional license.

Foglight for Hyper-V is covered by the Foglight for Virtualization, Enterprise Edition license. A separate additional license is required for installation in the base Foglight product.

To activate a trial or a purchased commercial license:

  1. On the navigation panel, under Dashboards, click Administration > Setup > Manage Licenses.
  2. Click Install.
  3. In the Install License dialog box, click Browse.
  4. In the file browser that appears, specify the location of the license file.
  5. In the Install License dialog box, click Install License.

 


 

Getting started with Foglight for Hyper-V

Contents of the release package

The Foglight for Hyper-V release package contains the following:

  1. Cartridge files: Note: Some of the Foglight for Hyper-V browser interface elements are defined in the DRP-5_7_5.car, SCVMM-5_7_5.car and Virtual-HyperV-Admin-5_7_5.car files. All of the available CAR files need to be installed on the Management Server.
  2. Product Documentation, including:

Installation instructions

Foglight for Virtualization EE 8.7.5 includes a new version of Foglight for Hyper-V 5.7.5. This new version of Foglight for Hyper-V is installed with Foglight for Virtualization EE 8.7.5.

To install the cartridge files and deploy agents:
  1. Navigate to the Cartridge Inventory dashboard, and install the following cartridge files:
  2. To enable System Center Virtual Machine Manager (SCVMM) monitoring, install the SCVMM-5_7_5.car file.
  3. On the Hyper-V Environment dashboard, open the Administration tab.
  4. On the Agents area, click Hyper-V Agents, SCVMM Agents, or SOFS Agents, and then click Add.
  5. Follow the Agent Setup wizard to create and deploy Hyper-V agent, SCVMM agent, or SOFS agent instances, as required.

After installing all of the cartridge files, the following cartridges appear on the list of installed cartridges:

For more information, see the Foglight for Hyper-V Installation Guide.

Configuration prerequisites

  1. Privileges of Monitor Account for Hyper-V® or SOFS Agent:
  2. Privileges of Monitor Account for SCVMM Agent (Hyper-V® environments):
  3. Privileges of Hyper-V Optimizer (Hyper-V® environments):

Additional resources

Additional information is available from the following:

Globalization

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.

 


About Us

We are more than just a name

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 brand, our vision. Together.

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.

Contacting Quest

For sales or other inquiries, visit www.quest.com/contact.

Technical support resources

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:

 


Copyright© 2018 Quest Software Inc.

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.