Adding Redundancy Interfaces to an HA Pair

This procedure describes how to add a second redundancy interface to each appliance event broker in an existing HA pair of appliance event brokers. The procedure does not cause loss of client service, however, redundancy must be disabled for a period of time during the change.

For more information about redundancy interfaces, refer to Configuring Redundancy Parameters.

Before you Begin

Before starting this procedure, verify the following:

  • You have a redundant pair of appliance event brokers deployed using an active/active or active/standby redundancy model. In this example, the appliance event brokers are deployed in a active/standby redundancy model and the primary and backup appliance event brokers are named solace-primary and solace-backup respectively.
  • The appliance event brokers are deployed with a SolOS version that includes support for multiple redundancy interfaces.
  • The message spool is enabled as primary on the primary appliance event broker and backup on the backup appliance event broker.
  • The redundancy status is Up for both appliance event brokers.
  • Both the primary and backup appliance event brokers are active for their primary virtual router.
  • Auto-revert is disabled on both appliance event brokers.
  • A single redundancy interface is configured on each appliance event broker. In this example 1/6/1 is the only redundancy interface configured on each appliance event broker.
  • The second interface you want to add has static, primary, and/or backup IP addresses configured (as needed) and operational. In this example 1/6/2 is to be added as a second redundancy interface for each appliance event broker.

Step 1: Disable Redundancy on the Primary Appliance Event Broker

Verify that the primary appliance event broker currently has activity for its own virtual router before performing this step.

To disable redundancy on the primary appliance event broker, enter the following commands:

solace-primary(configure)# redundancy
solace-primary(configure/redundancy)# shutdown

Step 2: Add the Redundancy Interface to the Primary Appliance Event Broker

To add the redundancy interface to the primary appliance event broker:

  1. Assign the redundancy interface.

    solace-primary(configure/redundancy)# vrrp
    solace-primary(configure/redundancy/vrrp)# interface 1/6/2
  2. Specify the appropriate failover criteria. For more information about the failover criteria, refer to Specifying the Redundancy Failover Criteria .

    solace-primary(configure/redundancy/vrrp)# failover-criteria {any-fail | all-fail}

Step 3: Disable Redundancy on the Backup Appliance Event Broker

Verify that the backup appliance event broker currently has activity for its own virtual router before performing this step.

To disable redundancy on the backup appliance event broker, enter the following commands:

solace-backup(configure)# redundancy
solace-backup(configure/redundancy)# shutdown

Step 4: Add the Redundancy Interface to the Backup Appliance Event Broker

To add the redundancy interface to the backup appliance event broker:

  1. Assign the redundancy interface. For more information about redundancy interfaces, refer to Configuring Redundancy Parameters.

    solace-backup(configure/redundancy)# vrrp
    solace-backup(configure/redundancy/vrrp)# interface 1/6/2
  2. Specify the appropriate failover criteria. For more information about the failover criteria, refer to Specifying the Redundancy Failover Criteria .

    solace-backup(configure/redundancy/vrrp)# failover-criteria {any-fail | all-fail}

Step 5: Enable Redundancy on Both Appliance Event Brokers

To enable redundancy on the primary appliance event broker, enter the following commands:

solace-primary(configure)# redundancy
solace-primary(configure/redundancy)# no shutdown

To enable redundancy on the backup appliance event broker, enter the following commands:

solace-backup(configure)# redundancy
solace-backup(configure/redundancy)# no shutdown

Step 6: Verify Redundancy is Working Correctly

To verify redundancy is working correctly on both appliance event brokers, issue the following show command and verify that the Redundancy Status is Up:

solace-primary(configure)# show redundancy
solace-backup(configure)# show redundancy