We performed a comparison between Device42 and Infoblox IPAM based on real PeerSpot user reviews.
Find out in this report how the two IP Address Management (IPAM) Tools solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."The solution's agentless approach to asset discovery is very important for us because installing agents on physical or virtual devices is not easy in our company. We have to escalate these kinds of things to different levels of security. Not having to install agents makes it easy for us."
"The solution is agentless."
"The import/export for bulk operations is a valuable and good feature."
"The REST API abilities enables us to run scripts that pull information from our servers about software, storage, etc. Anything we need is pushed through REST API to the Device42 server and reflected in the report it generates."
"It has agentless discovery; you don't need to put agents on your servers. You can open one or two ports to discover all your infrastructure."
"I like the tool's agentless discovery feature. The tool configures the devices based on the documentation provided. I am also impressed with its auto-discovery feature. The tool also keeps on tracking and finds whatever is in the environment."
"One of the most valuable features in my experience is the precise tracking of hardware devices and their locations registered in the solution. The solution allows to determine the exact placement of assets based on the building maps and the room details. This feature has allowed us to gain upper hand on the customers and provide them with a great satisfaction because they can visually see the arrangement of their assets within the organisation or building."
"The Insights+ component is useful for us because it does business application mapping and helps us visualize it. It saves us time because we don't have to hunt for data."
"Infoblox IPAM provides visibility into what's on your network and helps fingerprint devices based on the OS, manufacturer, and other things along those lines."
"Regarding DDI, I would say the best feature of Infoblox is the DNS security. DNS tunneling is a significant security issue and is very difficult to protect against based on our tests with other types of security devices. However, Infoblox eliminates this issue and provides excellent security against a difficult threat."
"IPAM's best features include the view of how many soft nets are filled from your container and the grid master."
"The features we found the most valuable were being able to handle DHCP scopes and handing out DHCP leases. We weren't doing some of the things that we can do, such as DNS query rate limiting. Our usage was pretty standard. We wanted to be able to track our IP addresses to create DNS entries and then create DHCP and manage DHCP scopes. We used the standard features the most."
"The most important feature of Infoblox IPAM for my clients is its reliability."
"Infoblox gives us the flexibility to manage our internal networks and publish the data outside of the network on the internet. It's quite fluid to do it."
"Before IPAM (IP Address Management) came into the picture, every user had to depend on an Active Directory engineer to get an IP assigned. With Infoblox IPAM, there's automation or auto assignment of IP addresses which is a valuable feature. There's also the capability of storing many networks in one place through the solution. Infoblox IPAM solved the major issue of needing an Active Directory engineer to assign an IP."
"This is a DDI solution and having one management control has been most useful."
"The breadth and depth of the solution's discovery of IT asset information means the system does most of the work, but they need to work on improving the database discovery part, especially for Oracle Exadata."
"If I want to delete an asset from a cabinet it does take a while. And if I'm doing it in bulk — say, for example, if we have one cabinet that has 20 servers in — if I want to remove all 20 servers, I have to do them individually, which is a bit time-consuming. If there were a way that I could just bulk-remove everything from there, that would definitely save some time."
"The dependency mapping can be quite slow sometimes, if you've got a lot of things connecting to services. It can be very slow to build up the map."
"The architecture is a bit old-fashioned. Device42 is on one server, appliance, virtual machine, or guest. We are loading more into Device42 than it can hold. Overloading Device42 with REST API calls or tasks will directly impact every aspect because the server will be too busy to answer requests."
"The reporting could be better. The Insights+ component is an improvement, but they even admit it isn't the greatest. The documentation on their website could also be improved, but Device42 is constantly changing, so the documentation would have to change almost daily."
"Mapping items wasn't as intuitive as importing in Device42, so this is an area for improvement."
"Device42 is a main part of our processes. We need reliability, not only in terms of the data but with the solution itself. It's really difficult when we have 10 minutes of Device42 downtime because none of our teams can work for those 10 minutes, and it's more time lost if there is longer downtime. An improvement would be to have a cluster implementation of Device42 to have high-availability and ensure that we don't have downtime in case of failure."
"In my experience I believe that the key concern is the pricing strategy of the solution. Instead other solutions such as lanweber are much more cost effective. Previously, Device42 operated on perpetualysis without any fees. But recently they have altered the pricing model to include a subscription fee which I see as a very costly affair. Therefore I would like to suggest that they evaluate their pricing strategy and licence scheme, conduct a market research and ensure that they provide the right product in the market at the right price."
"How you track IPs within a subnet and how all of that works was not intuitive to me. If I compare it to VitalQIP, I create a subnet, and it's a slash 24 size. It's very easy. I look, and here are my 254 IPs. I can then see if I have assigned a static, do I have a DHCP scope, and what's the name of the device. That's all there in front of me. The thing that I found frustrating with Infoblox was that it was not very intuitive."
"An area for improvement is IPAM's smart folders, which can be slow to access and would benefit from a search feature."
"Infoblox IPAM has improved and is better, but it needs to have an external GSLB functionality. Currently, the solution has a GLSB functionality for internal appliances, but for an external user, that functionality doesn't exist. Infoblox IPAM also needs some improvement on its threat engine and RPZ policies, or DNS firewall or DNS policies. An additional feature I'd like to see in Infoblox IPAM is zero-touch provisioning in terms of the appliances. Currently, there's zero-touch provisioning for cloud-based devices, but for physical appliances in branches, there's none, so you still have to do some configurations. For example, if you have existing DNS infrastructure and you need to set up Infoblox IPAM in new branches, and you need more appliances, you should be able to just plug the solution into the network, and there shouldn't be any manual interference required."
"The marketing of the solution could improve to give customers the awareness of the benefits."
"CLI needs to be user-friendly. There should be an option to commit changes."
"Infoblox IPAM could improve some of the features. The market is demanding for some features that are not there, but there is always a reason why it's not there. At the moment, the solution is rather complete for what it's used for. It can always extend to solve some other issues that are linked to it, but the solution itself is complete."
"It is challenging to find training tutorials online."
"The only room for improvement in Infoblox IPAM is its compatibility and flexibility with IPv6. There's been an issue transitioning from IPv4 to IPv6, and though Infoblox is in the process of resolving the issue, it would be better if the team could come up with a solution in a quicker timeframe. Better transitioning from IPv4 to IPv6 is what I'd like to see in the next release of the solution."
Device42 is ranked 4th in IP Address Management (IPAM) Tools with 25 reviews while Infoblox IPAM is ranked 1st in IP Address Management (IPAM) Tools with 15 reviews. Device42 is rated 8.4, while Infoblox IPAM is rated 9.0. The top reviewer of Device42 writes "Good reporting and discovery capabilities, and helpful for understanding device dependencies and asset management". On the other hand, the top reviewer of Infoblox IPAM writes "Plug-and-play, stable, scalable, and lets you manage everything from the cloud; has professional technical support". Device42 is most compared with ServiceNow, ServiceNow CMDB, JIRA Service Management, BMC Helix Discovery and NetBox.dev, whereas Infoblox IPAM is most compared with SolarWinds IPAM, BlueCat Integrity, BT Diamond IP, NetBox.dev and ManageEngine OpUtils. See our Device42 vs. Infoblox IPAM report.
See our list of best IP Address Management (IPAM) Tools vendors.
We monitor all IP Address Management (IPAM) Tools reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.