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

Model transmit power for interfaces #5549

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

Originally created by @jeremystretch on GitHub (Oct 21, 2021).

Originally assigned to: @jeremystretch on GitHub.

NetBox version

v3.0.8

Feature type

New functionality

Proposed functionality

Add a tx_power field to the Interface model for tracking transmit signal strength. This will be an integer value measured in dBm.

Use case

This was originally going to be part of the wireless networking feature (#3979), but I realized that such an attribute could be useful for optical interfaces as well. I'm opening this issue for review by the community to see if the proposed implementation would be suitable for general use.

Database changes

Add a new integer field to the dcim.Interface model. This would not apply to VM interfaces.

External dependencies

No response

Originally created by @jeremystretch on GitHub (Oct 21, 2021). Originally assigned to: @jeremystretch on GitHub. ### NetBox version v3.0.8 ### Feature type New functionality ### Proposed functionality Add a `tx_power` field to the Interface model for tracking transmit signal strength. This will be an integer value measured in [dBm](https://en.wikipedia.org/wiki/DBm). ### Use case This was originally going to be part of the wireless networking feature (#3979), but I realized that such an attribute could be useful for optical interfaces as well. I'm opening this issue for review by the community to see if the proposed implementation would be suitable for general use. ### Database changes Add a new integer field to the dcim.Interface model. This would _not_ apply to VM interfaces. ### External dependencies _No response_
adam added the status: acceptedtype: feature labels 2025-12-29 19:29:19 +01:00
adam closed this issue 2025-12-29 19:29:19 +01:00
adam commented 2025-12-29 19:29:20 +01:00
Author
Owner
Copy Link

@tb-killa commented on GitHub (Oct 21, 2021):

Nice idea for wifi it's great.
For gbic it would be great if we have Rx and Tx power.

@tb-killa commented on GitHub (Oct 21, 2021): Nice idea for wifi it's great. For gbic it would be great if we have Rx and Tx power.
adam commented 2025-12-29 19:29:20 +01:00
Author
Owner
Copy Link

@xkilian commented on GitHub (Oct 21, 2021):

For optical, I don't see great value, as the power is defined by the optics type. ZX, BX20, ER,etc. Actual power observed is in the monitoring domain and not Netbox. Maybe there is other use case...

@xkilian commented on GitHub (Oct 21, 2021): For optical, I don't see great value, as the power is defined by the optics type. ZX, BX20, ER,etc. Actual power observed is in the monitoring domain and not Netbox. Maybe there is other use case...
adam commented 2025-12-29 19:29:20 +01:00
Author
Owner
Copy Link

@julianze commented on GitHub (Oct 21, 2021):

The tx_power of optical transceiver could be useful for tracking the normal/desired TX Power. On the monitoring part we can compare the real power with the power it should be.

Of course the tx power has to bei baselined after the link has established.

Beide the tx_power there would be useful to have additional values like tx and rx dBm. Both values have to be baselined and then put in NetBox as single source of truth.
Monitoring can poll the live values and trigger alerts of the delta is to big. In additional in manual debugging this could as a desired reference.

This applies to optical and wireless interfaces.

@julianze commented on GitHub (Oct 21, 2021): The tx_power of optical transceiver could be useful for tracking the normal/desired TX Power. On the monitoring part we can compare the real power with the power it should be. Of course the tx power has to bei baselined after the link has established. Beide the tx_power there would be useful to have additional values like tx and rx dBm. Both values have to be baselined and then put in NetBox as single source of truth. Monitoring can poll the live values and trigger alerts of the delta is to big. In additional in manual debugging this could as a desired reference. This applies to optical and wireless interfaces.
adam commented 2025-12-29 19:29:20 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Oct 21, 2021):

@julianze the purpose of this field is solely to indicate configured transmit power. Anything beyond that should utilize a custom field.

@jeremystretch commented on GitHub (Oct 21, 2021): @julianze the purpose of this field is solely to indicate configured transmit power. Anything beyond that should utilize a custom field.
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#5549
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?