Orion IPAM 1.7 is right around the corner, which has a couple of really cool features we want to tell you about. First, as usual, you asked for it, so you shall receive: Cisco DHCP. Yes, now you can add Cisco DHCP servers and their corresponding scopes to IPAM. Let’s take a look. You’ll add a Cisco DHCP server in the same way you add Microsoft DHCP servers.
From the DHCP Scope Monitoring tab, select ‘Add New,’ then ‘DHCP Server.’ From here you’ll be given a list of devices.
From this list it’s easiest to sort by Vendor, then expand the list of devices under Cisco. Here, we’re going to add Tok-2621.aus.lab, which is one the Cisco DHCP servers in our lab. The next step will be to provide credentials for the DHCP server. See screenshot below.
For Cisco DHCP servers, you’ll select ‘CLI Credential’ (vs. Windows). You can use an existing set of credentials, or you can create new credentials. Here we’ve created a new set of credentials for Tok-2621.aus.lab. We’ve specified Telnet as the protocol on Port 23, and we’ve successfully tested our credentials against the DHCP server, and IPAM found seven scopes on the server. Once credentials have been added, click ‘Add DHCP’ at the bottom of the page. You should now be able to see this server on the DHCP Scope Monitoring tab.
Here we can see the server has been added, and IPAM is actively looking for scopes. Once added, the scopes will appear under the Scopes subtab above.
The next feature we want to highlight is something we call Indirect Discovery. If ICMP and/or SNMP is disabled on a particular subnet, IPAM can’t get an accurate status on the IPs in that subnet; however, Indirect Discovery solves that problem. Indirect Discovery works by specifying a ‘neighbor’ device that has up to date ARP tables, which gives IPAM an accurate status on the IPs in that subnet. Let’s take a look at how to configure Indirect Discovery in IPAM.
From the Manage Subnets & IP Addresses tab, select a subnet then click Properties. This will open up the Edit Subnet Properties dialogue in the screenshot below.
Here you’ll notice a new section titled ‘Neighbor Scanning.’ In this section you’ll specify the IP address of a neighbor device (in other words, a high traffic device on the subnet), and the scan interval. In the scenario where ICMP and/or SNMP is blocked on that subnet, IPAM should now get an accurate status on the IPs in that subnet.
As I stated at the beginning of the post, IPAM 1.7 will be out very, very soon. We hope you like the new features (you specifically asked for them!); let us know what you think.