CloudCenter 4.8 has reached End of Life (EOL) as of November 14, 2018. See End of Support Notices for additional context.

Configuring ACI Extensions

Overview

CloudCenter users can use out-of-the-box application profiles to create infrastructure-independent models of any application. Once modeled, the Cisco CloudCenter platform and Cisco Application Centric Infrastructure (ACI) can work together to provide automated, end-to-end provisioning of compute, storage, and network configuration of the application as well as its set of required components.

ACI Fundamentals

See the Cisco ACI Fundamentals Guide for additional details on the ACI policy model. 

Benefits

The CloudCenter – ACI integration provides the following benefits:

  • Use a fully automated creation of ACI policy objects.

  • Gain the security and efficiency of network microsegmentation without the need to program or modify application code, write cloud-specific scripts, or have special network expertise. 

  • Users get self-service/on-demand deployment and management of applications with fully integrated Cisco ACI network policy and configuration.

Availability

The CloudCenter – ACI integration is available for VMware cloud environments.

CloudCenter supports the following APIC releases:

  • Cisco APIC, Release 1.0

  • Cisco APIC, Release 1.1

  • Cisco APIC, Release 1.2

  • Cisco APIC, Release 2.0 (only Distributed Virtual Switch – DVS mode)

  • Cisco APIC, Release 2.1 

  • Cisco APIC, Release 2.3

  • Cisco APIC, Release 3.0 (effective CloudCenter 4.8.2.1)

  • Cisco APIC, Release 3.1 (effective CloudCenter 4.8.2.1)

Requirements

The CloudCenter platform automates the end-to-end-provisioning of the overlay infrastructure and deployments of applications. On ACI, this includes the provisioning and management of the following resources:

Ensure that the APIC tenant being configured in the CloudCenter has the privileges to create these resources.

  • Application Network Profiles (ANP)

  • Endpoint Groups (EPG)

  • Contracts

  • Subjects/Filters

As a prerequisite for the CloudCenter platform to provision and configure the applications on APIC, first complete the following requirements to have a working Cisco ACI environment:

  • Leaf switch profiles, Switch Selectors, Interface Profile, and Policy Groups

  • VLAN Pool

  • VMware's Virtual Machine Manager (VMM) Domain

  • Routable IP subnet to a New Tenant and Bridge Domain(s) configured with Layer 3 out (L3 Out) for external internet connectivity.

    The CloudCenter platform uses the L3 Out network to associate the Common tenant (or the selected tenant).

  • Routing protocols

  • VRF – To enable an application for ACI compatibility, enable the micro-segmentation capability in the application profile. This is also listed as a requirement in the CloudCenter Requirements section below.

APIC Requirements

The Cisco Application Policy Infrastructure Controller (Cisco APIC) functions over both HTTP or HTTPS.

  • HTTPS: By default, Cisco APIC listens to HTTPS for both the UI and REST APIS.

    Ensure that the APIC is configured with a valid SSL certificate that corresponds to the APIC host name.

  • HTTP: Enable the HTTP access for APIC and ensure accessibility using either the host name or IP address

