Active Fabric Manager (AFM) User 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 - 10 Rev.
Contents 1 Introduction........................................................................................................... 9 2 Getting Started....................................................................................................10 Designing and Deploying a Fabric...................................................................................................... 10 3 Site Map..............................................................................................................
Use Case 5: Three-Tier Layer 2.....................................................................................................57 Use Case 6: Three-Tier Layer 3 Resiliency (Routed VLT).............................................................57 Using the Fabric Design Wizard..........................................................................................................58 Fabric Design – Step 1: Fabric Name and Type.............................................................................
Pre-Deployment – DHCP Integration........................................................................................132 Pre-Deployment – Summary......................................................................................................133 Viewing the DHCP Configuration File.............................................................................................. 133 Deploying and Validating the Fabric........................................................................................
Validation Errors.......................................................................................................................... 164 Switch Deployment Status Errors..................................................................................................... 167 Deployment Task Errors.................................................................................................................... 171 TFTP/FTP Errors.........................................................................
Restoring a Switch Configuration .............................................................................................. 197 Deleting a Backup Configuration................................................................................................197 Editing a Description................................................................................................................... 197 Viewing and Editing the Switch Backup Configuration.........................................................
Managing User Sessions................................................................................................................... 216 Audit Log............................................................................................................................................217 16 Technical Support.......................................................................................... 219 Accessing Dell License Portal .......................................................................
Introduction 1 Active Fabric Manager (AFM) is a network automation and orchestration tool with a graphical user interface (GUI) 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.
2 Getting Started NOTE: To view this document in AFM, select the User Guide option from the Help drop-down menu in the upper right. Figure 1. Help Menu — User Guide Designing and Deploying a Fabric This section provides an overview of the steps required to design and deploy a fabric, including the information you need before you begin. NOTE: If you are using the OpenStack Neutron Managed option, refer to the AFM Plug-in for OpenStack Guide.
• Overview of a Distributed Core • Terminology • 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.
3 Site Map To navigate the AFM user interface, refer to the following site map.
• • Revert to Last Saved Save Move Search by fabric name Fabric Level Summary Fabric View Actions • View Switch Topology • Manage/ Unmanag e Switch Topology Options • Show Tooltips • Hide Links Search by switch name Alerts and Events Current Historical Performance Average Bandwidth Utilization Link Usage Acknowled Switch ge/ Statistics Unacknowl edge/Clear Maintenance Configure and Deploy Schedule Switch Fabric Software Image Update Deploy Fabric Schedule Activate Standby • Device MAC Partition Asso
View Wiring Plan Switch Level Summary Device View Graphical and Tabular View Jobs Job Results Alerts and Events Current Historical Acknowled ge/ Unacknowl edge/Clear Scheduled Jobs Add • • • Performance Switch and Port Realtime and Historical data Troubleshootin g Switch Replacement Ping Decommissi on Switch SSH Traceroute Telnet Data Collections Replace Switch Deploy Switch Reports New Report Schedule data collection Run Switch Backup Edit threshold Edit Switch Duplicate Softwar e Image Up
Syslog IP Addresses System Information Active Link Settings Data Retention Settings Client Settings NTP Server Settings DHCP Server Settings Secure SMTP Email Settings Site Map 15
4 Supported Fabric Types 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, refer to 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 2. Getting Started Tab Key Considerations for Designing a Layer 3 with Resiliency (Routed VLT) Fabric To extend equal cost multipathing capabilities, use the Layer 3 with Resiliency (Routed VLT) fabric. When designing a Layer 3 with Resiliency (Routed VLT) fabric, consider the following: • You can deploy up to 10 fabric designs. However, the fabric designs do not communicate with each other. • AFM manages Dell Networking S4810, S4820T, S6000, and Z9000 switches.
• The number of planned edge ports (future uplinks and downlinks) for the access switches. • Whether the access switches need to act as a ToR or access. • Fabric interlink bandwidth (the links between the aggregation and access switches). • Downlinks (1 Gb, 10 Gb, or 40 Gb). • The fabric interlink bandwidth (10 Gb or 40 Gb) is fixed and based on the fabric type.
Conventional Core Versus Distributed Core This section describes the differences between a conventional core and a distributed core. 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. High availability, which provides redundancy and resiliency, requires chassis-based core routers.
This two-tier network design allows traffic to move more efficiently in the core and at a higher bandwidth with lower latencies than most traditional three-tier networks. Since there is no single point of failure that can disrupt the entire fabric, the distributed core architecture is more resilient and there is less impact on the network if a link or node failure occurs. AFM views the distributed core as one logical switch. NOTE: There are no uplinks on the spines. All the leaves have downlinks.
• Edge ports — The uplinks and downlinks on the 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 two.
NOTE: In a single distributed fabric, all the leaves can act as a non-ToR or as a ToR, not both at the same time.
• Overview of a Distributed Core • Key Core Design Considerations For a Layer 3 distributed core topology, select the Layer 3 option in the Design Wizard on the Deployment Topology screen. For information about distributed core fabric, refer to Selecting a Distributed Core Design. DL BW — Downlink Bandwidth UL BW — Uplink Bandwidth FLBSL — Fabric Link bandwidth between the spine and leaf MND — Maximum number of downlinks NOTE: The maximum number of downlinks is based on two uplinks. Table 1.
Figure 3. 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 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–16 spines. The Type 1: Extra Large Distributed Core Design uses a 1:1 spine-to-leaf ratio.
Figure 4.
Figure 5. Type 3: Medium Distributed Core Fabric Design Use the Type 3: Medium Distributed Core design if: • You require a 40 Gb fabric interlink (fabric links) bandwidth between the spines and leaves. • The current and planned uplinks and downlinks on the leaves for your distributed core fabric are 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.
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 shown in the following figure. Figure 6.
• by allowing LAG terminations on two separate distribution or core switches • by supporting a loop-free topology, similar to how STP prevents any initial loops that may occur prior to VLT being established NOTE: After VLT is established, RSTP may be used to prevent loops from forming with new links that are incorrectly connected and outside the VLT domain.
• Uplinks — An edge port link on the first two aggregation switches in the VLT fabric that connects to outside the fabric. • Downlinks — An edge port link that connects the access switches to the access layer. For example, servers or ToR elements. • Fabric Interlinks (Fabric Links) — The fabric interlink bandwidth is fixed: 10 Gb or 40 Gb. – For a one-tier fabric, fabric interlinks connect a pair of aggregation switches.
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 a VLT fabric, AFM manages Dell Networking S4810, S4820T, S55, S60, S5000, S6000, Z9000, IOA blade and MXL blade switches. CAUTION: If you are already using a deployed switch, you must reset the factory settings.
load the correct software image configuration file for each type of switch from the TFTP/FTP site during BMP. For information about BMP, refer to DHCP Integration. • The pool of IP addresses for the management port for each switch in the fabric. • The IP addresses (must be an even number) for the uplink configuration from the ISP service. The uplink port number range is based whether a 10 Gb or 40 Gb bandwidth is selected. – For a 10 Gb bandwidth, AFM supports 2–32 uplinks.
UL BW = Uplink Bandwidth UL AVC = Aggregation VLTi Capacity Table 3.
One and Two-Tier ToR 10 Gb for Layer 2 LAN/SAN for Fibre Channel Topologies Table 5. One-Tier LAN/SAN Layer 2 for Fibre Channel — 10 Gb Downlinks Downlink Bandwidth Uplink Bandwidth Downlink Port Aggregation Range VLTi Capacity Possible Aggregation Topologies 10 Gb 10 Gb 1–86 2 * 40G S5000 10 Gb 40 Gb 1–80 2 * 40G S5000 Table 6.
access switches is based on the number of uplinks and downlinks in the fabric. With this topology, the downlinks connect to access S55 or S60 switches using a 1 Gb bandwidth. Figure 8. 1 Gb ToR VLT Deployment NOTE: All the VLT aggregation switches must be same mode type for aggregation (for example, S4810). On the VLT access, configure the same model type.
Table 8.
Table 9.
Figure 9. 10 Gb or 40 Gb ToR VLT Deployment (mVLT) NOTE: All the VLT aggregation switches must be same model for aggregation (for example, all Z9000 switches). On the VLT access, configure the same switch types or a combination of S4810 and S4820T switches.
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 Mixed node 105– Basic 3224 2 * 40 Gb NA 20 Gb NA S4810 S4810 or S4820T 10 Gb 40 Gb Mixed node 105– Basic 1624 2 * 40 Gb NA 80G NA Z9000 or S6000 S4810 or S4820T 10 Gb 40 Gb Resiliency 105– 2808 2 * 40 Gb 2 * 40 Gb 20 Gb NA S4810 S4810 10 Gb 40 Gb Resiliency 105– 1344 2 * 40 Gb 2 * 40 Gb 80G NA Z9000 or S6000 S4810 10 Gb 40 Gb Mixed node 105– Resil
DL BW 40 Gb UL BW Type 40 Gb Resiliency DL Port Range AVC 59–784 2 *40 Gb Access VLTi Capacity FL BW AA Possible Topologies Aggregation Access 2 * 40 Gb 80 Gb S6000 S6000 Three-Tier Topologies for a 10 Gb or 40 Gb ToR (mVLT) Deployment Layer 2 or Layer 3 with Resiliency (Routed VLT) Use the following tables as a guideline for selecting the appropriate three-tier Layer 2 VLT or Layer 3 with Resiliency (Routed VLT) fabric design for a 40 Gb Tor (mVLT) Deployment.
DL BW UL BW Type DL Port Range CVC 10 Gb 10 Gb Basic 3411– 41664 2 * 40 Gb 10 Gb 10 Gb Basic 1625– 21952 10 Gb 10 Gb Basic 10 Gb 10 Gb AVC AVC FL BW CA FL BW AA 2 * 40 Gb NA 80 Gb 2 *40 Gb 2 *40 Gb NA 1625– 21952 2 * 40 Gb 2 * 40 Gb Resilienc y 2917– 36288 2 * 40 Gb 10 Gb 10 Gb Resilienc y 2917– 36288 10 Gb 10 Gb Resilienc y 10 Gb 10 Gb Possible Topologies Aggregati on Access 20 Gb Z9000 or S6000 S4810 S4820 80 Gb 80 Gb Z9000 or S6000 Z9000 or S6000 S4810 NA 80
DL BW UL BW Type DL Port Range CVC 10 Gb 40 Gb Basic 1225– 21952 2 * 40 Gb 10 Gb 40 Gb Basic 1225– 21952 10 Gb 40 Gb AVC AVC FL BW CA FL BW AA 2 * 40 Gb NA 80 Gb 2 * 40 Gb 2 * 40 Gb NA Resilienc y 2809– 2 * 40 36288 Gb 2 * 40 Gb 10 Gb 40 Gb Resilienc y 2809– 2 * 40 36288 Gb 10 Gb 40 Gb Resilienc y 1345– 18816 10 Gb 40 Gb Resilienc y 1345– 18816 Possible Topologies Core Aggregati on Access 80 Gb Z9000 or S6000 Z9000 or S6000 S4810 80 Gb 80 Gb Z9000 or S6000 Z9000 or
Table 13.
10 Gb blade switch (MXL) VLT Deployment Figure 10. 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 VLTi A BWBA BW &A VLTi Access BW MXL Interchassis BW Possible Topologies Aggregation 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– 27 10 Gb
MXL Blade Pairs Range UL BW Type Fabric Type FL VLTi A BWBA BW &A VLTi Access BW MXL Interchassis BW Possible Topologies Aggregation Access (Routed VLT) 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 Res
BW = Bandwidth DL = Downlink FL BWB A & A = Fabric Link Bandwidth between Aggregation and Access FL BWB C & A = Fabric Link Bandwidth between Core and Access UL BW = Uplink Bandwidth VCBW = VLTi Core Bandwidth Table 15.
MXL UL Blade BW Pairs Range Type Fabric Type FL BW BC &A 15– 196 40 Gb 28– 336 VLTi Aggregatio n BW Possible Topologies Basic Layer 2/ Layer 3 with Resiliency (Routed VLT) 80G 80G 2 * 40 Gb 2 * 40 Gb S600 S6000 0 MXL 10 Gb Stacking Layer 2 or Layer 3 with Resiliency (Routed VLT) 80G 40 Gb 2 * 40 Gb 2 * 40 Gb Z900 0 or S600 0 S4810 or S4820 T MXL 28– 336 40 Gb Stacking Layer 2/ Layer 3 with Resiliency (Routed VLT) 80G 40 Gb 2 * 40 Gb 2 * 40 Gb Z900 0 or S600 0 S4810 or S4820
MXL UL Blade BW Pairs Range Type Fabric Type FL BW BC &A 28– 336 10 Gb 27– 336 VLTi Aggregatio n BW Possible Topologies Core Aggreg Access ation MXL intraChassis resiliency Layer 2 or Layer 3 with Resiliency (Routed VLT) 80G 20 Gb 2 * 40 Gb 2 * 40 Gb Z900 0 or S600 0 S4810 or S4820 T MXL 40 Gb MXL intraChassis resiliency Layer 2 or Layer 3 with Resiliency (Routed VLT) 80G 20 Gb 2 * 40 Gb 2 * 40 Gb Z900 0 or S600 0 S4810 or S4820 T MXL 15– 196 10 Gb MXL intraChassis resiliency L
5 Designing the Fabric To design a Layer 3 two-tier distributed core fabric or Layer 2 VLT fabric based on your current or future needs, use the Fabric Design Wizard on 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, refer to IOA Fabric Design Wizard.
Network Deployment Summary Use AFM to design a fabric, make changes to the pre-deployment configuration, deploy the fabric, and validate the fabric designed by comparing it to a discovered fabric. AFM provides up-to-date status during each phase of the fabric from design to validate. AFM displays any pending steps required to ensure the fabric is fully functional for each fabric design.
Phase State State Description successfully deployed versus the number of total switches in the design. NOTE: Deployment on any of the switches is not In-progress while in this state. Validation Complete Deployment is successful for the switch. Required Validation state for all switches is required. In-progress Validation is in progress for one or more switches; displays a progress bar and provides information about count of switches successfully validated vs.
Phase State State Description Deployment Required Deployment has not been initiated for the switch or the Deployment state was reset due to a Design/Pre-deployment Configuration change. NOTE: Deployment can be initiated/re-initiated only if Predeployment Configuration is Complete. Validation In-progress Deployment is in progress; provides the percentage of completion. Error Deployment errors exist. Complete Deployment is successful for the switch.
Design State Pre-Deploy Configuration State Deployment State Validation State Operation Allowed Complete Not Started Not Started • • Incomplete. The system MAC and IP address are not configured for the switches. • • • Complete Partial Complete / Complete–Partial complete indicates that at least 1 switch has its system MAC and IP address configured.
Design State Pre-Deploy Configuration State Deployment State Validation State Incomplete indicates that AFM is deploying the switches. Error / Complete Complete indicates all the switches in the distributed fabric are deployed.
• The uplinks between the aggregation switches and external switch (WAN) support the Layer 3 protocol (OSPF, iBGP or eBGP). • The downlinks from the access switches support the Layer 2 protocol (VLAN or VLAN/VRRP). The default setting on the pre-deployment screen is VLAN configuration, which allows you to configure downlink connections to servers. Select the VLAN and VRRP Configuration option to support redundancy between the access switch and ToR switches.
Figure 11. Layer 3 with Resiliency (Routed VLT) with VLT option + Advanced VLAN IP Configuration 3. Layer 3 with Resiliency (Routed VLT) – Basic option – If you select the Basic option, configure the VLAN with the primary and secondary IP addresses for each access switch. 4. Layer 3 with Resiliency (Routed VLT) with MXL Blade with interChassis option – For this topology, select the Deployment Type with an MXL Blade switch with Resiliency (VLT) and Interchassis (across chassis) resiliency.
type (topology). Based on the selected deployment type options, different downlinks options are configured at the access tier. The following section lists the available topology types: 1. Layer 3 with Resiliency (Routed VLT) with stacking option – If you select the Stacking option, configure the VLAN with the primary and secondary IP addresses for each access switch. 2.
To design a fabric, use the following screens: 1. Fabric Name and Type — Select the fabric name, type, and description. Enable OpenStack Neutron Management (Standard fabric only), LAN, LAN/SAN, and blade switch deployments, if required. a. b. 2. 3. To design a Standard Fabric: 1. Bandwidth and Port Count — Configure the number of edge port uplinks to the WAN connection and downlinks required (for example, to servers or ToRs) for deployment as well as for future expansion. 2.
Figure 13. Fabric Design Wizard — Fabric Name and Type 1. Navigate to the Fabric Design Wizard on the Network > Design Fabric screen. 2. Click New Fabric . The Introduction screen displays. 3. Review the introduction and click Next. The Fabric Name screen displays. 4. Enter the name of the fabric in the Fabric Name field. The fabric name must be unique. The range is 1–17 characters. AFM supports the following character types: 5.
channel switch and server. Configure up to eight VLANs with a VLAN ID range of 2–4094 on the fiber channel and associate these VLANs with any FC port. * • iSCSI – Supports iSCSI interfaces. Advanced — Create a mixed node or custom topology. For more information, refer to Advanced Fabric Design. – In this release, AFM supports only two-tier VLT topologies. • 7. OpenStack Neutron Managed: (Standard fabric only) If you are using AFM Plug-in for OpenStack, select this option.
1. In the Bandwidth Specification section: a. Select the uplink bandwidth (10 Gb or 40 Gb) from the Uplink Bandwidth drop-down menu. b. Select the downlink bandwidth (1 Gb, 10 Gb, or 40 Gb) from the Downlink Bandwidth dropdown menu. • If you select the 1 Gb Downlink Bandwidth option, AFM supports deployment topologies using S55 and S60 switches on the access side. • If you select the 10 Gb Downlink Bandwidth option, AFM supports deployment topologies using S4810 and S4820T switches on the access side.
5. In the Downlink Ports Future column, enter an even number of downlink ports (connections to the servers, switches, or ToR) required for future expansion of the fabric. NOTE: If you select the Blade switch (MXL) deployment option in the Fabric Name and Type screen, the Bandwidth and Port Count screen displays a Blade Switch Pairs option instead of a Downlink Ports option in the Number of edge ports required by the fabric area. 6.
Table 19. Deployment Topology (Filter) Options Deployment Options Description Oversubscription Ratio (Layer 3 distributed core deployment topology only) For a Layer 3 deployment, the following oversubscription ratios are available: 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 topologies where S4810 and S4820T can be swapped.
Figure 16. Two-Tier VLT Topology: Aggregation and Access Layer Figure 17. Two-Tier Distributed Core Topology: Spine and Leaf • Three-Tier Topology — Layer 3 with Resiliency (Routed VLT). Has three layers of switches, fabric interlinks, uplinks and downlinks. For more information about three-tier topologies, refer to Designing a Layer 2 VLT and Layer 3 with Resiliency (Routed VLT) Fabric. Figure 18.
If you select LAN/SAN deployment with iSCSI or Fibre Channel storage facing ports using the Fabric Designer wizard, AFM automatically selects a Layer 2 fabric and the Layer 2, Layer 3, and Layer 3 options in the Deployment Topology screen are not displayed. 3. Select the appropriate deployment topology that uses the core switches and aggregation switch types in the fabric. 4. (Optional) Click Advanced Options to configure VLTi links and fabric links. a.
Figure 19. Enabled Link Bandwidth Customization Option 3. Check the Enable Link Bandwidth Customization checkbox. 4. Select the number of links and the fabric bandwidth value from the appropriate drop-down menu. Only the applicable options for a select topology are configurable. For example, for a two-tier topology, select the 120 Gb bandwidth option to customize the bandwidth from 20 to 120 Gb in increments of 20 Gb on the Fabric Customization screen. 5.
Figure 20. Customizing Fabric Link Bandwidth between Switches 9. Click Next to go to the Output screen. Standard Fabric Design — Fabric Customization To modify the fabric link bandwidth between the aggregation and access switches for two-tier and threetier fabrics, use the Fabric Customization screen, which displays the switch names, models, and switch roles (spine, leaf, aggregation or access).
about the Advanced Options, refer to Configuring Advanced Options. For information about tiers, refer to Deployment Topology and Deployment Topology Use Cases. 1. Navigate to the Network > Design Fabric > New Fabric > Deployment Topology > Fabric Customization screen. 2. From the Fabric Link Bandwidth drop-down menu, select the fabric link maximum bandwidth for each access switch. 3. Click Next to go the Output screen.
Advanced Fabric Design – Advanced Aggregation Config The Advanced Aggregation Config screen displays the default values for the fabric uplinks and VLTi links. Uplinks connect the fabric from the next upstream tier of devices to the core of the network. The minimum number of uplinks is two: one uplink is the active link and one uplink is for redundancy. Figure 21. Advanced Aggregation Config 1. (Optional) To customize the switch names, enter a name in each of the Aggregation Names fields.
Advanced Fabric Design — Advanced Access Config To add switches to the fabric, edit switch information, or remove switches, use the Advanced Access Config screen. The selected aggregation model (Z9000, S4810, S4820T, or S6000) and the available, used, and total bandwidth values display at the top of the screen. Adding Access Switches 1. In the upper left of the Advanced Access Config screen, click Add. The Add Switch Unit window displays.
Figure 22. Add Switch Unit Window NOTE: The information and options in the Add Switch Unit window vary based on the selected aggregation switch model. 2. Select a switch type from the Switch Model drop-down menu. • S4810 • S4820T • MXL • Z9000 • S6000 • S55 • S60 NOTE: The switch type options vary depending on the aggregation model. • 3. 72 S55 and S60 are only available if S4810 is the aggregation model. • Z9000 and S6000 are only available if Z9000 or S6000 is the aggregation model.
• VLT NOTE: Z9000 and S6000 do not support stack mode. 4. (VLT mode only) Enter a value in the Number of VLT pairs field. NOTE: Both switches in the VLT pair must be the same model type. 5. (MXL, S55, or S60) Select an optional module type from the first and second Optional Module dropdown menus: NOTE: The first optional module menu name and options vary based on the access switch type and mode (standalone or stack). Refer to the following table for supported options. Table 20.
The name must be unique. The range is 1–16 characters. AFM supports the following character types: • alphanumeric • underscore ( _ ) • + 10. To allocate ports, enter a value in the appropriate field in the Config Speed section. • Fabric Link • VLTi Link • Stack Ports NOTE: Configure at least two fabric links. The Remaining Ports field displays the number of available ports. The Total column displays the amount of bandwidth in Gb allocated to each link type.
Figure 23. Advanced Port Config 1. Select a switch from the drop-down Switch menu. 2. For each device, select a port from the drop-down From Port menu. NOTE: • To reset all switches to original port configurations, click Reset All Switches. • For switches that are not pre-deployed, the drop-down menus display both used and available ports. For pre-deployed switches, only available ports display. • If you change aggregation or access information, AFM resets port configurations. • 3.
• 6. PDF — Table, Data, Graphical Wiring Plan, or Both. • Visio — Network Topology. Click Generate. The output displays in the selected format. Figure 24. Example: Visio Output Output Types Network Topology • Graphical Network Topology — View information about how the switches are connected physically using a topology map. By default, no links are displayed in the fabric. To display the links in the fabric, click a switch. – If you select a switch, all the fabric interlinks display.
– If you select the access switches, the links to aggregation switches display. – If you select the core switches, the links to all the switches in the fabric (aggregation and access) display. Figure 25. Graphical Network Topology • Tabular Network Topology — View information about the network topology in a tabular format, including switch names, model types, role (aggregation or access), and usage status (designed or deployed). Figure 26.
Figure 27. Graphical Wiring Plan • 78 Tabular Wiring Plan — Displays information about how the switches are connected in the fabric in a tabular format, as shown below. The tabular wiring plan contains a list of switches, their names, link types, and the ports that connect to ports of other switches in the fabric.
Figure 28. Tabular Wiring Plan 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. Link Type Displays the type of link (VLTi, Fabric, or Stack link) Usage Status – Designed – Deployed Fabric Design – Summary The Summary screen displays a summary of your fabric design.
To prepare the fabric for deployment: 1. 2. Check with your system administrator for the TFTP or FTP IP address. To stage the switch software images, use this address. When you prepare the software images: • Make sure that the software version is the same for each switch type in the fabric. • Download the software image for each type of Dell Networking switch. • Stage the software images on the TFTP or FTP site.
Deleting the Fabric 1. Navigate to the Network screen. 2. Select the Design Fabric tab. 3. Select the fabric to delete. 4. Click Delete Fabric . Viewing the Wiring Plan 1. Navigate to the Network > Design Fabric screen. 2. Select the fabric and then click View Wiring Plan. 3. To display future switches and links, click Display future switches/links. 4. Click one of the following options: • Tabular Wiring Plan • Graphical Wiring Plan • Network Topology Plan 5.
6 IOA Fabric Designer Wizard To design a Layer 2 fabric that has an I/O Aggregator (IOA) blade switch in a M1000e chassis, use the IOA fabric design wizard. AFM supports IOA in standalone mode only. 1. To verify that the IOA blade switch is in standalone mode (default mode), use the following CLI command: show system stack-unit iom-mode For more information about this command, refer to the Dell PowerEdge Command Line Reference Guide for the M I/O Aggregator. 2.
5. On the Fabric Name and Type screen, select the Blade Switch Deployment checkbox, then select the IOA radio button. 6. Click Next. The IOA Fabric Design wizard displays. 7. Click Next. The Chassis Details screen displays. Figure 30. IOA Fabric Design Wizard — Chassis Details Screen 8. Enter the Chassis Management Controller (CMC) IP addresses to include in the fabric. • Add — Enter the chassis IP address in the first field and the prefix in the field after the slash and click OK.
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 • password — calvin If you have changed the CLI credentials, update these fields with the new information. a. Enter the user name in the User Name field. b. Enter the password in the Password and Confirm Password fields. NOTE: To unmask the CLI credentials, check the Show Password as Text checkbox. 11.
Figure 31. IOA Design Summary Screen 12. Review the fabric design information on the Summary screen. To confirm the information, click Finish . The Discovery Confirmation screen displays. 13. Click Yes to start the fabric discovery process. The Discovery Status screen displays detailed information about the installed IOA blade switches in the M1000e chassis. For information about the Discover Status screen, refer to Discovery Status Screen.
Figure 32. IOA Discover Status Screen 14. After the IOA fabric is successfully discovered, complete the pre-deployment configuration. For information about IOA pre-deployment configuration, refer to IOA Pre-deployment Wizard.
Configuring and Deploying the Fabric 7 After creating a fabric on the Network > Design Fabric > New Fabric screen, configure and deploy the fabric on the Network > Fabric Name > Configure and Deploy screen. This screen deploys the configuration to the switches in the fabric, as well as auto-generated and custom configurations. This screen contains the following options: • Deploy Fabric — Prepares the fabric for deployment and deploys the fabric.
• To automatically discover MAC addresses and the locations of the devices in the fabric, click Device MAC Association, select a fabric, and click OK. For more information, refer to Device MAC Association. • To use the wizard to complete the pre-deployment process, click Pre-deployment Configuration, select a fabric, and click OK. For more information, refer to the following subsections.
• Pre-deployment L3 DC – Downlink Configuration 2. Pre-deployment – Assign Switch Identities 3. Pre-deployment – Management IP 4. Pre-deployment – SNMP and CLI Credentials 5. Pre-deployment – Software Images 6. Pre-deployment – DHCP Integration 7. Pre-deployment – Summary Layer 3 with Resiliency (Routed VLT) Pre-deployment To prepare the Layer 3 with Resiliency (Routed VLT) fabric for deployment, complete the following tasks using the Pre-deployment Configuration wizard. 1.
NOTE: • Use Device MAC Association on only one fabric at a time. If you select a fabric for Device MAC Association and then try to select a different fabric while Device MAC Association is in progress , the following message displays: MAC discovery already enabled for the fabric "FabricName". Do you want to disable it and enable MAC discovery for the current fabric? To disable Device MAC Association for the first fabric and enable it on the current fabric, click Yes.
Figure 33. Device MAC Association — IP Configuration 4. Enter the default gateway in the Default Gateway field. 5. Enter the management route in the Management Route field. Enter the netmask in the / field. 6. Enter the switch’s IP address in the Enter Switch IP Address field and click the + button. Repeat for any additional switches. NOTE: You can add an individual IP address or IP address with a subnet or a range (for example: 10.16.133.1-150).
Figure 34. Preview IP Address Window 7. Add at least one IP address to the List of added IPs: field. 8. Enter the netmask in the Net Mask for IP Address field (for example: 24). The netmask range is 8–30. 9. To go to the SNMP Credentials screen, click Next. SNMP Credentials NOTE: AFM populates the CLI and SNMP credentials from the Administration settings.
Figure 35. Device MAC Association — SNMP Credentials 1. 2. In the Read Community String field, enter the read community string (for example, public). In the Write Community String field, enter the write community string (for example, private). The trap port and SNMP port numbers display as read-only fields. 3. From the Protocol drop-down menu, select one of the following protocols: • Telnet • SSHv2 NOTE: AFM automatically enters the default credentials for the username, password, and enable password.
Figure 36. Device MAC Association — DHCP Integration 1. Click Save to ... and specify the location for the generated DHCP configuration file or copy and paste the configuration into the DHCP server. 2. Verify the TFTP or FTP file transfer for the DHCP configuration file is successful and verify the CLI and SNMP information on the Summary screen, then click Finish. After completing the Device MAC Association wizard: 1. Enable BMP on all devices. 2.
Figure 37. Device MAC Association Status Screen If the wiring is correct, AFM automatically populates the Associated Name column. If the wiring is not correct, this column is blank. If wiring errors exist, AFM displays the cause in the Reason column. IOA Pre-deployment Wizard IOA Pre-Deployment Screens To provide the minimum configuration for a IOA fabric, use the following IOA Pre-deployment screens. These screens automate the IOA deployment process.
Figure 38. 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. • VLAN Configuration — Apply a VLAN to the Layer 2 VLT. Include at least one VLAN configuration. • Software Images — Specifies the TFTP or FTP address (local or remote server) and the path of the FTOS software image download to each type of switch.
For information about IOA pre-deployment error messages, refer to IOA Pre-deployment Error Messages. Pre-deployment (IOA) – Management IP Before you begin: 1. Review the IOA Pre-deployment Wizard information. 2. Insert the IOA blade switch into the M1000e chassis. 3.
Pre-deployment (IOA) – VLAN Configuration 1. Navigate to the Network > Fabric Name > Configure and Deploy screen. Figure 40. IOA Pre-deployment VLAN Configuration 2. From the Deploy Fabric pull-down menu, select Pre-deployment Configuration. The pre-deployment Introduction screen displays. 3. Navigate to the VLAN Configuration screen. 4. From the Chassis drop-down menu, select a chassis name that you want to configure. 5.
Figure 41. IOA Pre-deployment VLAN Configuration with Populated Data The following Pre-deployment IOA VLAN configuration options are available: Table 21. IOA VLAN Pre-deployment Options VLAN Option Description Add VLAN Create a VLAN. The range is 2–4094. NOTE: VLAN ID 1003 is reserved. Add VLAN Range Create a VLAN range.
VLAN Option Description Configure Isolated Network Enable the isolated network security feature on a VLAN or a range of VLANs. Only standalone mode is supported. For more information about this option, refer to Isolated Networks. Copy Chassis Configuration Copy the chassis configuration from the current chassis to another chassis in the fabric. NOTE: The VLAN configuration is copied symmetrically to the new chassis.
6. VLAN Option Description Copy VLAN Tagged Ports Copy the VLAN tagged port configuration from a selected port to other ports within a switch. Edit Edit the VLAN configuration. Delete Remove the VLAN configuration. Click Next to go to the SNMP and CLI Credentials screen. Isolated Networks The isolated networks security feature can be enabled on a VLAN or a range of VLANs. Only standalone mode is supported, as there is only a single LAG uplink.
Figure 42. Isolated Networks Enabled on VLAN 5 Pre-deployment (IOA) – SNMP and CLI Credentials Configure SNMP so that the AFM can perform SNMP queries on the switches in the fabric. Configure SNMP and CLI credentials at the fabric level. 1. Navigate to the Network > Fabric Name > Configure and Deploy screen. 2. From the Deploy Fabric drop-down menu, select Pre-deployment Configuration. 3. Navigate to the SNMP and CLI Credentials screen.
Figure 43. 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 drop-down menu, select one of the following protocols: • Telnet • SSHv2 NOTE: AFM automatically enters the default IOA credentials (username root, password calvin). 7. In the User Name field, enter the user name. 8.
1. Navigate to the Network > Fabric Name > Configure and Deploy screen. 2. From the Deploy Fabric drop-down menu, select the Pre-deployment Configuration option. 3. Navigate to the Software Images screen. Figure 44. IOA Pre-deployment Software Images Screen 4. Select the TFTP or FTP site option that contains the software image. 5. Enter the path of the software image on the TFTP or FTP site. 6. Click Next to go to the Summary screen.
5. Click Finish. Next Steps 1. Deploy the IOA switches from the Network > Fabric > Configuration and Deploy > Deploy and Validate > Deploy screen. Figure 46.
NOTE: Before deployment, make sure that the IOA switches are in standalone mode using the following CLI command: show system stack-unit iom-mode For more information about this command, refer to the Dell PowerEdge Command Line Reference Guide for the M I/O Aggregator. 2. During deployment, check for IOA deployment failures such as Not being in Standalone Mode in the Response Actions column. To correct this issue, set the IOA to standalone mode and then redeploy it.
Error Recommended Action 2. 3. Make sure the image is present on the TFTP or FTP site. Verify Telnet/SSH connectivity from AFM server and re-deploy. Ping verification: Failed From the AFM server, verify connectivity to the IOA device. Telnet/SSH session verification: Failed Make sure Telnet/SSH session available from the AFM server has the correct credentials.
• DHCP Integration — Create a dhcp.cfg file that loads the correct software image and the configuration file for each switch type. The DHCP server also uses this file to assign a management IP address to each switch. NOTE: Install the DHCP configuration file on the DHCP server before you deploy the fabric. • Downlink Configuration — For a Layer 3 Distributed Core or Layer 3 with Resiliency (Routed VLT) fabric. Configure an EdgePort that connects to the access layer, such as servers or a ToR.
L2 VLT Pre-deployment – Uplink Configuration The Uplink Configuration page displays the port bandwidth and the number of specified ports as readonly fields on the Fabric Name and Type and Port Specification screens. To configure the uplink protocol for the EdgePort uplinks to the WAN, use the Uplink Configuration screen. NOTE: If you enable OSPF, the uplinks or interlinks must be in area 0. Figure 48. Uplink Configuration Screen 1. Navigate to the Network > Fabric Name > Configure and Deploy screen. 2.
7. Click Next to go the VLAN Configuration screen. L2 VLT Pre-deployment - VLAN Configuration Specify at least one VLAN for the Layer 2 fabric manually or automatically using this screen. 1. Navigate to the Network > Fabric Name > Configure and Deploy screen. 2. From the Deploy Fabric drop-down menu, select the Pre-deployment Configuration option. 3. Navigate to the VLAN Configuration screen. Figure 49. VLAN Configuration without VLAN and VRRP Configuration 4.
Table 22. VLAN Configuration Options VLAN Option Description Add VLAN Enter the VLAN ID. Edit VLAN Change the VLAN ID or VLAN ID, primary IP address, secondary IP address. Add VLAN Range Automates VLAN creation and automatically populates IP addresses. Enter the following VLAN information: • • • • Starting VLAN ID — Specify the starting VLAN ID. The range is 2–4094. Number of VLANs — Specify the number of VLANs. VLAN Increment — Specify the increment of the VLAN.
Field Name Description Delete Delete the selected port channel configuration. Edit Enter the port channel configuration. Figure 50. Port Channel Configuration Screen 1. Navigate to the Network > Fabric Name > Configure and Deploy screen. 2. From the Deploy Fabric drop-down menu, select Pre-deployment Configuration. 3. Navigate to the Port Channel Configuration screen. 4. From the Switch drop-down menu, select the switch for the port channel configuration. 5.
Figure 51. Storage Facing Port Screen 4. Navigate to the VLAN ID column. 5. Click the VLAN ID icon to the right of the VLAN ID field, select a VLAN ID, and associate it with the storage-facing port. a. If you connect to fibre channel storage-facing ports, AFM automatically populates the SAN Fabric ID when you select the VLAN ID. b. If you connect to iSCSI storage-facing ports, select a VLAN ID and associate it with a vendor.
NOTE: Associate only one vendor for each VLAN. If you associate a VLAN to multiple storage-facing ports, AFM automatically sets the vendor as the same across for all associated entries. 6. Click Next to configure the VLAN Mapping configuration. L2 VLT/L3 Routed VLT Pre-deployment – VLAN Mapping To add VLANs and associate ports on the different switches for a Layer 2 fabric, use the Downlink Port Configuration screen.
Option Description Copy VLAN Tagged Port Config Copy the VLAN tagged port configuration from a selected port to other ports in a switch. 1. Navigate to the Network > Fabric Name > Configure and Deploy screen. 2. From the Deploy Fabric drop-down menu, select Pre-deployment Configuration. 3. Navigate to the VLAN Mapping screen. Figure 53. Pre-deployment Configuration — VLAN Mapping 4. From the Switches drop-down menu, select an access or aggregation switch.
• populates the starting IP address range and prefix • populate the loop IP address and prefix based on the fabric design • sets the area ID for OSPF to 0 Review these settings before deployment. You can modify the IP address range and loopback address. The range for the starting prefix for both types of addresses is 8–29 and the range for the loopback prefix is 8–26. NOTE: The area ID for the interconnect link must not be the same as the area ID for the uplink. 1.
Figure 54. Add Static Route Window Configure up to 10 static routes for each aggregation device. When you check the Default Route option, AFM automatically populates the destination network field as 0.0.0.0/0. For static routes, enter the destination network and the next hop. Figure 55. Uplink Configuration Screen • L2 — Configures Layer 2 uplinks for a Layer 2 fabric. This option is disabled by default on a Layer 3 Distributed Core fabric.
Figure 56. Layer 3 Static Routes 5. In the Protocol Settings area, select a routing protocol (OSPF, IBGP, or eBGP) for the EdgePort uplinks. Specify the number of uplinks on the Bandwidth and Port Count screen. AFM automatically populates the range of IP addresses in the /30 subnet. • If you enable OSPF, enter the local IP address, remote neighbor IP address, and area ID for each specified uplink. The area ID area range is 0–65535.
Figure 57. Downlink Configuration for Layer 3 Distributed Core Fabric 1. Navigate to the Network > Fabric Name > Configure and Deploy screen. 2. From the Deploy Fabric drop-down menu, select Pre-deployment Configuration. 3. Navigate to the Downlink Configuration screen. 4. To specify a leaf as a ToR, select Specify Leaf as ToR. 5. Manually configure the downlinks or automatically generate the downlink configuration by checking the Generate Downlink Configuration option. 6.
To configure links connecting the leaves and spines for a Layer 3 distributed core fabric or links connecting the core, access, and aggregation switches for a Layer 3 with Resiliency (Routed VLT) fabric using the OSPF routing protocol, use the Fabric link Configuration screen. The selected fabric type and fabric oversubscription ratio determines the value that AFM automatically assigns to the Port Bandwidth read-only field .
Figure 58. Add Static Route Window Configure up to 10 static routes for each aggregation device. When you check the Default Route option, AFM automatically populates the destination network field as 0.0.0.0/0. For static routes, enter the destination network and the next hop. Figure 59. Uplink Configuration Screen • L2 — Configures Layer 2 uplinks for a Layer 2 fabric. This option is disabled by default on a Layer 3 Distributed Core fabric.
Figure 60. Layer 3 Static Routes 5. In the Protocol Settings area, select a routing protocol (OSPF, IBGP, or eBGP) for the EdgePort uplinks. Specify the number of uplinks on the Bandwidth and Port Count screen. AFM automatically populates the range of IP addresses in the /30 subnet. • If you enable OSPF, enter the local IP address, remote neighbor IP address, and area ID for each specified uplink. The area ID area range is 0–65535.
Table 26. VLT VLAN Configuration Options for Layer 3 with Resiliency (Routed VLT) Fabric VLAN Option Description Add VLAN Create a VLAN row. Add VLAN Range Automate VLAN creation and automatically populate IP addresses. Enter the following VLAN information: • • • • Starting VLAN ID — Enter the starting VLAN ID. The range is 2–4094. Number of VLANs — Enter the number of VLANs. VLAN Increment — Enter the increment of the VLANs. If you do not specify an increment, the default value is 1.
Figure 61. Layer 3 with Resiliency (Routed VLT) Deployment Topology 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 the primary and secondary IP address for the VLAN ID. Figure 62.
(Routed VLT) topology, select the Enable Layer 3 protocol in Access Switches option. If you use this option, provide the network IP address range using the Add VLAN Range link. AFM assigns IP addresses to all the access and aggregation switches. 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 63.
Figure 64. Advanced VLAN IP Configuration Option L3 Routed VLT Pre-deployment – Port Channel Configuration To add, edit, delete, and automatically populate the port channel configuration for Layer 3 with Resiliency (Routed VLT) fabric, use the Port Channel Configuration screen. After you add a port channel configuration, you can copy it to use on another switch in the fabric. Table 27. Port Channel Configuration Options Field Name Description Add Enter the port channel information and enable LACP.
Figure 66. Pre-deployment — Port Channel Configuration 1. Navigate to the Network > Fabric Name > Configure and Deploy screen. 2. From the Deploy Fabric drop-down menu, select Pre-deployment Configuration. 3. Navigate to the Port Channel Configuration screen. 4. From the Switches drop-down menu, select a switch for the port channel configuration. The selected switch for the port channel configuration displays in the read-only Model field. 5.
Field Name Description NOTE: VLANs previously associated with storage-facing ports are included in the selection list. Table 29. Layer 2 VLAN Mapping Options Option Description Auto-fill Tagged Port For selected VLANs, apply sequential tagging to the available ports and the number of ports specified on a VLAN. Auto-fill Untagged Port For selected VLANs, apply untagged ports. Based on available ports, associate only one port per VLAN.
5. In the Tagged VLANs field, click the icon to the right and enter one or more VLANs to associate with the port. 6. Click Next to go to the Assign Network Identities screen. Pre-deployment – Change Port Status NOTE: The Change Port Status pre-deployment screen applies to advanced fabric only. To enable or disable a downlink, use the Change Port Status screen. If you use an Advanced configuration, AFM does not automatically assign any available ports as downlinks.
NOTE: You can only copy port status configurations to switches that are the same model and access switch type. 6. Click Next to go to the Assign Switch Identities screen. Pre-deployment – Assign Switch Identities To assign the system MAC addresses to the switches in the fabric, use the Assign Switch Identities screen.
NOTE: Before you begin, gather the management IP addresses for all the switches in the Layer 2 or Layer 3 fabric for the management port. All management switch IP addresses must be on the same subnet. 1. Navigate to the Network > Fabric Name > Configure and Deploy screen. 2. From the Deploy Fabric pull-down menu, select Pre-deployment Configuration. 3. Navigate to the Management IP screen. 4. In the Default Gateway field, enter the address of the default gateway for the management interface. 5.
the software image(s) for the switches on the TFTP or FTP site so that the switches can install the appropriate FTOS software image and configuration file from this site. To change the address of the TFTP or FTP site, navigate to the Administration > Settings > TFTP/FTP screen. 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.
S4810, S4820T, S6000, Z9000, and MXL blade switches. The switch automatically configures itself by loading and installing an embedded Dell Networking OS image with the startup configuration file. For more information about BMP, refer to the Open Automation Guide. NOTE: When you enter the system MAC address into the Assign Switch Identities screen, AFM generates a port MAC address from the pre-deployment configuration, not a chassis MAC address. 1.
NOTE: If you are using Internet Explorer and the Windows 7 OS, change your indexing options by performing the following steps: 1. Navigate to the Control Panel >Indexing Options screen. 2. Click Advanced and then click the File Types tab. 3. In the Add new extension to list field, enter conf as the extension file type and then click Add. 4. Click OK. 1. Navigate to the Network > >Fabric Name> Configure and Deploy screen. 2. From the Deploy Fabric drop-down menu, select View DHCP Configuration .
Table 31. Deployment Status Number Status Status Details Recommended Action 1 Required Deployment Required None 2 Complete Deployment successfully completed None 3 Error Protocol transfer failed Verify TFTP/FTP connectivity and FTP credentials 5 Error Device cleanup task failed 1. 2. 6 Error Complete config upload failed 1. 2. Verify the switch connectivity from AFM using Telnet or SSH.
3. If you use a remote DHCP server, verify that the DHCP configuration file generated by AFM for the switches in the fabric is integrated into the DHCP server. This file enables the switch to connect to the DHCP server and download the correct configuration and boot files. 4. Restart the DHCP server that contains the generated DHCP file that you created on the DHCP Integration screen. For information about DHCP integration, refer to DHCP Integration.
• Add the Switch Specific Custom Configuration • Preview the Combined Configuration View the 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 drop-down menu, select Deploy and Validate. 3. On the Deploy tab, click Advanced Configuration. 4. Click View Auto-Generated Configuration link and wait for the configuration to display.
3. On the Deploy tab, select Advanced Configuration and then Add Switch Specific Custom Configuration. The Switch Specific Custom Configuration screen displays. Figure 70. Switch Specific Custom Configuration View the auto-generated configuration and switch-specific custom configuration applied to the deployed switches in the fabric on the Switch Specific Custom Configuration screen. 4. Enter the switch specific-custom configuration using CLI commands in the Switch Specific Custom Configuration area.
Validation To verify that the discovered fabric matches the planned fabric and correct any errors, use the Validate screen. AFM reports mismatches as errors and generates the corresponding alarms. After fixing any errors found during validation, verify that all issues were resolved according to the planned fabric by revalidating the fabric.
Number Status Status Details Response Action 3. 4. 7 Error Switch is not Discovered To verify switch connectivity from AFM: 1. 2. 3. 4. 8 Error Configuration mismatch errors exist 2. 3. 4. Error Custom Configuration errors exist 2. 3. 4. Error Wiring Errors Exist Navigate to the Network > Fabric Name > Configure and Deployment screen. Click Errors. To view error details, click the Custom Config Errors tab. Fix any errors. To verify the Errors in the Wiring Error tab: 1. 2. 3. 4.
Number Status Status Details Response Action 5. Fix any errors. 11 InProgress Node validation in progress... None 12 InProgress Configuration Validation in progress... None 13 InProgress Wiring Validation in progress... None Validating the Fabric 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 for validation. 3. Click Validate Selected. 4.
• All leaf switches in the fabric • All spines in the fabric 1. Navigate to the Network > Fabric > Configure and Deploy screen. 2. From the CLI Configuration pull-down, select Associate Template. The Templates screen displays. 3. Click Add Template. 4. In the Template Name field, specify a unique name for the template. 5. (Optional) In the Description field, enter a description for the template. 6.
3. Click Copy Template. The Copy Template screen displays. 4. Select the template to copy. 5. In the Template Name field, enter a unique name for the new template. \ 6. Click OK. Associating Templates Associate one or more existing configuration templates to the entire fabric, all spines, all leaves, all aggregation devices, all access devices, all core switches, or a set of switches.
2. From the CLI Configuration drop-down menu, select Associate Templates. 3. Select the template. 4. Click Delete. 5. Click OK. Adding a Switch-Specific Custom Configuration Before editing the existing configuration, back up the existing running configuration in the flash with a unique name that includes the date and time. 1. Navigate to the Network > Fabric Name > Configure and Deploy screen. 2. From the Deploy Fabric drop-down, select Deploy and Validate. 3.
Viewing Custom Configuration History To view a complete history of all custom configuration applied to each of the switches, use the Custom Configuration History screen. • Custom Configuration History — View a chronological list of custom configurations applied to the switch. To view details for a configuration, select a row in the table.
Discovering and Deploying an Existing Fabric 8 To discover an existing fabric or an IOA blade switch in a M1000e chassis, use the Discover Fabric option. After you deploy the discovered fabric, the fabric sends alarms and events to AFM. For information about IOA, refer to Designing an IOA Fabric. Figure 72. Discovering and Deploying an Existing Fabric 1. Initiate discovery of an existing fabric on the Network > Design > Discover Fabric screen. Refer to Step 1: Discover an Existing Fabric. 2.
Step 1: Discover an Existing Fabric For more information about discovering and deploying an existing fabric, refer to Discovering and Deploying an Existing Fabric. 1. Click Network and then the Design Fabric tab. The Network Deployment Summary screen displays. 2. Click Discover Fabric. The Introduction screen for the Discover Fabric wizard displays. 3. Read the introduction and click Next. The Fabric Name and Type screen displays. 4. Enter the fabric name in the Fabric Name field.
Figure 73. Preview IP Address Window 8. Add at least one IP address to the List of added IPs: field and click Next. The Credentials screen displays. 9. In the SNMP section, click Add. The SNMP Credential window displays.
Figure 74. Discover Fabric SNMP Credential Screen 10. 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 five. • Enter the read community string in the Read Community String(s) field. You can only enter one read community string. NOTE: The SNMP credential information requires the read community string.
12. Enter the CLI credential information. a. Select the appropriate credential type (Telnet or SSHv2). b. Enter the user name in the User Name field and enter the password in the Password and Confirm Password fields. c. If you configured an enable password, enter it in the Enable Password and Confirm Enable Password fields. d. Click OK to confirm the information or click Close to close the window.
• 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 the recommended action. For information about how to discover a fabric, see Discovering an Existing Fabric. View the tabular wiring plan for a discovered fabric on the Network > Design > View Wiring Plan screen. To view the discovery status of an existing fabric 1.
Viewing the Fabric 9 This section contains the following topics: • Inventory Management • Dashboard • View Network Summary • View Fabric Summary • Switch Summary Related Links: Fabric Performance Management. Inventory Management The Inventory Management screen displays all discovered switches in the fabric.
NOTE: To refresh the inventory, click the blue Refresh button above the last column heading and below the Help button. Network-Level 1. Navigate to the Network and click the Inventory tab. The list of all switches displays in tabular format. 2. To export the data, click Export. Fabric-Level 1. Navigate to the Network > Fabric Name screen and click the Inventory tab. Details for the switches in the selected fabric display in tabular format. 2. To export the data, click Export.
Figure 77. Dashboard with Color Codes The Dashboard provides the following key performance information: • System — View a tabular listing of system health and fabrics and the corresponding alert count in order of severity. The Switch Health column displays the number of switches that have no alerts and the number of switches in the fabric. • Average Port Bandwidth Utilization — View the average port bandwidth utilization for all fabrics.
Table 33. 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: If the color code is yellow or red, AFM displays an alarm on the Network > Fabric Name > Switch Name > Alerts and Events > Current screen.
Figure 78. Network Topology Tabular View Network Topology Graphical View Navigate to the Network > Summary screen and then click the Graphical tab. The network topology contains fabric icons.
Figure 79. Network Topology Graphical View • Status: — View the status of the fabric using the following colors: – Red: Critical alerts – Orange: Major alerts – Yellow: Minor alerts – Blue: Warning alerts – Green: Information alerts or no alerts – Gray: AFM does has not deployed or managed these fabrics • Selection — To view the fabric data in the Detail tab, click a fabric icon.
• Revert to Last Saved — Revert fabric locations to the last saved version. • Save Move — Save changes to fabric locations. • Popup menu — To display a menu of available actions and the fabric name, right-click a fabric. • Enter fabric name — To locate a fabric, enter the name and then click the search icon. • Background Map Actions — Load or delete a geographical background map for the network.
Figure 80. Fabric Summary Screen — Graphical View For information about how to configure the Active Link, navigate to the Administrative > Settings > Active Link Settings screen. • Show Tooltips — View information about a switch such as associated fabric, switch name, model name, IP address, alarm status, and managed state when you place the cursor over the switch. • Show All Links — View all the links between the spines and the leaves, aggregation and access, or aggregation, access, and core.
Troubleshooting 10 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. Ping, Traceroute, SSH, and Telnet To troubleshoot a switch in the fabric, use ping, traceroute, SSH, or Telnet.
4. To display the Telnet results, click Send Command. Validation Alarms To troubleshoot alarms triggered during deployment, use the following table: Table 35. Validation Alarms Alarm Recommended Action Validation failed because the switch cannot be discovered. Log on to the switch console to isolate the fault. Validation failed because the switch has a mismatch MAC address. NOTE: Make sure that the switch has been power cycled and check the physical connection. 1.
Alarm Recommended Action b. c. d. Validation failed because the switch has a model mismatch. 1. From the Deploy Fabric drop-down menu, select Deploy and Validate. Click the Validation tab and select the switch. Click Validate Selected. 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 drop-down menu, select the Pre-deployment Configuration option c. 2.
Deployment and Validation Errors Pre-deployment Errors To troubleshoot pre-deployment errors, use the following table. For information about IOA predeployment errors, refer to IOA Pre-deployment Errors. Error Details Recommended Action Failed to transfer minimum configuration file via TFTP/FTP. Verify the TFTP or FTP connectivity from AFM. For FTP, verify the credentials and restart the DHCP Integration step using the Pre-deployment Configuration wizard. 1. 2. 3.
Error Details Recommended Action Complete configuration upload failed 1. 2. Verify TFTP/FTP or Telnet/SSH connectivity from AFM. 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 Deploy Selected. Smart script transfer failed 1. 2. Verify connectivity to the switch from AFM.
Figure 81. Validation Errors Screen Table 36. Configuration Errors Error Details Recommended Action Configuration Mismatch 1. 2. 3. 4. On the Deployment and Validation Status screen, select the switch. Click View Mismatch. Review the configuration mismatch and correct the configuration errors. Restart switch validation from the Deploy and Validate screen by selecting the switch from the list and clicking Start Validation.
Error Details Missing Link Recommended Action 3. Validate the switch from the screen by selecting the switch from the list and clicking Start Validation. 1. 2. 3. Review the wiring plan. Wire the switch according to the wiring plan to fix the missing link. Validate the switch. a. Navigate to the Network > Fabric Name > Configure and Deploy screen. From the Deploy Fabric drop-down menu, select Deploy and Validate. Click the Validation tab and then select the switches. Click Deploy Selected. b. c. d.
Error Details Recommended Action a. b. c. d. Switch Name Mismatch 1. 2. Verify that the IP address to switch name mapping is correct in the pre-deployment configuration. If the pre-deployment configuration is updated, redeploy the switch. Validate the switch. a. b. c. d. Switch Model Mismatch 1. 2. c. d. 1. 2. Navigate to the Network > Fabric Name > Configure and Deploy screen. From the Deploy Fabric drop-down menu, select Deploy and Validate. Click the Validation tab and select the switches.
Switch Deployment Status Description Requires Action Recommended Actions 2. Name > Configure and Deploy screen. Select the switch from the list and click Deploy Selected. NOTE: Verify that the switch is in BMP mode. CONFIG GENERATION IN PROGRESS Configuration File Generation In-progress No CONFIG GENERATION FAILED Configuration File Generation Failed Yes Information only 1. 2. 3. Check the write permission for the AFM installation directory on the AFM server.
Switch Deployment Status Description Requires Action Recommended Actions then clicking Deploy Selected. NOTE: Verify that the switch is in BMP mode. MIN CONFIG UPLOAD INPROGRESS Minimum Configuration Upload In-Progress No MIN CONFIG UPLOAD ERROR Minimum Configuration Yes Upload Error Information only 1. 2. 3. 4. 5. Verify the connectivity to the TFTP/FTP server from the switch. Resolve any errors the Validation Status column. Verify that the system MAC address in the dhcpd.
Switch Deployment Status Description Requires Action Recommended Actions 2. 3. 4. 5. 6. 7. 8. Resolve any errors in the Validation Status column. Verify that the DHCP server is running. Verify that the CFG file is on the TFTP/FTP server and the switch can reach it using the ping command. Redeploy the switch. NOTE: Verify that the switch is not in BMP mode. Navigate to the Network > Fabric Name > Configure and Deploy screen. From the Deploy Fabric drop-down menu, select Deploy and Validate.
Switch Deployment Status Description Requires Action Recommended Actions UPLINK RECONFIGURED REDEPLOY REQUIRED Uplink re-configured, Re-deployment of Switch is required Yes Restart switch deployment. NOTE: Verify that the switch is not in BMP mode. 1. 2. 3. REDEPLOYMENT REQUIRED Re-deployment of the switch is required Yes Navigate to the Network > Fabric Name > Configure and Deploy screen. From the Deploy Fabric drop-down menu, select Deploy and Validate.
AFM Deployment Task Error Status Recommended Action Reload of switch Reboot of switch: Failed Verify Telnet/SSH connectivity and redeploy. Boot image error Boot image was not loaded from flash 1. 2. To change the boot image path to flash, enter CONFIG mode and use the following CLI command through console session: no boot system stackunit 0 primary tftp://10.16.148.24/FTOSSE-9.5.0.0P3.bin Enable BMP on the switch. • • For S55 or S60, use the reload-type jumpstart config-download enable command.
AFM Deployment Task Error Status Recommended Action Deployment Software image Upload the software image as a superuser using the AFM selected in pre-deploy Virtual Appliance: wizard is not available in 1. Log in to the AFM server as a superuser. AFM image location. 2. Select Upload Switch Software Image. 3. Enter the number for the switch model. 4. Enter your user name and password for the FTP connection. 5. Enter the URL location for the switch software image. 6. Press Enter.
Alerts and Events 11 This section contains the following topics: • Current — Active Alerts • Historical — Alerts and Events Current Active Alerts To view active network, fabric, and switch alerts, use the Current tab. To acknowledge an active alert, select the active alert and then click Acknowledge. 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 83. Fabric Alerts • To filter active switch alerts, navigate to the Network > Fabric Name > Switch Name > Alerts and Events screen. Figure 84. Switch Alerts 1. Click Current. 2. Click the filtering icon on the right of the screen. To filter results, use the filter options: from date and to date. The filtering options display. 3.
4. • Indeterminate 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) drop-down menu, select one of the following options: • All • Yes • No Click Apply. 8. Historical Alerts and Event History To view historical events at the network, fabric or switch level, use the Alerts and Events screen.
Performance Management 12 This section contains the following topics: • Network Performance Management • Fabric Performance Management • Switch Performance Management • Port Performance Management • Detailed Port Performance • TCA Threshold Setting • Data Collection • Reports Network Performance Management To monitor the following network historical data for all the fabrics, use the Network > Performance screen: • Bandwidth utilization • Top 25 port inbound usage • Top 25 port outboun
Figure 85. Network Performance Management Screen Fabric Performance Management To monitor the following information 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 Figure 86.
NOTE: To view performance, enable data collection on the Jobs > Data Collections screen. Figure 87. Switch Performance Management Screen Port Performance Management 1. Navigate to the Network > Fabric Name > Switch Name > Summary screen.
Figure 88. Port Performance Summary 2. Select a port and then click the Performance tab. 3. Select a date type: 4. • Real-Time Data • Historical To display port performance, select one of the following View Type options: 5. • Bar • Graphical • Tabular Review the performance information.
• Traffic in Kbps • Packets 1. Navigate to the Network > Fabric Name > Switch Name > Summary screen. 2. Click the Performance tab at the bottom of the screen. 3. In the upper right of the screen, select the format for the data: 4.
Figure 89. TCA Bandwidth • Average Traffic Threshold — Configure the threshold for a Layer 3 fabric. The range is 60– 90 percent. The monitoring value applies only to the fabric link between the spine and leaf switches. • Low Utilization — Configure the value for TCA. The range is 40–60 percent. If AFM exceeds this value, the graphical performance monitoring displays a solid red line labeled Traffic Utilization Alert Threshold.
Reports This section contains the following topics: • Creating New Reports • Editing Reports • Running Reports • Deleting Reports • Duplicating Reports NOTE: To run a report, schedule data collection. Refer to Data Collection. Creating New Reports 1. Navigate to the Network > Fabric Name > Reports screen. 2. Click New Report. The Add/Modify Reports screen displays. 3. In the Report Name field, enter a name for the report. 4.
17. Click Finish. Editing Reports 1. Navigate to the Network > Fabric Name > Reports screen. 2. Select the report. 3. Click Edit . The Add/Modify Report screen displays. 4. Edit the report. 5. To navigate to different parts of the report, click Next. 6. In the Summary area, review the changes. 7. Click Finish. Running Reports Before running a report, schedule the data collection. For information on scheduling data collection, refer to Data Collection. 1.
Maintenance 13 Using the AFM Virtual Appliance After you have deployed and configured AFM, use the AFM Virtual Appliance to perform the following tasks: • Configure the system • Change the AFM superuser password • Update the AFM server • Set AFM software to the next reboot • Restart AFM • Restart the AFM server • Shut down the AFM server • Transfer files • Edit files • Upload switch software images • Backup the AFM database • Restore the AFM database • Log out To access the AFM v
Figure 91. AFM Virtual Appliance Menu Configuring the System To configure the device settings, use the Configure System option. • Device configuration (Network Configuration) — Use this option to configure a static IP as the AFM Ethernet controller or add a new device, such as an interface. • DNS configuration — Use this option to configure the AFM DNS settings. 1. Select Configure System and press Enter.
Figure 92. Select Action Screen 3. Select Device configuration. To navigate between elements, use the Tab and down arrow keys. The Network Configuration screen displays. Figure 93. Network Configuration Settings 4. View or modify the following settings as needed: • Name — Displays the name of AFM Server. NOTE: Do not change the default device name (eth0).
• Device — Displays the NIC Card. NOTE: Do not change the default device name (eth0). • Use DHCP — Allow DHCP to assign an IP address to the VM. • Static IP — Specify the static IP Address of the AFM server. NOTE: To verify connectivity, ping the IP address assigned to the AFM. If the destination host is unreachable, assign the same IP address. • Netmask — Specify the subnet mask of the static IP address for the AFM Server. • Default gateway IP — Specify the gateway IP Address of the AFM server.
• DNS search path — Configure the DNS search path. 4. Select the OK option to save your changes. 5. Select Quit to exit this screen. Changing the AFM Superuser Password 1. Select Change AFM Superuser Password option. 2. Press Enter. The CHANGE AFM SUPERUSER PASSWORD screen displays. Figure 95. Change AFM Superuser Password 3. In the Enter current superuser password field, enter the superuser password (for example, Superuser1).
The UPDATE AFM Server screen displays the current software version and any available version updates. The following message displays: The download file will overwrite the available software. Do you want to download RPM file from the Remote Server? 2.
2. Enter y. Transferring Files NOTE: FTP or TFTP is configured during the initial AFM server configuration. 1. Select Transfer File. Figure 96. Transfer Files 2. Press Enter . 3. Enter the file type to transfer: • 1. Syslog • 2. AFM Database Backup • 3. AFM Performance Database Backup 4. Press Enter. 5. Click y to upload all the files to the FTP or TFTP server. 6. Press Enter . 7. Press Enter to return to the main menu.
changed to changed to 2. config.properties — The config.properties file contains the system level configuration for the database backup. 1. Select Edit File . 2. Enter the edit file option 1 to select the 1.logback.xml option. Figure 97. Edit AFM File System 3. Press Enter. 4. Search for com.dell.dfm and com.dell.wnm.
6. Press Enter to return to the main menu. To edit a config.properties AFM system file: 1. Select Edit File. 2. Enter the edit file option 2 and then select the 2. config.properties option. Figure 98. Edit AFM File System 3. Press Enter. 4. To change the time, search for 2am or 1am You can change 2am to 3am for backup postgres DB or change it from 1am to 4am for the Hbase. For example, # The folder to store backed up database files.
Uploading Switch Software Images To upload a new switch software image to the AFM local FTP/TFTP server from a remote URL, use the Upload Switch Software Image option. To upload switch software from the AFM: 1. Select the Upload Switch Software Image option and press the Enter button. The Upload Switch Software Image screen displays. Figure 99. AFM Virtual Appliance Upload Software Image Screen 2. 194 Enter a switch model option. The range is 1–9. • 1. MXL Blade • 2. S4810 • 3. S4820T • 4.
For FTP, enter your user name and password. This option transfers the Dell Networking OS image file into the /data/FTOS/ directory and copies the files to the TFTP/FTP location. 3. Enter the URL location to upload the switch software image using the formats listed in the Upload Switch Software Image screen. 4. To return to the main menu, press Enter. Backing up the AFM Database NOTE: 1. • The backup file does not include AFM historical performance data.
Figure 100. Restore Configuration and Database Screen 2. Select a restoration option: NOTE: The backup file extensions are type-specific. You cannot restore the AFM database files using the 2. AFM Performance Database or 3. AFM Configuration and Database options. You must use the 1. AFM Database option. Similarly, you cannot restore configuration files using the 1. AFM Database option. 3. 4. 5. • 1. AFM Database — Restore the AFM database files only. • 2.
Backing Up a Switch To schedule the number of days to keep switch backup files, view the fabric, switch name, software version that the switch is running, the startup configuration, running configuration, backup time, and description of the backup configuration, use the Back Up Switch screen. This screen has the following options: • Switch Backup — Schedule a backup for a switch’s running configuration and startup configuration files now or later.
Viewing and Editing the Switch Backup Configuration To edit the running or startup configuration on deployed devices, use the View/Edit option. The edited configuration is available after you restore the switch backup configuration. 1. Navigate to the Network > Fabric Name> Maintenance screen. 2. Click Backup Switch in the upper right of the screen then click View/Edit. The View and Edit Switch Backup Screen Configuration screen displays. Figure 101.
• Schedule Switch Software Update — Create a new scheduled software image upgrade and software image activation job. • Schedule Activate Standby Partition— Activate the software in the standby partition of the device as a scheduled job later or immediately. Replacing an IOA Blade Switch This section describes how to replace an IOA blade switch. For information about how to replace other switch types, refer to Replacing a Switch. 1. Remove the decommissioned IOA blade switch from the M1000e chassis. 2.
5. To save the text file that contains information for submitting a Return Material Authorization (RMA), click Save. Send this information to your Dell Networking software support representative for switch replacement. 6. Once a replacement switch is available, click Replace Switch. Step 2: Replacing a Switch NOTE: To replace an IOA blade switch, refer to Replacing an IOA Blade Switch.
Step 3: Deploy Replacement Switch 1. Navigate to the Network > Fabric Name > Switch Name screen. 2. Click the Switch Replacement tab. 3. Click Deploy Switch. NOTE: If you change the switch outside of AFM (for example, using Telnet), use the restore option to restore the switch configuration. For information about how to replace a switch, see Replacing a Switch. Updating AFM To view and manage AFM server updates, use the Administration > Update Server screen. 1.
Jobs 14 This section contains the following topics: • Displaying Job Results • Scheduling Jobs Displaying Job Results To view job status, 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 the job results. 3. In the Job Name field, enter the job name. 4. From the Status drop-down menu, select a filter option: • All • Success • Failure • In Progress 5.
• Run Now — Start a job immediately. Select a job and click Run. • Edit — Edit or modify an existing job schedule. NOTE: You can only change the scheduled time. You cannot change the job name, image location, or switch. • Delete — Delete a job. Select a job and then click Delete. • Enable — Enable the job or activate the schedule. • Disable — Disable the job or the schedule without deleting the job.
• Two-tier distributed core filtering options — All, Spine, and Leaves • Two-tier VLT options — All, Aggregation and Access • Three-tier filtering options — All, Core, Aggregation and Access 7. To move the switches to the Selected area, click the >> button and click Next. 8. In the Update Location area, if necessary, click Edit TFTP or FTP settings. 9.
Scheduling Switch Software Updates The Update Software screen displays a software summary for each switch in the fabric. To create a new scheduled job for backup, software image upgrade, and software image activation, use the Schedule Switch Software Update option. As part of ongoing data center operations, periodically update the software and configurations in the fabric. Update one or more switches.
1. Navigate to the Network > Fabric Name > Maintenance screen. 2. Click Update Software. 3. Click Schedule Activate Standby Partition. 4. In the Job Name field, enter a name for the job. 5. (Optional) In the Description field, enter a description for the job. 6. Click Next. 7.
Administration 15 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: NOTE: AFM allows you to configure the SNMP configuration and CLI credentials before designing and deploying the fabric. You cannot edit SNMP and CLI credentials settings during the run phase.
NOTE: By default, the web service is turned off in the OMNM server. To enable web service: 1. On the OMNM server, go to the server installation directory. 2. Navigate to the installed.properties file at C:\ProgramFiles\Dell\OpenManage\Network Manager\owareapps\installprops\lib. 3. Disable the Application Server and Synergy Network Management server. 4. Add the following three lines in the installed.properties file: com.dorado.core.ws.disable=false com.dorado.core.ws.legacy.soap.enabled=true oware.
• Navigate to the Network >Switch > Tabular view and click Launch Active Link. The Active Link displays the selected switch view and performance charts. To configure active link settings: 1. Navigate to the Administration > Settings screen. 2. Navigate to the Active Link Settings area and click Edit. 3. In the Active Link area, check the Integrate to Dell OpenManage Network Manager (OMNM) checkbox to display additional performance statistics. 4.
2. In the Client Settings area, click Edit. 3. From the GUI Polling Interval (in Seconds) drop-down menu, select one of the following options. The default value is 60 seconds. • 15 Seconds • 30 Seconds • 60 Seconds • 120 Seconds 4. From the Pop-out Client Session drop-down menu, select the maximum number of browser windows for each user’s session. The range is 3–7 and the default value is 3. 5. Click OK. Data Retention Settings To configure the amount of time to retain performance history: 1.
SMTP Email To configure SMTP email: 1. Navigate to the Administration > Settings screen. 2. In the Secure SMTP Email Settings area, click Edit. 3. In the Outgoing Mail Server field, enter the IP address or complete host name of the email server. 4. In the Server Port field, enter the port number of the email server. 5. In the User Name field, enter the user name. 6. In the To Email Address(es) field, enter the mail addresses separated by a semicolon (;). 7.
TFTP/FTP Settings 1. Navigate to the Administration > Settings screen. 2. From the File Transfer Protocol drop-down menu, select one of the following options: 3. • TFTP (default) • FTP In the TFTP/FTP Settings area, select one of the following options: • Local — Provision AFM as a TFTP/FTP server. NOTE: If you use the Local option, the TFTP or FTP server must be in the same subnet as AFM. – If you select the local TFTP server option, the TFTP server uses the AFM management IP address.
• User Accounts Summary View — Display a summary view of all user accounts when the current user’s role is Superuser. When the role is user or administrator, only the current user’s account information displays. • Add User — Add new user accounts. Configure up to 50 user accounts but AFM supports only one superuser account. • Edit User — Edit the following information for user accounts: – Role — Select the account role (user or administrator). – First Name — Enter the user’s first name.
7. 8. (Optional) In the Last Name field, enter the user’s last name. The range is 1–50 characters. There are no character restrictions. From theRole drop-down menu, select one of the following roles: • Admin • User For information about roles, refer to Managing User Accounts. 9. In the Sessions Allowed drop-down menu, specify the number of sessions allowed for the user. The range is 1–5 and the default is 5. 10. In the Session Timeout pull-down menu, specify one of the following values.
7. In the Confirm Password field, enter the user’s password. 8. From the Sessions Allowed drop-down menu, specify the number of sessions allowed for the user. 9. From the Session Timeout drop-down menu, specify one of the following values: • 15 minutes • 30 minutes • 45 minutes • 60 minutes 10. From the Unsuccessful Login Limit drop-down menu, select the number of allowed unsuccessful login attempts. The range is 3–10. 11.
Managing User Sessions To display active AFM users and terminate users’ sessions, use the User Sessions screen. Only the Superuser can terminate an AFM user’s session. For more information about user accounts, refer to Managing User Accounts. This screen displays the following information: • User Name — View a list of user names for users who are currently logged in. • Session Login Time — View the date and time of the user’s last login. • Client IP Address — View the IP address of the user.
Audit Log To log a chronological sequence of audit records with 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. The Audit Log only captures actions by AFM users. Figure 102. Audit Log 1. Navigate to the Administration > Audit Log screen. 2. To display the audit trail options, click the filter icon on the upper right of the screen. 3.
8. Click Apply. • 218 To export the results, click Export.
Technical Support 16 Dell Networking Technical Support provides a range of documents and tools to assist you with effectively using Dell Networking equipment and mitigating the impact of network outages. Accessing Dell License Portal When you receive the Order Fulfillment email, follow these instructions to download the software. 1. Go to http://www.dell.com/support/licensing. 2. Enter your order number and click Available Software List. 3. Select the latest released version. 4.
