Chat now with support
Chat with Support

Foglight for SQL Server (Cartridge) 5.7.5.5 - Deployment Guide

Permissions for Monitored Operating Systems

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 — SUDO permissions
Table 20. SUDO Permissions
Permission
Linux
Solaris
AIX
HP-UX
Execute
df
iostat
uptime
sed
ps
hostname
awk
free
uname
/proc/
vmstat
netstat
getconf
 
 
 
 
 
 
lsnrctl
sysstat
df
iostat
uptime
netstat
vmstat
ps
hostname
awk
mpstat
/usr/sbin/prtconf
uname
pagesize
lsnrctl
 
 
 
 
 
 
psrinfo
db2ptree
df
iostat
uptime
netstat
vmstat
ps
hostname
awk
lsdev
lsattr
oslevel
pagesize
uname
 
 
 
 
 
 
lsnrctl
bdf
uptime
sar
netstat
vmstat
ps
hostname
awk
/usr/sbin/
ioscan
uname
getconf
iostat
lsnrctl
lsattr
lsdev
pagesize
bindprocessor
oslevel
Read
/proc/net/dev
/proc/stat
/proc/vmstat on Linux >= 2.6
/proc
cpuinfo
getconf
sysstat package*
/proc/net/dev*
/proc/cpuinfo*
free*
/proc/cpuinfo*
 
 
/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 referred 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://documents.quest.com/foglight-agent-manager/5.8.5.1/foglight-agent-manager-guide/advanced-system-configuration-and-troubleshooting/configuring-windows-remote-management-winrm?ParentProduct=856#
 
WMI (fallback) — Permission to access both DCOM and WMI. For more information refer to http://documents.quest.com/foglight-agent-manager/5.8.5.1/foglight-agent-manager-guide/advanced-system-configuration-and-troubleshooting/configuring-windows-management-instrumentation-wmi?ParentProduct=856#
 

Special Configurations

This section documents the product settings required for special configurations.
High Availability
The Foglight High Availability Field Guide is available online at:
http://documents.quest.com/foglight/5.7.5/high-availability-field-guide
* 
NOTE: HA is not supported for:
•
Sybase Agents
•
SQL PI repositories
Federation
The Foglight Federation Field Guide is available online at:
http://documents.quest.com/foglight/5.7.5/federation-field-guide/
Concentrator (Proxy)
Information is available online:
•
Agent Manager — http://documents.quest.com/foglight-agent-manager/5.8.5.2/guide/configuring-the-agent-manager/configuring-an-agent-manager-instance-as-a-concentrator/
•
DB agent — Step by step configuration is available in the Database User Guide under "Configuring the On-Demand Data Port on the Agent Manager Concentrator"
* 
NOTE: Not supported for Sybase agents.
Table 21. Concentrator Agent Manager
Number of Agents
<100
<200
JVM Settings**
2048MB
4096MB
CPUs (2.4GHz)*
2 cores
4 cores
RAM*
4GB
6GB
CPUs (2.4GHz)* — for a virtual machine the CPU allocation must be reserved. The reservation is expressed in MHz
RAM*- for a virtual machine the memory allocation must be reserved.
** — After locating your hardware requirements in the tables, ensure that you complete the manual JVM Setting configuration as described in Manual Configuration Required by all Users.

High Availability

This section documents the product settings required for special configurations.
The Foglight High Availability Field Guide is available online at:
http://documents.quest.com/foglight/5.7.5/high-availability-field-guide
* 
NOTE: HA is not supported for:
•
Sybase Agents
•
SQL PI repositories
Federation
The Foglight Federation Field Guide is available online at:
http://documents.quest.com/foglight/5.7.5/federation-field-guide/
Concentrator (Proxy)
Information is available online:
•
Agent Manager — http://documents.quest.com/foglight-agent-manager/5.8.5.2/guide/configuring-the-agent-manager/configuring-an-agent-manager-instance-as-a-concentrator/
•
DB agent — Step by step configuration is available in the Database User Guide under "Configuring the On-Demand Data Port on the Agent Manager Concentrator"
* 
NOTE: Not supported for Sybase agents.
Table 21. Concentrator Agent Manager
Number of Agents
<100
<200
JVM Settings**
2048MB
4096MB
CPUs (2.4GHz)*
2 cores
4 cores
RAM*
4GB
6GB
CPUs (2.4GHz)* — for a virtual machine the CPU allocation must be reserved. The reservation is expressed in MHz
RAM*- for a virtual machine the memory allocation must be reserved.
** — After locating your hardware requirements in the tables, ensure that you complete the manual JVM Setting configuration as described in Manual Configuration Required by all Users.

Federation

This section documents the product settings required for special configurations.
High Availability
The Foglight High Availability Field Guide is available online at:
http://documents.quest.com/foglight/5.7.5/high-availability-field-guide
* 
NOTE: HA is not supported for:
•
Sybase Agents
•
SQL PI repositories
The Foglight Federation Field Guide is available online at:
http://documents.quest.com/foglight/5.7.5/federation-field-guide/
Concentrator (Proxy)
Information is available online:
•
Agent Manager — http://documents.quest.com/foglight-agent-manager/5.8.5.2/guide/configuring-the-agent-manager/configuring-an-agent-manager-instance-as-a-concentrator/
•
DB agent — Step by step configuration is available in the Database User Guide under "Configuring the On-Demand Data Port on the Agent Manager Concentrator"
* 
NOTE: Not supported for Sybase agents.
Table 21. Concentrator Agent Manager
Number of Agents
<100
<200
JVM Settings**
2048MB
4096MB
CPUs (2.4GHz)*
2 cores
4 cores
RAM*
4GB
6GB
CPUs (2.4GHz)* — for a virtual machine the CPU allocation must be reserved. The reservation is expressed in MHz
RAM*- for a virtual machine the memory allocation must be reserved.
** — After locating your hardware requirements in the tables, ensure that you complete the manual JVM Setting configuration as described in Manual Configuration Required by all Users.
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating