Update RT-7.1 and RT-1.27#2
Closed
AmrNJ wants to merge 1 commit into
Closed
Conversation
Pull Request Test Coverage Report for Build 16666637779Warning: This coverage report may be inaccurate.This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.
Details
💛 - Coveralls |
AmrNJ
pushed a commit
that referenced
this pull request
Feb 20, 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, 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>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
RT-7.1 - Update timeout to avoid test falkiness
RT-1.27 - Add "skip_bgp_peer_group_send_community_type" deviation for Cisco