Chatta subito con l'assistenza
Chat con il supporto

Foglight for DB2 (Cartridge) 6.1.0.10 - Getting Started Guide

Windows Systems

Windows Systems

The agent’s OS user account requires:

•
To monitor Windows Operating System metrics, access to WMI. Ensure that the WMI service is started before creating agents and monitoring the process metrics.
Permissions for monitoring Windows OS

Monitoring with WMI:

http://support.quest.com/technical-documents/foglight-agent-manager/6.1.0.10/foglight-agent-manager-guide/advanced-system-configuration-and-troubleshooting/configuring-windows-management-instrumentation-wmi

Monitoring with WinRM:

http://support.quest.com/technical-documents/foglight-agent-manager/6.1.0.10/foglight-agent-manager-guide/advanced-system-configuration-and-troubleshooting/configuring-windows-remote-management-winrm

UNIX Systems

The agent’s OS user account requires:

•
Access and execute permission to the following programs: df, du, awk, iostat, vmstat, uptime, hostname, netstat, sed, ps, uname
•
Silent log-in — in particular, there must be no user-input required and no special login banners displayed
•
For connection using SSH, the sshd daemon must be installed and running
•
For connection using Telnet, a Telnet daemon must be installed and running

In addition to these general UNIX system requirements, the agent’s user account requires additional privileges depending on the operating system, as specified in the following table.

 
Table 1. User account requirements by OS
OS
Additional OS user account requirements
Linux
•
Access to the sysstat package, to permit the agent to get detailed disk I/O information
•
Access to the /proc filesystem
•
Access to the following programs: /proc/vmstat, /proc/net/dev, free, /proc/cpuinfo, getconf
Solaris

Access to the following programs: /usr/sbin/prtconf, mpstat, pagesize, psrinfo, db2ptree

AIX
•
setuid permissions on vmstat and iostat
•
setgid permissions on PS
•
Access to the following programs: lsattr, lsdev, pagesize, bindprocessor, oslevel
Using Sudo

The sudo utility allows system administrators to grant specific users (or groups of users) the ability to run certain commands that require administrative privileges as the root, without having to log in as administrator.

If you intend for an agent to run UNIX commands with sudo permissions, check the /etc/sudoers file on the monitored host for the following line and comment it out:

Defaults requiretty

The programs that can be run using sudo are as follows:

•
On all platforms: db2, du, df, grep, hostname, awk, iostat, vmstat, ps, uname, egrep
•
On the Linux platform: free, /proc/cpuinfo, getconf
•
On the Solaris platform: /usr/sbin/prtconf, xargs, pagesize, psrinfo, db2ptree
•
On the AIX platform: lsattr, pagesize, bindprocessor, oslevel

Required DB2 LUW User Account Privileges

Foglight monitoring agents use DB2 LUW user accounts to access the monitored DB2 instances. Before adding monitored instances, ensure that the user accounts have at least the following privilege and permission set:

•
SYSMON authority (enables monitoring)
•
AUTH_LIST_AUTHORITIES_FOR_AUTHID permission (enables the wizard to verify and set permissions)
•
Select permission on SYSIBMADM.PRIVILEGES, SYSCAT.VIEWS and SYSCAT.ROUTINES

When you add monitored instances, the Monitor DB2 Instance wizard checks that other required permissions exist and, if not, executes a script to grant any missing permissions. For a list of the required permissions granted by this script, see Permissions .

Required DB2 LUW Monitor Switches

To monitor DB2 instances below version 9.7, ensure that the following monitored switches are turned on:

•
UOW
•
STATEMENT
•
LOCK
•
SORT
•
TABLE
•
BUFFERPOOL
•
TIMESTAMP

To monitor DB2 instances of version 9.7 and above, ensure that the following monitoring configuration parameters are set to base level (at least):

•
MON_REQ_METRICS
•
MON_ACT_METRICS
•
MON_OBJ_METRICS

When you add monitored instances, the Monitor DB2 Instance wizard checks that the monitoring configuration parameters are set correctly. If not, it prompts you to set them.

The switches can be turned on or off manually by updating the database manager configuration. Enabled switches may cause additional overhead on the database manager.

For additional information, see http://publib.boulder.ibm.com/infocenter/db2luw/v9r5/index.jsp?topic=/com.ibm.db2.luw.admin.mon.doc/doc/c0005719.html System Monitor Switches and http://pic.dhe.ibm.com/infocenter/db2luw/v9r7/index.jsp?topic=%2Fcom.ibm.db2.luw.wn.doc%2Fdoc%2Fc0054153.html on IBM’s DB2 InfoCenter web site.

Or, review the information in at http://publib.boulder.ibm.com/infocenter/db2luw/v9r5/index.jsp?topic=/com.ibm.db2.luw.common.doc/doc/r0008264.htm DB2 System Monitor Guide and Reference Redbook

Related Documents

The document was helpful.

Seleziona valutazione

I easily found the information I needed.

Seleziona valutazione