The adoption of Cisco ACI with the APIC controller continue to gain traction in the market.  With their latest major APIC release, 1.2.1i , Cisco has streamlined how ADCs are connected to the fabric.    There have traditionally been two methods of connecting services:

  1. Service Insertion with a device package and a service graph (Managed)
  2. Connecting a device as an endpoint device into an EPG (Unmanaged)

What Cisco has done is simplified how a services device can be connected into the fabric as an Unmanaged device to the APIC.  This is known as “Unmanaged  Mode” vs the “Managed Mode” where a device package is used. 

Instead of the usual multi-step manual configuration process for specifying the network configuration in APIC, the attachment has been consolidated into the service graph.  Before it was necessary to manually static bind the VLAN to the EPG (Provider and Consumer) and assign the physical domain to the EPG. It was also required to bind contracts between multiple Provider and Consumer EPGs. Now, all you have to do is go into the service graph and specify connectivity just like you were building a managed service graph.  By doing this, there is now one common location and workflow for configuring services.  The process is simplified.

Advantages

  • Service graph representation with Unmanaged  and Managed modes mixed  (few devices managed by APIC, few devices NOT managed by APIC)
  • Unified view of a service chain

Why needed

  • Customers have requested to provide “Unmanaged ” mode for their custom devices
    • Need to manage their own security policies outside of the networking team
    • Need to use their existing orchestration infrastructure for a particular devices in the chain
    • Need to use advanced vendor specific functionality

What this means for BIG-IP integration

  • BIG-IP is attached as an EPG - but now being able to represent this mode within a service graph

Difference between Managed and Unmanaged mode

Mode

Goal

Unmanaged  Mode
(Device managed externally)

  • Service Chaining (traffic redirection) through ACI

Managed Mode
(Device managed by device package)

  • Service Chaining (traffic redirection) through ACI
  • Device configuration through APIC (Policy based configuration)

 

Some prerequisites for deploying an Unmanaged logical device cluster

  • BIGIP:
    • Define VLANS, Self IP’s and trunk (if needed)
  • APIC:
    • VLAN Pool – Static allocation
    • Fabric access policies to ensure physical connectivity to BIGIP

Click here to view a video with more details on how to deploy a BIGIP in Unmanaged mode on APIC

https://www.youtube.com/watch?v=OJPEYzNGD3A

Once deployed as an Unmanaged device cluster with traffic redirection through ACI configure your BIGIP with nodes, pools, monitors, virtual servers and all other features required by your application like you always do by using the BIG-IP GUI/CLI etc (not through the Cisco ACI)

References:

http://www.cisco.com/c/en/us/td/docs/switches/datacenter/aci/apic/sw/1-x/L4-L7_Services_Deployment/guide/b_L4L7_Deploy_ver121x/b_L4L7_Deploy_ver121x_chapter_010000.pdf

http://blogs.cisco.com/datacenter/new-innovations-for-l4-7-network-services-integration-with-ciscos-aci-approach