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

Device port type - Fixed LC (without front/back) #8118

New Issue
Closed
opened 2025-12-29 20:32:38 +01:00 by adam · 2 comments
adam commented 2025-12-29 20:32:38 +01:00
Owner
Copy Link

Originally created by @falz on GitHub (May 25, 2023).

NetBox version

3.5.2

Feature type

New functionality

Proposed functionality

We've added some active optical transport gear to netbox - many of these have optical transponders with 'fixed' (built in) 'line side' LC ports.

There is not currently a way to model this as an 'interface', but you can choose 'LC' if you're adding Front/Rear ports, which isn't quite right here.

A few people have band-aided this by either just choosing a pluggable type (QSFP-DD 200g) or using Front/Back ports, but neither are quite right. Some slack conversation here: https://netdev-community.slack.com/archives/C01P0FRSXRV/p1684853944063759

Older case https://github.com/netbox-community/netbox/issues/1675 touches on this but not exactly.

Use case

Active Optical transport gear has built in LC (and perhaps other - MU, MPO..) connectors but is not a panel with rear ports.

Looking to see how to best handle devices of this type. Adding things like 'QSFP28-100g' is not correct here as it's not pluggable.

Here's a few photos of devices with transponders that have these fixed LC ports:

Line port 1 / port 2 (top left) are fixed LC
chm2t

the ports on the left and right side (1, 12) look like LC pluggables, but are in fact fixed:
waveserver

Database changes

No response

External dependencies

No response

Originally created by @falz on GitHub (May 25, 2023). ### NetBox version 3.5.2 ### Feature type New functionality ### Proposed functionality We've added some active optical transport gear to netbox - many of these have optical transponders with 'fixed' (built in) 'line side' LC ports. There is not currently a way to model this as an 'interface', but you can choose 'LC' if you're adding Front/Rear ports, which isn't quite right here. A few people have band-aided this by either just choosing a pluggable type (QSFP-DD 200g) or using Front/Back ports, but neither are quite right. Some slack conversation here: https://netdev-community.slack.com/archives/C01P0FRSXRV/p1684853944063759 Older case https://github.com/netbox-community/netbox/issues/1675 touches on this but not exactly. ### Use case Active Optical transport gear has built in LC (and perhaps other - MU, MPO..) connectors but is not a panel with rear ports. Looking to see how to best handle devices of this type. Adding things like 'QSFP28-100g' is not correct here as it's not pluggable. Here's a few photos of devices with transponders that have these fixed LC ports: Line port 1 / port 2 (top left) are fixed LC ![chm2t](https://github.com/netbox-community/netbox/assets/707319/efa82cdc-7323-4881-8b6f-b20577f5bc43) the ports on the left and right side (1, 12) look like LC pluggables, but are in fact fixed: ![waveserver](https://github.com/netbox-community/netbox/assets/707319/c8860324-0ce0-431a-b702-5db187d320fe) ### Database changes _No response_ ### External dependencies _No response_
adam added the type: featurepending closure labels 2025-12-29 20:32:38 +01:00
adam closed this issue 2025-12-29 20:32:38 +01:00
adam commented 2025-12-29 20:32:39 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Aug 24, 2023):

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. Do not attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our contributing guide.

@github-actions[bot] commented on GitHub (Aug 24, 2023): 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. **Do not** attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our [contributing guide](https://github.com/netbox-community/netbox/blob/develop/CONTRIBUTING.md).
adam commented 2025-12-29 20:32:39 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Sep 23, 2023):

This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.

@github-actions[bot] commented on GitHub (Sep 23, 2023): This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.
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 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#8118
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?