Fglam to Database Connectivity. Port number ... - Support

screechingagendaΔίκτυα και Επικοινωνίες

26 Οκτ 2013 (πριν από 4 χρόνια και 17 μέρες)

109 εμφανίσεις

Fglam to Database Connectivity. Port number communications


Article # QSI
-
DBWC
-
005

1. This article is relevant for:

Operating System

DataBases

Agent/Component Version

Windows, UNIX

Oracle, SQL Server

5.5.2 and up

Symptoms



Firewall environment is established between the FglAM and the remote database



What ports are needed to be opened in order to allow FglAM
-

Database connectivity?



Auto Discovery

is not running on the target host for
SQL Server


Explanation

This page will
discuss a scenario where a firewall has been established between FglAM and the monitored database.

The other possible scenario is firewall between FMS
-

FglAM and FglAM
-

Database. This is more Foglight direct issue and
will not be the focus of this page.


Solution

UNIX and UNIX flavors FglAM
-
Db ports (Oracle)

For UNIX/UNIX Flavors machines, the ports required are as in the table below.

The needed ports required to be opened between FglAM and the database will be:

Default Port Number

Description

Usage

Mandatory or Optional?

1521

Database port

Oracle Connection

Mandatory

22

SSH

OS connection

Optional

23

Telnet

OS connection

Optional

Notes:



OS Connection is optional. The Database Cartridge will not collect system metrics, but will fetch the database
data and metrics.

Windows FglAM
-
Db ports (SQL Server)

For Windows platforms, the ports required are as in the table below.

The needed ports required to be opened between FglAM and the database will be:

Default Port
Number

Description

Usage

Mandatory or
Optional?

1433

Database port

Inbound SQL Server
Connection

Mandatory

1434

Database port

Outbound SQL Server
Connection

Mandatory

135

RPC (Remote Procedure Call

Client/Server connection

Mandatory

5000
-

50001

WMI (Windows Management
Instrumentation)

OS connection

Optional

Notes:



WMI

requires 20 ports range to be opened
above

port 5000. Please refer to
http://support.microsoft.com/default.aspx?scid=kb;en
-
us;154596




Working without
WMI

means that no OS metrics will be fetched (Database metrics will
be fetched).

SQL Server browser needs to be running on the target host

In order for
Auto Discovery

to complete its process and discover
SQL Server

instances on the remote host,
SQL
Server Browser

service
must

be up and running.

Windows 2008/Vista ports

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.

o

Use the
RPCCfg.exe

(Windows Resource Kits) by running:
rpccfg.exe
-
pe 5009
-
5009
-
d 0


o

man
ually 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
foll
owing 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.