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

Missing Fibrechannel interface types #6658

New Issue
Closed
opened 2025-12-29 19:43:36 +01:00 by adam · 2 comments
adam commented 2025-12-29 19:43:36 +01:00
Owner
Copy Link

Originally created by @martindalum on GitHub (Jul 14, 2022).

NetBox version

v3.2.2

Feature type

Data model extension

Proposed functionality

The current list of fibrechannel interface types are, from contansts.py:

  1. [IFACE_TYPE_1GFC_SFP, 'SFP (1GFC)'],
  2. [IFACE_TYPE_2GFC_SFP, 'SFP (2GFC)'],
  3. [IFACE_TYPE_4GFC_SFP, 'SFP (4GFC)'],
  4. [IFACE_TYPE_8GFC_SFP_PLUS, 'SFP+ (8GFC)'],
  5. [IFACE_TYPE_16GFC_SFP_PLUS, 'SFP+ (16GFC)'],
  6. [IFACE_TYPE_32GFC_SFP28, 'SFP28 (32GFC)'],
  7. [IFACE_TYPE_128GFC_QSFP28, 'QSFP28 (128GFC)'],

This indicates that eg. a 32GB link must be using the SFP28 form-factor, which is not true.

Brocade have a list of their transciever types here: https://www.broadcom.com/products/fibre-channel-networking/transceiver-modules

This includes eg. 32Gbit SFP+, 64Gbit SFP+ and 64Gbit SFP-DD which are not on the list in Netbox.

Ideally interface types could be moved to the database and added or changed via the webinterface or API, but since that's a quite big change, it would be nice to have the list in contansts.py maintained.

The current list assumes only one transciever type per speed, so an alternative could be to remove transceiver types from the list and add the missing 64GFC speed.

Use case

This would enable correct documentation of needed transceivers in netbox.

Database changes

No response

External dependencies

No response

Originally created by @martindalum on GitHub (Jul 14, 2022). ### NetBox version v3.2.2 ### Feature type Data model extension ### Proposed functionality The current list of fibrechannel interface types are, from contansts.py: 1. [IFACE_TYPE_1GFC_SFP, 'SFP (1GFC)'], 2. [IFACE_TYPE_2GFC_SFP, 'SFP (2GFC)'], 3. [IFACE_TYPE_4GFC_SFP, 'SFP (4GFC)'], 4. [IFACE_TYPE_8GFC_SFP_PLUS, 'SFP+ (8GFC)'], 5. [IFACE_TYPE_16GFC_SFP_PLUS, 'SFP+ (16GFC)'], 6. [IFACE_TYPE_32GFC_SFP28, 'SFP28 (32GFC)'], 7. [IFACE_TYPE_128GFC_QSFP28, 'QSFP28 (128GFC)'], This indicates that eg. a 32GB link must be using the SFP28 form-factor, which is not true. Brocade have a list of their transciever types here: https://www.broadcom.com/products/fibre-channel-networking/transceiver-modules This includes eg. 32Gbit SFP+, 64Gbit SFP+ and 64Gbit SFP-DD which are not on the list in Netbox. Ideally interface types could be moved to the database and added or changed via the webinterface or API, but since that's a quite big change, it would be nice to have the list in contansts.py maintained. The current list assumes only one transciever type per speed, so an alternative could be to remove transceiver types from the list and add the missing 64GFC speed. ### Use case This would enable correct documentation of needed transceivers in netbox. ### Database changes _No response_ ### External dependencies _No response_
adam added the type: featurestatus: revisions needed labels 2025-12-29 19:43:36 +01:00
adam closed this issue 2025-12-29 19:43:36 +01:00
adam commented 2025-12-29 19:43:37 +01:00
Author
Owner
Copy Link

@DanSheps commented on GitHub (Jul 14, 2022):

Please fill out the proposal section with the specific interfaces you are proposing to be added.

@DanSheps commented on GitHub (Jul 14, 2022): Please fill out the proposal section with the specific interfaces you are proposing to be added.
adam commented 2025-12-29 19:43:37 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Aug 10, 2022):

Closing as there has been no follow-up from the OP.

@jeremystretch commented on GitHub (Aug 10, 2022): Closing as there has been no follow-up from the OP.
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: revisions needed 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#6658
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?