Firewall Requirements

When installing and starting one or more nodes, either in StreamBase Studio or at the command line with the epadmin command, the StreamBase Runtime opens multiple TCP and UDP ports for both outgoing and incoming traffic. This is to provide channels for node communication and administration, and to allow node-to-node communication. These ports are required even when nodes are installed on a single machine using the hostname localhost.

To connect to a node running on a remote machines, the epadmin command allows you to specify the hostname parameter to specify the DNS name or IP address of the remote machine and the adminport parameter to specify the administration port for that node. (Use an epadmin servicename=nodename.clustername display node command to determine a node's administration port.)

If you have configured the node with a node-specific username and password, you may have to specify that those parameters as well. If the node is running with default security, you can use username=guest and password=guest to authenticate to remote nodes.

Some development or server machines may experience port blocking by their firewall software. If it is not feasible to disable the local firewall, you can configure the firewall to allow incoming traffic as follows:

Program name Function Protocol Ports Required
epadmin Node administration SSL using IPv4 Random free port per node greater than 1024.
swcoord Node administration SSL using IPv4 Random free port per node greater than 1024.
epadmin Service discovery UDP broadcast over IPv4 54321
DTMengine Distribution transport SSL or TCP using IPv4, IPv6 or Infiniband A free port between 5557 up to 5577.
Your JMX-compliant network manager JMX administration TCP over IPv4 Random free port per engine greater than 1024.