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

Add cSFP Interface Type #10973

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

Originally created by @aroth01 on GitHub (Apr 1, 2025).

NetBox version

v4.2.5

Feature type

Data model extension

Proposed functionality

For interface types, add the cSFP type as an option.

Use case

While a bit rare, we have a few devices that use compact SFP (cSFP) and need to be able to document them properly in netbox. compact SFP has two bidi 1G optics that use the same physical SFP cage.

Database changes

No response

External dependencies

No response

Originally created by @aroth01 on GitHub (Apr 1, 2025). ### NetBox version v4.2.5 ### Feature type Data model extension ### Proposed functionality For interface types, add the cSFP type as an option. ### Use case While a bit rare, we have a few devices that use compact SFP (cSFP) and need to be able to document them properly in netbox. compact SFP has two bidi 1G optics that use the same physical SFP cage. ### Database changes _No response_ ### External dependencies _No response_
adam added the type: feature label 2025-12-29 21:38:38 +01:00
adam closed this issue 2025-12-29 21:38:39 +01:00
adam commented 2025-12-29 21:38:39 +01:00
Author
Owner
Copy Link

@elixdreamer commented on GitHub (Apr 3, 2025):

When using devices that support cSFP (compact Small Form-factor Pluggable), the port count remains unchanged. A single physical SFP slot can accommodate two ports. When a cSFP is installed, both ports can be used independently to connect to two different devices. However, if a standard SFP is installed in the same slot, the second port becomes unusable.

However having the option to define the port as cSFP doesn't mean that such an SFP is installed.

@elixdreamer commented on GitHub (Apr 3, 2025): When using devices that support cSFP (compact Small Form-factor Pluggable), the port count remains unchanged. A single physical SFP slot can accommodate two ports. When a cSFP is installed, both ports can be used independently to connect to two different devices. However, if a standard SFP is installed in the same slot, the second port becomes unusable. However having the option to define the port as cSFP doesn't mean that such an SFP is installed.
adam commented 2025-12-29 21:38:39 +01:00
Author
Owner
Copy Link

@bctiemann commented on GitHub (Apr 3, 2025):

Based on https://edgeoptic.com/compact-sfp-csfp-what-it-is-and-when-it-is-used/ -- it appears that cSFP is not an interface type, but rather a type of transceiver or optic. It wouldn't fit our modeling to add cSFP as a separate interface type. It's another type of SFP like 10G or 40G which we don't currently have a way of modeling, though you could do it via Inventory Items.

@bctiemann commented on GitHub (Apr 3, 2025): Based on https://edgeoptic.com/compact-sfp-csfp-what-it-is-and-when-it-is-used/ -- it appears that cSFP is not an interface type, but rather a type of transceiver or optic. It wouldn't fit our modeling to add cSFP as a separate interface type. It's another type of SFP like 10G or 40G which we don't currently have a way of modeling, though you could do it via Inventory Items.
adam commented 2025-12-29 21:38:40 +01:00
Author
Owner
Copy Link

@aroth01 commented on GitHub (Apr 3, 2025):

While you can use a normal SFP in a cSFP cage. You can't use a cSFP optic in a normal SFP cage and expect both ports to work. The device has to be built to use cSFP.

SFP+ and SFP exist as interface type options. So why couldn't cSFP just exist as cSFP (1GE)?

@aroth01 commented on GitHub (Apr 3, 2025): While you can use a normal SFP in a cSFP cage. You can't use a cSFP optic in a normal SFP cage and expect both ports to work. The device has to be built to use cSFP. SFP+ and SFP exist as interface type options. So why couldn't cSFP just exist as cSFP (1GE)?
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 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#10973
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?