Two ways to boost enterprise IT self-service delivery

To elevate self-service automation, tie in your IPAM solution and account for IP address over-allocation. Learn how BlueCat Gateway can help.

Small child at base of towering stone steps, illustrating the steep journey to scalable IT self-service automation
Key Takeaways
  • Integrating IPAM directly into self-service workflows eliminates manual IP lookups, reducing human error and freeing IT staff from routine administrative tasks.
  • Disconnected self-service and IPAM systems increase the likelihood of configuration mistakes and outages, and slow down incident resolution when failures occur.
  • High-speed automation amplifies the risk of IP address collisions and over-allocation when multiple parallel processes draw from the same finite IP pools.
  • Resilient self-service designs must explicitly account for automation race conditions in IP allocation, particularly in large environments with many concurrent requests.
  • BlueCat Gateway, together with the ServiceNow Adaptive Plugin, enables end-to-end DNS/DHCP/IPAM automation and self-service directly from existing ITSM and orchestration tools.
  • Using BlueCat’s “assign next available IP” API instead of “get next available IP” ensures atomic IP allocation, preventing duplicate assignments and improving IP address consistency.

Self-service automation tools for IT enterprises are an increasingly common antidote to shadow IT, costly human errors, and prolonged outages.

Adding IP address management (IPAM) to your self-service automation strategy can reduce those errors, resource drains, and outages even further. However, the importance of integrating IPAM into your network self-service delivery sometimes gets little more than a passing glance.

This post will examine two ways to elevate your IT self-service delivery. First, it will outline the importance of tying your enterprise’s IPAM solution to self-service. Then, it will explore fortifying your self-service by planning for automation collisions that can cause IP address over-allocation. Finally, it will highlight capabilities in BlueCat’s Gateway network automation platform that support both strategies.

The discussions of a group of IT professionals who are part of BlueCat’s open DNS expert conversation series inspired this post. All are welcome to join through the Network VIP community on Slack.

Step 1: Tie your IPAM into self-service delivery

A good self-service structure calls on all the right data and systems needed to execute against sound business logic.

With self-service, users can get what they need quickly, keeping them from seeking their own solutions. IT resources can focus on higher-level work instead of fulfilling rote requests. Network automation also significantly reduces manual errors and the risk of service disruptions.

Unfortunately, BlueCat often finds that enterprises’ self-service tools are fully disconnected from their IPAM solution. Look-ups to find an available IP address or server to assign still mostly occur in a manual fashion. That means expending valuable IT resources on basic admin tasks. Furthermore, it increases the risk of introducing human error.

Organizations that don’t automate IPAM as part of self-service delivery ought to. By doing so, they can free up network teams’ time and reduce the risk of mistakes that can lead to outages. And when outages do occur, they can resolve them much faster.

Step 2: Fortify self-service by planning for IP over-allocation

Even for organizations who automate IPAM for self-service, it’s not always smooth sailing.

A user might put in a ServiceNow ticket to, let’s say, create a host record. ServiceNow will then proceed and grab the next available IP address. But by the time that request is fulfilled and approved, that same IP address has been taken by another request.

With automation, you make processes a whole lot faster than if you did them manually. You might be able to handle dozens of requests simultaneously to execute hundreds of actions.

However, when you’re allocating or deallocating from a finite pool of resources like IP addresses, collisions between automation processes are much more likely to occur. Especially if you’re a large shop with thousands of users.

One participant provided a plausible large-enterprise example scenario from his experience.

“Sixty people could all go in and request servers at the same time. And it could be 200 servers that get built and allocated. And if they happen to be going into some combination of the same subnets…” the participant began. “Because automation is so fast, from the time that I identify which IP I’m going to do, somebody else has identified that same IP in a parallel process. And one of the two loses, depending on who gets there first for the actual grab.”

Consequently, it’s important for network teams to keep this in mind when implementing automation. Definitely factor it into resiliency planning.

Make IPAM automation more resilient with BlueCat

Automate IPAM for self-service with Gateway and the ServiceNow Plugin

BlueCat’s automation platform, Gateway, allows you to quickly create and customize DNS, DHCP, and IPAM workflows. Furthermore, it integrates with adjacent systems and technologies, like ServiceNow and VMware vRealize Orchestrator (vRO).

Learn about how to get started with Gateway and watch a quick demo here:

Introduction to BlueCat Gateway | Automating DNS, DHCP, and IPAM Workflows

Our ServiceNow Adaptive Plugin for Gateway offers automation and self-service functionality through the ServiceNow user interface. With it, you can automatically add, modify, and delete host records, alias records, and IP addresses and allow end-users to make changes or validate configurations directly.

Get a quick demo of the plugin here:

Ease IP address over-allocation with BlueCat’s API

BlueCat’s API uses automation to address some of the conditions where IP-address over-allocation can occur. And Gateway makes it an especially easy platform for building and compiling these automation building blocks.

APIs that can help include “assign next available IP“, “get next available IP“, and “get next available IP range“.

The “assign next available IP” API is especially helpful for easing IP over-allocation, even more so than “get next available IP”. When taking the “assign next available IP” action, the API immediately assigns the IP to the host record rather than just getting what is available. It avoids two people assigning the same IP if users make requests during the same timing window.

As a result, it ensures that the IP is actually yours. IP address assignment is consistent and only allocates exactly what a user requires.


Published in:


An avatar of the author

Rebekah Taylor is a former journalist turned freelance writer and editor who has been translating technical speak into prose for more than two decades. Her first job in the early 2000s was at a small start-up called VMware. She holds degrees from Cornell University and Columbia University’s Graduate School of Journalism.

Related content

Flock of geese flying in formation across a blue sky, framed by a pink graphic border, symbolizing coordinated network migrat

Automate your DDI modernization path by migrating with Micetro

Automate cross-platform DNS and DHCP migration with Micetro to reduce risk, eliminate manual effort, and modernize infrastructure faster.

Read more
Three armored figures walking toward a futuristic Las Vegas skyline with pyramids, glowing orb, and "Welcome to Fabulous Las

Your journey to intelligent NetOps begins at Cisco Live

Visit BlueCat’s booth or book a meeting now to learn more about how our solutions can help you build a network that supports constant change.

Read more
Stacked colorful wooden directional arrows on a post by a calm seaside with distant hills and blue sky

Replace BIND and ISC with Micetro DNS/DHCP Server (MDDS)

Tired of patching and manually configuring BIND DNS and ISC DHCP? Discover how Micetro MDDS appliances can replace them for modern DDI.

Read more
Row of orange industrial robotic arms positioned along an automated conveyor belt in a factory setting

Automate it all in Integrity with REST v2 API-first DDI management

Discover API-first DDI with Integrity X by using REST v2 to automate DNS, DHCP, and IPAM for scalable, secure network operations.

Read more