Skip to content

Add the initial ISIS base and adjacency feature profile#3

Merged
drautio merged 2 commits intomainfrom
isis-1
Jan 25, 2022
Merged

Add the initial ISIS base and adjacency feature profile#3
drautio merged 2 commits intomainfrom
isis-1

Conversation

@drautio
Copy link
Copy Markdown
Contributor

@drautio drautio commented Dec 20, 2021

Add the initial ISIS base and adjacency feature profile.

 On branch isis-1
 Changes to be committed:
	new file:   isis/base_isis_and_adjacenty/feature.textproto

Add the initial ISIS base and adjacency feature profile.
@drautio drautio requested a review from rsgcp December 20, 2021 21:37
@dplore dplore changed the title Committer: Dan Rautio <drautio@google.com> Add the initial ISIS base and adjacency feature profile Dec 20, 2021
@sthesayi sthesayi requested a review from dplore December 22, 2021 14:24
@dplore
Copy link
Copy Markdown
Member

dplore commented Jan 11, 2022

@drautio friendly reminder, can you respond to the comments?

 On branch isis-1
 Your branch is up to date with 'origin/isis-1'.

 Changes to be committed:
	new file:   isis/isis_auth/feature.textproto
	renamed:    isis/base_isis_and_adjacenty/feature.textproto -> isis/isis_base/feature.textproto

address comments
@drautio
Copy link
Copy Markdown
Contributor Author

drautio commented Jan 24, 2022

I addressed all the comments and uploaded new files.

Copy link
Copy Markdown
Contributor

@sthesayi sthesayi left a comment

Choose a reason for hiding this comment

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

Just a couple of minor comments. LGTM.

}
telemetry_path {
path: "/network-instances/network-instance/protocols/protocol/isis/interfaces/interface/authentication/key/state/auth-password"
}
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.

We should have a dependency on isis_base feature profile.

@drautio drautio merged commit 2f17fb2 into main Jan 25, 2022
@dplore dplore mentioned this pull request Feb 9, 2022
@dplore dplore deleted the isis-1 branch February 17, 2022 16:28
sgirishj added a commit to sgirishj/featureprofiles that referenced this pull request Oct 12, 2022
… to check for DUT vendor at the start of the test with the help of a map and moved PID finding logic into its own function
liulk pushed a commit that referenced this pull request Oct 12, 2022
* Code commit for TE-8.1: DUT Daemon Failure

* Updated file permissions and made some minor changes in the code comments

* Updated file permissions again

* Removed newline in the end

* Addressed review comments: updated Arista and Cisco gRIBI daemon names, changed gNOI kill signal from sigkill to sigterm and changed traffic flow setup as suggested.

* Addressed review comments #2: removed testTraffic and reused startTraffic/stopAndVerifyTraffic instead

* Addressed review comments #3: Gribi -> GRIBI, added support to check for DUT vendor at the start of the test with the help of a map and moved PID finding logic into its own function
singh-prem pushed a commit to mingyangcisco/featureprofiles that referenced this pull request Dec 13, 2022
* Code commit for TE-8.1: DUT Daemon Failure

* Updated file permissions and made some minor changes in the code comments

* Updated file permissions again

* Removed newline in the end

* Addressed review comments: updated Arista and Cisco gRIBI daemon names, changed gNOI kill signal from sigkill to sigterm and changed traffic flow setup as suggested.

* Addressed review comments openconfig#2: removed testTraffic and reused startTraffic/stopAndVerifyTraffic instead

* Addressed review comments openconfig#3: Gribi -> GRIBI, added support to check for DUT vendor at the start of the test with the help of a map and moved PID finding logic into its own function
prinikasn pushed a commit that referenced this pull request Jun 30, 2023
* Code commit for TE-8.1: DUT Daemon Failure

* Updated file permissions and made some minor changes in the code comments

* Updated file permissions again

* Removed newline in the end

* Addressed review comments: updated Arista and Cisco gRIBI daemon names, changed gNOI kill signal from sigkill to sigterm and changed traffic flow setup as suggested.

* Addressed review comments #2: removed testTraffic and reused startTraffic/stopAndVerifyTraffic instead

* Addressed review comments #3: Gribi -> GRIBI, added support to check for DUT vendor at the start of the test with the help of a map and moved PID finding logic into its own function
nsadhasivam added a commit to nsadhasivam/featureprofiles that referenced this pull request Oct 30, 2024
alshabib pushed a commit to alshabib/featureprofiles that referenced this pull request Jan 19, 2025
sachendras added a commit that referenced this pull request Dec 13, 2025
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 added a commit that referenced this pull request Feb 19, 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 #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 was referenced Mar 26, 2026
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.

4 participants