Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Create README.md #3495

Closed
wants to merge 7 commits into from
Closed

Create README.md #3495

Changes from 5 commits
Commits
Show all changes
7 commits
Select commit Hold shift + click to select a range
d8192f5
Create README.md
vvlakshmanamurthy Oct 2, 2024
3d12b85
Update README.md
vvlakshmanamurthy Oct 9, 2024
7d16dec
Update README.md
vvlakshmanamurthy Oct 9, 2024
03929a8
Update README.md
vvlakshmanamurthy Oct 9, 2024
1647388
Merge branch 'main' into patch-3
vvlakshmanamurthy Oct 9, 2024
c1ea778
Update README.md
vvlakshmanamurthy Oct 10, 2024
e1091b5
Merge branch 'main' into patch-3
vvlakshmanamurthy Oct 10, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
162 changes: 162 additions & 0 deletions ...lection/otg_tests/policy_based_traffic_steering_default_to_nondefault/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,162 @@

vvlakshmanamurthy marked this conversation as resolved.
Show resolved Hide resolved
## Summary
This test ensures NOS is able to host multiple VRFs, perform GUE tunnel DECAP in the default VRF and also allows for gradual traffic migration from Default to Non-Default VRF using VRF selection policy.


## Procedure
vvlakshmanamurthy marked this conversation as resolved.
Show resolved Hide resolved
Test environment setup

### Topology
Create the following connections:
```mermaid
graph LR;
subgraph ATE1 [ATE1]
A1[Port1]
end
subgraph DUT1 [DUT1]
B1[Port1]
B2[Port2]
end
subgraph ATE2 [ATE2]
C1[Port1]
end
A1 <-- IBGP(ASN100) --> B1;
B2 <-- EBGP(ASN100:ASN200) --> C1;
```

### Advertisements:

ATE1:Port1 advertises following prefixes over IBGP to DUT:Port1
- IPv4Prefix1/24 IPv6Prefix1/64
- IPv4Prefix2/24 IPv6Prefix2/64
- IPv4Prefix3/24 IPv6Prefix3/64
- IPv4Prefix4/24 IPv6Prefix4/64
- IPv4Prefix5/24 IPv6Prefix5/64

ATE2:Port1 advertieses following prefixes to DUT:Port2 over EBGP
- IPv4Prefix6/24 IPv6Prefix6/64
- IPv4Prefix7/24 IPv6Prefix7/64
- IPv4Prefix8/24 IPv6Prefix8/64
- IPv4Prefix9/24 IPv6Prefix9/64
- IPv4Prefix10/24 IPv6Prefix10/64

### Flows:

From ATE1:Port1 to ATE2:Port1
- IPv4Prefix1/24 to IPv4Prefix6/24
- IPv6Prefix1/64 to IPv6Prefix6/64

- IPv4Prefix2/24 to IPv4Prefix7/24
- IPv6Prefix2/64 to IPv6Prefix7/64

- IPv4Prefix3/24 to IPv4Prefix8/24
- IPv6Prefix3/64 to IPv6Prefix8/64

- IPv4Prefix4/24 to IPv4Prefix9/24
- IPv6Prefix4/64 to IPv6Prefix9/64

- IPv4Prefix5/24 to IPv4Prefix10/24
- IPv6Prefix5/64 to IPv6Prefix10/64

Flows from ATE2:Port1 to ATE1:Port1
- IPv4Prefix6/24 to IPv4Prefix1/24
- IPv6Prefix6/64 to IPv6Prefix1/64

- IPv4Prefix7/24 to IPv4Prefix2/24
- IPv6Prefix7/64 to IPv6Prefix2/64

- IPv4Prefix8/24 to IPv4Prefix3/24
- IPv6Prefix8/64 to IPv6Prefix3/64

- IPv4Prefix9/24 to IPv4Prefix4/24
- IPv6Prefix9/64 to IPv6Prefix4/64

- IPv4Prefix10/24 to IPv4Prefix5/24
- IPv6Prefix10/64 to IPv6Prefix5/64


