Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clarify utilization percentages for prefixes #1721

Closed
Zimeon- opened this issue Nov 17, 2017 · 4 comments
Closed

Clarify utilization percentages for prefixes #1721

Zimeon- opened this issue Nov 17, 2017 · 4 comments
Labels
type: bug A confirmed report of unexpected behavior in the application

Comments

@Zimeon-
Copy link

Zimeon- commented 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 #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.

@dirtycajunrice
Copy link
Contributor

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

@Zimeon-
Copy link
Author

Zimeon- commented Nov 21, 2017

https://imgur.com/BYrEk6c

An example from out view.

@dirtycajunrice
Copy link
Contributor

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.

@jeremystretch jeremystretch changed the title Addressspace utilization Clarify utilization percentages for prefixes Nov 22, 2017
@jeremystretch jeremystretch added type: bug A confirmed report of unexpected behavior in the application and removed awaiting reply labels Nov 22, 2017
@jeremystretch
Copy link
Member

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.

@lock lock bot locked as resolved and limited conversation to collaborators Jan 17, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
type: bug A confirmed report of unexpected behavior in the application
Projects
None yet
Development

No branches or pull requests

3 participants