Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

When deploying a bare-metal on-prem host, you must open applicable ports on the host, to ensure that all services are functioning properly. The following table lists the ports that need to be available on the bare-metal on-prem host, in addition to the port usage for firewalls, as described in BloxOne Connectivity and Service Requirements

IP ProtocolPortServices using this portDescription
TCP22
  • Data Connector
  • NIOS
Required for an incoming SCP data transfer from NIOS to Data Connector when deployed as a container. When you deploy Data Connector as a container, ensure that there are no SSH processes listening on port 22. You must terminate these SSH processes for Data Connector to collect data from NIOS.
TCP53

On-prem hosts

Ensure that there are no other processes using port 53 on the host system on which your on-prem host will be deployed. For example, some Ubuntu systems running a local DNS cache (system-resolved) might occupy port 53, and your on-prem host might not function properly in this case.

TCP514

Data Connector

Required for a Data Connector secure syslog for RPZ hits data. If you deploy Data Connector as a container, ensure that this port is not used by other processes.
TCP2222

On-prem hosts

Used by an internal service for remote monitoring.
TCP6514
  • NIOS (SCP data transfer)
  • Data Connector
Used for transferring syslog data from NIOS to Data container. Port 6514 is a default secure port. If you deploy Data Connector as a container, ensure that this port is not used by other processes.
TCP8125

Data Connector

This is an internal port used for communications between containers. If you deploy Data Connector as a container, ensure that this port is not used by other processes.
TCP8126

Data Connector

This is an internal port used for communications between containers. If you deploy Data Connector as a container, ensure that this port is not used by other processes. 
TCP50514

Data Connector

This is an internal port used for communications between containers. If you deploy Data Connector as a container, ensure that this port is not used by other processes.
  • No labels