Monitoring Redundancy

This section discusses the show commands that you can use to view the configuration and state of Solace PubSub+ appliances used in HA deployments.

To view the redundancy configuration and status of an appliance, enter the following show command:

solace1> show redundancy [detail]

Where:

detail specifies that detailed information on the redundancy configuration should be shown.

:  To read descriptions of many of the show commands' output values, enter a ? at the end of the command (for example, solace1> show redundancy ?).

When no parameters are entered, the following summary information is displayed:

  • Configuration Status indicates whether system redundancy is:
    • “Enabled”—redundancy is started on the event broker.
    • “Shutdown”—redundancy is stopped on the event broker.
    • “Released”—the event broker is surrendering activity to its mate event broker.
  • Redundancy Status indicates whether the system redundancy operational state:
    • “Up”—the event broker is operational and available to provide service.

      :  When only VRRP is available (that is, no ADB mate link is established), check that the redundancy status is "Up" on both event brokers. It is also possible to configure a neighbor link between the event brokers so that you only monitor one event broker—the neighbor link will provide the mate status necessary to properly determine the state.

    • “Down”—the event broker is not operational and is unavailable to provide service.
  • Auto-Revert indicates whether auto-revert is enabled or disabled (refer to Enabling Auto-Revert).
  • Redundancy Mode indicates the redundancy mode being provided (Active/Active, Active/Standby, or None). This state is derived from the redundancy and IP interface configuration.
  • Active-Standby Role indicates the configured active-standby-role (refer to Assigning the Active/Standby Role).
  • Failover Criteria indicates the conditions that trigger an activity switch (refer to Specifying the Redundancy Fail-Over Criteria ).
  • A list of configured redundancy interfaces (refer to Assigning a Redundancy Interface).
  • a table with redundancy information for each virtual router:
    • the activity status as described in the General Status Items table (Local Active or Mate Active).
    • the VRRP VRID.
    • the overall state of the redundancy interfaces.
    • the VRRP status for the VRID as described in General Status Items table (Master, meaning the local event broker is active for the VRID from a VRRP viewpoint, or Backup, meaning the remote event broker is active for the VRID from a VRRP viewpoint).
    • the VRRP priority with which the local event broker is advertising (0-255).

If the detail parameter is provided, the following additional information is displayed:

  • The primary event broker for the virtual router (that is, the physical address of the event broker that owns the VRID).
  • The “Up” or “Down” state of the link between the local and backup event broker.
  • The current priority reported by the mate event broker for the VRID, which is the highest of the priorities that the remote event broker is advertising over CSPF, VRRP and the ADB Hello Protocol as described in the Local Priority Level Descriptions (Assert-Activity, Active, Standby, Primary-Reconcile, Backup Reconcile, or Release).
  • Refer to the following tables for further explanation of the additional information displayed:
    • General Status Items—describes the general status items for the virtual routers.
    • Redundancy Status Items—indicates whether the redundancy facility believes the event broker is in a state where it could provide service for VRID.
    • SMRP Status Items—indicates whether Subscription Management Routing Protocol (SMRP) is ready to provide service for the VRID.
    • Message Spool Status Items—indicates the readiness of the message spool facility to provide Guaranteed messaging for the VRID.

General Status Items

Item

Values

