starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-12 05:20:31 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

Show interfaces provided by device bay on main device screen #1265

New Issue
Closed
opened 2025-12-29 16:30:54 +01:00 by adam · 2 comments
adam commented 2025-12-29 16:30:54 +01:00
Owner
Copy Link

Originally created by @bitratio on GitHub (Sep 26, 2017).

Issue type

[o] Feature request
[ ] Bug report
[ ] Documentation

Environment

  • Python version:
  • NetBox version:

Description

Hello;

Please show interfaces provided by child devices on parent device page.

We have a large juniper routing estate and we are hoping that you might accommodate a feature for us.

Currently, we have a mixed estate of different Juniper routers with interfaces provided by MPC or MIC Cards.

We have added these as child devices as the data schema suggests however to view the ports that these cards provide to the device you have to physically click into the child device, this seems clunky.

Is there a way that we can populate the main device interfaces list with the interfaces that are provided by the child device?

Obviously, we aren't going to populate the interfaces list for the main device as these devices do not come with any interfaces as standard, they are all provided by the child MICS.

Originally created by @bitratio on GitHub (Sep 26, 2017). <!-- Before opening a new issue, please search through the existing issues to see if your topic has already been addressed. Note that you may need to remove the "is:open" filter from the search bar to include closed issues. Check the appropriate type for your issue below by placing an x between the brackets. If none of the below apply, please raise your issue for discussion on our mailing list: https://groups.google.com/forum/#!forum/netbox-discuss Please note that issues which do not fall under any of the below categories will be closed. ---> ### Issue type [o] Feature request <!-- Requesting the implementation of a new feature --> [ ] Bug report <!-- Reporting unexpected or erroneous behavior --> [ ] Documentation <!-- Proposing a modification to the documentation --> <!-- Please describe the environment in which you are running NetBox. (Be sure to verify that you are running the latest stable release of NetBox before submitting a bug report.) --> ### Environment * Python version: <!-- Example: 3.5.4 --> * NetBox version: <!-- Example: 2.1.3 --> <!-- BUG REPORTS must include: * A list of the steps needed to reproduce the bug * A description of the expected behavior * Any relevant error messages (screenshots may also help) FEATURE REQUESTS must include: * A detailed description of the proposed functionality * A use case for the new feature * A rough description of any necessary changes to the database schema * Any relevant third-party libraries which would be needed --> ### Description Hello; Please show interfaces provided by child devices on parent device page. We have a large juniper routing estate and we are hoping that you might accommodate a feature for us. Currently, we have a mixed estate of different Juniper routers with interfaces provided by MPC or MIC Cards. We have added these as child devices as the data schema suggests however to view the ports that these cards provide to the device you have to physically click into the child device, this seems clunky. Is there a way that we can populate the main device interfaces list with the interfaces that are provided by the child device? Obviously, we aren't going to populate the interfaces list for the main device as these devices do not come with any interfaces as standard, they are all provided by the child MICS.
adam closed this issue 2025-12-29 16:30:54 +01:00
adam commented 2025-12-29 16:30:55 +01:00
Author
Owner
Copy Link

@lampwins commented on GitHub (Sep 26, 2017):

Child devices in netbox are intended for devices which are managed independently of the parent. In other words, the parent it just a chassis that provides power. In the case of Juniper MPC/MIC's these are not managed independently of the router chassis. The most common way in netbox to do this is to populate the "parent" (just the regular router) with the interfaces as normal. Netbox has some intelligence (for sorting and such) for the fpc/pic/port syntax. You can track asset information in the inventory section of the device at this point for things like the MPC's serial number.

Related to your query is #940 for switch stacking. But that would be for actual virtual chassis support in Juniper world.

@lampwins commented on GitHub (Sep 26, 2017): Child devices in netbox are intended for devices which are managed independently of the parent. In other words, the parent it just a chassis that provides power. In the case of Juniper MPC/MIC's these are not managed independently of the router chassis. The most common way in netbox to do this is to populate the "parent" (just the regular router) with the interfaces as normal. Netbox has some intelligence (for sorting and such) for the fpc/pic/port syntax. You can track asset information in the inventory section of the device at this point for things like the MPC's serial number. Related to your query is #940 for switch stacking. But that would be for actual virtual chassis support in Juniper world.
adam commented 2025-12-29 16:30:55 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Sep 26, 2017):

As @lampwins said, you wouldn't represent MPCs as child devices. #824 has been opened to represent discrete line cards in this manner.

@jeremystretch commented on GitHub (Sep 26, 2017): As @lampwins said, you wouldn't represent MPCs as child devices. #824 has been opened to represent discrete line cards in this manner.
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#1265
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?