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

Virtual switch dont return all interfaces #9437

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

Originally created by @rsp1991 on GitHub (Apr 4, 2024).

Deployment Type

NetBox Enterprise

NetBox Version

v3.7.3

Python Version

3.8

Steps to Reproduce

1 - Get the Master device of the Virtual Switch with switch switches
2 - Go to https:///api/dcim/interfaces/?device=
3 - The output show only interfaces from Master switch.

Expected Behavior

The expected is the Master return all interface

Observed Behavior

Return all interfaces

Originally created by @rsp1991 on GitHub (Apr 4, 2024). ### Deployment Type NetBox Enterprise ### NetBox Version v3.7.3 ### Python Version 3.8 ### Steps to Reproduce 1 - Get the Master device of the Virtual Switch with switch switches 2 - Go to https://<Netbox IP>/api/dcim/interfaces/?device=<device name> 3 - The output show only interfaces from Master switch. ### Expected Behavior The expected is the Master return all interface ### Observed Behavior Return all interfaces
adam closed this issue 2025-12-29 20:49:57 +01:00
adam commented 2025-12-29 20:49:57 +01:00
Author
Owner
Copy Link

@arthanson commented on GitHub (Apr 5, 2024):

Thank you for opening a bug report. Unfortunately, the information you have provided is not sufficient for someone else to attempt to reproduce the reported behavior. Remember, each bug report must include detailed steps that someone else can follow on a clean, empty NetBox installation to reproduce the exact problem you're experiencing. These instructions should include the creation of any involved objects, any configuration changes, and complete accounting of the actions being taken. Also be sure that your report does not reference data on the public NetBox demo, as that is subject to change at any time by an outside party and cannot be relied upon for bug reports.

@arthanson commented on GitHub (Apr 5, 2024): Thank you for opening a bug report. Unfortunately, the information you have provided is not sufficient for someone else to attempt to reproduce the reported behavior. Remember, each bug report must include detailed steps that someone else can follow on a clean, empty NetBox installation to reproduce the exact problem you're experiencing. These instructions should include the creation of any involved objects, any configuration changes, and complete accounting of the actions being taken. Also be sure that your report does not reference data on the public NetBox demo, as that is subject to change at any time by an outside party and cannot be relied upon for bug reports.
adam commented 2025-12-29 20:49:58 +01:00
Author
Owner
Copy Link

@rsp1991 commented on GitHub (Apr 5, 2024):

Hello @arthanson

Sorry, but I don't have too much ideia to explain, I will try again:

I configured one virtual switch with two cisco switch with 48 ports,

SW1 48 Ports - Master
SW2 48 Ports

When I user the device.interfaces.all() I get just interfaces from SW1, I checked via URL:

https://<netbox_IP>api/dcim/interfaces/?device=

And I confirmed that API answer the requisition with just SW1.

All interfaces in SW1 start with 1 and in the SW2 start with 2 so I don't use same name.

@rsp1991 commented on GitHub (Apr 5, 2024): Hello @arthanson Sorry, but I don't have too much ideia to explain, I will try again: I configured one virtual switch with two cisco switch with 48 ports, SW1 48 Ports - Master SW2 48 Ports When I user the device.interfaces.all() I get just interfaces from SW1, I checked via URL: https://<netbox_IP>api/dcim/interfaces/?device=<device> And I confirmed that API answer the requisition with just SW1. All interfaces in SW1 start with 1 and in the SW2 start with 2 so I don't use same name.
adam commented 2025-12-29 20:49:58 +01:00
Author
Owner
Copy Link

@jeffgdotorg commented on GitHub (May 17, 2024):

It seems you're looking for advice on how to accomplish a task, rather than reporting a bug in the NetBox code that needs to be fixed. I'm therefore converting this issue to a discussion so that others in the community can help you accomplish your goal.

@jeffgdotorg commented on GitHub (May 17, 2024): It seems you're looking for advice on how to accomplish a task, rather than reporting a bug in the NetBox code that needs to be fixed. I'm therefore converting this issue to a discussion so that others in the community can help you accomplish your goal.
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#9437
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?