Connectivity requirements

Overview

This page outlines the connectivity requirements of a Gateway Hub node.

Existing Geneos components

You can find the latest versions of all Geneos components at ITRS Downloads.

For more information about the compatibility between Gateway Hub components and other Geneos components, see the Gateway Hub Compatibility Matrix.

Licence

A valid licence is required to run Gateway Hub.

Server connections

Hostnames

Each server in the cluster must have a unique hostname, resolvable forward and backward with every other node with both normal and reverse DNS name lookup.

Logon method

You must decide to use either passwordless SSH, or an interactive logon, as the method to log in to any server that will form part of the Gateway Hub cluster.

Server to server access

Each Gateway Hub server must have unrestricted access to all other Gateway Hub nodes in the cluster.

Ports

All ports used are TCP ports. The diagram below shows the configuration for ports on each Gateway Hub node. The diagram shows the ports required to be open for incoming connections, outgoing connections, and Gateway Hub node to node connections.

The table below provides more information on the ports and connections outlined in the diagram. Ports marked as external must be accessible to systems connecting to Gateway Hub. Ports marked as internal must be available to other Gateway Hub nodes only.

Service Port (TCP) External/Internal Source IP Destination IP Purpose
CLDB 7222 Internal

Any Gateway Hub node

Any Gateway Hub node

MapR-FS API calls
DNS 53 External

Any Gateway Hub node

DNS server Domain Name Service
Gateway Hub message bus (Kafka listener) 9092 External Any external Gateway

Any Gateway Hub node

Receives Gateway data
Gateway Hub REST API 8080 External Any external client

Any Gateway Hub node

Gateway Hub REST API
Gateway Hub Web Console 8080

External

Any external client

Any Gateway Hub node

Gateway Hub Web Console
MapR Gateway 7660 Internal

Any Gateway Hub node

Any Gateway Hub node

Replication operations
MapR Monitoring Console 8443 External Web browser

Any Gateway Hub node

MapR monitoring web UI
MFS file server 5660
5692
5724
5756
Internal

Any Gateway Hub node

Any Gateway Hub node

FileServer services
MFS replication server 6660 Internal

Any Gateway Hub node

Any Gateway Hub node

MFS replication
NFS management 9998 Internal

Any Gateway Hub node

Any Gateway Hub node

NFS VIP management
NFS monitor 9997 Internal

Any Gateway Hub node

Any Gateway Hub node

NFS VIP management
NTP 123 External

Any Gateway Hub node

NTP server Network Time Protocol
SSH 22 External Any external client

Any Gateway Hub node

Secure Shell, for Ansible install and troubleshooting
SSO Agent 8080 External Any external client Any Gateway Hub node Gateway Hub SSO Agent
Zookeeper 5181 Internal

Any Gateway Hub node

Any Gateway Hub node

Zookeeper API calls
Zookeeper follow-the-leader 2888 Internal

Any Gateway Hub node

Any Gateway Hub node

Zookeeper server-to-server communication
Zookeeper leader election 3888 Internal

Any Gateway Hub node

Any Gateway Hub node

Zookeeper server-to-server communication

The ports for the following services can be manually specified on install:

  • Gateway Hub REST API.
  • MapR Monitoring Console.
  • Gateway Hub message bus (Kafka listener).

For instructions on how to specify port on install, see Configure ports.

SSL certificates

SSL certificates are required to secure the communication between Gateway Hub nodes and client applications, and these are added to Gateway Hub after installation of the binaries.

Obtain the certificates from your systems administrator.

For instructions on adding the SSL certificates to Gateway Hub, see Configure transport layer security.