supervisor_failure_test - bstoll/featureprofiles GitHub Wiki

TE-8.2: Supervisor Failure

Summary

Ensure that gRIBI entries are persisted over supervisor failure.

Procedure

  • Connect DUT port-1 to ATE port-1, DUT port-2 to ATE port-2. Assign IPv4 addresses to all ports.

  • Connect gRIBI client to DUT specifying persistence mode PRESERVE, SINGLE_PRIMARY client redundancy in the SessionParameters request, and make it become leader. Ensure that no error is reported from the gRIBI server.

  • Add an IPv4Entry for prefix 203.0.113.0/24 pointing to ATE port-2 via gRIBI-A. Ensure that the entry is active through AFT telemetry and correct ACK is received.

  • Send traffic from ATE port-1 to prefix 203.0.113.0/24, and ensure traffic flows 100% and reaches ATE port-2.

  • Validate: Traffic continues to be forwarded between ATE port-1 and ATE port-2 during supervisor switchover triggered using gNOI SwitchControlProcessor.

    Following reconnection of a gRIBI client to new master supervisor , ensure the prefix 203.0.113.0/24 pointing to ATE port-2 is present and traffic flows 100% from ATE port-1 to ATE port-2.

Protocol/RPC Parameter coverage

  • gNOI:
    • System
      • SwitchControlProcessor

Config parameter coverage

Telemery parameter coverage

  • CHASSIS:

    • /components/component[name=]/state/last-reboot-time
    • /components/component[name=]/state/last-reboot-reason
  • CONTROLLER_CARD:

    • /components/component[name=]/state/redundant-role
    • /components/component[name=]/state/last-switchover-time
    • /components/component[name=]/state/last-switchover-reason/trigger
    • /components/component[name=]/state/last-switchover-reason/details
    • /components/component[name=]/state/last-reboot-time
    • /components/component[name=]/state/last-reboot-reason
⚠️ **GitHub.com Fallback** ⚠️