**PF-1.6.1: [Baseline] Default VRF for all flows. Regular traffic.**
vvlakshmanamurthy marked this conversation as resolved.
Show resolved Hide resolved

In this case ATE2:Port1 simulates the regular flows from ATE2:Port1 as stated above.
* ATE2 sends following IPv4 and IPv6 flows:
- IPv4Prefix6/24 to IPv4Prefix1/24
- IPv4Prefix7/24 to IPv4Prefix2/24
- IPv4Prefix8/24 to IPv4Prefix3/24
- IPv4Prefix9/24 to IPv4Prefix4/24
- IPv4Prefix10/24 to IPv4Prefix5/24
- IPv6Prefix6/64 to IPv6Prefix1/64
- IPv6Prefix7/64 to IPv6Prefix2/64
- IPv6Prefix8/64 to IPv6Prefix3/64
- IPv6Prefix9/64 to IPv6Prefix4/64
- IPv6Prefix10/64 to IPv6Prefix5/64
- Expectations:
- All traffic must be successful<br><br><br>

**PF-1.6.2: Traffic from ATE2:Port1 to ATE1:Port1 Prefix 1 migrated to Non-Default VRF using the VRF selection policy.**
vvlakshmanamurthy marked this conversation as resolved.
Show resolved Hide resolved
* ATE2 sends following IPv4 and IPv6 flows:
* IPv4Prefix6/24 to IPv4Prefix1/24
* IPv4Prefix7/24 to IPv4Prefix2/24
* IPv4Prefix8/24 to IPv4Prefix3/24
* IPv4Prefix9/24 to IPv4Prefix4/24
* IPv4Prefix10/24 to IPv4Prefix5/24
* IPv6Prefix6/64 to IPv6Prefix1/64
* IPv6Prefix7/64 to IPv6Prefix2/64
* IPv6Prefix8/64 to IPv6Prefix3/64
* IPv6Prefix9/64 to IPv6Prefix4/64
* IPv6Prefix10/64 to IPv6Prefix5/64
* DUT has the following VRF selection policy
* Statement1: traffic matching IPv4Prefix1/24 & IPv6Prefix1/64, Punt to Non-default vrf
* Statement2: traffic matching IPv4Prefix2/24 & IPv6Prefix2/64, Punt to default vrf
* Statement3: traffic matching IPv4Prefix3/24 & IPv6Prefix3/64, Punt to default vrf
* Statement4: traffic matching IPv4Prefix4/24 & IPv6Prefix4/64, Punt to default vrf
* Statement5: traffic matching IPv4Prefix5/24 & IPv6Prefix5/64, Punt to default vrf
* Statement6: traffic matching IPv4Prefix6/24 & IPv6Prefix6/64, Punt to default vrf
* DUT must also leak all the routes from the Default VRF to the non-default VRF
* Expectations:
* Traffic for Prefix 1 received from ATE2:Port1 once punted to non-defailt VRF by the VRF selection policy, must be received by ATE1:Port1
* Traffic sent by ATE2:Port1 must be routed to ATE1:Port1 via the DEFAULT VRF in the DUT.<br><br><br>

**PF-1.6.3 to PF-1.6.7: Traffic from ATE2:Port1 to ATE1:Port1 migrated to Non-Default VRF using the VRF selection policy.**
Follow the steps in PF-1.6.2 above to gradually move different traffic flows from the Default VRF to the Non-Defailt in the following sequence:

