Wiki Reorganisation
This page has been classified for reorganisation. It has been given the category MOVE.
The content of this page will be revised and moved to one or more other pages in the new wiki structure.

ESGF Node Port description

Port	Direction	Type	Application	Description
80	in	tcp	Tomcat	Web server access
443	in	tcp	Tomcat	SSL - Secure Web Server Access.
5432	in	tcp	Postgres	Postgres Access. (not external: by default bound ONLY TO LOCAL INTERFACE)
2811	in	tcp	GridFTP	user-configured GridFTP Server control channel
(60000-61000)	in/out	tcp	GridFTP	user-configured GridFTP Server data channel (or as defined in the global variable GLOBUS_TCP_PORT_RANGE)
2812	in	tcp	GridFTP	BDM-configured GridFTP Server control channel. May run together with the user-configured one though not recommended - system resource intensive!
(60000-61000)	in/out	tcp	GridFTP	BDM-configured GridFTP Server data channel. May run together with the user-configured one though not recommended - system resource intensive!
7512	out	tcp	MyProxy	MyProxy client access to the certificate repository
8984	-	tcp	esgf-search (Tomcat)	local connection to the Solr master instance (not external!)
8983	in/out	tcp	esgf-search (Tomcat)	Connection to remotes Solr slave instance. Used in distributed search (shard).
80	out	tcp	esg-publisher	Local connection to THREDDS server (e.g., to check catalogs) and other nodes (node-manager)
443	out	tcp	esg-publisher	Local secure connection to THREDDS server (e.g., to restart the application) and to the idp

Installer

• The installer further requires outbound ports 20 and 21 to be open so it can download the required libraries.

Some notes

• BDM ( B ulk D ata M over): It is used for moving data from one node to other ( Use cases , Security Architecture )