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

Add PoE attributes to interface templates #6696

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

Originally created by @PaulR282 on GitHub (Jul 20, 2022).

Originally assigned to: @jeremystretch on GitHub.

NetBox version

v3.3.0-beta1

Feature type

Data model extension

Proposed functionality

In addition to my feature request #8272 it would be nice to be able to configure more in the device type that you can configure when editing an interface that already exists.
I would suggest the following fields:

  • Interface: Speed
  • Interface: Duplex
  • all of Operation section
  • all of Related Interfaces section (like Bridged interface from the existing feature request)
  • all of new PoE section

Use case

The mentioned fields are attributes that you can often predefine. Currently (in beta), if you have a PoE switch, you would need to configure PoE mode and type every time you create a new switch from the device type. The same goes for the other fields like Speed, Duplex, etc.

Database changes

No response

External dependencies

No response

Originally created by @PaulR282 on GitHub (Jul 20, 2022). Originally assigned to: @jeremystretch on GitHub. ### NetBox version v3.3.0-beta1 ### Feature type Data model extension ### Proposed functionality In addition to my feature request #8272 it would be nice to be able to configure more in the device type that you can configure when editing an interface that already exists. I would suggest the following fields: - Interface: Speed - Interface: Duplex - all of Operation section - all of Related Interfaces section (like Bridged interface from the existing feature request) - all of new PoE section ### Use case The mentioned fields are attributes that you can often predefine. Currently (in beta), if you have a PoE switch, you would need to configure PoE mode and type every time you create a new switch from the device type. The same goes for the other fields like Speed, Duplex, etc. ### Database changes _No response_ ### External dependencies _No response_
adam added the status: acceptedtype: featurebeta labels 2025-12-29 19:44:05 +01:00
adam closed this issue 2025-12-29 19:44:05 +01:00
adam commented 2025-12-29 19:44:05 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jul 20, 2022):

A device type represents the make and model of a physical device, and thus intentionally does not incorporate any configurable characteristics such as interface speed and duplex: These attributes are assigned after instantiation and vary from one interface to another. The only item in your list above that would make sense to add is the PoE designations, which I agree should have been incorporated under #1099.

@jeremystretch commented on GitHub (Jul 20, 2022): A device type represents the make and model of a _physical_ device, and thus intentionally does not incorporate any configurable characteristics such as interface speed and duplex: These attributes are assigned after instantiation and vary from one interface to another. The only item in your list above that would make sense to add is the PoE designations, which I agree should have been incorporated under #1099.
adam commented 2025-12-29 19:44:06 +01:00
Author
Owner
Copy Link

@PaulR282 commented on GitHub (Jul 20, 2022):

Alright. Testing the new PoE functionality in the beta was the origin of this idea. It makes sense to only model the physical device this way. So I would suggest just adding PoE and #8272.

@PaulR282 commented on GitHub (Jul 20, 2022): Alright. Testing the new PoE functionality in the beta was the origin of this idea. It makes sense to only model the physical device this way. So I would suggest just adding PoE and #8272.
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 beta 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#6696
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?