Configuration Defaults

A Solace PubSub+ software message broker starts with a basic configuration that enables many common services that can be modified as required. In particular, the following 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 default is enabled with no client authentication.
  • The client username called default in the default Message VPN is enabled. The client username default has all settings enabled.
  • All features are unlocked and do not require a product key.
  • All services are enabled. The table below lists the default port numbers that are used for those services.

Default Port Numbers for Solace PubSub+ software message broker Services

Port Service description Type Protocol External Access
22

Host OS SSH

(2222 for Solace PubSub+ software message broker Machine & Cloud Image releases prior to 8.5.0)

Mgmt TCP

Y

2222

Solace CLI SSH/SFTP

(22 for for Solace PubSub+ software message broker Machine & Cloud Image releases prior to 8.5.0)

Mgmt TCP

Y

 

8080 SEMP - SolAdmin Mgmt TCP Y
943 SEMP TLS / SSL Mgmt TCP Y
5550 Health Check Listen Port Data TCP Y
55555 Solace Message Format (SMF) Data TCP Y
55003 SMF compressed Data TCP Y
55556 SMF routing Data TCP Y
55443 SMF TLS / SSL Data TCP Y
80 Web Transport - WebSockets, Comet, etc. Data TCP Y
443 Web Transport TLS / SSL Data TCP Y
5671 AMQP encrypted global port Data TCP Y
5672 AMQP plain-text global port Data TCP Y
1883

MQTT ('default' VPN; note that each message VPN configured on the Solace PubSub+ software message broker would require its own unique set of MQTT ports)

Data TCP Y
8883 MQTT TLS / SSL('default' VPN; note that each message VPN configured on the Solace PubSub+ software message broker would require its own unique set of MQTT ports) Data TCP Y
8000 MQTT / WebSockets ('default' VPN; note that each message VPN configured on the Solace PubSub+ software message broker would require its own unique set of MQTT ports) Data TCP Y
8443 MQTT / WebSockets TLS / SSL ('default' VPN; note that each message VPN configured on the Solace PubSub+ software message broker would require its own unique set of MQTT ports) Data TCP Y
9000 REST ('default' VPN; note that each message VPN configured on the Solace PubSub+ software message broker would require its own unique set of REST ports) Data TCP Y
9443 REST TLS / SSL ('default' VPN; note that each message VPN configured on the Solace PubSub+ software message broker would require its own unique set of REST ports) Data TCP Y
8741 High Availability (HA) Mate Link HA TCP N

8300

8301

8302

HA Configuration Synchronization HA

TCP (8300)

TCP / UDP(8301, 8302)

N

For information on how to modify the message broker configuration with the Solace CLI, refer to the sections provided in the Configuration section.

Note  
  • TLS/SSL services will not become operational until a server certificate is installed.
  • In cloud environments (AWS), ports are typically blocked by the default security group. To access these ports, you have to allow access in the security group.
  • HA Group Configuration requires three visible ports to work properly, some on TCP, UDP, or both protocols. For more details about the requirements for each ports see, HA Group Configuration.
  • When the Solace PubSub+ software message 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 message broker to its initial basic configuration.