* PF-1.6.3 Prefix 1-2 Traffic from ATE2:Port1 to ATE1:Port1 migrated to Non-Default VRF using the VRF selection policy.
VRF selection policy on DUT:Port2 changes as follows:
* Statement1: traffic matching IPv4Prefix1/24 & IPv6Prefix1/64, Punt to Non-default vrf
* Statement2: traffic matching IPv4Prefix2/24 & IPv6Prefix2/64, Punt to Non-default vrf
* Statement3: traffic matching IPv4Prefix3/24 & IPv6Prefix3/64, Punt to default vrf
* Statement4: traffic matching IPv4Prefix4/24 & IPv6Prefix4/64, Punt to default vrf
* Statement5: traffic matching IPv4Prefix5/24 & IPv6Prefix5/64, Punt to default vrf
* Statement6: traffic matching IPv4Prefix6/24 & IPv6Prefix6/64, Punt to default vrf<br><br>
* PF-1.6.4 Prefix 1-3 Traffic from ATE2:Port1 to ATE1:Port1 migrated to Non-Default VRF using the VRF selection policy.
VRF selection policy on DUT:Port2 changes as follows:
* Statement1: traffic matching IPv4Prefix1/24 & IPv6Prefix1/64, Punt to Non-default vrf
* Statement2: traffic matching IPv4Prefix2/24 & IPv6Prefix2/64, Punt to Non-default vrf
* Statement3: traffic matching IPv4Prefix3/24 & IPv6Prefix3/64, Punt to Non-default vrf
* Statement4: traffic matching IPv4Prefix4/24 & IPv6Prefix4/64, Punt to default vrf
* Statement5: traffic matching IPv4Prefix5/24 & IPv6Prefix5/64, Punt to default vrf
* Statement6: traffic matching IPv4Prefix6/24 & IPv6Prefix6/64, Punt to default vrf<br><br>
* PF-1.6.5 Prefix 1-4 Traffic from ATE2:Port1 to ATE1:Port1 migrated to Non-Default VRF using the VRF selection policy.
VRF selection policy on DUT:Port2 changes as follows:
* Statement1: traffic matching IPv4Prefix1/24 & IPv6Prefix1/64, Punt to Non-default vrf
* Statement2: traffic matching IPv4Prefix2/24 & IPv6Prefix2/64, Punt to Non-default vrf
* Statement3: traffic matching IPv4Prefix3/24 & IPv6Prefix3/64, Punt to Non-default vrf
* Statement4: traffic matching IPv4Prefix4/24 & IPv6Prefix4/64, Punt to Non-default vrf
* Statement5: traffic matching IPv4Prefix5/24 & IPv6Prefix5/64, Punt to default vrf
* Statement6: traffic matching IPv4Prefix6/24 & IPv6Prefix6/64, Punt to default vrf<br><br>
* PF-1.6.6 Prefix 1-5 Traffic from ATE2:Port1 to ATE1:Port1 migrated to Non-Default VRF using the VRF selection policy.
VRF selection policy on DUT:Port2 changes as follows:
* Statement1: traffic matching IPv4Prefix1/24 & IPv6Prefix1/64, Punt to Non-default vrf
* Statement2: traffic matching IPv4Prefix2/24 & IPv6Prefix2/64, Punt to Non-default vrf
* Statement3: traffic matching IPv4Prefix3/24 & IPv6Prefix3/64, Punt to Non-default vrf
* Statement4: traffic matching IPv4Prefix4/24 & IPv6Prefix4/64, Punt to Non-default vrf
* Statement5: traffic matching IPv4Prefix5/24 & IPv6Prefix5/64, Punt to Non-default vrf
* Statement6: traffic matching IPv4Prefix6/24 & IPv6Prefix6/64, Punt to default vrf<br><br>
* PF-1.6.7 Prefix 1-6 Traffic from ATE2:Port1 to ATE1:Port1 migrated to Non-Default VRF using the VRF selection policy.
VRF selection policy on DUT:Port2 changes as follows:
* Statement1: traffic matching IPv4Prefix1/24 & IPv6Prefix1/64, Punt to Non-default vrf
* Statement2: traffic matching IPv4Prefix2/24 & IPv6Prefix2/64, Punt to Non-default vrf
* Statement3: traffic matching IPv4Prefix3/24 & IPv6Prefix3/64, Punt to Non-default vrf
* Statement4: traffic matching IPv4Prefix4/24 & IPv6Prefix4/64, Punt to Non-default vrf
* Statement5: traffic matching IPv4Prefix5/24 & IPv6Prefix5/64, Punt to Non-default vrf
* Statement6: traffic matching IPv4Prefix6/24 & IPv6Prefix6/64, Punt to Non-default vrf<br><br>
* Expectations are the same for traffic routed via the Default and the Non-Default VRFs on the DUT.
Loading