Device42 IPAM

Built for accurate network visibility and safer change planning, Device42 IPAM(IP Address Management) helps teams discover, document, and manage IP address space across subnets and VLANs. By moving away from manual tracking, you can prevent IP conflicts, reclaim unused ranges, and keep DNS/DHCP alignment clean across on-prem and hybrid environments.

Why teams choose this series

• Automated IP Discovery: Populate IP usage from scans and discovery jobs instead of relying on manual spreadsheets.
• Conflict Prevention: Track used, free, and reserved IPs to reduce outages caused by duplicate assignments.
• Subnet & VLAN Organization: Model networks logically so teams can plan expansions and segmentations with confidence.
• DNS/DHCP Visibility: Maintain cleaner alignment between addressing, naming, and provisioning workflows.
• CMDB Context: Link IPs to devices, racks, and applications so operations can answer “who owns this IP?” immediately.

Device42 IPAM: At a Glance

• What it is: Integrated IP Address Management to track subnets, IP usage, and assignments inside Device42.
• Best For: Reducing IP conflicts, speeding up provisioning, reclaiming unused ranges, and creating audit-ready documentation.
• Licensing Model: Annual subscription based on Device42 licensing units (Core device count + enabled modules).
• Activation: Upload & apply a .lic file in the Device42 UI (Tools → Settings → Licensing).
• Required Data: Device count (Core), rough number of subnets/VLANs, discovery sources, and DNS/DHCP integration needs.

License Overview

The Device42 IPAM license is an annual subscription that activates your purchased modules and defines the capacity your instance can manage.

How it works : Device42 is generally licensed by a Core device count (since devices are the primary IP-addressed items). IPAM capabilities are unlocked as part of this subscription level. After purchase, you receive a .lic license file. You simply apply it in the UI (Tools → Settings → Licensing → Upload & Apply) to activate the features.

Sizing & Operations : The main sizing input is your Core device count (current + growth), as this determines the scale of discovery and CMDB coverage IPAM relies on. Success comes down to enabling IPAM workflows where they matter most: core subnets and VLANs, high-change environments (like VMware or cloud clusters), and areas prone to conflicts.

Note for controlled networks: The license file workflow is fully compatible with offline processes since activation is performed locally in the UI.

Product Overview

Device42 IPAM replaces spreadsheet-driven IP tracking with a discoverable, queryable system of record—linking subnets and addresses to real devices, interfaces, and owners.

Core Technical Flow

1. Define Address Space: Model subnets/VLANs and reserved ranges so IP planning starts from a clean structure.
2. Discover Usage: Run discovery jobs/scans to populate IP status (used/free/reserved) and link IPs to interfaces.
3. Track Ownership: Maintain assignment context so teams can answer “what is this IP?” and “who changed it?”
4. Align with Operations: Use views to identify free blocks, reclaim unused ranges, and support new provisioning.
5. Reduce Change Risk: Use dependency context from the CMDB to reduce mistakes when moving services or expanding networks.

Operational Outcomes

• Fewer IP Conflicts: Faster root cause analysis during incidents.
• Cleaner Planning: Know exactly what is free vs. what is truly unused.
• Better Alignment: Shared ownership context between network, systems, and app teams.

Ordering Guide and Pricing

Ordering Device42 IPAM is mainly driven by your Core device count and the scope of your discovery coverage (data centers, branches, cloud VPC/VNETs). Since IPAM value relies on accurate mapping, best results come when paired with reliable discovery sources.

Pricing Factors:

• Term: Subscription duration (annual / multi-year).
• Capacity: Core device count / licensing units.
• Scope: Discovery depth and integrations planned.
• Constraints: Support level and deployment needs.\

Quick Guidance

• Know your specs? We can size the subscription quickly based on device count and sites.
• Unsure? Write “Help me choose” and tell us your network size, biggest pain (conflicts vs. auditing), and where addressing changes most frequently.

Activation Guide For Device42 IPAM

Device42 IPAM supports straightforward activation for both connected and controlled environments via a simple file upload.

Connected / Online Activation

1. Receive .lic file.
2. Navigate to Tools → Settings → Licensing.
3. Click Upload & Apply.
4. Features enabled and compliance maintained.

Controlled / Offline Activation

1. Receive .lic file via approved channel.
2. Transfer to the isolated admin workstation.
3. Navigate to Tools → Settings → Licensing.
4. Click Upload & Apply.
5. Compliance maintained (no outbound internet required).