F5 Logo MyF5
Search
  1. MyF5 Home
  2. Knowledge Centers
  3. BIG-IQ Cloud and Orchestration
  4. BIG-IQ Cloud: Cisco APIC Administration
  5. Integrating with Cisco APIC
Manual Chapter : Integrating with Cisco APIC

Applies To:

Show Versions Show Versions

BIG-IQ Cloud and Orchestration

  • 1.0.0
Manual Chapter
Table of Contents | << Previous Chapter | Next Chapter >>

BIG-IQ and Cisco APIC Integration

About F5 and Cisco APIC integration

F5® products integrate with Cisco Application Policy Infrastructure Controller (APIC) using a Device Package. The F5 BIG-IP® Device Package for Cisco APIC downloads from a BIG-IQ device, and then is imported into APIC. The file contains:

  • A device model, which describes the features and functions available to APIC on the BIG-IP system
  • A device script, which implements the features and functions described by the device model

APIC is built with a standard application programming interface (API) used to configure services implemented by integrated vendor devices, such as F5. The F5 BIG-IP device package for Cisco APIC implements the API specific to the semantics of the BIG-IP system.

Using Cisco APIC, a customer can configure tenants, device clusters containing one or two BIG-IP devices, and service graphs. When a service graph is pushed to the BIG-IP system, the F5 BIG-IP Device Package for Cisco APIC running on Cisco APIC uses iApps® to configure all aspects of the supported service.

Each Tenant context is assigned a unique partition on the BIG-IP system, in the form of apic_XXXX, where XXXX is the Tenant ID. Similarly, each Tenant is assigned a random, unique route domain ID. After successfully deploying a service graph on the BIG-IP system, you can log in to the BIG-IP system to view the configuration.

Cisco APIC uses a single admin-level userid and password to configure the BIG-IP system on behalf of all tenants. Tenants are not expected to log in to the BIG-IP system to diagnose issues: that is the responsibility of the provider administrator.

When you are choosing BIG-IP devices to integrate with Cisco APIC, F5 recommends you use dedicated device(s), and not a BIG-IP system that is already being used (or will be used) for another purpose. This is mainly because parts of this configuration, especially the device cluster HA setup, are managed by the device package.

logical flow between Cisco APIC and the BIG-IP system

The logical flow between Cisco APIC and the BIG-IP system

  1. An administrator uses the northbound API or the user interface on APIC for configuration.
  2. Service graphs created with the device package cause APIC to push configuration to the BIG-IP system, ascertain health, and obtain statistics (interface counters).
  3. The APIC API for L4-L7 services is implemented by the F5 device script.
  4. The device script uses iApp calls to translate the standard APIC API calls into BIG-IP system calls to implement the service.
  5. Status and information from these calls are packaged and returned to APIC for processing.

APIC-related documentation

  • For detailed information about Cisco ACI, see http://www.cisco.com/c/en/us/solutions/data-center-virtualization/application-centric-infrastructure/index.html.
  • For detailed information about Cisco APIC, see http://www.cisco.com/c/en/us/products/cloud-systems-management/application-policy-infrastructure-controller-apic/index.html
  • For more information about APIC, refer to your Cisco APIC documentation set.

About network topology using the BIG-IP system integrated with Cisco APIC

apic network topology

A typical network topology using the BIG-IP® system integrated with Cisco ACI

The internal and external interfaces on the BIG-IP system are connected to leaf nodes in the ACI architecture. Items such as web servers, database engines, and application tiers are also connected to leaf nodes. Spine nodes handle the routing between the BIG-IP system and the various other end points necessary to deliver an application service.

The management port of the BIG-IP system is connected out-of-band to a switch outside of the ACI architecture (not shown in the diagram) to provide management access.

This diagram is not meant to illustrate all possible architectures but rather communicate a typical architecture showing where the BIG-IP system fits into the Cisco ACI architecture.

Important: Make sure you are using the most recent version of this guide, available at http://www.askf5.com.

Version requirements

Be sure your environment meets or exceeds the requirements described here before you integrate the F5® BIG-IQ® Cloud with Cisco APIC.

  • Cisco APIC and Switch software .
    Note: Some features and functions described in this guide require APIC version 1.2. These features will be noted as encountered.
  • F5 BIG-IQ Cloud version 1.0.

Minimum Cisco APIC requirements

