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

Please add "CS" and "SN" as a connector type options. #4343

New Issue
Closed
opened 2025-12-29 18:34:59 +01:00 by adam · 2 comments
adam commented 2025-12-29 18:34:59 +01:00
Owner
Copy Link

Originally created by @heyhogan on GitHub (Dec 10, 2020).

Originally assigned to: @jeremystretch on GitHub.

Environment

  • Python version: 2.7.5
  • NetBox version: V2.9.10

Proposed Functionality

Please add "CS" and "SN" as a connector Type choices for devices and interfaces. This is a new connector this is a smaller form factor than LC and thus more CS connectors will fit in the same space. This connector is coming out primarily for higher speed applications like 400G. You can see this connector alongside a traditional LC at https://www.senko.com/cs-connector/
and https://www.senko.com/sn-connector/

Use Case

Instead of an LC cassette or patch panel in the rack, there will be a CS (orSN) cassette or patch panel. This will allow you to model a new device with a CS interface connector and patch it so the patch panel. My existing cassette (LC) has 6 ports. The new cassette will have 8 (CS) front ports. (Both have MPO rear ports).

Database Changes

None - other than adding CS and SN as options if this info is stored in a database.

External Dependencies

None that I am aware of.

Originally created by @heyhogan on GitHub (Dec 10, 2020). Originally assigned to: @jeremystretch on GitHub. <!-- NOTE: IF YOUR ISSUE DOES NOT FOLLOW THIS TEMPLATE, IT WILL BE CLOSED. This form is only for proposing specific new features or enhancements. If you have a general idea or question, please post to our mailing list instead of opening an issue: https://groups.google.com/g/netbox-discuss NOTE: Due to an excessive backlog of feature requests, we are not currently accepting any proposals which significantly extend NetBox's feature scope. Please describe the environment in which you are running NetBox. Be sure that you are running an unmodified instance of the latest stable release before submitting a bug report. --> ### Environment * Python version: 2.7.5 * NetBox version: V2.9.10 <!-- Describe in detail the new functionality you are proposing. Include any specific changes to work flows, data models, or the user interface. --> ### Proposed Functionality Please add "CS" and "SN" as a connector Type choices for devices and interfaces. This is a new connector this is a smaller form factor than LC and thus more CS connectors will fit in the same space. This connector is coming out primarily for higher speed applications like 400G. You can see this connector alongside a traditional LC at https://www.senko.com/cs-connector/ and https://www.senko.com/sn-connector/ <!-- Convey an example use case for your proposed feature. Write from the perspective of a NetBox user who would benefit from the proposed functionality and describe how. ---> ### Use Case Instead of an LC cassette or patch panel in the rack, there will be a CS (orSN) cassette or patch panel. This will allow you to model a new device with a CS interface connector and patch it so the patch panel. My existing cassette (LC) has 6 ports. The new cassette will have 8 (CS) front ports. (Both have MPO rear ports). <!-- Note any changes to the database schema necessary to support the new feature. For example, does the proposal require adding a new model or field? (Not all new features require database changes.) ---> ### Database Changes None - other than adding CS and SN as options if this info is stored in a database. <!-- List any new dependencies on external libraries or services that this new feature would introduce. For example, does the proposal require the installation of a new Python package? (Not all new features introduce new dependencies.) --> ### External Dependencies None that I am aware of.
adam added the status: acceptedtype: feature labels 2025-12-29 18:34:59 +01:00
adam closed this issue 2025-12-29 18:34:59 +01:00
adam commented 2025-12-29 18:35:00 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Dec 10, 2020):

Given these appear to be proprietary form factors, should they be prefixed with "Senko"?

@jeremystretch commented on GitHub (Dec 10, 2020): Given these appear to be proprietary form factors, should they be prefixed with "Senko"?
adam commented 2025-12-29 18:35:00 +01:00
Author
Owner
Copy Link

@heyhogan commented on GitHub (Dec 11, 2020):

No, I don't think so. I work for Panduit and we are launching a full line of CS products. Senko developed the connector I think and many vendors will license it or be purchasing it from Senko as a raw material for a finished good. I would prefer to treat it like an LC connector and keep its name simple. The Panduit SC guide can be found here: [(https://www.panduit.com/content/dam/panduit/en/products/media/2/52/252/3252/110093252.pdf)]

@heyhogan commented on GitHub (Dec 11, 2020): No, I don't think so. I work for Panduit and we are launching a full line of CS products. Senko developed the connector I think and many vendors will license it or be purchasing it from Senko as a raw material for a finished good. I would prefer to treat it like an LC connector and keep its name simple. The Panduit SC guide can be found here: [(https://www.panduit.com/content/dam/panduit/en/products/media/2/52/252/3252/110093252.pdf)]
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#4343
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?