Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clarification of terminal-phy-protocol-stats/fec-uncorrectable-blocks #1255

Open
proberts2022 opened this issue Feb 11, 2025 · 0 comments
Open

Comments

@proberts2022
Copy link

Within openconfig-terminal-device.yang, the grouping terminal-phy-protocol-stats is defined to report a set of statistics about the operation of the Forward Error Correction. And this group is used both for the optical channel component, the logical-channel OTN and the logical channel Ethernet.
Within the group there are several attributes that use an "avg-min-max-instant-stats-xxx" type that allows for the reporting of intervalized statistics.
Within the CMIS specification for transceivers, these statistics are supported as VDM Observable Types and support include reporting of the avg, min, max, and current value over an interval. This part lines up nicely.

The fec-uncorrectable-blocks attribute is defined within openconfig to be a simple counter64 and not a interval stats type. The description of this attribute is "The number of blocks or frames that were uncorrectable by the FEC"

Within CMIS, this appear to relate to the Frame Error Count (FERC) and that is also VDM Observable type with a min, max, avg, and current value. Also in CMIS 5.2 (April 2022) a "Total Accumulated" value was also added.

Question: Which of the following value from CMIS should be used to populate the fec-uncorrectable-blocks?
FERC Sample Average
FERC Current Sample Value
FERC Total Accumulated
or is some other computation to be used for this fec-uncorrectable-blocks attribute?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: No status
Development

No branches or pull requests

1 participant