Documentation of SFPs/QSFPs / add a field "installed SFP" in Interface #7151

Closed
opened 2025-12-29 20:19:46 +01:00 by adam · 2 comments
Owner

Originally created by @jehrhardt-bego on GitHub (Oct 23, 2022).

NetBox version

v3.3.5

Feature type

Change to existing functionality

Proposed functionality

Documentation of the used SFPs/QSFPs in a port, which is important to get all the needed details for a physical connection.

Attached is a list of all kinds of possible SFPs/QSFPs.

sfp-kinds.txt

Use case

The field "Type" in Interface describes the maximal speed of the port, but not which SFP/speed is really used.
e.g. You can add an 1G-SX SFP into a 10G port. Another example, you use 100GBASE-SR4 and needs a MPO cable or 100GBASE-CWDM4 with a OM4/LC cable.

Without the documentation of the used SFP, you don't know which cable to use or which speed is possible or what kind of SFP you need to replace when faulty.

Database changes

another field is needed

External dependencies

none

Originally created by @jehrhardt-bego on GitHub (Oct 23, 2022). ### NetBox version v3.3.5 ### Feature type Change to existing functionality ### Proposed functionality Documentation of the used SFPs/QSFPs in a port, which is important to get all the needed details for a physical connection. Attached is a list of all kinds of possible SFPs/QSFPs. [sfp-kinds.txt](https://github.com/netbox-community/netbox/files/9845840/sfp-kinds.txt) ### Use case The field "Type" in Interface describes the maximal speed of the port, but not which SFP/speed is really used. e.g. You can add an 1G-SX SFP into a 10G port. Another example, you use 100GBASE-SR4 and needs a MPO cable or 100GBASE-CWDM4 with a OM4/LC cable. Without the documentation of the used SFP, you don't know which cable to use or which speed is possible or what kind of SFP you need to replace when faulty. ### Database changes another field is needed ### External dependencies none
adam added the type: feature label 2025-12-29 20:19:46 +01:00
adam closed this issue 2025-12-29 20:19:46 +01:00
Author
Owner

@PieterL75 commented on GitHub (Oct 24, 2022):

you can be done using Inventory Items :
https://docs.netbox.dev/en/stable/models/dcim/inventoryitem/

An inventory item may also be associated with a specific component within the same device. For example, you may wish to associate a transceiver with an interface.
@PieterL75 commented on GitHub (Oct 24, 2022): you can be done using Inventory Items : https://docs.netbox.dev/en/stable/models/dcim/inventoryitem/ ``` An inventory item may also be associated with a specific component within the same device. For example, you may wish to associate a transceiver with an interface. ```
Author
Owner

@jeremystretch commented on GitHub (Oct 24, 2022):

As @PieterL75 points out, pluggable optics should be modeled as inventory items and associated with the interfaces into which they are installed.

@jeremystretch commented on GitHub (Oct 24, 2022): As @PieterL75 points out, pluggable optics should be modeled as inventory items and associated with the interfaces into which they are installed.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#7151