Aggregates Question

[Jason Kopacko]

Am I doing something wrong?

If I create an aggregate for a physical site and then create a master prefix for that site, it shows fully consumed. (See the Aggregate-10.25.0.0-16.png file.)

If I delete the /16 prefix it shows similar to what the prefix overview shows.

I was assuming if the /16 prefix was created as a container, it would NOT show the aggregate 100% utilized.

Thanks,

Jason

[Brian Candler]

You're using Aggregate wrongly.  An Aggregate represents an allocation from an address provider - your ISP, or your LIR.

If you want to allocate address ranges to sites, create a Container Prefix for each site.  Containers can contain other containers, so this is fine.

If you have a /22 from your RIR, and you've got four sites and have created a /24 container for each one, then the Aggregate correctly shows 100% utilisation - you have no more address space left if you wanted to assign space to a fifth site.

Regards,

Brian.

[Jason Kopacko]

I realize that, from your perspective, it is wrongly. From my perspective and many others that I have introduced to NetBox...we all seemed to have the same question. Why does it show 100%? It should be showing based on IP assignment count. Whether we are looking at a specific site prefix or a collection of prefixes (aka the aggregate) the % usage could be the same or maybe broken out to show number of possible prefixes as well as total IP usage.

[Jeremy Stretch]

As Brian explained, it shows 100% utilization because the entire aggregate has been allocated. When you need to allocate more IP space, and you look at your list of aggregates, you can see that this one does not have any more space available.

--
You received this message because you are subscribed to the Google Groups "NetBox" group.
To unsubscribe from this group and stop receiving emails from it, send an email to netbox-discuss+unsubscribe@googlegroups.com.
To post to this group, send email to netbox-discuss@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/netbox-discuss/9391d105-0903-4221-95b7-d866acbc3b11%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

[Jason Kopacko]

I get that, but there isn't a page or summary that I can use to give me something similar to the attached example for prefixes. So aggregates is what we use.

On Wednesday, September 19, 2018 at 12:28:09 PM UTC-5, Jeremy Stretch wrote:

As Brian explained, it shows 100% utilization because the entire aggregate has been allocated. When you need to allocate more IP space, and you look at your list of aggregates, you can see that this one does not have any more space available.

On Wed, Sep 19, 2018 at 11:47 AM, Jason Kopacko <ja...@kopacko.com> wrote:

I realize that, from your perspective, it is wrongly. From my perspective and many others that I have introduced to NetBox...we all seemed to have the same question. Why does it show 100%? It should be showing based on IP assignment count. Whether we are looking at a specific site prefix or a collection of prefixes (aka the aggregate) the % usage could be the same or maybe broken out to show number of possible prefixes as well as total IP usage.

On Wednesday, September 19, 2018 at 3:02:44 AM UTC-5, Brian Candler wrote:

You're using Aggregate wrongly.  An Aggregate represents an allocation from an address provider - your ISP, or your LIR.

If you want to allocate address ranges to sites, create a Container Prefix for each site.  Containers can contain other containers, so this is fine.

If you have a /22 from your RIR, and you've got four sites and have created a /24 container for each one, then the Aggregate correctly shows 100% utilisation - you have no more address space left if you wanted to assign space to a fifth site.

Regards,

Brian.

--
You received this message because you are subscribed to the Google Groups "NetBox" group.

To unsubscribe from this group and stop receiving emails from it, send an email to netbox-discus...@googlegroups.com.
To post to this group, send email to netbox-...@googlegroups.com.

[Brian Candler]

Simply browse to "prefixes".  Your top-level container prefixes will be shown there, and each one will show its utilisation.

Let me repeat: aggregates are for tracking the utilisation of your RIR allocations.  What you have shown - 10.1.0.0/16, 10.2.0.0/16 etc - are container prefixes.

The correct way to use Netbox Aggregates here is to create a single aggregate for 10.0.0.0/8, and label it "RFC1918 (block A)".  The RIR is "IANA".  Then looking at this Aggregate, you can see how much private address space from this block you've assigned, and how much is still available.

[Ovidiu Pacuraru]

@Brian: thanks for the great explanations, I feel I understand aggregates more after reading your replies a couple of times. 

I'm just wondering if you could expand a bit on this sentence: 

What you have shown - 10.1.0.0/16, 10.2.0.0/16 etc - are container prefixes.

I'm wondering why you would use those as container prefixes vs active prefixes? 

Do you use them as container prefixes only if you want to further break down that range?

[Brian Candler]

On Tuesday, 25 September 2018 09:44:24 UTC+1, Ovidiu Pacuraru wrote:

I'm just wondering if you could expand a bit on this sentence: 

What you have shown - 10.1.0.0/16, 10.2.0.0/16 etc - are container prefixes.

I'm wondering why you would use those as container prefixes vs active prefixes? 

An active prefix is one which is actually configured on a network somewhere.

For example, if you have a device configured with address 10.1.0.123 netmask 255.255.255.0, then 10.1.0.0/24 is an active prefix.  An active prefix shouldn't contain any other prefixes, only individual addresses.

A container prefix is space which has been reserved for a particular purpose.  Parts of it may be other containers or active prefixes, and the remainder not yet assigned.