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

Make available to show only own ports of Stack master #2075

New Issue
Closed
opened 2025-12-29 17:22:03 +01:00 by adam · 1 comment
adam commented 2025-12-29 17:22:03 +01:00
Owner
Copy Link

Originally created by @igorrev on GitHub (Oct 29, 2018).

Environment

  • Python version:
  • NetBox version:

Proposed Functionality

Make available to show only own interfaces of Stack master in contrast to show all interfaces of stack.

Use Case

I name interfaces how I see it on the physical device. So if I have stack of two Cisco switches I make two devices with different names but the same interface names. It looks like:
Switch-1: GE0, GE1, ...
Switch-2: GE0, GE1, ...
It's not a problem. But if I combine these switches to stack via Virtual Chassis and select, for example, Switch-1 as Master, then go to Switch-1 page, I see all stack interfaces in list:
Switch-1:
GE0,
GE0,
GE1,
GE1,
...
The first entry of each interface relates to Switch-1, the second entry - to Switch-2. But it's impossible to indicate relation from this page. It's very difficult to maintain connections.

I can name interfaces how I see it in device configs, for example, GE1/0/1, GE1/0/2, GE2/0/1, GE2/0/2, ... But in this case it's more difficult to identify interface on device because labels on device doesn't match names in NetBox. Also I need to rename all interfaces if I change switch number in stack, move it to another stack or install it stand-alone.

Additionally it will be great to see internal interface name (how it named in config) and external name (how it labeled on device)

Originally created by @igorrev on GitHub (Oct 29, 2018). ### Environment * Python version: <!-- Example: 3.5.4 --> * NetBox version: <!-- Example: 2.3.6 --> <!-- Describe in detail the new functionality you are proposing. Include any specific changes to work flows, data models, or the user interface. --> ### Proposed Functionality Make available to show only own interfaces of Stack master in contrast to show all interfaces of stack. ### Use Case I name interfaces how I see it on the physical device. So if I have stack of two Cisco switches I make two devices with different names but the same interface names. It looks like: Switch-1: GE0, GE1, ... Switch-2: GE0, GE1, ... It's not a problem. But if I combine these switches to stack via Virtual Chassis and select, for example, Switch-1 as Master, then go to Switch-1 page, I see all stack interfaces in list: Switch-1: GE0, GE0, GE1, GE1, ... The first entry of each interface relates to Switch-1, the second entry - to Switch-2. But it's impossible to indicate relation from this page. It's very difficult to maintain connections. I can name interfaces how I see it in device configs, for example, GE1/0/1, GE1/0/2, GE2/0/1, GE2/0/2, ... But in this case it's more difficult to identify interface on device because labels on device doesn't match names in NetBox. Also I need to rename all interfaces if I change switch number in stack, move it to another stack or install it stand-alone. Additionally it will be great to see internal interface name (how it named in config) and external name (how it labeled on device)
adam closed this issue 2025-12-29 17:22:03 +01:00
adam commented 2025-12-29 17:22:03 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Oct 30, 2018):

I can name interfaces how I see it in device configs, for example, GE1/0/1, GE1/0/2, GE2/0/1, GE2/0/2, ...

This is the recommended approach.

But in this case it's more difficult to identify interface on device because labels on device doesn't match names in NetBox.

But they do match how the master device references its interfaces, which is far more important. Further, having e.g. multiple interfaces named GE0 doesn't help, because you have no way of knowing which is which.

@jeremystretch commented on GitHub (Oct 30, 2018): > I can name interfaces how I see it in device configs, for example, GE1/0/1, GE1/0/2, GE2/0/1, GE2/0/2, ... This is the recommended approach. > But in this case it's more difficult to identify interface on device because labels on device doesn't match names in NetBox. But they _do_ match how the master device references its interfaces, which is far more important. Further, having e.g. multiple interfaces named `GE0` doesn't help, because you have no way of knowing which is which.
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#2075
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?