Chat now with support
Chat mit Support

Foglight for Databases Shared 6.3.0 - Deployment Guide

Permissions for monitored operating systems

For details, see the following topics:

•
General Unix requirements
•
VMware permissions
•
Windows permissions
General Unix requirements

The OS user account for each agent requires:

•
Silent log-in — in particular, there must be no user-input required and no special login banners displayed
•
For connections using SSH, the sshd daemon must be installed and running.

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

 
* 
NOTE: When monitoring DB2, SYSMON role and privileges for OS user is not required but is recommended to allow the installation to provide more information when discovering DB2 databases.
Linux/UNIX permissions
 
Table 20. Linux/UNIX Permissions
Permission
Linux®
Solaris®
AIX®
HP-UX

Execute

awk

df

free

getconf

head

hostname

iostat

lsnrctl

netstat

ps

sed

tail

sysstat

uname

uptime

vmstat

/proc/

awk

db2ptree

df

head

hostname

iostat

lsnrctl

mpstat

uptime

netstat

pagesize

ps

psrinfo

tail

uname

vmstat

/usr/sbin/prtconf

awk

df

head

hostname

iostat

lsattr

lsdev

lsnrctl

netstat

oslevel

pagesize

ps

tail

uname

uptime

vmstat

awk

bdf

bindprocessor

getconf

head

hostname

ioscan

iostat

lsattr

lsdev

lsnrctl

netstat

oslevel

pagesize

ps

sar

tail

uname

uptime

vmstat

/usr/sbin/

Read

cpuinfo

free*

getconf

sysstat package*

/proc

/proc/cpuinfo*

/proc/net/dev

/proc/stat

/proc/vmstat on Linux >= 2.6

 

 

/var/adm/syslog/syslog.log

VMware permissions

To monitor VMware®, users must have read only access to the virtual center.

Windows permissions

Foglight support monitoring Windows® operating system in one of two ways: WinRM and WMI. The preferred method is WinRM when no WinRM connection WMI connection is used.

WinRM (default) - Based on Kerberos authentication or Basic authentication uses standard HTTP headers. For more information, see http://support.quest.com/technical-documents/foglight-agent-manager/7.1.0/foglight-agent-manager-guide/advanced-system-configuration-and-troubleshooting/configuring-windows-remote-management-winrm.

WMI (fallback) — Permission to access both DCOM and WMI. For more information, see

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

 

 

Install the DB cartridge and DB agent

This section includes details about the following topics:

•
Install the DB cartridge
•
Install a single DB agent

Install the DB cartridge

Foglight for database cartridges run on the Foglight Management Server, which is the operation framework. Therefore, Foglight Management Server must be installed before installing a database cartridge.

To install the Foglight for <database> cartridge:
1
Copy the cartridge car file included in the installation media to your local computer. This file is named as follows:
•
For Foglight for DB2 LUW: DB_DB2-76_3_0 car
•
For Foglight for Oracle: DB_Oracle-6_3_0 car
•
For Foglight for SQL Server: DB_SQL_Server-6_3_0 car
•
For Foglight for Azure SQL Database: DB_Azure-6_3_0 car
2
Log in to the Foglight browser interface.
3
On the navigation panel, click Dashboards > Administration > Cartridges > Cartridge Inventory.
4
On the Cartridge Inventory dashboard, click Install Cartridge to find the CAR file on your local computer.
5
Click Install Cartridge.

Install a single DB agent

For details, see the following topics:

•
Install a single SQL Server or Oracle agent
•
Install a single DB2 agent
•
Install a single SAP ASE agent
•
Install an Azure SQL DB agent
Verwandte Dokumente

The document was helpful.

Bewertung auswählen

I easily found the information I needed.

Bewertung auswählen