BlueCat Cisco ACI creates a number of Configurations in BlueCat Address Manager (BAM) to hold the infrastructure information that it imports. The number of Configurations depends on what you entered in the Configuration field when performing an import operation.
After importing the Cisco ACI infrastructure, the workflow creates tags for each imported ACI Tenant with the same name as the tenant. This tag is linked to the tenant's Configuration, plus all of the IP Blocks, IP Networks, and Devices that were created based on that tenant's infrastructure.
BlueCat Cisco ACI places these tags in a new BAM Tag Group called "Cisco ACI Tenants". To view the BAM objects that were created for a specific tenant, in Address Manager, go to .
Importing information into a single, specific BAM Configuration
If you specify a Configuration when importing tenant information, the BlueCat Cisco ACI workflow stores all discovered components from all tenants in the same, single Configuration in Address Manager.
The BlueCat Cisco ACI workflow also creates a UDF (user-defined field) named
Cisco Tenant for each IPv4 block and Ipv4 network object,
visible in the Details page of the BAM object (in the
General section). This UDF contains the name of the ACI
tenant. You can use this UDF to determine the ACI tenant to which a BAM object
belongs.
Importing information into multiple BAM Configurations
If you do not specify a Configuration when importing tenant information (that is, if the Configuration field is blank), the BlueCat Cisco ACI workflow stores object details in multiple Configurations, one for each ACI tenant. The name of each Configuration has the following format:
Cisco ACI: [<ACI tenant name>/<ACI application profile name>/<ACI bridge domain name>]Within these Configurations, the Configuration Group is set to the Cisco ACI tenant's name.