Step-By-Step Deployment Guide - BIG-IP Service Insertion process with Cisco ACI [End of Life]

The F5 and Cisco APIC integration based on the device package and iWorkflow is End Of Life.
The latest integration is based on the Cisco AppCenter named ‘F5 ACI ServiceCenter’.
Visit for updated information on the integration.

Hi Cisco ACI followers!!!  There is a lot of information about Cisco ACI and APIC, but not so much about service insertion for Layer 4-7 services and how to properly deploy it. If you are already knee deep in a current deployment, planning for a new deployment, or even just looking to understand how it is done, check out our design guide as well as deployment guide for BIG-IP and ACI.

Click here to view the design guide


Click here to view the deployment guide


The guide provides step by step instructions on configurations needed for Day 0, Day 1 and Day 2 operations. It talks about how to physically connect the BIG-IP to the ACI fabric, how to import a device package into the APIC, how to enable APIC and BIG-IP to communication and really how to manage the BIG-IP configurations (network and application) via the APIC.

The guide has some great tips on how to troubleshoot the service insertion process and also provides insight on the upgrade path from one device package to another.

Step by step guidance to deploy the following scenarios are covered:

  • One ARM Service Insertion
  • Two ARM Service Insertion
  • Two node graph (ASA + F5)
  • End Point Group mode

Some Videos to help you understand more

Published Dec 11, 2015
Version 1.0

Was this article helpful?

1 Comment

  • Joad's avatar
    Icon for Nimbostratus rankNimbostratus

    Hi Payal,

    I don't have any knowledge about f5/Cisco APIC integration.

    I read that BIG-IP LTM can be deployed only in Go-to mode in Cisco APIC, where F5 serves as a default gateway to all traffic in both one-arm and two-arm modes.

    This mean that if my f5 is not the default gateway, I can't integrate it with APIC?

    Thank you