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 front/rear port types 6P2C and more xPyC combinations #5022

New Issue
Closed
opened 2025-12-29 19:23:15 +01:00 by adam · 0 comments
adam commented 2025-12-29 19:23:15 +01:00
Owner
Copy Link

Originally created by @ypid on GitHub (Jun 21, 2021).

Originally assigned to: @jeremystretch on GitHub.

NetBox version

v2.11.7

Feature type

Data model extension

Proposed functionality

Add all missing common modular connector types:

  • 6P6C
  • 6P4C
  • 6P2C
  • 4P4C
  • 4P2C

#3234 mentioned that adding those port types might be an option. No other telephony specific changes (as discussed in #3234) are part of this issue.

Use case

This occurred while I was creating a device type for APC Back-UPS Pro which has 8P8C (Gigabit Ethernet) and 6P2C (Telephone) surge-protected in/out ports. It would be nice to correctly model the IT device even though telephony is out of scope for NetBox.

Database changes

Only add additional options to PortTypeChoices.

External dependencies

No.

Originally created by @ypid on GitHub (Jun 21, 2021). Originally assigned to: @jeremystretch on GitHub. ### NetBox version v2.11.7 ### Feature type Data model extension ### Proposed functionality Add all missing common modular connector types: * 6P6C * 6P4C * 6P2C * 4P4C * 4P2C #3234 mentioned that adding those port types might be an option. No other telephony specific changes (as discussed in #3234) are part of this issue. ### Use case This occurred while I was creating a device type for APC Back-UPS Pro which has 8P8C (Gigabit Ethernet) and 6P2C (Telephone) surge-protected in/out ports. It would be nice to correctly model the IT device even though telephony is out of scope for NetBox. ### Database changes Only add additional options to PortTypeChoices. ### External dependencies No.
adam added the status: acceptedtype: feature labels 2025-12-29 19:23:15 +01:00
adam closed this issue 2025-12-29 19:23:15 +01:00
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 status: accepted 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#5022
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?