Default Port Numbers
Default port numbers for the PubSub+ Appliances and PubSub+ Software Event Brokers are listed in the tables below:
Appliance
Default port numbers for services on the PubSub+ Appliance
| Port | Service Description | Appliance Interface |
|---|---|---|
|
22 |
Access to host shell or CLI depending on the account you log into. |
Management |
|
80 |
Access to Broker Manager, SEMP, and SolAdmin |
Management |
|
443 |
Access to Broker Manager over HTTPS, SEMP over TLS, and SolAdmin over TLS |
Management |
|
80 |
Used for Web Messaging |
Message Backbone |
| 5550 | Health Check Listen Port | Message Backbone |
|
5553 |
Health Check Listen Port TLS |
Message Backbone |
|
55555 |
(SMF) |
Message Backbone |
|
55003 |
SMF compressed |
Message Backbone |
|
55556 |
SMF routing |
Message Backbone |
|
55443 |
SMF TLS / SSL (with or without compression) |
Message Backbone |
|
443 |
Web Transport TLS / SSL |
Message Backbone |
Software Event Broker
Default port numbers for the services on the PubSub+ Software Event Broker
In cloud environments (for example, AWS), ports are typically blocked by the default security group. To access them, you have to allow access in the security group.
| Port | Service description | Type of Traffic |
|---|---|---|
|
2222 |
Solace CLI SSH/SFTP |
Management |
|
8080 |
Access to Broker Manager, SEMP, and SolAdmin |
Management |
|
1943 |
Access to Broker Manager over HTTPS, SEMP over TLS, and SolAdmin over TLS |
Management |
|
5550 |
Health Check Listen Port |
Data |
| 5553 | Health Check Listen Port TLS | Data |
|
55555 |
(SMF) |
Data |
|
55003 |
SMF compressed |
Data |
|
55556 |
SMF routing |
Data |
|
55443 |
SMF TLS / SSL (with or without compression) |
Data |
|
8008 |
Web Transport - WebSockets, Comet, etc. |
Data |
|
1443 |
Web Transport TLS / SSL |
Data |
|
5671 |
AMQP TLS / SSL ('default' VPN; note that each message VPN configured on the PubSub+ Software Event Broker would require its own unique set of AMQP ports) |
Data |
|
5672 |
AMQP ('default' VPN; note that each message VPN configured on the PubSub+ Software Event Broker would require its own unique set of AMQP ports) |
Data |
|
1883 |
MQTT ('default' VPN; note that each message VPN configured on the PubSub+ Software Event Broker requires its own unique set of MQTT ports) |
Data |
|
8883 |
MQTT TLS / SSL('default' VPN; note that each message VPN configured on thePubSub+ Software Event Broker requires its own unique set of MQTT ports) |
Data |
|
8000 |
MQTT / WebSockets ('default' VPN; note that each message VPN configured on the PubSub+ Software Event Broker requires its own unique set of MQTT ports) |
Data |
|
8443 |
MQTT / WebSockets TLS / SSL ('default' VPN; note that each message VPN configured on the PubSub+ Software Event Broker requires its own unique set of MQTT ports) |
Data |
|
9000 |
REST ('default' VPN; note that each message VPN configured on the PubSub+ Software Event Broker requires its own unique set of REST ports) |
Data |
|
9443 |
REST TLS / SSL ('default' VPN; note that each message VPN configured on the PubSub+ Software Event Broker would require its own unique set of REST ports) |
Data |
|
8741 |
High-availability (HA) Mate Link |
HA |
|
8300 8301 8302 |
HA Configuration Synchronization |
HA |
A typical Linux operating system ports 0 to 1023 are by default privileged ports for the root user. These are ports which only a process with NET_BIND_SERVICE capability can bind too .PubSub+ event brokers can bind to privileged ports when the container has been granted NET_BIND_SERVICE capability, and the UID is 0. For more information on privileged port configuration, refer to Configuring Privileged Ports.