IP Addresses in the Device42 database must be unique per VRF group. So, you can have two subnets with overlapping IP ranges as long as they are in different VRF groups. The only issue with overlapping subnet ranges is that autodiscovery and import will add or modify the IP into first subnet it finds in the list.
IP Address List Page
The list page shows IPv4 and IPv6 addresses that you can sort by any field. You can also filter by type, availability, updated time stamp, subnet, VRF group, and tags.
You can search for IPs with full or partial entries right here. Clicking on an IP takes you to the view page.
Bulk Actions for IP Addresses
The following bulk actions are available for IP addresses:
Export selected items to CSV: create CSV export file.
Delete with Detailed Confirmation: Displays prompt before deleting.
Fast Background Delete: Delete without prompt.
Mark selected IP as available: Will only mark those IPs available that have no device association.
Mark selected IPs as not available : Will mark selected IPs as not available.
Clear ALL fields and Mark selected IPs as available : This command will clear all device association for the selected IPs and mark those IPs as available.
Relocate Selected IPs : This will bring up a matching subnets page based on first selected IPs. You can choose to move IPs to another subnet with this. Only IPs that are within the range will be moved.
Do a re-importable export for selected items: Create an export file that you can re-import.
Add tags to selected items: add a comma-separated list of tags.
Check/Fix selected IPs Subnet assignment: Displays a page to check or fix Subnet assignment.
View IP Address Page
Click on an IP address to view its page.
The view IP page shows the details for an IP and you can see the history of changes for that IP from the History (Audit Logs) button (similar to all other view pages in the application). If you have appropriate permissions, you will see the Edit button to edit. All DNS records that use this IP are shown in the view page as well.
Note: Entries in the Configuration Resource and Configuration Resource Item fields make sense only in the context of a Kubernetes cloud discovery job (https://docs.device42.com/auto-discovery/cloud-auto-discovery/) and are filled in automatically. These field should not be populated for a regular IP address.
In the example above, the Configuration Resource link will take you to the K8s cluster that is currently holding that IP, and Configuation Resource Item contains the name and type of resource. In this case, the name is Tiller-….jkfpl and the resource type is a pod.
Click the Add IP Address button on the view page to add an IP address.
When Adding or editing an IP, the Subnet field is required. Device42 will automatically check if the IP falls within the allowed IP range in the subnet and will not allow duplicate IP to be added in that VRF group or subnet (if not a VRF group). You can choose an existing Device and Port or add a new ones from this page.
Select Network > DNS Records from the main menu to can add DNS A/AAAA records for the IP and they will be updated on the IP address.
IP Address Management from the Command Line
With Device42, you can find if an IP is already in a D42 instance, suggest a next available IP and add an IP from the command line using the REST APIs. Here is a post discussing this: https://www.device42.com/blog/2013/03/ip-address-management-from-the-command-line/