In this post I will cover the infrastructure that I put together in order to create an IPAM test lab. This is only to try out some of the more simple things that this feature has. More VMs can be added if you want to expand your testing.
In short I made 2 domain controllers each in its own site and with its own subnet. Both domain controllers have the DNS role installed but only one has DHCP at first. For linking the 2 sites I installed a virtual machine with Linux that has the purpose of passing traffic from one network to the other. IPAM is installed on a server found in the first Active Directory site. In order to test the allocation of IPs I used 2 machines, one in each site. At first I joined only the first one to the domain (the one that has the DHCP server in its site). All Windows systems have Windows Server 2016 installed. Here is a diagram of my IPAM test lab:
In order to make this work you will also need to create 2 private switches. I have a series that explains everything about creating a test lab including making a VM act as a router. Here is the link to the articles.
And here is how the virtual machines for the IPAM test lab look in Hyper-V. All VMs except the router have Windows Server 2016 installed:
Let’s see how each VM is configured.
Router is a Linux box with 2 NICs that has IP forward activated so traffic can pass through it. Info about installing and configuring it can be found in the link above.
IPAM-DC1 is the first domain controller in the Active Directory domain. I placed it in the HQ AD site and installed DNS and DHCP on it. For some time it will be the only DHCP server in the infrastructure so I also created a scope for 192.168.1.0 with the range between 192.168.1.20 and 192.168.1.100.
IPAM-DC2 is the second domain controller. For now we will install only DNS as an extra role on it and place it in a second site with the 192.168.2.0/24 subnet.
IPAM-SRV1 is the server on which we will install the IPAM feature.
IPAM-CLIENT1 is just a machine that I use to obtain an IP address from the DHCP server. I placed it in the 192.168.1.0 network and joined it to the domain. It does not matter what OS you install on it.
IPAM-CLIENT2 will be joined to the domain at a later time after IPAM-DC2 will have the DHCP role. For now just install it and set the NIC to be part of the 192.168.2.0 network. The OS is also not important.
Now that we covered the IPAM test lab infrastructure we can begin installing and configuring it.