To configure the ACI Extension for the CloudCenter tenant to use the APIC’s default SSL certificate for HTTPS access, follow this process:

  1. Add an A record to the DNS zone for the “APIC” name - this record must match the name assigned to the default certificate shipped with the APIC.

  2. Once the record is added, ensure that https://APIC is resolved to the IP Address of the APIC – This is especially important for the CloudCenter platform. To configure the ACI extension, the default certificate must be first be imported into the key store.

    There is a useful utility that can facilitate this process:

    1. Log on as root to the CCO appliance and change to the /tmp directory

    2. Capture text necessary to create certificate (*.crt) file
      openssl s_client -connect your https host:443 < /dev/null

      For example:
      openssl s_client -connect 12.1.0.5:443 < /dev/null

    3. Copy the section from -----BEGIN CERTIFICATE----- to -----END CERTIFICATE——

    4. Save the copied text to a file named APIC.crt - for this example the file is placed in /tmp directory

  3. Add the certificate to the trust store:

    1. keytool -import -alias apic -keystore /usr/lib/jvm/jdk1.8.0_65/jre/lib/security/cacerts -file /tmp/APIC.crt

    2. Enter the password.

    3. keytool -import -alias apic -keystore /usr/local/osmosix/ssl/cco/cco_keystore.jks -file /tmp/APIC.crt

  4. Restart the Tomcat process:

    1. systemctl stop tomcat

    2. systemctl start tomcat

  5. Add the extension in CloudCenter Manager (ensure that you use the hostname APIC - for example, https://APIC/ - as the APIC Controller URL).

To ensure the sanity of the environment, follow this procedure.

  1. Using the APIC UI, manually add a new application network profile with one EPG.

  2. Verify that a new VMware Virtual Distribute Switch (vDS) port group is provisioned and displayed in the APIC UI.

  3. Using the vCenter UI, provision/clone a new VM with the network pointing to the created port group.

  4. If operating in Strict mode, you will not have SSH/RDP access to the VM:

    1. Create a Contract for Port 22/3389 with its provider being the EPG from Step 1. 

    2. Create a new L3 out setting to be consumed by the Contract created in Step 4a.

  5. SSH/RDP into the VM launched in Step 3 and verify that you can access the CloudCenter Bundle repository and the AMQP server.

CloudCenter Requirements

The CCO being used in the ACI Extension should be able to access the corresponding APIC endpoint – activate the native APIC integration in CloudCenter by adding the endpoint URL of the APIC as an Extension in the Admin area

The CloudCenter platform assumes that you have configured the ACI extension based on the following setup requirements:

  • The typical ACI constructs for the tenant (Bridge Domain, DHCP Policy/Relay Label, VRF, External Routed Network - whether tenant specific or shared from the common tenant) are preconfigured and operationally health.

  • CloudCenter will create a new ACI Application Profile, new EPGs - one per tier of the application, new filters and contracts and apply them to the new EPGs according to the design of the CloudCenter application profile.

  • The ACI objects created by CloudCenter are named after the original deployment name so that they can be quickly and easily traced to the CloudCenter deployment.

    • Configure the ACI Extension in the CloudCenter platform.

    • Once the extension is selected, the CloudCenter will auto-discover the objects relevant to the privileges of the user whose credentials were used to configure the ACI Extension.

    • The following resources are specified by the APIC:

      • Virtual Machine Manager – My-vCenter is specified by the APIC

      • APIC Tenant

      • L3 Out

    • Network Type = ACI

    • End Point Group = Existing EPG

    • Existing EPG:

      • Web-Servers

      • DB-Servers

  • If the CloudCenter components (CCM, CCO, AMQP) are contained in a different and separate tenant than the existing EPG(s) into which the application nodes are deployed, policies and corresponding contracts should exist and be applied so as to allow the nodes to reach the requisite CloudCenter services.

  • To enable an application for ACI compatibility, enable the micro-segmentation capability in the application profile. The default firewall rules for a service are automatically displayed if microsegmentation is enabled – you can restrict any firewall rule to any tier by specifying the tier name or IP for the source. See Security and Firewall Rules > Inter-Tier Communication (Firewall Rules) for additional context.

VMware vSphere Requirements

The following table describes the VMware vSphere requirements.

RequirementDetails
A working VMware vCenter 5.0/5.5/6.0 environment

The minimum VMware vSphere version is v5.0, but  vSphere v5.5 U2 is optimal.

The CloudCenter platform automates the provisioning of virtual machines into the VMware private datacenter.The CloudCenter platform requires access credentials to the vCenter setup.
All ESX host(s) must be physically connected to the ACI leaf switches.The prerequisite installation requirements for the datacenter are:
  • A physical ESX host capable of running at least 10 medium sized instances
  • An ESX cluster (cluster could comprise of just the one host)
  • A datastore (or datastore cluster for DRS support), at least 100gb of free space
If the ESXi hosts are Cisco UCS based
  • The VLANs for the CMM must be mapped to the vNIC template.
  • The uplinks from the Fabric must interconnect trunking VLANs to the leaf switches.

CloudCenter Extensions

The APIC policy model is available as a standalone extension on the CloudCenter platform and provides increased ease when creating ACI objects by allowing better, faster, and easier network isolation by:

  • Using Extensions on the CloudCenter platform, network administrators can access CloudCenter from the UI or the API to create, update, or delete the following objects:

    • Bridge domains

    • Virtual Machine Manager (VMM) domains

  • Allowing the consumption of newly-created bridge and VMM domains during the application deployment process or the deployment environment process without having to manually sync configurations.

Once you configure an extension (procedure provided later in this page), select the cloud and cloud accounts in the Network Settings section to see that a configured network, such as Cisco ACI, is available for selection when configuring this deployment environment.

Using ACI with CloudCenter Extensions

You can create a CloudCenter extension to extend the capabilities of the CCO to provision networks in an ACI environment. You can then Launch the ACI Extension to configure the following CloudCenter resources:

  • Deployment Environment Flow: ACI Extensions are also integrated in the deployment environment and you can determine the extension to be used by each cloud account. CCMs do not need to make the request to the cloud provider. See Deployment Environment Defaults for additional context.

  • Application Deployment Level: Configure tenant and VMM domains to be populated into the application profile when Deploying an Application. You can configure the External Routed Network field (Layer 3 out) for your APIC setup, as shown in the following screenshot, and connect to that tenant network.

  • NIC: When you select the Cisco ACI tab, you have the option to select one of the options from the Endpoint Group (EPG) Type, as shown in the following screenshot.

    • Existing EPG: Uses a preconfigured EPG form the APIC setup.

    • New EPG: Creates a new EPG for this deployment. Optionally, you can also select contracts or interfaces that are consumed by this new EPG.

    • Bridge Domain Template: Creates a new bridge domain using the selected template.

  • ACI as an External Service: When you Deploy an Application that contains an External Service, you can configure the ACI extension in the Advanced section for this service tier to use the APIC Service Graph Template. The following screenshot shows this section.

Configuring Extensions

When you have configured the cloud or datacenter resources (for example, the tasks listed in the ACI Integrations section), verify your network connectivity and launch a sample application to ensure everything is working from end-to-end. If all the requirements worked, you are ready to configure the extension from the CCM UI.

To configure an extension from the CCM UI, follow this procedure.

  1. Access the CCM UI and navigate to Admin > Extensions. The Extensions page displays and you can edit an existing extension or add a new extension as required for your ACI integration. The following screenshot shows the Extensions page.

    The TYPE column in the Extensions page currently displays ACI for all extensions as this is the only type of extension that is currently accepted by the CloudCenter platform.

  2. Click Add Extension. The New ACI Extension page displays, as shown in the following screenshot.

  3. Configure the following Cisco APIC endpoint information in the Connection Settings section:

    • The APIC Name

    • The APIC endpoint URL (HTTP or HTTPS)

    • The APIC access credentials (Username and Password) – Use the ACI admin credentials for APIC access. 

      If you do not use Admin credentials for the ACI account

      Most integrations use the ACI admin credentials for APIC access.

      If you use the Admin credentials, you do not need the information in this note.

      If you prefer to limit the CloudCenter platform's access to ACI, then make sure that the ACI user for the ACI–CloudCenter integration account is configured as follows:

      • Create the Security Domain (SD) and associate the SD with the VMM(s) and Tenant(s) used for the ACI – CloudCenter integration.

      • Create an ACI Role with the following privileges:

        • vmm-connectivity

        • tenant-security

        • tenant-network-profile

        • tenant-epg

      • Add (associate) the SD to the ACI–CloudCenter integration account and assign the created ACI Role with writePriv (write privilege).

    • The CCO used to manage this APIC endpoint (select the required CCO from the dropdown list)

  4. Click Connect to connect and save the ACI configuration information. 

    1. The CloudCenter software validates the APIC endpoint connection and displays a status message displays at the top of this page.

    2. Once the APIC endpoint connects successfully, you also see the New ACI Extension page refresh to display the Bridge Domain Template section below the Connection Settings section. You can use this section to provide additional placement information. See the Bridge Domain Template section below for additional details.

  5. Click Save to save this new extension. The Extensions page refreshes to display the newly-configured extension to the list of configured and validated Extensions.

Launch the ACI Extension

To launch the ACI integration in your cloud, follow this procedure.

  1. Access the CCM UI and navigate to Deployments. The Deployments page displays

  2. Click the Environments tab. The Deployments page refreshes to dis play the configured environments and you can edit an existing environment or add a new environment as required for your ACI integration.

  3. Click Add Environment. The New Deployment Environment page displays.

  4. In the General Settings section:

    1. Provide the deployment environment Name

    2. Optionally, provide a Description.

    3. Identify if approval is required to deploy to this environment by switching On the button. 

  5. In the Cloud Selection section:

    1. Select the checkbox for the required Cloud Region. This cloud region must be the same as the CCO cloud region (used to manage your new APIC extension in the above section).

    2. Select the Cloud Account from the dropdown list.

  6. Click Define Default Cloud Settings to define the Deployment Environment default settings for this cloud. See Deployment Environment Defaults for additional context.

    You can pre-define much of your experience during the deployment submission in the Default Settings of the Deployment Environment. See Deployment Environment Defaults for additional context.

  7. (Optional) Define the Networks Settings: 

    1. Turn On the Use Network Types button. The Networks section expands to display the Network Types.

    2. Click +Network Type to add a new type. The New Network Type page displays.

      1. Provide the network type Name.

      2. Optionally, provide a Description.

      3. Configure the Network SettingsThe available networks for this cloud are displayed in the Network Settings section. The Network Settings section differs for each cloud. 

        VMware Cloud Settings

        Configure the fields described in the table below for VMware cloud regions. These fields are configurable for the following features:

        The CloudCenter platform does not explicitly request the disk provisioning type for root disk or additional volumes on the virtual machines that it deploys on vCenter, to be thin provisioning, thick provisioning eager zeroes or thick provisioning lazy zeroed. The root disk provisioning type is the vCenter default which is the same format as the source template or snapshot on the VM. For additional volumes it will either be the vCenter default or the datastore default depending on the type of datastore.

        CloudCenter 4.9.1 introduces the Allowed Additional Volume that was configured as specified in the Region-Level Cloud Settings > Allowed Additional Volume Sizes field

        Select the required option from the dropdown lists for each field identified in the following table:

        FieldDescription
        Root Disk

        Effective CloudCenter 4.9.0, the Root Disk setting is available in the Tier Settings > Volumes section on the Deployments page (not the Deployment Environment Defaults page).

        You can only select the Root Disk size if the Cloning Mode is set to Full Clone (Enable Full Clone = Selected).

        Specify the Root disk size to be greater than the size specified in your template/snapshot.

        Additional Volume (if configured)

        Effective CloudCenter 4.9.1 the Regions tab for VMware vCenter environments displays two new fields:

        • Allowed Root Disk Sizes 

        • Allowed Additional Volume Sizes (allows users to delete or use the specified GB for this setting)

        See Region-Level Cloud Settings for additional context.

        DatacenterRequired. The name of the datacenter object in vSphere.

        Either this setting is required

        This field is ONLY available if the Capacity Management feature is enabled.

        Auto Select Cluster

        The CloudCenter platform makes this determination when you deploy from the the Deployment Environment Defaults form or from the Deployment (Job) Details (Job Submission) page.

        • DisabledDefault. Can select a cluster during deployment because the CloudCenter platform determines the cluster for the deployment. The Cluster, Datastore, and Resource Pool settings are available and can be configured.
        • Enabled – Cannot select a cluster during deployment because the CloudCenter platform determines the cluster for the deployment. The Cluster, Datastore, and Resource Pool settings are NOT available and cannot be configured. 

        Or

        This group of settings are required

        Cluster

        The name of the server group in this datacenter's virtual environment in vSphere where you want to deploy VMs.

        Datastore

        The list of DataStores (DS) from vSphere. You can select both the datastore cluster and the the DS if DRS is disabled. When you select a Datastore cluster, if DRS is:

        • Disabled – Select a Datastore deployment from a dropdown menu or leave the DS un-selected so the CloudCenter platform can assign the logic for the datastore selection.
        • Enabled – The Datastore dropdown is disabled and neither you nor the CloudCenter platform can make any selection.
        Resource PoolThe default computing resources used to manage resource allocations between VMs. Use the default source pool name from vSphere where you need to deploy instances.

        Target Deployment Folder

        The default folders used to group objects of the same type for  management and VM deployment.


        Enable Full Clone

        If you use VM Template when configuring images for VMware cloud environments, be aware of the following settings.


        SettingDescription
        Full Clone
        • Use if deploying to a different VMware cluster from the worker image.

        • Use if you select an image that is mapped to a Template. Add this Template to the CliqrTemplates folder
        • The full clone operation is performed on the source VM or VM template, the cloned VM can be on either datastore or datastore cluster that you specify.
        • You can use the Full clone option for both Snapshots and Templates.
        Linked Clone
        • Use if the image is mapped to a snapshot.
        • Add a folder in vSphere (to store your CloudCenter snapshots), name it CliqrTemplates, and add this snapshot to the CliqrTemplates folder.
        • At the time of deployment, deploy to the datastore where the snapshot is present.

        When you use a Snapshot, both the Linked Clone and Full Clone options are possible settings. See Configure Image IDs for additional context.

        To configure these settings, you should have already configured the following entities in VMware:

        • A VMware cluster
        • A datastore cluster

        To configure the clone settings in the CloudCenter platform, select the Enable Full Clone (linked clone) checkbox

        Full Clone SettingDescription
        Selected

        CloudCenter creates a full disk clone of the VM.

        If the root size reflects the same size as the template, be sure to resize the partition once the instance is up and running.

        Not Selected (default)

        CloudCenter creates a thin clone which is faster but relies on the original VM disk being available in its original location.

        The format is the same as the source template/snapshot disk format (the default when you create a VM from the vCenter UI).


        Root Disk Resizable

        This field is deprecated in CloudCenter 4.9.0 and later releases.

        You can only select the Root Disk Resizable if the Cloning Mode is set to Full Clone (Enable Full Clone = Selected).

        This feature is only available for VMware VMs.

        The CloudCenter platform provides the capability to resize the root disk for VMware VMs by a configurable setting to specify the root disk size based on the OS type. This configuration setting is similar to the data store cluster setting.

        When you initially provision the VM, you can define the base OS disk size in the instance type configuration for each VM. A default VM includes a base (root) OS disk and an ephemeral disk. Some enterprises may have a requirement in place to only use one disk instead of both disks.

        You can only increase (not reduce) the VM root disk size – The new root disk size should not be smaller than the default root disk size.

        For example, if the root disk size is 250 GB, then you can only resize the instance type to be greater than 250 GB. The instance size in this case cannot be less than 250 GB.

        • Enabled: When you specify the Instance Type Storage for a deployment and if this setting is greater than the configured root disk size in the template or snapshot, then the root size of the deployed VM will be set to the size specified in the instance type.

          The additional space is not formatted or partitioned by CloudCenter. Use the Node initialization script to perform these tasks.

        • Disabled: When this option is disabled, an additional disk with the specified size is created in the instance type.

        VMware Network Settings
        1. Toggle the Visibility  switch to determine if you want to allow your end users to use pre-configured settings.  

          • OFF: (Default) End users are not allowed to use preconfigured ACI extensions.

            1. Select the Network in the NIC section. See IP Allocation Mode for additional context on NIC configuration.

            2. Add additional NICs, if required.

          • ON: End users are allowed to use preconfigured ACI extensions.

            1. Select the required extension, the corresponding options are displayed in the dropdown list for the remaining fields (see Extensions for additional details):

            2. Select the APIC Extension from the dropdown list (see ACI Extensions for additional details).

            3. Select the APIC Virtual Machine Manager (VMM) associated with this APIC Extension from the filtered dropdown list .

            4. Select the APIC Tenant associated with this APIC Extension from the filtered dropdown list.

        2. Select the Network in the NIC section.

          • If you select VMware, select the Network in the NIC section. See IP Allocation Mode for additional context on NIC configuration.

          • If you select Cisco ACI, select the type in the End Point Group (EPG) Type field.

            1. Existing EPG: If you select this type, you must further select a pre-existing EPG (that is already connected to one of the Bridge Domains) from the Existing EPG dropdown, which appears if you select this type.

            2. New EPG: If you select this type, you must further select a pre-existing Bridge Domain (to which this EPG must connect) from the Bridge Domain dropdown list.

            3. Bridge Domain Template: See Extensions for additional context.

        3. Add additional NICs, if required.

        SSH Options

        See SSH Options for additional context.

        Back to:


  8. Click Save to save this new deployment environment. The Environments page refreshes to display the newly-configured deployment environment to the list of configured and validated Environments.

  9.  Designate a Bridge domain from the ACI environment. The list of bridge domains is pulled from ACI. See the Bridge Domain Template section for additional context.

Bridge Domain Template

bridge domain represents a Layer 2 forwarding construct within the fabric. The Bridge Domain template (Layer 2 space) is linked to an ACI Virtual Routing and Forwarding (VRF) template (Layer 3 space). See the Cisco ACI Fundamentals Guide for additional details.

From the CloudCenter context, the ACI integration requires a routable IP subnet to a New Tenant that is configured with Layer 3 Out for external internet connectivity. When configuring an ACI Extension as part of the Deployment Environment Defaults, you have the option to select Bridge Domain Template in the Cisco ACI, End Point Group (EPG) Type field. 
If you do, you should have already configured the Bridge Domain Template so it displays in the dropdown list for that field.

CloudCenter administrators can create a Bridge Domain template to configure ACI extensions:

  • Each time CloudCenter admins configure an ACI extension, they also have the option to configure a Bridge Domain template.

  • The L3 Out connection to the external world is through the CloudCenter EPG Type selection. If you are deploying this instance into an existing EPG type, you do not need to update the subnet mask each time. 

  • To restrict this subnet from being accessed by any other network, update the subnet mask with the database tier ID in the Bridge Domain template. This way, the subnet is exposed to the world on this external network and allows the destination to be open to the DB node.

  • When connecting to the database tier, the database Layer 3 out is linked to one of the IP addresses displayed in a dropdown list — instead of allowing everyone to connect to a tier.

To add a Bridge Domain Template, follow this procedure.

  1. Access an ACI Extension as outlined in the section above (Admin > Extensions) and edit an existing extension. You can also opt to create a new extension in the process outlined above and continue to add a Bridge Domain Template as an extension of that process.

  2. In the Add ACI Extension page or Edit ACI Extension page, scroll down to the Bridge Domain Templates section, as shown in the following screenshot.

  3. Click Add Template. The New Bridge Domain Template pages displays.

  4. Configure the following Bridge Domain Template details in the General Settings section:

    • Template Name: A name reference by which you can refer to this Bridge Domain template.

    • Bridge Domain Name Configuration: The exact name variable for the Bridge Domain that is used by the ACI.

    • VRF Selection:

      • Existing VRF: Select the VRF from the dropdown list. Templates are listed by tenant in the dropdown list, be sure to select the VRF template for the correct ACI tenant.

        Shared resources are saved in the Common tenant, as shown in the following screenshot.

        When you select a VRF from a Common tenant (highlighted in the dropdown list image), that Bridge Domain Template can be selected by any tenant and consequently deployed to any other tenant. If you select a VRF that is specific to just one tenant, you can only deploy the Bridge Domain Template to just that tenant.

      • Dynamic VRF: Select a VRF that is provisioned for this APIC. The VRF hosts the Bridge Domain that is created using the Bridge Domain Template.

    • Associated L3 Outs: Optional. Depending on the tenant selected in the VRF settings, you can now associate the L3 Out networks from the Common tenant (or the selected tenant).

    • L3 Out for Route Profile: Optional. Depending on the tenant selected in the VRF settings, you can now select the desired L3 Out for route profile from the Common tenant (or the selected tenant).

    • DHCP Relay Label: Optional. Depending on the tenant selected in the VRF settings, you can now select the one or more DHCP relay labels from the Common tenant (or the selected tenant) that is applied to the new bridge domain.

  5. Configure the following network details in the Subnet section. 

    • Scope: APIC concept – See the Cisco ACI Fundamentals Guide for additional details. 

      • Private to VRF: An APIC setting that refers to a Private Network (context) is equivalent to a virtual routing and forwarding (VRF) instance in the networking world.

      • Advertised Externally: An APIC setting that refers to an EPG that provides a shared service must have its subnet configured under that EPG (not under a bridge domain), and its scope must be set to advertised externally, and shared between VRFs.

      • Shared between VRFs: An APIC setting that refers to shared subnets must be unique across the VRF involved in the communication. When a subnet under an EPG provides a Layer 3 external network shared service, such a subnet must be globally unique within the entire ACI fabric.

    • Subnet Control: APIC concept – See the Cisco ACI Fundamentals Guide for additional details.

      • ND RA Prefix: An APIC setting to control Neighbor Discovery (ND) – Router Advertisement (RA) message communications between an outside public or private network and the ACI fabric.

      • Querier IP: An APIC setting to enable Internet Group Management Protocol (IGMP) snooping on the subnet.

    • Subnet Pools: CloudCenter concept – Prevents any subnet in the pool from being wrongly reused. When you deploy a Bridge Domain Template on an application with multiple tiers, then each tier will use a different subnet from within this pool to ensure that the same subnet is not reused multiple times. If you deployment uses more subnets than are defined in this pool, the deployment will fail as all configured subnets are already used in this deployment.)

      • Master Subnet: The IP address of the first subnet in the tenant network.

      • Pool Subnet: A dropdown list to identify the last subnet in the tenant network.

      • Networks: This section automatically updates to reflect the number of networks in the pool based on the Master and Pool Subnet configurations.

      • You can add multiple subnet pools by clicking the Add Subnet Pool button.

      • Delete Icon: Allows you to delete a previously configured subnet pool from the CloudCenter platform.

        Once you add a subnet pool, you cannot update the pool. You can only delete the configured pool and add a new subnet pool.

  6. Click Save to save this new Bridge Domain Template along with the configured ACI extension. The Extensions page displays the Success message below the header to state the the extension is saved.

ACI Actions

Administrators can perform the actions that the following screenshot shows for each ACI extension listed in the Extensions page.

The Deployment Environment pages list configured information and allows you perform the actions that the following table describes.

Actions Dropdown
Description
Edit

Change configurations for an existing extension. Once configured, you can only perform the following changes to an Extension:

  • Change the name of the ACI Extension, URL, username, password as required.
  • Add a new Bridge Domain Templates for the extension.
  • Delete a configured Bridge Domain Template.

See the Adding a Deployment Environment section (below) for additional details.

Share

Share an Extension. See Permission Control > Extension Permissions for details.

Delete

Delete an Extension.

If you choose to delete a configured Extension, the Delete Extension popup confirms your intention, deletes the configured Extension, and displays a status message at the top of the Extension page.

Troubleshooting

If you set the cliqrIgnoreAppFailure parameter (see Troubleshooting Parameters), then the APIC resources (ANP, EPGs, Contracts, and so forth) created using the CloudCenter platform are not removed if the deployment fails. The launched VMs and related APIC policies are only removed when the user terminates the deployment from the Deployments page. See Terminate Protection for additional context.

© 2017-2019 Cisco Systems, Inc. All rights reserved