CLI Configuration of Scaling Tiers for HA Groups

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

Before you begin

Verify that HA is operationally up on all event brokers in the HA group. You can use the show redundancy command to check operational states.

Step 1: Review System Resource Requirements

Before increasing the connection scaling tiers, review the available tiers and the system resources required to support each one. See Scaling Tiers for Software Event Brokers.

Step 2: 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.

Note  
  • The connection scaling tier configuration is not Config-Sync’d. For further information on Config-Sync, 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 standby event broker, shut down the message backbone service:

    solace-standby(configure)# service
    solace-standby(configure/service)# msg-backbone
    solace-standby(configure/service/msg-backbone)# shutdown
    solace-standby(configure/service/msg-backbone)# exit
    solace-standby(configure/service)# exit

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

    solace-standby(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-primary(configure)# service
    solace-primary(configure/service)# msg-backbone
    solace-primary(configure/service/msg-backbone)# shutdown
    solace-primary(configure/service/msg-backbone)# exit
    solace-primary(configure/service)#exit

  4. On the primary event broker, shutdown the message spool:

    solace-primary(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. Power down the primary event broker:

      solace-primary# power-down
      Do you want to continue (y/n)? y

      The event broker will shut down and power itself off.

    2. Power down the standby event broker:

      solace-standby# power-down
      Do you want to continue (y/n)? y

      The event broker will shut down and power itself off.

    3. In your virtual machine manager or cloud environment, it is recommended to 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-primary(configure)# system
    solace-primary(configure/system)# scaling
    solace-primary(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-primary(configure)# no hardware message-spool shutdown

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

    solace-primary(configure)# service
    solace-primary(configure/service)# msg-backbone
    solace-primary(configure/service/msg-backbone)# no shutdown

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

    solace-primary(configure/service/msg-backbone) show message-spool

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

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

    solace-standby(configure)# system
    solace-standby(configure/system)# scaling
    solace-standby(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.

  13. In Solace CLI, enable the message spool for the standby event broker:

    solace-standby(configure)# no hardware message-spool shutdown

  14. On the standby event broker, enable the message backbone service:

    solace-standby(configure)# service
    solace-standby(configure/service)# msg-backbone
    solace-standby(configure/service/msg-backbone)# no shutdown

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

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

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

    On the primary event broker:

    solace-primary> show redundancy

    On the backup event broker:

    solace-standby> show redundancy

    On the monitoring node:

    solace-monitoring> show redundancy