This section details how the Cisco ACI tenant infrastructure is modeled in Address Manager.
Created BAM objects for Cisco ACI tenants
The Cisco ACI workflow creates objects in BlueCat Address Manager (BAM) based on the ACI tenant infrastructure as follows.
Cisco ACI infrastructure component | BAM objects |
---|---|
ACI Tenant |
Configuration Note: If you select a specific BAM Configuration when importing a
Cisco ACI infrastructure, objects for all tenants are instead
imported into that single Configuration.
|
ACI Subnet | IPv4 Block with one or more IPv4 Networks |
ACI Endpoint Device |
Device (with a new Device Type) |
New BAM Device Types and Device Subtypes
The Cisco ACI workflow creates several device types and subtypes to model ACI fabric
devices, including a new Device Type named Cisco ACI
Infrastructure
.
-
To view the list of available device types, in Address Manager, from the Groups tab, click Device Types.
-
To view the list of new device subtypes, in Address Manager, from the Groups tab, click Device Types, click Cisco ACI Infrastructure, then click Device Subtypes.
The new types and subtypes appear after the first time you import a Cisco ACI infrsatructure. The new types and subtypes are:
Entity | Name |
---|---|
Device Type |
|
Device Subtype (of device type Cisco ACI Infrastructure) |
|
Device Subtype (of device type Cisco ACI Infrastructure) |
|
Device Subtype (of device type Cisco ACI Infrastructure) |
|
BAM object settings for Cisco ACI tenant infrastructures
When adding or updating objects in BlueCat Address Manager (BAM), the Cisco ACI workflow configures each object's settings to track details about the corresponding ACI infrastructure. In some cases, these values are tracked in new user-defined fields (UDFs).
Settings for Configurations, Blocks, Networks, and Devices for Cisco ACI tenants are as follows.
BAM Configuration
Setting | Value |
---|---|
Name |
If you specified a Configuration when importing the Cisco ACI infrastructure into Address Manager, the existing name is retained. If you did not specify a Configuration when importing the Cisco ACI infrastructure, the Cisco ACI workflow creates a separate Configuration for each tenant. The name of each configuration is based on the names of the Cisco ACI tenant and the associated ACI bridge domain and ACI application profile:
|
Configuration Group | Associated Cisco ACI tenant name. |
IPv4 Block
Setting | Value |
---|---|
Name |
|
Range | The ACI subnet gateway address (CIDR). |
Cisco tenant (UDF) |
If you specified a Configuration when importing the Cisco ACI infrastructure into Address Manager, this UDF contains the name of the associated Cisco ACI tenant. Otherwise, this UDF is empty. |
IPv4 Network
Setting | Value |
---|---|
Name |
|
Addresses | The ACI subnet gateway address range. |
ACI Scope (UDF) | The scope can be one of the following:
|
Cisco ACI (UDF) |
If you specified a Configuration when importing the Cisco ACI infrastructure into Address Manager, this UDF contains the name of the associated Cisco ACI tenant. Otherwise, this UDF is empty. |
Endpoint device within an ACI tenant
Setting | Value |
---|---|
Name |
The ACI endpoint device's MAC address. |
IP Addresses |
The ACI endpoint device's primary and secondary IPv4 addresses that lie within the ACI subnet under the ACI application profile. |
Device Type |
|
App Profile (UDF) | The ACI tenant application profile name. |
Cisco External Addresses (UDF) | The ACI endpoint device's IP addresses that fall outside of the ACI subnet that is under the ACI application profile. |
DN (UDF) |
The device's ACI bridge domain name (DN). |
EPG | The device's ACI endpoint group name. |
MODEL (UDF) | N/A (applicable only to ACI fabric devices) |
PORT (UDF) | N/A (applicable only to ACI fabric devices) |
SERIAL (UDF) | N/A (applicable only to ACI fabric devices) |
STATE (UDF) | N/A (applicable only to ACI fabric devices) |
VENDOR (UDF) | N/A (applicable only to ACI fabric devices) |