Cisco Cisco Prime Network Services Controller Adaptor for DFA White Paper

 

 

© 2015 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public Information. 

Page 22 of 46 

The trigger to download the end-host (physical or virtual) network configuration from DCNM to the physical leaf 

switch is based on the ARP, ND, DHCP or any other packet with a IEEE 802.1q tag or the exchange of VDP 

packets. Additionally, NX-OS provides the auto-pull command to allow the network operator to trigger the 

download and instantiation of a given tenant network configuration. The auto-pull option typically is helpful during 

the testing phases of a deployment or in deployments in which the network operator wants to distribute the tenant 

network configuration in the Cisco Unified Fabric consistently after the POAP process. The auto-pull command 

queries the LDAP database in the same way as the previously discussed trigger options. 

The example in Figure 24 shows how the network operator can download the workload-automation profile to the 

physical leaf switch. 

Figure 24.    Workload Automation Using Auto-Pull 

! 

LEAF# fabric database auto-pull dot1q <<VLAN>> interface e X/Y 

! 

The auto-pull command supports several interface options. To successfully instantiate a profile, the definition of a 

valid interface is required. The auto-pull command also can be used with the option vni instead dot1q. The vni 

option chooses the end-host-facing VLAN from the local pool, as discussed previously for VDP. 

Note:   If virtual PortChannel plus (vPC+) is configured on a pair of leaf switches, the end-host (physical or virtual) 
network profile is automatically synched between the vPC+ peer switches. Please see the detailed 

autoconfiguration description for vPC+ in the appendix. 

Figure 25 shows verification of the instantiated profile on a leaf switch. You can use the command show fabric 

database host independently for any kind of triggered tenant network configuration as well with the auto-pull 

command. The command shows the downloaded variables from the DCNM LDAP database along with the object 

classes. Note that the contents of the network profile (for example, defaultNetworkIpv4EfProfile) are also 

downloaded to the leaf switch. 

Figure 25.    Verification of the Instantiated Autoconfiguration Profile 

! 

LEAF# show fabric database host dot1q 77 

Got Local originated vlan type trigger at 20:36:04 

Number of associated interfaces: 2 

Sent to Database Manager at 20:36:02 

Received Parameters from Database Manager at 20:36:02 

Displaying parameters for profile defaultNetworkIpv4EfProfile and instance insta 

nce_def_77_77 

parameter 0: $gatewayIpAddress=10.10.77.254 

parameter 1: $netMaskLength=24