Connectivity requirements

Overview

This page outlines the connectivity requirements of a Gateway Hub nodeA node is one server that consistutes a Gateway Hub instance. Many nodes form a cluster..

Existing Geneos components

You must have at least version 4.8.0. of both Active Console 2 and Gateway. You can find the latest versions of all Geneos components at https://resources.itrsgroup.com/downloads.

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.

Port (TCP) Service External/Internal Source IP Destination IP Purpose
8080 Gateway Hub REST API External Any external client

Any Gateway Hub node

Gateway Hub REST API
8443 MapR Monitoring Console External Web browser

Any Gateway Hub node

MapR monitoring web UI
8888 Gateway Hub Web Console

External

Any external client

Any Gateway Hub node

Gateway Hub Web Console
9092 Gateway Hub message bus (Kafka listener) External Any external Gateway

Any Gateway Hub node

Receives Gateway data
9999 SSO Agent External Any external client Any Gateway Hub node Gateway Hub SSO Agent
  Message bus JMX monitoring External Any Netprobe

Any Gateway Hub node

Monitoring of message bus queue information
22 SSH External Any external client

Any Gateway Hub node

Secure Shell, for Ansible install and troubleshooting
53 DNS External

Any Gateway Hub node

DNS server Domain Name Service
123 NTP External

Any Gateway Hub node

NTP server Network Time Protocol
2888 Zookeeper follow-the-leader Internal

Any Gateway Hub node

Any Gateway Hub node

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

Any Gateway Hub node

Any Gateway Hub node

Zookeeper server-to-server communication
5181 Zookeeper Internal

Any Gateway Hub node

Any Gateway Hub node

Zookeeper API calls
5660
5692
5724
5756
MFS server Internal

Any Gateway Hub node

Any Gateway Hub node

FileServer services
6660 MFS server Internal

Any Gateway Hub node

Any Gateway Hub node

MFS replication
7222 CLDB Internal

Any Gateway Hub node

Any Gateway Hub node

MapR-FS API calls
7660 MapR Gateway Internal

Any Gateway Hub node

Any Gateway Hub node

Replication operations
8998 Livy Internal

Any Gateway Hub node

Any Gateway Hub node

Apache Livy
9997 NFS monitor Internal

Any Gateway Hub node

Any Gateway Hub node

NFS VIP management
9998 NFS management Internal

Any Gateway Hub node

Any Gateway Hub node

NFS VIP management

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

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

For instructions on how to specify port on install, see Additional configuration for 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.