show chassis high-availability services-redundancy-group

SRG failure event codes

SRG failure event codes are:

• BF— BFD monitoring

• IP— IP monitoring

• IF— Interface Monitoring

• CP— Control Plane monitoring

Services Redundancy Group

• Deployment Type—Multinode High Availability deployment type - Routing, switching, hybrid, or cloud

• Status—Indicates the current SRG state of the node in the high availability setup. Possible statuses include:

  • Active: The current SRG is actively processing traffic and managing the system.
  • Backup: The current SRG is in standby mode, ready to take over if the peer node fails.
  • Hold: The current SRG is ready to participate in the Multinode High Availability setup.
  • Ineligible: The current SRG is not ready to take over the role after a failover.

• Activeness Priority—Priority value determines whether a node can act as the active node in a Multinode High Availability setup. The node with the higher activeness priority become active for the service redundancy group.

• Process Packet In Backup State—Yes or No. Yes indicates IPsec packets will be processed by the backup node. This option is not applicable for non-IPsec traffic.

• Control Plane State—Displays the Control plane cold sync readiness after taking over the backup role. Means the control plane finished syncing all the control plane data from the new active node.

  The options are:

  • READY—Active mode

  • READY/NOT READY—Backup node based on the actual state

  • N/A—in other states

• System Integrity Check—Displays if the hold timer is running and system integrity check is under progress. Applicable only in BACKUP and INELLIGIBLE state.

• Failure Events—Displays local service redundancy group related attribute failure events.

• Monitoring Object Failures: —Displays failed monitor-object information.

• Peer Information—Displays peer node information.

  • Peer Id— Peer node identification number.

  • Status—Displays status of the peer node. The options are Active/Backup/Ineligible/Unknown.

  • Health Status—Displays health status of the peer node as advertised last

    • HEALTHY—Peer node SRG state is healthy

    • UNHEALTHY—Peer node SRG state is unhealthy

    • UNKNOWN—Peer link is down

    • SRG NOT CONFIGURED—SRG not configured at peer node.

  • Failover Readiness—Displays Failover readiness of the peer node and applicable only in Active state.

    The options are:

    • READY—Peer’s healthy, control and data plane cold sync is complete and hence peer is ready for a failover. A manual failover can be done

    • NOT READY—Peer is either unhealthy, or data/control plane cold sync is pending

    • UNKNOWN—Peer’s failover readiness is awaited or if peer link is down

    • N/A—In all states other than Active.

  • Signal Route Info

    • Active Signal Route—Active signal route required for activeness enforcement
    • Backup Signal Route—Backup signal route required for activeness enforcement
    • Routing Instance—Routing instance of routes
    • Status—Status of the routes - INSTALLED or NOT INSTALLED
  • Split-brain Prevention Probe Info
    • DST-IP—IP addresses of the upstream routers as the destination IP address for the activeness determination probe.
    • SRC-IP—floating IP address as source IP address for activeness determination probe.
    • Routing Instance—Routing instance of routes

    • Type - Type of probing. Available options are BFD-based probing or ICMP-based probing.

      For BFD-based probing:

      • Interval: Configured intervals for probes.
      • Multiplier: Multipliers for probes.
    • Status—Status of the probes - RUNNING or NOT RUNNUNG
  • BFD Monitoring
    • Status—State of the BFD session: Up, Down, Init or failing
    • SRC-IP—Source IP address for outgoing BFD packets
    • DST-IP—Destination IP address for outgoing BFD packets
    • Routing Instance—Routing instance of routes on which BFD monitoring is configured.

    • Type—Session type (single hop or multihop)

    • IFL Name—

      Interface on which the BFD session is active
    • Status—Status of the probes - RUNNING or NOT RUNNUNG
  • Object Monitoring
    • Object Name—Name of the object-monitor.
    • Object Status—Status of the object-monitor. Indicates if the object-monitoring is running or not (Up or Down).
    • Object Monitored Entries: Monitoring options created under object-monitor entity. Available options are IP monitoring, BFD monitoring, or interface monitoring.
    • Object Failures: Failed monitoring entity (IP monitoring, BFD monitoring, or interface monitoring)
    • Object Threshold: Threshold value set for object-monitor.
    • Object Current Weight: Weight of object-monitor at present.