Track. Automate. Configure.

Home About Features Community Develop
Download this project as a tar.gz file

IP Ranges -> Blocks


04-04-2012 06:37:02

Hey everybody,

can someone explain the 'blocks'-function? I don't know about the Usage.

Thanks, Ximil


04-04-2012 09:05:17

Blocks allow you to keep track of CIDR ranges as well as arbitrary ranges of IP address space.

Lets say you have route summarization that says is dedicated to your New York office. You can define a block to help describe that. Then within that CIDR range you may have several actual subnets defined. It can help you even audit/manage your route tables if you wanted to get crazy with it.

On the other side you could define a block that said was allocated for test database servers in the lab.

This is simply just a method to track non subnet related usages for IP space for reference. There is no configuration that is driven from this information (at this time).

When you are on a subnet, you will see block related information just below the subnet map so that you can have the quick reference to how this subnet relates to defined blocks.

Hope that helps.


10-04-2012 02:42:21

Okay, thanks.

If I understand you correctly, then it is a way to split IP addresses logically?

I am looking for a way to reserve IP addresses only for a certain subdomain that they can be awarded only in this subdomain.


10-04-2012 20:39:53

Yep you are correct. It is a way to track logical ranges of address space.

At the moment there is not a feature to associate address space with a domain or a security role. There are features in planning around that but they do not yet exist.


11-04-2012 05:33:52

And actually it's the same with the VLANs?

BTW: THANK YOU so much for your help!!! It's just for my understanding. :)


12-04-2012 08:53:30

Well no, VLANS are for a different purpose. Vlans in ONA should represent your vlans that actually exist in your environment. Typically a switch gets assigned several vlans with vlan numbers. Then one or more subnets are placed on each vlan. Sometimes if you are using VTP or other tech you would have what is called a campus or vlan domain. This is a grouping of vlans.

So ONA allows you to keep track of those vlans. There are currently only a few things within ONA that use the VLAN information directly outside of the informational tracking purposes. When you are using DHCP and have multiple subnets on a single vlan with a helper address you must define them as a "shared" network in the DHCP server config. You do this by defining the VLAN information in ONA. Secondly you can use this vlan information to help build VTP configuration for things like VMPS if you use that.

Hope that helps clear it up further.