Ports

Description of ports used for Opsview Monitor

Overview

Since Opsview Monitor is based on microservices there are a lot of network ports in use across all the different components to pass the required data around. These will need to be configured in any network or host firewalls.

The below configuration examples assume an installation based upon opsview_deploy-02-small.yml has been set up as per the Advanced Automated Installation guide.

Collectors to the Orchestrator

These ports need to be opened from the Collector to the Orchestrator:

PortComponent
15985datastore-access
35673messagequeue-access
45673messagequeue-management-access
12378registry-access

Collector Clusters

All collectors within the same cluster need to be able to communicate over the following ports:

PortComponent
4369erlang-clustering-port
5666opsview-agent
8183cache-manager-access
15985datastore-access
25672messagequeue-internode-communication
25984datastore-management-access
35672:35682messagequeue-access
45673messagequeue-management-access

Collectors in different Clusters do not communicate.

Remote Databases

These ports need to be opened from the Orchestrator to the remote database instance:

PortComponent
13307database-access

These ports need to be opened from the remote database instance to the Orchestrator:

PortComponent
15985datastore-access
35673messagequeue-access
45673messagequeue-management-access
12378registry-access

Remote Timeseries Server

These ports need to be opened from the Orchestrator to the Timeseries server (assuming all Timeseries components are on the same server):

PortComponent
11601timeseries-access

These ports need to be opened from the Timeseries server to the Orchestrator:

PortComponent
15985datastore-access
35673messagequeue-access
45673messagequeue-management-access
12378registry-access

List of All Ports

In the table below we list the TCP and UDP ports that are used by Opsview Monitor in the default setup:

Database

Listening PortProtocolLoopback OnlyComponentLocationDescriptionConnection From
13306TCPopsview-loadbalancerOrchestratorLoad balances traffic for intra-host communicationLoadbalancer on local server
13307TCPopsview-loadbalancerDatabase serversInter-host communication with TLS encryption optionalPrimary and collector servers, routed to 3306 on local server
3306TCPmysqldDatabase serversActual database port. Should not be used directly, but via Opsview LoadbalancerLoadbalancer on local server

Datastore

Listening PortProtocolLoopback OnlyComponentLocationDescriptionConnection From
15984TCPopsview-loadbalancerPrimary serverLoad balances traffic for intra-host communicationCollector Servers
15986TCPopsview-loadbalancerCollector serversLoad balances traffic for intra-host communicationCollector servers within the same cluster
15985TCPopsview-loadbalancerDatastore serversInter-host communication with TLS encryption optionalCollector servers within the same cluster
5984TCPopsview-datastoreDatastore serversActual datastore port. Should not be used directly, but via Opsview LoadbalancerLoadbalancer on local server
25984TCPopsview-datastoreDatastore serversDatastore dist bind port. See http://docs.couchdb.org/en/stable/cluster/setup.html#firewallOther Datastore servers when HA is set up

Loadbalancer

Listening PortProtocolLoopback OnlyComponentLocationDescriptionConnection From
9000TCPopsview-loadbalancerPrimary and collector serversLoadbalancer port. Should not be used directly. Required by Opsview - Components - Loadbalancer OpspackOpsview Collector on localhost

Messagequeue

Listening PortProtocolLoopback OnlyComponentLocationDescriptionConnection From
35672TCPopsview-loadbalancerPrimary serverLoad balances traffic for intra-host communicationCollector servers
35675TCPopsview-loadbalancerCollector serversLoad balances traffic for intra-host communicationCollector servers within the same cluster
35673TCPopsview-loadbalancerMessagequeue serversInter-host communication with TLS encryption optionalLoadbalancer on any server
5672TCPopsview-messagequeueMessagequeue serversActual messagequeue port. Should not be used directly, but via Opsview LoadbalancerLoadbalancer on same server
45672TCPopsview-loadbalancerPrimary serverLoad balances traffic for intra-host communication (Messagequeue management)Collector servers
45675TCPopsview-loadbalancerCollector serversLoad balances traffic for intra-host communication (Messagequeue management)Collector servers within the same cluster
45673TCPopsview-loadbalancerMessagequeue serversInter-host communication with TLS encryption optional (Messagequeue management)Loadbalancer on any server
15672TCPopsview-messagequeueMessagequeue serversActual messagequeue management port. Should not be used directly, but via Opsview LoadbalancerLoadbalancer on same server
25672TCPopsview-messagequeueMessagequeue serversMessagequeue dist bind port. See https://www.rabbitmq.com/networking.html#portsOther Messagequeue servers when HA is set up

Registry

Listening PortProtocolLoopback OnlyComponentLocationDescriptionConnection From
12379TCPopsview-loadbalancerPrimary and collector serversLoad balances traffic for intra-host communicationAll Opsview servers, routed to 12378 on Registry servers
12378TCPopsview-loadbalancerRegistry serversInter-host communication with TLS encryption optionalLoadbalancer on any Opsview any server, routed to 12379 on localhost
2379TCPopsview-registryRegistry serversActual registry port. Should not be used directly, but via Opsview LoadbalancerLoadbalancer on local server
2380TCPopsview-registryRegistry serversUsed for HA registry clusteringOther Registry servers

Cache Manager

Listening PortProtocolLoopback OnlyComponentLocationDescriptionConnection From
8183TCPopsview-cachemanagerPrimary and collector serversUsed to cache session and other disposable data with a short shelf lifeAll Opsview servers, routed to 12378 on Registry servers

Timeseries

Listening PortProtocolLoopback OnlyComponentLocationDescriptionConnection From
11600TCPopsview-loadbalancerPrimary and collector serversLoad balances traffic for intra-host communicationPrimary Server, routed to 11601 on Timeseries servers
11601TCPopsview-loadbalancerTimeseries serversInter-host communication with TLS encryption optionalLoadbalancer on Primary Server, routed to 1600 on local server
1600TCPopsview-timeseriesTimeseries serversActual timeseries port. Should not be used directly, but via Opsview LoadbalancerLoadbalancer on local server
1620TCPopsview-timeseries-enqueuerTimeseries serversTimeseries enqueuer portopsview-timeseries component
1640..43TCPopsview-timeseries-rrd
opsview-timeseries-influxdb
Timeseries serversTimeseries write portsopsview-timeseries-enqueuer component
1660TCPopsview-timeseries-rrd
opsview-timeseries-influxdb
Timeseries serversTimeseries query portsopsview-timeseries-enqueuer component

Web UI

Listening PortProtocolLoopback OnlyComponentLocationDescriptionConnection From
80TCPNGINXPrimary serverHTTP port for the web UIUser Web Browser
443TCPNGINXPrimary serverHTTPS port for the web UIUser Web Browser
3000TCPopsview-web-appPrimary serverMay be configured to listen on specific interfaces by changing the $bind_address in opsview.confNGINX proxy on localhost

Other

Listening PortProtocolLoopback OnlyComponentLocationDescriptionConnection From
5666TCPopsview-agentAll serversOpsview Collectors should be able to access it for monitoringOpsview Collectors
8181TCPopsview-orchestratorPrimary serverOrchestrator port. Should not be used directly, but via Opsview Web UIopsview-web-app component
4369 TCPopsview-datastore
opsview-messagequeue
Datastore and Messagequeue serversErlang port used for peer service discovery. See Opsview Message Queue HA and Opsview Datastore HA- opsview-loadbalancer
- opsview-datastore and opsview-messagequeue when HA is set up.
6343
2055
9066
TCP
UDP
UDP
opsview-flow-collectorCollector serversYou may need to check your sFlow/NetFlow source device configuration for which ports to openAny device submitting "*flow" data