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

[PR #14783] [CLOSED] Add support for displaying port and interface information on a virtual chassis #14454

New Issue
Closed
opened 2025-12-29 23:24:34 +01:00 by adam · 0 comments
adam commented 2025-12-29 23:24:34 +01:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/netbox-community/netbox/pull/14783
Author: @jschewebbn
Created: 1/12/2024
Status: ❌ Closed

Base: develop ← Head: feature/virtual-chassis-ports

📝 Commits (3)

  • 784eba4 Add support for finding all front ports in a virtual chassis
  • 1b71e51 Add support for finding all rear ports in a virtual chassis
  • f551c8b Add support for displaying device information to VirtualChassis

📊 Changes

3 files changed (+136 additions, -1 deletions)

View changed files

📝 netbox/dcim/filtersets.py (+42 -0)
📝 netbox/dcim/models/devices.py (+32 -0)
📝 netbox/dcim/views.py (+62 -1)

📄 Description

This is in support of fixing the issues discussed at https://github.com/netbox-community/netbox/discussions/12525

In addition to seeing the interfaces and ports on the master device in a virtual chassis this change allows one to view the interfaces and ports for all members on the virtual chassis device itself. This makes it easier to make cable connections from a virtual device as one can find all of the information on the virtual device itself.

By adding ports support to the virtual device one can create virtual patch panels in addition to stacked switches. This is useful when there are a number of physical patch panels in a rack where all ports are uniquely numbered and one needs to connect a cable from that stack of patch panels to another device. One doesn't need to remember which physical patch panel the port is on, only the label of the port.

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/netbox-community/netbox/pull/14783 **Author:** [@jschewebbn](https://github.com/jschewebbn) **Created:** 1/12/2024 **Status:** ❌ Closed **Base:** `develop` ← **Head:** `feature/virtual-chassis-ports` --- ### 📝 Commits (3) - [`784eba4`](https://github.com/netbox-community/netbox/commit/784eba479665f0d01723135399dd6b554e9d264f) Add support for finding all front ports in a virtual chassis - [`1b71e51`](https://github.com/netbox-community/netbox/commit/1b71e51f4d77c2cf7130b0b45d00f614fddf5d27) Add support for finding all rear ports in a virtual chassis - [`f551c8b`](https://github.com/netbox-community/netbox/commit/f551c8b7f5d5803c9f48faa025927a2708b09eba) Add support for displaying device information to VirtualChassis ### 📊 Changes **3 files changed** (+136 additions, -1 deletions) <details> <summary>View changed files</summary> 📝 `netbox/dcim/filtersets.py` (+42 -0) 📝 `netbox/dcim/models/devices.py` (+32 -0) 📝 `netbox/dcim/views.py` (+62 -1) </details> ### 📄 Description This is in support of fixing the issues discussed at https://github.com/netbox-community/netbox/discussions/12525 In addition to seeing the interfaces and ports on the master device in a virtual chassis this change allows one to view the interfaces and ports for all members on the virtual chassis device itself. This makes it easier to make cable connections from a virtual device as one can find all of the information on the virtual device itself. By adding ports support to the virtual device one can create virtual patch panels in addition to stacked switches. This is useful when there are a number of physical patch panels in a rack where all ports are uniquely numbered and one needs to connect a cable from that stack of patch panels to another device. One doesn't need to remember which physical patch panel the port is on, only the label of the port. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
adam added the pull-request label 2025-12-29 23:24:34 +01:00
adam closed this issue 2025-12-29 23:24:34 +01:00
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 pull-request
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#14454
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?