Enabling IP address management

This section describes how to enable IP address management (IPAM) for your environment. You can use the integrated IPAM system in BMC Network Automation, or you can enable an interface between BMC Network Automation and a third-party IPAM system. BMC Atrium Orchestrator is used as a middle tier between BMC Network Automation and the third-party IPAM system. BMC Network Automation currently supports the use of the Alcatel-Lucent VitalQIP IPAM and the Infoblox IPAM products as third-party IPAM solutions.

Managing the BMC Network Automation integrated IPAM system

See Managing the integrated IP Address Management system in the BMC Network Automation online technical documentation for more information about managing the integrated IPAM system that is installed with BMC Network Automation.

BMC Atrium Orchestrator components required for integrating with a third-party IPAM system

BMC Network Automation integration with third-party IPAM solutions requires BMC Atrium Orchestrator platform and content components.

The BMC Atrium Orchestrator platform provides the configuration distribution peer (CDP) and the tools that you need to create a grid. Installing the platform is a prerequisite for installing BMC Atrium Orchestrator content, which includes adapters, modules, and run books. For more information about installing BMC Atrium Orchestration platform components, see Installing in the BMC Atrium Orchestrator online documentation.

The following table summarizes the BMC Atrium Orchestrator contents that are required for integration with third-party IPAM solutions:

BMC Atrium Orchestrator content




Base adapters > Terminal

Third party adapters > Infoblox NIOS


Run books > BMC BBNA IP Address Management

Run books > BMC BBNA IP Address Management

Management modules > AutoPilot OA IP Address Management (Vital QIP)

Management modules > AutoPilot OA IP Address Management

Core modules > AO AD VitalQIP



BMC Network Automation does not support a hybrid IPAM environment. A hybrid IPAM environment would be one in which a pod is created using the integrated IPAM system and another pod is created using a third-party IPAM system. You must delete existing pods before switching IPAM systems, for example, from the integrated IPAM system to Infoblox.

Related topics

Was this page helpful? Yes No Submitting... Thank you