-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
Comments
@Zimeon- I cannot reproduce this issue. Do you have "Is a pool" checked on that subnet? |
An example from out view. |
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. |
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. |
Issue type
[ ] Feature request
[X ] Bug report
[ ] Documentation
Environment
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.
The text was updated successfully, but these errors were encountered: