Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
ON THIS PAGE
 

show services redundancy-group

Syntax

Description

Display redundancy group status information for all redundancy groups or a specified redundancy group.

Options

rg-id

(Optional) Name of a specific redundancy group.
brief | extensive | terse

(Optional) Display the specified level of output. When no level is specified, display terse level output.

  • Default: terse

Required Privilege Level

view

Output Fields

Table 1 lists the output fields for the show services redundancy-group command. Output fields are listed in the approximate order in which they appear.

Table 1: show services redundancy-group Output Fields

Field Name

Field Description

Level of Output

ICCP process connection

Status of the connection between the srd and iccpd.

  • Connected

  • Not connected

all levels

Redundancy Group ID

Identifier of the redundancy group.

all levels

Number of peer RG connections

Total number of peers in the redundancy group.

brief, extensive

Local RG IP

IP address of the local redundancy group.

all levels

RS ID

terse

Local RS state

State of the local redundancy set.

  • MASTER

  • STANDBY

  • INITIALIZING

  • STANDBY (WARNED)

terse

Peer RS state

State of the peer redundancy set.

  • MASTER

  • STANDBY

  • INITIALIZING

  • STANDBY (WARNED)

terse

Peer RG IP

Peer redundancy group IP address.

all

Status

Status of redundancy group connection with this peer.

  • Connected

  • Not Connected

terse

Number of peer RG connections

Total number of peers in the redundancy group.

brief

Redundancy Set ID

Identifier of the redundancy set.

brief, extensive

Connection status

Status of the connection between the srd and iccpd.

  • Connected

  • Not Connected

brief, extensive

Redundancy Set state

State of the local redundancy set state.

  • INITIALIZING

  • MASTER

  • STANDBY

  • STANDBY (WARNED)

brief, extensive

Redundancy Set peer state

State of the peer redundancy set state.

  • INITIALIZING

  • MASTER

  • STANDBY

  • STANDBY (WARNED)

brief, extensive

Redundancy Set health status

  • Passed

  • Failed

brief, extensive

Number of Monitored interface down

Number of monitored interfaces that are d

brief, extensive

Failed Interfaces

List of all monitored interfaces that are down.

brief, extensive

Service Set

Service set used for stateful sync.

brief, extensive

Service Interface

Service set used for

brief, extensive

Type

Type of redundancy and stateful sync for the listed service interface.

  • Inter-chassis

  • Intra-chassis

brief, extensive

Role

Role of the listed service interface.

  • active

  • backup

brief, extensive

Connection

Status of connection with peer service PIC.

  • Up

  • Down

brief, extensive

Synchronization

Type of synchronization. When all eligible sessions are still synchronizing, it is cold synchronization. When all current existing sessions are synchronized, it is a HOT synchronization, When long lived sessions are eligible, they are synchronized.

  • Hot—All current existing sessions are synced. When long-lived sessions are eligible, they are synchronized.

  • Cold–Eligible sessions are in the processing of synchronizing.

brief, extensive

ICCP process connection open complete count

Number of completed opens of ICCP process connections.

extensive

ICCP process connection close complete count

Number of completed closes of ICCP process connections.

ICCP packet sent count

Number of ICCP packets sent.

extensive

ICCP packet receive count

Number of ICCP packets received.

extensive

ICCP process keepalive receive count

Number of ICCP process keepalive messages received.

extensive

ICCP process keepalive sent count

Number of ICCP process keepalive messages sent.

extensive

ICCP redundancy group add count

Number of redundancy group add messages received by srd from ICCP.

extensive

ICCP redundancy group delete count

Number of redundancy group delete messages received by srd from ICCP.

extensive

RG connection up count

Number of redundancy group connection up messages received by srd from ICCP.

extensive

RG connection down count

Number of redundancy group connection down messages received by srd from ICCP.

extensive

RG join count

Number of redundancy group join messages sent from srd to ICCP.

extensive

RG data receive count

Number of packets of messages received by srd from a peer.

extensive

RG data sent count

Number of packets of messages sent from srd to a peer.

extensive

RG connect message sent count

Number of connect messages sent from srd to ICCP.

extensive

RG connect message receive count

Number of connect messages received by srd from ICCP.

extensive

RG disconnect message sent count

Number of disconnect messages sent from srd to ICCP.

extensive

RG disconnect message receive count

Number of disconnect messages received by srd from ICCP.

extensive

RG ack sent count

Number of RG ack messages sent.

extensive

RG nack sent count

Number of RG nack messages sent.

extensive

RG nack receive count

Number of RG nack messages received.

extensive

Transition Events Received

Number of transition events received in each of the following categories:

  • Acquire primary role auto

  • Acquire primary role manual

  • Release primary role auto

  • Release primary role manual

extensive

Transition Events Ignored

Number of transition events ignored in each of the following categories:

  • Acquire primary role auto

  • Acquire primary role manual

  • Release primary role auto

  • Release primary role manual

In a high-availability or redundancy pair of SDGs, in which one SDG is the primary and the other is the standby, when perform a double failover of the SDGs, the second failover event is not ignored, which is the expected behavior. The event is not disregarded because it arrives as a critical redundancy-event based on the redundancy-policy. However, because the SDG is already be in Standby state, the finite state machine transitions to the Standby-Warned state until it recovers. Therefore, the event is honored and not ignored. Although there was no primary role transition, it is because of a valid reason that the SDG is already in Standby state. The redundancy-event is associated with to a primary role release policy based on the configuration and the Release primary role field under the Transition Events Ignored column displays a number that corresponds to the redundancy event.

The services redundancy daemon (SRD) finite state machine quickly recovers (transitions from Standby-Warned to Standby) during restart-routing because the rpd restart-handling and recovery are fast and the following critical event is not ignored. However, disabling or deactivating the interface results in the FSM remaining in Standby-Warned until the interface is up. Any critical events during the time when the interface is down are ignored because the state is already Standby-Warned and does not transition to a different state. In summary, the following is the manner in which critical events are analyzed during state transitions:

  • Standby -> Standby Warned = Critical Event Not ignored [valid state transition]

  • Standby Warned -> Standby Warned = Critical Event Ignored [no state transition]

extensive

Monitored Events Received

Number of monitored events received in each of the following categories:

  • Link-down

  • Routing restart/terminate

  • Route update error

  • Peer primary-role-acquire

  • Peer primary-role-release

extensive

Monitored Events Ignored

Number of monitored events ignored in each of the following categories:

  • Link-down

  • Routing restart/terminate

  • Route update error

  • Peer primary-role-acquire

  • Peer primary-role-release

extensive

Sample Output

show services redundancy-group terse

show services redundancy-group brief (Health Status Passed)

show services redundancy-group brief (Health Status Failed)

show services redundancy-group extensive

Release Information

Statement introduced in Junos OS Release 16.1.