Want `swadm` subcommand for simulating physically reseating a transceiver
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 30/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Active
- Tech stack
- rust
- Domain
- backend-api-design, cli, networking
Research direction
Start by tracing the existing swadm sp xcvr reset and management-mode operations, along with the sled-agent reconciliation behavior described here. Determine whether a swadm subcommand and/or Dendrite API can reliably perform the listed reseat sequence; done means links and module state are restored without conflicting API operations.
Written by the indexing model from the issue text.
Description
In some situations, we'd like to "fully reset" a transceiver. As an example, the Tofino software sometimes fails to fully power up a module. We haven't seen this much for a while, but we did just have another, similar situation at a customer site. In this case, we were also running Omicron's rack-setup process, which means the sled-agent is continually attempting to construct the links we've configured.
This complicates things. swadm sp xcvr reset will fail if the module is in automatic mode, but setting it to manual with swam sp xcvr set-management-mode manual will fail if there are extant links. One could instead use the lower-level xcvradm tool to reset the module, but that's out of band, and the Tofino doesn't reliably restart its module state machines.
We should add a subcommand to swadm and possibly a new Dendrite API, for fully effecting this kind of simulated reseat. It's a little tricky in light of the sled-agent reconciliation mentioned above, but this would essentially do:
- probably set some bit to prevent API operations on the module
- store the parameters for all the links on the port
- delete all the links
- set the module into management mode
- reset the module
- set the module into auto mode
- recreate all the links
- unset the bit from the top
I'm not convinced this could be done reliably, but it's worth pursuing. We often have physical access
- Dominant language
- Rust
- Stars
- 21
- Forks
- 3
- Avg merge
- 8h 29m
- Merged PRs (30d)
- 2
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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.
More from oxidecomputer/dendrite
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
oxidecomputer/dendrite#380 ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 65/100
oxidecomputer/dendrite#375 ·
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
oxidecomputer/dendrite#369 ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 58/100
oxidecomputer/dendrite#368 ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 52/100
oxidecomputer/dendrite#359 · 1 comment ·
Maintainers usually reply within 1 day
All issues in oxidecomputer/dendrite
Similar issues
-
backend::vllm diffusion multimodal
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
lambdaclass/ethrex#7329 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
shadowsocks/shadowsocks-rust#2186 · 1 comment ·
-
C-bug S-awaiting-triage
Difficulty 1/5 Under an hour Newbie friendliness 92/100
juspay/hyperswitch#14479 ·
Maintainers usually reply within 1 day