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 Ports should have Port Speed #4302

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

Originally created by @docsteel on GitHub (Nov 24, 2020).

Originally assigned to: @jeremystretch on GitHub.

Environment

  • Python version: 3.8.5
  • NetBox version: 2.9.9

Proposed Functionality

Console Ports should include Port Speed in Baud:

9600
14400
38600
115200

Use Case

Templating and configure automated Console Server Solutions via API.

Database Changes

Yes

External Dependencies

Not aware of any external Dependencies.

Originally created by @docsteel on GitHub (Nov 24, 2020). Originally assigned to: @jeremystretch on GitHub. <!-- NOTE: IF YOUR ISSUE DOES NOT FOLLOW THIS TEMPLATE, IT WILL BE CLOSED. This form is only for proposing specific new features or enhancements. If you have a general idea or question, please post to our mailing list instead of opening an issue: https://groups.google.com/g/netbox-discuss NOTE: Due to an excessive backlog of feature requests, we are not currently accepting any proposals which significantly extend NetBox's feature scope. Please describe the environment in which you are running NetBox. Be sure that you are running an unmodified instance of the latest stable release before submitting a bug report. --> ### Environment * Python version: 3.8.5 * NetBox version: 2.9.9 <!-- Describe in detail the new functionality you are proposing. Include any specific changes to work flows, data models, or the user interface. --> ### Proposed Functionality Console Ports should include Port Speed in Baud: 9600 14400 38600 115200 <!-- Convey an example use case for your proposed feature. Write from the perspective of a NetBox user who would benefit from the proposed functionality and describe how. ---> ### Use Case Templating and configure automated Console Server Solutions via API. <!-- Note any changes to the database schema necessary to support the new feature. For example, does the proposal require adding a new model or field? (Not all new features require database changes.) ---> ### Database Changes Yes <!-- List any new dependencies on external libraries or services that this new feature would introduce. For example, does the proposal require the installation of a new Python package? (Not all new features introduce new dependencies.) --> ### External Dependencies Not aware of any external Dependencies.
adam added the status: acceptedtype: feature labels 2025-12-29 18:34:31 +01:00
adam closed this issue 2025-12-29 18:34:31 +01:00
adam commented 2025-12-29 18:34:31 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Nov 24, 2020):

This needs more detail. For example, are you proposing a fixed list of speeds? Or should it be a customizable value? Only console ports, or console server ports as well? Is it to be measured in baud or bits per second? The more detail you provide, the more likely a feature request is to be considered for adoption.

@jeremystretch commented on GitHub (Nov 24, 2020): This needs more detail. For example, are you proposing a fixed list of speeds? Or should it be a customizable value? Only console ports, or console server ports as well? Is it to be measured in baud or bits per second? The more detail you provide, the more likely a feature request is to be considered for adoption.
adam commented 2025-12-29 18:34:31 +01:00
Author
Owner
Copy Link

@docsteel commented on GitHub (Nov 24, 2020):

Port Speed should be a Drop-Down Selection Field as fixed List with the following Values, measured in Baud:
1200
2400
4800
9600
19200
38400
57600
115200

Default Value should be 9600. This list should cover all default Speed Settings for Switches, Routers, Serial Devices, etc.

If it's feasible this should be added for Console Ports and Console Server Ports as well, because both Ports have a Port Speed Setting in the Real World. With this Setting we could automate the Setup of Serial Console Servers in the Datacenter (e.g. Device 1, Port 1 needs Speed 9600 for serial Console of APC USV; Device 1, Port 2 needs Port Speed of 115200 Baud for Console of a Cisco Switch)

@docsteel commented on GitHub (Nov 24, 2020): Port Speed should be a Drop-Down Selection Field as fixed List with the following Values, measured in Baud: 1200 2400 4800 9600 19200 38400 57600 115200 Default Value should be 9600. This list should cover all default Speed Settings for Switches, Routers, Serial Devices, etc. If it's feasible this should be added for Console Ports and Console Server Ports as well, because both Ports have a Port Speed Setting in the Real World. With this Setting we could automate the Setup of Serial Console Servers in the Datacenter (e.g. Device 1, Port 1 needs Speed 9600 for serial Console of APC USV; Device 1, Port 2 needs Port Speed of 115200 Baud for Console of a Cisco Switch)
adam commented 2025-12-29 18:34:31 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Nov 24, 2020):

Those are bps values, not baud rate.

With this Setting we could automate the Setup of Serial Console Servers in the Datacenter

What about other parameters, such as parity, flow control, or port pinout?

@jeremystretch commented on GitHub (Nov 24, 2020): Those are bps values, [not baud rate](https://www.linuxjournal.com/files/linuxjournal.com/linuxjournal/articles/010/1097/1097s2.html). > With this Setting we could automate the Setup of Serial Console Servers in the Datacenter What about other parameters, such as parity, flow control, or port pinout?
adam commented 2025-12-29 18:34:31 +01:00
Author
Owner
Copy Link

@docsteel commented on GitHub (Nov 24, 2020):

Those are bps values, not baud rate.

Oh sorry, my fault. Yes you're right this should have been bps and not Baud.

With this Setting we could automate the Setup of Serial Console Servers in the Datacenter

What about other parameters, such as parity, flow control, or port pinout?

For our Templates we don't need Parity, flow control or port pinout, only Port Speed.
But for other Users these could be a Feature.
In this Case I would add:

Port Pinout has too many values to image this in compact form in the Console Port Form, so i would not add this here.

@docsteel commented on GitHub (Nov 24, 2020): > Those are bps values, [not baud rate](https://www.linuxjournal.com/files/linuxjournal.com/linuxjournal/articles/010/1097/1097s2.html). Oh sorry, my fault. Yes you're right this should have been bps and not Baud. > > > With this Setting we could automate the Setup of Serial Console Servers in the Datacenter > > What about other parameters, such as parity, flow control, or port pinout? For our Templates we don't need Parity, flow control or port pinout, only Port Speed. But for other Users these could be a Feature. In this Case I would add: - Parity (N,O,E,M,S Value) see: https://en.wikipedia.org/wiki/Serial_port#Parity - Flow Control (Hardware, Software Value) as described here: https://en.wikipedia.org/wiki/Serial_port#Flow_control Fields for Data Bits and Stop Bits are not needed here, because today's Electronic uses 8 Data Bits and 1 Stop Bit for Communication. Port Pinout has too many values to image this in compact form in the Console Port Form, so i would not add this here.
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#4302
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?