Skip to content

Create README.md - #1

Open
paramasivamn1 wants to merge 3 commits into
mainfrom
paramasivamn1-patch-1
Open

paramasivamn1 wants to merge 3 commits into
mainfrom
paramasivamn1-patch-1

Conversation

@paramasivamn1

Copy link
Copy Markdown
Owner

No description provided.

@paramasivamn1

Copy link
Copy Markdown
Owner Author

Kindly review new test which can cover b/512354109

paramasivamn1 pushed a commit that referenced this pull request Aug 24, 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, 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 <dloher@google.com>
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.

1 participant