A Solace PubSub+ software event broker starts with a basic configuration that enables many common services that can be modified as required.
The following services are included in the basic configuration.
- The message spool is configured and enabled. The maximum spool usage is set to 1500 MB.
- The message VPN named
defaultis enabled with no client authentication. - The client username called
defaultin thedefaultMessage VPN is enabled. The client usernamedefaulthas all settings enabled. - All features are unlocked and do not require a product key.
- All services are enabled and the table below lists their default port numbers.
TLS/SSL services will not become operational until a server certificate is installed.
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.
Default port numbers for Solace PubSub+ software event broker services
| Port | Service description | Type of Traffic |
|---|---|---|
| 22 |
Host OS SSH (2222 for Solace PubSub+ software event broker Machine & Cloud Image releases prior to 8.5.0) |
Management |
| 2222 |
Solace CLI SSH/SFTP (22 for for Solace PubSub+ software event broker Machine & Cloud Image releases prior to 8.5.0) |
Management |
| 8080 | Access to Broker Manager, SEMP, and SolAdmin | Management |
| 1943 |
Access to Broker Manager over HTTPS, SEMP over TLS, and SolAdmin over TLS. For Solace PubSub+ software event broker versions before the 9.4.0 release, use port 943. |
Management |
| 5550 | Health Check Listen Port | Data |
| 5553 | Health Check Listen Port (TLS/SSL ) | Data |
| 55555 | Solace Message Format (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. For Solace PubSub+ software event broker versions before the 9.4.0 release, use port 80. |
Data |
| 1443 |
Web Transport TLS / SSL For Solace PubSub+ software event broker versions before the 9.4.0 release, use port 443. |
Data |
| 5671 | AMQP TLS / SSL ('default' VPN; note that each message VPN configured on the Solace 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 Solace 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 Solace PubSub+ software event broker would require its own unique set of MQTT ports) |
Data |
| 8883 | MQTT TLS / SSL('default' VPN; note that each message VPN configured on the Solace PubSub+ software event broker would require its own unique set of MQTT ports) | Data |
| 8000 | MQTT / WebSockets ('default' VPN; note that each message VPN configured on the Solace PubSub+ software event broker would require its own unique set of MQTT ports) | Data |
| 8443 | MQTT / WebSockets TLS / SSL ('default' VPN; note that each message VPN configured on the Solace PubSub+ software event broker would require its own unique set of MQTT ports) | Data |
| 9000 | REST ('default' VPN; note that each message VPN configured on the Solace PubSub+ software event broker would require its own unique set of REST ports) | Data |
| 9443 | REST TLS / SSL ('default' VPN; note that each message VPN configured on the Solace 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 |
Reloading
When the Solace PubSub+ software event broker is reloaded (for example, using the CLI reload command), the current configuration is preserved. However, the Solace CLI command enable> reload default-config will restore the software event broker to its initial basic configuration.