BlueCat Gateway Reviews

We use the Azure cloud infrastructure. The objective is to leverage BlueCat's IPAM solution capabilities. Specifically, within the Gateway, the process involves deploying new solutions in the cloud. It's crucial to monitor the allocation of network resources for these new solutions to prevent network overlap.

Here's how the process works: When a request is made to deploy a new solution in the middle of the construction process, the individual specifies their requirements including the needed amount of resources and Azure services. After sending this request, automation comes into play. The first step is for the automation to assess the network requirements for the Azure deployment. It queries the IPAM to identify the next available network within that Azure region. This information is then provided by IPAM to the automation tool.

Subsequently, the automation tool integrates this network data into Azure's deployment process. Concurrently, updates are made within the IPAM system to associate this network with the corresponding group or project. This is done through descriptions and features recorded in IPAM. Following these preparations, the automation tool initiates the processing of the deployment requests. It triggers additional automation scripts required to effectively construct the solutions within Azure.

Conversely, a similar process occurs when a solution is decommissioned in Azure. The deactivation of virtual networks within Azure triggers a communication back through the Gateway. This communication notifies the need to release these network resources for potential future use. The system then locates the specific networks, eliminates associated tags and descriptions within IPAM, and marks them as available for future allocations.

BlueCat's ServiceNow and CMDB adaptive plugins assist in reducing the time required to resolve tickets. This out-of-the-box solution simplifies the integration with the ServiceNow tool and provides a bridging framework. This framework facilitates smoother coding of components by our development teams, enabling them to collaborate effectively with BlueCat. As a result, we now have a readily available solution instead of having to build everything from the ground up.

Gateway's capability to enable the integration of third-party investments through Adaptive Applications and Plugins works exceptionally well. We are using Cisco for this purpose. These are direct plug-ins that Cisco provides to BlueCat, and they perform excellently. We use them extensively, whether it's for Cisco ACI, Titan, or Umbrella.

The visibility into our multi-cloud applications is great.

The ability to develop a kiosk-like solution for in-person assistance is crucial. This is especially true when individuals require assistance beyond automated processes, such as setting up a virtual network. This situation might arise when they are expanding their existing solution. If they require a new virtual network component, like one for the East US region in this case, they can access this information and then perform the necessary tasks manually at their location. I appreciate the convenience offered by this kind of walk-up request feature.

Another important aspect is the integration capabilities. For instance, integrating with ServiceNow would enable us to establish ticketed processes for requesting or releasing resources in on-premises scenarios, such as building new servers. For example, users could request new IPs for specific VLANs. This level of automation provided by the tool significantly streamlines these processes.

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.

I am currently using BlueCat Gateway. 

Regarding what our finance teams have coordinated with BlueCat, we don't currently experience any issues with the pricing. The cost is actually quite favorable based on our negotiations. Typically, each business is responsible for negotiating its own pricing. While we receive our Manufacturer's Suggested Retail Price, as is customary for reputable corporate entities, BlueCat is open to negotiating a more advantageous deal.

I would rate BlueCat Gateway a nine out of ten. BlueCat Gateway is a fantastic product. I've gained a lot of knowledge over time, and I have a solid understanding of the product line. My most significant concern is that the documentation has problems.

Creating, verifying, and validating APIs for third-party integrations and DDI self-service forms using BlueCat Gateway typically require our teams a few hours of work to complete. Therefore, they consider it comparable to other solutions in terms of time and effort.

We are utilizing BlueCat Cloud Discovery; however, our implementation is still a work in progress. The initial setup process aligns with the provided documentation and is straightforward. The challenges arise when running it within our intricate environment. We maintain direct communication with senior management responsible for the tool, seeking assistance in resolving issues, as we have identified scenarios that cause malfunctions. This is why I refer to it as an ongoing project. I aim to be equitable to BlueCat, considering they have other clients who are successfully using the tool. Unfortunately, our cloud environment's complexity poses challenges to the tool's functionality within our setup.

Researchers of BlueCat Gateway would have a significant opportunity if they were working in the DNS field to make use of the platform. The reference roll-up model facilitates the ability to integrate with BlueCat, instead of attempting to develop their own solution.