Foglight® Infrastructure Utilities

Foglight® Web Monitor 5.9.2
Foglight® Net Monitor 5.9.2
Foglight® for PowerVM 5.9.2

Developed for Foglight Management Server 5.9.2

Release Notes

December 2017


Contents

Welcome to Foglight Infrastructure Utilities

New in this Release

Resolved Issues and Enhancements

Known Issues

Third Party Known Issues

Upgrade and Compatibility

System Requirements

Troubleshooting

Product Licensing

Getting Started with Foglight Infrastructure Utilities

About Us

 


Welcome to Foglight Infrastructure Utilities

Foglight Infrastructure Utilities consists of the following components:

These Release Notes cover the resolved issues, known issues, workarounds and other important information about the Foglight Infrastructure Utilities.

Note: As of these release notes, the most current version of Foglight Infrastructure Utilities are:

Review all sections before starting the installation.

Foglight Log Monitor

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.

Note: For more information about Foglight Log Monitor including known and resolved issues, see the Foglight for Infrastructure Release Notes and Foglight for Infrastructure User and Reference Guide.

 


New in this Release

This release contains the following  new features and updates:

Foglight Web Monitor New Features

Foglight Web Monitor 5.9.2 introduces the following new feature: 

Foglight Net Monitor New Features

Foglight Net Monitor 5.9.2 does not include any new features.

Foglight for PowerVM New Features

Foglight for PowerVM 5.9.2 does not include any new features.

 


Resolved Issues and Enhancements

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

Foglight Web Monitor Resolved Issues

This release of Foglight Web Monitor 5.9.2 includes the following fixes or enhancements:

Defect ID

Resolved Issue

IC-3745 The ConcurrentModificationException occurs when loading the webmonitor performance dashboard.

IC-3702

Fixed issue where Proxy authentication required was not selected by default, after upgrading Foglight Web Monitor from 5.6.10 to 5.8.5.7.

IC-2979

Fixed the view rendering issue on the WebMonitor dashboard.

IC-2968

Old EUTransaction or EUWebMonitorTransactionMetrics objects sill show up under the Service Builder dashboard, even if the transaction has been deleted.

Foglight Net Monitor Resolved Issues

This release of Foglight Net Monitor 5.9.2 includes the following fixes or enhancements:

Defect ID

Resolved Issue

IC-3874

Fixed issue where the NetMonitor Performance Browser dashboard could not be loaded due to ConcurrentModificationException.

IC-3297

F5NetMonitorAgent on the Script Console dashboard missed some properties, including agentname, type, and agentversion.

 

Foglight for PowerVM Resolved Issues

This release of Foglight for PowerVM 5.9.2 does not include any fixes or enhancements.

 


Known Issues

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

Foglight Web Monitor Known Issues

The following is a list of Foglight Web Monitor issues known to exist at the time of this Foglight Infrastructure Utilities release.

Defect ID

Known Issue

IC-3361 "Deployed Locations" changed frequently if user sets several different "Agent Location Alias Name" for the same location.

IC-3043

Registry Value of Synthetic_Transaction_Sample_Period, Aggregation rule and collection interval should match.

AGENT-3050

Further performance improvement with 6000+ URL - Transactions Domain.

AGENT-3036

Issue with Overall Response Time bar.

Foglight Net Monitor Known Issues

The following is a list of Foglight Net Monitor issues known to exist at the time of this Foglight Infrastructure Utilities release.

Defect ID

Known Issue

IC-3768 The value of DeviceNameOverride cannot be displayed in the Alarms table, if user sets a value for the DeviceNameOverride field.

IC-3013

Duplicate "Monitor Location" values displaying on Single Device Summary on HA primary FMS.

AGENT-3345

Redesign the Net Monitor reports.

AGENT-3258

It is not suitable to limit the packet size to larger than 40 bytes in UI, should find another better way.

AGENT-3122

Add the ability to select existing hosts, monitored by other agents.

AGENT-2852

The Single Location Summary page times out when a high number of devices is monitored by a single location.

Workaround: You can monitor a maximum of 3,000 devices from a single location. Each device should be monitored from one location only.

AGENT-2747

On SUSE® Linux® 10 or lower version [os command icmp] TraceRoute failed with java.lang.Exception: Stack Trace.

AGENT-2700

Devices belonging to different LANs, with the same IP address but having different network IDs, are merged into the same Device Wrapper object.

Workaround: Provide different override names for the merged network devices.

AGENT-2658

The Net Monitor Agent does not support monitoring devices through a Round Robin DNS or DDNS name.

Workaround: Do not use a Round Robin DNS or DDNS name as a device name.

AGENT-2531

