Page MenuHomePhabricator

Document eqsin power connections in Netbox
Closed, ResolvedPublic

Description

During the original eqsin buildout, a spreadsheet was made that documented all power connections. This should be moved to Netbox now

Related Objects

Event Timeline

faidon triaged this task as Medium priority.Oct 16 2018, 9:11 AM
faidon created this task.

This refers to power connections specifically as it's a subtask of the power incident, but that spreadsheet covers patches as well, and we should probably document these as well.

Also, I'm not sure if this:

603 1042 C13/C14 Power 6' Black asw-0603-eqsin PSU 1 PDU tower A
603 1043 C13/C14 Power 6' Black asw-0603-eqsin PSU 2 PDU tower B
604 1045 C13/C14 Power 6' Black asw-0604-eqsin PSU 1 PDU tower A
604 1046 C13/C14 Power 6' Black asw-0604-eqsin PSU 2 PDU tower B

…is correct. I think I recall seeing PEM 0s being out when power feed B was under maintenance; maybe @ayounsi can verify.

Oct 14 19:05:27 asw1-eqsin craftd[1962]: Minor alarm cleared, FPC 0 PEM 0 is not powered
Oct 14 19:05:28 asw1-eqsin craftd[1962]: Minor alarm cleared, FPC 1 PEM 0 is not powered

So indeed PEM0 goes to Tower B. Doc updated.

All the power connections have been imported, note that some data can't be imported such as cable length and cable ID.

See https://netbox.wikimedia.org/dcim/power-connections/?site=eqsin

About the other links, the only less straightforward interfaces are the server's uplinks as their name can't be derived from the device/port table.
I'll keep the task open until at least all the other links are imported.

Awesome, thanks! No field for Cable IDs or labels is a bit disappointing :( It doesn't look like we can do it with a custom field either, but I'm not 100% sure.

We should file an upstream bug to request either a cable ID/label field, or support for custom fields for connections...

ayounsi claimed this task.

I imported everything that was not the servers' uplinks (for the reason mentioned above).