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

Wicket could show basic transceiver status during rack setup #6710

Open
bnaecker opened this issue Sep 27, 2024 · 1 comment · May be fixed by #7562
Open

Wicket could show basic transceiver status during rack setup #6710

bnaecker opened this issue Sep 27, 2024 · 1 comment · May be fixed by #7562
Labels
networking Related to the networking. wicket Operator Interaction Via Technician Port

Comments

@bnaecker
Copy link
Collaborator

Most customer installs have spent time handling the low-level physical details around transceivers. Common issues include swapped transmit / receive fiber pairs, dirty fiber, or not-quite-seated transceiver modules. Many of these can be diagnosed by looking at the basic transceiver monitoring information, most notably transmit / receive power. This data is available via Dendrite, but only available through the public API after rack setup has completed and Nexus is running. Before that, it's only accessible from the switch zone with swadm or xcvradm, both of which must be run in the switch zone by an Oxide employee.

It would be extremely valuable to show this information during rack setup, in the wicket UI. Wicketd can ask Dendrite (over localhost) for all transceivers that are plugged in, or we could optionally restrict that to the transceivers in the switch ports that the RSS TOML configuration expects to use. Either of these would be really useful when getting the basic networking connectivity off the ground at new customer sites.

@bnaecker bnaecker added networking Related to the networking. wicket Operator Interaction Via Technician Port labels Sep 27, 2024
@sunshowers
Copy link
Contributor

Chatted with Ben -- it would be good to get this in before the next customer install, but it's not a blocker for r11.

bnaecker added a commit that referenced this issue Feb 19, 2025
- Make the current inventory specific to MGS
- Add per-switch transceiver list to the inventory as well
- Fetch transceiver state periodically in wicketd
- Draw transceiver details in the wicket inventory panel
- Fixes #6710
bnaecker added a commit that referenced this issue Feb 19, 2025
- Make the current inventory specific to MGS
- Add per-switch transceiver list to the inventory as well
- Fetch transceiver state periodically in wicketd
- Draw transceiver details in the wicket inventory panel
- Fixes #6710
bnaecker added a commit that referenced this issue Feb 19, 2025
- Make the current inventory specific to MGS
- Add per-switch transceiver list to the inventory as well
- Fetch transceiver state periodically in wicketd
- Draw transceiver details in the wicket inventory panel
- Fixes #6710
bnaecker added a commit that referenced this issue Feb 19, 2025
- Make the current inventory specific to MGS
- Add per-switch transceiver list to the inventory as well
- Fetch transceiver state periodically in wicketd
- Draw transceiver details in the wicket inventory panel
- Fixes #6710
@bnaecker bnaecker linked a pull request Feb 19, 2025 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
networking Related to the networking. wicket Operator Interaction Via Technician Port
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants