-
Notifications
You must be signed in to change notification settings - Fork 148
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge branch 'main' into isis_missing_intf_afi_deviation
- Loading branch information
Showing
189 changed files
with
5,520 additions
and
17,354 deletions.
There are no files selected for viewing
This file contains 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,51 +1,15 @@ | ||
--- | ||
name: New featureprofiles test requirement | ||
about: Use this template to document the requirements for a new test to be implemented. | ||
about: Use this template to create an issue to assign and track implemenation of the code for a test. | ||
title: '' | ||
labels: enhancement | ||
assignees: '' | ||
|
||
--- | ||
|
||
# TestID-x.y: Short name of test here | ||
|
||
## Summary | ||
|
||
Write a few sentences or paragraphs describing the purpose and scope of the test. | ||
|
||
## Procedure | ||
|
||
* Test #1 - Name of test | ||
* Step 1 | ||
* Step 2 | ||
* Step 3 | ||
|
||
* Test #2 - New of test | ||
* Step 1 | ||
* Step 2 | ||
* Step 3 | ||
|
||
|
||
## Config Parameter Coverage | ||
|
||
Add list of OpenConfig 'config' paths used in this test, if any. | ||
|
||
## Telemetry Parameter Coverage | ||
|
||
Add list of OpenConfig 'state' paths used in this test, if any. | ||
|
||
## Protocol/RPC Parameter Coverage | ||
# Request for New Test Code Implementation Instructions | ||
|
||
Add list of OpenConfig RPC's (gNMI, gNOI, gNSI, gRIBI) used in the list | ||
* The label 'enhancement' is automatically set by this template. | ||
* Add a label for the test priority according to the test requirements. (p0, p1, p2) | ||
* Add a link in this issue description to the README.md for the test requirements. For example: | ||
|
||
For example: | ||
* gNMI | ||
* Set | ||
* Subscribe | ||
* gNOI | ||
* System | ||
* KillProcess | ||
* Healthz | ||
* Get | ||
* Check | ||
* Artifact | ||
Implement code for [Test name here](https://github.com/openconfig/featureprofiles/blob/main/feature/example/tests/topology_test/README.md) |
This file contains 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
This file contains 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
This file contains 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,71 @@ | ||
--- | ||
name: New featureprofiles test requirement | ||
about: Use this template to document the requirements for a new test to be implemented. | ||
title: '' | ||
labels: enhancement | ||
assignees: '' | ||
|
||
--- | ||
|
||
# Instructions for this template | ||
|
||
Below is the required template for writing test requirements. Good examples of test | ||
requirements include: | ||
|
||
* [TE-3.7: Base Hierarchical NHG Update](/feature/gribi/otg_tests/base_hierarchical_nhg_update/README.md) | ||
* [gNMI-1.13: Telemetry: Optics Power and Bias Current](https://github.com/openconfig/featureprofiles/blob/main/feature/platform/tests/optics_power_and_bias_current_test/README.md) | ||
* [RT-5.1: Singleton Interface](https://github.com/openconfig/featureprofiles/blob/main/feature/interface/singleton/otg_tests/singleton_test/README.md) | ||
|
||
# TestID-x.y: Short name of test here | ||
|
||
## Summary | ||
|
||
Write a few sentences or paragraphs describing the purpose and scope of the test. | ||
|
||
## Testbed type | ||
|
||
* Specify the .testbed topology file from the [topologies](https://github.com/openconfig/featureprofiles/tree/main/topologies) folder to be used with this test | ||
|
||
## Procedure | ||
|
||
* Sub Test #1 - Name of test | ||
* Step 1 | ||
* Step 2 | ||
* Validation and pass fail criteria | ||
|
||
* Sub Test #2 - New of test | ||
* Step 1 | ||
* Step 2 | ||
* Validation and pass fail criteria | ||
|
||
## Config Parameter Coverage | ||
|
||
Add list of OpenConfig 'config' paths used in this test, if any. | ||
|
||
## Telemetry Parameter Coverage | ||
|
||
Add list of OpenConfig 'state' paths used in this test, if any. | ||
|
||
## Protocol/RPC Parameter Coverage | ||
|
||
Add list of OpenConfig RPC's (gNMI, gNOI, gNSI, gRIBI) used in the list, if any. | ||
|
||
For example: | ||
|
||
* gNMI | ||
* Set | ||
* Subscribe | ||
* gNOI | ||
* System | ||
* KillProcess | ||
* Healthz | ||
* Get | ||
* Check | ||
* Artifact | ||
|
||
## Required DUT platform | ||
|
||
* Specify the minimum DUT-type: | ||
* MFF - A modular form factor device containing LINECARDs, FABRIC and redundant CONTROLLER_CARD components | ||
* FFF - fixed form factor | ||
* vRX - virtual router device |
This file contains 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,68 @@ | ||
Summary: | ||
- When operating in "openconfig mode", NOS (network operating system) defaults should match what OC defines as the defaults i.e, | ||
- For BGP, there are no defaults for AFI-SAFI at the neighbor and peer-group levels. However at the global level the default is "false" | ||
- This test currently only verifies the defaults for ipv4-unicast and ipv6-unicast families. However, this test can be extended further to cover for other | ||
AFI-SAFIs as well in future. | ||
- The test will check for default implementations under the neighbor and peer-group hierarchies and also test for inheritance rules as was specified in [pull/774](https://github.com/openconfig/public/pull/774) and [pull/815](https://github.com/openconfig/public/pull/815). | ||
|
||
|
||
Topology: | ||
ATE (Port1) <-EBGP-> (Port1) DUT (Port2) <-IBGP-> (Port2) ATE | ||
- Connect ATE Port1 to DUT port1 (EBGP peering) | ||
- Connect ATE Port2 to DUT port2 (IBGP peering) | ||
|
||
Procedure: | ||
- [Test case-1] AFI-SAFI configurations at "neighbor level": | ||
- Push EBGP and IBGP OC configuration to the DUT | ||
- Configuration should include corresponding IPv4 and IPv6 neighbor configurations. | ||
- Ensure that only IPv4-Unicast enabled boolean is made "true" for IPv4 neighbor. "IPv6-unicast enabled" boolean is left to OC default for the IPv4 peer". | ||
- Ensure that only IPv6-Unicast enabled boolean is made "true" for IPv6 neighbor. "IPv4-unicast enabled" boolean is left to OC default for the IPv6 peer". | ||
- Ensure that there are no AFI-SAFI configurations at the global and peer-group levels. | ||
- On the ATE side ensure that IPv4-unicast and IPv6-unicast AFI-SAFI are enabled==true for IPv4 and IPv6 neighbors. | ||
- verification: | ||
- For IPv4 neighbor, ensure that the IPv4 neighborship is up and IPv6-unicast capability is not negotiated. | ||
- For IPv6 neighbor ensure that the IPv6 neighborship is up and IPv4-unicast capability is not negotiated. | ||
- [Test case-2] IPv4-unicast and IPv6-Unicast AFI-SAFIs enabled at peer-group level: | ||
- Configuration at the neighbor level is same as in [Test case-1] except for IPv4-unicast and IPv6-unicast being enabled at the peer-group level | ||
- No configuration should be made at the global AFI-SAFI level | ||
- verification: | ||
- For IPv4 neighbor, ensure that the IPv4 neighborship is up and both IPv4-unicast and IPv6-unicast capabilities are negotiated. | ||
- For IPv6 neighbor ensure that the IPv6 neighborship is up and both IPv4-unicast and IPv6-unicast capabilities are negotiated. | ||
- [Test case-4] IPv4-unicast and IPv6-Unicast AFI-SAFIs enabled at Global level: | ||
- Configuration at the neighbor level is same as in [Test case-1] except for IPv4-unicast and IPv6-unicast being enabled at the global level | ||
- No configuration should be made at the peer-group AFI-SAFI level | ||
- verification: | ||
- For IPv4 neighbor, ensure that the IPv4 neighborship is up and both IPv4-unicast and IPv6-unicast capabilities are negotiated. | ||
- For IPv6 neighbor ensure that the IPv6 neighborship is up and both IPv4-unicast and IPv6-unicast capabilities are negotiated. | ||
|
||
Config Parameter coverage: | ||
|
||
/network-instances/network-instance/protocols/protocol/bgp/global/config/as | ||
/network-instances/network-instance/protocols/protocol/bgp/global/config/router-id | ||
/network-instances/network-instance/protocols/protocol/bgp/neighbors/neighbor/config/auth-password | ||
/network-instances/network-instance/protocols/protocol/bgp/neighbors/neighbor/config/neighbor-address | ||
/network-instances/network-instance/protocols/protocol/bgp/neighbors/neighbor/config/peer-as | ||
/network-instances/network-instance/protocols/protocol/bgp/neighbors/neighbor/neighbor-address | ||
/network-instances/network-instance/protocols/protocol/bgp/neighbors/neighbor/afi-safis/afi-safi/config/enabled | ||
|
||
|
||
/network-instances/network-instance/protocols/protocol/bgp/peer-groups/peer-group/config/auth-password | ||
/network-instances/network-instance/protocols/protocol/bgp/peer-groups/peer-group/config/neighbor-address | ||
/network-instances/network-instance/protocols/protocol/bgp/peer-groups/peer-group/config/peer-as | ||
/network-instances/network-instance/protocols/protocol/bgp/neighbors/neighbor/config/peer-group/peer-group-name | ||
/network-instances/network-instance/protocols/protocol/bgp/peer-groups/peer-group/afi-safis/afi-safi/config/enabled | ||
|
||
/network-instances/network-instance/protocols/protocol/bgp/global/afi-safis/afi-safi/config/enabled | ||
|
||
Telemetry Parameter coverage: | ||
/network-instances/network-instance/protocols/protocol/bgp/neighbors/neighbor/state/session-state | ||
/network-instances/network-instance/protocols/protocol/bgp/neighbors/neighbor/state/supported-capabilities | ||
/network-instances/network-instance/protocols/protocol/bgp/neighbors/neighbor/state/peer-type | ||
/network-instances/network-instance/protocols/protocol/bgp/neighbors/neighbor/state/peer-as | ||
/network-instances/network-instance/protocols/protocol/bgp/neighbors/neighbor/state/supported-capabilities | ||
|
||
/network-instances/network-instance/protocols/protocol/bgp/peer-groups/peer-group/state/peer-type | ||
/network-instances/network-instance/protocols/protocol/bgp/peer-groups/peer-group/state/peer-as | ||
/network-instances/network-instance/protocols/protocol/bgp/peer-groups/peer-group/state/local-as | ||
/network-instances/network-instance/protocols/protocol/bgp/neighbors/neighbor/state/peer-group | ||
|
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
Oops, something went wrong.