Foglight Agent Manager 5.9.2 - Foglight Agent Manager Guide

Access to WMI is required for both OS verification while creating an agent, and for collecting OS metrics from the monitored host. In some cases, an access violation on the WMI namespace (error 0x00000005) may occur when the agent connectivity verification fails. The access violation error can occur when the permissions or credentials used to access WMI, and specifically the root\cimv2 namespace and Root\MSCluster (if the machine is included in a cluster), are changed or invalid.

In order to view and change namespace security, the user must have Read Security and Edit Security permissions. Administrator accounts have these permissions by default, and can assign them to other users if necessary.

To grant namespace permissions to a user:

Right-click My Computer and click Manage.

In the Computer Management dialog box that appears, expand the Services and Applications node.

Right-click WMI Control, and click Properties.

In the WMI Control Properties dialog box that appears, open the Security tab.

Expand the Root node and select CIMV2, then click Security.

In the Security for ROOT\CIMV2 dialog box that appears, modify or assign permissions as necessary.


	IMPORTANT: If the user accesses the namespace remotely, you must select the Remote Enable permissions check box.

Click OK on each of the dialog boxes to close them.

If the machine is part of a cluster, repeat the procedure for the ROOT\MSCluster namespace.


	NOTE: User permissions set on a namespace apply only to the namespace and not to any sub-namespaces. If the user also needs to access sub-namespaces, you can enable access from the Advanced Security Settings dialog box (accessible by clicking Advanced on the Security for [namespace] dialog box).

WMI and Quota Violation error

In some cases, when the agent queries WMI to collect metrics on the monitored host, the host’s performance may be affected. When this occurs, the agent log includes the message: Quota violation [SWbemServicesEx]. This error stems from WMI rather than the agent, and has been identified by Microsoft® as a known issue in Windows® Server 2003.

To correct this error:

Ensure that the following hotfix, available from Microsoft in KB 828653, is applied:

http://support.microsoft.com/kb/828653

Restart the WMI service on the monitored host.

Known WMI issues in Windows Server 2008

Microsoft® has identified a number of known issues with WMI services in Windows® Server 2008. The following issues may occur:

•

The database agent OS validation or collection has errors, even when the OS credentials are correct.

•

The WMI reports incorrect data from the performance classes.

•

Remotely accessing WMI causes memory leaks in Windows Server 2008.

•

The WMI reports are unstable.

•

In SQL Server 2008, the perfmon counters do not appear under WMI because they do not exist.

To resolve these issues:

Using the same OS credentials as the agent uses, run perfmon /wmi on the monitored host.

Install the hotfixes available in the following Microsoft support articles on the Windows 2008 machine:

•

http://support.microsoft.com/?id=961435

•

http://support.microsoft.com/?id=970967

•

http://support.microsoft.com/?id=970520

In SQL Server 2008 on Windows Server 2008, if the perfmon counters are missing from WMI, install the following hotfix: http://support.microsoft.com/kb/969531.

Tuning WMI connections

The following parameters can be used to fine tune the Windows Management Instrumentation (WMI) connections made by Foglight® agents. You can set these parameters for Foglight Agent Manager either in the baseline.jvmargs.config file as vmparameter options, or specify them directly as jvm options when starting up Foglight Agent Manager via command line. The values used for these parameters vary from environment to environment and so should be used as reference only.

•

Max Active Connections: Defines the number of simultaneous outbound connections that can be made by all agents running on a particular instance of Foglight Agent Manager. The default value is 100.

Sample: -Dcom.quest.connection.regulator.maxActiveConnectionsCap=500

•

Expire connection based on no. of executions: Defines the number of executions that can be made by a connection before forcibly closing it. The default value is 50.

Sample: -Dquest.debug.poolable.wmi.time.to.live.executions=200

•

Timeout by elapsed time: Defines the time (in milliseconds) after which a connection is expired. The default value is 600000 (10 mins).

Sample: -Dquest.debug.poolable.wmi.time.to.live.timeout.millis=900000