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

View all interfaces #216

New Issue
Closed
opened 2025-12-29 16:19:33 +01:00 by adam · 5 comments
adam commented 2025-12-29 16:19:33 +01:00
Owner
Copy Link

Originally created by @ghost on GitHub (Jul 14, 2016).

Wondering what people think about viewing interfaces specifically (and only), and viewing groups, ability to filter by type (based on name, "form factor", use status, etc).

Would be nice to see what interfaces are available, and not just connected interfaces.

Originally created by @ghost on GitHub (Jul 14, 2016). Wondering what people think about viewing interfaces specifically (and only), and viewing groups, ability to filter by type (based on name, "form factor", use status, etc). Would be nice to see what interfaces are available, and not just connected interfaces.
adam closed this issue 2025-12-29 16:19:33 +01:00
adam commented 2025-12-29 16:19:33 +01:00
Author
Owner
Copy Link

@bellwood commented on GitHub (Jul 14, 2016):

@rekkoner can you clarify? When I view a device or device type I am able to see every interface defined regardless of its connected status.

Are you speaking to interface connections found on /dcim/interface-connections/?

@bellwood commented on GitHub (Jul 14, 2016): @rekkoner can you clarify? When I view a device or device type I am able to see every interface defined regardless of its connected status. Are you speaking to interface connections found on `/dcim/interface-connections/`?
adam commented 2025-12-29 16:19:34 +01:00
Author
Owner
Copy Link

@ghost commented on GitHub (Jul 14, 2016):

@bellwood sure, basically, listing all defined interfaces, regardless of connected status.

currently, you can see all connected interfaces, and that's it. that's the highest level you can go, and it's limited to view only interfaces connected to something. (not counting viewing a device's interfaces, but only that specific device's interfaces)

it'd be nice if we had visibility into all interfaces, regardless of status or use.

second to that, if we had that visibility, the ability to then filter down based on whatever criteria (core switches blue and green, etc), so we then can look at, potentially, multiple devices' interfaces. then we'd be able to compare primary/secondary port usage, etc.

@ghost commented on GitHub (Jul 14, 2016): @bellwood sure, basically, listing all defined interfaces, regardless of connected status. currently, you can see all connected interfaces, and that's it. that's the highest level you can go, and it's limited to view only interfaces connected to something. (not counting viewing a device's interfaces, but only that specific device's interfaces) it'd be nice if we had visibility into _all_ interfaces, regardless of status or use. second to that, if we had that visibility, the ability to then filter down based on whatever criteria (core switches blue and green, etc), so we then can look at, potentially, multiple devices' interfaces. then we'd be able to compare primary/secondary port usage, etc.
adam commented 2025-12-29 16:19:34 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jul 14, 2016):

As I understand it, you're asking for a list of all interfaces defined in NetBox, from all devices. A typical NetBox installation will have thousands of interfaces. I'm not sure I see what purpose this would serve. What would you do with a list of every interface?

@jeremystretch commented on GitHub (Jul 14, 2016): As I understand it, you're asking for a list of _all_ interfaces defined in NetBox, from all devices. A typical NetBox installation will have thousands of interfaces. I'm not sure I see what purpose this would serve. What would you do with a list of every interface?
adam commented 2025-12-29 16:19:35 +01:00
Author
Owner
Copy Link

@ghost commented on GitHub (Jul 14, 2016):

true, viewing a list of all 3000 or whatever interfaces wouldn't be very useful. but, if you can drill down to type, location, device model, primary/secondary/backup/etc, and show brief interface details, (if name, device, state (in use, unused, reserved, disabled, planned, decommed, etc)), i think it would be helpful.

i know my datacenter infrastructure teams would use that to track our core switch interface usage, storage switch interface usage, and so on, for capacity planning, physical configuration verification, etc.

@ghost commented on GitHub (Jul 14, 2016): true, viewing a list of all 3000 or whatever interfaces wouldn't be very useful. but, if you can drill down to type, location, device model, primary/secondary/backup/etc, and show brief interface details, (if name, device, state (in use, unused, reserved, disabled, planned, decommed, etc)), i think it would be helpful. i know my datacenter infrastructure teams would use that to track our core switch interface usage, storage switch interface usage, and so on, for capacity planning, physical configuration verification, etc.
adam commented 2025-12-29 16:19:35 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Sep 22, 2016):

I'm going to close this out as it seems like a pretty esoteric request. It can likely be accomplished with a few API calls anyway.

@jeremystretch commented on GitHub (Sep 22, 2016): I'm going to close this out as it seems like a pretty esoteric request. It can likely be accomplished with a few API calls anyway.
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#216
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?