Be sure your environment meets or exceeds these requirements before you integrate the F5® BIG-IQ® Cloud with Cisco APIC.

  • You must have access to an administrator-level account on the Cisco APIC.
  • All external network configuration must be complete.
  • The Layer 3 networks must be defined and operational.
  • The initial configuration of APIC and ACI must be complete. This includes racking and cabling the hardware, powering on the devices, installing the Cisco APIC and Switch version v1.1 (or v1.2) software, configuring the management IP address and verifying that it is reachable.
  • The AAA configuration (such as RADIUS or LDAP) must be completed and operational. You might need to create an application EPG to reach external AAA servers to verify the AAA configuration is functioning properly.
  • Any APIC tenants, security domains, private network(s), bridge domain(s), and related objects must be configured and operational.
  • Any inter-EPG application filters, contracts, and application profiles (if needed) to facilitate traffic flow between EPGs must be created.
  • You must have created a management EPG, which is required for APIC to reach the management IP addresses of the BIG-IP® system(s).
  • If you are testing multi-tenancy, you must have access to an account assigned to a tenant.
  • If you plan on using the BIG-IP Virtual Edition (VE) in your environment, you must have created a Virtual Machine Mobility (VMM) domain and configured vCenter integration.
  • If you plan on using a physical BIG-IP appliance in your environment, you must have created a physical domain.

Refer to the Cisco APIC Layer 4 to Layer 7 Services Deployment Guide for specific details about how to configure APIC.

Minimum F5 BIG-IP requirements

