oxidecomputer / oxidecomputer/dendrite
Propagate more information about transceiver failures
Open
@bnaecker is already working on this.
Since May 7, 2025.
- Dominant language
- Rust
- Stars
- 20
- Forks
- 3
- Avg merge
- 3d 11h
- Merged PRs (30d)
- 4
Description
swadm reports information about transceivers, and will show some basic failure information if we can't read from the modules. For example:
root@oxz_switch1:~# swadm switch-port transceiver list
Port State Reset Interrupt Power Power control Vendor Part No. Serial No.
qsfp0 faulted (Failed)
However, we added much more fine-grained error information to the transceiver-control protocol used under the hood to talk to the SP about the transceivers. We can see this with xcvradm for example:
root@oxz_switch1:~# xcvradm -i sidecar0 -t 0 vendor-info
Port Identifier Vendor Part Rev Serial Mfg date
Some operations failed, errors below
Port Error
0 Hardware error accessing module 0: The module stretched SCL too long
We need to go back and expose those error details through the Dendrite API and to swadm as well.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.