Share your experience using Cygna Diamond IP Platform

Infoblox IPAM is used primarily in the banking sector, where policies and requirements take time to implement. The deployment timeline also depends on how many services have been adopted, whether organizations are using only DNS, all three DDI solutions, or BloxOne as well.

Infoblox IPAM's integration with DNS and DHCP helps me streamline my network operations as an internal process. It is automatically connected with DHCP, and IPAM is internally connected with DHCP.

I utilize the automated IP address discovery feature with Infoblox IPAM, which is called Network Discovery. For Network Discovery, it actually helps with workflow because we have to configure the seed routers, then SNMP credentials, then CLI credentials. There are different ways to configure the different types of devices, such as devices in firewalls, devices in SDN elements, and devices connected with a switch. There are multiple ways to discover the devices.

For the valuable insights I have gained from Infoblox IPAM's real-time visibility and analytics, we have to set the SNMP polling. For the discovery, it may take approximately 24 hours to fetch all the details and get all the updates, including all discovered devices and their fetched details.

Since Infoblox IPAM fulfills the requirement of the customer currently, in my perspective, there is no additional information that could be improved about Infoblox IPAM. However, in future updates of IPAM, I would like to see features such as more customization and better AI functionality.

I have been integrating Infoblox IPAM for two and a half years.

I am overall satisfied with Infoblox support. I have been working with Infoblox for approximately 2.5 years, and I appreciate Infoblox TAC support. They are very supportive and patient persons, which is why I very much appreciate the Infoblox TAC support.

Usually, how many people from my side take part in the deployment process depends on the situation, but at the time I am the only person who will be deploying Infoblox DDI on one client. If I want help, my colleague will help me and join me for the implementation.

I am not using Infoblox IPAM directly. I am currently working for a partner and have implemented Infoblox in various different customers. As an implementer, I can tell you that deployment of Infoblox IPAM is quite a step forward. There is no issue while deploying the device or any services on the members. It usually takes approximately one year to deploy it because it depends on the banking sector. I use the threat intelligence feature with Infoblox IPAM for DNS perspective. The review rating for this product is 7.5 out of 10.

I primarily use Device42 for migration opportunities where workloads have been running in the on-premise data center. Before migration, I need to ensure that I discover everything running in the on-premise data center. I started using it as an assessment tool to explore workload discovery of on-premise data centers, virtual machines, and resources.

One specific project where Device42 helped with workload discovery and assessment was when I was using other assessment tools. In one workload assessment opportunity, the customer was explicitly looking for application-level assessment, which could not be met by other third-party tools at the time. I was really impressed by the workload discovery of applications discovered by Device42. I started using it for application discovery, including the infrastructure discovery of the complete workload.

I started using Device42 because I needed a robust migration plan to ensure that I was not left with any dependency during assessment, since assessment plays a vital role in determining the number of move groups required. During move group planning, I cannot leave any system that is critically dependent on another system in the on-premise environment during migration. To be cautious of workload discovery, Device42 provides more granularity toward ensuring that the number of systems parked in the move group are safe to migrate without leaving any dependency.

Device42 offers the best features for workload assessment, particularly useful for cloud-to-cloud workload or on-premise data center workload, especially when planning for workload migration to the public cloud.

For application and infrastructure discovery, Device42 has enabled me to know the number of machines running in the on-premise environment and has managed to capture complete utilization metrics or trends of their utilization. This has benefited me in right-sizing systems for my public cloud total cost of ownership (TCO) planning, providing me granularity to right-size these systems while planning a migration to the public cloud.

Device42 has positively impacted my organization by providing granularity toward application discovery compared to other assessment tools, which is a differentiator since none of the other tools provide such granularity, leading to better decision-making for my migration to the public cloud.

Device42 has improved my migration projects by providing granularity around system dependencies that gave me confidence knowing which systems communicate with each other parked in a particular move group. My move group planning became so robust that I am not leaving any system behind in the on-premise data center from my planning, which saves a lot of time and effort, leading to cost optimization—a value addition.

The features I appreciate most about Device42 are the agent-based service providing more granularity and metrics. However, I foresee areas of improvement for the agent-less solution, which could be very useful for those organizations that might not allow configuring an agent in their source machines for workload discovery.

I think the graphical representation of all associated machines needs improvement to better illustrate how these systems have dependencies on each other. The network graph representation can be matured, which I find useful.

I have been using Device42 for four years.

Device42 is stable and has been reliable for my organization. I find myself more confident using Device42 because I have been well-versed with this tool for a couple of years.

Device42 handles my organization's growth and changing needs well. Although it has some dependency on the number of agents, if you understand all the prerequisites shared by Device42, it is very much scalable and allows you to design your discovery solution without facing any challenge.

Customer support for Device42 is fantastic. They have quick SLA responses and provide support through call, email, and chat, effectively assisting me with any agent configuration or troubleshooting issues.

Negative

Prior to Device42, I was using Cloudamize and Migration Evaluator. Before choosing Device42, I evaluated AWS native Migration Evaluator.

As part of workload assessment, Device42 has enabled me to meet the required TCO calculation, helping to generate ROI while doing a workload assessment with TCO of five years and three years. It has facilitated bringing in the right-sized systems for the public cloud environment, ensuring these systems are rightly sized based on metrics and inventory captured for on-premise systems. The TCO calculations based on five years and three years have yielded a remarkable ROI compared to on-premise workload, validating the business case submission to the customer.

My experience with pricing, setup cost, and licensing for Device42 is that it is really reasonable. Compared to other competitors, it does not cost much, and I would recommend it from a cost perspective.

For anyone looking into using Device42 for workload discovery of their on-premise data center resources and planning to move to the public cloud, I recommend Device42 because of the level of granularity it generates, which instills more confidence during migration.

Device42 is a fantastic tool for workload discovery, and I believe everyone should start using it if they have plans to do so; it is a top-notch tool in the market. I gave this review a rating of 10 out of 10.