Quest® Foglight® Cartridge for Infrastructure 5.6.5

Developed for Foglight Management Server 5.6.3

Release Notes

October 2012 


Welcome to Foglight Cartridge for Infrastructure

New in this Release

Resolved Issues and Enhancements

Known Issues

Third Party Known Issues

Upgrade and Compatibility

System Requirements

Global Operations

Getting Started


For More Information


Welcome to Foglight Cartridge for Infrastructure

The Foglight Cartridge for Infrastructure provides the ability to monitor an infrastructure environment and to analyze performance issues affecting various host systems. The cartridge provides system agents for local and remote monitoring of Windows and UNIX (including Linux) hosts. The cartridge can be used - by itself - to monitor physical hosts, or - in combination with other agents - to monitor virtual hosts. The cartridge provides a service-based dashboard for easy monitoring and for quick access to relevant frequently-asked questions.

These Release Notes cover the resolved issues, known issues, workarounds, and other important information about the 5.6.5 release of the Cartridge for Infrastructure. Review all sections before starting the installation.


New in this Release

This release contains the following new features:

Multiple Hosts Wizard

This new wizard allows you to quickly start monitoring multiple hosts. The wizard is accessible from the Infrastructure Environment dashboard by clicking Multiple Hosts. Start by selecting the Agent Manager and the hosts you want to monitor. You have an option of selecting existing unmonitored hosts, or add new hosts by providing their IP address. If any of the hosts you intend to monitor are referenced by a different name in your environment, you can override it in this step.

Next, specify the credentials needed to access the hosts you want to monitor. Credentials store the security data that the monitoring agent needs to access the monitored system. At this point you can choose not to configure a credential (you can configure one later), create a new credential, or use an existing one. For complete information about this flow, see "Adding a Monitored Host" in the Managing the Infrastructure Cartridge User and Reference Guide.

As a last step in the wizard, you can review the hosts you are about to start monitoring, the Agent Manager used to manage the monitoring agents, and the credentials needed to access the monitored systems.


Resolved Issues and Enhancements

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

Defect ID

Resolved Issue


Solaris agents no longer require sudo access.


The Hosts report is modified to report the “period average” utilization values for the selected time range. Previously it reported the utilization values from the end of the selected time range.


The Memory and Disk Utilization rules now use a modified behavior setting, where they only fire if four of five evaluations are true. This intends to reduce the frequency of alarms and of the corresponding email notifications.


Infrastructure rules are changed to limit their scope to physical hosts. In particular, this eliminates an undesirable interaction with the virtualization cartridges, where multiple cartridges evaluate the same data and could cause multiple alarms.


Metrics that depended on polling period could be inflated due to slow collection times.


Preliminary support for Windows Server 2012 is added to the Agent Manager, version Testing of Windows Server 2012 monitoring with the WindowsAgent has uncovered no issues. Testing of this environment is ongoing, and formal support will be added in an upcoming release.


A new property is available in the UnixAgent properties to override the location of sudo (default is /usr/bin/sudo) if it is installed in an alternate location on the monitored system.
The sudo executable is typically found in /usr/bin; however, some systems use a different location. The UnixAgent has a new agent property that allows you to specify the location of the sudo executable. This property is only used if use sudo is enabled. Note: This is an advanced property, as such it is not exposed in the Add OS Monitor wizard.


If the Virtual/Guest check box is selected on the first page of the Add OS Monitor Wizard, all Collect metrics check boxes on the second page are cleared. These values are more accurately collected by the virtualization cartridges.


The IntelliProfile features are added for the key utilization metrics. Baseline envelopes now display on the charts in the Infrastructure Environment Quick View after running IntelliProfile for long enough, to have calculated the baseline values (24 hours, by default).


Memory reported for Windows hosts is now addressable memory, instead of installed memory.


The AIX command-line process information attempted to parse <defunct> as a number.


If a volume group is inactive, the UnixAgent does not query it for further information.


Several Infrastructure FAQts had incorrect sort orders or other defects. These are now corrected.


