IP Assignments & Sonar
Written by Mitchell Ivany
Updated at March 15th, 2025
- Our Products & Services
- Getting Started
- Accounts
- Communication
- Billing
- Companies
- Financial
- Integrations
- Inventory
- Jobs
- Mapping
- Misc.
- Monitoring
- Purchase Orders
- Release Notes
- Sonar Billing
- Voice
- Reporting
- Security
- sonarPay
- Ticketing
- Working With the Sonar Team & Additional Resources
- System
- Networking
Table of Contents
There are three main approaches in marrying Sonar to the IP assignments within your network. They are as follows:
Have Sonar IPAM act as the DHCP Server
In this approach, when an IP assignment takes place in Sonar, a static lease is triggered from Sonar to your DHCP server (or RADIUS server, LTE management platform, etc.) All management is controlled directly within Sonar.
| Advantages | Disadvantages |
|
|
Steps and Relevant Articles
- Setup IPAM
- Integrate with Server
Have the Assignment From the Server Come Into Sonar
In this approach, assignment happening from the server to a device causes the server to also send a copy of that assignment information either directly in Sonar, or in some cases to a DHCP batcher.
| Advantages | Disadvantages |
|
|
Steps and Relevant Articles
- Setup IPAM
- Integrate with the Server
Set the IP Assignment Statically in the Device and Use Sonar as the IPAM Record
In this approach, Sonar and the device do not interface at all. Sonar is merely a place to keep a statement of record.
| Advantages | Disadvantages |
|
|
It is common practice to statically assign infrastructural devices on most network sites. It makes sense to keep this information in Sonar and have the full IPAM record live here.