Be sure your environment meets or exceeds these requirements before you attempt to integrate the F5® BIG-IQ® Cloud with Cisco APIC. Refer to the BIG-IP® system documentation on the F5 technical support site (http://support.f5.com/kb/en-us/products/big-ip_ltm.html) for specific information about how to configure the BIG-IP system to meet these requirements.

  • You must have access to an administrator-level account on the BIG-IP system.
  • The BIG-IP system must be running version 11.5.3 HF2 or version 11.6.0 HF6.
  • The BIG-IP system must be cabled to a leaf switch and powered on (if using an appliance) or started in a VMware environment (if using a Virtual Edition).
  • You must have discovered the BIG-IP devices you plan to use with the BIG-IQ system.
Important: Although you can discover BIG-IP devices from BIG-IQ Device, successful integration with the Cisco APIC requires that you perform discovery using BIG-IQ Cloud.

About configuring the BIG-IQ device for a Cisco APIC integration

Some of the tasks you perform to deploy BIG-IQ® Cloud in a Cisco APIC environment are performed on the BIG-IQ device. You discover devices, create a connector and a custom template, and then export a device package. This device package is the key element of the integration from the Cisco APIC perspective. The parameters and values communicated when you import the package contains the configuration information the Cisco environment needs to perform the integration.

Adding a Cisco APIC connector

Before you add a Cisco APIC connector, you must discover the F5 devices that you plan to include in your Cisco APIC integration.
To enable integration between an APIC and BIG-IQ® Cloud, you must create a connector. A cloud connector is a resource that identifies the local or virtual environment in which a tenant deploys applications and, when necessary, adds parameters required by third-party cloud providers.
Important: Do not create more than one Cisco APIC connector.
  1. Log in to BIG-IQ® Cloud with the administrator user name and password.
  2. Hover over the Connectors header, and click the + icon when it appears..
    The New Connector screen opens.
  3. In the Name and Description fields, type a name and description.
    You can use the name and description to help you organize network resources into logical groups based on certain criteria, such as the location or application.
  4. From the Cloud Provider list, select Cisco APIC.
  5. Click the Save button.

Creating a customized application template

Before you can customize an application template for a tenant, you must discover the F5 devices that you plan to include in your Cisco APIC integration, and add a Cisco APIC connector.

An iApp is an application template located on F5 devices. When you discover an F5 device, all iApps® application templates installed on that device are imported to the BIG-IQ® system.

You must create at least one custom catalog template, based on an iApps template, that provides the network settings, levels of services, and so forth, that you expect to see in your APIC environment. You can modify the base template, choosing default values for selected parameters and specifying which parameters can be edited by the tenant. The values specified in the application templates you create are included in the device package that you export to Cisco APIC.

Note: Once you customize and save an application as a catalog entry, you cannot modify it.
Important: If you make modifications to an iApp, you need to save it with a new name. Once an iApp has been imported, it will not be imported again. When an iApp with a new name is saved on a managed BIG-IQ device, BIG-IQ software imports it automatically.
  1. In the BIG-IQ Cloud system, hover over the Catalog header and click the + icon when it appears.
    The New Template screen opens.
  2. In the Name field, type a name for this new template.
  3. For the Input Parameters, select the option that displays the parameters you want to work with.
    The setting you choose here determines which parameters from the base template that you select display in subsequent fields and areas on the screen.
    • Select Accept Defaults if you do not want to edit any parameters.
    • Select Common Options if you only want to edit a subset of the template parameters. This option displays parameters that:
      • are marked as tenant-editable
      • describe the virtual server or pool
    • Select All Options to view all of the parameters for the template you select. You can then expand individual template sections, or click Expand All to view every parameter in every section.
  4. For the Cloud Connector select the APIC connector you created earlier.
  5. From the Application Type list, select the base template that contains the parameters that provide the network settings and levels of services that you want to have available in your APIC environment.
  6. Expand sections as necessary and then specify parameter values as needed. You can provide default values in that column, and select which parameters the user can revise.
    Tip: The template options that you can view depend on which option you chose in step 3.
    Important: There are two parameters that you must select as Tenant Editable: the parameter that identifies the pool address and the parameter that defines the pool member table. You can specify default values and allow user revision for as many parameters as you want. The names of these two parameters varies from one template to the next.
  7. Click the Save button.
You can now use this connector to complete the Cisco APIC integration.

Creating a custom device package

Before you create a device package, you must discover BIG-IP® devices, then create a Cisco APIC connector and an application template.
To enable integration between a APIC and BIG-IQ® Cloud, you must create a device package that Cisco can import. A device package is a resource that the Cisco architecture parses and uses to identify the network resources needed to suit your integration requirements.
  1. In the BIG-IQ Cloud system, in the Connectors panel, hover over the name of the connector you created previously, click the gear icon (gear), and then select Properties.
    The screen displays properties for that connector.
  2. Under APIC Device Package, click the F5DevicePackage.zip link.
    The zip file will be copied to your Downloads folder.
  3. Click the Save button.

About configuring the Cisco APIC for BIG-IQ integration

After you finish configuring BIG-IQ® Cloud for integration, there are some tasks to perform in the Cisco APIC environment to complete the integration. You install the device package, create a device cluster, and then create a service graph.

A device cluster is a logical representation of one or more concrete devices acting as a single device. Concrete devices are physical (or virtual) BIG-IP® devices added to the device cluster. For more information, refer to the Cisco APIC documentation.

Installing the F5 BIG-IP device package on Cisco APIC

Before you install the F5® BIG-IP® device package on your Cisco APIC, you must have fully set up and configured your Cisco APIC environment.
Install the BIG-IP device package after you have downloaded the device package but before you create device clusters.
Note: The steps and illustrations in this task make reference to the Cisco APIC version 1.1. Controls of the version 1.2 user interface are likely to differ slightly.
  1. Log into Cisco APIC as an administrator.
  2. On the menu bar, click L4-L7 SERVICES, and then click PACKAGES.
  3. In the right pane, click Import a Device Package.
    apic import device package

    Importing the Device Package

  4. Click BROWSE, and then navigate to the location where you downloaded and saved the device package.
  5. Click SUBMIT to start the installation process.
  6. Once the installation is complete, verify the device package is accepted by APIC.
    1. In the left pane, click L4-L7 Service Device Types to open the folder.
    2. Click the device service package that you want, such as F5-BIGIQ-2.0, to expand the F5 BIG-IQ device package for Cisco APIC.
    3. Click L4-L7 Service Functions.
    apic device package imported

    Verifying successful installation of the package

Once the F5 BIG-IQ device package is successfully installed, you are ready to use Cisco APIC to deploy the services supported by the custom iApp templates you created previously. Each template you created is represented by a unique service package listed under L4-L7 Service Types > L4-L7 Services Function Profiles .
After you install the device package, you must fully configure your base Cisco APIC network settings. Consult your Cisco documentation for details. At a minimum you must:
  • Confirm that you have specified the tenants for whom you plan to make services available. If you have not, then create and configure those tenants.
  • Create and configure the end point groups and bridge domains that your tenants require.
  • Create the Physical Domain with associated VLAN and VXLANs name space.

About Chassis Manager and Device Manager

For Cisco APIC version 1.2 users, you can use Device Manager and Chassis Manager to extend the function of the Cisco APIC user interface to provide support for BIG-IQ® high availability and vCMP®.

If you are going to enable Device Manager and Chassis Manager, you must do so before you create the device cluster.

Enabling the Device Manager
You need to know the name of the APIC connector so that you can correctly form the content of the XML file used as part of this task.
The Device Manager makes it possible for you to specify the parameters needed to support BIG-IQ® HA. When you enable Device Manager on a Cisco APIC Version 1.2, additional controls are added to the device cluster user interface so you can add the necessary configuration details.
  1. Use a text editor to create an XML file named CreateMDevMgr.xml.
    Use the following for the file content, replacing <APIC-Connector> with the name of the APIC connector you created on the BIG-IQ system. 
    <polUni>
  <infraInfra>
    <vnsMDevMgr vendor="F5" model="BIGIQ" version="2.0-<APIC-Connector>">
      <vnsRsMDevMgrToMDev tDn="uni/infra/mDev-F5-BIGIQ-2.0-<APIC-Connector>" /> 
    </vnsMChassis>
  </infraInfra>
</polUni>
  2. Submit a REST POST containing your login credentials to the APIC API.
    The API response contains an authentication cookie.
  3. Submit a REST POST to the Cisco APIC API, including the authentication cookie in your HTTP header and the content of CreateMDevMgr.xml in the payload.
    Form your post as shown in the following example, replacing <apic-ip> with the IP address of the Cisco APIC. POST https://<apic-ip>/api/node/mo/.xml
The Cisco APIC processes the POST and enables the Device Manager.
Enabling the Chassis Manager
You need to know the name of the APIC connector so that you can correctly form the content of the XML file used as part of this task.
The Chassis Manager makes it possible for you to specify the parameters needed to support vCMP® guests on BIG-IQ® Cloud. When you enable Chassis Manager on a Cisco APIC Version 1.2, additional controls are added to the device cluster user interface so you can add the necessary configuration details for the vCMP devices.
  1. Use a text editor to create an XML file named CreateMChassis.xml.
    Use the following for the file content, replacing <APIC-connector> with the name of the APIC connector you created on the BIG-IQ. 
    <polUni>
  <infraInfra>
    <vnsMChassis vendor="F5" model="BIGIQ" version="2.0-<APIC-Connector>">
      <vnsRsMChassisToMDev tDn="uni/infra/mDev-F5-BIGIQ-2.0-<APIC-Connector>" /> 
    </vnsMChassis>
  </infraInfra>
</polUni>
  2. Submit a REST POST containing your login credentials to the APIC API.
    The API response contains an authentication cookie.
  3. Submit a REST POST to the Cisco APIC API, including the authentication cookie in your HTTP header and the content of CreateMChassis.xml in the payload
    Form your post as shown in the following example, replacing <apic-ip> with the IP address of the Cisco APIC. POST https://<apic-ip>/api/node/mo/.xml
The Cisco APIC processes the POST and enables the Chassis Manager.

Creating a device cluster for BIG-IP devices

As part of the BIG-IQ® Cloud and Cisco APIC integration, you need to create an L4-L7 device cluster. Creating the cluster using the F5 Device Package tells APIC a number of things about the F5 devices:

  • Their network topology
  • Access credentials
  • IP addresses
  • Configuration details

Additionally, when you create the device cluster, you specify all of the configuration details that Cisco APIC needs for the cluster.

  1. In the Cisco APIC user interface create an L4-L7 device cluster.
    For details on the correct settings to specify when you create the cluster, refer to Device cluster creation guidelines.
    Important: BIG-IQ Cloud, version 1.0 supports Cisco APIC version 1.1 and 1.2. Because the user interface for these versions vary significantly, and version 1.2 is still in flux at the time of this release, refer to the Cisco APIC user documentation for details on creating the L4-L7 device cluster.
  2. When the parameters for the new device cluster are correctly specified, click SUBMIT to start the device cluster creation.
Cisco APIC processes the information you provided and creates the device cluster. After a pause, the Device State displays Init, and then eventually changes to Stable.
Note: Do not be alarmed if this process takes some time. It can take several minutes to complete.
Device cluster creation guidelines

When you create the APIC device cluster, there are a number of parameter settings to specify. The following table serves as a guide for specifying the correct settings for a BIG-IQ® Cloud integration.

Parameter Factors to consider when specifying
Tenant

Choose the tenant for whom you want to create the device cluster.

  • If the BIG-IP® devices are to be shared between tenants, choose the pre-configured management tenant.
  • If the BIG-IP devices are to be used by a single tenant, choose that tenant.
L4-L7 device Specify the F5 BIG-IQ® device package that you imported.
Model

Select the model that best describes the BIG-IP device that will service your applications.

The model you choose also controls which interfaces you can select.

  • Select BIG-IP GENERIC if you are connecting to a physical BIG-IP device.
  • Select BIG-IP VE-GENERIC if you are connecting to a BIG-IP Virtual Edition (VE) that is part of the APIC fabric.
  • Select Unknown (Manual) if the interfaces you need do not show up.
Mode Select single node if you have a single BIG-IP device in the cluster, or HA Cluster if you have two BIG-IP devices in a cluster.
Physical Domain Select the physical domain you created previously.
APIC to Device Management Connectivity Select Out of Band.
Credentials Specify a BIG-IQ user with administrative privileges.
Important: For APIC version 1.1 users, the user name and password must be the same for both the BIG-IP Cloud and the BIG-IQ devices you intend to add to the device cluster instance.
Device

Specify the management IP address for the BIG-IP device.

Select https for the management port.

Identify each of the physical interfaces that connect to the ACI fabric.
Cluster
Important: BIG-IQ Cloud, version 1.0, supports Cisco APIC version 1.1 and 1.2.

For Cisco APIC version 1.1 users:

  • If the F5 devices are either physical BIG-IP devices or BIG-IP Virtual Edition (as opposed to vCMP® guests), you can use BIG-IQ Cloud version 1.0 with one BIG-IQ device, but there is no support for BIG-IQ HA.
  • If the F5 devices are vCMP guests, there is no support for using BIG-IQ Cloud, version 1.0.
  • If the F5 devices are vCMP guests, you must use the same credentials for both the vCMP guests and the vCMP host.

For Cisco APIC Version 1.2 users, you can use Device Manager and Chassis Manager to extend the function of the Cisco APIC user interface to provide support for BIG-IQ HA and vCMP.

  • Use the Device Manager to extend the Cisco APIC user interface so that you can specify multiple BIG-IQ Clouds and use different credentials for the BIG-IQ and BIG-IP devices. Refer to Enabling the device manager for details.
  • If you specify multiple BIG-IQ hosts, they must be in the same BIG-IQ HA cluster so that if one is down, the device package can contact one of the other hosts in the cluster.
  • Use the Chassis Manager to extend the Cisco APIC user interface so that you can specify unique credentials for the vCMP host and guest. Refer to Enabling the chassis manager for details.
Device Configuration For each parameter you want to specify for the device, double-click the parameter and specify the value. The device package configures the BIG-IP Cloud appropriately.
  • Use the device host configuration to set common parameters such as the host name, NTP server, and DNS server.
  • In most cases you will not need to specify the DeviceInterface or DeviceRoute parameters: these values are provided as part of the service graph.
  • The HighAvailability parameters are required when you have a device cluster with two BIG-IP devices.
  • For APIC version 1.1 users, if the BIG-IP devices are vCMP guests:
    • vCMP® configuration is a required parameter.
    • The vCMP host must use the same IP address as the cluster host.
    • The vCMP guests must reside on the same vCMP host.
  • For APIC version 1.2 users, vCMP parameters are specified using the Chassis Manager.

Viewing the device cluster you created

You might want to view the device cluster to confirm that you successfully created it before you export it to the tenant.
  1. On the menu bar, click TENANTS, and then click the tenant for whom the device cluster was created.
  2. In the left pane, expand the Tenant folder and then the L4-L7 Services folder.
  3. Click Device Clusters.
You should be able to view the device cluster you created.

Exporting the device cluster to a tenant

An APIC administrator can choose which tenant(s) are permitted to use the device clusters created in APIC. Use the following steps to export a device cluster to a tenant.
  1. On the menu bar, click TENANTS.
  2. From the sub-menu, click the tenant where the device cluster was created. In our example, we created the device cluster in the management tenant, so click mgmt.
  3. In the left pane, expand the Tenant folder and then the L4-L7 Services folder.
  4. Click L4-L7 Devices.
  5. From the ACTIONS list, select Export Device Cluster.
  6. From the Device Cluster list, select the device cluster you want to export.
  7. From the Tenant list, select the tenant to which you want to export the device cluster.
  8. In the Description field, you can optionally type a description.
  9. Click SUBMIT.
    exporting device cluster

    Exporting the device cluster

You should be able to view the device cluster you exported.

apic imported device clusters

Viewing the device cluster

You can repeat these steps if you want to export the same device cluster to multiple tenants. This functionality is useful for assigning BIG-IQ® resources in your network to meet your end-user's requirements.

About service graphs

A service graph is a single listener (virtual server) with its associated configuration objects that are required to allow traffic to go through the BIG-IP® system to a destination pool and the nodes in that pool.

The virtual server itself is unique, so each service graph is one virtual server. You can associate configuration objects and you can share some of those objects between the service graphs (virtual servers). The virtual server port, protocol, and IP address are all unique.

A multigraph means that a BIG-IQ system has multiple service graphs that are associated with a single tenant on the BIG-IQ device.

Creating a service graph
Creating a service graph provides you with the controls for specifying the parameters defined by the iApp template you created for this integration.
  1. On the menu bar, click TENANTS.
  2. From the sub-menu, select the tenant in which you want to create the service graph, for example, Customer1.
  3. In the left pane, expand the Tenant folder and then the L4-L7 Services folder.
  4. Right-click L4-L7 Service Graph Templates, and then click Create a L4-L7 Service Graph Template.
  5. In the Name field, type a name for the service.
  6. From the Type list, select an appropriate type.
    This setting determines the node configuration. Select either Single Node - ADC in One-Arm Mode or Single Node - ADC in Two-Arm Mode, depending on your requirements.
  7. For the Device Function, select the entry with the name that matches the catalog template you created on the BIG-IQ® device.
  8. For the Profile, select the entry with the name that matches the catalog template you created on the BIG-IQ device.
  9. Click SUBMIT.
    The system creates the service graph template as you specified it, and displays a model of it on screen.
At this point, the configuration has not yet been pushed to the BIG-IP® system(s); this occurs once you deploy the service graph.
Selecting your service graph for deployment
Deploying the service graph applies the parameter values to the BIG-IP® devices that are part of this integration.
  1. On the menu bar, click TENANTS.
  2. From the sub-menu, select the tenant that contains the service graph.
  3. In the left pane, expand the Tenant folder and then the L4-L7 Services folder.
  4. Expand the L4-L7 Service Graph Templates folder.
  5. Right-click the service graph you created, and then select Apply L4-L7 Service Graph Template.
    apply l4-l7 service graph template

    Applying the service graph template

Applying the L4-L7 service graph template
After selecting the service graph for deployment, you edit the service graph, EPGs, and contracts.
Note: The following figure depicts the APIC version 1.1 user interface. The interface for version 1.2 will likely be slightly different.
apic l4-l7 service graph template

Applying the service graph template to EPGs

  1. From the Consumer EPG list, select the appropriate EPG.
  2. From the Provider EPG list, select the appropriate EPG.
  3. In the Contract Information area, either select the appropriate existing contract, or create a new one.
  4. Click NEXT.
    The L4-L7 SERVICE GRAPH TEMPLATE TO EPGS screen displays so that you can configure the graph parameters. The parameters and default values that display are the ones you configured on the BIG-IQ device. You can revise the parameters that you marked as tenant editable.
  5. Under Device Config on the ALL PARAMETERS tab, configure the self IP addresses and floating IP addresses needed for each BIG-IP device in the cluster.
    • If the BIG-IP devices are in an HA pair, configure internal and external self IP addresses for each BIG-IP device. Also; configure internal and external floating IP addresses for each HA pair.
    • If the BIG-IP devices are standalone, only the internal and external self IP addresses for each BIG-IP device are needed.
  6. Under Function Config on the ALL PARAMETERS tab, configure (at least) the required parameters for the iApp template you used to create the device package.
    At a minimum, you must specify the parameter that identifies the pool address and the parameter that defines the table of pool members.
  7. Click FINISH to complete the process.
    The APIC deploys the iApp using the BIG-IQ device that you specified to the BIG-IP device(s) you specified.

If you log in to the BIG-IQ® device and look at the Applications tab, you can confirm that the application deployed successfully.

If you log in to one of the BIG-IP® devices and look at the iApps > Application Services screen, you can confirm that the iApp deployed successfully.

Note: The iApps® are not placed in the Common partition. Instead, the Cisco APIC integration places the iApp in a new partition. Navigate to the new partition before you look to confirm deployment.
Table of Contents | << Previous Chapter | Next Chapter >>
Contact Support Contact Support

Have a Question?

Support and Sales >

About F5

Education

F5 Sites

Support Tasks




©2023 F5 Networks, Inc. All rights reserved.


Trademarks Policies Privacy California Privacy Do Not Sell My Personal Information