starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-12 05:20:31 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

Allow IP address assignment to console server ports #3736

New Issue
Closed
opened 2025-12-29 18:30:51 +01:00 by adam · 3 comments
adam commented 2025-12-29 18:30:51 +01:00
Owner
Copy Link

Originally created by @chris-mccoy on GitHub (May 29, 2020).

Great software, thank you for working on it and opening to the community! 💯

Environment

  • Python version: 3.6.9
  • NetBox version: 2.8.4

Proposed Functionality

Permit the user to assign an IP address to console server ports.

Use Case

(This is Cisco-specific configurations, but other vendors easily apply)

As a network administrator, I wish to avoid logging into a console server first before choosing a line, so I use features such as ip alias, rotary and ip ssh port 2001 rotary ... to assign console ports directly to IP addresses. This permits greater visibility into who owns the session using SSH which provides a username. As is today, I could create a Virtual Interface for the corresponding TTY line, but it makes it difficult to trace IPs to console server ports using the UI. It also makes scripting the NetBox data model into a configuration for the console server easier.

It would be nice to be able to assign an IP address to a console server port to make it easier to note which IPs are assigned to which equipment so cable-tracing is more evident. It would be nice for this IP to be reflected in the connected device, but this isn't as necessary.

Database Changes

As necessary to support feature.

External Dependencies

None.

Originally created by @chris-mccoy on GitHub (May 29, 2020). Great software, thank you for working on it and opening to the community! 💯 ### Environment * Python version: 3.6.9 * NetBox version: 2.8.4 ### Proposed Functionality Permit the user to assign an IP address to console server ports. ### Use Case (This is Cisco-specific configurations, but other vendors easily apply) As a network administrator, I wish to avoid logging into a console server first before choosing a line, so I use features such as [`ip alias`](https://www.cisco.com/c/en/us/td/docs/ios/termserv/command/reference/tsv_book.pdf), `rotary` and `ip ssh port 2001 rotary ...` to assign console ports directly to IP addresses. This permits greater visibility into who owns the session using SSH which provides a username. As is today, I could create a Virtual Interface for the corresponding TTY line, but it makes it difficult to trace IPs to console server ports using the UI. It also makes scripting the NetBox data model into a configuration for the console server easier. It would be nice to be able to assign an IP address to a console server port to make it easier to note which IPs are assigned to which equipment so cable-tracing is more evident. It would be nice for this IP to be reflected in the connected device, but this isn't as necessary. ### Database Changes As necessary to support feature. ### External Dependencies None.
adam closed this issue 2025-12-29 18:30:51 +01:00
adam commented 2025-12-29 18:30:51 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (May 29, 2020):

Sorry, this would violate our design philosophy of modeling the real world: IP addresses are assigned only to interfaces, and software handles the transfer of data from interface to console server port. It would not make sense to map IP addresses to console ports directly.

@jeremystretch commented on GitHub (May 29, 2020): Sorry, this would violate our design philosophy of modeling the real world: IP addresses are assigned only to interfaces, and software handles the transfer of data from interface to console server port. It would not make sense to map IP addresses to console ports directly.
adam commented 2025-12-29 18:30:51 +01:00
Author
Owner
Copy Link

@chris-mccoy commented on GitHub (May 29, 2020):

Okay, thank you.

@chris-mccoy commented on GitHub (May 29, 2020): Okay, thank you.
adam commented 2025-12-29 18:30:51 +01:00
Author
Owner
Copy Link

@wat-doing commented on GitHub (Jun 4, 2020):

I agree with Chris' request. Makes sense to document the IP address used to connect to the Console port.
I guess I'll just keep creating Serial OOB / Console ports as Interfaces.

@wat-doing commented on GitHub (Jun 4, 2020): I agree with Chris' request. Makes sense to document the IP address used to connect to the Console port. I guess I'll just keep creating Serial OOB / Console ports as Interfaces.
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
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#3736
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?