In the context of NS1's Cloud-Managed DDI, a network in IPAM is a collection of IPv4 and IPv6 subnet trees. Networks essentially model private networks; therefore, they can contain subnets that overlap with other networks.
A subnet is any logical or physical subdivision of a network consisting of a collection of IP addresses that share the same IP prefix. The prefix is represented by the leading bits in an IP address. For example, the addresses
10.3.1.2 are in the subnet
10.3.0.0/20 sharing the same leading bits in a
/20 netmask. The netmask describes how many leading bits are fixed; thereby, determining the size or number of contiguous IP addresses in that subnet.
For DHCP to be able to assign a lease, it must be bound to an interface within the subnet. In other words, you must set up a static IP address on the server that is within the subnet (IP range) and then allow the container to use that interface. DHCP will automatically bind to it as long as it's there. For example, if a subnet is defined as
10.0.0.0/16, the interface should be
10.0.0.1 or similar.
You can use the NS1 Connect portal and the NS1 API to manage these subnets. This article describes how to use the NS1 Connect portal to perform management tasks via the portal. However, you can find links to the NS1 API below.
You may occasionally require information about IPAM objects (networks, subnets, and addresses), such as creation or last-modification timestamps, when subnets and addresses were issued, when they expired, and more. You can easily access this information by starting at the network level on the IPAM page and drilling down into the subnets and child addresses.
To move easily up and down the network architecture, use the breadcrumb navigation or the keyboard shortcuts:
H (or left arrow) to back out (from subnet to network)
L (or right arrow) to drill down (from network to subnet)
Select a network or subnet to view usage information and other metadata in the data panel.
The following images show the location of the data panel on the right side of the screen.
When creating a subnet, you should include descriptions for quick reference and search.
To configure overlapping IP space, you can create a second network that describes the overlap—physical or virtual. Specify a different ID for the network and name to use the same addresses without conflict.
Via the NS1 Connect portal:
Navigate to the IPAM page to view your list of Networks.
Drill down into your desired network by clicking its name or selecting it and pressing the > button or L or the → arrow key to view all subnets associated with the given network.
At any point, use the breadcrumb navigation (Networks | [Subnet Name]) if you are not sure where you are in the network hierarchy.
Click the + icon or press N to open the Create new subnet modal.
Complete the Create new subnet form. Add a prefix (in CIDR notation). You should also include a name and a brief description of the subnet to make it easier to locate and understand the purpose of the subnet in the future.
The prefix is auto-populated based on the currently selected object. For example, if you choose the 10.3.0.0/20 subnet, the 10.3.0.0 prefix is populated in the Prefix field.
Click Submit. The new subnet appears in the list.
Select the new subnet from the list to view its associated metadata and usage in the data panel.
You can adjust some of the metadata fields of a subnet (including its name, description, status, and tags) from the Metadata tab. You must update the subnet status to assigned before adding it to a scope group.
You can merge subnets that share the same netmask and penultimate bit. The result must equal a valid subnet in CIDR notation. You can merge assigned subnets, but you cannot merge a mixture of planned and assigned subnets.
On the Subnets page, click Select and select the subnets you want to merge.
From the Actions menu, select Merge Selected, then click Merge in the Merge Subnets modal.
When you re-parent a subnet, you reassign the subnet and each child address to a new prefix.
Some important notes about re-parenting subnets:
You cannot re-parent a larger subnet into a smaller subnet.
You can re-parent across networks.
The corresponding record's answer will be updated accordingly if a re-parented address is associated with a forward DNS zone.
If a re-parented address is associated with a reverse DNS zone:
A new PTR record will be created if the new address falls within a zone.
A new reverse zone and PTR record will be created if the new address doesn't fall within the zone.
To re-parent a subnet:
Open the network that contains the subnet that you want to re-parent.
Click the vertical ellipsis menu to the right of the subnet you want to re-parent, then click Reparent Prefix.
Complete the Reparent Prefix modal. You can specify an existing parent in one of the existing networks, or you can create a new parent. Click Next and confirm your choice on the next screen before clicking Save.
This process may take some time. You may leave the page that contains the subnet that you are reassigning.
To delete a single subnet:
Click the vertical ellipsis menu to the right of the subnet you want to delete.
To delete multiple subnets:
Click Select above the subnet list, then select the networks or subnets you want to delete.
From the Actions menu, select Delete Selected.
When prompted, confirm that you want to delete the selected subnets.