Cisco Cisco Prime Network Services Controller Adaptor for DFA White Paper
© 2016 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public Information.
Page 25 of 32
In addition, the next two sets of CLI output show the MAC address and the respective ARP entry of the load
balancer’s interface:
balancer’s interface:
Leaf-1# sh mac address-table vlan 331
Legend:
* - primary entry, G - Gateway MAC, (R) - Routed MAC, O - Overlay MAC
age - seconds since last seen,+ - primary entry using vPC Peer-Link
VLAN MAC Address Type age Secure NTFY Ports/SWID.SSID.LID
---------+-----------------+--------+---------+------+----+------------------
* 331 2020.0000.00aa static 0 F F sup-eth2
* 331 d867.d903.f345 dynamic 400 F F Eth1/1
Leaf-1#
Leaf-1# sh ip arp vrf OrganizationA:PartitionC
IP ARP Table for context OrganizationA:PartitionC
Total number of entries: 1
Address Age MAC Address Interface
10.10.20.2 00:00:09 d867.d903.f345 Vlan331
Leaf-1#
Deployment Scenario 4: Shared Hardware-Accelerated Application Delivery Controller with
VIP Address Directly Attached to Fabric
VIP Address Directly Attached to Fabric
Scenario 4 deploys an application load balancer along with a hardware-accelerated application delivery controller
(ADC). The ADC is equipped with hardware-accelerated encryption offload mechanisms and can be used as a
shared resource among multiple applications (Figure 18).
The load balancer can be either a physical appliance or a virtual appliance. In the latter case, it should be able to
offload SSL encryption from the virtual load balancer to a physical hardware-accelerated ADC.
Figure 18. Logical Schema Showing the Load Balancer and Hardware-Accelerated ADC Connection to the Service Leaf