backup_nhg_multiple_nh_test - bstoll/featureprofiles GitHub Wiki
Ensure that backup NHGs are honoured with NextHopGroup entries containing >1 NH.
- 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.
- Connect a gRIBI client to the DUT, make it become leader and inject the
following:
- An IPv4Entry in VRF-A, pointing to a NextHopGroup (in DEFAULT VRF)
containing:
- Two primary next-hops:
- IP of ATE port-2
- IP of ATE port-3
- A backup NHG containing a single next-hop pointing to VRF-B.
- Two primary next-hops:
- The same IPv4Entry but in VRF-B, pointing to a NextHopGroup (in DEFAULT VRF) containing a primary next-hop to the IP of ATE port-4.
- An IPv4Entry in VRF-A, pointing to a NextHopGroup (in DEFAULT VRF)
containing:
- Ensure that traffic forwarded to the destination 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.
- No new configuration covered.
- No new telemetry covered.
- gRIBI:
- Modify
- ModifyRequest
- NextHopGroup
- backup_nexthop_group
- NextHopGroup
- ModifyRequest
- Modify
vRX