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.
This section describes how to deploy Cisco Dynamic Fabric Automation (DFA).
This section includes the following topics:
Your software release might not support all the features documented in this module. For the latest caveats and feature information, see the Bug Search Tool at https://tools.cisco.com/bugsearch/ and the release notes for your software release. To find information about the features documented in this module, and to see a list of the releases in which each feature is supported, see the “New and Changed Information” chapter.
Product | Function | Software Release (and later releases) | ||||
---|---|---|---|---|---|---|
Spine |
Leaf |
Border- Leaf |
RR3 | Other | ||
Cisco Nexus 6001 Series switch |
Yes |
Yes |
Yes |
Yes |
Cisco NX-OS Release 7.0(0)N1(1) |
|
Cisco Nexus 6004 Series switch |
Yes |
Yes |
Yes |
Yes |
Cisco NX-OS Release 7.0(0)N1(1) |
|
Cisco Nexus 7000 Series switch |
Yes1 |
— |
— |
Yes |
Cisco NX-OS Release 6.2(6b) |
|
Cisco Nexus 5672UP switch |
Yes |
Yes |
Yes |
Yes |
Cisco NX-OS Release 7.0(1)N1(1) |
|
Cisco Nexus 56128 switch |
Yes |
Yes |
Yes |
Yes |
Cisco NX-OS Release 7.0(2)N1(1) |
|
Cisco Nexus 5596UP switch |
— |
— |
— |
— |
Layer 2-only leaf |
Cisco NX-OS Release 7.0(0)N1(1) |
Cisco NX-OS Release 7.0(2)N1(1) supports the CLI-based auto configuration option |
||||||
Cisco Nexus 5548P and 5548UP switches |
— |
— |
— |
— |
Layer 2-only leaf |
Cisco NX-OS Release 7.0(0)N1(1) |
Cisco NX-OS Release 7.0(2)N1(1) supports CLI-based auto configuration |
||||||
Cisco Nexus 1000V switch for VMware vSphere 5.1 and 5.5 |
— |
— |
— |
— |
Virtual switch with VDP signaling |
Cisco NX-OS Release 4.2(1)SV2(2.2) |
Cisco Prime Data Center Network Manager (DCNM) |
— |
— |
— |
— |
Fabric management |
Cisco Prime Data Center Network Manager Release 7.0 |
Cisco Prime Network Services Controller (NSC) |
— |
— |
— |
— |
Services support |
Release 3.2 |
OpenStack for Cisco DFA |
— |
— |
— |
— |
(Optional) -Controller |
OpenStack for Cisco DFA 1.0 |
Review the other hardware and software components of your existing fabric with respect to the Cisco Dynamic Fabric Automation (DFA) release requirements and compatibility constraints. Because Cisco DFA implements an architectural solution with a switch topology that is different from what you have previously used, devices might be required to perform different roles when used in a Cisco DFA implementation, and might be subject to new licensing requirements. For more information, see the "Platform Requirements" section of this guide.
The fabric management network can support only one Dynamic Host Configuration Protocol (DHCP) server. You can use either the DHCP server in Cisco Prime Data Center Network Manager (DCNM) or another designated DHCP server, but not both.
To ensure that Cisco Unified Fabric Automation device auto configuration does not interfere with other DHCP servers on your network, we recommend that you use a dedicated VLAN and subnet for the fabric management network. Cisco Prime DCNM and the Ethernet out-of-band ports of the Cisco Unified Fabric Automation switches (mgmt0) reside in the fabric management network. You have the option to interconnect the fabric management network with your existing out-of-band management network.
The management connectivity for Cisco Unified Fabric Automation must come through the Cisco NX-OS device management interface (mgmt0).
The management port on any Cisco Unified Fabric Automation switch must be connected to the same management subnet that includes the Cisco Prime DCNM user interface.
Every Cisco Unified Fabric Automation switch to be managed by fabric management must be connected to the fabric management network through the Ethernet out-of-band network.
A console connection for fabric management is recommended but not required for Cisco Unified Fabric Automation.
If Cisco Prime DCNM is your repository server, you must upload the Cisco NX-OS kickstart and system images to Cisco Prime DCNM using the Serial Copy Protocol (SCP) or Secure File Transfer Protocol (SFTP).
Every Cisco DFA switch that is to be managed by Cisco Dynamic Fabric Automation (DFA) fabric management must connect to the fabric management network through the Ethernet out-of-band port (mgmt0).
The fabric interfaces of the Cisco Dynamic fabric Automation (DFA) fabric connect the Cisco DFA switches to one another. Fabric interfaces are configured with Cisco FabricPath Frame Encapsulation (FE) for efficient forwarding based on a Shortest Path First (SPF) algorithm. You do not configure VLAN trunking or pruning for the transported VLANs on Cisco DFA fabric interfaces .
To transport data traffic across the Cisco Dynamic Fabric Automation (DFA) Fabric, the leaf switch must receive the traffic for connected VLANs that are to be extended across the fabric. The leaf-to-server interfaces are called host interfaces.
Note | Always connect servers to Cisco DFA leaf or border leaf switches. You must not connect servers to Cisco DFA spine switches. |
The Cisco Prime Data Center Network Manager (DCNM) is the central point of management for Cisco DFA.
Note | If this is not a new Cisco Dynamic Fabric Automation (DFA) deployment, see the Cisco Dynamic Fabric Automation Migration Guide for migrating your existing fabric to a Cisco DFA deployment. |
Ensure that you have the appropriate Cisco Nexus devices with the minimum required Cisco NX-OS software releases to support Cisco Dynamic Fabric Automation DFA). See the "Platform requirements" section of this guide.
Install the Data Center devices. For information, see the appropriate install guides for your Cisco DFA switches.
Note | To deploy Cisco Prime DCNM, two port groups or port profiles are required on the virtual switch. |
Create a cabling plan and cable your Cisco Nexus devices for Cisco DFA. For information, see the "How to Cable the Network Fabric and Servers for Cisco DFA" section of this guide.
Install the Cisco Prime Data Center Network Manager (DCNM) Open Virtual Appliance (OVA) to manage all the applications for the central point of management. For information, see the Cisco DCNM 7.0 OVA Installation Guide.
Start the Prime NSC adapter in the Cisco Prime DCNM OVA and configure Services support for Cisco DFA. For information, see the "Network Services" section of the Cisco DCNM 7.0 OVA Installation Guide.
Note |
|