Parent prefix does not inherit the use of child prefixes #9814

Closed
opened 2025-12-29 21:23:06 +01:00 by adam · 1 comment
Owner

Originally created by @fabioon on GitHub (Jun 7, 2024).

Deployment Type

Self-hosted

NetBox Version

v4.0.5

Python Version

3.10

Steps to Reproduce

Parent prefix didn't increase utilization when "Mark utilized" is checked

When a child prefix is ​​created and marked "Mark utilized", the child prefix object's fields do not increase the "Child IPs" attribute and also do not increase the IP usage of the parent prefix.

I tested on https://demo.netbox.dev/ (v4.0.5)

-> 192.168.100.0/24 - active - utilization - 0%
---> 192.168.100.0/25 - active - utilization 100%

Prefix summary(active prefix type)

image

Parent prefix details
image

Child prefix details ("Mark utilized" checked)
image

Problem:

I created the child prefix with the "Mark utilized" option checked, the use of the child prefix was not inherited to the parent prefix


When I change the status of the parent prefix to "Container" whenever we create a child prefix, even without creating the ip addresses, the use of the precise parent inherits everything, getting 100% usage even without using all the ip addresses

Parent prefix with container status
image

Parent prefix summary
image

Childs prefix details - 01

image

Childs prefix details - 02

image

Expected Behavior

We hope that when we check the "Mark utilized" box increase the ip address utilization from current prefix and this utilization will reflect in the parent prefix

Observed Behavior

The use of ip addresses of child prefixes is not shown in the parent prefix in the percentage

Originally created by @fabioon on GitHub (Jun 7, 2024). ### Deployment Type Self-hosted ### NetBox Version v4.0.5 ### Python Version 3.10 ### Steps to Reproduce ## Parent prefix didn't increase utilization when "Mark utilized" is checked ### When a child prefix is ​​created and marked "Mark utilized", the child prefix object's fields do not increase the "Child IPs" attribute and also do not increase the IP usage of the parent prefix. ##### I tested on https://demo.netbox.dev/ (v4.0.5) -> 192.168.100.0/24 - active - utilization - 0% ---> 192.168.100.0/25 - active - utilization 100% Prefix summary(active prefix type) ![image](https://github.com/netbox-community/netbox/assets/13603619/6135745f-6033-4ed1-8f1e-e559ded488ed) Parent prefix details ![image](https://github.com/netbox-community/netbox/assets/13603619/4c48b60e-e40f-405d-b8d6-25871e8d8bd0) Child prefix details ("Mark utilized" checked) ![image](https://github.com/netbox-community/netbox/assets/13603619/3c9402a1-a7b1-4d69-83af-d9157994e27b) Problem: # I created the child prefix with the "Mark utilized" option checked, the use of the child prefix was not inherited to the parent prefix ----------------------------- When I change the status of the parent prefix to "Container" whenever we create a child prefix, even without creating the ip addresses, the use of the precise parent inherits everything, getting 100% usage even without using all the ip addresses Parent prefix with container status ![image](https://github.com/netbox-community/netbox/assets/13603619/7029e8fc-f2ec-4ba3-a26d-b6a8d6aebe80) Parent prefix summary ![image](https://github.com/netbox-community/netbox/assets/13603619/9efe91f4-6fbc-4df7-b9fe-b5b63a171e02) Childs prefix details - 01 ![image](https://github.com/netbox-community/netbox/assets/13603619/f21a04a2-e5a5-4555-8286-1e7d00c9fbe1) Childs prefix details - 02 ![image](https://github.com/netbox-community/netbox/assets/13603619/6354eee4-7526-4405-b11b-03c935476337) ### Expected Behavior #### We hope that when we check the "Mark utilized" box increase the ip address utilization from current prefix and this utilization will reflect in the parent prefix ### Observed Behavior The use of ip addresses of child prefixes is not shown in the parent prefix in the percentage
adam closed this issue 2025-12-29 21:23:06 +01:00
Author
Owner

@jeremystretch commented on GitHub (Jun 10, 2024):

This is working as intended. If you'd like to propose modifying this behavior, which would be breaking for many use cases, please submit a feature request citing your justification.

@jeremystretch commented on GitHub (Jun 10, 2024): This is working as intended. If you'd like to propose modifying this behavior, which would be breaking for many use cases, please submit a [feature request](https://github.com/netbox-community/netbox/issues/new?assignees=&labels=type%3A+feature%2Cstatus%3A+needs+triage&projects=&template=feature_request.yaml) citing your justification.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#9814