지금 지원 담당자와 채팅
지원 담당자와 채팅

Foglight for SQL Server 5.7.5.35 - Hotfix Release Notes

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.

 

Defect ID

Known Issue

n/a

Anti-Virus Protection tools installed on Windows® may negatively impact CPU and system performance of machines running Foglight the Agent Manager and the SQL PI repository.
To reduce resource consumption it is highly recommended that you exclude the following directories from being scanned by the Anti-Virus tools:

  • <installation directory>:\Dell\<foglight>

  • <installation directory>:\Infobright

  • <installation directory>:\Dell\<FoglightAgentManager>

n/a

WMI-related issue

Problem: WMI support is affected by the firewall

Workaround: For Windows versions prior to Windows 2008/Vista, use the following steps:

  1. Open TCP port: 135.
    WMI by default uses the port range 1024 to 5000.
  2. Open up a range of ports above port 5000.
    Port numbers below 5000 may already be in use by other applications and could cause conflicts with your DCOM applications. It is recommended to have at least 100 ports opened, as several system services rely on these RPC ports to communicate with each other.
  3. Add the registry key, including additional ports.
    • Use the RPCCfg.exe (Windows Resource Kits) by running: rpccfg.exe -pe 5009-5009 -d 0
    • Manually add the registry keys under: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Rpc\Internet

For Windows Vista® and Windows Server 2008:

According to Microsoft® http://support.microsoft.com/kb/929851, the default dynamic port range for TCP/IP has changed in these versions. The new default start port is 49152 and end port is 65535.

Subsequently, monitoring instances that run under these operation systems can be carried out by using either of the following options:

  • Configure the firewalls to allow traffic between servers in the dynamic port range of 49152 through 65535 (less secure).
  • Limit the port range that is used in each monitored server.

n/a

As a result of the change introduced in Java 6 update 29 to how data is sent to databases, users may experience connection failures when using the Microsoft JDBC Driver for SQL Server® to connect to SQL Server. This interoperability enhancement is available in the following SQL Server versions:

  • SQL Server 2012 Production version and later
  • SQL Server 2008 Service Pack 3 Cumulative Update 4
  • SQL Server 2008R2 Service Pack 1 Cumulative Update 6
  • SQL Server 2008R2 Service Pack 2

n/a

Third Party Limitations

Monitoring an SQL Server instance that resides on a Windows 2008R2 requires a workaround as follows:

  1. Browse to https://support.quest.com/ and log in
  2. Perform solution https://support.quest.com/kb/SOL65870

n/a

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 site, http://support.microsoft.com/kb/961435/en-us.

n/a

Due to a known Microsoft issue (https://support.microsoft.com/en-us/kb/3036328), on SQL Server instances version 2014 the SQL text presented may be truncated.

n/a

The Windows System Center 2012 Endpoint Protection tool may negatively impact CPU and system performance of machines running Foglight and the Agent Manager. To reduce resource consumption it is highly recommended that you exclude the following directories from being scanned by the tool:

  • c:\Dell\<foglight>
  • c:\Infobright
  • c:\Dell\<FoglightAgentManager>

n/a

SQL's and execution plans may not be collected on SQL Server 2014 as a result of a Microsoft bug "

"The values of column query_hash and query_plan_hash are NULL for DMV sys.dm_exec_requests in SQL Server 2014"  http://support.microsoft.com/kb/2953592

n/a

The Foglight Time Bar Chart click event does not work with Chrome version 40.x.x.x and 39.x.x.x. https://code.google.com/p/chromium/issues/detail?id=428308

 

Workaround for all missing WMI metric cases

In some cases, running the command: %windir%\system32\wbem\wmiadap.exe /f in Windows' command-line (CMD) may solve the problem of missing WMI classes. This command parses all the performance libraries on the system and refreshes the Performance Counter Classes. For further details, see http://msdn.microsoft.com/en-us/library/aa394528%28VS.85%29.aspx

 


Compatibility of this hotfix

Compatibility of this hotfix

The following Foglight product versions and platforms are compatible with this release.

Product Name

Product Version

Platform

Foglight Management Server

5.6.11 or 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 SQL Server support the Agent Manager HA failover mode, except for the Agent Manager monitoring SQL PI agents. For more information about this mode, see the Agent Manager Guide.

5.7.0 or later

All Platforms supported by this version of the Foglight Agent Manager

 


System requirements

System requirements

Before installing Foglight for SQL Server, ensure that your system meets the hardware and software requirements detailed in Foglight System Requirements and Platform Support Guide. Customers running large deployments (more than 50 instances) should consult the Foglight for Databases Deployment Guide.

Supported Platforms

Foglight for SQL Server supports monitoring the following platforms:

  • Supported SQL Server versions:
    • SQL Server 2005 through 2016
  • Supported Operating Systems:
    • All Operating Systems supported by Microsoft®.

Notes:

  • Foglight for SQL Server also supports the Express and Developer editions of Microsoft® SQL Server.
  • Virtualization monitoring requires installing the VMware tools service on the monitored VM.
  • SQL Server on AWS VM (IaaS) is supported and can be monitored as long as the Instance port is opened and the OS is configured as described in:
    Configuring Windows Remote Management (WinRM)

Final Browser Support Notice

Support for Microsoft® Internet Explorer® 8, 9, and 10 will be discontinued as of the next Foglight release.

Microsoft ended the support for these browsers on January 12, 2016. For more information, visit https://support.microsoft.com/en-us/lifecycle?p1=13418.

These versions of Internet Explorer are supported in this release, as documented in the Foglight System Requirements and Platform Support Guide.

 


Product licensing

Product licensing

Foglight includes a licensing capability that restricts access to those features that are defined in the license. Any Management Server installation requires 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 the Foglight for Infrastructure), others may require an additional license.

Foglight for SQL Server is covered by the base Foglight license that allows cartridges to be installed. The SQL Performance Investigator extension requires a dedicated license.

To activate a trial or a purchased commercial license:

  1. On the navigation panel, under Dashboards, click Administration > Setup & Support > 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.

 


관련 문서

The document was helpful.

평가 결과 선택

I easily found the information I needed.

평가 결과 선택