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

Add the ability to view the list of VLANs on the device interface #1901

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

Originally created by @nborisenkov on GitHub (Aug 7, 2018).

Environment

  • Python version: 3.5.3
  • NetBox version: 2.4.0

Proposed Functionality

Add the ability to view the list of VLANs on the device interface

Use Case

netbox

Database Changes

External Dependencies

Originally created by @nborisenkov on GitHub (Aug 7, 2018). <!-- NOTE: This form is only for proposing specific new features or enhancements. If you have a general idea or question, please post to our mailing list instead of opening an issue: https://groups.google.com/forum/#!forum/netbox-discuss NOTE: Due to an excessive backlog of feature requests, we are not currently accepting any proposals which significantly extend NetBox's feature scope. Please describe the environment in which you are running NetBox. Be sure that you are running an unmodified instance of the latest stable release before submitting a bug report. --> ### Environment * Python version: 3.5.3 * NetBox version: 2.4.0 <!-- Describe in detail the new functionality you are proposing. Include any specific changes to work flows, data models, or the user interface. --> ### Proposed Functionality Add the ability to view the list of VLANs on the device interface <!-- Convey an example use case for your proposed feature. Write from the perspective of a NetBox user who would benefit from the proposed functionality and describe how. ---> ### Use Case ![netbox](https://user-images.githubusercontent.com/2655014/43775740-696db53e-9a56-11e8-95bb-558ad07867af.png) <!-- Note any changes to the database schema necessary to support the new feature. For example, does the proposal require adding a new model or field? (Not all new features require database changes.) ---> ### Database Changes <!-- List any new dependencies on external libraries or services that this new feature would introduce. For example, does the proposal require the installation of a new Python package? (Not all new features introduce new dependencies.) --> ### External Dependencies
adam closed this issue 2025-12-29 17:20:13 +01:00
adam commented 2025-12-29 17:20:14 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Aug 7, 2018):

One sentence is not a legitimate feature request. Please extend your request with sufficient detail per the template.

@jeremystretch commented on GitHub (Aug 7, 2018): One sentence is not a legitimate feature request. Please extend your request with sufficient detail per the template.
adam commented 2025-12-29 17:20:14 +01:00
Author
Owner
Copy Link

@nborisenkov commented on GitHub (Aug 7, 2018):

I want to see which vlans, IP addresses and tenants are connected to the device port. Summary table.

For example: I received a message that the device was unavailable and I want to find out which services and tenants suffered from this.

Now I have to go into each interface separately to find out what vlans and ip-addresses are configured on this device.

I need information about interface numbers, VLANs, IP addresses and tenants in one place.

With summary information, i can quickly find tenants who work through a specific device port. And just see all the tenants, IP addresses and vlans who work through this device.

I attach a new screenshot

Perhaps it can be done somehow differently or in another place.
netbox2

@nborisenkov commented on GitHub (Aug 7, 2018): I want to see which vlans, IP addresses and tenants are connected to the device port. Summary table. For example: I received a message that the device was unavailable and I want to find out which services and tenants suffered from this. Now I have to go into each interface separately to find out what vlans and ip-addresses are configured on this device. I need information about interface numbers, VLANs, IP addresses and tenants in one place. With summary information, i can quickly find tenants who work through a specific device port. And just see all the tenants, IP addresses and vlans who work through this device. I attach a new screenshot Perhaps it can be done somehow differently or in another place. ![netbox2](https://user-images.githubusercontent.com/2655014/43779437-159da526-9a61-11e8-8ebd-2e7de41b60e3.png)
adam commented 2025-12-29 17:20:15 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Aug 8, 2018):

This isn't a practical approach, as interfaces often carry dozens or hundreds of VLANs and the interfaces table is already very busy. Alternatively, the individual interface view lists the VLANs for each interface individually.

@jeremystretch commented on GitHub (Aug 8, 2018): This isn't a practical approach, as interfaces often carry dozens or hundreds of VLANs and the interfaces table is already very busy. Alternatively, the individual interface view lists the VLANs for each interface individually.
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#1901
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?