Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

This feature is exclusively available to participants in the Early Access Program (EAP). For information about the EAP, visit Infoblox Early Access Program. If you are not part of the EAP, you may not be able to access this feature. Infoblox consistently updates our documentation as we add new features to the EAP.

Problems with overlapping IP addresses can occur when various IPAM (IP Address Management) services, including on-premise solutions like NIOS and cloud-based DNS solutions such as AWS Route 53, Azure DNS, and Google Cloud Platform (GCP) are deployed across the network without a centralized management console that manages all on-premise and cloud providers. This can lead to conflicts in routing and addressing, potentially causing network communication problems. IPAM Federation solves this problem.

The purpose of the IPAM Federation service is to manage and organize unique address spaces that are required across IP spaces, namespaces, or views by maintaining federated block of IP addresses and delegating ownership of those blocks to other IPAM services. IPAM Federation provides a method to manage network address blocks to a federation of IPAM contexts in BloxOne DDI, NIOS, or any other cloud IPAM providers.

IPAM Federation contains the following objects:

  • Federated Realm - A realm serves as a named container for a group of objects, establishing a distinct namespace for IPv4 and IPv6 addressing.

  • Federated Block - CIDR notation prefix for globally unique address range which can be used for further allocation.

  • Delegation - A CIDR notation prefix represents an address range that has been delegated to another cooperating IPAM service.

  • Overlapping Block - A CIDR notation prefix representing an address range for which authority is expressly abandoned. Cooperating IPAM services may allocate overlapping prefixes from this block, with the understanding that they will never route to each other (for example, used behind a NAT gateway).

  • Reserved Block - A Reserved Block is a CIDR notation prefix representing an address range for which authority is expressly forbidden. Cooperating IPAM services must not allocate overlapping prefixes from this block.

The following diagram explains IPAM Federation:

As shown in the above diagram, IPAM Federation can be configured as follows:

  1. Create a Federated Realm.

  2. Create a Federated Block or a Overlapping Block under a specific Federated Realm. A Federated Block can only have unique IP addresses. A Shared Block can have overlapping IP addresses.

  3. Delegate an Address Block and Subnet from a Federated Realm.

  4. IPAM objects from BloxOne DDI, or discovered from NIOS, or a cloud IPAM provider is organized.

You can complete the following actions:

  • No labels