Activity Status—Whether the local event broker is active for the VRID.

  • Local Active—The local event broker is active for the specified VRID.
  • Mate Active—The mate event broker is active for the specified VRID.
  • Subscriptions Pending—The local event broker has not yet taken activity for the virtual router because it is in the process of adding internal management subscriptions (for example, #P2P/v:<router-name>/#client/>).
  • Shutdown—Redundancy is shutdown.
  • Local Inactive—The local event broker should be "Local Active", but some preconditions are not being met, preventing it from transitioning. Use the show redundancy detail User EXEC command to investigate further.

VRRP Status—Whether the local event broker owns the VRID from the viewpoint of the VRRP.

  • Master
  • Backup

Priority Reported By Mate—The priority the local event broker is announcing for the VRID.

  • Assert Activity
  • Active
  • Standby
  • Primary Reconcile
  • Backup Reconcile
  • Release

Subscriptions Pending—The local event broker has not yet taken activity for the virtual router because it is in the process of adding internal management subscriptions for the virtual router.

Example:

#SEMP/v:<router-name>/>

#P2P/v:<router-name>/#client/>

Local Priority Level Descriptions

Level

Description

Assert-Activity

The priority level the virtual router uses when it wants to assert itself as the “master” of the VRID. After a timeout period, when the virtual router is sure that the mate event broker does not claim to be the “master”, the local priority value for the virtual router is reduced to Active.

Active

The normal priority level to indicate that the virtual router is currently active.

Standby

The priority level that a backup virtual router uses to advertise that it is not currently active, but it is capable of taking activity if the primary virtual router unavailable.

Primary-Reconcile

The priority level that a virtual router uses on start up, to ensure that it does not take activity before it is ready.

Backup-Reconcile

The priority level that a backup virtual router uses to indicate that it is initializing, and it will not be able to take activity even if the primary virtual router is unavailable.

Release

The priority level that a virtual router uses to indicate that it is no longer willing to act on behalf of the IP address. This priority level is advertised when the release-activity Redundancy CONFIG command is used. It is also the priority advertised for the backup virtual router whenever the redundancy feature is shutdown on the virtual router.

1. There are a number of event broker priority levels defined for redundancy, which are advertised by the virtual routers. When activity switches occur between mates, the advertised priority levels for each appliance change to indicate their current state and role. These advertisements are broadcast between redundant pairs through VRRP. For example, the virtual router that advertises the highest priority level for a given VRID is the active virtual router for that VRID. All messages and system requests for that VRID are then forwarded to that virtual router.

Redundancy Status Items

Item

Values

Configuration Status—The event broker's redundancy configuration status.

  • Enabled
  • Release
  • Shutdown

Message Spool Status—Whether the message spool is ready to provide Guaranteed Messaging.

  • Ready
  • Not Ready

SMRP Status Items

Item

Values

DB Build Status—Whenever redundancy is enabled on an event broker, it can take up to a minute to ready the database for taking activity from its mate event broker on demand.

  • Ready
  • Not Ready (% complete)

DB Sync Status—When an event broker is restarted while running Multi-Node Routing, it must synchronize its database with its neighbor event brokers to learn of the subscriptions it will become active for. This value indicates the SMRP synchronization status.

Note:  If synchronization to any neighbor event broker is not completed within three minutes, then SMRP stops trying to synchronize its database to that event broker.

  • Ready
  • Not Ready

Message Spool Status Items

Item

Values

Message Spool Config Status—The config status of message spooling on the Guaranteed Messaging VRID.

  • Enabled
  • Shutdown

VRID Config Status—The local Guaranteed Messaging VRID configuration matches what has been reported by the ADB.

  • Ready
  • Config Mismatch

ADB Status—The high-level status of the ADB.

  • Not Ready
  • Ready

Flash Module Status—The high-level status of the Flash Memory Module on the ADB.

  • Not Ready
  • Ready

Power Module Status—The high-level status of the power module on the ADB.

  • Not Ready
  • Ready

ADB Contents—Is the ADB contents valid.

  • Invalid
  • Stale
  • Ready

Disk Status—The status of the external disk storage array.

  • Not Ready
  • Ready

Disk Contents—Whether the spool file directory on the external disk storage array appears to be valid. This value will generally be “Unknown” on an event broker that is not active.

  • Unknown
  • Mount Error
  • Invalid
  • Stale
  • Ready

ADB Datapath Status—Whether the ADB datapath is able to spool messages.

  • Ready
  • Not Ready

Internal Redundancy State—The internal state of the Guaranteed Messaging Redundancy facility.

  • AD-Activating
  • AD-Active
  • AD-Disabled
  • AD-NotReady
  • AD-Standby
  • AD-Unknown