backup_nhg_multiple_nh_test

TE-11.2: Backup NHG: Multiple NH

Summary

Ensure that backup NHGs are honoured with NextHopGroup entries containing >1 NH.

Procedure

• Connect ATE port-1 to DUT port-1, ATE port-2 to DUT port-2, ATE port-3 to DUT port-3, and ATE port-4 to DUT port-4.
• Create a L3 routing instance (VRF-A), and assign DUT port-1 to VRF-A.
• Create a L3 routing instance (VRF-B) that includes no interface.
• TODO: Create a L3 routing instance (VRF-C) that includes no interface.
• TODO: Connect a gRIBI client to the DUT, make it become leader and inject the following:
  • An IPv4Entry in VRF-A for IP-1, pointing to a NextHopGroup (in DEFAULT VRF) containing:
    • Two primary next-hops:
      • IP of ATE port-2
      • IP of ATE port-3
  • An IPv4Entry VRF-B for IP-1, pointing to a NextHopGroup (in DEFAULT VRF) containing a primary next-hop that decaps-and-reencaps traffic to IP-2 and redirects to VRF-C.
  • An IPv4Entry for IP-2 in VRF-C, pointing to a NextHopGroup (in DEFAULT VRF) containing:
    • One primary next-hop pointing to IP of ATE port-4
• TODO: Ensure that traffic with IP-1 as an outer IP (and an inner packet) is received at ATE port-2 and port-3. Validate that AFT telemetry covers this case.
• Disable ATE port-2. Ensure that traffic for the destination is received at ATE port-3.
• Disable ATE port-3. Ensure that traffic for the destination is received at ATE port-4.

Config Parameter coverage

• No new configuration covered.

Telemetry Parameter coverage

• No new telemetry covered.

Protocol/RPC Parameter coverage

• gRIBI:
  • Modify
    • ModifyRequest
      • NextHopGroup
        • backup_nexthop_group

Minimum DUT platform requirement

vRX