Chat now with support
Chat with Support

Foglight for Infrastructure 5.9.5 - Infrastructure Utilities Release Notes

Resolved Issues and Enhancements

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.3 does not include any fixes or enhancements.

Foglight Net Monitor Resolved Issues

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

Defect ID

Resolved Issue

IC-4121

There was no data showing in the Devices Management dashboard if a NetMonitor agent was not associated with a remoteClient.

Foglight for PowerVM Resolved Issues

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

 


Known Issues

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

Third Party Known Issues

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

 


Upgrade and Compatibility

Upgrade and Compatibility

The latest versions of the Foglight Infrastructure Utilities are:

  • Foglight Web Monitor 5.9.3
  • Foglight Net Monitor 5.9.4
  • Foglight for PowerVM 5.9.4

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.3 can co-exist with legacy Cartridge for Operating System 5.5.4. If you have the Cartridge for Operating System 5.5.4 installed:

  •  You can install Foglight Web Monitor 5.9.3 as you would install a new cartridge. For complete instructions, see “Installing Foglight cartridges” in the Administration and Configuration Help.
  •  If you accidentally install Foglight Web Monitor 5.6.10, both the Cartridge for Operating System 5.5.4 and Foglight Web Monitor 5.6.10 will be broken. This issue is fixed in the Foglight Web Monitor 5.6.11 and later versions of this product.

 

To upgrade Foglight Web Monitor to version 5.9.3: 

  1. Deactivate any existing WebMonitorAgent instances.
  2. Install the WebMonitor-5_9_3.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.4:

  1. Deactivate any existing NetMonitorAgent instances.
  2. Install the NetMonitor-5_9_4.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.4:

  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.4 (Infrastructure-5_9_4.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_4.car file, the following cartridges are added to the Cartridge Inventory:
    • HostAgents 5.9.4
    • Infrastructure 5.9.4
    • Infrastructure-IntelliProfile 5.9.4
    • Infrastructure-PowerVMAddons 5.9.4
  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.

 


Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating