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 https://f5.com/cisco for updated information on the integration.
With customers deploying ACI with service insertion, people are constantly asking both design and implementation related questions such as:
When should I use 1 ARM vs 2 ARM topology for services?
Can I use BIG-IP in HA mode?
Can I use/share my existing BIG-IP with ACI?
My services and networking teams are separate, how can I maintain that business separation while using ACI?
How are elastic workloads addressed with BIG-IP and ACI?
We have had discussions with various customers and helped them deploy ACI with F5 service integration based on their network designs and topologies. From these discussions F5 and Cisco have boiled down the topics into a brief design guide.
Our design guide starts with an introduction of ACI and the benefits of using service insertion.We then go into the F5 device package features and supported functions. With the reader having a baseline understanding of ACI and F5 integration we discuss the design considerations for service insertion.
To help further your knowledge on F5 BIG-IP and Cisco ACI, the following references are also recommended:
