Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Console Ports should have Port Speed #5375

Closed
docsteel opened this issue Nov 24, 2020 · 4 comments
Closed

Console Ports should have Port Speed #5375

docsteel opened this issue Nov 24, 2020 · 4 comments
Assignees
Labels
status: accepted This issue has been accepted for implementation type: feature Introduction of new functionality to the application
Milestone

Comments

@docsteel
Copy link

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.

@jeremystretch
Copy link
Member

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 jeremystretch added the status: revisions needed This issue requires additional information to be actionable label Nov 24, 2020
@docsteel
Copy link
Author

docsteel commented 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 docsteel reopened this Nov 24, 2020
@jeremystretch
Copy link
Member

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?

@docsteel
Copy link
Author

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.

@jeremystretch jeremystretch added status: under review Further discussion is needed to determine this issue's scope and/or implementation type: feature Introduction of new functionality to the application and removed status: revisions needed This issue requires additional information to be actionable labels Nov 24, 2020
@jeremystretch jeremystretch added needs milestone Awaiting prioritization for inclusion with a future NetBox release status: accepted This issue has been accepted for implementation and removed status: under review Further discussion is needed to determine this issue's scope and/or implementation needs milestone Awaiting prioritization for inclusion with a future NetBox release labels Dec 16, 2020
@jeremystretch jeremystretch added this to the v2.11 milestone Dec 21, 2020
@jeremystretch jeremystretch self-assigned this Mar 3, 2021
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jun 2, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
status: accepted This issue has been accepted for implementation type: feature Introduction of new functionality to the application
Projects
None yet
Development

No branches or pull requests

2 participants