The flow of address management is based on the creation of areas, then ranges which belong to areas, and finally, subnets which belong to ranges. Actually, only subnets are required, but on large networks it makes logical sense to group the network into areas to ease administration and to reduce routing updates on the network. There is a jpeg drawing included with the distribution that graphically shows these relationships. The methodology employed borrows significantly from OSPF routing concepts which are explained more fully here.
So in a new installation, first create the areas, then create ranges adding them to areas, and finally create subnets. Searching is now a simple matter of selecting an area which will display all the ranges for the area, or selecting no area and simply selecting a range from the total list of ranges, or simply selecting a base network address.
Within a customer or autonomous system, no overlaps of address space is allowed. This follows standard IP addressing rules. You can have overlapping ranges/aggregates, but the default behaviour of ranges also prevents overlaps. This can be changed in the config.php file.
To handle challenges like NAT or other overlapping address space, you will be required to create multiple autonomous systems. See 'Searching' below how to see information across multiple autonomous systems.
IP address records can be linked together. This allows one address or multiple addresses to reference another address or addresses. Using this feature allows for the referencing of NATed addresses or having a link to a loopback address of a device. Linking is done on the IP address details page by completing the "Linked address" field. Once the field is completed, you can follow the link. The link also appears on subnet summary pages.
You can also link many addresses in one go by choosing multiple addresses in the "Select multiple addresses to do a bulk change" window, then completing the "User" field as follows:
The LNK identifier must be in uppercase, followed by exactly one valid IP address with no spaces, then followed by an optional space and user description. After the page is submitted, the embedded LNK will vanish.
If the destination record of a linked address does not exist, a record will automatically get created pointing back to the source address, but only if the destination subnet exists. This is to signal the "Find Next Free" address logic of the subnet that the destination address is used.