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

Management/Console Interface within VC #1687

New Issue
Closed
opened 2025-12-29 16:34:26 +01:00 by adam · 1 comment
adam commented 2025-12-29 16:34:26 +01:00
Owner
Copy Link

Originally created by @tvberlin on GitHub (Apr 21, 2018).

Issue type

[x] Feature request
[ ] Bug report
[ ] Documentation

Environment

  • Python version: 3.4.2
  • NetBox version: 2.3.3

Description

When creating virtual chassis, e.g. w/ Juniper devices, some interfaces (Console, Management) have the same name across all members. Netbox displays them with their given name from the template (e.g. MGMT) w/o giving the user the possibility to distinguish between the different VC members

I'd recommend displaying the members name next to the interface when duplicate interface names are detected. We've found a workaround by naming interfaces "MGMT_LC0" for example.

Originally created by @tvberlin on GitHub (Apr 21, 2018). ### Issue type [x] Feature request [ ] Bug report [ ] Documentation ### Environment * Python version: 3.4.2 * NetBox version: 2.3.3 ### Description When creating virtual chassis, e.g. w/ Juniper devices, some interfaces (Console, Management) have the same name across all members. Netbox displays them with their given name from the template (e.g. MGMT) w/o giving the user the possibility to distinguish between the different VC members I'd recommend displaying the members name next to the interface when duplicate interface names are detected. We've found a workaround by naming interfaces "MGMT_LC0" for example.
adam closed this issue 2025-12-29 16:34:26 +01:00
adam commented 2025-12-29 16:34:26 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Apr 23, 2018):

You'll need to rename the interfaces of each member device in the virtual chassis. NetBox cannot make assumptions about whether or how these interfaces should be renamed.

@jeremystretch commented on GitHub (Apr 23, 2018): You'll need to rename the interfaces of each member device in the virtual chassis. NetBox cannot make assumptions about whether or how these interfaces should be renamed.
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#1687
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?