starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-11 21:10:29 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

Support additional IDC port types in addition to 110 #4893

New Issue
Closed
opened 2025-12-29 19:21:43 +01:00 by adam · 5 comments
adam commented 2025-12-29 19:21:43 +01:00
Owner
Copy Link

Originally created by @amuckart on GitHub (May 10, 2021).

NetBox version

v2.11.2

Feature type

Data model extension

Proposed functionality

When creating front or rear port types I want to be able to select a type that accurately reflects the port type for IDC connectors.

LSA-Plus ("Krone") blocks are commonly used outside the USA. They use a different punch-down tool than 110 and different physical mounting.

Series 2 and High Band are the most commonly used variants but the specific variant can probably be managed as Inventory rather than port type.

Use case

In buildings whose infrastructure has been extended over time there are often multiple different types of IDC punchdown block that need different tools.

The ability to record these helps with making numerous infrastructure decisions in heterogeneous environments.

Database changes

Not sure, sorry.

External dependencies

None

Originally created by @amuckart on GitHub (May 10, 2021). ### NetBox version v2.11.2 ### Feature type Data model extension ### Proposed functionality When creating front or rear port types I want to be able to select a type that accurately reflects the port type for IDC connectors. LSA-Plus ("Krone") blocks are commonly used outside the USA. They use a different punch-down tool than 110 and different physical mounting. Series 2 and High Band are the most commonly used variants but the specific variant can probably be managed as Inventory rather than port type. ### Use case In buildings whose infrastructure has been extended over time there are often multiple different types of IDC punchdown block that need different tools. The ability to record these helps with making numerous infrastructure decisions in heterogeneous environments. ### Database changes Not sure, sorry. ### External dependencies None
adam added the type: featurestatus: needs ownerpending closure labels 2025-12-29 19:21:43 +01:00
adam closed this issue 2025-12-29 19:21:44 +01:00
adam commented 2025-12-29 19:21:44 +01:00
Author
Owner
Copy Link

@amuckart commented on GitHub (May 10, 2021):

An less preferable alternative would be to remove the "110" from the existing type and just generically record "IDC punchdown" as a type.

@amuckart commented on GitHub (May 10, 2021): An less preferable alternative would be to remove the "110" from the existing type and just generically record "IDC punchdown" as a type.
adam commented 2025-12-29 19:21:44 +01:00
Author
Owner
Copy Link

@martinum4 commented on GitHub (May 12, 2021):

To me it seems like a more generic approach ("punchdown") would make more sense, otherwise there should be additions for LSA (the old basis for LSA+) and R&M VS83 too because there are minor differences in tooling.
So far i use 110 punch as an indicator for LSA+ because that's all that is build into netbox.

@martinum4 commented on GitHub (May 12, 2021): To me it seems like a more generic approach ("punchdown") would make more sense, otherwise there should be additions for LSA (the old basis for LSA+) and R&M VS83 too because there are minor differences in tooling. So far i use 110 punch as an indicator for LSA+ because that's all that is build into netbox.
adam commented 2025-12-29 19:21:45 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (May 13, 2021):

Renaming "110 punch" to the less-specific "punchdown" seems like the way to go IMO.

@jeremystretch commented on GitHub (May 13, 2021): Renaming "110 punch" to the less-specific "punchdown" seems like the way to go IMO.
adam commented 2025-12-29 19:21:45 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Jul 13, 2021):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. Please see our contributing guide.

@github-actions[bot] commented on GitHub (Jul 13, 2021): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. Please see our [contributing guide](https://github.com/netbox-community/netbox/blob/develop/CONTRIBUTING.md).
adam commented 2025-12-29 19:21:45 +01:00
Author
Owner
Copy Link

@martinum4 commented on GitHub (Jul 13, 2021):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. Please see our contributing guide.

This feature is still wanted, but not really time sensitive IMHO.

@martinum4 commented on GitHub (Jul 13, 2021): > This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. Please see our [contributing guide](https://github.com/netbox-community/netbox/blob/develop/CONTRIBUTING.md). This feature is still wanted, but not really time sensitive IMHO.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
beta
breaking change
complexity: high
complexity: low
complexity: medium
needs milestone
netbox
pending closure
plugin candidate
pull-request
Mirrored from GitHub Pull Request
 severity: high
severity: low
severity: medium
status: accepted
status: backlog
status: blocked
status: duplicate
status: needs owner
status: needs triage
status: revisions needed
status: under review
topic: GraphQL
topic: Internationalization
topic: OpenAPI
topic: UI/UX
topic: cabling
topic: event rules
topic: htmx navigation
topic: industrialization
topic: migrations
topic: plugins
topic: scripts
topic: templating
topic: testing
type: bug
type: deprecation
type: documentation
type: feature
type: housekeeping
type: translation
No Label pending closure status: needs owner type: feature
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#4893
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?