Update RT-3.52: Static GUE Encap/Decap from v4 to v6#4927
Conversation
Update the PR to replace v4 transport with v6 transport. Following changes:
1. **All IP addresses for the test:**
* Replaced with following IPv6 equivalents for the tunnel endpoint IP variables:
* `$DUT_TE11.v6/128`
* `$DUT_TE10.v6/128`
* `$ATE2_INTERNAL_TE11.v6/128`
* `$ATE2_INTERNAL_TE10.v6/128`
2. **Advertisements - BGP:**
* Updated `$ATE2_IBGP.v[46]<>$DUT_lo0.v[46]` peering to advertise/expect `/128`, `/64' for the TE IPs.
- $ATE2_INTERNAL_TE10.v4/30 --replaced by--> $ATE2_INTERNAL_TE10.v6/64
- `$ATE2_INTERNAL_TE11.v4/30 -- replaced by --> `$ATE2_INTERNAL_TE11.v6/64
- $DUT_TE10.v4/30 -- replaced by --> $DUT_TE10.v6/64
- $DUT_TE11.v4/30 -- replaced by --> $DUT_TE11.v6/64
* Updated `$ATE2_Port3<>$DUT_Port4` peering to advertise/expect `/128`, `/64` for the TE IPs.
3. **Different Flows used throughout the test:**
* The "Tunnel endpoint used" column for Flow-Sets #1, #2, #3, and #4 now references the `.v6/128` tunnel IP variables (e.g., `$ATE2_INTERNAL_TE11.v6/128`, `$DUT_TE11.v6/128`).
- ATE2_INTERNAL_TE11.v4/32 --replaced by--> ATE2_INTERNAL_TE11.v6/128
- $DUT_TE11.v4/30 --replaced to--> $DUT_TE11.v6/64
4. **DUT Configuration:**
* Under **Static GUE Encapsulation (IPv6 Transport):**
* `tunnel-source` changed from `$DUT_lo0.v4` to `$DUT_lo0.v6`.
* `tunnel-destination1` changed to `$ATE2_INTERNAL_TE11.v6/128`.
* `tunnel-destination2` changed to `$ATE2_INTERNAL_TE10.v6/128`.
* Static route next-hops changed to the `.v6/128` tunnel destinations.
* Under **GUE Decapsulation:**
* Decapsulation ranges changed from `$DUT_TE11.v4/30` and `$DUT_TE10.v4/30` to `$DUT_TE11.v6/127` and `$DUT_TE10.v6/127`.
5. **Test Expectations:**
* In RT-3.52.2, RT-3.52.5, RT-3.52.6, RT-3.52.7, and RT-3.52.8, expected tunnel destination IPs in the flow descriptions are changed to the `.v6/128` variables.
6. **Canonical OC - For GUEv1 Encapsulation configuration (IPv6 Transport) updated aswell. Following changes:**
* Changed `type` from `UDPV4` to `UDPV6`.
* Changed `udp-v4` block to `udp-v6`.
* Updated `dst-ip` to `$ATE2_INTERNAL_TE11.v6`.
* Updated `src-ip` to `$DUT_lo0.v6`.
Summary of ChangesHello @sachendras, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request performs a comprehensive migration of a network test setup from IPv4 to IPv6 for GUE (Generic UDP Encapsulation) transport. The changes ensure that all relevant IP addresses, BGP advertisements, flow configurations, DUT settings, and test expectations are updated to support IPv6, allowing for the validation of GUE encapsulation over an IPv6 transport layer. Highlights
Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here. You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension. Footnotes
|
There was a problem hiding this comment.
Code Review
This pull request updates the README to reflect the change from IPv4 to IPv6 transport for GUE encapsulation. The changes are mostly correct and align with the PR description. I've found a couple of issues:
- There are some formatting errors and a typo in the IP address table.
- The canonical OC JSON example for GUE decapsulation is invalid.
I've provided suggestions to fix these issues.
Also, there's a small inconsistency in the PR description. Point 2 mentions /64 for TE IPs, while point 4 mentions /127. The changes in the README use /64, which seems correct and consistent with other parts of the document. It would be good to correct the PR description to avoid confusion.
Pull Request Test Coverage Report for Build 21971047164Details
💛 - Coveralls |
Update some of the AI suggested changes around duplicate IP addresses.
|
/gemini review |
There was a problem hiding this comment.
Code Review
This pull request updates the README file to reflect the transition from IPv4 to IPv6 transport for GUE tunnels. The changes are largely accurate and align with the goal of the PR. I've identified a few areas for improvement, primarily related to formatting and consistency within the markdown file. These include missing HTML tags, inconsistent variable formatting in tables, and a recurring typo. More critically, I found an invalid JSON example that needs correction. I've also noted a discrepancy between the README and the pull request description that should be resolved.
…ap_and_bgp_path_selection/README.md Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
…ap_and_bgp_path_selection/README.md Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
…ap_and_bgp_path_selection/README.md Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
Correcting all occurrences of encaped to encapsulated.
dplore
left a comment
There was a problem hiding this comment.
Please fix the github checks for canonical OC and the flat OC path list.
https://github.com/openconfig/featureprofiles/actions/runs/20443835325/job/58742840086?pr=4927
Updated incorrect OC Paths
|
/gcburn |
Updating the canonical OC to use UDP-V4 encap headers temporarily as a placeholder.
|
/gcburn |
Fixing the error message "parent container ipv6-prefix-set ... JSON contains unexpected field prefix" which is caused by the prefix leaf-list being placed at the wrong level in the JSON structure.
|
/gcbrun |
* Update README.md
Update the PR to replace v4 transport with v6 transport. Following changes:
1. **All IP addresses for the test:**
* Replaced with following IPv6 equivalents for the tunnel endpoint IP variables:
* `$DUT_TE11.v6/128`
* `$DUT_TE10.v6/128`
* `$ATE2_INTERNAL_TE11.v6/128`
* `$ATE2_INTERNAL_TE10.v6/128`
2. **Advertisements - BGP:**
* Updated `$ATE2_IBGP.v[46]<>$DUT_lo0.v[46]` peering to advertise/expect `/128`, `/64' for the TE IPs.
- $ATE2_INTERNAL_TE10.v4/30 --replaced by--> $ATE2_INTERNAL_TE10.v6/64
- `$ATE2_INTERNAL_TE11.v4/30 -- replaced by --> `$ATE2_INTERNAL_TE11.v6/64
- $DUT_TE10.v4/30 -- replaced by --> $DUT_TE10.v6/64
- $DUT_TE11.v4/30 -- replaced by --> $DUT_TE11.v6/64
* Updated `$ATE2_Port3<>$DUT_Port4` peering to advertise/expect `/128`, `/64` for the TE IPs.
3. **Different Flows used throughout the test:**
* The "Tunnel endpoint used" column for Flow-Sets #1, #2, #3, and openconfig#4 now references the `.v6/128` tunnel IP variables (e.g., `$ATE2_INTERNAL_TE11.v6/128`, `$DUT_TE11.v6/128`).
- ATE2_INTERNAL_TE11.v4/32 --replaced by--> ATE2_INTERNAL_TE11.v6/128
- $DUT_TE11.v4/30 --replaced to--> $DUT_TE11.v6/64
4. **DUT Configuration:**
* Under **Static GUE Encapsulation (IPv6 Transport):**
* `tunnel-source` changed from `$DUT_lo0.v4` to `$DUT_lo0.v6`.
* `tunnel-destination1` changed to `$ATE2_INTERNAL_TE11.v6/128`.
* `tunnel-destination2` changed to `$ATE2_INTERNAL_TE10.v6/128`.
* Static route next-hops changed to the `.v6/128` tunnel destinations.
* Under **GUE Decapsulation:**
* Decapsulation ranges changed from `$DUT_TE11.v4/30` and `$DUT_TE10.v4/30` to `$DUT_TE11.v6/127` and `$DUT_TE10.v6/127`.
5. **Test Expectations:**
* In RT-3.52.2, RT-3.52.5, RT-3.52.6, RT-3.52.7, and RT-3.52.8, expected tunnel destination IPs in the flow descriptions are changed to the `.v6/128` variables.
6. **Canonical OC - For GUEv1 Encapsulation configuration (IPv6 Transport) updated aswell. Following changes:**
* Changed `type` from `UDPV4` to `UDPV6`.
* Changed `udp-v4` block to `udp-v6`.
* Updated `dst-ip` to `$ATE2_INTERNAL_TE11.v6`.
* Updated `src-ip` to `$DUT_lo0.v6`.
* Update README.md
Update some of the AI suggested changes around duplicate IP addresses.
* Update feature/policy_forwarding/encapsulation/otg_tests/staticgueencap_and_bgp_path_selection/README.md
Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
* Update feature/policy_forwarding/encapsulation/otg_tests/staticgueencap_and_bgp_path_selection/README.md
Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
* Update feature/policy_forwarding/encapsulation/otg_tests/staticgueencap_and_bgp_path_selection/README.md
Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
* Update README.md
Correcting all occurrences of encaped to encapsulated.
* Update README.md
Updated incorrect OC Paths
* Update README.md
Updating the canonical OC to use UDP-V4 encap headers temporarily as a placeholder.
* Update README.md
Fixing the error message "parent container ipv6-prefix-set ... JSON contains unexpected field prefix" which is caused by the prefix leaf-list being placed at the wrong level in the JSON structure.
---------
Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
Co-authored-by: Darren Loher <[email protected]>
* Update README.md
Update the PR to replace v4 transport with v6 transport. Following changes:
1. **All IP addresses for the test:**
* Replaced with following IPv6 equivalents for the tunnel endpoint IP variables:
* `$DUT_TE11.v6/128`
* `$DUT_TE10.v6/128`
* `$ATE2_INTERNAL_TE11.v6/128`
* `$ATE2_INTERNAL_TE10.v6/128`
2. **Advertisements - BGP:**
* Updated `$ATE2_IBGP.v[46]<>$DUT_lo0.v[46]` peering to advertise/expect `/128`, `/64' for the TE IPs.
- $ATE2_INTERNAL_TE10.v4/30 --replaced by--> $ATE2_INTERNAL_TE10.v6/64
- `$ATE2_INTERNAL_TE11.v4/30 -- replaced by --> `$ATE2_INTERNAL_TE11.v6/64
- $DUT_TE10.v4/30 -- replaced by --> $DUT_TE10.v6/64
- $DUT_TE11.v4/30 -- replaced by --> $DUT_TE11.v6/64
* Updated `$ATE2_Port3<>$DUT_Port4` peering to advertise/expect `/128`, `/64` for the TE IPs.
3. **Different Flows used throughout the test:**
* The "Tunnel endpoint used" column for Flow-Sets openconfig#1, openconfig#2, openconfig#3, and openconfig#4 now references the `.v6/128` tunnel IP variables (e.g., `$ATE2_INTERNAL_TE11.v6/128`, `$DUT_TE11.v6/128`).
- ATE2_INTERNAL_TE11.v4/32 --replaced by--> ATE2_INTERNAL_TE11.v6/128
- $DUT_TE11.v4/30 --replaced to--> $DUT_TE11.v6/64
4. **DUT Configuration:**
* Under **Static GUE Encapsulation (IPv6 Transport):**
* `tunnel-source` changed from `$DUT_lo0.v4` to `$DUT_lo0.v6`.
* `tunnel-destination1` changed to `$ATE2_INTERNAL_TE11.v6/128`.
* `tunnel-destination2` changed to `$ATE2_INTERNAL_TE10.v6/128`.
* Static route next-hops changed to the `.v6/128` tunnel destinations.
* Under **GUE Decapsulation:**
* Decapsulation ranges changed from `$DUT_TE11.v4/30` and `$DUT_TE10.v4/30` to `$DUT_TE11.v6/127` and `$DUT_TE10.v6/127`.
5. **Test Expectations:**
* In RT-3.52.2, RT-3.52.5, RT-3.52.6, RT-3.52.7, and RT-3.52.8, expected tunnel destination IPs in the flow descriptions are changed to the `.v6/128` variables.
6. **Canonical OC - For GUEv1 Encapsulation configuration (IPv6 Transport) updated aswell. Following changes:**
* Changed `type` from `UDPV4` to `UDPV6`.
* Changed `udp-v4` block to `udp-v6`.
* Updated `dst-ip` to `$ATE2_INTERNAL_TE11.v6`.
* Updated `src-ip` to `$DUT_lo0.v6`.
* Update README.md
Update some of the AI suggested changes around duplicate IP addresses.
* Update feature/policy_forwarding/encapsulation/otg_tests/staticgueencap_and_bgp_path_selection/README.md
Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
* Update feature/policy_forwarding/encapsulation/otg_tests/staticgueencap_and_bgp_path_selection/README.md
Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
* Update feature/policy_forwarding/encapsulation/otg_tests/staticgueencap_and_bgp_path_selection/README.md
Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
* Update README.md
Correcting all occurrences of encaped to encapsulated.
* Update README.md
Updated incorrect OC Paths
* Update README.md
Updating the canonical OC to use UDP-V4 encap headers temporarily as a placeholder.
* Update README.md
Fixing the error message "parent container ipv6-prefix-set ... JSON contains unexpected field prefix" which is caused by the prefix leaf-list being placed at the wrong level in the JSON structure.
---------
Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
Co-authored-by: Darren Loher <[email protected]>
* Update README.md
Update the PR to replace v4 transport with v6 transport. Following changes:
1. **All IP addresses for the test:**
* Replaced with following IPv6 equivalents for the tunnel endpoint IP variables:
* `$DUT_TE11.v6/128`
* `$DUT_TE10.v6/128`
* `$ATE2_INTERNAL_TE11.v6/128`
* `$ATE2_INTERNAL_TE10.v6/128`
2. **Advertisements - BGP:**
* Updated `$ATE2_IBGP.v[46]<>$DUT_lo0.v[46]` peering to advertise/expect `/128`, `/64' for the TE IPs.
- $ATE2_INTERNAL_TE10.v4/30 --replaced by--> $ATE2_INTERNAL_TE10.v6/64
- `$ATE2_INTERNAL_TE11.v4/30 -- replaced by --> `$ATE2_INTERNAL_TE11.v6/64
- $DUT_TE10.v4/30 -- replaced by --> $DUT_TE10.v6/64
- $DUT_TE11.v4/30 -- replaced by --> $DUT_TE11.v6/64
* Updated `$ATE2_Port3<>$DUT_Port4` peering to advertise/expect `/128`, `/64` for the TE IPs.
3. **Different Flows used throughout the test:**
* The "Tunnel endpoint used" column for Flow-Sets openconfig#1, openconfig#2, openconfig#3, and openconfig#4 now references the `.v6/128` tunnel IP variables (e.g., `$ATE2_INTERNAL_TE11.v6/128`, `$DUT_TE11.v6/128`).
- ATE2_INTERNAL_TE11.v4/32 --replaced by--> ATE2_INTERNAL_TE11.v6/128
- $DUT_TE11.v4/30 --replaced to--> $DUT_TE11.v6/64
4. **DUT Configuration:**
* Under **Static GUE Encapsulation (IPv6 Transport):**
* `tunnel-source` changed from `$DUT_lo0.v4` to `$DUT_lo0.v6`.
* `tunnel-destination1` changed to `$ATE2_INTERNAL_TE11.v6/128`.
* `tunnel-destination2` changed to `$ATE2_INTERNAL_TE10.v6/128`.
* Static route next-hops changed to the `.v6/128` tunnel destinations.
* Under **GUE Decapsulation:**
* Decapsulation ranges changed from `$DUT_TE11.v4/30` and `$DUT_TE10.v4/30` to `$DUT_TE11.v6/127` and `$DUT_TE10.v6/127`.
5. **Test Expectations:**
* In RT-3.52.2, RT-3.52.5, RT-3.52.6, RT-3.52.7, and RT-3.52.8, expected tunnel destination IPs in the flow descriptions are changed to the `.v6/128` variables.
6. **Canonical OC - For GUEv1 Encapsulation configuration (IPv6 Transport) updated aswell. Following changes:**
* Changed `type` from `UDPV4` to `UDPV6`.
* Changed `udp-v4` block to `udp-v6`.
* Updated `dst-ip` to `$ATE2_INTERNAL_TE11.v6`.
* Updated `src-ip` to `$DUT_lo0.v6`.
* Update README.md
Update some of the AI suggested changes around duplicate IP addresses.
* Update feature/policy_forwarding/encapsulation/otg_tests/staticgueencap_and_bgp_path_selection/README.md
Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
* Update feature/policy_forwarding/encapsulation/otg_tests/staticgueencap_and_bgp_path_selection/README.md
Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
* Update feature/policy_forwarding/encapsulation/otg_tests/staticgueencap_and_bgp_path_selection/README.md
Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
* Update README.md
Correcting all occurrences of encaped to encapsulated.
* Update README.md
Updated incorrect OC Paths
* Update README.md
Updating the canonical OC to use UDP-V4 encap headers temporarily as a placeholder.
* Update README.md
Fixing the error message "parent container ipv6-prefix-set ... JSON contains unexpected field prefix" which is caused by the prefix leaf-list being placed at the wrong level in the JSON structure.
---------
Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
Co-authored-by: Darren Loher <[email protected]>
* Update README.md
Update the PR to replace v4 transport with v6 transport. Following changes:
1. **All IP addresses for the test:**
* Replaced with following IPv6 equivalents for the tunnel endpoint IP variables:
* `$DUT_TE11.v6/128`
* `$DUT_TE10.v6/128`
* `$ATE2_INTERNAL_TE11.v6/128`
* `$ATE2_INTERNAL_TE10.v6/128`
2. **Advertisements - BGP:**
* Updated `$ATE2_IBGP.v[46]<>$DUT_lo0.v[46]` peering to advertise/expect `/128`, `/64' for the TE IPs.
- $ATE2_INTERNAL_TE10.v4/30 --replaced by--> $ATE2_INTERNAL_TE10.v6/64
- `$ATE2_INTERNAL_TE11.v4/30 -- replaced by --> `$ATE2_INTERNAL_TE11.v6/64
- $DUT_TE10.v4/30 -- replaced by --> $DUT_TE10.v6/64
- $DUT_TE11.v4/30 -- replaced by --> $DUT_TE11.v6/64
* Updated `$ATE2_Port3<>$DUT_Port4` peering to advertise/expect `/128`, `/64` for the TE IPs.
3. **Different Flows used throughout the test:**
* The "Tunnel endpoint used" column for Flow-Sets openconfig#1, openconfig#2, openconfig#3, and openconfig#4 now references the `.v6/128` tunnel IP variables (e.g., `$ATE2_INTERNAL_TE11.v6/128`, `$DUT_TE11.v6/128`).
- ATE2_INTERNAL_TE11.v4/32 --replaced by--> ATE2_INTERNAL_TE11.v6/128
- $DUT_TE11.v4/30 --replaced to--> $DUT_TE11.v6/64
4. **DUT Configuration:**
* Under **Static GUE Encapsulation (IPv6 Transport):**
* `tunnel-source` changed from `$DUT_lo0.v4` to `$DUT_lo0.v6`.
* `tunnel-destination1` changed to `$ATE2_INTERNAL_TE11.v6/128`.
* `tunnel-destination2` changed to `$ATE2_INTERNAL_TE10.v6/128`.
* Static route next-hops changed to the `.v6/128` tunnel destinations.
* Under **GUE Decapsulation:**
* Decapsulation ranges changed from `$DUT_TE11.v4/30` and `$DUT_TE10.v4/30` to `$DUT_TE11.v6/127` and `$DUT_TE10.v6/127`.
5. **Test Expectations:**
* In RT-3.52.2, RT-3.52.5, RT-3.52.6, RT-3.52.7, and RT-3.52.8, expected tunnel destination IPs in the flow descriptions are changed to the `.v6/128` variables.
6. **Canonical OC - For GUEv1 Encapsulation configuration (IPv6 Transport) updated aswell. Following changes:**
* Changed `type` from `UDPV4` to `UDPV6`.
* Changed `udp-v4` block to `udp-v6`.
* Updated `dst-ip` to `$ATE2_INTERNAL_TE11.v6`.
* Updated `src-ip` to `$DUT_lo0.v6`.
* Update README.md
Update some of the AI suggested changes around duplicate IP addresses.
* Update feature/policy_forwarding/encapsulation/otg_tests/staticgueencap_and_bgp_path_selection/README.md
Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
* Update feature/policy_forwarding/encapsulation/otg_tests/staticgueencap_and_bgp_path_selection/README.md
Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
* Update feature/policy_forwarding/encapsulation/otg_tests/staticgueencap_and_bgp_path_selection/README.md
Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
* Update README.md
Correcting all occurrences of encaped to encapsulated.
* Update README.md
Updated incorrect OC Paths
* Update README.md
Updating the canonical OC to use UDP-V4 encap headers temporarily as a placeholder.
* Update README.md
Fixing the error message "parent container ipv6-prefix-set ... JSON contains unexpected field prefix" which is caused by the prefix leaf-list being placed at the wrong level in the JSON structure.
---------
Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
Co-authored-by: Darren Loher <[email protected]>
Update the PR to replace v4 transport with v6 transport. Following changes:
All IP addresses for the test:
$DUT_TE11.v6/128$DUT_TE10.v6/128$ATE2_INTERNAL_TE11.v6/128$ATE2_INTERNAL_TE10.v6/128Advertisements - BGP:
$ATE2_IBGP.v[46]<>$DUT_lo0.v[46]peering to advertise/expect/128, `/64' for the TE IPs.$ATE2_INTERNAL_TE11.v4/30 -- replaced by -->$ATE2_INTERNAL_TE11.v6/64$ATE2_Port3<>$DUT_Port4peering to advertise/expect/128,/64for the TE IPs.Different Flows used throughout the test:
.v6/128tunnel IP variables (e.g.,$ATE2_INTERNAL_TE11.v6/128,$DUT_TE11.v6/128).DUT Configuration:
tunnel-sourcechanged from$DUT_lo0.v4to$DUT_lo0.v6.tunnel-destination1changed to$ATE2_INTERNAL_TE11.v6/128.tunnel-destination2changed to$ATE2_INTERNAL_TE10.v6/128..v6/128tunnel destinations.$DUT_TE11.v4/30and$DUT_TE10.v4/30to$DUT_TE11.v6/127and$DUT_TE10.v6/127.Test Expectations:
.v6/128variables.Canonical OC - For GUEv1 Encapsulation configuration (IPv6 Transport) updated aswell. Following changes:
typefromUDPV4toUDPV6.udp-v4block toudp-v6.dst-ipto$ATE2_INTERNAL_TE11.v6.src-ipto$DUT_lo0.v6.