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

Console speed for device types #4834

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

Originally created by @Omripresent on GitHub (Apr 27, 2021).

NetBox version

2.11.1

Feature type

Change to existing functionality

Proposed functionality

Add the speed field when creating or editing a console port and console server port under a device template.

Use case

All devices come with default console port speeds that vary between vendors and models, it would make sense to add the speed field so any created device from a given type would have the default speed already set,

Database changes

No response

External dependencies

No response

Originally created by @Omripresent on GitHub (Apr 27, 2021). ### NetBox version 2.11.1 ### Feature type Change to existing functionality ### Proposed functionality Add the `speed` field when creating or editing a `console port` and `console server port` under a device template. ### Use case All devices come with default console port speeds that vary between vendors and models, it would make sense to add the speed field so any created device from a given type would have the default speed already set, ### Database changes _No response_ ### External dependencies _No response_
adam added the type: feature label 2025-12-29 19:21:04 +01:00
adam closed this issue 2025-12-29 19:21:04 +01:00
adam commented 2025-12-29 19:21:05 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Apr 27, 2021):

IIRC this was discussed under #5375 and we opted not to add the field to device types because it's purely a configuration item. It can have a default value, yes, but that's defined by the software rather than the hardware type.

@jeremystretch commented on GitHub (Apr 27, 2021): IIRC this was discussed under #5375 and we opted not to add the field to device types because it's purely a configuration item. It can have a default value, yes, but that's defined by the software rather than the hardware type.
adam commented 2025-12-29 19:21:05 +01:00
Author
Owner
Copy Link

@Omripresent commented on GitHub (Apr 27, 2021):

That makes sense, personally I haven't encountered any case where the same HW across different software versions comes with different default speeds.

Yes most devices can have the console speed changed later on but there should be some way to know what default speed a given device type or platform (or the combination of the two?) is without the need of keeping this info in an external database and manually update on the creation of a new device.

This can be done with a webhook to an external backend on new device creation but it seems like an over complication of something simple.

@Omripresent commented on GitHub (Apr 27, 2021): That makes sense, personally I haven't encountered any case where the same HW across different software versions comes with different default speeds. Yes most devices can have the console speed changed later on but there should be some way to know what default speed a given device type or platform (or the combination of the two?) is without the need of keeping this info in an external database and manually update on the creation of a new device. This can be done with a webhook to an external backend on new device creation but it seems like an over complication of something simple.
adam commented 2025-12-29 19:21:06 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Apr 27, 2021):

It's a valid use case for sure, but device types aren't the right solution. There are plenty of places you might want to convey a default value that's not tied to the hardware: interface encapsulations, interface descriptions (#6261), assigned VLANs, tags, etc. We don't want to set a precedent of using the device type for this purpose as that approach would fall over pretty quickly.

I'd be happy to entertain a detailed proposal in support of default values for certain attributes, but it would need to be raised as a separate feature request.

This can be done with a webhook to an external backend on new device creation but it seems like an over complication of something simple.

A custom script might suit your needs.

@jeremystretch commented on GitHub (Apr 27, 2021): It's a valid use case for sure, but device types aren't the right solution. There are plenty of places you might want to convey a default value that's not tied to the hardware: interface encapsulations, interface descriptions (#6261), assigned VLANs, tags, etc. We don't want to set a precedent of using the device type for this purpose as that approach would fall over pretty quickly. I'd be happy to entertain a detailed proposal in support of default values for certain attributes, but it would need to be raised as a separate feature request. > This can be done with a webhook to an external backend on new device creation but it seems like an over complication of something simple. A [custom script](https://netbox.readthedocs.io/en/stable/additional-features/custom-scripts/) might suit your needs.
adam commented 2025-12-29 19:21:06 +01:00
Author
Owner
Copy Link

@Omripresent commented on GitHub (Apr 27, 2021):

Understood, thank you for the input.

I'll look into those other options and raise a new request if non pan out.

@Omripresent commented on GitHub (Apr 27, 2021): Understood, thank you for the input. I'll look into those other options and raise a new request if non pan out.
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 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#4834
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?