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

Clarify utilization percentages for prefixes #1409

New Issue
Closed
opened 2025-12-29 16:32:03 +01:00 by adam · 4 comments
adam commented 2025-12-29 16:32:03 +01:00
Owner
Copy Link

Originally created by @Zimeon- on GitHub (Nov 17, 2017).

Issue type

[ ] Feature request
[X ] Bug report
[ ] Documentation

Environment

  • Python version: 2.7.5
  • NetBox version: v2.2.6

Description

When viewing a prefix, that has all IPv4 host addresses used, it still shows the prefix as not fully utilized. For example in a /26 subnet, with all 62 host addressed utilized, it shows the prefix as 96% full.

Would propose that the subnet utilization calculation to be changed, so that the broadcast and network addresses are not calculated when showing the subnet utilization.

Also regarding to https://github.com/digitalocean/netbox/issues/1669, when the block is full it will default back to network address. Perhaps remove the add ip-address option when a subnet is fully utilized from a host perspective. Imho any network stuff would be documented in the prefix, not in the network ip or broadcast ip.

Originally created by @Zimeon- on GitHub (Nov 17, 2017). ### Issue type [ ] Feature request <!-- An enhancement of existing functionality --> [X ] Bug report <!-- Unexpected or erroneous behavior --> [ ] Documentation <!-- A modification to the documentation --> ### Environment * Python version: 2.7.5 * NetBox version: v2.2.6 ### Description When viewing a prefix, that has all IPv4 host addresses used, it still shows the prefix as not fully utilized. For example in a /26 subnet, with all 62 host addressed utilized, it shows the prefix as 96% full. Would propose that the subnet utilization calculation to be changed, so that the broadcast and network addresses are not calculated when showing the subnet utilization. Also regarding to https://github.com/digitalocean/netbox/issues/1669, when the block is full it will default back to network address. Perhaps remove the add ip-address option when a subnet is fully utilized from a host perspective. Imho any network stuff would be documented in the prefix, not in the network ip or broadcast ip.
adam added the type: bug label 2025-12-29 16:32:03 +01:00
adam closed this issue 2025-12-29 16:32:03 +01:00
adam commented 2025-12-29 16:32:04 +01:00
Author
Owner
Copy Link

@dirtycajunrice commented on GitHub (Nov 20, 2017):

@Zimeon- I cannot reproduce this issue. Do you have "Is a pool" checked on that subnet?

@dirtycajunrice commented on GitHub (Nov 20, 2017): @Zimeon- I cannot reproduce this issue. Do you have "Is a pool" checked on that subnet?
adam commented 2025-12-29 16:32:04 +01:00
Author
Owner
Copy Link

@Zimeon- commented on GitHub (Nov 21, 2017):

https://imgur.com/BYrEk6c

An example from out view.

@Zimeon- commented on GitHub (Nov 21, 2017): https://imgur.com/BYrEk6c An example from out view.
adam commented 2025-12-29 16:32:04 +01:00
Author
Owner
Copy Link

@dirtycajunrice commented on GitHub (Nov 22, 2017):

Yes, this is the intended behavior when "is pool" is checked. It allows the allocation of broadcast and network IPs. If you uncheck "is pool" in that subnet's settings you will get your desired 100% utilization.

@dirtycajunrice commented on GitHub (Nov 22, 2017): Yes, this is the intended behavior when "is pool" is checked. It allows the allocation of broadcast and network IPs. If you uncheck "is pool" in that subnet's settings you will get your desired 100% utilization.
adam commented 2025-12-29 16:32:04 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Nov 22, 2017):

I've marked this as a bug because the way we show utilization right now isn't clear. The "utilization" attribute of the prefix view always lists the number of child IP addresses it contains, but the utilization percentage is calculated differently for container and non-container prefixes.

I've moved the IP count to the "IP addresses" tab at the top, and replaced the attribute with the utilization graph that's displayed in the prefixes list.

@jeremystretch commented on GitHub (Nov 22, 2017): I've marked this as a bug because the way we show utilization right now isn't clear. The "utilization" attribute of the prefix view always lists the number of child IP addresses it contains, but the utilization percentage is calculated differently for container and non-container prefixes. I've moved the IP count to the "IP addresses" tab at the top, and replaced the attribute with the utilization graph that's displayed in the prefixes list.
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: bug
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#1409
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?