Fix VLAN config on port 18 on Nintendo #321

Open
opened 2026-01-29 13:27:45 +01:00 by oysteikt · 3 comments
Owner

Someone should bring a serial cable down to the server room to access the switch, and reset any VLAN config set on port 18. It's currently not usable, presumably because it was configured to be something else previously.

Someone should bring a serial cable down to the server room to access the switch, and reset any VLAN config set on port 18. It's currently not usable, presumably because it was configured to be something else previously.
oysteikt added the networking label 2026-01-29 13:27:45 +01:00
oysteikt added this to the Kanban project 2026-01-29 13:27:45 +01:00
Owner

Or, perhaps at least document it, in case it was set this way for a good reason that we just forgot 😅

Or, perhaps at least document it, in case it was set this way for a good reason that we just forgot 😅
Author
Owner

It is already documented, see https://wiki.pvv.ntnu.no/wiki/Maskiner/nintendo

It is already documented, see https://wiki.pvv.ntnu.no/wiki/Maskiner/nintendo
Owner

We talked about a few tricks when configuring the switch, so I assume it is either

  • physically broken
  • half-configured to test a separate OOB network for BMCs without exposing them to the internet (half- because that would require multiple ports to be useful)
  • half-configured as a port to the OV network or as alternate upstream

If 1, it is probably unfixable, if 2 or 3, those features are still useful, and we should probably finish implementing them rather than "fixing" the configuration, unless we really need more available ports than we have now. If we need the ports, then sure, clear the config!

We talked about a few tricks when configuring the switch, so I assume it is either - physically broken - half-configured to test a separate OOB network for BMCs without exposing them to the internet (half- because that would require multiple ports to be useful) - half-configured as a port to the OV network or as alternate upstream If 1, it is probably unfixable, if 2 or 3, those features are still useful, and we should probably finish implementing them rather than "fixing" the configuration, unless we really need more available ports than we have now. If we need the ports, then sure, clear the config!
oysteikt moved this to Low priority in Kanban on 2026-01-29 14:43:09 +01:00
Sign in to join this conversation.
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Drift/issues#321