
14
Reference Architecture | Dynamic L4-L7 Service Insertion with Cisco ACI and A10 Thunder ADC
The A10 device package enables Cisco APIC to configure ADC server load balancing configuration parameters
defined in the service graph configuration. In this example, the service graph allows the user to configure the
following parameters for A10 Thunder ADC load balancing service:
• Multiple real servers with IP address, port number, etc.
• Service-group to pool multiple real servers into a group
• Virtual server IP (VIP) for application services
• Health monitoring rules to monitor the state of real servers
• Network Address Translation (NAT) pools to perform source and destination address translation
The service graph itself can be configured either through the APIC GUI or can be configured through an XML
post to the APIC. The service graph configuration requires some parameters that are marked as mandatory,
for example the virtual server name, IP address and port number. The user can configure one or more
service graph templates under the tenant; however, the service graph renderings are done only when the
graph is applied to a security contract as shown in Figure 15. When the service graph is rendered, the APIC
communicates with the A10 device using aXAPI commands and configures interfaces, VLANs and server
load balancing specific configuration parameters. The A10 device package makes the distinction between a
physical A10 device and virtual A10 device so that the Ethernet interface on the A10 device can be configured
as a tagged or untagged port. Figure 14 shows the ADC configuration in the APIC once the graph has been
associated with a contract.
Figure 14: Service graph showing L4-L7 function node conguration
Figure 15 shows how the graph is associated with a contract. EPGs can only communicate with other EPGs
as per the contract rules, and inter-EPG communication is disabled by default in ACI. The function node gets
inserted in inter-EPG communication through the service graph.
Kommentare zu diesen Handbüchern