Trailing spaces from Services are now removed and added to "Services to Monitor".


In Infrastructure releases prior to 5.6.5, several rules had an email action associated with the normal condition. In the Cartridge for Infrastructure 5.6.5, the email action associated with the Normal condition is removed.

If any of the affected rules had been edited locally, that can cause Foglight to send blank emails after the Infrastructure cartridge is upgraded.

The workaround is to use the Rule Editor to manually delete the email action for the Normal severity.


Memory metrics for memory capped non-global zones running in Solaris 10u7 and later were miscalculated.

Memory metrics for Solaris 10u6 and earlier now report memory capacity, consumed, and utilization values for the global zone, regardless of whether monitoring a global or local zone.

Memory metrics for Solaris 10u7 and later now report memory capacity, consumed, and utilization values for each zone, respecting memory and swap caps (for virtual memory).


When using the native collector to monitor AIX hosts, the VirtualMemorySize metric was reported incorrectly, inflating the value by the amount of physical memory present on the host.


The VirtualMemorySize metric reported when using the non-native collector has changed. It used to report the Active Memory Pages statistic from the vmstat utility; it now reports the sum of physical memory (from vmstat) and total paging space (from lsps).


The sudoers config file required NOPASSWD access to /usr/bin/find and /bin/cat in earlier versions of the Cartridge for Infrastructure when collecting data from Linux systems with sudo.

The entries can be further restricted in this release by replacing them with following (for the foglight user):

