Foglight® for Infrastructure 5.9.6
Developed for Foglight Management Server 5.9.6
Release Notes
December 2019
Welcome to Foglight for Infrastructure
Resolved issues and enhancements
Getting started with Foglight for Infrastructure
Foglight® for Infrastructure provides the ability to monitor an infrastructure environment and to analyze performance issues affecting various host systems. It 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.9.6 release of Foglight for Infrastructure. Review all sections before starting the installation.
For complete product information, see the Foglight for Infrastructure User and Reference Guide.
Foglight® Log Monitor is an Infrastructure utility shipped with Foglight for Infrastructure which monitors log files and identifies activities that can potentially lead to performance issues.
For complete information about Foglight Log Monitor, see the Foglight for Infrastructure User and Reference Guide.
Foglight® for PowerVM allows you to monitor IBM® PowerVM® environments. Foglight alerts you about infrastructure problems as soon as they develop, enabling you to resolve issues proactively before end users are affected. Early intervention ensures consistent application performance at established service levels. Foglight for PowerVM monitors the health of your virtual system by tracking the levels of resource utilization such as CPU, network, and memory consumption of individual objects in your integrated environment.
For complete information about Foglight for PowerVM, see the Foglight for Infrastructure User and Reference Guide.
This release contains the following new features and updates:
This release contains the following Foglight for Infrastructure new features and improvements:
This release of Foglight Log Monitor does not include any new features. It is made to accompany the 5.9.6 release of Foglight for Infrastructure.
This release of Foglight for PowerVM does not include any new features. It is made to accompany the 5.9.6 release of Foglight for Infrastructure.
The following is a list of issues addressed and enhancements implemented in this release:
The following is a list of issues addressed and enhancements implemented in this Foglight for Infrastructure release.
|
Defect ID |
Resolved Issue |
|
IC-2424 |
Fixed an issue that the Processor Queue Length chart displays incorrectly when the value is less than 1 on Solaris. |
|
IC-2521 |
Fixed an issue if the default lockbox does not exist, there will be an NPE in the IC cartridge lifecycle scripts. |
|
IC-4214 |
Fixed an issue that IC agent will submit loopback address for the FglAM host object if ipv4/ipv6 is disabled on the FglAM host. |
This release of Foglight Log Monitor does not include any fixes or enhancements. It is made to accompany the 5.9.6 release of Foglight for Infrastructure.
This release of Foglight for PowerVM does not include any fixes or enhancements. It is made to accompany the 5.9.6 release of Foglight for Infrastructure.
The following is a list of issues known to exist at the time of this release:
|
Defect ID |
Known Issue |
|
IC-4275 |
Some metrics (bytes read/written, reads/writes) cannot be collected for ZFS disk. |
|
IC-4047 |
The "sqlserv.exe process" and "Memory Top Consumers" metrics collected by the Windows Agent are incorrect. |
|
IC-3873 |
On the All Hosts dashboard, metrics of Logical Disks are not accurate. |
|
IC-3617 |
The alarm view of the rule that was copied from the Record Severity could not be shown correctly. |
|
IC-2841 |
Half of processors (16/31) do not have Utilization metric. |
|
IC-2644 |
DellUnixAgent logs 'No begin line' when configured to monitor Solaris® on
Foglight Agent Manager 5.8.1. |
|
IC-2370 |
On the Infrastructure Environment dashboard, Uptime always displays "Not Available" for Solaris® zones. |
|
IC-2058 |
Different cpu usage between Top CPU Consumers table and "topas" output on command line. |
|
IC-1684 |
Network metrics may be unavailable when monitoring Solaris® LDOMs. |
|
IC-1572 |
UnixAgent generates the
Workaround: This is a basic attribute of Java® processes that use a large amount of memory on Solaris®. The workarounds are either to reduce the amount of memory used by FglAM (perhaps by moving agents to other FglAM instances) or by increasing the swap space available to the Solaris® system. The root problem is described in the following Oracle® report: JDK-5049299 : (process) Use posix_spawn, not fork, on S10 to avoid swap exhaustion. Please note that the fix for this issue provided in this report is only for Solaris 10 and later). This is generally only an issue for agents monitoring the local system, but can also occur when agents run on the system in question, but are monitoring a remote system. They may still need to execute commands on the host system. |
|
IC-1478 |
The Linux® data collector incorrectly identifies HP Smart Array physical disk as a logical disk. |
|
IC-1440 |
Research if HP-UX agent might submit incorrect value for run queue length: includes active processes not just queued. |
|
IC-1439 |
The Linux® agent submits incorrect value for run queue length; it includes active processes and not all blocked processes. |
|
IC-1304 |
When parsing |
|
IC-1253 |
Replace or augment the Event Log rule with a multi-severity rule. |
|
IC-1163 |
When a UnixAgent monitors an AIX® system remotely, the remote monitor running quest_perfstat.bin fails with a timeout, and the following message is logged:
|
|
IC-1103 |
LinuxCollector on local host:
|
|
IC-1097 |
Network(receiveRate, sendRate, transferRate, utilization) can not be collected successfully while use non-native collector for AIX®, HP-UX agents. |
|
IC-1093 |
The WindowsAgent does not remove invalid characters in log data before transmitting it. |
|
IC-1049 |
While monitoring AIX® or HP-UX with the native collector, changing the user name of the credential used for monitoring generates an error related to the quest_perfstat.bin file. Workaround: Before making changes to the credential, stop data collection on any AIX or HP-UX agent that are currently using those credentials. Failing to stop data collection causes the collector to generate an error indicating that it cannot execute a binary in the remote host's tmp directory. To enable the agent to resume data collection, delete the offending binary from the remote host machine. |
|
IC-904 |
Mounted ISOs not reliably detected as read only. |
|
IC-851 |
Selecting a severity level on a tile in the Infrastructure Environment dashboard 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. Workaround: If you leave the Infrastructure Environment dashboard and return, the filters are updated. |
|
IC-811 |
The user installing or upgrading a cartridge will sometimes get an error when accessing views installed with the cartridge. This only happens if users go from the Cartridge Inventory dashboard directly to a Dashboard of the newly installed or updated cartridge (for example, the Infrastructure Environment dashboard does not render on first access after an upgrade). Workaround: Refreshing the browser can often correct this problem. If this doesn't solve the problem, logging out and logging back in will clear the issue. |
|
IC-747 |
Output from interactive shell during an SSH connection may cause errors when parsing command execution results. |
|
IC-561 |
All Foglight for Infrastructure agents use the collection interval to calculate rate metrics. This is incorrect because a stop/start triggers a recollection before the interval expires. |
|
Defect ID |
Known Issue |
|
IC-3617 |
Custom rules (which are copied from existing cartridge rules) will drop some tables or charts that exist in the original Alarm dialog. Contact Quest Support for workaround. |
|
IC-2529 |
Foglight Log Monitor does not support the AIX® and
Solaris® (SPARC®) platform with Foglight for Infrastructure 5.8.1. |
|
IC-1901 |
The Log Monitor page does not auto-refresh on Foglight Management Server
version 5.6.5 to 5.6.10. |
|
Defect ID |
Known Issue |
|
AGENT-3716 |
PowerVMVirtualManager is not submitted when the PowerVM agent is running in an upgraded environment. For more details, see Troubleshooting Foglight for PowerVM. |
|
AGENT-3232 |
The metrics in pop-up view of the dependency node should use the specific dependency time range, not the system time range. |
|
AGENT-3218 |
The "PowerVM VIOS State Inspect" alarm does not display in the alarm table as expected when using a Firefox® 18.0 browser. The "PowerVM Server Connect State" alarm has been cleared, but the warning icon of the specific server still exists when using a Firefox 18.0 browser. |
The following is a list of third party issues known to exist at the time of this release.
|
Defect ID |
Known Issue |
|
FDOC-4057 |
Collecting Logical Disk metrics from Windows Vista®,
Windows Server® 2008, and Windows Server 2008 R2 may be affected by a
Microsoft® defect. |
|
FDOC-2771 |
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. |
|
IC-2856 |
Some Windows® processes report very large memory for virtual bytes performance counters (these are products marked with the large address space awareness flag, including Chkdsk.exe and Lsass.exe). The value is reported as such by Microsoft Windows on some 64-bit systems. This is a known 3rd-party issue; the values reported are as expected. |
|
IC-594 |
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® Web site, at http://support.microsoft.com/kb/961435/en-us. |
|
Defect ID |
Known Issue |
|
FDOC-6474 |
Foglight for Infrastructure native AIX collector running on AIX® 6.1 hosts without "6100-07-04 Service Pack 04" may incorrectly report network metrics and utilization being collected. This issue has been acknowledged by IBM®: IV11918: PERFSTAT EXTENSION RETURNS STALE NETWORK/INTERFACE METRICS. APPLIES TO AIX 6100-07. Workaround: A hotfix, IV11918, is available in various service packs and technology level packs. More information about the fix is available here: http://www-01.ibm.com/support/docview.wss?uid=isg1fixinfo134504. |
For upgrade and compatibility information, see the following sections:
The latest version of Foglight for Infrastructure is 5.9.6.
Note: Foglight for Infrastructure is order-dependent. Therefore, the Agent Manager must be updated on the Management Server before you install Foglight for Infrastructure.
Note: Some content in Foglight 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 Foglight for Infrastructure.
The following is a list of product versions and platforms compatible with this Foglight for Infrastructure release.
|
Product Name |
Product Version |
Platform |
|
Foglight Management Server |
5.9.2 or later |
All platforms supported by this version of the Foglight Management Server |
|
Foglight Agent Manager Note: All monitoring agents available in this version of Foglight for Infrastructure support the Agent Manager HA failover mode. For more information about this mode, see the Agent Manager Guide. |
5.8.0 or later |
All platforms supported by this version of the Foglight Agent Manager |
To upgrade Foglight for Infrastructure to version 5.9.6:
The following is a list of product versions and platforms compatible with this Foglight for PowerVM release.
|
Product Name |
Product Version |
Platform |
|
Foglight Management Server |
5.7.5 and later |
All platforms supported by this version of the Foglight Management Server. |
|
Foglight Agent Manager Note: The monitoring agents
available in this version of Foglight for PowerVM support the Agent
Manager HA failover mode. |
5.8.0 and later |
All platforms supported by this version of the Foglight Agent Manager. |
To upgrade Foglight for PowerVM to version 5.9.6:
def topSrv = server.TopologyService;
def type =
topSrv.getType("PowerVMVirtualManager");
def stringType =
type.getProperty("longName").getValueType();
if(type.findProperty("host")){
def shell =
topSrv.beginUpdate(type);
shell.addProperty("hmcName", null,
stringType, false, false, false, "default", null);
topSrv.endUpdate(shell);
def objects =
#!PowerVMVirtualManager#.topologyObjects;
if(objects){
def shells = []
objects.each{object ->
def objShell = topSrv.getObjectShell(object);
objShell.set("hmcName", object.host.name);
topSrv.mergeData(objShell);
}
}
def tmp = topSrv.beginUpdate(type);
tmp.removeProperty("hmcName");
topSrv.endUpdate(tmp);
topSrv.addProperty(type , "hmcName", null, "String", false,
false, true, null);
tmp = topSrv.beginUpdate(type);
tmp.removeProperty("host");
tmp.removeProperty("virtualManagerHostName");
topSrv.endUpdate(tmp);
} def topSrv = server.TopologyService;
def type =
topSrv.getType("PowerVMVirtualManager");
if(type.findProperty("host")){
tmp = topSrv.beginUpdate(type);
tmp.removeProperty("host");
tmp.removeProperty("virtualManagerHostName");
topSrv.endUpdate(tmp);
}
Foglight for Infrastructure 5.9.6 must be installed on a running Foglight Management Server 5.9.2 (or later). Foglight Agent Manager 5.9.2 (or later) 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.
Foglight for Infrastructure 5.9.6 is supported on the same platforms as Foglight Agent Manager 5.9.2.
|
Operating System |
Version |
Architecture |
|
CentOS™ Linux® |
5.x 7.x 8.x |
IA-32 |
| x86_64 | ||
HP-UX |
11i v2 11i v3 |
Itanium™ |
| IBM® AIX® |
6.1 7.1 7.2 |
POWER |
| Microsoft® Windows® |
Windows Vista® (SP1 or above) 7 (Professional or above) 8 (Pro, Enterprise) 8.1 10 Note: For WinRM connections on Windows Vista, Service Pack 1 (SP1) or later must be installed. |
IA-32 |
| x86_64 | ||
|
Windows Server® 2008 |
IA-32 | |
| x86_64 | ||
|
Windows Server 2008 R2 |
x86_64 | |
| Novell® SUSE® Linux® Enterprise Server |
10 11 12 13 |
IA-32 |
| x86_64 | ||
|
Oracle® Linux® |
5.x 6.x 7.x 8.x |
IA-32 |
| x86_64 | ||
|
Oracle Solaris® |
10 (including Zones) Note: See Quest Support Policies on our support portal for important information on using Foglight in virtual environments. |
x86_64 |
| SPARC® | ||
|
11 (including Zones) Note: See Quest Support Policies on our support portal for important information on using Foglight in virtual environments. |
x86_64 | |
| SPARC | ||
|
Red Hat® Enterprise Linux® |
AP/Server 5.x 6.x 7.x 8.x |
IA-32 |
| x86_64 | ||
|
Ubuntu® Linux® |
12.04.x LTS 14.04.x LTS 16.04.x LTS 18.04.x LTS |
x86_64 |
The following agents are available with this cartridge:
Foglight® for PowerVM supports IBM® Power Systems™ servers based on POWER5, POWER6, POWER7, and POWER8 processors.
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:
Symptom:
When Foglight Management Server is upgraded from version 5.7.5.x to 5.7.5.3, the server reports the error "Object being merged of type PowerVMVirtualManager has incomplete identity: PowerVMVirtualManager.host". The PowerVMVirtualManager and PowerVMVirtualCenter are not submitted successfully, and the UI does not display the data for the HMC domain.
Resolution:
Use the following commands to edit the PowerVMVirtualManager:
def topSrv = server.TopologyService;
def type = topSrv.getType("PowerVMVirtualManager");
tmp = topSrv.beginUpdate(type);
tmp.removeProperty("host");
topSrv.endUpdate(tmp);
Foglight includes a licensing capability that restricts access to those features that are defined in the license. All Management Server installations require a license that grants access to server-specific parts of the browser interface and the features associated with them.
Foglight for Infrastructure is covered by the base Foglight license.
To activate a trial or a purchased commercial license:
The Foglight for Infrastructure release package contains the following:
Foglight for Infrastructure, Foglight Log Monitor, and Foglight for PowerVM are distributed in the Infrastructure-5_9_6.car file. Use the Administration > Cartridges > Cartridge Inventory dashboard to install this cartridge file. For full installation instructions, refer to the topic "Installing Foglight cartridges" in the Foglight Administration and Configuration Help.
Note: Foglight for Infrastructure is order-dependent. Therefore, the Agent Manager must be updated on the Management Server before you install Foglight for Infrastructure.
Product: |
Installing this file: |
Adds these cartridges to Cartridge Inventory: |
Adds these components to Components for Download: |
|
Foglight for Infrastructure |
Infrastructure-5_9_6.car |
HostAgents 5.9.6 Infrastructure 5.9.6 Infrastructure-IntelliProfile 5.9.6 Infrastructure-PowerVMAddons 5.9.6 |
WinRM GPO Setting Against AD script 1.0.0 |
Caution: If Foglight for Infrastructure is already installed on the Management Server, there is no need to re-install it. Check Cartridge Inventory to see if this file is already installed. For complete information about Foglight for Infrastructure, see Foglight for Infrastructure User and Reference Guide. |
|||
Foglight Log Monitor only. On the Log Monitor dashboard, create File Log Monitor and Windows Event Log Monitor agent instances using the available wizards. For instructions, see the Foglight for Infrastructure User and Reference 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: The cartridge is enabled for Global Operations, but not localized to any particular locale.
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 www.quest.com/contact.
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.