Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Update RT-3.52: Static GUE Encap/Decap from v4 to v6#4927

Merged
sachendras merged 13 commits into
mainfrom
sachendras-patch-30
Feb 19, 2026
Merged

Update RT-3.52: Static GUE Encap/Decap from v4 to v6#4927
sachendras merged 13 commits into
mainfrom
sachendras-patch-30

Conversation

@sachendras

Copy link
Copy Markdown
Contributor

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.

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`.
@sachendras sachendras requested a review from a team as a code owner December 13, 2025 17:41
@gemini-code-assist

Copy link
Copy Markdown
Contributor

Summary of Changes

Hello @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

  • IPv6 Migration for Tunnel Endpoints: All IPv4 tunnel endpoint IP variables have been replaced with their IPv6 equivalents, specifically using /128 prefixes for tunnel IPs.
  • BGP Advertisement Updates: BGP peering configurations have been updated to advertise and expect IPv6 prefixes, changing from /30 or /32 IPv4 prefixes to /64 or /128 IPv6 prefixes for tunnel endpoint IPs.
  • Flow Configuration Adjustment: The 'Tunnel endpoint used' column for Flow-Sets 1, 2, 3, and 4 now correctly references the new IPv6 tunnel IP variables.
  • DUT Configuration Changes: The Device Under Test (DUT) configuration for Static GUE Encapsulation now uses IPv6 for tunnel sources and destinations, and GUE Decapsulation ranges have been updated to IPv6 /127 or /64 prefixes.
  • Test Expectation Alignment: Expected tunnel destination IPs in various test flow descriptions (e.g., RT-3.52.2, RT-3.52.5, RT-3.52.6, RT-3.52.7, RT-3.52.8) have been updated to reflect the new IPv6 /128 variables.
  • Canonical OC GUEv1 Configuration: The GUEv1 Encapsulation configuration has been updated to use UDPv6, changing the type from UDPV4 to UDPV6 and updating source and destination IPs to IPv6.
Using Gemini Code Assist

The 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 /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

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 .gemini/ folder in the base of the repository. Detailed instructions can be found here.

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

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

@OpenConfigBot

OpenConfigBot commented Dec 13, 2025

Copy link
Copy Markdown

Pull Request Functional Test Report for #4927 / d53735d

Virtual Devices

Device Test Test Documentation Job Raw Log
Arista cEOS status
RT-3.52: Multidimensional test for Static GUE Encap/Decap based on BGP path selection and selective DSCP marking
11b3f6a9 Log
Cisco 8000E status
RT-3.52: Multidimensional test for Static GUE Encap/Decap based on BGP path selection and selective DSCP marking
f6efe607 Log
Cisco XRd status
RT-3.52: Multidimensional test for Static GUE Encap/Decap based on BGP path selection and selective DSCP marking
7683297f Log
Juniper ncPTX status
RT-3.52: Multidimensional test for Static GUE Encap/Decap based on BGP path selection and selective DSCP marking
6a640ce4 Log
Nokia SR Linux status
RT-3.52: Multidimensional test for Static GUE Encap/Decap based on BGP path selection and selective DSCP marking
1231ea76 Log
Openconfig Lemming status
RT-3.52: Multidimensional test for Static GUE Encap/Decap based on BGP path selection and selective DSCP marking
d9a77e76 Log

Hardware Devices

Device Test Test Documentation Raw Log
Arista 7808 status
RT-3.52: Multidimensional test for Static GUE Encap/Decap based on BGP path selection and selective DSCP marking
Cisco 8808 status
RT-3.52: Multidimensional test for Static GUE Encap/Decap based on BGP path selection and selective DSCP marking
Juniper PTX10008 status
RT-3.52: Multidimensional test for Static GUE Encap/Decap based on BGP path selection and selective DSCP marking
Nokia 7250 IXR-10e status
RT-3.52: Multidimensional test for Static GUE Encap/Decap based on BGP path selection and selective DSCP marking

Help

@gemini-code-assist gemini-code-assist Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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:

  1. There are some formatting errors and a typo in the IP address table.
  2. 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.

@coveralls

coveralls commented Dec 13, 2025

Copy link
Copy Markdown

Pull Request Test Coverage Report for Build 21971047164

Details

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage remained the same at 10.114%

Totals Coverage Status
Change from base Build 21941007643: 0.0%
Covered Lines: 2300
Relevant Lines: 22741

💛 - Coveralls

Update some of the AI suggested changes around duplicate IP addresses.
@sachendras

Copy link
Copy Markdown
Contributor Author

/gemini review

@gemini-code-assist gemini-code-assist Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

sachendras and others added 4 commits December 23, 2025 02:25
…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 dplore changed the title Update README.md Update RT-3.52: Static GUE Encap/Decap from v4 to v6 Dec 22, 2025

@dplore dplore left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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

@sachendras

Copy link
Copy Markdown
Contributor Author

/gcburn

Updating the canonical OC to use UDP-V4 encap headers temporarily as a placeholder.
@sachendras

Copy link
Copy Markdown
Contributor Author

/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.
@sachendras

Copy link
Copy Markdown
Contributor Author

/gcbrun

@ksgireesha ksgireesha requested a review from dplore February 9, 2026 04:47
@sachendras sachendras merged commit fc2f6e5 into main Feb 19, 2026
17 checks passed
@sachendras sachendras deleted the sachendras-patch-30 branch February 19, 2026 18:45
ampattan pushed a commit to nokia/featureprofiles that referenced this pull request Apr 1, 2026
* 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]>
nsadhasivam pushed a commit to nsadhasivam/featureprofiles that referenced this pull request Apr 6, 2026
* 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]>
prakashbadri-arista pushed a commit to prakashbadri-arista/featureprofiles that referenced this pull request Jun 9, 2026
* 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]>
prakashbadri-arista pushed a commit to prakashbadri-arista/featureprofiles that referenced this pull request Jun 26, 2026
* 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]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants