CLI Configuration of Scaling Tiers for HA Groups

This section shows you the steps to increase the connection scaling tier for the primary and backup software event brokers in a high-availability (HA) group using the Solace CLI .

Step 1: Review System Resource Requirements and HA Status

Before you increase the connection scaling tiers of your brokers:

  • Ensure that you can adequately provision your system for the new scaling tier. See Scaling Tiers for Software Event Brokers for details about the available tiers and the required resources for each one.
  • Verify that HA is operationally up on all event brokers in the HA group and that the Activity Status for each event broker is correct. You can use the show redundancy command to check operational states.

For example, if you have two brokers in an HA pair, where solace_01 is the primary and solace_02 is the backup, the output of the show redundancy command would look similar to the following for the primary broker:

solace_01# show redundancy 

Configuration Status     : Enabled
Redundancy Status        : Up
Operating Mode           : Message Routing Node
Switchover Mechanism     : Hostlist
Auto Revert              : No
Redundancy Mode          : Active/Standby
Active-Standby Role      : Primary
Mate Router Name         : solace_02
ADB Link To Mate         : Up
ADB Hello To Mate        : Up

                               Primary Virtual Router  Backup Virtual Router
                               ----------------------  ----------------------
Activity Status                Local Active            Shutdown
Routing Interface              intf0:1                 intf0:1
Routing Interface Status       Up                      
VRRP Status                    Initialize              
VRRP Priority                  250                     
Message Spool Status           AD-Active               
Priority Reported By Mate      Standby

The output of the show redundancy command would look similar to the following for the backup broker:

solace_02# show redundancy 

Configuration Status     : Enabled
Redundancy Status        : Up
Operating Mode           : Message Routing Node
Switchover Mechanism     : Hostlist
Auto Revert              : No
Redundancy Mode          : Active/Standby
Active-Standby Role      : Backup
Mate Router Name         : solace_01
ADB Link To Mate         : Up
ADB Hello To Mate        : Up

                               Primary Virtual Router  Backup Virtual Router
                               ----------------------  ----------------------
Activity Status                Shutdown                Mate Active
Routing Interface              intf0:1                 intf0:1
Routing Interface Status                               Up
VRRP Status                                            Initialize
VRRP Priority                                          100
Message Spool Status                                   AD-Standby
Priority Reported By Mate                              Active

Increase the Connection Scaling Tier

All event brokers within an HA group must be configured to use the same connection scaling tier. If this is misconfigured, HA will remain operationally down. You can use the show redundancy command to check operational states.

For replicated sites, the primary and replication event broker sites should have the same resources and scaling tiers.

  • The connection scaling tier configuration is not automatically synchronized. For further information, refer to Config-Sync Configuration.
  • This procedure changes the system-wide max-connections. After completing this procedure, you can then modify the maximum number of connections permitted for a specific Message VPN (Configuring Maximum Connections) or for clients using a specific client profile (see Configuring Services).

To increase the connection scaling tier for an HA group, do the following:

  1. On the backup event broker, shut down the message backbone service:

    solace_02(configure)# service
    solace_02(configure/service)# msg-backbone
    solace_02(configure/service/msg-backbone)# shutdown
    solace_02(configure/service/msg-backbone)# exit
    solace_02(configure/service)# exit

  2. On the backup event broker, shut down the message spool:

    solace_02(configure)# hardware message-spool shutdown
    All message spooling will be stopped
    Do you want to continue (y/n)? y

  3. On the primary event broker, shut down the message backbone service:

    solace_01(configure)# service
    solace_01(configure/service)# msg-backbone
    solace_01(configure/service/msg-backbone)# shutdown
    solace_01(configure/service/msg-backbone)# exit
    solace_01(configure/service)#exit

  4. On the primary event broker, shut down the message spool:

    solace_01(configure)# hardware message-spool shutdown
    All message spooling will be stopped
    Do you want to continue (y/n)? y

  5. If you need to increase the system resources provisioned for your primary and backup event brokers to meet the connection scaling tier you want to use, perform the following sub-steps:
    1. Stop the primary event broker:
      • If you are running a cloud or machine image, stop the Solace PubSub+ service on the host by running the following solacectl command from the Linux host shell as root:
        solacectl service stop
      • If you are running a Docker container, stop the container using the stop command:
        sudo docker stop [OPTIONS] CONTAINER [CONTAINER...]
    2. Stop the backup event broker:
      • If you are running a cloud or machine image, stop the Solace PubSub+ service on the host by running the following solacectl command from the Linux host shell as root:
        solacectl service stop
      • If you are running a Docker container, stop the container using the stop command:
        sudo docker stop [OPTIONS] CONTAINER [CONTAINER...]
    3. In your virtual machine manager or cloud environment, increase the provisioning of the primary and backup event brokers in accordance with the system resources listed in Scaling Tiers for Software Event Brokers.
    4. Start the primary event broker, and log in as admin.
  6. On the primary event broker, increase the connection limit:

    solace_01(configure)# system
    solace_01(configure/system)# scaling
    solace_01(configure/system/scaling)# max-connections <connection-limit>

    Where:

    connection-limit is the max number of client connections to allocate to the software event broker.

    The event broker will automatically reboot when the max-connections is confirmed.

  7. In the Solace CLI, enable the message spool for the primary event broker:

    solace_01(configure)# no hardware message-spool shutdown

  8. On the primary event broker, enable the message backbone service:

    solace_01(configure)# service
    solace_01(configure/service)# msg-backbone
    solace_01(configure/service/msg-backbone)# no shutdown

  9. On the primary event broker, verify that the message spool’s Operational Status is AD-Active:

    solace_01(configure/service/msg-backbone) show message-spool

    :  The primary message spool status must be AD-Active before continuing with this procedure or message loss will occur.

  10. Optional: If you increased the system resources in Step 5, start the backup event broker, and log in as admin.
  11. On the backup event broker, increase the connection limit:

    solace_02(configure)# system
    solace_02(configure/system)# scaling
    solace_02(configure/system/scaling)# max-connections <connection-limit>

    Where:

    connection-limit is the max number of client connections to allocate to the software event broker.

    The event broker will automatically reboot when the max-connections is confirmed.

  12. In Solace CLI, enable the message spool for the backup event broker:

    solace_02(configure)# no hardware message-spool shutdown

  13. On the backup event broker, enable the message backbone service:

    solace_02(configure)# service
    solace_02(configure/service)# msg-backbone
    solace_02(configure/service/msg-backbone)# no shutdown

  14. On the backup event broker, verify that the message spool’s Operational Status is AD-Standby:

    solace_02(configure/service/msg-backbone)# show message-spool

  15. Verify that the Redundancy Status is Up on all nodes in the HA group:

    On the primary event broker:

    solace_01> show redundancy

    On the backup event broker:

    solace_02> show redundancy

    On the monitoring node:

    solace-monitoring> show redundancy