-
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.
- Loading branch information
Showing
18 changed files
with
571 additions
and
51 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
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 |
48 changes: 48 additions & 0 deletions
48
feature/platform/transceiver/ZR_pre-fec_ber_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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,48 @@ | ||
# gNMI-1.20: Telemetry: 400ZR Optics Pre-FEC(Forward Error Correction) BER(Bit Error Rate) | ||
|
||
## Summary | ||
|
||
Validate 400ZR optics module reports pre-FEC bit error rate performance data. | ||
|
||
## Procedure | ||
|
||
* Connect two ZR interfaces using a duplex LC fiber jumper such that TX | ||
output power of one is the RX input power of the other module. | ||
* To establish a point to point ZR link ensure the following: | ||
* Both transceivers state is enabled | ||
* Both transceivers are set to a valid target TX output power | ||
example -10 dBm | ||
* Both transceivers are tuned to a valid centre frequency | ||
example 193.1 THz | ||
* With the link ZR link established as explained above, verify that the | ||
following ZR transceiver telemetry paths exist and are streamed for both | ||
the ZR optics | ||
* /terminal-device/logical-channels/channel/otn/state/pre-fec-ber/instant | ||
* /terminal-device/logical-channels/channel/otn/state/pre-fec-ber/avg | ||
* /terminal-device/logical-channels/channel/otn/state/pre-fec-ber/min | ||
* /terminal-device/logical-channels/channel/otn/state/pre-fec-ber/max | ||
|
||
**Note:** For min, max, and avg values, 10 second sampling is preferred. If | ||
10 seconds is not supported, the sampling interval used must be | ||
communicated. | ||
|
||
|
||
* Verify that the optics pre-FEC BER is updated after the interface flaps. | ||
|
||
* Enable a pair of ZR interfaces on the DUT as explained above. | ||
* Verify the ZR optics pre FEC BER PMs are in the normal range. | ||
* Disable or shut down the interface on the DUT. | ||
* Re-enable the interfaces on the DUT. | ||
* Verify the ZR optics pre FEC PM is updated to the value in the normal | ||
range again. Typical expected value should be less than 1.2E-2 | ||
|
||
## Config Parameter coverage | ||
|
||
* /components/component/oc-transceiver:transceiver/oc-transceiver/config/enabled | ||
|
||
## Telemetry Parameter coverage | ||
|
||
* /terminal-device/logical-channels/channel/otn/state/pre-fec-ber/instant | ||
* /terminal-device/logical-channels/channel/otn/state/pre-fec-ber/avg | ||
* /terminal-device/logical-channels/channel/otn/state/pre-fec-ber/min | ||
* /terminal-device/logical-channels/channel/otn/state/pre-fec-ber/max |
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
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.