SolarWinds IP Address Manager 2.0 is officially here. Here is a link to the Release Notes. Below is a quick overview of some of the cool new features now available.

1. Standalone

IPAM no longer needs NPM. A lot of our customers enjoy the benefits of running IPAM and NPM side by side. For those of you who like the single pane of glass, nothing changes. For people who are interested in more complex deployment scenarios or only need an IP Management solution, you can purchase and install IPAM on its own server.

If you want to install IPAM 2.0 on the same server as NPM, you will need to be running the latest version of NPM, 10.1.2. If you have additional polling engines or websites, those servers will need to be upgraded to the latest version of NPM as well.

2. Historical Tracking

Want to know who had a specific address from a week ago? Maybe you have a NetFlow log with an IP of suspicious traffic but no hostname, or another product with a security event for an address at a certain time; simply search for the IP address and click View Assignment History to find out who (hostname or MAC address) had that address at that time .







Or, for full details about an address, click the View Details button (available on the search results page and Subnet Management page). This is a new view in IPAM 2.0 and gives you all the information you need to know about a specific IP address.



3. IPv6 Planning

Heard about the depletion of the IANA Free Pool and don’t know how that will impact you? Get informed and make a plan. With the new features in IPAM 2.0, you can create IPv6 address plans to deploy address schemes that make sense for your network. Whether you already have your global prefix or if you just need to get more  familiar with working in Hex instead of Decimal, we’ve got the tools to help you get started. Some customers will establish multiple subnets below one global prefix while others will carve out their address space using some of the bits for creating a hierarchy that include sites then subnets - either way, we’ve got you covered.



Here are the dialog boxes to add a Global Prefix, then a Site (optional), then a Subnet. In this example, I created a global prefix of 2001:DB80 /32 and added a site for State (Texas 2001:DB80:A000 /36) and used another site for City (Austin 2001:DB80:AA00 /40) and a final subnet for my specific building (2001:DB80:AAA0 /44). This is just an arbitrary example and not a recommendation on  how you should design your address plan. Although it would be good to consider staying on nibble boundaries (single characters, 4 bits) when creating these hierarchies (unless you just really enjoy doing binary math and in general making everyone’s life difficult Smile ).





For a great source of information on IPv6 deployment planning, see this slide deck by Shannon McFarland from Cisco.

4. Duplicate Subnets

Some customers want to be able to  manage overlapping or duplicate subnets (for example, MSPs managing customers who are each using the 10 /8 network). For customers who do not need to manage environments with overlapping addresses, we’ve introduced a new setting to allow you to turn off duplicate subnets. For new installs, duplicate subnets are disabled by default, for customers upgrading from a previous version of IPAM, you need to change this setting. For more information, see my previous blog post SNEAK PEAK–IPAM 2.0 and Duplicate Subnets.

5. UI Tweaks and Search

There are several other fixes and UI tweaks. For example, we removed the redundant tabs from the management page and added search to more places.

Before and After



Want more? Go What we are working on post IPAM 2.0 what we are already hard at work on next to make your job (life?) easier.