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

Improper naming of interfaces if the master VC member displays the interfaces of all members in the VC / Stack. #4639

New Issue
Closed
opened 2025-12-29 19:19:01 +01:00 by adam · 2 comments
adam commented 2025-12-29 19:19:01 +01:00
Owner
Copy Link

Originally created by @igloo777 on GitHub (Mar 9, 2021).

NetBox version

v.2.10.4

Python version

3.7

Steps to Reproduce

  • Create VC with 2 members.
  • Open Interfaces tab in Master member object and check for duplicated interfaces.

Expected Behavior

Node value inside the Node/Slot/Port triplet should be equal to VC member Position value.
Interface name should be changed when we look at the Interfaces of VC/Stack master in UI (or asking for master interfaces in API query).

Observed Behavior

For sample, I have more than one Interface with name Gi1/0/1.

It looks like a bug.

Originally created by @igloo777 on GitHub (Mar 9, 2021). ### NetBox version v.2.10.4 ### Python version 3.7 ### Steps to Reproduce - Create VC with 2 members. - Open Interfaces tab in Master member object and check for duplicated interfaces. ### Expected Behavior Node value inside the Node/Slot/Port triplet should be equal to VC member Position value. Interface name should be changed when we look at the Interfaces of VC/Stack master in UI (or asking for master interfaces in API query). ### Observed Behavior For sample, I have more than one Interface with name Gi1/0/1. It looks like a bug.
adam added the type: bug label 2025-12-29 19:19:01 +01:00
adam closed this issue 2025-12-29 19:19:02 +01:00
adam commented 2025-12-29 19:19:03 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Mar 9, 2021):

You need to rename the interfaces manually (there is a bulk rename option for this). NetBox has no way of discerning how the device's vendor chooses to name VC member interfaces.

@jeremystretch commented on GitHub (Mar 9, 2021): You need to rename the interfaces manually (there is a bulk rename option for this). NetBox has no way of discerning how the device's vendor chooses to name VC member interfaces.
adam commented 2025-12-29 19:19:03 +01:00
Author
Owner
Copy Link

@igloo777 commented on GitHub (Mar 11, 2021):

@jeremystretch thank you for reply!

You need to rename the interfaces manually (there is a bulk rename option for this). NetBox has no way of discerning how the device's vendor chooses to name VC member interfaces.

Usually the 1rst number in the interface name of switch (counting from left) is the Node number (VC member position value).
I've never met another logic in stacks, but maybe you have another experience.

If i rename the interfaces on master switch, it also will be renamed on non-master switch. If i open interfaces tab of non-master switch after that, i see the renamed interfaces, and it looks strange.

How about the idea to hide Interfaces tab if the switch isnon-master member of VC/Stack?

@igloo777 commented on GitHub (Mar 11, 2021): @jeremystretch thank you for reply! > You need to rename the interfaces manually (there is a bulk rename option for this). NetBox has no way of discerning how the device's vendor chooses to name VC member interfaces. Usually the 1rst number in the interface name of switch (counting from left) is the Node number (VC member position value). I've never met another logic in stacks, but maybe you have another experience. If i rename the interfaces on master switch, it also will be renamed on non-master switch. If i open interfaces tab of non-master switch after that, i see the renamed interfaces, and it looks strange. How about the idea to hide Interfaces tab if the switch isnon-master member of VC/Stack?
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 type: bug
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#4639
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?