VLAn overview - Device Interfaces List - With Connection, Link Peers #9512

Open
opened 2025-12-29 20:50:49 +01:00 by adam · 0 comments
Owner

Originally created by @LHBL2003 on GitHub (Apr 22, 2024).

NetBox version

v.3.7.5

Feature type

Change to existing functionality

Proposed functionality

In the Device Interfaces list of a VLAN, all devices and their interfaces that use this VLAN are listed. (https://netbox/ipam/vlans/XXX/interfaces/)
Please also list the Connection, Link Peers columns.
These columns also exist for the Device --> Interface.

image

Use case

The majority of entries are switches, as the VLANs are configured as tagged or untagged here.

However, it is often of interest which server, telephone system etc. ultimately uses this VLAN. One unattractive option is to store the VLAN on each server as an Untagged vLan, for example, even if nothing has been set on the server device. However, this will result in the status of the server and switch differing at some point because you may forget to change the VLAN entry on the server.

In order to still have an overview, it is helpful if the device interface list of the VLAN contains the following columns:

[Existing]

  • Device
  • Interface
  • Tagged

[New]

  • Connection
  • Link Peers

Database changes

None

External dependencies

None

Originally created by @LHBL2003 on GitHub (Apr 22, 2024). ### NetBox version v.3.7.5 ### Feature type Change to existing functionality ### Proposed functionality In the Device Interfaces list of a VLAN, all devices and their interfaces that use this VLAN are listed. (https://netbox/ipam/vlans/XXX/interfaces/) Please also list the Connection, Link Peers columns. These columns also exist for the Device --> Interface. ![image](https://github.com/netbox-community/netbox/assets/46369917/cc20c85c-c16a-43af-82db-012e995fe402) ### Use case The majority of entries are switches, as the VLANs are configured as tagged or untagged here. However, it is often of interest which server, telephone system etc. ultimately uses this VLAN. One unattractive option is to store the VLAN on each server as an Untagged vLan, for example, even if nothing has been set on the server device. However, this will result in the status of the server and switch differing at some point because you may forget to change the VLAN entry on the server. In order to still have an overview, it is helpful if the device interface list of the VLAN contains the following columns: [Existing] - Device - Interface - Tagged [New] - Connection - Link Peers ### Database changes None ### External dependencies None
adam added the type: featurenetboxstatus: backlogcomplexity: low labels 2025-12-29 20:50:50 +01:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#9512