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

Unable to create virtual interface with duplicate name across Virtual Device Contexts (VDC) #7593

New Issue
Closed
opened 2025-12-29 20:25:50 +01:00 by adam · 1 comment
adam commented 2025-12-29 20:25:50 +01:00
Owner
Copy Link

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

NetBox version

v3.4.3

Python version

3.9

Steps to Reproduce

  1. Create a device
  2. Create a VDC on the device with name VDC1
  3. Create a VDC on the device with name VDC2
  4. Create an interface on the device with the following properties:
  • name: Vlan100
  • type: virtual
  • virtual device context: VDC1
  1. Try to create an interface on the device with the following properties:
  • name: Vlan100
  • type: virtual
  • virtual device context: VDC2

Expected Behavior

Netbox should successfully create the interface object in step 5. Alternatively, if Netbox fails to do so, it should at the very least throw an error.

Reason:

A device object should be able to hold multiple virtual interfaces (i.e. interfaces with type LAG, Virtual or Bridge) with the duplicate names as long as they are assigned to separate Virtual Device Contexts on said device object. Otherwise, it may not be possible to use Netbox to model e.g. SVIs (Switched Virtual Interfaces) or Port-channels (= Cisco-speak for LAGs), which may perfectly well exist as multiple but isolated completely instances across VDCs of one single, read-world switch.

Observed Behavior

The "Add a new interface" page reloads without any error or warning message, and the interface is not created.

Originally created by @koratfood on GitHub (Feb 2, 2023). ### NetBox version v3.4.3 ### Python version 3.9 ### Steps to Reproduce 1. Create a device 2. Create a VDC on the device with name VDC1 3. Create a VDC on the device with name VDC2 4. Create an interface on the device with the following properties: - name: Vlan100 - type: virtual - virtual device context: VDC1 5. Try to create an interface on the device with the following properties: - name: Vlan100 - type: virtual - virtual device context: VDC2 ### Expected Behavior Netbox should successfully create the interface object in step 5. Alternatively, if Netbox fails to do so, it should at the very least throw an error. Reason: A device object should be able to hold multiple virtual interfaces (i.e. interfaces with type LAG, Virtual or Bridge) with the duplicate names as long as they are assigned to separate Virtual Device Contexts on said device object. Otherwise, it may not be possible to use Netbox to model e.g. SVIs (Switched Virtual Interfaces) or Port-channels (= Cisco-speak for LAGs), which may perfectly well exist as multiple but isolated completely instances across VDCs of one single, read-world switch. ### Observed Behavior The "Add a new interface" page reloads without any error or warning message, and the interface is not created.
adam closed this issue 2025-12-29 20:25:50 +01:00
adam commented 2025-12-29 20:25:51 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Feb 2, 2023):

This is expected behavior. Interface names must be unique per device irrespective to their assignment to VDCs.

@jeremystretch commented on GitHub (Feb 2, 2023): This is expected behavior. Interface names must be unique per device irrespective to their assignment to VDCs.
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#7593
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?