One area for improvement in BlueCat Gateway is the time it takes to fill in the dropdown in the UI of the solution because the speed with which the data loads isn't that fast. It would be better if you didn't have to wait for old items to load before seeing the first data. Another area for improvement in BlueCat Gateway is the discovery probe, as it doesn't allow you to see all the setup parameters after you've set it up. This may not be a big issue, but it's something my team noticed that may not be good in the solution.
Principal Architect, System Design /Enterprise-Hybrid Cloud DNS Lead at a healthcare company with 1,001-5,000 employees
Real User
Top 5
Aug 24, 2023
What I dislike is that there are limitations on how the data is viewed within BlueCat IPAM. As a result, we need to examine it from two different perspectives. While observing the tool's operation in Cloud Discovery visibility within its environment, we can witness it extracting the data and showing us the data's origin and location in the cloud – all of which is quite informative. However, upon importing this data into BlueCat for actual analysis, many of these informative components seem to be absent. We are hopeful version ten of BlueCat IPAM might resolve this matter. Currently, the data present there, when I inspect, let's say, a newly arrived or discovered device, I can see that device. Nevertheless, we lack a method to determine its location. For instance, if another person were to access that device aside from me, they wouldn't find information regarding its location. Although we can view the device itself and its configurations, its Azure-based location is not provided. Regrettably, certain essential flags are not transferred. I am presently engaged in an ongoing discussion with BlueCat's senior leadership regarding this matter. I am collaborating closely with them on resolving this issue, and they are acknowledging the problems. Given the complexities of our extensive presence in Azure, they also comprehend the rationale behind our configuration choices in CDNV. Consequently, we are also considering potential adjustments in IPAM to better align with the required data presentation. The biggest issue is the visibility of cloud discovery in the IPAM database and how it structures data. This is currently a significant hindrance.
Network Automation enhances the efficiency, reliability, and management of network processes by replacing manual tasks with automated systems. This technology supports scalable network operations and reduces errors caused by human intervention.Network Automation offers significant improvements for businesses seeking to streamline operations. By automating routine network tasks, organizations can free up IT resources to focus on higher-value projects. This leads to quicker implementations and...
One area for improvement in BlueCat Gateway is the time it takes to fill in the dropdown in the UI of the solution because the speed with which the data loads isn't that fast. It would be better if you didn't have to wait for old items to load before seeing the first data. Another area for improvement in BlueCat Gateway is the discovery probe, as it doesn't allow you to see all the setup parameters after you've set it up. This may not be a big issue, but it's something my team noticed that may not be good in the solution.
What I dislike is that there are limitations on how the data is viewed within BlueCat IPAM. As a result, we need to examine it from two different perspectives. While observing the tool's operation in Cloud Discovery visibility within its environment, we can witness it extracting the data and showing us the data's origin and location in the cloud – all of which is quite informative. However, upon importing this data into BlueCat for actual analysis, many of these informative components seem to be absent. We are hopeful version ten of BlueCat IPAM might resolve this matter. Currently, the data present there, when I inspect, let's say, a newly arrived or discovered device, I can see that device. Nevertheless, we lack a method to determine its location. For instance, if another person were to access that device aside from me, they wouldn't find information regarding its location. Although we can view the device itself and its configurations, its Azure-based location is not provided. Regrettably, certain essential flags are not transferred. I am presently engaged in an ongoing discussion with BlueCat's senior leadership regarding this matter. I am collaborating closely with them on resolving this issue, and they are acknowledging the problems. Given the complexities of our extensive presence in Azure, they also comprehend the rationale behind our configuration choices in CDNV. Consequently, we are also considering potential adjustments in IPAM to better align with the required data presentation. The biggest issue is the visibility of cloud discovery in the IPAM database and how it structures data. This is currently a significant hindrance.