The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
Contents
This chapter contains the following sections:
Cisco Dynamic Fabric Automation (DFA) simplifies a cloud deployment through automated provisioning and centralized management. Cisco DFA automates device and fabric configuration, eases virtual machine (VM) deployment and migration, and integrates baremetal and virtualized resources without using a dedicated gateway.
For more information about Cisco DFA, see http://www.cisco.com/c/en/us/products/cloud-systems-management/dynamic-fabric-automation/index.html.
The Cisco Nexus 1000V acts as a leaf extension in the Cisco DFA network. The Cisco Nexus 1000V is configured as an end station in the DFA network and uses VSI Discovery and Configuration Protocol (VDP)-based communication to notify the DFA leaf of a VM instantiation or a VM mobility event.
The components of the Cisco DFA architecture are as follows:
Leaf switch—A DFA leaf node operates as the bridge for the VDP exchange that handles requests from end hosts. The leaf node also communicates with the configuration profile databases to retrieve and apply the previously defined port profiles to each attached end host.
End station—An end station in Cisco DFA can be VDP capable or incapable. A VDP-capable end station operates as the primary station for the VDP exchange and registers or deregisters its resident VMs to the attached leaf switch. A VDP-incapable end station is a normal server node that does not participate in the VDP message exchange.
Profile database—This database is a standalone server or a local configuration storage in the leaf switch that maps each end host to its predefined port profile. This profile can be VLAN, ACL, or QoS.