Active Fabric Manager (AFM) User Guide 2.
Copyright © 2015 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. 2015 - 10 Rev.
Contents 1 Introduction........................................................................................................... 8 2 Getting Started...................................................................................................... 9 Designing and Deploying a Fabric........................................................................................................ 9 3 Supported Fabric Types.....................................................................................
Using the Fabric Design Wizard..........................................................................................................53 Fabric Design — Fabric Name and Type............................................................................................ 54 Standard Fabric..............................................................................................................................56 Advanced Fabric Design...........................................................................
Viewing Deployment and Validation Status................................................................................151 Custom CLI Configuration................................................................................................................ 151 Managing Templates....................................................................................................................151 Associating Templates........................................................................................
Switch Performance Management...................................................................................................190 Port Performance Management....................................................................................................... 191 Detailed Port Performance Management........................................................................................ 192 Data Collection.....................................................................................................
Displaying Job Results...................................................................................................................... 215 Scheduling Jobs................................................................................................................................ 215 Switch Backup............................................................................................................................. 216 Switch Software Image Updates...............................................
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.
Getting Started 2 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. After completing the installation, configure AFM using the Getting Started configuration wizard on the Home > Getting Started screen.
• 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.
Supported Fabric Types 3 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, Z9000, and Z9500 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 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. • 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.
Figure 4. Distributed Core Architecture: Two-Tier NOTE: There are no uplinks on the spines. All the leaves have downlinks. Configure the uplink in the first two leaves.
• • NOTE: Specify an even number of uplinks. The minimum number of uplinks is two. One uplink is for redundancy. Fabric Interlinks — Links that connect the spines to the leaves. The fabric interlink bandwidth is fixed: 10 GB or 40 GB. Fabric over-subscription ratio — Varies the maximum number of available interconnect links. This ratio determines the number of fabric interlinks (the number of communication links between the spine and leaf devices).
• The Remote Trivial File Transfer Protocol (TFTP) or File Transfer Protocol (FTP) address from your network administrator or network operator. To specify a TFTP/FTP site, go to Administration > Settings > TFTP/FTP screen. For information about which software packages to use, refer to the Release Notes. • The software image for each type of switch in the fabric. Each type of switch must use the same version of the software image within the fabric.
NOTE: The maximum number of downlinks is based on two uplinks. Table 1.
Figure 6. 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 7.
Figure 8. 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 9.
• 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. For information about VLT, refer to the Dell Networking Configuration Guide for the S4048–ON, S3048– ON, S4810, S6000, or the Z9000, or refer to Selecting a Layer 2 and Layer 3 with Resiliency (Routed VLT) Fabric Design.
• 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. – For a two-tier fabric, fabric interlinks connect the aggregation switches to the access switches. – For a three-tier fabric, fabric interlinks connect the core, aggregation, and access switches together.
CAUTION: If you are already using a deployed switch, reset the factory settings. The switch must be in BMP mode. For more information on BMP, refer to DHCP Integration and the Configuration Guide for the Dell Networking OS. The number and type of switches in a VLT fabric are based on the following: • The number of current uplinks (at least two) and downlinks for the access switches. • The number of planned edge ports (future uplinks and downlinks) for the access switches.
Selecting a Layer 2 and Layer 3 with Resiliency (Routed VLT) Fabric Design For workload migration in virtualized environments, use a Layer 2 VLT fabric design. To extend equal cost multipath capabilities, use the Layer 3 with Resiliency (Routed VLT) fabric .
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.
Two Tier and Three Tier Topologies for 1 Gb ToR VLT Deployment for Layer 2 and Layer 3 with Resiliency (Routed VLT) In a 1 Gb ToR VLT Deployment fabric design, the S4810 aggregation switches connect to access switches at 10 Gb. The maximum number of VLT aggregation is two switches and the maximum number of VLT 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 11.
NOTE: With a Layer 2 VLT fabric, the uplinks come from the first two switches on the aggregation side. For information about tiers, see Standard Fabric Design — Deployment Topology. Table 8.
UL BW = Uplink Bandwidth 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 12. 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 Standard Fabric Design — Deployment Topology. Table 10.
DL BW UL BW Type DL Port Range AVC Access VLTi Capacity FL BWB A&A Possible Topologies Core Aggregation Access 10 Gb 40 Gb Mixed node Stacking 105 2808 2 * 40 Gb NA 40 Gb NA S4810 S4810 or S4820T 10 Gb 40 Gb Mixed node Stacking 105 1392 2 * 40 Gb NA 160 Gb NA Z9000 or S6000 S4810 or S4820T 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
FL BW AA = Fabric Link Bandwidth between Aggregation & Access UL BW = Uplink Bandwidth Use the following tables as guideline to select the appropriate two tier Layer 2 VLT or Layer 3 with Resiliency (Routed VLT) fabric design for a 40 Gb ToR (mVLT deployment). NOTE: With a Layer 2 VLT fabric, the uplinks come from the switches on the aggregation side. For information about tiers, refer to Standard Fabric Design — Deployment Topology. Table 11.
FL BW AA = Fabric Link Bandwidth between Aggregation & Access UL BW = Uplink Bandwidth 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 10 Gb Resilienc y 1355 18816 2 * 40 Gb 2 * 40 Gb 2* 40 Gb 80 Gb 80 Gb Z9000 or S6000 Z9000 or S6000 S4820 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
DL BW UL BW Type 10 Gb 40 Gb Resilienc y DL Port Range CVC AVC 1345 18816 2 * 40 Gb 2 * 40 Gb AVC FL BW CA FL BW AA 2* 40 Gb 80 Gb Z9000 or S6000 80 Gb Possible Topologies Core Aggregati on Access Z9000 or S6000 S4820 AVC = Aggregation VLTi Capacity 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 =
Two and Three Tier MXL Blade Topologies for Layer 2 and Layer 3 with Resiliency (Routed VLT) You can create a fabric using MXL blades by selecting the MXL blade option and 10 Gb downlinks. For information about MXL fabric deployments, refer MXL Topologies for MXL Blade Deployment.. NOTE: All the VLT aggregation switches must be same model (for example, all S4810 switches). On the VLT access, all the switches must be MXL blades. Refer to the previous tables in this section for more information.
Table 14.
MXL Blade Pairs Range UL BW 2 - 26 Type Fabric Type FL BWBA &A VLTi A BW VLTi Acces s BW MXL Possible Topologies InterAccess chass Aggregation is BW 40 Gb Stackin Layer 2/ g Layer 3 with Resiliency (Routed VLT) 40 Gb 2* 40 Gb NA NA S4810 or S4820T MXL 2 -27 10 Gb MXL intraChassi s resilien cy 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 intraChassi s resilien cy Layer 2/ Layer 3 with Resiliency (Routed VLT) 80 Gb
MXL Blade Pairs Range UL BW Type numbe rs only) Fabric Type FL BWBA &A VLTi A BW VLTi Acces s BW MXL Possible Topologies InterAccess chass Aggregation is BW s (Routed resilien VLT) cy 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 Blade Pairs Range UL BW Type VLTi Aggreg at-ion BW Possible Topologies Core Aggregation Access 15 196 40 Gb Basic Layer 2 or 80G Layer 3 with Resiliency (Routed VLT) 80G 2 * 40 Gb 2 * 40 Gb Z9000 Z9000 MXL 15 196 40 Gb Basic Layer 2/ 80G Layer 3 with Resiliency (Routed VLT) 80G 2 * 40 Gb 2 * 40 Gb S6000 S6000 MXL 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
MXL Blade Pairs Range UL BW Type Fabric Type FL FL VCBW BWB BWB C& A&A A VLTi Aggreg at-ion BW Possible Topologies Core Aggregation Access Resiliency (Routed VLT) 28 336 10 Gb MXL intraChassis resilienc y Layer 2 or 80G Layer 3 with Resiliency (Routed VLT) 20 Gb 2 * 40 Gb 2 * 40 Gb Z9000 or S6000 S4810 or S4820T MXL 27 336 40 Gb MXL intraChassis resilienc y Layer 2 or 80G Layer 3 with Resiliency (Routed VLT) 20 Gb 2 * 40 Gb 2 * 40 Gb Z9000 S4810 or S4820T MXL or S6000 15 196 10
Designing a Fabric 4 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. The design consists of a wiring plan, network topology information, summary of the inventory requirement, and a design specification. Refer also to 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, change 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 that the fabric is fully functional for each fabric design.
Phase State State Description 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. count of total switches per design (based on current port count — future port count is not included).
Phase Validation State State Description In-progress Deployment is in progress; provides the percentage of completion. Error Deployment errors exist. Complete Deployment is successful for the switch. Required Validation has not been initiated for the switch or the validation state was reset due to a Design/Pre-deployment Configuration/Deployment change. NOTE: Validation can be initiated only if Deployment is Complete. In-progress Deployment is in progress; provides the percentage of completion.
Design State Pre-Deploy Configuration State 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 switches in the distributed fabric are deployed. Operation Allowed • • • Deploy and Validate Fabric — Validation is only allowed when deployment is partial or fully complete View Deployment and Validation Status Delete Fabric Deployment Topology Use Cases To select a deployment topology, refer to the following use cases as a guide.
Use Case 4: Two-Tier Layer 3 Distributed Core If you select a two-tier Layer 3 distributed core fabric: • The fabric links between the spine and leaf switches support the Layer 3 OSPF routing protocol. • The uplinks between spine switch 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 and LAG).
Figure 13. 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.
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. Layer 3 with Resiliency (Routed VLT) with VLT option — If you select the VLT option, 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 the IP Range.
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. Deployment Topology — Select a Layer 2 or Layer 3 solution from a list of all applicable deployment topologies based on the fabric requirements entered on the Bandwidth and Port Count and Fabric Name and Type screens.
Figure 15. Fabric Design Wizard — Fabric Name and Type 1. From the menu, click Network and then the Design Fabric tab. 2. Click New Fabric. The Introduction screen of the Fabric Design wizard appears. 3. Review the introduction and click Next. The Fabric Name screen appears. 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.
the fibre 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 — Select to create one of the following topologies: – One-tier – Two-tier. – Three-tier. 7. For more information, refer to Advanced Fabric Design. Click Next and review the uplink and downlink bandwidth settings on the Bandwidth and Port Count screen.
Figure 16. Standard Fabric Design — Bandwidth and Port Count 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. • 2. If you select the 1 Gb Downlink Bandwidth option, AFM supports deployment topologies using S55 and S60 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 19. Two-Tier VLT Topology: Aggregation and Access Layer Figure 20. 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 21.
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. 5. Select the appropriate deployment topology that uses the core switches and aggregation switch types in the fabric. 6. (Optional) Click Advanced Options to configure VLTi links and fabric links. a.
Figure 22. Enabled Link Bandwidth Customization Option 3. Check the Enable Link Bandwidth Customization check box. 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 23. 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).
Figure 24. Standard Fabric Design — Fabric Customization 5. Click Next to go the Output screen.
Figure 25. Advanced Core Config Screen 1. 2. Select a switch model from the Switch Model drop-down menu: • Z9500 • S6000 • S4820T • S4810 • S4048–ON • N4064F • N4064 • N4032F • N4032 • N3048P • N3048 • N3024P • N3024F • N3024 For one-tier topologies, from the Type menu, this setting is automatically VLT or MLAG. Table 20.
Aggregation Switch Deployment Type VLT S6000 NE Z9500 NE MLAG ”NE” denotes non-endpoint switches that can extend with another tier. The Number of switches field displays the number switches in the inter chassis pair. 3. (N3000 and N4000 series switch models only) Select an optional module type from the Optional Module drop-down menu. Options vary based on the core switch type. Refer to the following table for supported options. Table 21.
NOTE: • The type of ports you can configure for this setting depend upon the number of topology tiers you select and the switch model type. • Configure at least one inter chassis link and one uplink for VLT or MLG type topologies. • You cannot edit the Remaining Ports field. • All values must be even. • The maximum configurable bandwidth is 160 GB for VLT or MLG type topologies. • The Inter Chassis link range is 2–16 for Dell OS switches and 2–8 for N series switches.
• N4064 • N4032F • N4032 • N3048P • N3048 • N3024P • N3024F • N3024 • N2048P (one-tier topology only) • N2048 (one-tier topology only) • N2024P (one-tier topology only) • N2024 (one-tier topology only) • MXL (one-tier topology only) The Number of switches field displays the number switches in the inter chassis pair. Table 22.
Aggregation Switch Deployment Type VLT S4810 NE S4820 NE S6000 NE Z9500 NE MLAG Stack Standalone ”NE” denotes non-endpoint switches that can extend with another tier. 2. (N3000 and N4000 series switch models only) Select an optional module type from the Optional Module drop-down menu. Options vary based on the switch type. Refer to the following table for supported options. Table 24.
NOTE: • AFM does not validate whether the specified number of licensed ports is correct for the switch. An incorrect setting causes the fabric deployment to fail. • This setting applies for both members in VLT mode. • 4. 5. You can edit this value without restriction before beginning pre-deployment steps for the switch. After pre-deployment begins, you can only edit the number of ports licensed upwards (for example, 36–84). The default switch names are FabricName—Agg-1 and FabricName—Agg-2.
• The 40G ⇨10G Split uplink bandwidth range is 2–32. This setting is not applicable to N3048, N3048P, N3024P, N3024F, or N3024 switch models. • The 40G uplink bandwidth range is 2–8. This setting is not applicable to N3048, N3048P, N3024P, N3024F, or N3024 switch models. • The 10G uplink bandwidth range is 2–32. This setting not applicable to Z9500 or S6000 switch models. • The Inter Chassis link range is 2–16. The Allocated column displays the total amount of configured uplink bandwidth (in GB). 6.
Figure 28. Add Switch Unit Dialog Box NOTE: The information and options in the Add Switch Unit dialog box vary based on the selected aggregation switch model. 2. Select Supports downlink if the switch connect servers or other switches which are not part of the fabric. When a switch is configured this way, that part of the fabric cannot extend any further. 3. Select a switch model from the Switch Model drop-down menu.
• N4032F • N4032 • N3048P • N3048 • N3024P • N3024F • N3024 • MXL (only available if you select Supports downlink) • Z9500 NOTE: The switch model options vary depending on the core switch model. 4. From the Type menu, select one of the following settings: • Stack • Standalone • VLT or MLAG (depending on the switch model selected). NOTE: Stack and Standalone settings are only available if you selected Supports downlink in step 1.
Switch Type and Mode Optional Module Supported Options 2 x 10 G — Fiber S60 (available only if you select 0/48 Supports downlink) 0/50 (Stack mode only) 2 x 10 G — Fiber 2 x 12 G — Fiber 1 x 24 G — Fiber MXL (available only if you select Supports downlink) 0/41 2 x 40 G — Fiber 0/49 4 x 10 G — Fiber 4 x 10 G — Copper N3000 series 1/1/1 2 x 10 G — Fiber 2 x 10 G — Copper N4000 series 1/1/1 4 x 10 G — Fiber 4 x 10 G — Copper 2 x 40 G — Fiber None 6.
Table 29.
Table 30. Support for 40 GB to 10 GB Split Core Switch Aggregation Switch Z9500 S6000 S4820 S4810 S4048–ON S3048–ON Z9500 S S S S6000 S S S S4820 S S4810 S S S S4048–ON S S S N4000 S ”S” denotes support for 40 GB to 10 GB split. Table 31.
Editing Aggregation Switch Information 1. Select a configured switch. 2. In the upper left of the Advanced Aggregation Config screen, click Edit. The Edit Switch Unit dialog box appears. NOTE: Depending on pre-deployment/deployment status, some options cannot be changed. Refer to Operations Allowed. 3. To save changes, click OK. Removing Aggregation Switches 1. Select a configured switch. 2. In the upper left of the Advanced Aggregation Config screen, click Delete. 3.
Figure 30. Add Switch Unit Dialog Box NOTE: The information and options in the Add Switch Unit dialog box vary based on the selected aggregation switch model. 3. 78 Select a switch model from the Switch Model drop-down menu.
• N3048P • N3048 • N3024P • N3024F • N3024 • N2048P • N2048 • N2024P • N2024 • MXL Table 32.
Deployment Type Access Switch VLT MLAG Stack Standalone E E E S55 E E S60 E E N4000 series S3048–ON E E E S4048–ON E E E S4810 E E E S4820 E E E S6000 E E E Z9500 E E ”E” denotes endpoint switches that cannot be extended to another tier. 4. Select a deployment mode from the Type drop-down menu: • Standalone • Stack • VLT or MLAG (N series only) NOTE: 5. • Z9500 does not support stack mode. • S55, S60 do not support VLT.
Table 34.
Table 35. Support for 40 GB to 10 GB Split Core Switch Aggregation Switch Z9500 S6000 S4820 S4810 S4048–ON S3048–ON Z9500 S S S S6000 S S S S4820 S S4810 S4048–ON S S S S S S S N4000 S ”S” denotes support for 40 GB to 10 GB split. Table 36.
The Edit Switch Unit dialog box appears. NOTE: Depending on pre-deployment/deployment status, some options cannot be changed. Refer to Operations Allowed. 3. To save changes, click OK. Removing Access Switches 1. In the Add Switch Unit dialog box, select a configured switch. 2. In the upper left of the Advanced Access Config screen, click Delete. 3. To confirm the switch deletion, click Yes.
Fabric Design — Viewing and Exporting Output To view the graphical wiring, tabular wiring, and network topology wiring plans for your fabric design, use the Output screen. Use the wiring plan as a guide for installing your equipment into the fabric. Based on the configuration, AFM calculates the number of switches required for the design and displays a physical wiring plan in PDF or Microsoft Visio® 2010 format that you can export and print.
Figure 32. 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 appear. – If you select a spine switch, the links to the leaf switches appear. – If you select an aggregation switch, the links to the access switches appear.
Figure 33. Graphical Network Topology • Tabular Network Topology — View information about the network topology in a tabular format, including switch names, model types, role (core, aggregation, or access), and usage status (designed or deployed). Figure 34. Tabular Network Topology Wiring • 86 Graphical Wiring Plan — View a diagram of each switch, including uplinks, downlinks, and port numbers, in the fabric.
Figure 35. Graphical Wiring Plan • Tabular Wiring Plan — Displays information about how the switches are connected in the fabric in a tabular format, as the following figure illustrates. 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 36. Tabular Wiring Plan Table 37. Tabular Wiring Plan Field Descriptions Field Name Description From Device (Switch) Displays the name of the device from the side. From Port Displays the port number and speed on the switch from the side. To Device (Switch) Displays the name of the device to the side. To Port Displays the port number and speed\on the device to the side.
3. Click Generate. 4. Review the design carefully before committing the changes. 5. Click Finish to commit your changes. Next Steps 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.
3. Select a fabric to edit and then click OK. The Fabric Design wizard appears. 4. Edit the fabric. Deleting the Fabric 1. From the menu, click to Network. 2. Click the Design Fabric tab. 3. Select the fabric to delete. 4. Click Delete Fabric. 5. In the confirmation dialog box, click Yes. Viewing the Wiring Plan 1. From the menu, click Network and then click the Design Fabric tab. 2. Select the fabric and then click View Wiring Plan. 3.
IOA Fabric Designer Wizard 5 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.
6. Click Next. The IOA Fabric Design wizard appears. 7. Click Next. The Chassis Details screen appears. Figure 38. 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. To close the window without adding the IP address, click Cancel.
Figure 39. IOA Fabric Design Wizard — CLI Credentials Screen 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.
Figure 40. IOA Design Summary Screen 12. Review the fabric design information on the Summary screen. To confirm the information, click Finish. The Discovery Confirmation screen appears. 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 View Discovery Status of an Existing Fabric.
Figure 41. IOA Discovery 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 6 This tab displays settings for the configuration of 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.
IOA Fabric Pre-Deployment To prepare the IOA fabric for deployment, complete the following tasks using the Pre-deployment Configuration wizard. 1. Pre-Deployment IOA — Management IP 2. Pre-Deployment IOA — VLAN Configuration 3. Pre-Deployment IOA — SNMP and CLI Credentials 4. Pre-Deployment (IOA) — Software Images 5.
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 appears: 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 42. 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 43. 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 44. Device MAC Association — SNMP Credentials 1. In the Read Community String field, enter the read community string (for example, public). 2. 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.
Figure 45. Device MAC Association — DHCP Integration 1. Click Save File 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 46. 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 To provide the IOA fabric the minimum configuration, use the following IOA Pre-deployment screens. These screens automate the IOA deployment process. See also Using the Pre-deployment Configuration Wizard.
1. Review the IOA Pre-deployment Wizard information. 2. Insert the IOA blade switch into the M1000e chassis. 3. 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, refer to the Dell PowerEdge Command Line Reference Guide for the M I/O Aggregator. 4. Obtain the Chassis Management Controller (CMC) M1000e chassis IP address.
Figure 48. IOA Pre-deployment VLAN Configuration 2. From the Deploy Fabric drop-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. From the Switch drop-down menu, select the name of the switch that you want to configure. Figure 49.
Table 38. 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. 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.
VLAN Option Description 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. 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 Copy the IOA VLAN configuration to any IOAs inserted in the same or different M1000e chassis.
• The uplink core (ToR) applies all the required security measures and other services before switching or routing traffic. • The VLAN is configured only on the server-side interface specified as the isolated network. All traffic arriving on this interface from the server is sent to the associated uplink. • Multiple servers belonging to the same VLAN cannot communicate with each other over IOA because all traffic is sent to the single uplink LAG and is not switched locally.
Figure 51. 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.
NOTE: To download the latest Dell Networking operating system software version for the switch, refer to Upload Switch Software in the AFM Installation Guide. 1. From the menu, click Network > Fabric Name and then click the Configure and Deploy tab. 2. From the Deploy Fabric drop-down menu, select the Pre-deployment Configuration option. 3. Navigate to the Software Images screen. Figure 52. IOA Pre-deployment Software Images Screen 4.
5. Click Finish. Next Steps 1. Deploy the IOA switches from the Network > Fabric > Configuration and Deploy > Deploy and Validate > Deploy screen. Figure 54.
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 IOA Software Upgrade task: Failed 1. 2. 3. Power cycle the IOA. Make sure that 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 screen 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 56. Uplink Configuration Screen Figure 57. Uplink Configuration Screen (N Series Switches) 1.
• 5. 6. L3 — Configure uplinks for a Layer 2 VLT or Layer 3 Distributed Core fabric. If you select the L3 option, the Uplink Configuration screen displays additional options to configure the Layer 3 protocol settings. Static Route — If you select this option, click Add in the Route Configuration area to display Add Static Route dialog box. Configure up to 10 static routes for each aggregation device.
Figure 58. VLAN Configuration without VLAN and VRRP Configuration 4. To configure the VLAN ID, primary IP address, secondary IP address, and virtual address, select VLAN and VRRP Configuration. 5. Click the Add VLAN link. The Add VLAN dialog box appears. NOTE: If you add a VLAN and do not enable the VLAN and VRRP Configuration option, you can only enter the VLAN ID name and description. 6. In the mandatory VLAN ID field, enter the VLAN ID. The range is 2–511. There is no default value. 7.
VLAN Option Description • • VLAN Description — Specify a description of the VLAN range. Start Subnet IP Address/Prefix — Specify the IP range to automatically populate VLAN IP addresses. Valid IP addresses include primary, secondary peer VLAN, and VRRP IP. NOTE: Select the VLAN and VRRP Configuration check box in the VLAN Configuration screen. to view this option. Delete VLAN Remove the selected VLAN row.
Table 41. Layer 2 Port Channel Configuration Options Command Description Add Enter port channel information and enable LACP. Edit Enter the port channel configuration. Delete Delete the selected port channel configuration. Auto Populate Enter the following port channel information to automatically assign port channels to switches in the fabric and enable LACP. • • • • • Copy Switch Port Channel Configuration 6.
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. Navigate to the Vendor drop-down menu and select one of the following options: • Compellent • EqualLogic • Other Figure 61. Selecting a Vendor NOTE: Associate only one vendor for each VLAN.
Figure 62. Pre-deployment Configuration — VLAN Mapping Table 42. VLAN Mapping Field Descriptions Field Name Description Configured VLANs View a list of VLANs specified in the VLT VLAN Configuration screen. Port Name View the port name (read-only). Tagged VLANs Enter one or more VLANs to associate with the port. The VLANs must be in the Configured VLANs list and the Untagged VLAN field must be empty. There is no default value. a. b.
Option Description NOTE: The number of Port/VLAN Ports option is disabled on the Autofill Tagged/Untagged Port screen. Copy Switch VLAN Config Copy the VLAN association from the current switch to other switches in the fabric. Copy VLAN Port Config Copy the VLAN association from a selected port to other ports in a switch. Port-VLAN Association Map the physical port to the VLAN ID. For example, map one port to multiple VLANs. VLAN-Port Association Map the VLAN ID to physical port interfaces.
NOTE: The area ID for the interconnect link must not be the same as the area ID for the uplink. 1. From the menu, click Network > Fabric Name and then the Configure and Deploy tab. 2. From the Deploy Fabric drop-down menu, select Pre-Deployment Configuration. The Introduction screen appears. 3. Review the Introduction screen and gather the useful information for deployment. 4. Click Next. The Fabric Link Configuration screen appears. 5.
Figure 63. Static Route Configuration Screen a. Click Add to configure a static route. The Add Static Route dialog box appears. Figure 64. Add Static Route Dialog Box b. For static routes, enter the destination network and the next hop. If you select Default Route, AFM automatically populates the destination network field as 0.0.0.0/0. c. Click OK. d. Repeat steps a-c to add an additional static route. You can configure up to 10 static routes for each aggregation switch.
NOTE: AFM automatically populates the range of IP addresses in the /30 subnet. 8. Click Next to go the Downlink Configuration screen. L3 DC Pre-Deployment — Downlink Configuration Downlinks are EdgePort links that connect to servers, switches, or ToRs. If you enable the ToR configuration, the leaf switch functions as a ToR. If you disable the ToR configuration, the leaf functions as a switch. The read-only port bandwidth for the downlinks is 1 GB, 10 GB, or 40 GB.
4. Pre-Deployment — Step 1c: VLAN Configuration 5. Pre-Deployment — Step 1d: Port Channel Configuration 6. Pre-Deployment — Step 1e: VLAN Mapping L3 DC/Routed VLT Pre-Deployment — Fabric Link Configuration Before you begin, review Using the Pre-deployment Configuration Wizard and Pre-deployment Wizard: Introduction.
• L2 — Configures Layer 2 uplinks for a Layer 2 fabric. This option is disabled by default on a Layer 3 Distributed Core fabric. • 5. 6. L3 — Configures uplinks for a Layer 2 VLT or Layer 3 Distributed Core fabric. If you select the L3 option, the Uplink Configuration screen displays additional options to configure the Layer 3 protocol settings. In the Protocol Settings area, select Static Routes or routing protocol (OSPF, IBGP, or eBGP) for the EdgePort uplinks.
• If you select 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. • If you select iBGP, enter the local IP address, remote neighbor IP address, local AS number for each specified uplink. The AS number range is 1–4294967295. • If you select eBGP, enter the local IP, remote neighbor IP address, local AS number, and remote AS number for each specified uplink. The AS number range is 1–4294967295.
VLAN Option Description Enter the following VLAN information: • • • • • • Starting VLAN ID — Enter the starting VLAN ID. The range is 2–511. 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. Start Subnet IP Address/Prefix: — Enter an IP range to automatically populate the VLAN IP addresses. The IP addresses include primary, secondary peer VLAN, and VRRP IP.
The following screen shot displays the VLAN Configuration screen without selecting the Enable Layer 3 protocol in Access Switches option. By default, the VLAN screen requires the primary and secondary IP address for the core devices. Figure 68. VLAN Configuration Without Using the Enable Layer 3 Protocol in Access Switches Option The following figure displays a VLT VLAN Configuration screen using the Enable Layer 3 protocol in Access Switches option.
Range command. AFM assigns IP addresses to all the Core and Aggregation switches. The following figure displays the results after selecting the Enable Layer 3 Protocol in Aggregation Switches option and adding VLANs for a Layer 3 fabric. Figure 70.
Figure 71. Advanced VLAN IP Configuration Option Figure 72.
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 45. Port Channel Configuration Options Field Name Description Add Enter the port channel information and enable LACP.
L2 VLT/L3 Routed VLT Pre-Deployment — VLAN Mapping To add VLANs and associate ports on the different access switches to which VLAN for a Layer 3 with Resiliency (Routed VLT) fabric, use the VLAN Mapping screen. After adding the VLANs and associating them with ports, you can copy switch VLAN or port VLAN configurations. Associate one or more tagged VLANs with a port. For untagged VLANs, only one association is supported.
Table 48. VLAN-Port Mapping Field Descriptions Field Name Description VLAN View the port name (read-only). Tagged Port/Port Channel Enter one or more tagged ports to associate with the VLAN. Untagged Port/Port Channel 1. 2. Click on the icon next to the field entry. Select one or more ports to associate with the VLAN. Enter one or more untagged ports to associate with the VLAN. 1. 2. Click on the icon next to the field entry. Select one or more ports to associate with the VLAN. Table 49.
Figure 74. Pre-deployment Configuration — VLAN Mapping 4. From the Switches drop-down menu, select an access or aggregation switch. The selected switch for the VLAN mapping displays in the read-only Model field. 5. In the Tagged VLANs field, click the icon to the right and enter one or more VLANs to associate with the port. 6. To enable hybrid port mode, select one or more ports and click Enable Hybrid Mode. To disable hybrid port mode, select the ports and click Disable Hybrid Mode.
Figure 75. Change Port Status Screen 4. From the Switches drop-down menu, select an access switch to enable the downlinks on that switch. The selected access switch for the port status appears in the read-only Model field. By default, AFM enables the configured port channels and VLANs on the access switch as downlink ports and displays the status details for these ports. 5. Select one or more ports and click Enable. • To disable one or more ports, select the port or ports and click Disable.
NOTE: When configured ports are part of a VLAN, the fabric design only configures VLAN access. 7. 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. From the menu, click Network > Fabric Name and then click the Configure and Deploy tab. 2. From the Deploy Fabric drop-down menu, select Pre-deployment Configuration. 3. Navigate to the Management IP screen. 4.
system CLI user’s credentials and enable the configuration credentials for all the switches in the fabric. This option allows you to remotely make configuration changes to the switches in the fabric. 1. From the menu, click Network > Fabric Name and then click the Configure and Deploy tab. 2. From the Deploy Fabric drop-down menu, select Pre-deployment Configuration . 3. Navigate to the SNMP and CLI Credentials screen. 4. Navigate to the SNMP Configuration area. 5.
Pre-Deployment — 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.
• Specified IP and protocol settings for the fabric, uplink, and downlink configuration • Software image information for each type of switch • Configuration file transfer status to the remote or local TFTP or FTP server 1. From the menu, click Network > Fabric Name and then click the Configure and Deploy tab. 2. From the Deploy Fabric drop-down menu, select Pre-deployment Configuration. 3. Navigate to the Summary screen. 4. Carefully review the pre-deployment configuration. 5.
Figure 77. Configure and Deploy — Deploy and Validate NOTE: During initial deployment, the BMP process wait time to install the software onto the switches in the fabric depends on whether stacking is enabled. Approximate wait times are: • 10 minutes for a non-stacked fabric • 20 minutes for stacked fabric To view a custom configuration file, navigate to the Network > Fabric Name> Configure and Deploy tab. From the CLI Configuration drop-down menu, select the Custom Configuration option.
Number Status Status Details Recommended Action 12 InProgress Device cleanup task done, reload in progress... None 13 InProgress Complete config upload in progress... None 14 InProgress Smart script transfer in progress... None 15 InProgress Custom config upload in progress... None 16 InProgress Backup config in progress... None 17 InProgress Merged config upload in progress... None 1. Verify that the software images for the switches are installed on the TFTP or FTP server. 2.
Aborting Deployment 1. From the menu, click Network > Fabric Name and then the Configure and Deploy tab. 2. From the Deploy Fabric drop-down menu, select Deploy and Validate. The Deploy and Validation dialog box appears. 3. On the Deploy tab, select the switches. 4. Click Abort Selected. 5. In the confirmation dialog box, click Yes.
• All — Associate the template to all the switches in the fabric. • Aggregation — Associate the template to all aggregation switches. • Access — Associate the template to all access switches. • Core — Associate the template to all core switches. • Spines — Associate the template to all spine switches. • Leafs — Associate the template to all leaf switches. • 9. Custom — Associate the template with specific switches. In the Available Switches, select the switches to associate with the template.
7. To view the last applied configuration or save it, click View or Save To next to the Last committed configuration on the switch area. 8. Review the combined configuration and make any necessary changes. 9. If you make changes, click Save To to save the combined auto-generated and custom configuration. 10. Click OK to close the Switch Specific Custom Configuration dialog box. Preview Combined Configuration To preview the combined configuration: 1.
Number Status Status Details Response Action 4. 4 Error HOSTNAME/MAC Address/MODEL Mismatch and STANDBY UNIT down To check for switch mismatch errors: 1. 2. 3. 4. 5 Error STANDBY UNIT down 2. 3. 4. Error Switch is not reachable 2. 3. 4. Error Switch is not Discovered 2. 3. 4. Error Configuration mismatch errors exist From the menu, click Network > Fabric Name and then click the Configure and Deploy tab. Click Errors. To view error details, click the Discovered Errors tab. Fix any errors.
Number Status Status Details Response Action 3. 4. 9 Error Custom Configuration errors exist To check for switch custom configuration errors: 1. 2. 3. 4. 10 Error Wiring Errors Exist 2. 3. 4. 5. Error Validation failed because switch license mismatch (Z9500–series switches only) From the menu, click Network > Fabric Name and then click the Configure and Deploy tab. Click Errors. To view error details, click the Custom Config Errors tab. Fix any errors.
Viewing Deployment and Validation Status 1. From the menu, click Network > Fabric Name and then click the Configure and Deploy tab. 2. Select the fabric. 3. From the Deploy Fabric drop-down menu, select Deploy and Validate. The Deploy and Validation dialog box appears, displaying all configured switches and their status. Custom CLI Configuration This section contains the following topics.
3. Select the template. 4. Click Edit. The Edit Template dialog box appears. 5. In the Template Name field, enter a name for the template. 6. (Optional) In the Description field, enter a description for the template. 7. In the Configuration Commands area, edit the CLI commands. 8. Click OK. Deleting Templates • Before you delete a template, make sure that the template is not in use. You can only delete templates that are not being used.
Associating Templates 1. From the menu, click Network > Fabric Name and then click the Configure and Deploy tab. 2. From the CLI Configuration drop-down menu, select the Associate Templates option. 3. Click Add Association. The Associate Templates dialog box appears. The Associate Template dialog box appears. 4. In the Template Name drop-down menu, select the template. 5. (Optional) In the Comments field, enter any comments about this association. 6.
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. From the menu, click Network > Fabric Name and then the Configure and Deploy tab. 2. From the Deploy Fabric drop-down menu, select Advanced Configuration. The Advanced Configuration dialog box appears. 3. On the Deploy tab, select Advanced Configuration. The Advanced Configuration dialog box appears. 4.
• 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. • Applied Custom Configuration Commands — View all template-based custom configuration commands and switch-specific custom configuration commands applied during deployment or redeployment, including command execution errors. 1. Navigate to the Network > Fabric Name > Configure and Deploy screen. 2.
Discovering and Deploying an Existing Fabric 7 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 80. Discovering and Deploying an Existing Fabric 1. Initiate discovery of an existing fabric. Refer to Step 1: Discover an Existing Fabric. 2. Check the status of the discovered fabric.
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. From the menu, click Network and then the Design Fabric tab. The Network Deployment Summary screen appears. 2. Click Discover Fabric. The Introduction screen for the Discover Fabric wizard appears. 3. Read the introduction and click Next. The Fabric Name and Type screen appears. 4. Enter the fabric name in the Fabric Name field.
Figure 81. Preview IP Address Window 8. Add at least one IP address to the List of added IPs: field and click Next. The Credentials screen appears. 9. In the SNMP section, click Add. The SNMP Credential window appears.
Figure 82. 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.
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. NOTE: • To delete CLI credentials, check the checkbox for the credentials you want to delete and click Delete in the CLI section.
• 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. 1. From the menu, click Network and then the Design Fabric tab. 2. Click Discovery Status.
8 Viewing the Fabric 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 tab displays all discovered switches in the fabric. From this screen, you can: • View simplified or detailed inventory information • Refresh the inventory • Export the current inventory as a comma-separated value (CSV) file Figure 84.
AFM exports the fabric data as a spreadsheet. Dashboard You can view the fabric and system health on the Dashboard tab. You can access this tab by selecting Home from the menu and then clicking the Dashboard tab. Figure 85. Dashboard Figure 86.
The Dashboard provides the following 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.
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. For more information, refer to Alerts and Events. Network Topology To display all the fabrics in the network topology in a graphical or tabular view, use the Network > Summary tab. The network topology view contains a collection of fabric icons with a color-coded status and fabric names. There are no links between fabrics.
Figure 88. 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 has not deployed or managed these fabrics • Selection — To view the fabric data in the Summary tab, click a fabric icon. • Popup menu — To display a menu of available actions and the fabric name, right-click a fabric.
• Enable Move — To move each fabric icon to a new location in the map, enable this option. • Revert to Last Saved — Revert fabric locations to the last saved version. • Save Move — Save changes to fabric locations. Fabric Summary The Network > Fabric Name > Summary tab displays information about a network fabric and its constituent switches in tabular or graphical format. Displaying the Fabric in a Tabular View To view the switches in the fabric and check alarms, click Tabular.
Figure 89. Fabric Summary Screen — Graphical View For information about how to configure the Active Link, navigate to the Active Link Settings screen. The following options are available from the Topology Options menu: • 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.
Troubleshooting 9 This section contains the following topics: • Ping, Traceroute, Telnet, and SSH • Validation Alarms • Deployment and Validation Errors • TFTP/FTP Error • Switch Deployment Status • Validating Connectivity to the ToR Ping, Traceroute, Telnet, and SSH To troubleshoot a switch in the fabric, use ping, traceroute, SSH, or Telnet. NOTE: SSH or Telnet functionality depends on the switch protocol configuration. 1.
Table 57. 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. To verify that you have correctly mapped the system MAC address to the associated switches: a. 2. Navigate to the Network> Fabric Name > Configure and Deploy tab. b.
Alarm Recommended Action a. 2. Navigate to the Network> Fabric Name > Configure and Deploy tab. b. From the Deploy Fabric drop-down menu, select the Pre-deployment Configuration option c. Navigate to the Assign Switch Identities screen and check the system MAC address mapping for the associated switches. To verify changes, validate the switch: a. b. c. d. Validation failed because the switch is in a disconnected state. Validation failed because Te 0/1 has a wiring mismatch.
Table 58. 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. Navigate to the Network > Fabric Name > Configure and Deploy tab. From the Deploy Fabric drop-down menu, select Predeployment Configuration. Redo the DHCP Integration step.
Error Details Recommended Action b. c. d. e. 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 tab by selecting the switch from the list. a. b. c. d. e. Smart script transfer failed 1. 2. b. c. d. e. 1. 2. b. c. d. e. 1. 2. Navigate to the Network > Fabric Name > Configure and Deploy tab. From the Deploy Fabric drop-down menu, select Deploy and Validate.
Error Details Recommended Action c. d. e. Click the Deploy tab and then select the switches. Click Deploy Selected. In the confirmation dialog box, click Yes. Validation Errors To troubleshoot the following validation errors when you deploy a fabric, use the following tables. The validation process reports any inconsistencies between the design and the discovered fabric. AFM reports mismatches as errors and generates the corresponding alarms.
Figure 90. Validation Errors Screen Table 60. Configuration Errors Error Details Recommended Action Configuration Mismatch 1. 2. 3. 4. 5. 6. On the Configure and Deploy tab, select the switch. Click Errors. Click the Config Errors Mismatch tab. Click View Mismatch. Review the configuration mismatch and correct the configuration errors. Restart switch validation from the Configure and Deploy tab by selecting the switch from the list and from the Deploy drop-down menu, click Deploy and Validate.
Error Details Recommended Action 3. Validate the switch. a. Navigate to the Network > Fabric Name > Configure and Deploy tab. From the Deploy Fabric drop-down menu, select Deploy and Validate. Click the Validation tab and then select the switches. Click Validate Selected. b. c. d. Missing Link 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 tab.
Table 63. Discovered Switch Error Error Details Recommended Action Disconnected 1. 2. 3. Verify connectivity from the AFM server to the switch. Verify that the switch is running the minimum required software. Validate the switch. 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.
Error Details Recommended Action 3. Verify that the license installation task is successful during deployment. Switch Deployment Status Errors Table 64. Switch Deployment Status Errors Switch Deployment Status Description Requires Action NOT STARTED Not Started No Recommended Actions 1. 2. 3. Start the switch deployment on the Network > Fabric Name > Configure and Deploy tab by selecting the switch from the list. From the Deploy Fabric drop-down menu, select Deploy and Validate.
Switch Deployment Status Description Requires Action CONFIG FILE TRANSFER FAILED Configuration File Transfer Failed Yes Recommended Actions 1. 2. 3. 4. CONFIG FILE TRANSFER SUCCESS Configuration File Transferred Successfully No REQUEST TO DISCOVER NODE Request To Discover Switch Yes 1. 2. 4. Minimum Configuration Upload In-Progress MIN CONFIG UPLOAD ERROR Minimum Configuration Yes Upload Error No Power on the switch.
Switch Deployment Status Description Requires Action Recommended Actions Configure and Deploy tab by selecting the switch from the list. 6. 7. NOTE: Verify that the switch is in BMP mode. From the Deploy Fabric drop-down menu, select Deploy and Validate. On the Deploy tab, select the switch and click Deploy Selected.
Switch Deployment Status Description Requires Action Recommended Actions 7. 8. Deploy tab by selecting the switch from the list. From the Deploy Fabric drop-down menu, select Deploy and Validate. On the Deploy tab, select the switch and click Deploy Selected.
Switch Deployment Status Description Requires Action Recommended Actions REDEPLOYMENT REQUIRED Re-deployment of the switch is required Yes Restart switch deployment. NOTE: Verify that the switch is not in BMP mode. 1. 2. 3. Navigate to Network > Fabric Name > Configure and Deploy tab by selecting the switch from the list. From the Deploy Fabric drop-down menu, select Deploy and Validate. On the Deploy tab, select the switch and click Deploy Selected. Deployment Task Errors Table 65.
AFM Deployment Task Error Status Recommended Action 2. Enable BMP on the switch. • • For S55 or S60, use the reload-type jumpstart config-download enable command. For all other switch types, enter CONFIG mode and use the reload-type bmp config-scrdownload enable command. Stack unit cleanup Stack unit renumbering task: Failed Verify Telnet/SSH/SNMP connectivity. Upgrade standby Upgrade standby: Failed The standby MAC was not found or reported a card problem.
AFM Deployment Task Error Status Recommended Action 4. 5. 6. Enter your user name and password for the FTP connection. Enter the URL location for the switch software image. Press Enter. For more information, refer to Uploading Switch Software Images in the AFM Deployment Guide. TFTP/FTP Errors Table 66. Deployment Status Configuration Errors Deployment Status Error Category TFTP/FTP Failed Configuration Deployment Error Error Details Recommended Action Error occurred during TFTP/FTP 1. 2.
Alerts and Events 10 This section contains the following topics: • Current — Active Alerts • Historical — Alerts and Events Current Active Alerts You can view active network, fabric, and switch alerts on the Current view of Alerts and Events tab. You can perform the following tasks on this tab: • 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 92. Fabric Alerts • To filter active switch alerts, click Network > Fabric Name > Switch Name and then click the Alerts and Events tab. Figure 93. Switch Alerts • To acknowledge an active alert, select the active alert and then click Acknowledge. • To dismiss an acknowledged alert, select the alert and then click Unacknowledge. • To dismiss an active alert, select the alert and then click Clear. 1. Click Current. 2. Click the filtering icon on the right of the screen.
• Cleared • Unknown • Info 4. • Indeterminate In the Source IP Address 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: 8. • All • Yes • No Click Apply. Historical Alerts and Event History On the Alerts and Events tab, you view historical events at the network, fabric, or switch level.
9. 188 Click Apply.
Performance Management 11 This section contains the following topics: • Network Performance Management • Fabric Performance Management • Switch Performance Management • Port Performance Management • Detailed Port Performance Management • TCA Threshold Setting • Data Collection • Reports Network Performance Management On the Performance tab, you can monitor the following network historical data for all the fabrics: • Bandwidth utilization • Top 25 port inbound usage • Top 25 port outbo
Figure 94. Global Statistics Screen of the Performance Tab Fabric Performance Management On the Performance tab, you can monitor the following information for all the switches in the fabric: • Bandwidth utilization • Top 25 port inbound usage • Top 25 port outbound usage • Top 10 highest CPU utilization • Top 10 high memory utilization Figure 95. Fabric Statistics Screen – Performance Tab You access the Performance tab by clicking Network > Fabric Name on the menu.
NOTE: To view performance, enable data collection on the Data Collections tab, which is accessed by clicking Jobs from the menu. Figure 96. Switch Performance Tab Port Performance Management 1. From the menu, click Network > Fabric Name > Switch Name and then make sure that the Summary tab is selected.
Figure 97. Summary and Performance Tabs with Port Performance Details 2. Select a port and then click the Performance tab. 3. Select a date type: • Real-Time Data • Historical To display port performance, select one of the following View Type options: 4. • Bar • Graphical • Tabular Review the performance information. 5.
For Power over Ethernet (PoE) ports, the following metrics are available: • Power in Milliwatts • Voltage in volts • Current in MilliAmps • Temperature in celsius 1. From the menu, click Network > Fabric Name > Switch Name and then make sure that the Summary tab is selected. 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.
clicking the Data Collections tab. Next, click Edit Threshold Settings. The Average Traffic Threshold option monitors the Layer 3 fabric link bundle. The TCA Bandwidth option monitors low bandwidth and high bandwidth for Layer 2 and Layer 3 fabrics. If the average traffic or both utilization thresholds are exceeded, AFM receives an alarm from the switch on the Alerts and Events tab. Figure 98. TCA Bandwidth • Average Traffic Threshold — Configure the threshold for a Layer 3 fabric.
Figure 99. Traffic Utilization Alert Threshold For information about how to view port performance, refer to Detailed Port Performance Management. 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 data collection. Refer to Data Collection. Creating New Reports 1. From the menu, click Jobs and then click the Reports tab. 2.
7. In the Output Format area, select a report output format: • 8. 9. Tabular • Chart Click Next. In the Monitors field, select the monitors to use for the report and click the >> button. The monitors that you can select depend on whether you selected Switch or Port.
NOTE: If you select a custom range, specify a start and end date. 16. Click Next. 17. On the Summary screen, review the report settings. 18. To run the report now, check the Run Report Now check box. 19. Click Finish. Editing Reports 1. From the menu, click Jobs and then click the Reports tab. 2. Select the report. 3. Click Edit. The Add/Modify Report window appears. 4. Edit the report. 5. To navigate to different parts of the report, click Next. 6. In the Summary area, review the changes. 7.
Maintenance 12 This section discusses maintenance tasks for Active Fabric Manager.
Figure 100. AFM Virtual Appliance Options Screen Configuring the System To configure the AFM server settings, use the Configure System option. • Device configuration (Network Configuration) — Use this option to configure a static IP as the AFM Ethernet controller or change another device’s eth0 attribute. • DNS configuration — Use this option to configure the AFM DNS settings. 1. Select Configure System and press Enter.
Figure 101. Select Action Screen 3. Select Device configuration. To navigate between elements, use the Tab and down arrow keys. The Network Configuration screen appears. Figure 102. Network Configuration Settings Screen 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. • Primary DNS Server — Specify the primary DNS server address.
Changing the AFM Superuser Password 1. Select Change AFM Superuser Password option. 2. Press Enter. The CHANGE AFM SUPERUSER PASSWORD screen appears. Figure 104. Change AFM Superuser Password 3. In the Enter current superuser password field, enter the superuser password (for example, Superuser1). NOTE: The password must have 8–32 characters and include at least three of the following character types: 4.
3. If the location is a remote server, enter the URL location of the RPM file on the remote server using the following formats and click Enter: • https://ipaddress/path_to_rpm.file • ftp://ipaddress/path_to_rpm.file • sftp://ipaddress/path_to_rpm.file 4. If the location is local, enter the absolute path of the RPM file and then click Enter. 5. If necessary, enter your user name and password. 6. Press Enter to return to the main menu.
Figure 105. Transfer Files 2. Press Enter. 3. Enter the file type to transfer: • 1. Syslog • 2. AFM Database Backup • 3. AFM Configuration and Database Backup 4. • 4. AFM Performance Database Backup Press Enter. 5. To upload all the files to the FTP or TFTP server, click y. 6. Press Enter. 7. Press Enter to return to the main menu. Editing AFM Files You can edit the following types of files using the Edit File option: • 1. logback.xml — The logback.
Figure 106. Edit AFM File System 3. Press Enter. 4. Search for com.dell.dfm and com.dell.wnm. Change the logging level from level=INFO to level=DEBUG. For example: 5.
Figure 107. 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. If the folder does not exist, the backup program will try to create it wnm.database.backup.folder=/data/backup/postgres # The backup job will be started every day at 2am. wnm.database.backup.
Figure 108. AFM Virtual Appliance Upload Switch Software Image Screen 2. Enter a switch model option. The range is 1–9. • 1. MXL Blade • 2. S4810 • 3. S4820T • 4. S55 • 5. S60 • 6. Z9000 • 7. S6000 • 8. S5000 • 9. IOA 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.
Backing up the AFM Database NOTE: 1. • The backup file does not include AFM historical performance data. • The AFM server IP must be the same as the location of the database backup file. Select Backup Database. The Backup Configuration and Database screen appears. 2. Select a backup option: NOTE: If AFM uses the local DHCP server and/or a local FTP server, select AFM Configuration and Database to back up the database instead of AFM Database. • 1. AFM Database — Back up the AFM database files only.
Figure 110. 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. Use the 1. AFM Database option. Similarly, you cannot restore configuration files using the 1. AFM Database option. 3. • 1. AFM Database — Restore the AFM database files only. • 2.
Backing Up a Switch On the Back Up Switch view of the Maintenance tab, you can 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. This screen has the following options: • Backup Switch — Schedule a backup for a switch’s running configuration and startup configuration files now or later.
Viewing and Editing the Switch Backup Configuration You can use AFM to edit the running or startup configuration on deployed devices. The edited configuration is available after you restore the switch backup configuration. 1. 2. From the menu, click Network > Fabric Name and then click the Maintenance tab. Click Backup Switch in the upper right of the screen and then click View/Edit. The View and Edit Switch Backup Screen Configuration screen appears. Figure 111.
• Scheduling Switch Software Updates — Create a new scheduled software image upgrade and software image activation job. • Activating Standby Partition Software — 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 toReplacing a Switch . 1.
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. From the menu, click Network > Fabric Name > Switch Name. 2. Click the Switch Replacement tab. 3. Click Deploy Switch. NOTE: If you change the switch outside of AFM (for example, using Telnet), refer to Restoring a Switch Configuration to restore the switch configuration. For information about how to replace a switch, refer to Replacing a Switch. Updating AFM You can view and manage AFM server updates on the Server Update tab. 1.
Jobs 13 This section contains the following topics: • Displaying Job Results • Scheduling Jobs Displaying Job Results To view job status, use the Job Results tab. 1. From the menu, click Jobs and then make sure that the Job Results tab is selected 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.
• 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. • Run Now — Start a job immediately. Select a job and click Run. • 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.
7. In the Update Location area, if necessary, click Edit TFTP or FTP settings. 8. In the Path and Image file name to the software updates on selected TFTP or FTP site field, specify the path and image file for the switch software update. 9. Click Next. 10. In the Update Option area, select one of the following options and click Next: • Manual — Stage the update to the secondary partition but do not apply it. • Automatic — Apply the software update and reboot. The Schedule screen appears. 11.
software updates and then schedule the update to load immediately or schedule it for a later date and time. 1. From the menu, click Network > Fabric Name and then click the Maintenance tab. 2. Click Update Software. 3. Click Schedule Switch Software Image Update. 4. On the Job Name screen, in the Job Name field, enter a unique name for the software job. 5. (Optionally) In the Description field, enter a description for the schedule software update. 6. Click Next.
8. • Three-tier filtering options — All, Core, Aggregation and Access Select the switches for standby partition activation and then click the >> button to move them to the Selected area. 9. Click Next jn. 10. From the Schedule screen, select one of the following options and click Next: • Run Now — Schedule the job to run immediately. • Schedule job to start on — Schedule the job to run later. 11. Review the Summary settings and click Finish. Scheduling a Back Up Switch Configuration 1.
Administration 14 This section contains the following topics: • Administrative Settings • Managing User Accounts • Managing User Sessions • Audit Log • Updating the Server 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, follow these steps: 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. Disable the Application Server and Synergy Network Management server. com.dorado.core.ws.disable=false com.dorado.core.ws.legacy.
• Navigate to the Network >Switch > Summary tab > Tabular view and click Launch Active Link. The Active Link displays the selected switch view and performance charts. 1. From the menu, click Administration and then click the Settings tab. 2. Navigate to the Active Link Settings area and click Edit. 3. In the Active Link Type area, select the Integrate to Dell OpenManage Network Manager (OMNM) check box to display additional performance statistics. 4.
• 30 Seconds • 60 Seconds 4. • 120 Seconds From the New Window per 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. From the menu, click Administration and then click the Settings tab. 2. In the Data Retention area, click Edit. 3.
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. In the To Email Address(es) field, enter the mail addresses separated by a semicolon (;). 8. • Critical • Major • Minor • Warning Click OK. SNMP Configuration Configure SNMP so that AFM can perform SNMP queries on the switches in the fabric. AFM uses the SNMP configuration values for configuring and monitoring the switches. 1.
4. • Remote — Use an external TFTP server. Enter the TFTP IPv4 address. For FTOS switches, in the TFTP/FTP Settings area, select one of the following options: • Local — Provision AFM as a TFTP or 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 FTP server option, the FTP server uses the AFM management IP address. Enter the AFM user name and password.
• Unlock — Unlock account for a user who was locked out because he or she exceeded the maximum number of login attempts. To unlock a user account, select the user and click Unlock. • Default User — During the installation process, AFM prompts you to create a Superuser account. • Reset Default User (Superuser) Password — Contact technical support if you need to reset the Superuser password. • Password Rules — Enforces special password rules for enhanced security.
12. In the Lockout Duration drop-down menu, select one of the following options. • 15 minutes • 30 minutes • 45 minutes • 60 minutes • Permanent The default value is 30 minutes. 13. Click OK. Editing a User To edit a user, log in as a Superuser. For more information about user accounts, refer to Managing User Accounts. 1. From the menu, click Administration and then click the User Accounts tab. 2. Select the user. 3. Click Edit. The Edit User dialog box appears. 4.
NOTE: You cannot delete the Superuser account. 1. From the menu, click Administration and then click the User Account tab. 2. Select the user. 3. Click Delete. 4. In the confirmation dialog box, click Yes. Unlocking a User To unlock a user, log in as a Superuser. For information about user accounts, refer to Managing User Accounts. 1. From the menu, click Administration and then click the Users Account tab. 2. Select the user. 3. Click Unlock. 4. Click OK. Changing Your Password 1.
To terminate users’ sessions: 1. From the menu, click Administration and then click the User Session tab. 2. Select the users that you want to log off. 3. Click Force Logoff. 4. Click OK. 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, use the Audit Log tab. The Audit Log only captures actions by AFM users. Figure 112. Audit Log Tab 1.
8. 9. • Query • Create • Modify • Cancel • Move • SNC Config • Monitor • Login • Logout From the Status drop-down menu, select an audit trail progress status: • All • Queued • In Progress • Success • Failure • Timeout • Response Delivered • Invalid Request (Optional) In the Reason field, enter a reason. 10. Click Apply. • To export the results, click Export.
Technical Support 15 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.
