aggregate_all_not_viable_test - openconfig/featureprofiles GitHub Wiki

RT-5.7: Aggregate Not Viable All

[TODO: test automation/coding; issue https://github.com/openconfig/featureprofiles/issues/1655]

Summary

Test forwarding-viable with LAG and routing

Ensure that when --all LAG member-- become set with forwarding-viable == FALSE

  • forwarding-viable=false impact --only-- transmit traffic on all member port
  • All member ports set with forwarding-viable=false can receive all type of traffic
    and forward it normally (same as with forwarding-viable=true)
  • ISIS adjacency is established on LAG port w/ all member set to forwarding-viable
    == FALSE
  • Traffic that normally egress LAG with all members set to forwarding-viable == FALSE
    is forwarded by the next best egress interface/LAG.

Procedure

                                               LAG_2
+------------+            +-------------+ p2     .    p2   +--------------+
|  ATE       |            |             +-------;-:--------+   ATE        |
|            |            |             + - - - + + - - - -|              |
|            |            |             + - - - + + - - - -|     .-------.|
|.-------.   |            |             +-------+-+--------+    (  pfx2   )
(  pfx1   )  |     .      |             | p6    : ;   p6   |     `-------'|
|`-------'   | p1 ; : p1  |     DUT     |        '         |     .-------.|
|            |----+-+-----|             |                  |    (  pfx3   )
|            |    | |     |             | p7     .    p7   |     `-------'|
|            |    | |     |             +-------;-:--------+     .-------.|
|            |    : ;     |             |       | |        |    (  pfx4   )
|            |     '      |             |       | |        |     `-------'|
|            |  LAG_1     |             +-------+-+--------+              |
+------------+            +-------------+ p8    : ;   p8   +--------------+
                                                 '
                                                LAG_3
  • Connect ATE port-1 to DUT port-1, and ATE ports 2 through 8 to DUT ports 2-8
  • Configure ATE and DUT ports 1 to be LAG_1 w/ LACP running.
  • Configure ATE and DUT ports 2-6 to be LAG_2 w/ LACP running.
  • Configure ATE and DUT ports 7-8 to be LAG_3 w/ LACP running.
  • Establish ISIS adjacencies on LAG_1, LAG_2, LAG_3.
    1. Advertise one network prefix (pfx1) from ATE LAG_1
    2. Advertise one network prefix (pfx2) from ATE LAG_2 and ATE LAG_3.
  • Establish iBGP between ATE and DUT over LGA using LAG interface IPs and advertise prefix pfx3 with BGP NH from pfx2 range.
  • Programm via gRIBI route for prefix pfx4 with NHG pointing to NH LAG_2 & backup to NHG pointing to NH LAG_3(all ports are forwarding-viable at this point) with equal weight.

RT-5.7.1: For ISIS cost of LAG_2 lower than ISIS cost of LAG_3:

Run traffic:

  • From prefix pfx1 to all three: pfx2, pfx3, pfx4
  • From prefix pfx2 to: pfx1

RT-5.7.1.1: Make the forwarding-viable transitions from TRUE --> FALSE on ports 3-6 within the LAG_2 on the DUT

  • Ensure that only DUT port 2 of LAG ports has bidirectional traffic.
  • Ensure there is no traffic transmitted out of DUT ports 3-6
  • Ensure that traffic is received on all port2-6 and delivered to ATE port1
  • Ensure there are no packet losses in steady state (no congestion).
  • Ensure there is no traffic received on DUT LAG_3
  • Ensure there is no traffic transmitted on DUT LAG_3

RT-5.7.1.2: Verify forwarding-viable behavior on an aggregate interface with all members down or set with forwarding-viable=FALSE.

  • Ensure ISIS adjacency is UP on DUT LAG_2 and ATE LAG_2
  • Set with forwarding-viable=FALSE on port 2 (All Ports now on LAG_2 are set with FV=false)
  • Ensure that the ISIS adjacency is UP on DUT LAG_2 and ATE LAG_2
  • Ensure there is no layer3 traffic transmitted out of DUT ports 2-6 (LAG_2)
  • Ensure that traffic is received on all port3-6 and delivered to ATE LAG_1
  • Ensure there are no packet losses in steady state (no congestion) for traffic from ATE LAG_2 to ATE LAG_1 (pfx_1).
  • Ensure there are no packet losses in steady state (no congestion) for traffic from ATE LAG_1 to ATE LAG_3 (pfx_2, pfx3).
  • Ensure there is no traffic received on DUT LAG_3
  • Ensure that traffic from ATE port1 to pfx2, pfx3 are transmitted via DUT LAG3
  • Ensure that traffic from ATE port1 to pfx4 are transmitted out through backup NHG pointing to NH LAG3

RT-5.7.1.3: Make the forwarding-viable transitions from FALSE --> TRUE on a ports 6 within the LAG_2 on the DUT

  • Ensure that only DUT port 6 of LAG ports has bidirectional traffic.
  • Ensure there is no traffic transmitted out of DUT ports 2-6
  • Ensure that traffic is received on all port3-6 and delivered to ATE port1
  • Ensure there are no packet losses in steady state (no congestion).
  • Ensure there is no traffic received on DUT LAG_3
  • Ensure there is no traffic transmitted on DUT LAG_3

RT-5.7.1.4: Verify forwarding-viable behavior on an aggregate interface with some members are down with all member are set with forwarding-viable=FALSE.

  • Ensure ISIS adjacency is UP on DUT LAG_2 and ATE LAG_2
  • Set with forwarding-viable=FALSE on port 2 and make down other ports on LAG_2 (All Ports now on LAG_2 are set with FV=false and some ports are down)
  • Ensure that the ISIS adjacency is UP on DUT LAG_2 and ATE LAG_2
  • Ensure there is no layer3 traffic transmitted out of DUT ports 2-6 (LAG_2)
  • Ensure that traffic is received on all port3-6 and delivered to ATE LAG_1
  • Ensure there are no packet losses in steady state (no congestion) for traffic from ATE LAG_2 to ATE LAG_1 (pfx_1).
  • Ensure there are no packet losses in steady state (no congestion) for traffic from ATE LAG_1 to ATE LAG_3 (pfx_2, pfx3).
  • Ensure there is no traffic received on DUT LAG_3
  • Ensure that traffic from ATE port1 to pfx2, pfx3 are transmitted via DUT LAG3
  • Ensure that traffic from ATE port1 to pfx4 are transmitted out through NHG pointing to NH LAG3

RT-5.7.2: For ISIS cost of LAG_2 equal to ISIS cost of LAG_3

Run traffic:

  • From prefix pfx1 to all three: pfx2, pfx3, pfx4
  • From prefix pfx2 to: pfx1

RT-5.7.2.1: Make the forwarding-viable transitions from TRUE --> FALSE on ports 3-6 within the LAG_2 on the DUT

  • Ensure that only DUT port 2 of LAG_2 and all ports of LAG_3 ports has bidirectional traffic.
  • The traffic split between LAG_2 and LAG_3 should be 50:50
  • Ensure there is no traffic transmitted out of DUT ports 3-6
  • Ensure that traffic is received on all port2-6 and ports7-8 and delivered to ATE port1
  • Ensure there are no packet losses in steady state (no congestion)

RT-5.7.2.2: Verify forwarding-viable behavior on an aggregate interface with all are set with forwarding-viable=FALSE.

  • Ensure ISIS adjacency is UP on DUT LAG_2 and ATE LAG_2
  • Set with forwarding-viable=FALSE on port 2 (All Ports now on LAG_2 are set with FV=false)
  • Ensure that the ISIS adjacency is UP on DUT LAG_2 and ATE LAG_2
  • Ensure there is no traffic transmitted out of DUT ports 2-6 (LAG_2)
  • Ensure that traffic received on all port3-6 and ports7-8 is delivered to ATE LAG_1
  • Ensure there are no packet losses in steady state (no congestion) for traffic from ATE LAG_2, LAG_3 to ATE LAG_1 (pfx_1).
  • Ensure there are no packet losses in steady state (no congestion) for traffic from ATE LAG_1 to ATE LAG_3 (pfx_2, pfx3).
  • Ensure that traffic from ATE port1 to pfx2, pfx3 are transmitted via DUT LAG3
  • Ensure that traffic from ATE port1 to pfx4 are transmitted out through NHG pointing to NH LAG3

RT-5.7.2.3: Make the forwarding-viable transitions from FALSE --> TRUE on a ports 6 within the LAG_2 on the DUT

  • Ensure that only DUT port 6 of LAG_2 and all ports of LAG_3 ports has bidirectional traffic.
  • Ensure there is no traffic transmitted out of DUT ports 2-6
  • Ensure that traffic received on all port3-6 and ports7-8 is delivered to ATE port1
  • Ensure there are no packet losses in steady state (no congestion).

RT-5.7.2.4: Verify forwarding-viable behavior on an aggregate interface with some members are down with all member are set with forwarding-viable=FALSE.

  • Ensure ISIS adjacency is UP on DUT LAG_2 and ATE LAG_2
  • Set with forwarding-viable=FALSE and make down other ports on LAG_2 (All Ports now on LAG_2 are set with FV=false and some ports are down)
  • Ensure that the ISIS adjacency times out on DUT LAG_2 and ATE LAG_2
  • Ensure there is no traffic transmitted out of DUT ports 2-6 (LAG_2)
  • Ensure that traffic received on all port3-6 and ports7-8 is delivered to ATE LAG_1
  • Ensure there are no packet losses in steady state (no congestion) for traffic from ATE LAG_2, LAG_3 to ATE LAG_1 (pfx_1).
  • Ensure there are no packet losses in steady state (no congestion) for traffic from ATE LAG_1 to ATE LAG_3 (pfx_2, pfx3).
  • Ensure that traffic from ATE port1 to pfx2, pfx3 are transmitted via DUT LAG3
  • Ensure that traffic from ATE port1 to pfx4 are transmitted out through NH pointing to LAG3

OpenConfig Path and RPC Coverage

The below yaml defines the OC paths and RPC intended to be covered by this test.

paths:
  /interfaces/interface/ethernet/config/aggregate-id:
  ## Config forwarding Viable to True/false
  /interfaces/interface/config/forwarding-viable:
  ## Define Lag type
  /interfaces/interface/aggregation/config/lag-type:
  ## Configure LACP
  /lacp/config/system-priority:
  /lacp/interfaces/interface/config/name:
  /lacp/interfaces/interface/config/lacp-mode:
  /lacp/interfaces/interface/config/interval:
  /lacp/interfaces/interface/config/system-id-mac:
  /lacp/interfaces/interface/config/system-priority:


rpcs:
    gnmi:
        gNMI.Subscribe:
            ON_CHANGE: true

    gnoi:
        system.System.Reboot:

Telemetry Parameter coverage

None

Protocol/RPC Parameter coverage

None

Minimum DUT platform requirement

vRX

⚠️ **GitHub.com Fallback** ⚠️