The response time, availability, and packet loss data are not consistent during the first time range period when the agents begin data collection. After the first time range period (four hours by default), the collected data becomes accurate.

Workaround: Upgrade the Management Server to a version later than 5.6.11 (when available).

AGENT-2449

Specifying an IP address as the target device name in the Net Monitor Agent Properties requires the agent to resolve the DNS name using the provided IP address. In some environments this result in a failure when the reverse DNS entry for a device is not configured properly.

Workaround: Ensure that both forward and reverse DNS entries for the specified host are configured. If this does not work, use the device DNS name as the Device name override agent property value.

AGENT-2446

Two network device entries in the Net Monitor Agent properties pointing to the same device do not trigger the Duplicated monitor on same IP Device rule. This is because one entry points to the device using the host name, while the other uses the IP address.

Workaround: There is no workaround for this issue.

AGENT-2108

NetMonitor agent doesn't support IPv6 IP address.

 

Foglight for PowerVM Known Issues

The following is a list of Foglight for PowerVM issues known to exist at the time of this Foglight Infrastructure Utilities release.

 

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-3679

IBM® HMC Console events log takes too long to open, while the PowerVM agent is executing too many commands.

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.

 

 


Third Party Known Issues

There are no known third-party issues specific to this release of Foglight Infrastructure Utilities.

 


Upgrade and Compatibility

The latest versions of the Foglight Infrastructure Utilities are:

For upgrade and compatibility information for these utilities, see the following sections:

Compatibility Information for Foglight Web Monitor

The following is a list of product versions and platforms compatible with this Foglight Web Monitor 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

5.7.0 and later

All platforms supported by this version of the Foglight Agent Manager.

Note: Foglight Agent Manager 5.7.0 or later must be installed on all the hosts that you want to use for local or remote monitoring.

Compatibility Information for Foglight Net Monitor

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

Product Name

Product Version

Platform

Foglight Management Server

5.6.5 and later

All platforms supported by this version of the Foglight Management Server.

Foglight Agent Manager

5.7.0 and later

All platforms supported by this version of the Foglight Agent Manager.

Note: Foglight Agent Manager 5.7.0 or later must be installed on all the hosts that you want to use for local or remote monitoring.

Compatibility Information for Foglight for PowerVM

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. For more information about this mode, see the Agent Manager Guide.

5.8.5 and later

All platforms supported by this version of the Foglight Agent Manager.

Note: Foglight Agent Manager 5.8.5 or later must be installed on all the hosts that you want to use for local or remote monitoring.

Upgrading Foglight Web Monitor

Foglight Web Monitor 5.9.2 can co-exist with legacy Cartridge for Operating System 5.5.4. If you have the Cartridge for Operating System 5.5.4 installed:

 

To upgrade Foglight Web Monitor to version 5.9.2: 

  1. Deactivate any existing WebMonitorAgent instances.
  2. Install the WebMonitor-5_9_2.car file on the Management Server as you would install a new version of Foglight Web Monitor.

    Do not uninstall or delete the previous version.

    For complete instructions, see "Installing Foglight cartridges" in the Administration and Configuration Help.

  3. Deploy the Web Monitor Agent package to each Agent Manager that hosts one or more Web Monitor Agent instances.

    For complete instructions, see "Deploying agent packages to monitored hosts" in the Administration and Configuration help.

  4. Activate the WebMonitorAgent instances.

Note: If you are monitoring URLs which need a proxy and proxy authentication, you will need to set the property 'enableProxyAuth' to 'true' to ensure there are no errors. If you do not set the property 'enableProxyAuth' to true, the monitored URLs will report a 407 error. For more details, see NTLM Proxy Authentication with Java Runtime Environment version 7.

Upgrading Foglight Net Monitor

To upgrade Foglight Net Monitor to version 5.9.2:

  1. Deactivate any existing NetMonitorAgent instances.
  2. Install the NetMonitor-5_9_2.car file on the Management Server as you would install a new version of Foglight Net Monitor.

    Do not uninstall or delete the previous version.

    For complete instructions, see "Installing Foglight cartridges" in the Administration and Configuration Help.

  3. Deploy the Net Monitor Agent package to each Agent Manager that hosts one or more Net Monitor Agent instances.

    For complete instructions, see "Deploying agent packages to monitored hosts" in the Administration and Configuration help.

  4. Activate the NetMonitorAgent instances.

Upgrading Foglight for PowerVM

