Page MenuHomePhabricator

Audit Serial Console Connections (2026)
Open, LowPublic

Description

Over time the documentation of our serial console connections has drifted a little bit. It's usually not a major problem but we should try to get on top of it.

Currently we have 3 types of problems:

  1. OpenGear ports are configured with a name of a device, but nothing is connected to that port
  2. OpenGear ports are configured with the wrong/old name of connected device
  3. OpenGear port is correct with name but Netbox shows it as empty or going somewhere else

Config Generation

Netbox is now able to generate the config for our scs servers once the connections are properly documented on it, including setting the right port speed based on the vendor/model etc.

Devices

The following devices need to be audited for connections:

  • scs-a1-codfw
  • scs-c1-codfw
  • scs-e3-codfw
  • scs-a8-eqiad
  • scs-c1-eqiad
  • scs-f8-eqiad
  • scs-ulsfo
  • scs-by27-esams
  • scs-eqsin
  • scs-drmrs
  • scs-magru

The audit should verify what ports are in use, and what devices are connected. Then Netbox should be updated to match. When the audit is complete the config Netbox generates can be pushed, which will remove the config from any ports no longer in use.

Related Objects

Event Timeline

cmooney triaged this task as Low priority.

@Jclark-ctr @VRiley-WMF, going through the ports on scs-a8-eqiad these were the issues I found.

Port 8 - should be connected to ps1-a8-eqiad, but there is nothing coming back? Hopefully easy to solve as it's in-rack
Port 17 - says it's connected to asw2-a1-eqiad, but no output on console (lsw1-a1-eqiad is on a different port)
Port 24 - no output on console? this says it's going to asw2-a8-eqiad, not sure if it is still cabled to that?
Port 44 - no output on console? it says it's going to msw2-eqiad but nothing comes back (I'm not sure it's possible to be connected to that, do we have RJ45 copper patches to row e/f?)

Additionally ports 41 and 45 show no connection, and had names that make no sense (already connected elsewhere), so I left them empty in Netbox. Original names are saved in P96498, I pushed the config generated from Netbox now to remove/rename eveyrthing so we are all in sync.

scs-a1-codfw:
ps1-b7-codfw on port 15 was being used to console to a test server. i moved it back for now. if they yell, i'll run a new connection instead. it had been used for almost a year.
@cmooney the console port on the atlas on port 47, there is no cable connected to it and it doesn't seem to have an approriate console port. not without using a 9 pin. i can fix this if we want to do that. or disable the port.

scs-c1-codfw:
i ran into a number of ports where they connected to the switch, but the switch name did not come up on the login. I can trace these to confirm but would like to know if there is a less ladder intensive solution =) ports 22, 23, 26-29, and 41
did also find a few that were disconnected. will investigate this week. 16, 31, 43

scs-e3-codfw:
i need to investigate disconnected port on 37
found two more that are not showing the switch name 45, and 47.

@cmooney the console port on the atlas on port 47, there is no cable connected to it and it doesn't seem to have an approriate console port. not without using a 9 pin. i can fix this if we want to do that. or disable the port.

Thanks for looking at this Jenn <3. For that I think we are ok, the console if needed is only for initial setup, so I don't think it's worth rigging up a custom DB9 connection for the current one.

scs-c1-codfw:
i ran into a number of ports where they connected to the switch, but the switch name did not come up on the login. I can trace these to confirm but would like to know if there is a less ladder intensive solution =) ports 22, 23, 26-29, and 41
did also find a few that were disconnected. will investigate this week. 16, 31, 43

scs-e3-codfw:
i need to investigate disconnected port on 37
found two more that are not showing the switch name 45, and 47.

Thanks. I think the main goal here is to make sure Netbox matches what's actually in place (and then use the generated config from netbox to label all the ports). So whatever we can do to get us there is great thanks.