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

Please add 200Gig Form Factors #2090

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

Originally created by @cmacnevin on GitHub (Nov 6, 2018).

eg: CFPX-200G-DWDM (https://www.finisar.com/optical-transceivers/ftlc3322x3nl)

CFP2 form factor, they're also very close to releasing 400g and 800g, and it's entirely possible these exists in labs right now..

The 200G is on the market and in use, in my network, so it'd be nice to have this now. Maybe just create the 200,400,800 options, with the option to be DWDM/Tunable.

Originally created by @cmacnevin on GitHub (Nov 6, 2018). eg: CFPX-200G-DWDM (https://www.finisar.com/optical-transceivers/ftlc3322x3nl) CFP2 form factor, they're also very close to releasing 400g and 800g, and it's entirely possible these exists in labs right now.. The 200G is on the market and in use, in my network, so it'd be nice to have this now. Maybe just create the 200,400,800 options, with the option to be DWDM/Tunable.
adam closed this issue 2025-12-29 17:22:10 +01:00
adam commented 2025-12-29 17:22:11 +01:00
Author
Owner
Copy Link

@cmacnevin commented on GitHub (Nov 6, 2018):

While I'm at it, I understand that ther'es a reticence to overpopulate the list. Maybe a reformatting of the options is in order, to let networks which aren't 21st century cloud DCs play too. If it was a couple of fields with a branching option structure, it cold be more inclusive. And turning on exotic interface types as options could be enabled in settings, and potentially locked to specific device type. eg an Infiniband switch could be tagged as such, and those interface types become available.

That is, if the dev team is still insisting on keeping full control of this list.

@cmacnevin commented on GitHub (Nov 6, 2018): While I'm at it, I understand that ther'es a reticence to overpopulate the list. Maybe a reformatting of the options is in order, to let networks which aren't 21st century cloud DCs play too. If it was a couple of fields with a branching option structure, it cold be more inclusive. And turning on exotic interface types as options could be enabled in settings, and potentially locked to specific device type. eg an Infiniband switch could be tagged as such, and those interface types become available. That is, if the dev team is still insisting on keeping full control of this list.
adam commented 2025-12-29 17:22:11 +01:00
Author
Owner
Copy Link

@cimnine commented on GitHub (Nov 7, 2018):

You need to use the official issue template or your feature request will be closed as invalid right away.

@cimnine commented on GitHub (Nov 7, 2018): You need to use the official issue template or your feature request will be closed as invalid right away.
adam commented 2025-12-29 17:22:13 +01:00
Author
Owner
Copy Link

@cmacnevin commented on GitHub (Nov 7, 2018):

I opened another ticket. There's not a lot more information in it, but I guess it's in the template now, so that's got to be worth something I suppose?

@cmacnevin commented on GitHub (Nov 7, 2018): I opened another ticket. There's not a lot more information in it, but I guess it's in the template now, so that's got to be worth something I suppose?
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
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#2090
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?