SAME

SAME Default Ports

SAME uses services that are assigned to use ports for inter-server communication channels at runtime. Once a port has been assigned for use by a service on a server, that port cannot be used by another service when communicating to that server.

The Riedel Software Manager has specific requirements for the ports that must be open during software deployment, installation, and maintenance. See RSM Deployment Ports.

End User Access

Internal Control Network Access

End User Browser <> STAGE Cluster (bi-directional)

NAME

PURPOSE

PORT/s

TCP or UDP

HTTP

HTTP

80

TCP

HTTPS

HTTPS

443

TCP

System Services

STAGE Cluster <> STAGE Cluster

NAME

PURPOSE

PORT/s

TCP or UDP

NTP

NTP

123

UDP

DNS

DNS

53

TCP and UDP

SSH

Secured Shell (SSH)

22

TCP

HTTP

HTTP

80

TCP

HTTPS

HTTPS

443

TCP

Nomad HTTP API

Nomad HTTP API - This is used by clients and servers to serve the HTTP API.

4646

TCP

Nomad RPC

Nomad - Internal RPC communication between client agents and servers, and for inter-server traffic.

4647

TCP

Nomad Serf WAN

Nomad - Used by servers to gossip both over the LAN and WAN to other servers.

4648

TCP and UDP

Consul API

Consul API

8500

TCP

Riedel Software Manager

Riedel Software Manager API

9900-
9901

TCP and UDP

Consul DNS

Inter-Node Consul DNS

8600

TCP and UDP

Consul HTTP

Inter-Node Consul HTTP

8500

TCP

Consul HTTP(S)

Inter-Node Consul HTTP(S)

8501

TCP

Consul gRPC

Inter-Node Consul gRPC

8502

TCP

Consul gRPC TLS

Inter-Node Consul gRPC with TLS

8503

TCP

Consul Server RPC

Inter-Node Consul internal communication with servers

8300

TCP

Consul LAN Serf

The Serf local area network port

8301

TCP and UDP

Consul WAN Serf

The Serf wide area network port

8302

TCP and UDP

Vert.X

Event Bus

20000-
32000

TCP

Hazelcast

Cluster Management

20000-
32000

TCP

STAGE Cluster <> Active Directory

NAME

PURPOSE

PORT/s

TCP or UDP

Active Directory

User Data Sync

389 / 636 (default LDAP / LDAPS port, configurable)

TCP


STAGE Cluster <> NMOS Registry

NAME

PURPOSE

PORT/s

TCP or UDP

NMOS

IS-04 NMOS Discovery and Registration

IS-05 NMOS Device Connection Management

443 / 80

TCP / UDP


STAGE Cluster <> SAME DSP Engine

NAME

PURPOSE

PORT/s

TCP or UDP

Control Port

Control Port

Default: 4000 (Configurable)
bidirectional gRPC connection

TCP

Host Engine Control Port

Host Engine Control Port

Default: 4001 (Configurable)
bidirectional gRPC connection

TCP

Host Media Control Port

Host Media Control Port

Default: 4002 (Configurable)
bidirectional gRPC connection

TCP

Host Metrics Listen Port

Host Metrics Listen Port

Default: 9273 (Configurable)

TCP


3rd party Client <> STAGE Cluster

When a SAME DSP Engine instance is set to Direct Control Mode, a Northbound API using REST & gRPD becomes available for use by a Broadcast Control System (BCS). It is also possible for this SAME DSP Engine instance to become an AMWA NMOS Node.

See SAME_ Putting a SAME DSP Engine Under Northbound Control .

NAME

PURPOSE

PORT/s

TCP or UDP

REST

gRPD

The STAGE Northbound API enables remote control of Applications hosted by a STAGE system.

Default: 8444 (Configurable at installation time in RSM)

TCP / UDP

NMOS

IS-04 NMOS Discovery and Registration

IS-05 NMOS Device Connection Management

Configurable. See SAME_ Putting a SAME DSP Engine Under Northbound Control.

TCP / UDP 


SAME DSP Engine <> Metrics

NAME

PURPOSE

PORT/s

TCP or UDP

LGraphina

Host Metrics port.

Default: 8089 (Configurable; see SAME_ SAME DSP Engine Configuration )

TCP / UDP