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

Parent device inherits child's primary IP #4942

New Issue
Closed
opened 2025-12-29 19:22:29 +01:00 by adam · 1 comment
adam commented 2025-12-29 19:22:29 +01:00
Owner
Copy Link

Originally created by @CapnCheapo on GitHub (May 25, 2021).

NetBox version

v2.11.3

Feature type

Change to existing functionality

Proposed functionality

It would be nice if a parent device could inherit a child's primary IP if the primary doesn't already have an address assigned. Either automatically, in the case of a single child having a single primary, or otherwise maybe the child primaries show up in the parent's dropdown box.

Use case

A chassis-based switch or router often does not have a management interface outside of whatever the supervisors have, but is considered managed by the sup's IP. This doesn't account for advanced setups such as active/standby sups or virtual device partitioning, but would be helpful for many standard use cases.

Database changes

Unknown

External dependencies

Unknown

Originally created by @CapnCheapo on GitHub (May 25, 2021). ### NetBox version v2.11.3 ### Feature type Change to existing functionality ### Proposed functionality It would be nice if a parent device could inherit a child's primary IP if the primary doesn't already have an address assigned. Either automatically, in the case of a single child having a single primary, or otherwise maybe the child primaries show up in the parent's dropdown box. ### Use case A chassis-based switch or router often does not have a management interface outside of whatever the supervisors have, but is considered managed by the sup's IP. This doesn't account for advanced setups such as active/standby sups or virtual device partitioning, but would be helpful for many standard use cases. ### Database changes Unknown ### External dependencies Unknown
adam added the type: feature label 2025-12-29 19:22:29 +01:00
adam closed this issue 2025-12-29 19:22:29 +01:00
adam commented 2025-12-29 19:22:29 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (May 25, 2021):

In NetBox, child devices have their own control plane and components, IP addresses, etc. From the docs:

Device bays are not suitable for modeling line cards (such as those commonly found in chassis-based routers and switches), as these components depend on the control plane of the parent device to operate. Instead, line cards and similarly non-autonomous hardware should be modeled as inventory items within a device, with any associated interfaces or other components assigned directly to the device.

This model is intended for e.g. blade servers and similar independent devices. Chassis line card should be modeled as inventory items, with their components and addressed added to the chassis device in which they reside.

@jeremystretch commented on GitHub (May 25, 2021): In NetBox, child devices have their own control plane and components, IP addresses, etc. From [the docs](https://netbox.readthedocs.io/en/stable/core-functionality/devices/#device-bays): > Device bays are not suitable for modeling line cards (such as those commonly found in chassis-based routers and switches), as these components depend on the control plane of the parent device to operate. Instead, line cards and similarly non-autonomous hardware should be modeled as inventory items within a device, with any associated interfaces or other components assigned directly to the device. This model is intended for e.g. blade servers and similar independent devices. Chassis line card should be modeled as inventory items, with their components and addressed added to the chassis device in which they reside.
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 type: feature
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#4942
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?