foglight ALL = NOPASSWD: /usr/bin/find /proc -maxdepth 2 -regex ^/proc/\[0-9\]\*/io$ -exec /bin/echo *, /bin/cat /proc/*/io

Note: The ethtool and mii-tool entries are still required, and were not changed. If either tool is present on the host you want to monitor (check in /sbin or /usr/sbin), include them in the sudoers file for the appropriate user.


A new UnixAgent property Include filesystems mounted from memory is added to allow Foglight to display Solaris partitions using the "swap" file system type (essentially RAM disks) as logical disks.

Note: This is an advanced property, as such it is not exposed in the Add OS Monitor wizard.


Bandwidth/utilization metrics are no longer available on loopback interfaces. They are removed because the values reported by Windows were not reliable.


If a host has no current data for one of the top five tables on the Infrastructure Environment dashboard, it no longer appears in the table.


Email notifications are not longer sent when an Infrastructure alarm clears.


The Solaris' run queue length metric value is now calculated properly.


The fixed value for the interrupts threshold on Windows was too low, making it difficult to collect the interrupt metrics and generate alarms. The Interrupts rule is updated in this release to make use of the IntelliProfile thresholds, to improve the metric collection and alarm generation.

Note: This is a new feature.


Selecting a host from the top 5 tables of the Infrastructure Environment view now drills down to the detailed view for the selected host, as if clicking the Explore button on that host's Quick View.


The Interrupts rule appended an unnecessary percentage sign to the Subject line of the alarm email.


Network data collection on Windows XP-based systems could fail with an IndexOutOfBounds exception.


A new UnixAgent property Include filesystems mounted from memory is added, to allow Foglight to collect loopback and RAM logical disk metrics. Previous versions of the Cartridge for Infrastructure always collected this data. This data is now only collected if the property is set to True. Note that this is a behavior change, designed to remove extraneous data, and while correct, it is not relevant for most systems.

Note: This is an advanced property, and as such it is not exposed in the Add OS Monitor wizard.


In the 5.6.4 version of the cartridge, certain metrics were only collected if the use sudo option was set in the UnixAgent properties. This option was required even if logging in to the host with root credentials. If running in this mode, you had to make sure that sudo was permitted to allow root users to run it.

In this release, the use sudo property can be set to enable collection of additional metrics that depend on commands requiring run permissions higher than those of a default user. The commands vary by platform. For more information, see the Managing the Infrastructure Cartridge User and Reference Guide.

Also in this release, if monitoring a host using root credentials (or an account with sufficiently elevated permissions), the use sudo property does not have to be set to enable collection of these additional metrics.


If monitoring an AIX WPAR (Workload Partition), many metrics are missing. This is because interfaces/commands within a WPAR have limited permissions, so they are unable to report data required. CPU metrics, swap space, network interface characteristics (such as network mask and MAC address), as well as physical and logical disk metrics are affected.


The Windows EventLog running on a virtual machine used to contain events logged at startup using GMT, resulting in invalid future timestamps, discarded by the StaleDataFilter.


When collecting process information, the Solaris agent no longer requires the use of /bin/sh with sudo access.


This cartridge version includes the ability to create agents from a list of hosts. A new wizard can be accessed from the Infrastructure Environment page.


Known Issues

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

Defect ID

Known Issue


If a rule is configured to use an Alarm Association, when it fires an alarm viewing, that alarm will use the New Alarm Detail Dialog. If the rule also generates an email, or if a service configured to send emails is triggered by the alarm, the generated email will have a URL that should link back to the New Alarm Detail Dialog.

In the 5.6.3 release of Foglight there is bug in the handling of this URL which causes the user to be directed to an error page instead of the New Alarm Detail Dialog. This bug had been fixed in 5.6.4. Rules that do not have Alarm Associations will generate emails that correctly bring the user to the Old Alarm Detail Dialog and should be unaffected by this bug.

Workaround: This issue is resolved by upgrading Foglight Management Server to version 5.6.4.


In an environment that has a mixture of legacy OS Cartridge agents and Infrastructure agents, both cartridges' rules are active on the server. This results in some overlap in the rules monitoring the data from these agents.

The Infrastructure cartridge rules fire on data collected by the OS Cartridge agents. Because the OS Cartridge agents are not scoped on Host objects, but simulated Foglight 4 tables, the OS agents are not displayed as the Monitoring Agent for alarms fired by the Infrastructure rules. This manifests as an "n/a" in the Agent column on the Alarms dashboard and in other places where these alarms are displayed. This is the expected behavior, given the differences in how the OS Cartridge agents and the Infrastructure agents data is modeled.

Workaround: This issue is best resolved by migrating to all Infrastructure Cartridge agents.


If you select a severity level on a tile in the Infrastructure Environment dashboard, it filters the list of hosts to only that severity. If a host's severity level changes, the host remains in the list even if you refresh the page. If you leave the Infrastructure Environment dashboard and return, the filters are updated.


Having the Show Lockboxes currently assigned to each client check box selected in the View Clients dashboard can cause several dashboards to take a long time to respond.
Workaround: Clear this check box. It is a diagnostic control which should not be enabled for normal operation.


In order to function correctly, the native collector for the HP-UX agent requires the installation of the patch fileset PHKL_22987.

To determine whether this patch is installed on an HP-UX machine, run the following command:

/usr/sbin/swlist -l fileset | grep PHKL_22987


Certain disk rate statistics for logical disks are not collected for AIX 5.3. This is a limitation of the AIX 5.3 operating system.


Support for monitoring Veritas clusters is currently unavailable. It will be added in a future release.


The Top IO Processes metric is unavailable for HP-UX systems.

Devices (such as filesystems) in HP-UX can be configured with different block sizes. However, the data available for processes only includes the number of blocks read and written. Without knowing where those read/writes occurred, it is not possible to calculate how much data was transferred.

The IO rates are used in determining the top IO consuming processes, therefore this feature is unavailable for HP-UX machines.

The block read/write rates are recorded for each process.


Certain physical disk metrics (spaceAvailable, spaceUsed, totalSpace, capacityUsed, and capacityAvailable) are neither collected nor displayed.


Support for monitoring Microsoft clusters is currently unavailable. It will be added in a future release.

Third Party Known Issues

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

Windows-Related Issues

Defect ID

Known Issue


Collecting Logical Disk metrics from Windows Vista, Windows Server 2008, and Windows Server 2008 R2 may be affected by a Microsoft defect.

Workaround: A hotfix is available on the Microsoft's Web site, at


In order for the WindowsAgent to have access to query WMI to collect OS and database metrics, the agent must have permission to access both DCOM and WMI.

On Windows Server 2003, only users in the Local Administrators group on the monitored host have the required permissions.


Some base values are not updated when using the Win32_PerfRawData_PerfDisk_LogicalDisk WMI class to calculate performance data in Windows Vista or in Windows Server 2008, because this class does not contain the PercentDiskTime_Base metric.

Workaround: A hotfix is available on Microsoft's Web site, at


Upgrade and Compatibility

The latest version of the Cartridge for Infrastructure is version 5.6.5.

The Cartridge for Infrastructure 5.6.5 requires Foglight Management Server 5.6.3 or later.

To upgrade the Cartridge for Infrastructure to the latest version, install version 5.6.5 of the cartridge as you would install a new Cartridge for Infrastructure. Do not delete the older version of the .car file. Install version 5.6.5 over the older version. For installation instructions, refer to the topic "Installing Foglight Cartridges" in the Foglight Administration and Configuration Help.

Note: Some content in the Cartridge for Infrastructure supersedes that of the Cartridge for Operating Systems. However, no upgrade path is provided for replacing an existing Cartridge for Operating System with the Cartridge for Infrastructure.


The WindowsAgent that was released with Infrastructure cartridge version 5.6.2 contained a defect whereby data for ALL Windows services was erroneously collected in the default case. That is, if "defaultServices" was selected, the 5.6.2 WindowsAgent collected data for ALL Windows services, instead of just those that were selected for monitoring.

Infrastructure cartridge version 5.6.3 introduced a HostService rule that raises an alarm and sends an email whenever a monitored service stops running. Due to a defect in the 5.6.2 WindowsAgent, data was collected by that agent for services that were not selected for monitoring. To prevent the generation of unwanted HostService alarms when upgrading the Infrastructure cartridge from version 5.6.2, the HostService rule does not operate on data collected by the 5.6.2 WindowsAgents. To make use of the HostService rule, you must upgrade the WindowsAgents to version 5.6.3 or later, by deploying the updated HostAgents.gar from this release to each Agent Manager which manages WindowsAgents.


System Requirements

The Cartridge for Infrastructure must be installed on a running Foglight Management Server 5.6.3 or later. Foglight Agent Manager must be installed on all the hosts that you want to use for local or remote monitoring. To learn about the system requirements for these components, refer to the Foglight System Requirements and Platform Support Guide.


The Cartridge for Infrastructure 5.6.5 is supported on the same platforms as Foglight Agent Manager, except as follows: Windows 2000 is not supported.

Operating System




CentOS Linux 5.x
x86 32-bit
x86_64 32-bit; 64-bit
HP-UX 11i v1 PA-RISC 32-bit; 64-bit
11i v2

11i v3

PA-RISC 32-bit; 64-bit
Itanium 64-bit



Note: The AIX support requires the recommended patch levels from IBM. For example, AIX 5.3 should be patched to at least TL9 SP1.

POWER 32-bit; 64-bit
Microsoft Windows XP (SP3)

Vista (SP1 or above)

7 (Professional or above)

Note: For WinRM connections on Windows Vista, Service Pack 1 (SP1) or later must be installed.

x86 32-bit
x86_64 32-bit; 64-bit
Server 2003
Server 2008
x86 32-bit
x86_64 32-bit; 64-bit
Itanium 64-bit
Server 2008 R2 x86_64 64-bit
Novell SUSE Linux Enterprise Server 9



x86 32-bit
x86_64 32-bit; 64-bit
Oracle Linux 4.x



x86 32-bit
x86_64 32-bit; 64-bit
Oracle Solaris 8


SPARC 32-bit; 64-bit
10 (including Zones)

Note: See Quest Support Policy on Virtualization on our support portal for important information on using Foglight in virtual environments.

x86_64 64-bit
SPARC 32-bit; 64-bit
11 (including Zones)

Note: See Quest Support Policy on Virtualization on our support portal for important information on using Foglight in virtual environments.

Red Hat Enterprise Linux AS/ES 4.x

AP/Server 5.x


x86 32-bit
x86_64 32-bit; 64-bit
Ubuntu Linux 11.10 x86_64 64-bit


The following agents are available with this cartridge:


Global Operations

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: The cartridge is enabled for Global Operations, but not localized to any particular locale.


Getting Started

Contents of the Release Package

The Cartridge for Infrastructure release package contains the following:

  1. Foglight Cartridge for Infrastructure 5.6.5 files:
  2. Product Documentation, including:

Installation Instructions

The Cartridge for Infrastructure is distributed as a .car file: Use the Administration > Cartridges > Cartridge Inventory dashboard to install the cartridge. For full installation instructions, refer to the topic "Installing Foglight Cartridges" in the Foglight Administration and Configuration Help.



This section provides a list of references which address the most commonly faced issues relating to remote connectivity, allowing for easy troubleshooting using the vendor's information knowledgebase or Foglight documentation:


For More Information

Get the latest product information, find helpful resources, test the product betas, and join a discussion with the Foglight Quest team and other community members. Join the Foglight Community at


Contacting Quest Software:

Mail Quest Software, Inc.
World Headquarters
5 Polaris Way
Aliso Viejo, CA 92656

Refer to our Web site for regional and international office information.

Contacting Quest Support:

Quest Support is available to customers who have a trial version of a Quest product or who have purchased a Quest product and have a valid maintenance contract. Quest Support provides unlimited 24x7 access to our Support Portal at

From our Support Portal, you can do the following:

View the Global Support Guide for a detailed explanation of support programs, online services, contact information, policies, and procedures.
The guide is available at


© 2012 Quest Software, Inc. ALL RIGHTS RESERVED.


This document contains proprietary information protected by copyright. The software described in this guide is furnished under a software license or nondisclosure agreement. This software may be used or copied only in accordance with the terms of the applicable agreement. No part of this guide may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying and recording for any purpose other than the purchaser’s personal use without the written permission of Quest Software, Inc.


If you have any questions regarding your potential use of this material, contact:

Quest Software World Headquarters
5 Polaris Way
Aliso Viejo, CA 92656


Refer to our Web site for regional and international office information.



Quest, Quest Software, the Quest Software logo, Foglight, IntelliProfile, PerformaSure, Spotlight, StealthCollect, TOAD, Tag and Follow, Vintela Single Sign-on for Java, and vFoglight are trademarks and registered trademarks of Quest Software, Inc in the United States of America and other countries. For a complete list of Quest Software's trademarks, please see Other trademarks and registered trademarks are property of their respective owners.


Third Party Contributions

Foglight contains some third party components. For a complete list, see the License Credits page in Foglight online help.



The information in this document is provided in connection with Quest products. No license, express or implied, by estoppel or otherwise, to any intellectual property right is granted by this document or in connection with the sale of Quest products. EXCEPT AS SET FORTH IN QUEST'S TERMS AND CONDITIONS AS SPECIFIED IN THE LICENSE AGREEMENT FOR THIS PRODUCT, QUEST ASSUMES NO LIABILITY WHATSOEVER AND DISCLAIMS ANY EXPRESS, IMPLIED OR STATUTORY WARRANTY RELATING TO ITS PRODUCTS INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT. IN NO EVENT SHALL QUEST BE LIABLE FOR ANY DIRECT, INDIRECT, CONSEQUENTIAL, PUNITIVE, SPECIAL OR INCIDENTAL DAMAGES (INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF PROFITS, BUSINESS INTERRUPTION OR LOSS OF INFORMATION) ARISING OUT OF THE USE OR INABILITY TO USE THIS DOCUMENT, EVEN IF QUEST HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. Quest makes no representations or warranties with respect to the accuracy or completeness of the contents of this document and reserves the right to make changes to specifications and product descriptions at any time without notice. Quest does not make any commitment to update the information contained in this document.