cable duplicate label ; or Feature Request? #2257

New Issue

adam · 2025-12-29T17:24:11+01:00

adam commented

2025-12-29 17:24:11 +01:00

Originally created by @ak4443 on GitHub (Jan 4, 2019).

Environment

Python version:
NetBox version:

It is possible to provide cables with the same label.

As an an example:

At the switch 1 port 1 the cable with the label NET0001 is connected.
It is now possible to connect to port 2 a cable with the same label NET0001.

At this point, from my point of view, would have to be checked if there is a duplicate label.

Originally created by @ak4443 on GitHub (Jan 4, 2019). ### Environment * Python version:  * NetBox version:  It is possible to provide cables with the same label. As an an example: At the switch 1 port 1 the cable with the label NET0001 is connected. It is now possible to connect to port 2 a cable with the same label NET0001. At this point, from my point of view, would have to be checked if there is a duplicate label.

adam closed this issue

2025-12-29 17:24:11 +01:00

adam commented

2025-12-29 17:24:12 +01:00

@jbakklund commented on GitHub (Jan 4, 2019):

A label should ideally only have to be unique within the perimeters of a given site, allowing you to use e.g. label 'NET0001' in both London and Paris.

@jbakklund commented on GitHub (Jan 4, 2019): A label should ideally only have to be unique within the perimeters of a given site, allowing you to use e.g. label 'NET0001' in both London and Paris.

adam commented

2025-12-29 17:24:12 +01:00

@ak4443 commented on GitHub (Jan 4, 2019):

That's true.

Then at least below a site would have to be checked for duplicates.

@ak4443 commented on GitHub (Jan 4, 2019): That's true. Then at least below a site would have to be checked for duplicates.

adam commented

2025-12-29 17:24:12 +01:00

@jeremystretch commented on GitHub (Jan 4, 2019):

Cabling labels are entirely arbitrary and every organization uses whatever system works for them. It would be inappropriate for NetBox to assume any particular uniqueness requirement. If you need to check for duplicate labels, I suggest writing a validation report, which allows complete flexibility.

@jeremystretch commented on GitHub (Jan 4, 2019): Cabling labels are entirely arbitrary and every organization uses whatever system works for them. It would be inappropriate for NetBox to assume any particular uniqueness requirement. If you need to check for duplicate labels, I suggest writing a validation report, which allows complete flexibility.

adam commented

2025-12-29 17:24:12 +01:00

@ak4443 commented on GitHub (Jan 4, 2019):

Thanks ....

my workaround are in postgres DB:

create unique index unique_label on dcim_calbe(label) ;

Thus, a label can only be created once and Postgres reports a readable error.

@ak4443 commented on GitHub (Jan 4, 2019): Thanks .... my workaround are in postgres DB: create unique index unique_label on dcim_calbe(label) ; Thus, a label can only be created once and Postgres reports a readable error.

Sign in to join this conversation.

Branches Tags

main

update-changelog-comments-docs

feature-removal-issue-type

20911-dropdown

20239-plugin-menu-classes-mutable-state

21097-graphql-id-lookups

feature

fix_module_substitution

20923-dcim-templates

20044-elevation-stuck-lightmode

feature-ip-prefix-link

v4.5-beta1-release

20068-import-moduletype-attrs

20766-fix-german-translation-code-literals

20378-del-script

7604-filter-modifiers-v3

circuit-swap

12318-case-insensitive-uniqueness

20637-improve-device-q-filter

20660-script-load

19724-graphql

20614-update-ruff

14884-script

02496-max-page

19720-macaddress-interface-generic-relation

19408-circuit-terminations-export-templates

20203-openapi-check

fix-19669-api-image-download

7604-filter-modifiers

19275-fixes-interface-bulk-edit

fix-17794-get_field_value_return_list

11507-show-aggregate-and-rir-on-api

9583-add_column_specific_search_field_to_tables

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/netbox#2257