Active Fabric Manager (AFM) Deployment Guide 2.
Copyright © 2014 Dell Inc. All rights reserved. This product is protected by U.S. and international copyright and intellectual property laws. Dell™ and the Dell logo are trademarks of Dell Inc. in the United States and/or other jurisdictions. All other marks and names mentioned herein may be trademarks of their respective companies. 2014 - 4 Rev.
Contents 1 Introduction............................................................................................................... 9 Problem: Challenges to Build a Fabric in the Data Center..................................................................9 Solution: Active Fabric Manager......................................................................................................... 10 2 About AFM...................................................................................................
7 IOA Fabric Designer Wizard................................................................................. 69 8 Designing the Fabric.............................................................................................. 75 Network Deployment Summary ........................................................................................................ 75 Fabric Configuration Phases and States.......................................................................................
Pre-Deployment – Step 6: DHCP Integration........................................................................... 160 Pre-Deployment – Step 7: Summary......................................................................................... 161 Viewing the DHCP Configuration File.............................................................................................. 161 Deploying and Validating the Fabric................................................................................................
13 Performance Management.............................................................................. 207 Network Performance Management............................................................................................... 207 Fabric Performance Management................................................................................................... 208 Switch Performance Management..................................................................................................
16 Administration..................................................................................................... 231 Administrative Settings...................................................................................................................... 231 Active Link Settings......................................................................................................................231 CLI Credentials......................................................................................
Introduction 1 Active Fabric Manager (AFM) is a graphical user interface (GUI) based network automation and orchestration tool that enables you to design, build, deploy, and optimize a Layer 2 Virtual Link Trunking (VLT), Layer 3 distributed core, and Layer 3 with Resiliency (Routed VLT) fabric for your current and future capacity requirements. This tool helps you simplify network operations, automate tasks, and improve efficiency in the data center.
Solution: Active Fabric Manager 10 Introduction
About AFM 2 Active Fabric Manager (AFM) is a graphical user interface (GUI) based network automation and orchestration tool that allows you to design, build, deploy, and optimize a Layer 3 distributed core, Layer 3 with Resiliency (Routed VLT), and Layer 2 VLT fabric for your current and future capacity requirements. This tool helps you simplify network operations, automate tasks, and improve efficiency in the data center. NOTE: Before you begin, review the Getting Started page.
Getting Started 3 This section contains the following topics: • Designing and Deploying the Fabric • Flowchart for Designing and Deploying a Fabric Related links: • Designing the Fabric • AFM Site Map • Supported Fabric Types NOTE: You can view the Active Fabric Manager Deployment Guide in the AFM by selecting the Deployment Guide option from the Help pull-down menu in the upper right of the screen.
Figure 1. Getting Started Wizard To design and deploy a Layer 2 VLT, Layer 3 distributed core fabric, or Layer 3 with Resiliency (Routed VLT) 1. Gather useful information. Related links. 2. • Gather Useful Information for Layer 2 VLT Fabric • Gathering Useful Information for a Layer 3 Distributed Core Fabric. • Gathering Useful Information for a Layer 3 with Resiliency (Routed VLT) Fabric Design the fabric.
• Selecting a Distributed Core Design Related links for designing a Layer 3 with Resiliency (Routed VLT): • Key Considerations for Designing Layer 3 with Resiliency (Routed VLT) • Selecting a Layer 2 VLT and Layer 3 with Resiliency (Routed VLT) Fabric Design 3. Build the physical network. 4. Configure the following settings: • TFTP/FTP • SNMP • CLI Credentials 5. Prepare the Fabric for Deployment 6. Deploy and Validate the Fabric 7. Validate the deployed fabric against the fabric design.
Figure 2. Capacity Planning Figure 3.
4 AFM Site Map To help you navigate the AFM user interface use the following site map.
Manage Templates Associate Templates Custom Configuration View Custom Configuration History View Wiring Plan Switch Level Summary Device View Graphical and Tabular View Alerts and Events Current Historical Performance Troubleshootin g Switch and Port RealPing time and Historical data SSH Traceroute Replace a Switch Decommission Switch Replace Switch Deploy Switch Telnet Jobs Job Results Schedule Jobs Backup Switch Configuratio n Files Data Collection Reports Edit threshold Delete Create Sched
DHCP Server Settings NTP Server Settings Email Settings Syslog IP Addresses SNMP Configuratio n System Information TFTP/FTP Settings AFM Site Map 19
Supported Fabric Types 5 The fabric design wizard defines the basic configuration for a Layer 2 VLT, Layer 3 distributed core, and Layer 3 with Resiliency (Routed VLT) fabric. • Use the Layer 3 distributed core fabric for large fabric deployments. For information about distributed core fabrics, see Conventional Core Versus Distributed Core and Selecting a Layer 3 Distributed Core Fabric Design. • Use the Layer 2 VLT fabric for workload migration over virtualized environments.
Figure 4. Getting Started Wizard Key Considerations for Designing a Layer 3 with Resiliency (Routed VLT) Fabric Use the Layer 3 with Resiliency (Routed VLT) fabric to extend equal cost multi-pathing capabilities. When designing a Layer 3 with Resiliency (Routed VLT) fabric, consider the following: • You can deploy up to 10 fabrics. However, the fabrics do not communicate with each other. • AFM manages Dell Networking S4810, S4820T, S6000, and Z9000 switches.
• Fabric interlink bandwidth (the links between the aggregation and access switches). • Downlinks which can be 1Gb, 10Gb, or 40 Gb. • The fabric interlink bandwidth, 10 Gb or 40 Gb, is fixed and based on the fabric type. CAUTION: If you do not specify additional links in the fabric design for future expansion in the Bandwidth and Port Count screen, you can only expand the downlinks on the existing fabric.
Conventional Core A conventional core is a three-tier network that is typically chassis-based and is composed of the following: • • • Core — The core layer routes traffic to and from the internet and the extranet. Redundancy and resiliency are the main factors for high availability, which requires chassis-based core routers. Aggregation layer — The aggregation layer connects with top of rack (ToR) switches and aggregates the traffic into fewer high-density interfaces such as 10GbE or 40GbE.
NOTE: There are no uplinks on the spines. All the leaves have downlinks. The uplink should be configured in the first two leaves.
• Uplinks — An edge port link on the first two leaves in the distributed core fabric that connects to the edge WAN, which typically connects to an internet server provider (ISP). The uplink can also connect to a router gateway or an external switch. • Downlinks — An edge port link that connects the leaves to the data access layer; for example, servers or ToR elements. NOTE: Specify an even number of uplinks. The minimum number of uplinks is 2. One uplink is for redundancy.
Important: In a single distributed fabric, all the leaves can act as a non-ToR or as a ToR, not both at the same time. Key Considerations for Designing a Distributed Core When designing the Layer 3 distributed core fabric, consider the following: • You can deploy up to 10 fabrics. However, the fabrics do not communicate with each other. • AFM manages Dell S4810, S4820T, S6000, and Z9000 switches. CAUTION: If you are already using a deployed switch, reset the factory settings.
Gathering Useful Information for a Distributed Core To gather the following useful information for a Layer 3 distributed core fabric before you begin: • Obtain the comma-separated values (CSV) file that contains the system media access control (MAC) addresses, service tag, and serial numbers for each switch provided from Dell manufacturing or manually enter this information. • Obtain the location of the switches, including the rack and row number from your network administrator or network operator.
• Key Considerations for Designing a Distributed Core Fabric • Flowchart for Designing and Deploying a Fabric. With a Layer 3 distributed core topology, you select the Layer 3 option using the Design Wizard on the Deployment Topology screen. For information about distributed core, see Selecting a Distributed Core Design.
Figure 5. Type 1: Extra Large Distributed Core Fabric Design Use the Type 1: Extra Large Distributed Core fabric design when: • The line rate-performance with a fabric oversubscription ratio of 1:1 between the spines and leaves. • The current and future planned uplinks and downlinks on the leaves for the distributed core is less than or equal to 2048 ports. For redundancy, each leaf in a large core design can connect 2 to 16 spines.
With a Type 2: Large Distributed Core fabric design, the S4810 spines connect to the S4810 leaves at a fixed 10 Gb. The maximum number of spines is 32 and the maximum number of leaves is 64, as shown in the following figure. Figure 6.
Figure 7. Type 3: Medium Distributed Core Fabric Design Use the Type 3: Medium Distributed Core design when: • You require a fabric interlink (fabric links) bandwidth between the spines and leaves at a 40 Gb line rate. • The current and future planned uplinks and downlinks on the leaves for your distributed core fabric 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.
• The maximum port count for a Type 4: Small Distributed Core fabric with an OS ratio of 3:1 is 768. For an OS ratio of 5:1, the maximum port count is 896. • The leaves act as a switch or ToR-leaf switch. Within the ToR, the downlink protocol can be either VLAN or VLAN and LAG. With a Type 4: Small Distributed Core fabric design, the S4810 spines connect to the S4810 leaves at a fixed 10 Gb. The maximum number of spines is 4 and the maximum number of leaves is 16, as show in the following figure.
For information about VLT, see the FTOS Configuration Guide for either the S4810, S6000, or the Z9000 at https://www.force10networks.com/CSPortal20/KnowledgeBase/Documentation.aspx. For more information about VLT, see Selecting a Layer 2 and Layer 3 with Resiliency (Routed VLT) Fabric Design.
confused with failures of the VLT interconnect. VLT ensures that local traffic on a chassis does not traverse the VLTi and takes the shortest path to the destination via directly attached links. VLT Fabric Terminology The following terms are unique to the design and deployment of a Layer 2 VLT fabric. • Core — A switch that connects to aggregation switches. The role of the core is to provide an interconnect to all the aggregation switches.
as shown in the following illustration. The backup-link connected through the out-of-band (OOB) management network. Some hosts can connect through the non-VLT ports. Key Considerations for Designing a Layer 2 VLT Fabric Use the Layer 2 VLT fabric for workload migration over virtualized environments. When designing the Layer 2 VLT fabric, consider the following: • You can deploy up to 10 fabrics. However, the fabrics do not communicate with each other.
For information on how to expand a fabric, see Editing and Expanding an Existing Fabric Design. Gathering Useful Information for a Layer 2 VLT Fabric To gather useful information for a layer 2 VLT fabric before you begin: • Obtain the CSV file that contains the system MAC addresses, service tag and serial numbers for each switch provided from Dell manufacturing or manually enter this information.
• 10 Gb Blade Switch (MXL) for Layer 2 and Layer 3 with Resiliency (Routed VLT) For information about tiers, refer to Deployment Topology and Deployment Topology Use Cases. For more information about VLT, refer to the following sections: • Overview of VLT • Key Core Design Considerations for VLT • Getting Started. 1 and 2 Tier ToR 10 Gb for Layer 2 LAN/SAN for iSCSI Topologies Table 2.
2-4 2-8 101 - 2808 2 * 40G 2 * 40G 20G S4810 S4810 FL BW AA = Fabric Link Bandwidth between Aggregation & Access Table 4.
DL BW UL BW Deployment Type Downlink Port Range AVC Access VLTi Capacity FL BW AA Possible Aggregation Topologies Aggregation Access 10 Gb 10G Resiliency 87 - 2750 2 * 40G 2 * 40G 20G S4810 S5000 10 Gb 40G Resiliency 81 - 2600 2 * 40G 2 * 40G 20G S4810 S5000 DL BW = Downlink Bandwidth UL BW = Uplink Bandwidth FL BW AA = Fabric Link Bandwidth between Aggregation & Access 1 Tier for 10 Gb and 40 Gb ToR for Layer 2 and Layer 3 Resiliency (Routed VLT) Table 7.
Figure 9. 1 Gb ToR VLT Deployment Important: All the VLT aggregation switches must be same mode type for aggregation; for example, S4810. On the VLT access, you must configure the same model type.
Table 8.
BW = Bandwidth Table 9.
10 Gb or 40 Gb ToR (mVLT) Use the 10 Gb or 40 Gb ToR Deployment (mVLT) fabric when you require 10 Gb or 40 Gb downlinks for a ToR. For information about mVLT, refer to Multi-domain VLT. Refer to the MXL Topologies for MXL Blade Deployment. Figure 10. 10 Gb or 40 Gb ToR VLT Deployment (mVLT) Important: All the VLT aggregation switches must be same model for aggregation (for example, all Z9000 switches). On the VLT access, you can configure the same model or mixed the following models : S4810 and S4820T.
Use the following tables as guideline to select the appropriate two tier Layer 2 VLT or Layer 3 with Resiliency (Routed VLT) fabric design. NOTE: With a Layer 2 VLT fabric, the uplinks come from the first two switches on the aggregation side. For information about tiers, see Deployment Topology. Table 10.
DL BW UL BW Type DL Port Range AVC Access VLTi Capacity FL Possible Topologies BWB A Core Aggregation Access &A 10 Gb 40 Gb Stacking 105 2808 2 * 40 Gb NA 40 Gb NA S4810 S4810 10 Gb 40 Gb Stacking 105 1392 2 * 40 Gb NA 160 Gb NA Z9000 or S6000 S4810 10 Gb 40 Gb Basic 105 3224 2 * 40 Gb NA 20 Gb NA S4810 S4810 10 Gb 40 Gb Basic 105 1624 2 * 40 Gb NA 80G NA Z9000 or S6000 S4810 10 Gb 40 Gb Mixed node 105 Basic 3224 2 * 40 Gb NA 20 Gb NA S4810 S4810 or S4820T 1
Table 11.
Table 12.
DL BW UL BW Type DL Port Range CVC AVC AVC FL BW CA FL BW AA Possible Topologies Core Aggregati on Access 10 Gb 40 Gb Stacking 2809 - 2 * 40 36288 Gb 2 * 40 Gb NA 80 Gb 40 Gb Z9000 or S6000 S4810 S4810 10 Gb 40 Gb Stacking 2809 - 2 * 40 36288 Gb 2 * 40 Gb NA 80 Gb 40 Gb Z9000 or S6000 S4810 S4820 10 Gb 40 Gb Stacking 1393 18816 2 * 40 Gb 2 * 40 Gb NA 80 Gb 160 Gb Z9000 or S6000 Z9000 or S6000 S4810 10 Gb 40 Gb Stacking 1393 18816 2 * 40 Gb 2 * 40 Gb NA 80 Gb 16
CVC = Core VLTi Capacity BW = Bandwidth DL = Downlink DL BW = Downlink Bandwidth FL BWB C & A = Fabric Link Bandwidth between Core and Aggregation Switches FL BWB A & A = Fabric Link Bandwidth between Aggregation and Access Switches UL BW = Uplink Bandwidth Table 13.
10 Gb Blade Switch (MXL) VLT Deployment BW = Bandwidth DL = Downlink FL BWB A & A = Fabric Link Bandwidth between Aggregation and Access UL BW = Uplink Bandwidth VLTi A BW = VLTi Aggregation Bandwidth Table 14.
MXL Blade Pairs Range UL BW Type Fabric Type FL BWBA &A VLTi A BW VLTi Access BW MXL Interchassis BW Possible Topologies Aggregatio n Access (Routed VLT) 2 - 14 10 Gb Basic Layer 2/ Layer 3 with Resiliency (Routed VLT) 80 Gb 2 * 40 Gb NA NA Z9000 or S6000 MXL 2 - 14 40 Gb Basic Layer 2/ Layer 3 with Resiliency (Routed VLT) 80 Gb 2 * 40 Gb NA NA Z9000 or S6000 MXL 2 - 26 40 Gb Basic Layer 2/ Layer 3 with Resiliency (Routed VLT) 20 Gb 2 * 40 Gb NA NA S4810 or S4820T MXL 2
MXL Blade Pairs Range UL BW Type Fabric Type FL BWBA &A VLTi A BW VLTi Access BW MXL Interchassis BW Possible Topologies Aggregatio n Access 2 -27 10 Gb MXL intraChassis resiliency Layer 2/ Layer 3 with Resiliency (Routed VLT) 20 Gb 2 * 40 Gb 2 * 40 Gb NA S4810 or S4820T MXL 2 - 14 10 Gb MXL intraChassis resiliency Layer 2/ Layer 3 with Resiliency (Routed VLT) 80 Gb 2 * 40 Gb 2 * 40 Gb NA Z9000/ S6000 MXL 2 - 14 40 Gb MXL intraChassis resiliency Layer 2/ Layer 3 with Resilie
FL BWB C & A = Fabric Link Bandwidth between Core and Access UL BW = Uplink Bandwidth VCBW = VLTi Core Bandwidth Table 15.
MXL Blade Pairs Range UL BW Type VLTi Aggreg at-ion BW Possible Topologies Core Aggregation Access 28 336 10 Gb Stacking Layer 2 or 80G Layer 3 with Resiliency (Routed VLT) 40 Gb 2 * 40 Gb 2 * 40 Gb Z9000 S4810 or S4820T MXL 28 336 40 Gb Stacking Layer 2/ 80G Layer 3 with Resiliency (Routed VLT) 40 Gb 2 * 40 Gb 2 * 40 Gb Z9000 S4810 or S4820T MXL 15 196 10 Gb Stacking Layer 2 or 80G Layer 3 with Resiliency (Routed VLT) 160G 2 * 40 Gb 2 * 40 Gb Z9000 Z9000 MXL 15 196 10 G
MXL Blade Pairs Range UL BW Type Fabric Type FL FL VCBW BWB BWB C& A&A A VLTi Aggreg at-ion BW resilienc Resiliency y (Routed VLT) Possible Topologies Core Aggregation Access S6000 15 196 10 Gb MXL intraChassis resilienc y Layer 2 or 80G Layer 3 with Resiliency (Routed VLT) 80G 2 * 40 Gb 2 * 40 Gb Z9000 Z9000 MXL 15 196 10 Gb MXL intraChassis resilienc y Layer 2 or 80G Layer 3 with Resiliency (Routed VLT) 80G 2 * 40 Gb 2 * 40 Gb S6000 S6000 MXL 15 196 40 Gb MXL intraChassis r
Discovering and Deploying an Existing Fabric 6 Use the discover fabric option to discover an existing fabric or an IOA blade switch in a M1000e chassis. For information about IOA, see Designing an IOA Fabric. To discover and deploy an existing fabric: Figure 11. Discovering and Deploying an Existing Fabric 1. Initiate discovery of an existing fabric at the Network > Design > Discover Fabric screen. See Step 1: Discover an Existing Fabric 2.
4. Perform maintenance operations, such as monitoring and software updates. See Maintenance and Performance Management. Step 1: Discover an Existing Fabric This section describes how to discover an existing fabric. For an overview about discovering and deploying an existing fabric, see Discovering and Deploying an Existing Fabric. To discover an existing fabric: 1. Click on the Network and then the Design Fabric tab. The Network Deployment Summary screen displays. 2. Click Discover Fabric.
6. Click the Next button. The Discovery Information screen displays. Figure 13. Discover Fabric Wizard — Discovery Information Screen 7. Enter the switch IP address in the Enter the Switch IP Address field and click the + button to add the IP address. NOTE: You can add an individual IP address, and IP address with a subnet, or a range. You must add at least one IP address to the List of added IPs: field before clicking Next. • IP range example 10.16.133.1-150 • Network with mask example 10.16.132.
10. To exclude an IP address, enter it in the Enter Exclusion IP Address field. Figure 14. Preview IP Address Window 11. To view a list of all IP addresses to be added, click the Preview IP button. The Preview IP screen displays only the inclusion list of devices: the devices that are participating in the discovery. The Preview IP List is paginated. Use the arrow buttons to view additional pages or enter the page number in the page number entry field to the left of the arrow buttons. 12.
13. In the SNMP section, click the Add link. The SNMP Credential window displays. Figure 15. Discover Fabric SNMP Credential Screen 14. Enter the SNMP credential information and click OK to confirm the information or click Close to close the window. By default, the SNMP port number is 161 and the trap port number is 162. The maximum number of SNMP credentials is 5. • Enter the read community string in the Read Community String(s) field. You can only enter one read community string.
15. Click Add in the CLI Credentials section. The CLI Credential window displays. Figure 16. Discover Fabric CLI Credential Screen NOTE: You can configure up to five CLI credentials for a single fabric and can be a combination of credential types (SSHv2 and Telnet). 16. Enter the CLI credential information. • Select the appropriate credential type (Telnet or SSHv2). • Enter the user name in the User Name field and enter the password in the Password and Confirm Password fields.
17. Click the Next button. The Summary screen displays. Figure 17. Discover Fabric Wizard — Summary Screen 18. In the Summary screen, review the discover summary information and then click Finish to start the fabric discovery process. AFM then displays the Network Deployment Summary screen. Next Steps Click the Discover Status link to check the status of discovered existing fabric. For information about the Discover Status screen, see Step 2: View Discovery Status Screen Figure 18.
• Display the current fabric discovery status and details for switches and chassis used in the existing fabric or an IOA in a M1000e chassis. • Verify that AFM has discovered all the switches in an existing fabric or IOA fabric. • Rediscover an existing chassis or switch for troubleshooting. • Remove a switch from the discovered fabric. See also Discovering and Deploying an Existing Fabric. The following discover options are available: • Rediscover Fabric — Rediscovers an existing fabric.
NOTE: Only Dell IOA and MXL blades are identified. All other blade types are listed as “Unknown.” • Software version • SNMP status • CLI login status • Discovery status • Reason (Completed, In Progress, Failed, or Not Yet Started) — If a device is not discovered, check the Reason Column for a recommended action. For information about how to discover a fabric, see Discovering an Existing Fabric.
Figure 21. Discovery Status Link NOTE: To remove a chassis, navigate to the Edit Fabric screen and delete the IP address of the chassis. 2. 66 Click the Discover Status link to check the discovery status of an existing fabric. Check for discovered failed devices and look for error messages in the Reason column for why the devices were not discovered, such as an authentication failure.
Figure 22. Successfully Discovered Fabric Next Steps 1. Close the Discovery Status screen. 2. After you successfully discovered the existing fabric, deploy it. For information about deploying an existing fabric, see Step 3: Deploy Discovered Fabric. Step 3: Deploy Discovered Fabric This section describes how to deploy a discovered fabric. Once the discovered fabric is successfully deployed, the fabric can send alarms and events to AFM.
Figure 23. Deploy Successfully Discovered Existing Fabric To deploy a discovered fabric: 1. Close the Discovery Status screen. 2. Navigate to the Network > Design Fabric screen. 3. Navigate to the Step 3 Deployment column and deploy the discovered fabric by clicking the Required link that is associated with the discovered fabric. The Deploy and Validation screen displays. 4. On the Deploy tab, select the switches in the fabric you want to deploy in the discovered fabric. 5.
IOA Fabric Designer Wizard 7 Use the IOA fabric design wizard to design a Layer 2 fabric that has an I/O Aggregator (IOA) blade switch in a M1000e chassis. AFM supports IOA in standalone mode only. 1. Make sure that the IOA blade switch is in standalone mode (default mode) using the following FTOS CLI command: show system stack-unit iom-mode For more information about this command, see the Dell PowerEdge Command Line Reference Guide for the M I/O Aggregator. 2.
6. Click the Next button to display a Fabric Design Wizard that is for designing fabrics that only use IOA blades. The IOA Fabric Designer wizard displays. Figure 26.
7. Click the Next button. The Chassis Details screen displays. Figure 27. IOA Fabric Design Wizard — Chassis Details Screen 8. Enter the Chassis Management Controller (CMC) IP addresses to include in the fabric. The following options are available: • Add: Enter the chassis IP address in the first field and the prefix in the field after the slash and click OK. Click Cancel to close the Add window without adding the IP address. • Add Range: Enter the chassis ID in the Number of M1000e Chassis: field.
9. Click the Next button. The CLI Credentials screen displays. 10. Enter the user credentials for the CMC. This information is used to log in to all CMCs in the fabric. By default, the CLI Credentials screen uses the following CLI credentials: username = root and password = calvin. If you have changed the CLI credentials, update these fields with the new user name and/or password. 72 • Enter the user name in the User Name field. • Enter the password in the Password and Confirm Password fields.
11. Click the Next button. The Summary screen displays. The design summary screen shows the added chassis number and IP addresses, and CLI credentials. Figure 28. IOA Design Summary Screen 12. Review the fabric design information on the Summary screen. To confirm the information, click the Finish button. then click OK to go to the Discovery Status screen The discover Confirmation screen displays.
13. Click Yes to start the fabric discovery process. The Discovery Status screen displays detailed information about the installed IOA blade switch on the M1000e chassis. For information about the Discover Status screen, see Discovery Status Screen. Figure 29. IOA Discover Status Screen 14. After the IOA fabric is successfully discovered, complete the pre-deployment configuration. For information about IOA pre-deployment configuration, see IOA Pre-deployment Wizard.
Designing the Fabric 8 To design a Layer 3 two-tier distributed core fabric or Layer 2 VLT fabric based on your capacity planning for your current and future needs, use the Fabric Design Wizard at the Network > Design Fabric > New Fabric screen. The design consists of a wiring plan, network topology information, summary of the inventory requirement, and a design specification. See also Network Deployment Summary. NOTE: If you are designing a fabric using an IOA blade switch, see IOA Fabric Design Wizard.
Fabric Configuration Phases and States The following table describes the four fabric phases displayed on the Network > Fabric Name > Configure and Deploy > Deploy screen. To correct the fabric design and pre-deployment configuration before and after you deploy the fabric, use this information. Table 16. Fabric Configuration Phases and States Phase State State Description Design Incomplete Indicates that not all required information to complete the design was provided.
Validation Complete Indicates that deployment was successful for the switch. Required Indicates that the validation state for all switches is in state Required. In-progress Indicates that validation is In-progress (progress bar to be displayed in UI) on one or more switches. It provides information about count of switches successfully validated vs. count of total switches per design (based current port count, doesn’t include future port count).
NOTE: Deployment can be initiated/re-initiated only if Predeployment Configuration is in state Complete Validation In-progress Indicates that Deployment is in-progress and also provides the latest percentage complete information. Error Indicates that deployment error exists. Complete Indicates that deployment was successful for the switch.
3. Deployment Topology — Displays the option to select between a Layer 2 or Layer 3 solution and a list of all applicable deployment topologies based on the workload requirements that you entered on the Bandwidth and Port Count and Fabric Name and Type screens. This screen also displays Advanced options for configuring VLTi links and fabric links. See also Deployment Topology Use Cases. 4.
1. Navigate to the Fabric Design Wizard at the Network > Design Fabric screen. 2. Click the New Fabric link. The Introduction screen is displayed. 3. Review the introduction and click the Next button. The Fabric Name screen displays. 4. Enter the name of the fabric in the Fabric Name field. The fabric name must be a unique name. It can have from 1 to 17 characters.
6. Navigate to the Deployment Type area. Select one of the following options: • LAN only deployment — Creates a Layer 2, Layer 3, or Layer 3 Routed VLT fabric. • LAN/SAN deployment – Creates a Layer 2 LAN/SAN converge fabric. – Fibre Channel – Supports a fibre channel (FC) interfaces. Uses the S5000 as a N_Port ID Virtualization (NPIV) Proxy Gateway. This option provides a gateway between the fibre channel switch and server.
Designing the Fabric
To configure bandwidth and port count for the switches in the fabric: 1. In the Bandwidth Specification: a. Select the uplink bandwidth (10 Gb or 40 Gb) using the Uplink Bandwidth pull-down menu. b. Select the downlink bandwidth (1 Gb, 10 Gb, or 40 Gb) using the Downlink Bandwidth pull-down menu. 2. • When you select the 1 Gb Downlink Bandwidth option, the AFM supports deployment topologies with the S55 and S60 switches on the access side.
columns. The minimum number of fibre channel ports is 2 The maximum number of fibre channel ports (current and future) is 12 * number of S5000 access switches.
f. If you are connecting to iSCSI ports, navigate to the iSCSI ports area and then enter the number of current and future ports required for this interface in the in the Current and Future columns. The minimum number of iSCSI ports is 2. The maximum number of iSCSI ports (current and future) is 8. 3. Review the values and then click the Next button to go to the Deployment Topology screen. Deployment Topology Use Cases Use the following use cases as a guide to select a deployment topology.
configure downlink connections to servers. To support redundancy between the aggregation switches and ToR switches, select the VLAN and VRRP Configuration option. Figure 30. Example: Tier 1 with Layer 2 VLT fabric Deployment Topology Figure 31.
Use Case 2: 1 Tier Layer 3 with Resiliency (Routed VLT) When you select a 1 tier Layer 3 with Resiliency (Routed VLT) fabric: • The uplinks between the 2 aggregation switches and external switch (WAN) supports the Layer 3 protocol (OSPF, iBGP or eBGP). • The downlinks from the 2 aggregation switches supports the Layer 2 protocol (VLAN/VRRP or VLAN IP). During the design phase at the Deployment Topology screen, you select the fabric type and deployment type (topology).
Use Case 3: 2 tier Layer 3 Distributed Core When you select a 2 tier Layer 3 distributed core fabric: • The fabric links between the spine and leaf switches supports the Layer 3 OSPF routing protocol. • The uplinks between spine switch and external switch (WAN) supports the Layer 3 protocol (OSPF, iBGP or eBGP). • The downlinks from the access switches supports the Layer 2 protocol (VLAN or VLAN and LAG).
1. Layer 3 with Resiliency (Routed VLT) with stacking option – When you select the Stacking option, configure the VLAN with the primary and secondary IP addresses for each access switch. Figure 34. Example: 2 Tier Layer 3 with Resiliency (Routed VLT) with Stacking Option 2. Layer 3 with Resiliency (Routed VLT) with VLT option – When you select the VLT option, the default configuration is to enter the VLAN ID, Primary IP address and Secondary address.
Figure 35. Layer 3 with Resiliency (Routed VLT) with VLT option Figure 36. Layer 3 with Resiliency (Routed VLT) with VLT option + Advanced VLAN IP Configuration 3. 90 Layer 3 with Resiliency (Routed VLT) – Basic option – When you select the Basic option, configure the VLAN with the primary and secondary IP addresses for each access switch.
Figure 37. Layer 3 with Resiliency (Routed VLT) with Basic Option 4. Layer 3 with Resiliency (Routed VLT) with MXL Blade with interChassis option – With this topology , you select the Deployment Type that has a MXL Blade switch with Resiliency (VLT) and Interchassis (across Chassis) resiliency. Enter the VLAN ID and the IP range. When you complete the pre-deployment configuration, the Advanced VLAN IP Configuration option is available at the “Configure and Deploy” Summary screen. Figure 38.
5. Layer 3 with Resiliency (Routed VLT) – Blade MXL with IntraChassis option: With this topology, you select the deployment type using that has a MXL Blade switch with Resiliency (VLT) and Intrachassis (within the same chassis) resiliency option. Enter the VLAN ID, primary and secondary IP addresses. Figure 39.
Figure 40. 3 Tier Layer 2 VLT Topology Use Case 6: 3 Tier Layer 3 Resiliency (Routed VLT) When you select a 3 tier Layer 3 with Resiliency (Routed VLT) fabric: • The fabric links between core and aggregation switches supports Layer 3 protocol with OSPF in the VLAN interfaces. • The fabric links between the aggregation and access switches supports the Layer 2 protocol the Layer 2 protocol.
Figure 41. 3 Tier Layer 3 with Resiliency (Routed VLT) with Stacking Option 2. 94 Layer 3 with Resiliency (Routed VLT) with VLT option – When you select the VLT option, the default configuration is to enter the VLAN ID, Primary IP address and Secondary address. If you select the Enable Layer 3 Protocol in Access Switches option, configure the VLAN ID and then the IP Range.
Figure 42. Example: 3 Tier Layer 3 with Resiliency (Routed VLT) with VLT option Figure 43. 3 Tier Layer 3 with Resiliency (Routed VLT) with VLT Option + Advanced VLAN IP Configuration 3. Layer 3 with Resiliency (Routed VLT) – Basic option – When you select the Basic option, configure the VLAN with the primary and secondary IP addresses for each access switch.
Figure 44. Example: 3 Tier Layer 3 with Resiliency (Routed VLT) with Basic Option 4. Layer 3 with Resiliency (Routed VLT) – Blade MXL with IntraChassis option: With this topology , you select the deployment type that has a MXL Blade switch with Resiliency (VLT) and Intrachassis (within the same chassis) resiliency option. Enter the VLAN ID, primary and secondary IP addresses. Figure 45.
one of the topologies. Click the deployment topology filter icon on the top right of the screen to display additional deployment topology options. The output from these screens and the Deployment Topology and Fabric Customization screens create a network topology and the detailed wiring plan. See also Deployment Topology Use Cases. Based on your design requirements you can create a 1, 2, or 3 tier topology as shown below • Tier 1 Topology — Contains 2 switches and a downlink and uplink configuration.
Figure 49. Tier 3 VLT Topology Core: Aggregation - Access Layer The following illustration and table describes the deployment types for a fabric. NOTE: For topologies, refer to the Designing a Layer 2 VLT and Layer 3 with Resiliency (Routed VLT) Fabric and Selecting a Layer 3 Distributed Core Fabric Design. Table 18.
Resiliency in Access Devices Configures Virtual Router Redundancy Protocol (VRRP) on the downlink. 10 Gb Cable Type for Access Tier This option is applicable only for the topologies in which S4810 and S4820T can be swapped with each other. • SFP+ • RJ-45 Stacked/Non-Stacked Selects stacking for the topologies that are applicable. When you select stacking, you can use VLTi. High Stream Buffering • • high stream buffering — The access layer uses S60 switches.
Figure 50. Enabled Link Bandwidth Customization Option 3. In the Fabric Link Core Aggregation and aggregation and Access option (only the applicable options for a select topology are configurable), select the fabric bandwidth value from the Aggregation and Access pull-down menu. For example, for 2 tier topology, selecting the 120 Gb bandwidth option allows you to later customize the bandwidth from 20 to 120 Gb in increments of 20 Gb in the Fabric Customization screen. 4.
Figure 51. Customizing Fabric Link Bandwidth between Switches 10. Click the Next button to go to the Output screen.
Figure 52. Layer 3 with Resiliency (Routed VLT) : Deployment Type screen 1. Navigate to the Network > Design Fabric > New Fabric > Deployment Topology screen. 2. In the Fabric Type area, select one of the following fabric types: a. Layer 2 — Use the Layer 2 VLT fabric for workload migration over virtualized environments. See VLT and Selecting a Layer 2 VLT and Layer 3 with Resiliency (Routed VLT) Fabric Design. b. Layer 3 — Use the Layer 3 distributed core for large fabric deployments.
4. (Optional) Click the Advanced Options to configure VLTi links and fabric links. a. VLTi and Fabric Link options • VLTi link • – Core — Specify the number of links and bandwidth. – Aggregation — Specify the number of links and bandwidth. – Access — Specify the number of links and bandwidth. Fabric Link – Core and Aggregation — Specify the bandwidth. – Aggregation and Access — Specify the bandwidth. b.
To use this feature, you must first configure the Advance Configuration option, Fabric Link between Aggregation and Access, to the maximum bandwidth for each access switch; for example, 120 Gb, at the Network > Design Fabric > New Fabric > Deployment Topology screen. If you do not configure this option, the Fabric Customization screen will be a read-only screen. For information about the Advanced Options, see the section at Configuring Advanced Options. For information about tiers, see Deployment Topology.
• Graphical Wiring Plan — Displays information about how the switches are connected graphically. • Network Topology — Displays information about how the switches are connected physically using a topology map. By default, no links are displayed in the fabric. Click on a switch to display the links in the fabric. When you select a switch, all the fabric interlinks are displayed. When you select a spine switch the links to the leaf switches are displayed.
and access) are displayed. • Tabular Wiring Plan — Displays information about how the switches are connected in the fabric design in a tabular format, as shown below. The tabular wiring plan contains a list of switches along with their names and ports which connect to the ports on the other switches in the fabric.
Figure 53. Example: Visio Output Table 19. Tabular Wiring Plan Output Descriptions Field Name Description From Device (Switch) Displays the name of the device — from the side. From Port Displays the port number on the switch — from the side. To Device (Switch) Displays the name of the device— to the side. To Port Displays the port number on the device — to the side. Usage Status • • • Current — Represents the links based on your current needs.
3. Click the Export link. The Generate Wiring Plan window displays. 4. Specify the following export options. a. PDF — Table, Data, Graphical Wiring Plan, or Both. b. Visio — Network Topology. 5. Click the Generate button. Fabric Design – Step 6: Summary The Summary screen displays a summary of your fabric design. To export the fabric design: 1. Click one of the following export options: • Export Wiring Plan • Export Summary • Export Design 2.
Importing an Existing Fabric Design To import an existing fabric design: 1. Navigate to the Home > Getting Started screen. 2. Click the Importing Existing Design option. The Import Existing Design screen displays. 3. In the Fabric XML file area, click the Browse button and locate the fabric XML design file (the XML design that you have exported from the AFM design wizard). 4. Click the Upload button.
Configuring and Deploying the Fabric 9 After you create a fabric at the Network > Design Fabric > New Fabric screen, you can configure and deploy the fabric at the Network > Fabric Name > Configure and Deploy screen. This screen deploys the configuration to the switches in the fabric. You can deploy auto-generated and custom configurations. This screen contains the following options: • Deploy Fabric — Prepares the fabric for deployment and deploys the fabric.
Fabric Deployment Summary Switch Configuration Phases and States Table 20. Switch Configuration Phases and States Phase State State Description Design Complete Indicates that the design is complete for the switch. NOTE: At switch level, design Partial Complete is not tracked. Partial Complete is only tracked at the fabric level. Pre-deployment Required Configuration Error Indicates that not all required Pre-deployment Configuration information was provided.
Complete Indicates that validation was successful for the switch. Operations Allowed in Each Fabric State To determine which operations are allowed during the design, pre-deployment configuration, deployment, and validation states, use the following table. Table 21.
Complete Partial Complete / Complete Incomplete / Partial Complete / Complete Not Started / In-progress / Stopped / Error / Complete Incomplete indicates that the AFM is in the middle of deploying the switches. Complete indicates all the switches in the distributed fabric are deployed. • • View Wiring Plan Edit Fabric—Allow editing of all fabric attributes except fabric name, fabric type interlink oversubscription, port count, and expand fabric.
To prepare the IOA fabric for deployment, complete the following tasks using the Pre-deployment Configuration wizard. 1. Pre-deployment IOA – Step 1: Management IP 2. Pre-deployment IOA – Step 2: VLAN Configuration 3. Pre-deployment IOA – Step 3: SNMP and CLI Credentials 4. Pre-deployment IOA – Step 4: Software Images 5.
IOA Pre-deployment Wizard IOA Pre-Deployment Screens Use the following IOA Pre-deployment screens to provide the fabric the minimum configuration for a IOA fabric. These screens automate the IOA deployment process. See also Using the Pre-deployment Configuration Wizard. Figure 54. IOA Pre-deployment Workflow • Management IP — Displays all the IOA blades available in the discovered chassis. If the discovered chassis is configured with an IP address, AFM populates with the IP address that you can edit.
• Summary — Displays the fabric name and location of the software image. The pre-deployment configuration for IOA consists of the following tasks: • Pre-deployment IOA - Step 1: Management IP • Pre-deployment IOA - Step 2: VLAN Configuration • Pre-deployment IOA - Step 3: SNMP and CLI Credentials • Pre-deployment IOA - Step 4: Software Images • Pre-deployment IOA - Step 5: Summary For information about IOA pre-deployment error messages, see IOA Pre-deployment Error Messages.
Figure 55. IOA Pre-deployment Management IP Address Screen 1. Navigate to the Network > Fabric Name > Configure and Deploy screen. 2. From the Deploy Fabric pull-down menu, select the Pre-deployment Configuration option. The pre-deployment Introduction screen displays. 3. In the Introduction screen, review the useful information that you need to gather before you begin. 4. Click the Auto Populate IP Address link and in the Start IP Address/Prefix field enter the starting IP address and prefix. 5.
Figure 56. IOA Pre-deployment VLAN Configuration Figure 57. IOA Pre-deployment VLAN Configuration with Populated Data 1. 2. Navigate to the Network > Fabric Name > Configure and Deploy screen. From the Deploy Fabric pull-down menu, select the Pre-deployment Configuration option. The pre-deployment Introduction screen displays. 3. Navigate to the VLAN Configuration screen. 4. From the Chassis pull-down menu, select a chassis name that you want to configure.
5. From the Switch pull-down menu, select the name of the switch that you want to configure. The following Pre-deployment IOA VLAN configuration options are available: Table 22. IOA VLAN Pre-deployment Options VLAN Option Description Add VLAN Creates a VLAN. The range is from 2 to 4094. NOTE: VLAN ID 1003 is reserved. 120 Add VLAN Range Creates a VLAN range. Configure Isolated Network Provides security that can be enabled on a a VLAN or a range of VLANs. Only standalone mode is supported.
Copy Chassis Configuration Copies the chassis configuration from the current chassis to another chassis in the fabric. NOTE: The VLAN configuration is copied symmetrically to the new chassis. For example, the port assigned as Port 1 on the source chassis is also assigned as Port 1 on the destination chassis. 6. Copy Switch Config Copies IOA VLAN configuration to any IOAs inserted in same or different M1000e chassis.
• The VLAN is configured only on the server side interfaces, which is specified as the isolated network. All traffic coming arriving on this interface from the server is sent out to the associated uplink.
NOTE: Before you begin, make sure that you have loaded the software image for each type of switch on to the TFTP or FTP site. NOTE: To download the latest FTOS switch software version, see the "Upload Switch Software" section in the AFM Installation Guide. 1. Navigate to the Network > Fabric Name > Configure and Deploy screen. 2. From the Deploy Fabric pull-down menu, select the Pre-deployment Configuration option. 3. Navigate to the Software Images screen. Figure 59.
3. Navigate to the SNMP and CLI Credentials screen. Figure 60. IOA SNMP and CLI Credentials Screen 4. In the Read Community String field, enter the read community string; for example, “public”. 5. In the Write Community String field, enter the write community string; for example, “private”. 6. From the Protocol pull-down menu, select one of the following protocols: Telnet or SSHv2. 7. In the User Name field, enter the user name. 8. In the Password field, enter the password. 9.
4. Review the IOA pre-deployment summary information. To export configure VLAN information, click the Export link. Figure 61.
5. Click the Finish button. Next Steps a. Deploy the IOA switches from the Network > Fabric > Configuration and Deploy > Deploy and Validate > Deploy screen. NOTE: Before you deploy the IOA switches, make sure that the IOA switches are standalone mode using the following FTOS CLI command: show system stack-unit iom-mode For more information about this command, see the Dell PowerEdge Command Line Reference Guide for the M I/O Aggregator. Figure 62. IOA Deploy and Validate b.
Figure 63. Deploy IOA Fabric and Check for Response Actions IOA Pre-deployment Error Messages Use the following table to troubleshoot the IOA pre-deployment. Error Recommended Action Discovered MAC is different from planned MAC Make sure the MAC provided for this device is correct. Discovered model is different from planned model Make sure the model provided for this device is correct. IOA is not in standalone mode Put the IOA in standalone mode.
Unable to get the MAC Address through Racadm Verify that the chassis/device is reachable and then rediscovery it. Unable to set the Management IP in IOA device Verify that the chassis/device is reachable or a valid management IP/subnet mask/gateway IP is specified.
NOTE: The pre-deployment flowchart does not list all the prerequisites. This flowchart does not include obtaining the fabric interlink and loop back IP address groups. For more information, see Prerequisites. Pre-Deployment Screens To provide the fabric the minimum configuration to the switches, use the following Pre-deployment screens. These screens automate the deployment process. • Assign Switch Identities— Assigns a system media access control (MAC) address to each switch in the fabric.
• Downlink Configuration — (for a Layer 3 Distributed Core or Layer 3 with Resiliency (Routed VLT) fabric) An edge port that connects to the access layer; for example, servers or a ToR. • Fabric link Configuration — (for a Layer 3 or Layer 3 with Resiliency (Routed VLT) fabric. For a Layer 3 fabric, configures options for the spine and leaf to communicate in the fabric. For a Layer 3 with Resiliency (Routed VLT) fabric, the links that connect the core, access, and aggregation switches in the fabric.
Pre-deployment – Step 1a: Uplink Configuration The Uplink Configuration page displays the port bandwidth and the number of specified ports (read-only fields) entered on the Fabric Name and Type and Port Specification screens. To configure the uplink protocol for the edge port uplinks to the WAN, use the Uplink Configuration screen. NOTE: For OSPF, the uplinks or interlinks must be in area 0. Figure 64. Uplink Configuration To configure the uplink protocol for the edge port uplinks to the WAN: 1.
Figure 65. VLAN Configuration without VLAN and VRRP Configuration Table 23. VLAN Configuration Options VLAN Option Description Add VLAN Enter the VLAN ID. Add VLAN Range Automates VLAN creation and automatically populates IP addresses. Enter the following VLAN information: • • Starting VLAN ID — Enter the Starting VLAN ID. The range is 2 to 4094. Number of VLANs — Enter the Number of VLANs. • VLAN Increment. If you do not specify an increment, the VLAN is incremented by 1.
Delete VLAN Removes selected VLAN row. Edit VLAN Change the VLAN ID or VLAN ID, primary IP address, secondary IP address. VLAN ID Enter the VLAN ID. Range: 2 to 4094 Default: Primary IP Enter the primary IP address. The prefix is auto-populated. Validation Criteria for Primary IP: Valid IP Prefix Range: from 8 to 29 Default Primary IP: Default Prefix: 24 Secondary IP Enter the secondary IP address. The prefix is auto-populated.
4. In the VLAN ID field, enter the VLAN ID. 5. In the Primary IP address field, enter the primary IP address. 6. In the Secondary IP address field, enter the secondary IP address. 7. In the Virtual IP address field, enter the virtual IP address 8. Click the Next button to view the Port Channel Configuration screen. Pre-deployment – Step 1c: Port Channel Configuration (Layer 2) Use this screen to optionally add, edit, delete, and automatically populate the port channel configuration.
To create port channels to increase bandwidth and redundancy: 1. Navigate to the Network > Fabric Name > Configure and Deploy screen. 2. From the Deploy Fabric pull-down menu, select the Pre-deployment Configuration option. 3. Navigate to the Port Channel Configuration screen. 4. From the Switch pull-down menu, select a switch to apply the port channel configuration. 5. Click the Add link to manually add a port channel or the Auto populate link to automatically populate the port channels.
5. To the right of the VLAN ID field, click the VLAN ID icon and select one VLAN ID and then associate it with the storage facing port. a. If you are connecting to fibre channel storage facing ports, AFM automatically populates the SAN Fabric ID when you select the VLAN ID. b. If you are connecting to iSCSI storage facing ports, select a VLAN ID and associated it with Vendor.
Pre-deployment – Step 1e: VLAN Mapping (Layer 2 VLT) To add VLANs and associate ports on the different switches for a Layer 2 fabric, use the Downlink Port Configuration screen. Once that is done you can copy switch VLAN or port VLAN configurations. You can be associate one or more tagged VLANs with a port and for untagged VLAN only one is allowed. Table 25. VLAN Mapping Field Descriptions Field Name Description Configured VLANs Displays list of VLANs specified in the VLT VLAN Configuration screen.
Copy VLAN Port Config Copies the VLAN association from a selected port to other port (s) within a switch. Port-VLAN Association Maps the physical port to the VLAN ID. For example, maps 1 port to multiple VLANs. VLAN-Port Association Maps the VLAN ID to physical port interfaces. For example, maps 1 VLAN to multiple ports. Copy VLAN Tagged Port Config Copies the VLAN tagged port configuration from a selected port to other port (s) within a switch.
• Pre-deployment – Step 1b: Uplink Configuration • Pre-deployment - Step 1c: : Downlink Configuration NOTE: For pre-deployment, the Layer 2 VLT, Layer 3 Distributed Core, and Layer 3 with Resiliency (Routed VLT) fabrics use the same pre-deployment configuration screens from step 2 through step 7. Pre-deployment – Step 1a: Fabric link Configuration Before you begin, review the Using the Pre-deployment Configuration Wizard and Pre-deployment Wizard: Introduction sections.
To configure the uplink protocol for the edge port uplinks to the WAN for a Layer 3 distributed core fabric: 1. Navigate to the Network > Fabric Name > Configure and Deploy screen. 2. From the Deploy Fabric pull-down menu, select the Pre-deployment Configuration option. 3. Navigate to the Uplink Configuration screen.
4. In the Type of Uplink Ports area, select one of the following options: a. static routes — When you select the static routes option, AFM displays the Adds Static Route window. You can configure up to 10 static routes for each aggregation device. When you check the of Default Route option , AFM automatically populates the destination network field to 0.0.0.0/0. For static routes, enter the destination network and the next hop.
b. L2 —Configures Layer 2 uplinks for a Layer 2 fabric. By default, this option is disabled on a Layer 3 Distributed Core fabric. c. L3 — Configures uplinks for a Layer 2 VLT or Layer 3 Distributed Core fabric. When you select the L3 option, the Uplink Configuration screen displays additional options to configure the Layer 3 protocol settings.
5. In the Protocol Settings, select a routing protocol (OSPF, IBGP, or eBGP) for the edge port uplinks. The number of uplinks is specified in the Bandwidth and Port Count screen. AFM automatically populates the range of IP addresses that belong to the /30 subnet. a. For OSPF, for each specified uplink, enter the local IP address, remote neighbor IP address, and area ID. A valid area ID area is from 0 to 65535. b.
8. In the Starting VLAN ID field, enter a starting VLAN ID. Range: from 2 and 4094. 9. From the Protocol Profile pull-down menu, when the leaves are acting as a leaf switch (the switches are directly connected to the server), select the Downlink VLAN and VRRP and LAG protocol setting. The default setting is Downlink VLAN. 10. Click Next to go the Assign Switch Identities screen.
6. In the Loopback IP Address Range/Prefix area, enter the loopback address range and prefix. The prefix must be from 8 to 26. 7. In the Area ID field, use the default setting of 0 or enter the area ID. The area ID is a value from 0 and 65535. The uplinks or interlinks must be in area 0 for OSPF.
4. In the Type of Uplink Ports area, select one of the following options: a. static routes — When you select the static routes option, AFM displays the Adds Static Route window. You can configure up to 10 static routes for each aggregation device. When you check the of Default Route option , AFM automatically populates the destination network field to 0.0.0.0/0. For static routes, enter the destination network and the next hop.
b. L2 —Configures Layer 2 uplinks for a Layer 2 fabric. By default, this option is disabled on a Layer 3 Distributed Core fabric. c. L3 — Configures uplinks for a Layer 2 VLT or Layer 3 Distributed Core fabric. When you select the L3 option, the Uplink Configuration screen displays additional options to configure the Layer 3 protocol settings.
5. In the Protocol Settings, select a routing protocol (OSPF, IBGP, or eBGP) for the edge port uplinks. The number of uplinks is specified in the Bandwidth and Port Count screen. AFM automatically populates the range of IP addresses that belong to the /30 subnet. a. For OSPF, for each specified uplink, enter the local IP address, remote neighbor IP address, and area ID. A valid area ID area is from 0 to 65535. b.
Delete VLAN Removes selected VLAN row. Edit VLAN Edit VLAN ID, primary IP address, and secondary IP address. VLAN ID Enter the VLAN ID. Range: 2 to 4094 Default: Primary IP Enter the primary IP address. The prefix is auto-populated. Validation Criteria for Primary IP: Valid IP Prefix Range: from 8 to 29 Default Primary IP: Default Prefix: 24 Secondary IP Enter the secondary IP address. The prefix is auto-populated.
The following screen shot displays a VLT VLAN Configuration screen without selecting the Enable Layer 3 protocol in Access Switches option. By default the VLT VLAN screen for Layer 3 with Resiliency (Routed VLT) requires that you enter the primary and secondary IP address for the VLAN ID as show in the following screen shot. Figure 68.
Figure 69. Layer 3 with Resiliency Using the Enable Layer 3 Protocol in Access Switches Option The following screen shot displays the results after checking the Enable Layer Protocol in Access Switches option and adding VLANs for a Layer 3 with Resiliency (Routed VLT) fabric. Figure 70. Adding VLANs and Enabling the Layer Protocol in Access Switches Option To configure a VLT VLAN for a Layer 3 with Resiliency (Routed VLT) topology: 1. Navigate to the Network > Fabric Name > Configure and Deploy screen.
5. Click the Add VLAN link. The Add VLAN Window is displayed. 6. Click the Add VLAN Range link and then specify the VLAN range to assign the IP addresses to the switches for the Layer 3 with Resiliency (Routed VLT) fabric. 7. Click the Next button to view the Port Channel Configuration screen.
• • • • Start Port Channel ID Number of Port Channel Port Channel Increment Enable LACP (optional) Copy Switch Port Channel Configuration Copies over switch port channel configuration from another switch. You first create a port channel configuration and then you can copy over to another switch. Delete Deletes a selected port channel configuration. Edit Enter the port channel configuration. Figure 73. Port Channel Configuration Screen To create port channels to increase bandwidth and redundancy: 1.
Table 29. VLAN Mapping Port Field Descriptions Field Name Description Configured VLANs Displays list of VLANs specified in the VLT VLAN Configuration screen. Port Name Displays the port name. This a read only field. Tagged VLANs Manual Entry: Enter one or more VLANs to associate with the port. Validation Criteria: The VLANs have to be from the Configured VLANs list and the Untagged VLAN field should be empty. Default: Untagged VLANs 1.
2. From the Deploy Fabric pull-down menu, select the Pre-deployment Configuration option. 3. Navigate to the Layer 3 with Resiliency (Routed VLT) VLAN Mapping screen. 4. Select one of the following options: 5. • Port-VLAN Association — Maps the physical port to the VLAN ID. For example, maps 1 port to multiple VLANs. • VLAN-Port Association — Maps the VLAN ID to physical port interfaces. For example, maps 1 VLAN to multiple ports.
6. In the Tagged VLANs, click on the icon next and enter one or more VLANs to be associated with the port. 7. When you are finished, click the Next button to go to the Assign Network Identities screen. Pre-deployment – Step 1e: VLAN Mapping (Layer 2 VLT) To add VLANs and associate ports on the different switches for a Layer 2 fabric, use the Downlink Port Configuration screen. Once that is done you can copy switch VLAN or port VLAN configurations.
Copy Switch VLAN Config Copies the VLAN association from the current switch to other switch (es) in the fabric. Copy VLAN Port Config Copies the VLAN association from a selected port to other port (s) within a switch. Port-VLAN Association Maps the physical port to the VLAN ID. For example, maps 1 port to multiple VLANs. VLAN-Port Association Maps the VLAN ID to physical port interfaces. For example, maps 1 VLAN to multiple ports.
The following is a sample CVS file. Table 33. Sample CSV Format serial_number purchase_order mfg_part_number mac_address server_tag HADL134J20193 163 759-0096-02 REV.F 9RGZTS2 00:01:E8:8B: 15:77 NOTE: Before you begin, obtain the CSV file that contains the system MAC addresses, service tag, and serials numbers for each switch provided from Dell manufacturing or manually enter this information. To assign switch identities: 1.
Pre-Deployment – Step 4: SNMP and CLI Credentials Use this screen to configure SNMP and CLI credentials at the fabric level. Configure SNMP so that the AFM can perform SNMP queries on the switches in the fabric. 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. The write community string is populated from the AFM global setting, which is configure during installation.
6. Click Next to go to the DHCP Integration screen. Pre-Deployment – Step 6: DHCP Integration The DHCP Integration screen uses the information configured at the Assign Switch Identities, Management IP, and Software Images screens to create a DHCP configuration file named dhcpd.
5. Install the DHCP file onto the DHCP server before your deploy the fabric. 6. Click Next to go to the Summary screen. Pre-Deployment – Step 7: Summary To review the pre-deployment configuration, use the Summary screen.
3. From the Deploy pull-down menu, select View DHCP Configuration. For more information on DHCP, see DHCP Integration. Deploying and Validating the Fabric This section contains the following topics: • Deploying the Fabric • Validate the Fabric • Viewing Deployment and Validation Status Deploying the Fabric To deploy the fabric, use the Network > Fabric Name> Configure and Deploy > Deploy Fabric > Deploy and Validate screen.
2 Complete Deployment successfully completed. NA 3 Error Protocol transfer failed Verify TFTP/FTP connectivity; verify FTP credentials. 5 Error Device cleanup task failed 6 Error Complete config upload failed 1. From the AFM, verify the switch connectivity using Telnet or SSH. 2. Restart the deployment of the switch from the Network > Fabric Name > Configure and Deploy screen by selecting the switch from the list and then click on the Deploy Selected link. 1.
12 InProgress Device cleanup task done, reload in progress... NA 13 InProgress Complete config upload in progress... NA 14 InProgress Smart script transfer Inprogress... NA 15 InProgress Custom config upload in progress... NA 16 InProgress Backup config in progress... NA 17 InProgress Merged config upload in progress... NA To deploy a fabric: 1. Verify that the software images for the switches are installed on to the TFTP or FTP server. 2.
10. Select the Apply configuration changes to the switch option or the Overwrite entire configuration on the switch option. When you deploy a switch, the following options are available: • Apply configuration changes to the switch– Apply new configuration changes from the AFM Server to the switch. • Overwrite entire configuration on the switch – Overwrites the entire current configuration on the switch instead of applying only the changes to the current switch configuration.
View the Auto-generated Configuration To view the AFM auto-generated configuration: 1. Navigate to the Network > Fabric Name > Configure and Deploy > Deploy Fabric > > Advanced Configuration > View Auto-Generated Configuration screen. 2. From the Deploy Fabric pull-down menu, select the Deploy and Validate option. 3. On the Deploy tab, click the Advanced Configuration link. 4.
2. From the Deploy Fabric pull-down, select the Deploy and Validate option. 3. On the Deploy tab, select the Advanced Configuration link and then click the Add Switch Specific Custom Configuration link. The Switch Specific Custom Configuration screen displays. Figure 74.
4. Click the Preview Combined Configuration screen. The Combined Configuration screen displays. Validation To verify that the discovered fabric matches the planned fabric and correct any errors, use the Validate screen . Mismatches are reported as errors and the corresponding alarms generate. If you fix the errors found during validation, to verify that all the issues were fixed according to the planned fabric, validate the fabric again. Validation Status Validation Sl.
7 Error Switch is not Discovered 1. Navigate to the Network > Fabric Name > Configure and Deployment screen. 2. Click the Errors link. 3. Click on the Discovered Errors tab to view error details. 4. Fix any errors. Verify the switch connectivity from the AFM. 1. 2. 8 Error Configuration mismatch errors exists 3. Click on the Undiscovered Errors tab to view error details. 4. Fix any errors. Check for switch configuration mismatch errors: 1.
11 InProgress Node validation in progress... NA 12 InProgress Configuration Validation in progress... NA 13 InProgress Wiring Validation in progress... NA Validating the Fabric To verify that the discovered fabric matches the planned fabric and correct any errors: 1. Navigate to the Network > Fabric Name > Configure and Deploy screen. The Configure and Deploy screen displays. 2. In the Switch column, select the switches to validate. 3. Click the Validate Selected link. 4.
Adding Templates You can add (create) a CLI configuration template. This is useful for applying a custom configuration to the following: • Specific switches in a fabric • All the aggregation switches in the fabric • All the access switches in the fabric • All the core switches • All the switches in the fabric • All the leafs in the fabric • All the spines in the fabric To add templates: 1. Navigate to the Network > Fabric > Configure and Deploy screen. 2.
You can only delete one template at a time. If you attempt to delete a template that is being used, AFM displays an error message indicating which fabric(s) the template is associated with. NOTE: To delete a template, you must have superuser or administrator privileges. To delete templates: 1. Navigate to the Network > Configure and Deploy screen. 2. From the CLI Configuration, select the Managing Templates pull-down menu. 3. Select the template and then click the Delete Link option. 4. Click Yes.
2. From the CLI Configuration pull-down, select the Associate Template option. The Templates screen displays. 3. Click the Add Template link. 4. In the Template Name field, specify a unique name for the template. 5. (Optional) In the Description field, enter a description of the template. 6. In the Configuration Commands: area, enter the CLI (FTOS) configuration commands that you want to include in the template. 7. Click the OK button.
To copy templates: 1. Navigate to the Network > Fabric > Configure and Deploy screen. 2. From the CLI Configuration pull-down, select the Manage Templates option. The Templates screen displays. 3. Click on the Copy Template link. The Copy Template displays. 4. Select the template to copy. 5. In the Template Name field, enter a unique name for the new template. 6. Click the OK button.
7. • Leafs — Associates the template to all the leaf switches. • Spines — Associates the template to all the spine switches. Click the Apply button. Editing Template Associations To edit a template association: 1. Navigate to the Network > Fabric > Configure and Deploy screen. 2. From the CLI Configuration pull-down menu, select the Associate Templates option. 3. Select the template to edit the association. 4. Click the Edit Association link. 5. Edit the association. 6. Click the OK button.
Figure 75. Switch Specific Custom Configuration The Switch Specific Custom Configuration screen provides support to view the auto-generated configuration and switch-specific custom configuration that is applied to the individual switches in the fabric. Only the switches that are deployed are listed. 4. Enter the switch specific-custom configuration (FTOS CLI commands) in the Switch Specific Custom Configuration area. 5.
To view custom configuration history: 1. Navigate to the Network > Fabric Name > Configure and Deploy screen. 2. From the CLI Configuration pull-down menu, select the View Custom Configuration History option. The Custom Configuration History displays.
Viewing the Fabric 10 This section contains the following topics: • Dashboard • View Network Summary • View Fabric Summary • Switch Summary Related Links: Fabric Performance Management. Dashboard To view the fabric and system health, use Home > Dashboard screen as shown. Figure 76.
Figure 77. Dashboard with Color Codes The Dashboard provides the following key performance information: • System — Provides a tabular listing of system health and fabrics being managed by the AFM and lists the corresponding alert count by severity. The Switch Health column displays the number of switches that are alert free and the total switches that are part of the fabric. • Average Port Bandwidth Utilization — Displays the average port bandwidth utilization for all fabrics managed by the AFM.
– Last Values (%): number with color code bar Table 36. CPU Utilization Color Codes Color Range Description Green (Good) x < 70 % Represents normal CPU utilization. Yellow (Minor) x > = 70 % and x < 80% Represents low CPU utilization. Red (Critical) x > = 80 % Represents high CPU utilization. NOTE: When the color code is yellow or red, the AFM displays an alarm at the Network > Fabric Name > Switch Name > Alerts and Events > Current screen.
Figure 78. Network Summary Tabular View Network Topology Graphical View The network topology contains fabric icons.
• Enable Move: After enabling this option, you can move each fabric icon to a new location in the map. • Revert to Last Saved: Revert to fabric locations to last saved version. • Save Move: Save the location of the fabrics that were moved. • Popup menu: Right-click a fabric to display a menu that contains actions that can be applied to the fabric. The menu contains the fabric name and “Open” menu item, which opens the fabric view.
Displaying the Fabric in a Tabular View With the fabric tabular view, you can view the switches in the fabric and check alarms. Export your results using the Export link. • You can also manage or unmanage a switch using the Manage/Unmanage Switch • You can display additional performance statistics about a fabric using the Launch Active Link option by navigating to the Network > Fabric level > Tabular screen.
Figure 79. Fabric Summary Screen in Graphical View For information about how to configure the Active Link, navigate to the Administrative > Settings > Active Link Settings screen. • Show Tooltips — Displays information (fabric, switch name, model name, IP address, alarm status, and manage state) about a switch when you place the cursor over the switch. • Show All Links — Displays all the links between the spines and the leaves, aggregation and access, or aggregation, access, and core.
• Active Alerts • Speed • Manage State 186 Viewing the Fabric
Troubleshooting 11 This section contains the following topics: • Ping, Traceroute, SSH, and Telnet • Validation Alarms • Deployment and Validation Errors • TFTP/FTP Error • Switch Deployment Status • Validating Connectivity to the ToR For more information about troubleshooting, see Ping, Traceroute, SSH, and Telnet.
1. Navigate to the Network > Fabric Name > Switch Name > Troubleshoot screen. . 2. Click the SSH tab. 3. In the SSH Command field, enter the SSH command. 4. Click the Send Command button to display the SSH results. Telnet To issue a Telnet command on a switch: 1. Navigate to the Network > Fabric Name > Switch Name > Troubleshoot screen. 2. Click the Telnet tab. 3. In the Telnet Command field, enter the Telnet command. 4. Click the Send Command button to display the Telnet results.
Validation failed because the switch has a name mismatch. 1. c. Click on the Validation tab and the check the switch to validate. d. Click the Validate Selected link. Verify that you have correctly mapped the system MAC address to the associated switches: a. Navigate to the Network> Fabric Name > Configure and Deploy screen. b. From the Deploy Fabric pull-down menu, select the Pre-deployment Configuration option. c. 2. Validation failed because the switch has a model mismatch. 1.
Validation failed because the switch is in a disconnected state. The switch is not reachable. Verify the reachability of the switch. Validation failed because Te 0/1 has a wiring mismatch. 1. Reviewing the wiring plan. 2. Wire according to the wiring plan to fix the wiring mismatch. 3. Make sure that the ports on the switches have accurately mapped. Validation failed because Te 0/1 has a missing link. No connectivity is detected to the switch. Check the cables.
Overwrite DHCP contents to local Verify the permission of the directory and disk space availability on DHCP server failed. the AFM server; verify the local DHCP server configuration and then restart the DHCP Integration step using Pre-deployment Configuration wizard. To restart the DHCP Integration: 1. Navigate to the Network > Fabric Name > Configure and Deploy screen. 2. From the Deploy Fabric pull-down menu, select the Predeployment Configuration option. 3. Restart the DHCP Integration step.
Validation Errors Use the following tables to troubleshoot the following validation errors when you deploy a fabric. Validation reports any inconsistencies between the design and the discovered fabric. The mismatches are reported by AFM as errors and the corresponding alarms that are generated.
Table 39. 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 screen by selecting the switch from the list and clicking the Start Validation button. Table 40.
3. From the AFM server, verify that the connectivity to the switch exists. 4. Verify that the switch is running the minimum required software. 5. Validate the switch. a. Navigate to the Network > Fabric Name > Configure and Deploy. b. From the Deploy Fabric pull-down menu, select the Deploy and Validate option. c. Click the Validation tab and then select the switches to validate. d. Click the Deploy Selected link. Table 42.
System MAC Address Mismatch c. Click the Validation tab and then select the switches to validate. d. Click the Deploy Selected link. 1. Verify that the IP address to switch name mapping is correct in the pre-deployment configuration. 2. If the pre-deployment configuration is updated, you might need to redeploy the switch. 3. Validate the switch. a. Navigate to the Network > Fabric Name > Configure and Deploy screen. b.
list and then click on the Deploy Selected link. NOTE: The switch is in BMP mode. CONFIG GENERATION SUCCESS Configuration File Generation Completed Successfully No Information only. CONFIG FILE TRANSFER IN Configuration File PROGRESS Transfer In-progress No Information only. CONFIG FILE TRANSFER FAILED Yes Configuration File Transfer Failed 1. Verify the connectivity to the TFTP server from the AFM server. 2.
file matches the csv. file that contains the MAC addresses of the switches. 4. Verify that the min.cfg file is in the correct directory on the TFTP/FTP server. 5. Redeploy the switch from the Network > Fabric Name > Configure and Deploy screen by selecting the switch from the list and then click on the Deploy Selected link. NOTE: The switch is in BMP mode. MIN CONFIG UPLOAD COMPLETED Minimum Configuration Upload Successful No Information only.
5. Redeploy the switch. NOTE: The switch is not in BMP mode. a. Navigate to the Network > Fabric Name > Configure and Deploy screen. b. From the Deploy Fabric pull-down menu, select the Deploy and Validate option. c. On the Deploy tab, check the switch to deploy and then click the Deploy Selected link. PROTOCOL CONFIG UPLOAD COMPLETED Protocol Configuration Upload Succesful No Information only. DEVICE DEPLOYMENT SUCCESS Switch Deployment Successful No Information only.
deploy and then click the Deploy Selected link. UPLINK RECONFIGURED REDEPLOY REQUIRED REDEPLOYMENT REQUIRED Uplink re-configured, Re-deployment of Switch is required Re-deployment of the switch is required Yes Restart the deployment of the switch. NOTE: The switch is not in BMP mode. Yes 1. Navigate to the Network > Fabric Name > Configure and Deploy screen. 2. From the Deploy Fabric pulldown menu, select the Deploy and Validate option. 3.
Reset to factory defaults Reset to factory defaults task: Failed Verify Telnet/SSH connectivity and deploy again Minimal Minimal config upload: configuration Failed upload to switch Verify Telnet/SSH connectivity and deploy again Minimal config upload on Unit-1: Failed Verify Telnet/SSH connectivity and deploy again Reload of switch Reboot of switch: Failed Verify Telnet/SSH connectivity and deploy again Boot image error Boot image was not loaded from flash Change the boot image path to flash by ex
TFTP/FTP Error To troubleshoot TFTP/FTP when the deployment status is “TFTP /FTP Failed”, use the following table. Table 45. Deployment Status Configuration Errors Deployment Status Error Category TFTP/FTP Failed Configuration Deployment Error Error Details Recommended Action Error occurred during TFTP/FTP 1. Check the TFTP/FTP connectivity on the network. 2. Make sure that you have specified the correct TFTP/FTP address at the Administration > Settings screen.
Alerts and Events 12 This section contains the following topics: • Current — Active Alerts • Historical — Alerts and Events Current — Active Alerts To view active alerts at the network, fabric and switch levels, use the Current tab. To acknowledge an active alert, select the active alert and then click the Acknowledge button. To display more information about the active alert, select the active alert. The system displays more information about the alert at the bottom of the screen.
Figure 81. Fabric Alerts • To filter active alerts at the switch level, navigate to the Network > Fabric Name > Switch Name > Alerts and Events screen. Figure 82. Switch Alerts 1. Click the Current button. 2. Click the filtering icon on the right of the screen. You can use the filter options, from date and to date. The filtering options display.
3. In the Severity pull-down menu, select one of the following filtering criteria: a. b. c. d. e. f. g. h. i. All Critical Major Minor Cleared Warning Unknown Info Indeterminate 4. In the Source IP field, enter the source IP address. 5. In the Source Name field, enter the source name. 6. In the Description field, enter a description. 7. In the Ack (acknowledgement) pull-down menu, select one of the following: a. All b. Yes c. No 8. Click the Apply button.
7. In the Ack (acknowledgement) pull-down menu, select one of the following: a. All b. Yes c. No 8. Click the Apply button. 9. If you want to export your results, click the Export link.
Performance Management 13 You can monitor performance at the network, fabric, switch, and port level.
Fabric Performance Management To monitor the following for all the switches in the fabric, use the Network > Fabric Name > Performance screen: • Bandwidth utilization • Top 25 port inbound usage • Top 25 port outbound usage • Top 10 highest CPU utilization • Top 10 high memory utilization Switch Performance Management To view historical and real-time data switch level performance, use the Network > Fabric Name > Switch Name > Performance screen .
Port Performance Management To view a summary of historical and real-time data port performance: 1. Navigate to the Network > Fabric Name > Switch Name > Summary screen.
Figure 83. Displaying Summary of Port Performance 2. Select a port and then click on the Performance tab to view port performance. 3. Click the Real-Time Data or Historical button. 4. Select one of the following View Type options to display port performance: Bar, Graphical, or Tabular. 5. Review the performance information.
2. Click the Performance tab at the bottom of the screen. Figure 84. Display Detailed Port Performance 3. In the upper right of the screen, select the format to view the data using the Graphical or Tabular options. 4. In the lower left of the screen near the Performance tab, select the Real-Time Data or Historical Data option. The default is real-time data. • For real-time data, from the Interval (seconds) pull-down menu, select the interval to collect real-time data (15, 30, 45, 60) seconds.
5. Check the fabric to collect data from. 6. Click the OK. Threshold Settings To configure the monitoring link bundle and Threshold Crossing Alert (TCA) between the spine switches and the leaf switches for a fabric, use the Jobs > Data Collections > Edit Threshold Settings screen. The Average Traffic Threshold option monitors the Layer 3 fabric link bundle.
Figure 85. Example: TCA Exceeds the Threshold For information about how to view port performance, see Port Performance. Make sure that you select the Real-Time Data option. Reports This section contains the following topics: • Creating New Reports • Editing Reports • Running Reports • Deleting Reports • Duplicating Reports NOTE: To run a report, schedule the data collection to start the task. See Data Collection. Creating New Reports To create a new report: 1.
5. In the Type and Output field: a. Select a report type: Switch or Port. b. Select a report output format: Tabular or Chart. 6. Click Next. 7. In the Date/Time Range pull-down menu, select a date or time range using one of the following options. If you select the custom range, specify a start and end date. a. b. c. d. 30 days 7 days 24 hours Custom Range 8. Click Next. 9.
Duplicating Reports To duplicate a report: 1. Navigate to the Network > Fabric Name > Reports screen. 2. Select a report to duplicate. 3. Click the Duplicate button. The Duplicate screen displays. 4. In the Report Name field, enter the name of the report. 5. (Optional) In the Description field, enter a description. 6. Modify the report as needed. 7. Click the Next button to navigate to different parts of the report that you want to duplicate. 8. Click Finish.
Maintenance 14 This section contains the following topics: • Backing Up the Switch Configuration • Viewing and Editing the Switch Backup Configuration • Scheduling Switch Software Updates • Replacing an IOA Blade Switch • Replacing a Switch • Updating the AFM Back Up Switch To schedule the number of days to keep switch backup files on the AFM, use the Back Up Switch screen.
6. • Restore Startup Config (default) • Restore Running Config Click the OK button. Deleting a Backup Configuration To delete a switch backup configuration: 1. Navigate to the Network > Fabric Name > Maintenance screen. 2. Click the Switch Backup button to display the switch backup options. 3. Select a backup switch configuration to delete. 4. Click the Delete link to delete the switch backup configuration. 5. Click the Yes button. Editing Description To edit a switch backup description: 1.
Figure 86. View and Edit Switch Backup Screen Configuration Screen 3. Click the Close button to exit from this screen. Updating the Switch Software The Network > Fabric Name > Maintenance > Update Software screen displays the summary of software for each switch in the fabric. This screen has the following options: • Schedule Switch Software Update — Creates new schedule job software image upgrade and software image activation.
NOTE: During the rediscover process, AFM sets the previously configured IP address on the replacement IOA blade switch. 4. Deploy the successfully discovered replacement IOA blade switch with the Overwrite entire configuration on the switch deploy option. Replacing a Switch To replace a switch in the fabric: 1. Decommission Switch 2. Replace Switch 3. Deploy Switch You must replace the switch with same type of switch.
Before you replace a switch, gather the following useful information: • Obtain the system MAC address, service tag and serial number for the new switch to be used for replacement, provided from Dell. • Location of the switch, including the rack and row number from your network administrator or operator. • Remote Trivial File Transfer Protocol (TFTP) / File Transfer Protocol (FTP) address from your network administrator or operation.
Step 3: Deploy Switch To deploy a replacement switch: 1. Navigate to the Network > Fabric Name > Switch Name screen. 2. Click the Switch Replacement tab. 3. Click the Deploy Switch link. Note: If you make changes to the switch outside of the AFM; for example, using Telnet, you might need to use the restore option to restore the switch configuration. Updating the AFM To view and manage AFM server updates. use the Administration > Update Server screen. Updating the AFM Server 1.
Activating the AFM Standby Partition Navigate to the Administration > Update Server screen and then click the Activate Available Partition link.
Jobs 15 This section contains the following topics: • Displaying Job Results • Scheduling Jobs Displaying Job Results To display the status of your jobs, use the Job Results screen. 1. Navigate to the Jobs > Jobs Results screen. 2. In the upper right of the screen, click the filter icon to filter your job results. 3. In the Job Name field, enter the job name. 4. In the Status pull-down menu, select one of the following filtering options: • All • Success • Failure • In Progress 5.
NOTE: You can only change the scheduled time. You cannot change the job name, image location, or switch. • Delete — Deletes a job. Select a job and then click the Delete link. • Enable — Enable the job or activate the schedule. • Disable — Disable the job or the schedule, without having to delete the job. Switch Backup To backup a switch running configuration and startup configuration files, use the Switch Backup screen. 1. Navigate to the Jobs > Scheduled Jobs screen. 2.
5. Click the Next button. The Switch Select screen is displayed. 6. In the Available area, select the fabric and then switches to update. • 2 Tier distributed core filtering options — All, Spine, and Leaves • 2 Tier VLT options — All, Aggregation and Access • 3 tier filtering options — All, Core, Aggregation and Access 7. Click the >> button to move the switches to update to the Selected area and the click the Next button. 8.
7. • 2 Tier distributed core filtering options — All, Spine, and Leaves • 2 Tier VLT options — All, Aggregation and Access • 3 tier filtering options — All, Core, Aggregation and Access Click the >> button to move the selected switches into the Selected area and then click the Next button. The Schedule screen displays. 8. Select one of the following options and then click the Next button: • Run Now — Actives the standby partition immediately.
7. • Enter the path and image name of the software file on the TFTP or FTP site for each type of switch. • Click the Next button. In Update Option • Select one of the following options: – Manual — Update is staged to the secondary partition but not applied. – Automatic — Apply software update and reboot. • 8. 9. Click the Next button. In the Schedule screen, select one of the following options and then click the Next button: • Run Now — Run the switch software update immediately.
1. Navigate to the Network > Fabric Name > Maintenance screen. 2. Click the Switch Backup button to display the switch backup options. 3. Click the Switch Backup link. The Job Name screen displays. 4. In the Name field, enter the name of the software job name. 5. In the Description field, optionally enter a description and then click the Next button. The Select Switches screen displays. 6. Navigate to the Available area: a.
Administration 16 This section contains the following topics: • Administrative Settings • Managing User Accounts • Managing User Sessions Administrative Settings To configure administrative settings, use the Administration > Settings screen: • Active Link Settings • CLI Credentials • Client Settings • Data Retention Settings • DHCP Server Settings • NTP Server Settings • SMTP Email • SNMP Configuration • Syslog IP Addresses • System Information • TFTP/FTP Settings NOTE: The AFM
openmanage-network-manager. Refer to the release notes or AFM Installation Guide for the supported versions of OMNM. Important: Install the Dell OMNM software onto a different server other than the AFM. To activate the performance statics, login directly as write permission into Dell OMNM web service. Important: By default, the web service is turned off in the OMNM server. To use the OMNM web service: 1. On the OMNM server go to the server installation directory. 2. Navigate to the installed.
b. Network > Fabric > Details screen. c. Network > Switch > Summary screen. By default, the topology view and link status refreshes every 60 seconds. To change the interval, navigate to the Administration > Settings screen. The Active link is available at the following screens. • Navigate to the Network > Fabric > Graphical view. Under the Action menu list, select the Launch Active Link option. • Navigate to the Network > Fabric > Graphical view.
5. In the Password field, enter the password. 6. In the Confirm Password field, confirm the password. The privilege level is a read-only field and is set at 15. 7. In the Enable Password field, enter a password for the privilege level. 8. In the Confirm Enable Password field, confirm the enabled password for the privilege level. 9. Click OK.
• 3. Remote — Use External DHCP server. When you select this option, manually install the dhcpd.conf file that is generated during pre-deployment into the DHCP server before you deploy the fabric. Click the OK button. NTP Server Settings To configure NTP Server Settings: 1. Navigate to the Administration > Settings screen. 2. In the NTP Server Settings area, click the Edit link. 3. Enter the NTP server primary IP address. 4. Enter the IP status address. 5.
4. In the Write Community String field, enter the write community string. For example, “private”. 5. In the Port field, enter the SNMP port number of the switches. The port number is typically 161. 6. In the Trap Host field, specify the IP address of the AFMso that the traps are sent to the AFM. 7. Click OK. Syslog Server IP Addresses 1. Navigate to the Administration > Settings screen. 2.
• Add User — Adds new user accounts. You can have up to 50 user accounts but only one Superuser. • Edit User — Edits user accounts. • Change Password — Allows a user to change his or her password. • Delete User — Deletes one or more user accounts. The system default user, Superuser, cannot be deleted. • Unlock — Unlocks a user who was locked out because he or she exceeded the maximum login attempts. To unlock a user, select the user and click the Unlock option.
Adding a User To add a user account, you must be a Superuser. For more information about user accounts, see Managing User Accounts. To add a user: 1. Navigate to the Administration > User Accounts screen. 2. Click Add User. The Add User screen displays. 3. In the User Name field, enter the user’s name. Enter a unique name that is alphanumeric. Length: from 1 to 25 characters. 4. In the Password field, enter the user’s password.
12. In the Lockout Duration pull-down menu, select one of the following options. The default value is 30 minutes. a. b. c. d. e. 15 minutes 30 minutes 45 minutes 60 minutes Permanent 13. Click OK. Deleting a User To add or delete users, you must be a Superuser . For more information about user accounts, see Managing User Accounts. To delete a user: 1. Navigate to the Administration > User Accounts screen. 2. Select the user that you want to delete. 3. Click the Delete button. 4. Click Yes.
Unlocking a User To unlock a user, you must be a Superuser . For information about user accounts, see Managing User Accounts. To unlock a user: 1. Navigate to the Administration > Users Accounts screen. 2. Select the user you want to unlock. 3. Click the Unlock button. 4. Click OK. Changing Your Password To change your password: 1. Go to the upper right of the screen next to your login name. A pull-down menu displays. 2. Select Change Password. The Change Current Account Password screen displays.
To terminate AFM 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. Audit Log To log a chronological sequence of audit records, each of which contains information on who has accessed the switch and what operations the user has performed during a given period of time, use the Audit Log screen.
7. From the Status pull-down menu, select the one of the following status of audit trail operations: a. b. c. d. e. f. g. 8. 242 Queued In Progress Success Failure Timeout Response Delivered Invalid Request Click the Apply button. You also export your results using the Export link.
