starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-13 13:53:31 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

prefix status : assigned #598

New Issue
Closed
opened 2025-12-29 16:23:41 +01:00 by adam · 3 comments
adam commented 2025-12-29 16:23:41 +01:00
Owner
Copy Link

Originally created by @moolinet on GitHub (Jan 2, 2017).

  • Problem description:
    When assigning a range to a customer I'm not interested in knowing how the IP addresses will be used. I just need to know that whom that range has been assigned to.
    I could use the existing "active" status for this but this will not help for capacity planning as netbox still believes all IP addresses are free.

  • Improvement request:
    It would be usefull to be able to add a "assigned" status to a prefix and then mark the prefix as fully used. this would allow to correctly calculate actual available ip space.

  • Alternatively:
    When looking at the aggregate summary I see an utilization percentage corresponding to how much ip space has been allocated within an aggregate.
    It would be practical to show the same utilization percentage at a container level (based on prefix assignation and not on IP reservation)

Thanks

Originally created by @moolinet on GitHub (Jan 2, 2017). * Problem description: When assigning a range to a customer I'm not interested in knowing how the IP addresses will be used. I just need to know that whom that range has been assigned to. I could use the existing "active" status for this but this will not help for capacity planning as netbox still believes all IP addresses are free. * Improvement request: It would be usefull to be able to add a "assigned" status to a prefix and then mark the prefix as fully used. this would allow to correctly calculate actual available ip space. * Alternatively: When looking at the aggregate summary I see an utilization percentage corresponding to how much ip space has been allocated within an aggregate. It would be practical to show the same utilization percentage at a container level (based on prefix assignation and not on IP reservation) Thanks
adam added the status: duplicate label 2025-12-29 16:23:41 +01:00
adam closed this issue 2025-12-29 16:23:41 +01:00
adam commented 2025-12-29 16:23:42 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jan 3, 2017):

I think you may be confusing the prefix and address objects. A prefix represents a network; an IP address is an individual address. NetBox tracks each independently. Both objects can be assigned a status of "active," which indicates that they are in use.

If you're assigning prefixes (networks) to customers and don't care about the usage of individual addresses within those prefixes, then there's no need to track them. Just look at the prefix utilization under its aggregates or a parent prefix. Does that make sense?

@jeremystretch commented on GitHub (Jan 3, 2017): I think you may be confusing the prefix and address objects. A prefix represents a network; an IP address is an individual address. NetBox tracks each independently. Both objects can be assigned a status of "active," which indicates that they are in use. If you're assigning prefixes (networks) to customers and don't care about the usage of individual addresses within those prefixes, then there's no need to track them. Just look at the prefix utilization under its aggregates or a parent prefix. Does that make sense?
adam commented 2025-12-29 16:23:43 +01:00
Author
Owner
Copy Link

@moolinet commented on GitHub (Jan 3, 2017):

If you can display the prefix utilization then everything is fine!
But I can't find it.
The only place where I see utilization is at the aggregate level.

I'm using a freshly deployed NetBox via docker install
the web site tells me it's version 1.7.3
(I just saw you bumped version to 1.8 but I don't know how to upgrade
the docker install)

On 03.01.2017 16:25, Jeremy Stretch wrote:

I think you may be confusing the prefix and address objects. A prefix
represents a network; an IP address is an individual address. NetBox
tracks each independently. Both objects can be assigned a status of
"active," which indicates that they are in use.

If you're assigning prefixes (networks) to customers and don't care
about the usage of individual addresses within those prefixes, then
there's no need to track them. Just look at the prefix utilization
under its aggregates or a parent prefix. Does that make sense?

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/digitalocean/netbox/issues/762#issuecomment-270138894,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AXue76ql2CXNakWn6lM-axkz_eQ1Ceegks5rOmhYgaJpZM4LZIot.

@moolinet commented on GitHub (Jan 3, 2017): If you can display the prefix utilization then everything is fine! But I can't find it. The only place where I see utilization is at the aggregate level. I'm using a freshly deployed NetBox via docker install the web site tells me it's version 1.7.3 (I just saw you bumped version to 1.8 but I don't know how to upgrade the docker install) On 03.01.2017 16:25, Jeremy Stretch wrote: > > I think you may be confusing the prefix and address objects. A prefix > represents a network; an IP address is an individual address. NetBox > tracks each independently. Both objects can be assigned a status of > "active," which indicates that they are in use. > > If you're assigning prefixes (networks) to customers and don't care > about the usage of individual addresses within those prefixes, then > there's no need to track them. Just look at the prefix utilization > under its aggregates or a parent prefix. Does that make sense? > > — > You are receiving this because you authored the thread. > Reply to this email directly, view it on GitHub > <https://github.com/digitalocean/netbox/issues/762#issuecomment-270138894>, > or mute the thread > <https://github.com/notifications/unsubscribe-auth/AXue76ql2CXNakWn6lM-axkz_eQ1Ceegks5rOmhYgaJpZM4LZIot>. >
adam commented 2025-12-29 16:23:43 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jan 3, 2017):

Sounds like a duplicate of #237 then. Please add any other comments/suggestion you have regarding this feature there. Thanks.

@jeremystretch commented on GitHub (Jan 3, 2017): Sounds like a duplicate of #237 then. Please add any other comments/suggestion you have regarding this feature there. Thanks.
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 status: duplicate
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#598
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?