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

Allow virtual interface objects in separate VDCs to have the same name #7594

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

Originally created by @koratfood on GitHub (Feb 2, 2023).

NetBox version

v3.4.3

Feature type

Change to existing functionality

Proposed functionality

Allow multiple virtual interfaces (i.e. types Bridge, LAG and Virtual) on a single device to be created with the same name as long as each of them are tied to separate Virtual Device Contexts.

Use case

Ability to model real-world Cisco Nexus switch deployments (e.g. 7000 series) where, for example, SVIs and Port-channels can exist on multiple VDCs with the same name.

Database changes

Unknown as I am not a programmer, but I would expect some challenges aligning such a change with uniqueness constraints.

External dependencies

No response

Originally created by @koratfood on GitHub (Feb 2, 2023). ### NetBox version v3.4.3 ### Feature type Change to existing functionality ### Proposed functionality Allow multiple virtual interfaces (i.e. types Bridge, LAG and Virtual) on a single device to be created with the same name as long as each of them are tied to separate Virtual Device Contexts. ### Use case Ability to model real-world Cisco Nexus switch deployments (e.g. 7000 series) where, for example, SVIs and Port-channels can exist on multiple VDCs with the same name. ### Database changes Unknown as I am not a programmer, but I would expect some challenges aligning such a change with uniqueness constraints. ### External dependencies _No response_
adam added the type: featurepending closurestatus: under review labels 2025-12-29 20:25:51 +01:00
adam closed this issue 2025-12-29 20:25:51 +01:00
adam commented 2025-12-29 20:25:52 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Mar 16, 2023):

Further research and discussion is needed before this can proceed. NetBox currently functions with the understanding that interfaces are unique per device/VM, and changing this could have wide-reaching effects across the application. The first step in this proposal would be to identify what those effects would be and how they can be mitigated.

@jeremystretch commented on GitHub (Mar 16, 2023): Further research and discussion is needed before this can proceed. NetBox currently functions with the understanding that interfaces are unique per device/VM, and changing this could have wide-reaching effects across the application. The first step in this proposal would be to identify what those effects would be and how they can be mitigated.
adam commented 2025-12-29 20:25:53 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Aug 9, 2023):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. Do not attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our contributing guide.

@github-actions[bot] commented on GitHub (Aug 9, 2023): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. **Do not** attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our [contributing guide](https://github.com/netbox-community/netbox/blob/develop/CONTRIBUTING.md).
adam commented 2025-12-29 20:25:53 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Sep 9, 2023):

This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.

@github-actions[bot] commented on GitHub (Sep 9, 2023): This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.
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 pending closure status: under review type: feature
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#7594
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?