サポートと今すぐチャット
サポートとのチャット

Foglight for Infrastructure 5.9.7 - 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 for Infrastructure resolved issues

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

Defect ID

Resolved Issue

IC-2841

Fixed an issue that half of the processors (16/31) do not have utilization metric.

Foglight Log Monitor resolved issues

This release of Foglight Log Monitor does not include any fixes or enhancements. It is made to accompany the 5.9.7 release of Foglight for Infrastructure.

Foglight for PowerVM resolved issues

This release of Foglight for PowerVM does not include any fixes or enhancements. It is made to accompany the 5.9.7 release of Foglight for Infrastructure.

 


Known issues

Known issues

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

Foglight for Infrastructure known issues

 

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.
Workaround: Upgrade Foglight Agent Manager to version 5.8.5.

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 IOException: error=12, Not enough space and no data is collected.

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 df output, make sure to account for the amount of space reserved in the filesystem.

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:

... Could not process metric query command: . Error: null

IC-1103

LinuxCollector on local host: Could not process metric query command: ... Error: null.

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.

Foglight Log Monitor known issues

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.
Workaround: The Log Monitor executables, in a Foglight Agent Manager (FglAM) install, are stored in the <FglAM_home>/client/<client_version>/bin directory, based on their corresponding platform and architecture.

IC-1901

The Log Monitor page does not auto-refresh on Foglight Management Server version 5.6.5 to 5.6.10.
Workaround: Upgrade the Management Server to version 5.6.11 or later.

Foglight for PowerVM known issues

 

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.


Third party known issues

Third party known issues

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

Windows issues

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.
Workaround: A hotfix is available on Microsoft's Web site, at http://support.microsoft.com/kb/961435/en-us.

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.
On Windows Server® 2003, only users in the Local Administrators group on the monitored host have the required permissions.

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.

IBM issues

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.

 


Upgrade and compatibility

Upgrade and compatibility

For upgrade and compatibility information, see the following sections:

Upgrade and compatibility information for Foglight for Infrastructure

The latest version of Foglight for Infrastructure is 5.9.7.

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

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

Upgrade and 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.0 and later

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

 

To upgrade Foglight for PowerVM to version 5.9.7:

  1. Deactivate any existing PowerVM Agent instances.
  2. Run the following script:
    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);
    }
  3. Install Foglight for Infrastructure version 5.9.7 (Infrastructure-5_9_7.car) on the Management Server as you would install a 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_7.car file, the following cartridges are added to the Cartridge Inventory:
    • HostAgents 5.9.7
    • Infrastructure 5.9.7
    • Infrastructure-IntelliProfile 5.9.7
    • Infrastructure-PowerVMAddons 5.9.7
  4. Run the following script:
    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);
    }  
  5. Activate the PowerVM Agent instances and start data collection.

 


関連ドキュメント

The document was helpful.

評価を選択

I easily found the information I needed.

評価を選択