To upgrade Foglight for PowerVM to version 5.9.2:

  1. Deactivate any existing PowerVM Agent instances.
  2. Run the following script:
    def stringType = type.getProperty("longName").type;
    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);
  3. Install Foglight for Infrastructure version 5.9.2 (Infrastructure-5_9_2.car) on the Management Server as you would install any new cartridge. Do not uninstall or delete the previous version of this file. For complete instructions, see "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. 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.
    When installing the Infrastructure-5_9_2.car file, the following cartridges are added to the Cartridge Inventory:
  4. Run the following script:
    def topSrv = server.TopologyService;
    def type = topSrv.getType("PowerVMVirtualManager");
    tmp = topSrv.beginUpdate(type);
    tmp.removeProperty("host");
    tmp.removeProperty("virtualManagerHostName");
    topSrv.endUpdate(tmp);
  5. Activate the PowerVM Agent instances and start data collection.

 


System Requirements

Before installing Foglight Infrastructure Utilities, ensure your system meets the following minimum hardware and software requirements:

Operating System

Foglight Infrastructure Utilities 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.

 

NTLM Proxy Authentication with Java Runtime Environment version 7

To support NTLM authentication, the Java Runtime Environment (JRE) used by Foglight Agent Manager must be version 7 or later.

 

Foglight Agent Manager 5.8.0 and later include JRE 7. Foglight 5.7.1 includes Foglight Agent Manager 5.8.1.

 

Versions of Foglight Agent Manager earlier than 5.8.0 ship with JRE version 6. If you need to run Web Monitor on a version of Foglight Agent Manager earlier than 5.8.0, you must:

Foglight for PowerVM

Foglight® for PowerVM supports IBM® Power Systems™ servers based on POWER5, POWER6, POWER7, and POWER8 processors.

 


Troubleshooting

This section provides information about problems that you might encounter while monitoring your environment with Foglight Infrastructure Utilities:

Troubleshooting Foglight Web Monitor

Symptom:

You cannot delete stale transactions directly from the Performance Browser dashboard Quick View.

Resolution:

For information on how to remove stale transactions from the Performance Browser dashboard, see "Removing stale transactions from the Performance Browser dashboard" in the Foglight Infrastructure Utilities User and Reference Guide.

Troubleshooting Foglight for PowerVM

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);

 


Product Licensing

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 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 Infrastructure Utilities are covered by the base Foglight license.

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 Infrastructure Utilities

Contents of the Release Package

The Foglight Infrastructure Utilities release package contains the following:

  1. Cartridge files: Note: Foglight for PowerVM and Foglight Log Monitor are included in the Foglight for Infrastructure cartridge file (Infrastructure-5_9_2.car). For more information, see the Foglight for Infrastructure Release Notes and Foglight for Infrastructure User and Reference Guide.
  2. Product Documentation, including:

Installation Instructions

Installation Instructions for Foglight Web Monitor and Foglight Net Monitor

To install Foglight Web Monitor and Foglight Net Monitor:

  1. Log in to the Foglight browser interface.
  2. Navigate to the Cartridge Inventory dashboard, and install the following cartridge files.
    Installing this file: Adds these cartridges to Cartridge Inventory:

    Foglight Web Monitor

    WebMonitor-5_9_2.car

    WebMonitor 5.9.2

    WebMonitorAgent 5.9.2

    WebMonitor-UI 5.9.2

    EndUserModels 5.9.8

    Foglight Net Monitor

    NetMonitor-5_9_2.car

    NetMonitor 5.9.2

    NetMonitor Agent 5.9.2

    NetMonitor-UI 5.9.2

    For more information about this step, see the Foglight Administration and Configuration Help.

  3. Navigate to the Agent Status or Agent Hosts dashboard, and deploy the following agent package files to desired hosts:

    Deploy this file:

    Foglight Web Monitor

    WebMonitorAgent.gar

    Foglight Net Monitor

    NetMonitorAgent.gar

    For more information about this step, see the Foglight Administration and Configuration Help.

  4. Configure monitoring agents.

Installation Instructions for Foglight for PowerVM

Foglight for PowerVM 5.9.2 is packaged in the Foglight for Infrastructure cartridge (Infrastructure-5_9_2.car).

To install Foglight for PowerVM:

  1. Log in to the Foglight browser interface.
  2. Use the Administration > Cartridges > Cartridge Inventory dashboard to install the Infrastructure-5_9_2.car cartridge. 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 prior to installing Foglight for Infrastructure. 

    Product:

    Installing this file:

    Adds these cartridges to Cartridge Inventory:

    Foglight for Infrastructure

    Infrastructure-5_9_2.car

    HostAgents 5.9.2

    Infrastructure 5.9.2

    Infrastructure-IntelliProfile 5.9.2

    Infrastructure-PowerVMAddons 5.9.2

    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.

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

 


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 http://quest.com/company/contact-us.aspx or call +1-949-754-8000.

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© 2017 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.