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 28 of 32 

Refer to deployment scenario 1 of this document for details about how to create the autoconfiguration profiles. 

Note that both the load balancer and the hardware-accelerated ADC must be members of the same partition to 

successfully communicate within the fabric. 

Deployment Considerations for vPC+ Dual-Attached Appliances  

If the load-balancer appliance needs to be dual homed, additional network autoconfiguration profile configuration is 

required for deployment scenario 2. Deployment scenarios 1 and 3 require no additional changes. 

In deployment scenario 2, the load balancer needs to establish and maintain OSPF dynamic routing adjacency with 

both vPC+ peer switches: Leaf-1 and Leaf-2 (Figure 21). 

Figure 21.    vPC+ Dual-Attached Load Balancer Establishes OSPF Routing Adjacency with Both vPC+ Peer Switches 

 

The OSPF routing protocol requires a unique IP address to establish such routing adjacency. That is why the 

network autoconfiguration profiles need to include additional detail. 

Figure 22 shows the Secondary Gateway IPv4 Address field. The autoconfiguration process will use the IP address 

specified in this field to configure the SVI IP address on a secondary vPC+ peer. The primary vPC+ peer is 

configured with the value specified in the gatewayIpAddress field.