Dell Fabric Manager Deployment Guide 1.0.
Notes, Cautions, and Warnings NOTE: A NOTE indicates important information that helps you make better use of your computer. CAUTION: A CAUTION indicates either potential damage to hardware or loss of data and tells you how to avoid the problem. WARNING: A WARNING indicates a potential for property damage, personal injury, or death. Information in this publication is subject to change without notice. © 2012 Dell Inc. All rights reserved.
Contents Notes, Cautions, and Warnings...................................................................................................2 1 Introduction..................................................................................................................................7 Conventional Core Versus Distributed Core.............................................................................................................7 Conventional Core..........................................................
Pre-Deployment – Step 3: Management IP ...........................................................................................................29 Pre-Deployment – Step 4: Software Images ..........................................................................................................30 Pre-Deployment – Step 5: DHCP Integration..........................................................................................................30 Pre-Deployment – Step 6: Output................................
Settings...................................................................................................................................................................59 TFTP Settings...................................................................................................................................................59 Syslog IP Addresses........................................................................................................................................
Introduction 1 Dell Fabric Manager (DFM) is a graphical user interface (GUI) based network automation and orchestration tool that allows you design, build, deploy, and optimize a distributed core for your current and future workload requirements. This tool helps you simplify network operations, automate tasks, and improve efficiency in the data center and campus environments. DFM supports Dell Z9000 and S4810 switches.
Distributed Core A distributed core is a two-tier architecture composed of multiple switches interconnected to provide a scalable, highperformance network that replaces the traditional and aggregation layers in a conventional core. Switches are arranged as spines and leaves; the spines interlink (connect) the leaves together using a routing protocol. The leaves’ edge ports connect to the switches, ToR switches, servers, other devices, and the WAN.
Key Advantages The key advantages of a distributed core architecture are: • Simplified fabric • Higher bandwidth • Highly resilient • Higher availability • Low power consumption • Less cooling • Lower latency • Lower cost • Less rack space • Easier to scale Designing a Distributed Core The core design wizard templates define the basic configuration for a distributed core.
This section contains the following topics: • Terminology • Gather Useful Information • Key Core Design Considerations • Select a Core Design Template • Type 1: Large Core Design • Type 2: Medium Core Design • Type 3: Small Core Design Terminology The following terms are unique to the design and deployment of a distributed core: • Leaf—A switch that connects switch, servers, storage devices, or top-of-rack (TOR) elements. • Spine—A switch that connects to leaf switches.
Gathering Useful Information Before you begin, gather the following useful information: • Comma separated values (.csv) file that contains all the chassis MAC addresses for the switches. If you do not have this file, write down the chassis MAC addresses. • Location of the switches, including the rack and row number. • Trivial File Transfer Protocol (TFTP) address from your system administrator. • Software image for each type of switch: Z9000, S4810, or both.
Figure 1. Flowchart for Designing a Distributed Core When designing the distributed core, consider the following: • You can deploy up to four distributed cores. However, the distributed cores do not communicate with each other. • DFM manages Dell Z9000 and S4810 switches. CAUTION: If you are already using a deployed switch, you must reset the factory settings. The switch must be in BMP mode.
• The uplinks or interlinks must be in area 0 for OSPF. • Interlink over-subscription ratio. NOTE: The Interconnect bandwidth link is fixed and based on the core type: • For a Type 1: Large Core and Type 2: Medium Core the interconnect bandwidth is 40 GbE. • For a Type 3: Small Core the interconnect bandwidth is 10 GbE. CAUTION: If you do not specify any additional links in the core design for future expansion in the Port Count screen: • Any future expansion requires rewiring the hardware.
Use the Type 1: Large Core design when: • The line rate-performance with an oversubscription ratio of 1:1 between the spines and leaves is required. • The current and future planned uplinks and downlinks on the leaves for the distributed core is less than or equal to 2048 ports. • The leaves do not act as a ToR. For redundancy, each leaf in a large core design can connect 2 to 16 spines. The Type 1: Large Core Design uses a 1:2 spine-to-leaf ratio.
Use the Type 2: Medium Core design when: • An interconnect link bandwidth between the spines and leaves at a 40 GbE line rate is required. • The current and future planned uplinks and downlinks on the leaves for your core is less than or equal to 1536 ports. • The leaves act as a switch or ToR-leaf switch. Within the ToR, the protocol can be either "VLAN" or "VLAN and LAG".
Type 3: Small Core Design Use the Type 3: Small Core design when: • An interconnect link bandwidth between the spines and leaves of 10 GbE is required. • The current and future planned uplinks and downlinks on the leaves for your core is less than or equal to 960 ports. • The leaves act as a switch or ToR-leaf switch. Within the ToR, the downlink protocol can be either "VLAN" or "VLAN and LAG".
Getting Started 2 Designing and Deploying a Distributed Core This section provides an overview of the steps required to design and deploy a distributed core, including the information you need to gather before you begin. After you do the basic installation of the Dell Fabric Manager (DFM), you must configured it. This is done using the Configuration Wizard when the application first starts, as shown below.
Flowchart for Designing and Deploying a Distributed Core How to Design and Deploy a Distributed Core To design and deploy a distributed core: 1. Gather Useful Information. 2. Design a Distributed Core 3. Build the physical network. 4. Configure the TFTP, SNMP, and CLI Credentials settings. 5. Prepare the Core for Deployment. 6. Deploy and Validate the Core. 7. Validate the deployed core against the core design . 8. Monitor the core health and performance.
Using the Core Design Wizard 3 Use the Core Design Wizard at the Home > Getting Started screen or the Cores > Core Deployment > Design > New Core screen to design a two-tier distributed core (spine and leaf architecture) based on your workload requirements for your current and future needs. The design consists of a wiring plan, network topology information, summary of the inventory requirement, and a design specification.
Core Design – Step 2: Core Name and Type Use the Core Design Wizard at the Home > Getting Started screen to design a two-tier distributed core (spine and leaf architecture) based on the workload requirements for your current and future needs.
– underscore ( _ ) – @ – + When you specify the name of the distributed core,Dell Fabric Manager automatically names the nodes (spines and leaves) in the distributed core with the core name as the prefix. For example, if the name of the core is EastCore, the node names assigned are EastCore-Spine-1 and EastCore-Leaf1. 2. (Optional) Enter the description of the distributed core. 3. Select the core type from the Core Type pull-down menu. 4.
CAUTION: If you do not specify any additional links in the core design for future expansion: • Any future expansion requires rewiring the hardware. • IP addresses are not reserved. • You might have to bring down currently deployed switches to expand the core. For information on how to expand the core, see Expanding the Core. To specify the number of edge port uplinks and downlinks for initial deployment and for future expansion: 1.
Core Design – Step 5: Uplink Configuration The Uplink Configuration page displays the port bandwidth (a read-only field) and the number of specified ports entered on the Core Name and Type and Port Count screens. Use the Uplink Configuration screen to configure the uplink protocol for the edge port uplinks to the WAN. NOTE: The uplinks or interlinks must be in area 0 for OSPF. To configure the uplink protocol for the edge port uplinks to the WAN: 1.
After the distributed core design is approved, the wiring plan is then typically given to your data center operator who uses this information to build the physical network according to the distributed core design. Review the wiring plans and then export them to a file. The distributed core design configuration is displayed in the following formats from the View pull-down menu. • Graphical Wiring Plan–Displays information about how the spines and leaves (switches) are connected graphically as shown below.
1. Navigate to the Cores > Core Deployment > Design > New Core > Output screen. 2. Click the Export button. The Export Wiring Plan window displays. NOTE: Exporting the network topology is not supported. 3. Specify the following export options. a) In What to export, select one of the following options: Save wiring table only (CSV), Save graphical wiring plan only, or Save Both (CSV + graphical wiring plan).
Using the Pre-deployment Wizard 4 To prepare the distributed core for deployment, complete the following tasks using the Pre-deployment Wizard. 1. Pre-deployment – Step 1: Introduction 2. Pre-deployment – Step 2: Assign Switch Identities 3. Pre-deployment – Step 3: Management IP 4. Pre-deployment – Step 4: Software Images 5. Pre-deployment – Step 5: DHCP Integration 6. Pre-deployment – Step 6: Output 7.
Figure 2. Pre-Deployment Flowchart Flowchart for preparing the distributed core for deployment NOTE: The pre-deployment flowchart does not list all the prerequisites. For more information, see Prerequisites. Pre-Deployment Screens Use the following Pre-deployment screens to prepare the distributed core for deployment. These screens automate the deployment process. • Assign Switch Identities – Assigns chassis MAC address to each switch.
• Summary – Displays the core name, location of the software image, and DHCP configuration file. Pre-deployment – Step 2: Assign Switch Identities Use the Assign Switch Identities page to associate the chassis MAC addresses to the switches in the distributed core. Entering the serial numbers and service tags are recommend but not required. Load the CSV file that contains the chassis MAC addresses, serial numbers, and service tags for the switches in the distributed core.
Pre-Deployment – Step 4: Software Images Use the Software Images screen to specify which software images to stage for each type of switch for the distributed core from a TFTP site. The software image must be the same for each type of platform. Place the software image(s) for the switches on the TFTP site so that the switches can install the appropriate FTOS software image and configuration file. To change the address of the TFTP site, navigate to the Administration > Settings screen.
1. Navigate to the Cores > Core Deployment > Deploy > Pre-deployment Configuration > Software Images screen. 2. Click Save to ... and then specify the location to save the generated DHCP configuration file. You can also copy and paste the configuration into the DHCP server. 3. Install the DHCP file onto the DHCP server before your deploy the core. NOTE: You must install the DHCP configuration file onto your DHCP server before you deploy the distributed core. 4. Click Next to go to the Output screen.
Deploying and Validating the Core 5 Use the Core Deployment screen to deploy the distributed core. Make sure that the designed core matches the deployed core. DFM prompts you to fix any errors when you deploy the distributed core. To view the DHCP file for the selected core, navigate to the Core Deployment > Deploy > View DHCP Configuration screen. Use the core validation to verify that the discovered distributed core matches the planned distributed core and correct any errors.
For information about the progress and status of selected nodes and operations allowed during a core state, see Operations Allowed During Each Core State and Understanding Core Phases. 12. Click on the Errors tab to view the following type of errors from the Select Errors to View pull-down menu. a) Discovered Switch Errors—If you have discovered switch errors, log on to switch console to isolate the fault.
b) Undiscovered Switch Errors—If you have undiscovered switch errors, log on to switch console to isolate the fault. Make sure that the switch has been power cycled on and check the physical connection. c) Configuration Errors—Click the View Mismatch button to view the configuration errors. Review the configuration mismatch and correct it. d) Wiring Errors—Click the View Mismatch button to view the wiring errors. Review the wiring mismatch and correct it. 13. Click on the Export button to export the errors.
Understanding Core Phases 6 DFM allows you to create a distributed core design, make changes to the pre-deployment configuration, deploy the core, and validate the core designed with the discovered core. DFM provides up-to-date status during each phase of the core from design to validate. The DFM displays any pending steps required that you need to complete to ensure the distributed core is fully functional for each core design.
Operations Allowed During Each Core State 7 Use the following table to determine which operations are allowed during the design, pre-deployment configuration, deployment, and validation states. Table 1.
Stopped / Error / Complete • • • Complete Partial Complete / Incomplete / Partial Complete / Complete Complete Incomplete indicates that the DFM is in the middle of deploying the switches. Complete indicates all the switches in the distributed core are deployed. Not Started / Inprogress / Stopped / Error / Complete • • View Wiring Plan Edit Core—Allow editing of all core attributes except core name, core type interlink oversubscription, port count, and expand core.
8 Troubleshooting Use this section to troubleshooting a deployed distributed core. This section contains the following topics: • Validation Errors • Validating Connectivity to the ToR • Switch Deployment Status Errors Switch Deployment Status Errors Use the following table to troubleshoot switch deployment status errors. Table 2.
CONFIG FILE TRANSFER FAILED Configuration File Transfer Failed Yes 1. Verify the connectivity to the TFTP server from the DFM server. 2. Restart the deployment of the switch from the Core Development > Deploy > Deploy and Validate Core screen by selecting the switch from the list and then click on the Deploy Selected button. NOTE: The switch is in BMP mode.
2. Make any necessary fixes. 3. Restart the deployment of the switch from the Core Development > Deploy > Deploy and Validate Core screen by selecting the switch from the list and then click on the Deploy Selected button. NOTE: The switch is in BMP mode. PROTOCOL CONFIG UPLOAD INPROGRESS Protocol Configuration Upload In-Progress No PROTOCOL CONFIG UPLOAD ERROR Protocol Configuration Upload Error Yes Information only. 1. Verify the connectivity to the TFTP server from switch. 2.
NOTE: The switch is not in BMP mode. UPLINK RECONFIGURED REDEPLOY REQUIRED Uplink re-configured, Redeployment of Switch is required Yes Restart the deployment of the switch from the Core Development > Deploy > Deploy and Validate Core screen by selecting the switch from the list and then click on the Deploy Selected button. NOTE: The switch is not in BMP mode.
Table 3. Configuration Errors Configuration Error Configuration Mismatch Recommended Action 1. On the Deployment and Validation Status screen, select the switch that you want to view. 2. Click the View Mismatch button. 3. Review the configuration mismatch and correct the configuration errors. 4. Restart validation of the switch from the Deploy and Validate Core screen by selecting the switch from the list and clicking the Start Validation button. Table 4.
1. Verify that the switch has a valid IP address. 2. If required, correct the pre-deployment configuration. 3. From the DFM server, verify that the connectivity to the switch exists. 4. Verify that the switch is running the minimum required software. 5. Validate the switch from the Core Deployment > Deploy > Deploy and Validate Core screen by selecting the switch from the list and then clicking the Start Validation button. Table 6.
Expanding the Core 9 Use the Expand Core Design screens to expand a deployed core. If you have configured the distributed core for future expansion and deployed it, you can later expand it. For information on configuring future expansion, see the Core Design – Step 3: Port Count. NOTE: When you use the Expand the Core wizard, the Core Name and Type and Downlink Configuration screens are read-only. The DFM automatically configures the downlinks entered in the Port Count screen.
Modifying and Viewing the Distributed Core 10 This section contains the following topics: • Dashboard • Cores • Editing the Core • Deleting the Core • Viewing and Exporting Wiring Diagram • Viewing the Core DHCP Configuration File Dashboard Use the Home > Dashboard screen as shown below to view the distributed core and system health.
Cores Use the Cores > Cores screen to display information about a deployed distributed core at the network, core, spine, leaf, and port level. The view is split into the tree view, tabular view, and tabbed view. NOTE: You must deploy a distributed core to view information about the core. • Tree view—The tree view on the left pane allows you to easy navigate across the cores and nodes. The tree hierarchy consists of the Network, Core, and Node (spine or leaf).
Deleting the Core When you delete a distributed core, Dell Fabric Manager manages the switches in the distributed core and removes the core related information from the system. To delete the a distributed core: 1. Navigate to the Cores > Cores Deployment screen. 2. Select the core that you want to delete. 3. Click the Delete button. Viewing and Exporting Wiring Diagram To view and export the wiring diagram: 1. Navigate to the Cores > Core Deployment screen. 2. Select the core that you want to view.
Alerts 11 This section contains the following topics: • Active Alerts • Alerts and Event History Active Alerts Use the Alerts > Active Alerts screen to display the active alerts in the distributed core and DFM. The top navigation pane also displays a summary of alerts for each severity across all cores. The system also displays the name of the user logged in, along with the options to Logout and access Help. Clicking an alert from this pane opens the Alerts > Active Alerts screen.
Alerts and Event History Use this screen to view alerts and event history. • To refresh the screen, click the reload grid icon. • To export alerts and event history, click the Export button. To filter alerts and event history in the distributed core and DFM: 1. Navigate to the Alerts > Alerts and Events screen. 2. Click the filtering icon. The filtering options display. 3.
Monitor 12 This section contains the following: • Reports • Global Statistics • Data Collection Reports This section contains the following topics: • Creating a new report • Running a Report • Editing a report • Duplicating reports • Deleting a report NOTE: To run a report, you must schedule the data collection to start the task. Creating a New Report To create a new report: 1. Navigate to the Monitor > Reports screen. 2. Click the New Report button.
10. In the Query field, to determine what to nodes should be included in the report for a core: a) Select the core to query from the first pull-down menu. b) Select the type of switches (spine and leaves) from the 2nd pull-down menu. 11. In the Available Nodes/Ports area, select the nodes that you want to include in the report, and then click the >> button. 12. In Summary screen, review the report settings. 13. If you want to run the report now, check the Run Report Now option. 14. Click the Finish button.
Deleting a Report To delete a report: 1. Navigate to the Monitor > Reports screen. 2. Select the report that you want to delete. 3. Click the Delete button. The Delete Confirmation window displays. 4. Click Yes. Global Statistics The Global Statistics screen displays the following statistics at the core level: • Top 25 ports used. • Top 10 highest CPU utilization. • Top 10 highest memory utilization. To view global statistics: 1. Navigate to the Monitor > Global Statistics screen. 2.
Administration 13 Use the Administration screens to configure the following: • Administrative Settings • User Accounts • User Sessions Settings This section contains the following topics: • TFTP Settings • Syslog IP Addresses • SNMP Configuration • CLI Credentials • Data Retention • Client Settings TFTP Settings Use the TFTP settings to specify to where to load the software images onto each switch in the distributed core from the TFTP site.
1. Navigate to the Administration > Settings screen. 2. In the Syslog IP Addresses area, click Edit. The Syslog IP Address screen displays. 3. In the Sylog IP Addresses fields, enter the IP address of the syslog server. 4. Click OK. SNMP Configuration Configure SNMP so that the DFM can perform SNMP queries on the switches in the distributed core. The values you enter in the SNMP configuration are also used for configuring the switches during the build phase and for monitoring during the run phase.
Data Retention To configure the amount of time to retain performance history: 1. Navigate to the Administration > Settings screen. 2. In the Data Retention area, click the Edit button. 3. In the Performance History area, enter the number of days you want to retain your performance history. The range is between 1 and 180 days. 4. In the Daily Purge Execution Time pull-down menu, specify the time to begin purging the performance history data. 5. Click OK.
• Password Rules – The DFM enforces special password rules for enhanced security. The password must be a minimum of 6 characters and contain one capital letter and one number. The password is masked when you enter it. • Unsuccessful Login Limit – Specifies the unsuccessful login limit for a user’s account. When the unsuccessful login limit is exceeded, the lockout duration is applied.
6. In the First Name field, enter the user’s first name. The first name can contain any characters. Length: 1 to 50 characters. 7. (Optional) In the Last Name field, enter the user’s last name. The last name can contain any characters. Length: 1 to 50 characters. 8. From the Role pull-down menu, select one of the following roles: Admin or User. For information about roles, see Managing User Accounts. 9. In the Sessions Allowed pull-down menu, specify the number sessions allowed for the user.
5. In the Confirm Password field, enter the user’s password. 6. In the First Name field, enter the user’s first name. 7. In the Last Name, enter the user’s last name. 8. In the Sessions Allowed pull-down menu, specify the number sessions allowed for the user. 9. In the Session Timeout pull-down menu, specify one of the following timeout values: a) b) c) d) 15 minutes 30 minutes 45 minutes 60 minutes 10. Click OK. Changing Your Password To change your password: 1.
• Current Session To terminate DFM users’ sessions: 1. Navigate to the Administration > User Sessions screen. 2. Select the users that you want to log off. 3. Click the Force Logoff button. 4. Click OK.
