Appliance Event Broker Health Check
You can perform a health check of self-managed Solace Appliance Event Brokers. These health checks are useful to:
-
self-serve health checks after a maintenance activity.
- identify required maintenance or upgrades for your appliance event broker.
The steps for the health check presume that you are familiar with:
- operating Solace Appliance Event Brokers, specifically the hardware components and maintenance procedures. For more information, see Hardware Maintenance.
- using the Solace Event Broker CLI and can interpret responses from running operational and configuration commands.
- have an understanding of networking concepts.
All examples provided are for illustrative purposes and have placeholder text to protect sensitive information, such as serial numbers and MAC addresses.
Here is an overview of the checks that Solace recommends you perform to assess the health of your appliance event brokers. Before you begin the health check, review the examples and steps:
- Part 1: Chassis and Broker Release (SolOS) Checks
- Verify that your appliance event broker chassis and broker release are in support.
- Part 2: System Stability Checks
- Verify that the appliance event broker has no stability issues, such as recent power failures or restarts.
- Part 3: Appliance Event Broker Hardware Status Checks
- Verify the hardware stability on the appliance event broker.
- Part 4: Network Connectivity Status Checks
- Verify the connectivity to the NTP/PTP servers and DNS servers.
- Part 5: Message-Spool Status Checks
- Verify the status of the Message Spool status.
- Part 6: Redundancy Checks
- Verify that redundancy is running. Perform these checks only if redundancy is configured on the appliance event broker.
You can use the following checklist to track the health check results of your appliance event brokers. If any part of the health check fails, you can choose to stop your health checks for the appliance event broker and contact Solace.
Part 1: Chassis and Broker Release (SolOS) Checks
For any appliance event broker, you first check that the chassis and installed event broker software (SolOS) are in support.
Part 1.1: Verifying that the Installed Broker Release (SolOS) Is Supported
Ensure that the installed broker release (SolOS) on your Solace Appliance Event Broker is in support. To see the support dates for event broker releases and SolOS versions, see Support Dates for Release Versions.
Use the show version command in the Solace Event Broker CLI to check the version on your appliance event broker. In the following example, the broker release is 10.25.0.
Copyright 2004-2025 Solace Corporation. All rights reserved. solace> show hostname Hostname: solace Deferred hostname: solace solace> show version ... ... Solace 3560 Version 10.25.0.74 [...]
Part 1.2: Checking the Chassis Is Supported
You must ensure that the chassis product number for your appliance event broker is in support. To check whether your Solace Appliance Event Brokers list of out-of-support, check the chassis number:
-
does not appear in the table on the Legacy Lifecycle Policy
-
does not appear on the Product Lifecycle Policy, then it is still generally available and not end of sale
If your chassis for your appliance event broker does appear in the table in the "Product Milestones" section on the page, validate that your chassis is still in support.
solace> show hardware details Platform: Solace 3560 Chassis Product #: CHS-3560AC-05-A Ensure that Chassis Number is still in support. Chassis revision: <chassis revision number> Chassis serial: <serial number> Board serial: <board serial> Board Part Number: <board part number> BIOS Version: <BIOS> CPU1 Version: <CPU version, model, and clock speed> CPU2 Version: <CPU version, model, and clock speed> System Memory: < Memory in GiB>
Part 2: System Stability Checks
For an appliance event broker, always check the stability of the system. To check stability of a system, you can look at recent and past activities, and see whether there have been any recent Power-On Self Test (POST) failures. If redundancy is configured, ensure that you verify the stability on both appliance event brokers.
Part 2.1: Checking the System Uptime and Last Restart Reason
You can check the system up-time and last restart reason to determine if the appliance event broker has rebooted recently and whether this reboot was expected. For more information, see Last Restart Reason.
Use the show system command in the Solace Event Broker CLI to check the system uptime and last restart reason. For example:
solace> show system System Uptime: 852d 4h 5m 26s Last Restart Reason: User request [...]
Part 2.2: Checking recent SYSTEM_* Events
You can use the show log system find <log> command. Any SYSTEM_CHASSIS_* or SYSTEM_SYSTEM_HEALTH_* logs may indicate issues on the appliance event broker. For more information about system logs, see Monitoring Events Using Syslog and Syslog Event Reference. For example:
solace> show log system find SYSTEM_CHASSIS solace> show log system find SYSTEM_SYSTEM_HEALTH
Part 2.3: Checking for POST Failures
You can check for any Power-On Self Test (POST) failures from the last reboot of the appliance event broker using the show system post command in the CLI. For example:
solace> show system post Overall Power-On Self Test (POST) Status: PASSED [...]
Part 3: Appliance Event Broker Hardware Status Checks
Depending on the model and configuration of the appliance event broker, check the health of the:
- power modules
- NAB (Network Acceleration Blade)
- HBA (Host Bus Adapter)
- ADB (Assured Delivery Blade)
Part 3.1: Checking the Power Module Status
The Solace 3530s and Solace 3560s have two redundant AC hot-swappable power supplies. Verify that both power modules are in the OK state using the show hardware detail command in the CLI. For example:
solace> show hardware detail [...] Power redundancy configuration: 1+1 Operational power supplies: 2 Both power supplies are operational. Power module 1: OK Module 1 is Up. Power module 2: OK Module 2 is Up. System Type: topic-routing Supported Blade Configuration: Yes [...]
Part 3.2: Checking the Status of the Network Acceleration Blade
Ensure that the Network Acceleration Blade (NAB) interface configuration is in the expected state. All Configured members of a given LAG interface should also appear in the Available members field. If this is not the case, inspect the physical interface to determine why it is unavailable. For example:
solace> show interface detail [...] Interface: 1/6/lag2 MAC address: <some MAC Address> Mode: LACP Enabled: yes Operational State: Up Last Failure Reason: N/A Last Failure Time: N/A Rx pkts: 307671432372 Rx bytes: 92106845229222 Tx pkts: 463909976538 Tx bytes: 407609381953533 Configured members: 1/6/5 1/6/6 1/6/7 1/6/8 Available members: 1/6/5 1/6/6 1/6/8 Operational members: 1/6/5 1/6/6 1/6/8 Interface is missing 1/6/7 as an operational member in this LAG interface 1/6/LAG2. Primary member: N/A [...] Interface: 1/6/7 MAC address: 70:b3:d5:0a:3d:54 Enabled: yes Operational State: Up Last Failure Reason: N/A Last Failure Time: N/A Rx pkts: 73809712667 Rx bytes: 22839861709128 Tx pkts: 89442733870 Tx bytes: 65817270597591 Link detected: no Interface 1/6/7 is not operational because the NAB does not detect any physical connection over the interface. Media type: 10G Base-SR Speed: 10 Gbps Duplex: full Egress traffic shaping Admin Status: disabled Oper Status: down(shutdown) Admin Rate Limit: 1000000000 Mbps Oper Rate Limit: 10000 Mbps
You can also download and check the system.logfile for any SYSTEM_NAB_* events. Any SYSTEM_NAB_* events may indicate issues or required maintenance for the NAB. For example:
grep "SYSTEM_NAB_*" system.log
Part 3.3: Checking the Status of the Host Bus Adapter
Ensure that both Fibre-Channels 1 & 2 on the Host Bus Adapter (HBA) have a Link State of Link Up using the show interface detail command in the CLI. For example:
solace> show interface detail
[...]
Slot 1/7: Host Bus Adapter Blade
Product #: HBA-0208FC-02-A
Serial #: <serial number>
Model Name: QLE2562
Model Description: PCI-Express Dual Channel 8Gb Fibre Channel HBA
Driver Version: 10.02.00.103-k
Fibre-Channel 1
Operational State: Online
Link State: Link Up - F_Port (fabric via point-to-point) Check that Link State
is Link Up.
Link Speed: 8 Gbit
Port Id: 0xec0240
Port Name: 0x21000024ff19a686
Port Type: NPort (fabric via point-to-point)
Node Name: 0x20000024ff19a686
Error Statistics:
Invalid CRC Count: 0
Invalid Tx Words Count: 0
Link Failure Count: 2
Loss of Signal Count: 1
Loss of Sync Count: 1
Primitive Sequence Protocol Error Count: 0
Fibre-Channel 2
Operational State: Online
Link State: Link Up - F_Port (fabric via point-to-point) Check that Link State
is Link Up.
Link Speed: 8 Gbit
Port Id: 0x8d01c0
Port Name: 0x21000024ff19a687
Port Type: NPort (fabric via point-to-point)
Node Name: 0x20000024ff19a687
Error Statistics:
Invalid CRC Count: 0
Invalid Tx Words Count: 0
Link Failure Count: 3
Loss of Signal Count: 1
Loss of Sync Count: 1
Primitive Sequence Protocol Error Count: 0
Part 3.4: Checking the Status of the Assured Delivery Blade
If the appliance event broker has an Assured Delivery Blade (ADB) installed:
- Ensure that the operational state of the ADB is
up. - Verify that the power module on the ADB is fully charged.
-
If the appliance event broker is configured for redundancy, ensure both ADB mate link ports 1 & 2 are in the
Okstate using theshow hardware detailin the CLI. For example:solace> show hardware detail [...] Slot 1/2: Assured Delivery Blade Product #: ADB-000000-02-A Serial #: <serial number> Operational State: Up Check that Operational State is Up. Flash Card State: Ready Power Module State: Ok Check that Power Module State is Ok. Mate Link Port 1: Ok If redundant, check that mate links are Ok. Mate Link Port 2: Ok If redundant, check that mate links are Ok. Errors: 0 Fatal errors: 0 SFP (Port 1) Details: Media Type : 3.125G Fibre-Channel Manufacturer: <manufacturer name> Part Number : <part number> Serial # : <serial number> Tx Power : -4.9935 dBm Rx Power : -4.3273 dBm SFP (Port 2) Details: Media Type : 3.125G Fibre-Channel Manufacturer: <manufacturer name> Part Number : <part number> Serial # : <serial number> Tx Power : -4.9935 dBm Rx Power : -4.9935 dBm FPGA Details: Bank 1 Bank 2 Build1 ID: 09010087 090107d4 FLASH Card Details: State: Ready Size(MB): 7168 Manufacturer: STEC M4 CF Rev:E6884-2 Serial #: STM00010D4F2 Power Module Details: State: Ok Charge Level : 100% Estimated Time Until Fully Charged: 0 minutes Mate Link Details: CRC Errors Port 1: 0 CRC Errors Port 2: 0
You can also check for logs by downloading the system.log file and searching for any SYSTEM_ADB_* logs. For example:
grep "SYSTEM_ADB_*" system.log
Part 4: Network Connectivity Status Checks
For an appliance event broker to operate properly, it requires that NTP (or PTP) and Domain Name Servers (DNS) are reachable.
Part 4.1: Checking for NTP or PTP Server Connectivity
Ensure that the appliance event brokers are configured with either Precision Time Protocol (PTP) or Network Time Protocol (NTP). The PTP and NTP servers must be reachable from the appliance event brokers for clock synchronization. For more information, see Clock Synchronization.
- For PTP:
- To check PTP connectivity, you can run the
show clock detailcommand in the CLI. Verify theProtocolisPTPandEnabledisYes. For example: solace> show clock detail Protocol: PTP Ensure that this is PTP. Enabled: Yes Ensure that this is Yes. PTP In Sync: Yes Ensure that this is Yes. NTP Server: NTP Reachable: No NTS Enabled: No [...]
- For NTP
- To check for NTP connectivity, you can run the
show clock detailcommand in the CLI. Verify theProtocolisNTP,EnabledisYes, and the specifiedNTP ReachableisYes. For example: solace> show clock detail Protocol: NTP Ensure that this is NTP. Enabled: Yes Ensure that this is Yes. PTP In Sync: No NTP Server: 129.6.15.28 NTP Reachable: Yes Ensure that the NTP server is reachable. [...]
Part 4.2: Checking the DNS Server Is Reachable
An appliance event broker can have up to three DNS servers configured.
You can run the show dns command in CLI and then ensure that any configured DNS servers have a Status of Up. Any DNS server in the down state indicates that the DNS server cannot resolve the configurable Polled Domain Name. For example:
solace> show dns Search Domain List : Polled Domain Name : www.mycompany.com Last Refreshed Time : Wed Sep 17 16:33:21 2025 Name Server Status Source ----------------------------------------- -------------- ------- 8.8.8.8 up system Ensure that Status is Up. 192.168.1.10 up system Ensure that Status is Up. 47.19.95.10 up system Ensure that Status is Up.
Part 5: Message-Spool Status Checks
You can verify the operational status of the message spool on the appliance event brokers if you have it configured. If you have redundancy configured, you should verify the status on both appliance event brokers.
Part 5.1: Verifying the Operational Status of the Message-Spool
If the message-spool has been configured and enabled on the appliance event broker, verify that the:
Config Statusof the message-spool isEnabled-
Operational Statusof the Message Spool on the event broker isAD-ActiveIf redundancy is configured, on the active event broker is
AD-Activeand the standby event broker isAD-Standby.
For example, you can run the show message-spool detail command in the CLI on the active event broker.
solace> show message-spool detail Config Status: Enabled (Primary) Ensure status is Enabled. Virtual Router When Active-Active: Primary Maximum Spool Usage: 60000 MB Spool While Charging: No Spool Without Flash Card: No Using Internal Disk: No Disk Array WWN: 60:0a:09:80:00:f8:c4:a7:00:00:7e:2a:65:54:cb:af Operational Status: AD-Active Ensure status is AD-Active (active) or AD-Standby (standby). Datapath Status: Up Synchronization Status: Synced Max Queue Messages: 500M Queue Message Resource Utilization: 0.00% Transaction Resource Utilization: 0.00% Delivered Unacked Msgs Utilization: 0.00% Spool Files Utilization: 0.00% Active Disk Partition Usage: 1.47% Standby Disk Partition Usage: 0.00% Next Message Id: 35207
Part 6: Redundancy Checks
If redundancy is configured, Solace recommends that you perform redundancy checks on the appliance event brokers. Perform on the following checks depending on whether you have Active/Active or Active/Standby configuration for redundancy.
- Part 6.1A: Checking Redundancy for Active/Active Configurations
- Part 6.1B: Checking Active/Standby Redundancy Configurations
For more information, see High Availability for Appliance Event Brokers.
Ensure that you perform the following check regardless of which configuration you use for redundancy:
For more information about Config-Sync, see Config-Sync.
Part 6.1A: Checking Redundancy for Active/Active Configurations
For an Active/Active redundancy configuration, the check you perform depends on whether Guaranteed messaging is configured on the appliance event broker:
- If Guaranteed Messaging Is Not Configured (Message-Spool Disabled)
- On Active/Active event brokers that do not have Guaranteed messaging configured, the
Message Spool Statusshould show asAD-Disabled. -
Status to Check When Appliance is Active/Active Appliance 1 Appliance 2 Configuration Status Enabled Enabled Redundancy Status Up Up Redundancy mode Active/Active Active/Active Activity Status Primary Virtual Router Local Active Local Active Backup Virtual Router Mate Active Mate Active Message Spool Status Primary Virtual Router AD-Disabled AD-Disabled Backup Virtual Router AD-Disabled AD-Disabled
You can run the show redundancy command in the CLI for Appliance 1 and Appliance 2.
For example, on Appliance 1:
solace-appliance1# show redundancy Configuration Status : Enabled Ensure status is Enabled. Redundancy Status : Up Ensure status is Up. Last Failure Reason : VRRP state down Last Failure Time : Jul 6 2023 07:31:08 EDT Auto Revert : No Redundancy Mode : Active/Active Active-Standby Role : None Ensure status None. There are issues if not. Mate Router Name : appliance2 ADB Link To Mate : Up This can be Up or Down. ADB Hello To Mate : Down Failover Criteria : Any Fail Interface Primary Address Status Backup Address Status ---------------- ------------------------ ------ ------------------------ ------ 1/6/1 192.168.160.101 Up 192.168.160.102 Down Primary Virtual Router Backup Virtual Router ---------------------- ---------------------- Activity Status Local Active Mate Active Ensure Activity Status is Local Active on the Primary Virtual Router and Mate Active on the Backup Virtual Router. VRRP VRID 68 70 Redundancy Interface Status Up Up VRRP Status 1/6/1 Master Backup VRRP Priority 250 100 Message Spool Status AD-Disabled AD-Disabled Ensure Message Spool status is AD-Disabled/AD-Disabled.
For example, on Appliance 2:
solace-appliance2# show redundancy Configuration Status : Enabled Ensure status is Enabled. Redundancy Status : Up Ensure status is Up. Last Failure Reason : VRRP state down Last Failure Time : Jul 6 2023 07:31:08 EDT Auto Revert : No Redundancy Mode : Active/Active Active-Standby Role : None Ensure status None. Mate Router Name : appliance1 ADB Link To Mate : Up This can be Up or Down. ADB Hello To Mate : Up Failover Criteria : Any Fail Interface Primary Address Status Backup Address Status ---------------- ------------------------ ------ ------------------------ ------ 1/6/lag1 192.168.160.102 Up 192.168.160.101 Down Primary Virtual Router Backup Virtual Router ---------------------- ---------------------- Activity Status Local Active Mate Active Ensure Activity Status is Local Active on the Primary Virtual Router and Mate Active on the Backup Virtual Router. VRRP VRID 70 68 Redundancy Interface Status Up Up VRRP Status 1/6/lag1 Master Backup VRRP Priority 250 100 Message Spool Status AD-Disabled AD-Disabled Ensure Message Spool status is AD-Disabled/AD-Disabled.
- Guaranteed Messaging Is Configured (When Message-Spool Enabled)
- On Active/Active event brokers that has Guaranteed messaging configured, the
Message Spool Statusshould show asAD-Active. Check the following status: -
Status to Check When Appliance is Active/Active Appliance 1 Appliance 2 Configuration Status Enabled Enabled Redundancy Status Up Up Redundancy mode Active/Active Active/Active Activity Status Primary Virtual Router Local Active Local Active Backup Virtual Router Mate Active Mate Active Message Spool Status Primary Virtual Router AD-Active AD-Disabled Backup Virtual Router AD-Disabled AD-Standby
You can run the show redundancy command in the CLI for Appliance 1 and Appliance 2.
For example, on appliance 1:
solace-appliance1# show redundancy Configuration Status : Enabled Ensure status is Enabled. Redundancy Status : Up Ensure status is Up. Last Failure Reason : VRRP state down Last Failure Time : Jul 6 2023 07:31:08 EDT Auto Revert : No Redundancy Mode : Active/Active Active-Standby Role : None Ensure status None. There are issues if not. Mate Router Name : appliance2 ADB Link To Mate : Up This can be Up or Down. ADB Hello To Mate : Down Failover Criteria : Any Fail Interface Primary Address Status Backup Address Status ---------------- ------------------------ ------ ------------------------ ------ 1/6/1 192.168.160.101 Up 192.168.160.102 Down Primary Virtual Router Backup Virtual Router ---------------------- ---------------------- Activity Status Local Active Mate Active Ensure Activity Status is Local Active on the Primary Virtual Router and Mate Active on the Backup Virtual Router. VRRP VRID 68 70 Redundancy Interface Status Up Up VRRP Status 1/6/1 Master Backup VRRP Priority 250 100 Message Spool Status AD-Active AD-Disabled Ensure Message Spool status is AD-Active/AD-Disabled.
For example, on Appliance 2:
solace-appliance2# show redundancy Configuration Status : Enabled Ensure status is Enabled. Redundancy Status : Up Ensure status is Up. Last Failure Reason : VRRP state down Last Failure Time : Jul 6 2023 07:31:08 EDT Auto Revert : No Redundancy Mode : Active/Active Active-Standby Role : None Ensure status None. Mate Router Name : appliance1 ADB Link To Mate : Up This can be Up or Down. ADB Hello To Mate : Up Failover Criteria : Any Fail Interface Primary Address Status Backup Address Status ---------------- ------------------------ ------ ------------------------ ------ 1/6/lag1 192.168.160.102 Up 192.168.160.101 Down Primary Virtual Router Backup Virtual Router ---------------------- ---------------------- Activity Status Local Active Mate Active Ensure Activity Status is Local Active on the Primary Virtual Router and Mate Active on the Backup Virtual Router. VRRP VRID 70 68 Redundancy Interface Status Up Up VRRP Status 1/6/lag1 Master Backup VRRP Priority 250 100 Message Spool Status AD-Disabled AD-Standby Ensure Message Spool status is AD-Disabled/AD-Standby.
Part 6.1B: Checking Active/Standby Redundancy Configurations
If you have Active/Standby configuration, the checks to assess the health of your appliances depend on whether the primary or backup appliance event broker configured is active.
- When the Primary Appliance Is Active
- When the primary appliance event broker is active in an Active/Active redundancy configuration, ensure that you see the following statuses when you run the
show redundancycommand in the CLI on the primary and backup appliance event brokers when the primary appliance event broker is Active. -
Status to Check When the Primary Appliance is Active Primary Appliance Backup Appliance Configuration Status Enabled Enabled Redundancy Status Up Up Active-Standby Role Primary Backup Activity Status Primary Virtual Router Local Active Shutdown Backup Virtual Router Shutdown Mate Active Message Spool AD-Active AD-Standby
For example, on the primary appliance (Primary is Active):
solace-primary> show redundancy Configuration Status : Enabled Ensure status is Enabled. Redundancy Status : Up Ensure status is Up. Auto Revert : No Redundancy Mode : Active/Standby Active-Standby Role : Primary Ensure status is Primary since it is Active. Mate Router Name : lab-129-77 ADB Link To Mate : Up ADB Hello To Mate : Up Failover Criteria : Any Fail Interface Primary Address Status Backup Address Status ---------------- ------------------------ ------ ------------------------ ------ 1/1/1 192.168.164.108 Up Primary Virtual Router Backup Virtual Router ---------------------- ---------------------- Activity Status Local Active Shutdown Ensure Activity Status is Local Active on Primary, and Shutdown on Backup. VRRP VRID 8 Redundancy Interface Status Up VRRP Status 1/1/1 Master VRRP Priority 250 Message Spool Status AD-Active Ensure Message Spool status is AD-Active. Priority Reported By Mate Standby Backup Broker
For example, on the backup appliance event broker (Primary is Active):
solace-backup> show redundancy Configuration Status : Enabled Ensure the status is Enabled. Redundancy Status : Up Ensure status is Up. Auto Revert : No Redundancy Mode : Active/Standby Active-Standby Role : Backup Ensure status is Backup since the Primary is Active. Mate Router Name : lab-129-8 ADB Link To Mate : Up ADB Hello To Mate : Up Failover Criteria : Any Fail Interface Primary Address Status Backup Address Status ---------------- ------------------------ ------ ------------------------ ------ 1/1/1 192.168.164.108 Down Primary Virtual Router Backup Virtual Router ---------------------- ---------------------- Activity Status Shutdown Mate Active Ensure Primary Virtual Router is Shutdown and Backup Virtual Router is Mate Active. VRRP VRID 8 Redundancy Interface Status Up VRRP Status 1/1/1 Backup VRRP Priority 100 Message Spool Status AD-Standby Ensure Message Spool status is AD-Standby. Priority Reported By Mate Active
- When the Backup Appliance Event Broker is Active
- When the backup appliance event broker is active in an Active/Standby configuration for redundancy, ensure that you see the following statuses when you run the
show redundancycommand in the CLI on the primary and backup appliance event brokers: -
Status to Check When the Backup Appliance is Active Primary Appliance Backup Appliance Configuration Status Enabled Enabled Redundancy Status Up Up Active-Standby Role Backup Primary Activity Status Primary Virtual Router Mate Active Shutdown Backup Virtual Router Shutdown Local Active Message Spool AD-Standby AD-Active
For example, on the primary appliance event broker (Backup is Active):
solace-primary> show redundancy Configuration Status : Enabled Ensure this is Enabled. Redundancy Status : Up Ensure this is Up. Auto Revert : No Redundancy Mode : Active/Standby Active-Standby Role : Primary Mate Router Name : lab-128-59 ADB Link To Mate : Up ADB Hello To Mate : Up Failover Criteria : Any Fail Interface Primary Address Status Backup Address Status ---------------- ------------------------ ------ ------------------------ ------ 1/6/1 192.168.160.158 Down Primary Virtual Router Backup Virtual Router ---------------------- ---------------------- Activity Status Mate Active Shutdown Ensure Primary Virtual Router is Mate Active and Backup Virtual Router is Shutdown. VRRP VRID 158 Redundancy Interface Status Up VRRP Status 1/6/1 Backup VRRP Priority 150 Message Spool Status AD-Standby Priority Reported By Mate Active
For example, on the backup appliance (Backup is Active):
solace-backup> show redundancy Configuration Status : Enabled Ensure status is Enabled. Redundancy Status : Up Ensure status is Up. Auto Revert : No Redundancy Mode : Active/Standby Active-Standby Role : Backup Mate Router Name : lab-128-58 ADB Link To Mate : Up ADB Hello To Mate : Up Failover Criteria : Any Fail Interface Primary Address Status Backup Address Status ---------------- ------------------------ ------ ------------------------ ------ 1/6/1 192.168.160.158 Up Primary Virtual Router Backup Virtual Router ---------------------- ---------------------- Activity Status Shutdown Local Active Ensure Primary Virtual Router is Shutdown and Backup Virtual Router is Local Active. VRRP VRID 158 Redundancy Interface Status Up VRRP Status 1/6/1 Master VRRP Priority 240 Message Spool Status AD-Active Priority Reported By Mate Standby
Part 6.2: Checking the Config-Sync Status
Config-Sync is an important aspect of the redundancy configuration on the appliance event brokers. You can run the show config-sync command in the CLI to check the operational status of Config-Sync.
Note: Config-sync requires that the message-spool configuration is correct and in an up status to operate.
Note: When you enable Config-Sync for the first time on a High-Availability (HA) pair, you must assert the system-level configuration of one event broker over its mate. For more information, see Config-Sync Configuration.
Config-Sync on the Primary Appliance Event Broker
Ensure that Config-Sync is enabled and up on the primary event broker. You can run the show config-sync command in the CLI. For example:
solace> show config-sync Admin Status : Enabled Ensure status is Enabled. Oper Status : Up Ensure status is Up. [...]
Config-Sync on the Backup Appliance Event Broker
Ensure that Config-Sync is enabled and up on the backup event broker. You can run the show config-sync command in the CLI. For example:
solace-backup> show config-sync Admin Status : Enabled Ensure status is Enabled. Oper Status : Up Ensure status is Up. [...]