Cable Identifier #1870

Closed
opened 2025-12-29 17:19:56 +01:00 by adam · 2 comments
Owner

Originally created by @siddallhotmail on GitHub (Jul 25, 2018).

[X ] Feature request
[ ] Bug report
[ ] Documentation
[ ] Housekeeping

Hi I'd like to request a new feature which would allow us to identify cables within the Netbox system.

In our datacentres all cables are labelled with a unique cable ID, so that when patching equipment in an engineer can ascertain what cables are in use and where.

I'd like a new field to be added to the dcim_interfaceconnections table as "cable_id" which is a unique field and would allow us to populate a cable ID when making a connection between two interfaces.

I've already made the changes in a fork of the main code... but would prefer to keep with the NetBox official release.

Many thanks

Martin

Originally created by @siddallhotmail on GitHub (Jul 25, 2018). [X ] Feature request <!-- An enhancement of existing functionality --> [ ] Bug report <!-- Unexpected or erroneous behavior --> [ ] Documentation <!-- A modification to the documentation --> [ ] Housekeeping <!-- Changes pertaining to the codebase itself --> Hi I'd like to request a new feature which would allow us to identify cables within the Netbox system. In our datacentres all cables are labelled with a unique cable ID, so that when patching equipment in an engineer can ascertain what cables are in use and where. I'd like a new field to be added to the dcim_interfaceconnections table as "cable_id" which is a unique field and would allow us to populate a cable ID when making a connection between two interfaces. I've already made the changes in a fork of the main code... but would prefer to keep with the NetBox official release. Many thanks Martin
adam added the status: duplicate label 2025-12-29 17:19:56 +01:00
adam closed this issue 2025-12-29 17:19:56 +01:00
Author
Owner

@siddallhotmail commented on GitHub (Jul 25, 2018):

Can see this is similar to #20 but that doesn't seem to be making any progress, been open since 2016 !!

@siddallhotmail commented on GitHub (Jul 25, 2018): Can see this is similar to #20 but that doesn't seem to be making any progress, been open since 2016 !!
Author
Owner

@lampwins commented on GitHub (Jul 25, 2018):

@martinpsiddall this sort of thing is best served under #20. You will find there has been quite a lot of activity on that issue lately. You can also find that it has been tagged for v2.5. Yes, #20 is currently the oldest FR, but it is also by far one of the most complex to implement, so great care must be taken in its design.

@lampwins commented on GitHub (Jul 25, 2018): @martinpsiddall this sort of thing is best served under #20. You will find there has been quite a lot of activity on that issue lately. You can also find that it has been tagged for v2.5. Yes, #20 is currently the oldest FR, but it is also by far one of the most complex to implement, so great care must be taken in its design.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#1870