Deployment Guide

ManualsBrandsDell ManualsserversDell Active Fabric Manager

Active Fabric Manager (AFM)

Deployment Guide 2.0

Summary of content (179 pages)

PAGE 1
Active Fabric Manager (AFM) Deployment Guide 2.
PAGE 2
© 2013 Dell Inc. All Rights Reserved. Trademarks used in this text: Dell™, the Dell logo, Dell Boomi™, Dell Precision™ , OptiPlex™, Latitude™, PowerEdge™, PowerVault™, PowerConnect™, OpenManage™, EqualLogic™, Compellent™, KACE™, FlexAddress™, Force10™, Venue™ and Vostro™ are trademarks of Dell Inc. Intel®, Pentium®, Xeon®, Core® and Celeron® are registered trademarks of Intel Corporation in the U.S. and other countries.
PAGE 3
Contents 1 Introduction..................................................................................................................................9 Problem: Challenges to Build a Fabric in the Data Center........................................................................................9 Solution: Active Fabric Manager.............................................................................................................................. 9 2 About AFM.......................................
PAGE 4
Fabric Design – Step 1: Fabric Name and Type............................................................................................... 52 Fabric Design – Step 2: Bandwidth and Port Count......................................................................................... 53 Deployment Topology Use Cases.....................................................................................................................55 Fabric Design – Step 3: Deployment Topology....................................
PAGE 5
8 Viewing the Fabric.................................................................................................................. 123 Dashboard............................................................................................................................................................ 123 Network Topology.................................................................................................................................................125 Network Topology Tabular View.........
PAGE 6
Duplicating Reports........................................................................................................................................155 Deleting Reports.............................................................................................................................................156 12 Maintenance..........................................................................................................................157 Back Up Switch.....................................
PAGE 7
Deleting a User...............................................................................................................................................176 Editing a User................................................................................................................................................. 176 Unlocking a User............................................................................................................................................ 177 Changing Your Password...
PAGE 8
PAGE 9
Introduction 1 Active Fabric Manager (AFM) is a graphical user interface (GUI) based network automation and orchestration tool that enables you to design, build, deploy, and optimize a Layer 2 Virtual Link Trunking (VLT), Layer 3 distributed core, and Layer 3 with Resiliency (Routed VLT) fabric for your current and future capacity requirements. This tool helps you simplify network operations, automate tasks, and improve efficiency in the data center.
PAGE 10
PAGE 11
About AFM 2 Active Fabric Manager (AFM) is a graphical user interface (GUI) based network automation and orchestration tool that allows you to design, build, deploy, and optimize a Layer 3 distributed core, Layer 3 with Resiliency (Routed VLT), and Layer 2 VLT fabric for your current and future capacity requirements. This tool helps you simplify network operations, automate tasks, and improve efficiency in the data center. NOTE: Before you begin, review the Getting Started page.
PAGE 12
PAGE 13
Getting Started 3 This section contains the following topics: • Designing and Deploying the Fabric • Flowchart for Designing and Deploying a Fabric Related links: • Supported Fabrics • Designing the Fabric • AFM Site Map NOTE: You can view the Active Fabric Manager Deployment Guide in the AFM by selecting the Deployment Guide option from the Help pull-down menu in the upper right of the screen.
PAGE 14
Figure 1. Getting Started Wizard To design and deploy a Layer 2 VLT, Layer 3 distributed core fabric, or Layer 3 with Resiliency (Routed VLT) 1. Gather useful information. Related links. 2. – Gather Useful Information for Layer 2 VLT Fabric – Gathering Useful Information for a Layer 3 Distributed Core Fabric. – Gathering Useful Information for a Layer 3 with Resiliency (Routed VLT) Fabric Design the fabric.
PAGE 15
– 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. 8. Monitor the fabric health and performance. See Performance Management.
PAGE 16
Figure 3.
PAGE 17
4 AFM Site Map To help you navigate the AFM user interface use the following site map.
PAGE 18
Jobs Job Results Schedule Jobs Backup Switch Configuration Files Update switch software Active Software Data Collection Schedule data collection Edit threshold Reports Create Edit Delete Duplicate Run Administration Audit Log Administration Active Link Settings CLI Credentials Client Settings Data Retention Settings DHCP Server Settings NTP Server Settings Email Settings Syslog IP Addresses SNMP Configuration System Information TFTP/FTP Settings User Accounts Add User Delete User Edit User Unlocking
PAGE 19
Supported Fabric Types 5 The fabric design wizard defines the basic configuration for a Layer 2 VLT, Layer 3 distributed core, and Layer 3 with Resiliency (Routed VLT) fabric. • Use the Layer 3 distributed core fabric for large fabric deployments. For information about distributed core fabrics, see Conventional Core Versus Distributed Core and Selecting a Layer 3 Distributed Core Fabric Design. • Use the Layer 2 VLT fabric for workload migration over virtualized environments.
PAGE 20
Key Considerations for Designing a Layer 3 with Resiliency (Routed VLT) Fabric Use the Layer 3 with Resiliency (Routed VLT) fabric to extend equal cost multi-pathing capabilities. When designing a Layer 3 with Resiliency (Routed VLT) fabric, consider the following: • You can deploy up to 10 fabrics. However, the fabrics do not communicate with each other. • AFM manages Dell Networking S4810, S4820T, S6000, and Z9000 switches.
PAGE 21
switches, the switches communicate with the DHCP server to obtain a management IP Address based on the system MAC Address. The DHCP server contains information about where to load the correct software image configuration file for each type of switch from the TFTP/FTP site during BMP. For information about BMP, see DHCP Integration. • Obtain the pool of IP addresses for the management port for each switch in the fabric.
PAGE 22
Distributed Core A distributed core is a two-tier architecture composed of multiple switches interconnected to provide a scalable, highperformance network that replaces the traditional and aggregation layers in a conventional core. Switches are arranged as spines and leaves; the spines fabric connect the leaves together using a routing protocol. The leaves’ edge ports connect to the switches, ToR switches, servers, other devices, and the WAN.
PAGE 23
Distributed Core Terminology The following terms are unique to the design and deployment of a Layer 3 distributed core fabric. • Leaf — A switch that connects switches, servers, storage devices, or top-of-rack (TOR) elements. The role of the leaves switches is to provide access to the fabric. The leaf switch connects to all of spines above it in the fabric. • Spine — A switch that connects to the leaves switches. The role of the spine is to provide an interconnect to all the leaves switches.
PAGE 24
Important: In a single distributed fabric, all the leaves can act as a non-ToR or as a ToR, not both at the same time. Key Considerations for Designing a Distributed Core When designing the Layer 3 distributed core fabric, consider the following: • You can deploy up to 10 fabrics. However, the fabrics do not communicate with each other. • AFM manages Dell S4810, S4820T, S6000, and Z9000 switches. CAUTION: If you are already using a deployed switch, reset the factory settings.
PAGE 25
• Whether the leaves act as a ToR or are connecting to a server. • Fabric interlink bandwidth (the links between the spines and leaves). • Uplinks which are 10 Gb. • Downlinks which are 1 Gb, 10 Gb, or 40 Gb. • When the Open Shortest Path First (OSPF) is selected for both uplinks and interlinks, one of the uplinks or interlinks must be in area 0. If one uplink is in area 0 then the interlinks must not be in area 0. • The fabric over-subscription ratio.
PAGE 26
Selecting a Layer 3 Distributed Core Fabric Design For large fabric deployments, use the Layer 3 distributed core fabric. AFM supports the following distributed core fabric designs: • Type 1: Extra Large Core Fabric • Type 2: Large Distributed Core Fabric • Type 3: Medium Distributed Core Fabric • Type 4: Small Distributed Core Fabric To select the appropriate Layer 3 distributed core fabric design, use the following table as a guide.
PAGE 27
Figure 5. Type 1: Extra Large Distributed Core Fabric Design Use the Type 1: Extra Large Distributed Core fabric design when: • The line rate-performance with a fabric oversubscription ratio of 1:1 between the spines and leaves. • The current and future planned uplinks and downlinks on the leaves for the distributed core is less than or equal to 2048 ports. For redundancy, each leaf in a large core design can connect 2 to 16 spines.
PAGE 28
Figure 6.
PAGE 29
Figure 7. Type 3: Medium Distributed Core Fabric Design Use the Type 3: Medium Distributed Core design when: • You require a fabric interlink (fabric links) bandwidth between the spines and leaves at a 40 Gb line rate. • The current and future planned uplinks and downlinks on the leaves for your distributed core fabric is less than or equal to 1536 ports. • The leaves act as a switch or ToR-leaf switch. Within the ToR, the protocol can be either VLAN or VLAN and LAG.
PAGE 30
With a Type 4: Small Distributed Core fabric design, the S4810 spines connect to the S4810 leaves at a fixed 10 Gb. The maximum number of spines is 4 and the maximum number of leaves is 16, as show in the following figure. Figure 8.
PAGE 31
• Provides fast convergence if either the link or a device fails • Optimized forwarding with Virtual Router Redundancy Protocol (VRRP) • Provides link-level resiliency • Assures high availability CAUTION: Dell Networking recommends not enabling stacking and VLT simultaneously. If both are enabled at the same time, unexpected behavior occurs.
PAGE 32
• Aggregation — A switch that connects to access switches. The role of the aggregation layer is to provide an interconnect to all the access switches. All the ports on the aggregation switches are used to connect the access, various racks together. The aggregation switch provides redundancy. • Edge ports — The uplinks on the aggregation and downlinks on the access. • Uplinks — An edge port link on the first two aggregation switches in the VLT fabric that connects to outside the fabric.
PAGE 33
connect through the non-VLT ports. Key Considerations for Designing a Layer 2 VLT Fabric Use the Layer 2 VLT fabric for workload migration over virtualized environments. When designing the Layer 2 VLT fabric, consider the following: • You can deploy up to 10 fabrics. However, the fabrics do not communicate with each other. • For a VLT fabric, the AFM manages Dell Networking S4810, S4820T, S55, S60, S6000, Z9000, and MXL Blade switches.
PAGE 34
Gathering Useful Information for a Layer 2 VLT Fabric To gather useful information for a layer 2 VLT fabric before you begin: • Obtain the CSV file that contains the system MAC addresses, service tag and serial numbers for each switch provided from Dell manufacturing or manually enter this information. • Obtain the location of the switches, including the rack and row number from your network administrator or network operator.
PAGE 35
• Getting Started. 1 Tier for 10 Gb and 40 Gb ToR for Layer 2 and Layer 3 Resiliency (Routed VLT) Table 2.
PAGE 36
DL BW = Down Link Bandwidth FL BWB A & A = Fabric Link Bandwidth between Aggregation & Access UL BW = Uplink Bandwidth BW = Bandwidth Use the following table as guideline to select the appropriate 2– Tier Layer 2 VLT or Layer 3 with Resiliency (Routed VLT) fabric design for a 1 Gb ToR VLT deployment. NOTE: With a Layer 2 VLT fabric, the uplinks come from the first two switches on the aggregation side. For information about tiers, see Deployment Topology. Table 3.
PAGE 37
or S6000 1 Gb 10 Gb Stacking 2641 32256 2 * 40 Gb 2 * 40 Gb NA 80G 40 Gb Z9000 or S6000 S4810 S60 (12G or 24G) 1 Gb 40 Gb Stacking 2497 32256 2 * 40 Gb 2 * 40 Gb NA 80G 40 Gb Z9000 or S6000 S4810 S55 (12G ) 1 Gb 40 Gb Stacking 2497 32256 2 * 40 Gb 2 * 40 Gb NA 80G 40 Gb Z9000 or S6000 S4810 S60 (12G or 24G) 1 Gb 10 Gb Basic 2641 32256 2 * 40 Gb 2 * 40 Gb NA 80G 20 Gb Z9000 or S6000 S4810 S60 1 Gb 10 Gb Basic 2641 32256 2 * 40 Gb 2 * 40 Gb NA 80G 20 Gb Z9000 or
PAGE 38
Figure 10. 10 Gb or 40 Gb ToR VLT Deployment (mVLT) Important: All the VLT aggregation switches must be same mode type for aggregation; for example, Z9000. On the VLT access, you can configure the same model type or mixed the following model types: S4810 and S4820T.
PAGE 39
10 Gb 10 Gb Mixed node 111 - 1392 Stacking 2 * 40 Gb NA 160 Gb NA Z9000 or S6000 S4810 or S4820T 10 Gb 10 Gb Stacking 111 - 2970 2 * 40 Gb NA 40 Gb NA S4810 S4810 10 Gb 10 Gb Stacking 111 - 1392 2 * 40 Gb NA 160 Gb NA Z9000 or S6000 S4810 10 Gb 10 Gb Basic 111 - 3410 2 * 40 Gb NA 20 Gb NA S4810 S4810 10 Gb 10 Gb Basic 111 - 1624 2 * 40 Gb NA 80 Gb NA Z9000 or S6000 S4810 10 Gb 10 Gb Mixed node 111 - 3410 Basic 2 * 40 Gb NA 20 Gb NA S4810 S4810 or S482
PAGE 40
10 Gb 40 Gb Mixed node 105 - 1344 Resiliency 2 * 40 Gb 2 * 40 Gb 80G NA Z9000 or S6000 S4810 or S4820T AVC = Aggregation VLTi Capacity BW = Bandwidth DL = Downlink DL BW = Downlink Bandwidth FL BWB A & A = Fabric Link Bandwidth between Aggregation & Access UL BW = Uplink Bandwidth Use the following tables as guideline to select the appropriate 2– 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
PAGE 41
Table 7.
PAGE 42
10 Gb 40 Gb Resiliency 2809 36288 2 * 40 Gb 2 * 40 Gb 2 * 40 Gb 80 Gb 20 Gb Z9000 or S4810 S6000 S4810 10 Gb 40 Gb Resiliency 2809 36288 2 * 40 Gb 2 * 40 Gb 2 * 40 Gb 80 Gb 20 Gb Z9000 or S4810 S6000 S4820 10 Gb 40 Gb Resiliency 1345 18816 2 * 40 Gb 2 * 40 Gb 2 * 40 Gb 80 Gb 80 Gb Z9000 or Z9000 or S6000 S6000 S4810 10 Gb 40 Gb Resiliency 1345 18816 2 * 40 Gb 2 * 40 Gb 2 * 40 Gb 80 Gb 80 Gb Z9000 or Z9000 or S6000 S6000 S4820 AVC = Aggregation VLTi Capacity CVC = Core
PAGE 43
10 Gb Blade Switch (MXL) VLT Deployment BW = Bandwidth DL = Downlink FL BWB A & A = Fabric Link Bandwidth between Aggregation and Access UL BW = Uplink Bandwidth VLTi A BW = VLTi Aggregation Bandwidth Table 9.
PAGE 44
2 - 26 40 Gb Basic Layer 2/ Layer 3 with Resiliency (Routed VLT) 20 Gb 2 * 40 Gb NA NA S4810 or S4820T MXL 2- 27 10 Gb Stacking Layer 2/ Layer 3 with Resiliency (Routed VLT) 40 Gb 2 * 40 Gb NA NA S4810 or S4820T MXL 2 - 14 10 Gb Stacking Layer 2/ Layer 3 with Resiliency (Routed VLT) 160G 2 * 40 Gb NA NA Z9000 or S6000 MXL 2 - 14 40 Gb Stacking Layer 2/ Layer 3 with Resiliency (Routed VLT) 160G 2 * 40 Gb NA NA Z9000/S6000 MXL 2 - 26 40 Gb Stacking Layer 2/ Layer 3 w
PAGE 45
FL BWB C & A = Fabric Link Bandwidth between Core and Access UL BW = Uplink Bandwidth VCBW = VLTi Core Bandwidth Table 10.
PAGE 46
28 - 336 40 Gb Stacking Layer 2/ Layer 3 with Resiliency (Routed VLT) 80G 40 Gb 2 * 40 Gb 2 * 40 Gb Z9000 or S6000 S4810 or S4820T MXL 15 - 196 10 Gb Stacking Layer 2 or Layer 3 with Resiliency (Routed VLT) 80G 160G 2 * 40 Gb 2 * 40 Gb Z9000 Z9000 MXL 15 - 196 10 Gb Stacking Layer 2/ Layer 3 with Resiliency (Routed VLT) 80G 160G 2 * 40 Gb 2 * 40 Gb S6000 S6000 MXL 15 - 196 40 Gb Stacking Layer 2/ Layer 3 with Resiliency (Routed VLT) 80G 160G 2 * 40 Gb 2 * 40 Gb Z9000 Z9
PAGE 47
15 - 196 40 Gb MXL intraChassis resilienc y Layer 2 or Layer 3 with Resiliency (Routed VLT) 80G 80G 2 * 40 Gb 2 * 40 Gb Z9000 Z9000 MXL 15 - 196 40 Gb MXL intraChassis resilienc y Layer 2 or Layer 3 with Resiliency (Routed VLT) 80G 80G 2 * 40 Gb 2 * 40 Gb S6000 S6000 MXL 47
PAGE 48
PAGE 49
Designing the Fabric 6 To design a Layer 3 two-tier distributed core fabric or Layer 2 VLT fabric based on your capacity planning for your current and future needs, use the Fabric Design Wizard at the Network > Design Fabric > New Fabric screen. The design consists of a wiring plan, network topology information, summary of the inventory requirement, and a design specification. See also Network Deployment Summary.
PAGE 50
Table 11. Fabric Configuration Phases and States Phase State State Description Design Incomplete Indicates that not all required information to complete the design was provided. Complete Indicates that all required input was provided to complete the design. Required Indicates that not all required Pre-deployment Configuration information for any of the switches was provided. Pre-deployment Configuration NOTE: The Pre-deployment Configuration state for all switches is in state Required.
PAGE 51
Switch Configuration Phases and States This section describes the phases and possible states for a switch. Table 12. Switch Level States Phase State State Description Design Complete Indicates that design is complete for the switch. NOTE: At switch level, design Partial Complete will not be tracked. Partial Complete will only be tracked at the fabric level. Pre-deployment Configuration Required Indicates that not all required Pre-deployment Configuration information was provided.
PAGE 52
• Layer 3 distributed core — Use the Layer 3 distributed core for large fabric deployments. See Conventional Core Versus Distributed Core • Layer 3 with Resilency (Routed VLT) — Use the Layer 3 fabric to extend equal cost multi-pathing capabilities. See Selecting a Layer 2 and Layer 3 with Resiliency (Routed VLT). This screen allows you to create, edit, delete, and view the fabric. NOTE: You can also use the Fabric Design Wizard from the Home > Design New Fabric screen.
PAGE 53
4. Enter the name of the fabric in the Fabric Name field. The fabric name must be a unique name. It can have from 1 to 17 characters. Valid characters are as follows: – alphanumeric – underscore ( _ ) – + When you specify the name of the fabric, AFM automatically names the switches in the fabric with the fabric name as the prefix. For example, if the name of the fabric is EastFabric, the switch names assigned are EastFabricSpine-1 and EastFabric-Leaf1. 5.
PAGE 54
PAGE 55
To configure bandwidth and port count for the switches in the fabric: 1. In the Bandwidth Specification: a) Select the uplink bandwidth (10 Gb or 40 Gb) using the Uplink Bandwidth pull-down menu. b) Select the downlink bandwidth (1 Gb, 10 Gb, or 40 Gb) using the Downlink Bandwidth pull-down menu. 2. – When you select the 1 Gb Downlink Bandwidth option, the AFM supports deployment topologies with the S55 and S60 switches on the access side.
PAGE 56
• The downlinks from the 2 aggregation switches supports the Layer 2 protocol (VLAN or VLAN/VRRP). The default setting on the pre-deployment screen is VLAN configuration which allows you to configure downlink connections to servers. To support redundancy between the aggregation switches and ToR switches, select the VLAN and VRRP Configuration option. Figure 11. Example: Tier 1 with Layer 2 VLT fabric Deployment Topology Figure 12.
PAGE 57
Use Case 2: 1 Tier Layer 3 with Resiliency (Routed VLT) When you select a 1 tier Layer 3 with Resiliency (Routed VLT) fabric: • The uplinks between the 2 aggregation switches and external switch (WAN) supports the Layer 3 protocol (OSPF, iBGP or eBGP). • The downlinks from the 2 aggregation switches supports the Layer 2 protocol (VLAN/VRRP or VLAN IP). During the design phase at the Deployment Topology screen, you select the fabric type and deployment type (topology).
PAGE 58
• The downlinks from the access switches supports the Layer 2 protocol (VLAN or VLAN and LAG). – If the VLAN option is selected, the downlinks connecting to server is configured to use the VLAN protocol. – If the VLAN and LAG option is selected, the downlinks between the leafs and ToR is configured to use VLAN, VRRP, and LAG for redundancy. Figure 14.
PAGE 59
Figure 15. Example: 2 Tier Layer 3 with Resiliency (Routed VLT) with Stacking Option 2. Layer 3 with Resiliency (Routed VLT) with VLT option – When you select the VLT option, the default configuration is to enter the VLAN ID, Primary IP address and Secondary address. If you select the Enable Layer 3 Protocol in Access Switches option, configure the VLAN ID and then the IP Range.
PAGE 60
Figure 17. Layer 3 with Resiliency (Routed VLT) with VLT option + Advanced VLAN IP Configuration 3. Layer 3 with Resiliency (Routed VLT) – Basic option – When you select the Basic option, configure the VLAN with the primary and secondary IP addresses for each access switch. Figure 18. Layer 3 with Resiliency (Routed VLT) with Basic Option 4.
PAGE 61
Figure 19. Layer 3 with Resiliency (Routed VLT) with MXL Blade with interChassis option 5. Layer 3 with Resiliency (Routed VLT) – Blade MXL with IntraChassis option: With this topology, you select the deployment type using that has a MXL Blade switch with Resiliency (VLT) and Intrachassis (within the same chassis) resiliency option. Enter the VLAN ID, primary and secondary IP addresses. Figure 20.
PAGE 62
Use Case 5: 3 Tier Layer 2 When you select a 3 tier Layer 2 fabric: • The fabric links between core and aggregation switches supports the Layer 3 protocol. • The fabric links between aggregation and access switches supports the Layer 2 protocol. • The uplinks between the aggregation switches and external switch (WAN) supports the Layer 3 protocol (OSPF, iBGP or eBGP). • The downlink from the access switches supports the Layer 2 protocol (VLAN or VLAN/VRRP).
PAGE 63
example shown below, a Layer 3 with Resiliency (Routed VLT) fabric. Based on the deployment type option selected, different downlinks options are configured at the access tier. The following section lists the topology types that you can select: 1. Layer 3 with Resiliency (Routed VLT) with stacking option – When you select the Stacking option, configure the VLAN with the primary and secondary IP addresses for each access switch. Figure 22.
PAGE 64
Figure 23. Example: 3 Tier Layer 3 with Resiliency (Routed VLT) with VLT option Figure 24. 3 Tier Layer 3 with Resiliency (Routed VLT) with VLT Option + Advanced VLAN IP Configuration 3. 64 Layer 3 with Resiliency (Routed VLT) – Basic option – When you select the Basic option, configure the VLAN with the primary and secondary IP addresses for each access switch.
PAGE 65
Figure 25. Example: 3 Tier Layer 3 with Resiliency (Routed VLT) with Basic Option 4. Layer 3 with Resiliency (Routed VLT) – Blade MXL with IntraChassis option: With this topology , you select the deployment type that has a MXL Blade switch with Resiliency (VLT) and Intrachassis (within the same chassis) resiliency option. Enter the VLAN ID, primary and secondary IP addresses. Figure 26.
PAGE 66
deployment topology filter icon on the top right of the screen to display additional deployment topology options. The output from these screens and the Deployment Topology and Fabric Customization screens create a network topology and the detailed wiring plan. See also Deployment Topology Use Cases. Based on your design requirements you can create a 1, 2, or 3 tier topology as shown below • Tier 1 Topology — Contains 2 switches and a downlink and uplink configuration. There are no fabric links. Figure 27.
PAGE 67
NOTE: For topologies, refer to the Designing a Layer 2 VLT and Layer 3 with Resiliency (Routed VLT) Fabric and Selecting a Layer 3 Distributed Core Fabric Design. Table 13.
PAGE 68
Resiliency In MXL (Routed VLT) • low latency — The access layer uses S55 switches • • Intra-chassis — Within the chassis (mVLT) Inter-chassis resiliency — Across 2 chassis (VLT) This section contains the following topics: • (Optional) Configuring Advanced Options • Selecting the Fabric Deployment Type (Optional) Configuring Advanced Options For a Layer 2 or Layer 3 with Resiliency (Routed VLT) fabric, you customize the bandwidth between the aggregation and access switches.
PAGE 69
5. On the Deployment Type, select the appropriate deployment type. 6. Click the deployment topology filtering icon on the top right of the screen to display deployment topology options. Only applicable options are displayed. 7. Configure the filter options for the deployment topology and click the Apply button. 8. Click the Next button to go to the Fabric Customization screen. 9.
PAGE 70
Figure 33. Layer 3 with Resiliency (Routed VLT) : Deployment Type screen 1. Navigate to the Network > Design Fabric > New Fabric > Deployment Topology screen. 2. In the Fabric Type area, select one of the following fabric types: a) Layer 2 — Use the Layer 2 VLT fabric for workload migration over virtualized environments. See VLT and Selecting a Layer 2 VLT and Layer 3 with Resiliency (Routed VLT) Fabric Design. b) Layer 3 — Use the Layer 3 distributed core for large fabric deployments.
PAGE 71
5. Click the deployment topology filter icon on the top right of the screen to display deployment topology options. Only applicable filter options are displayed. For a description about the filtering options, refer to the Deployment Topology Options table. 6. Configure the filter options for the deployment topology and click the Apply button. 7. Click the Next button to go to the Fabric Customization screen.
PAGE 72
read-only screen. For information about the Advanced Options, see the section at Configuring Advanced Options. For information about tiers, see Deployment Topology. See also Deployment Topology Use Cases. 1. Navigate to the Network > Design Fabric > New Fabric > Deployment Topology > Fabric Customization screen. 2. From the Fabric Link Bandwidth pull-down menu, select the fabric link bandwidth for each access switch. 3. Click the Next button to go the Output screen.
PAGE 73
• Graphical Wiring Plan — Displays information about how the switches are connected graphically. • Network Topology — Displays information about how the switches are connected physically using a topology map. By default, no links are displayed in the fabric. Click on a switch to display the links in the fabric. When you select a switch, all the fabric interlinks are displayed. When you select a spine switch the links to the leaf switches are displayed.
PAGE 74
fabric (aggregation and access) are displayed. • 74 Tabular Wiring Plan — Displays information about how the switches are connected in the fabric design in a tabular format, as shown below. The tabular wiring plan contains a list of switches along with their names and ports which connect to the ports on the other switches in the fabric.
PAGE 75
Figure 34. Example: Visio Output Table 14. Tabular Wiring Plan Output Descriptions Field Name Description From Device (Switch) Displays the name of the device — from the side. From Port Displays the port number on the switch — from the side. To Device (Switch) Displays the name of the device— to the side. To Port Displays the port number on the device — to the side. Usage Status • • • Current — Represents the links based on your current needs.
PAGE 76
3. Click the Export link. The Generate Wiring Plan window displays. 4. Specify the following export options. a) PDF — Table, Data, Graphical Wiring Plan, or Both. b) Visio — Network Topology. 5. Click the Generate button. Fabric Design – Step 6: Summary The Summary screen displays a summary of your fabric design. To export the fabric design: 1. Click one of the following export options: – Export Wiring Plan – Export Summary – Export Design 2.
PAGE 77
3. In the Fabric XML file area, click the Browse button and locate the fabric XML design file (the XML design that you have exported from the AFM design wizard). 4. Click the Upload button. Editing and Expanding an Existing Fabric Design You can edit or expand an existing fabric from the Getting Started screen. After you initiated the pre-deployment configuration, you can only update the fabric description and port count for expanding uplinks and downlinks. 1.
PAGE 78
PAGE 79
Configuring and Deploying the Fabric 7 After you create a fabric at the Network > Design Fabric > New Fabric screen, you can configure and deploy the fabric at the Network > Fabric Name > Configure and Deploy screen. This screen deploys the configuration to the switches in the fabric. You can deploy auto-generated and custom configurations. This screen contains the following options: • • Deploy Fabric — Prepares the fabric for deployment and deploys the fabric.
PAGE 80
Pre-deployment Configuration Required Indicates that not all required Pre-deployment Configuration information was provided. Error Indicates that an error occurred during file transfer (transfer of a minimum configuration file) to the FTP/TFTP server or an error occurred during automatic DHCP integration for the local DHCP server.
PAGE 81
Complete Not Started Incomplete. The system MAC and IP address are not configured for the switches. Not Started • • • • Complete Partial Complete / Not Started Complete–Partial complete indicates that at least 1 switch has its system MAC and IP address configured.
PAGE 82
• Delete Fabric Using the Pre-deployment Wizard Layer 2 VLT Fabric Pre-deployment To prepare the Layer 2 VLT fabric for deployment, complete the following tasks using the Pre-deployment Configuration wizard. 1. Protocol Configuration for a Layer 2 VLT fabric: Step 1 – Pre-deployment – Step 1a: Uplink Configuration – Pre-deployment – Step 1b: VLT VLAN Configuration – Pre-deployment – Step 1c: Port Channel Configuration – Pre-deployment – Step 1d: Downlink Port Configuration 2.
PAGE 83
– Pre-deployment – Step 1b: Uplink Configuration – Pre-deployment - Step 1c: VLT VLAN Configuration – Pre-deployment – Step 1d: Port Channel Configuration – Pre-deployment – Step 1e: Downlink Port Configuration 2. Pre-deployment – Step 2: Assign Switch Identities 3. Pre-deployment – Step 3 Management IP 4. Pre-deployment – Step 4: SNMP and CLI Credentials 5. Pre-deployment – Step 5: Software Images 6. Pre-deployment – Step 6 DHCP Integration 7.
PAGE 84
Pre-Deployment Flowchart NOTE: The pre-deployment flowchart does not list all the prerequisites. This flowchart does not include obtaining the fabric interlink and loop back IP address groups. For more information, see Prerequisites. Pre-Deployment Screens To provide the fabric the minimum configuration to the switches, use the following Pre-deployment screens. These screens automate the deployment process.
PAGE 85
• Fabric link Configuration — (for a Layer 3 or Layer 3 with Resiliency (Routed VLT) fabric. For a Layer 3 fabric, configures options for the spine and leaf to communicate in the fabric. For a Layer 3 with Resiliency (Routed VLT) fabric, the links that connect the core, access, and aggregation switches in the fabric. • Management IP — Specifies a management IP address to each switch.
PAGE 86
Figure 35. Layer 2 VLT Uplink Configuration To configure the uplink protocol for the edge port uplinks to the WAN: 1. Navigate to the Network > Fabric Name > Configure and Deploy screen. 2. From the Deploy Fabric pull-down menu, select the Pre-deployment Configuration option. 3. Navigate to the Uplink Configuration screen. 4. In the Protocol Settings, select a routing protocol (OSPF, IBGP, or eBGP) for the edge port uplinks. The Bandwidth and Port Count screen specifies the number of uplinks.
PAGE 87
Figure 36. VLT VLAN Configuration with VLAN and VRRP Configuration Figure 37. VLT VLAN Configuration without VLAN and VRRP Configuration Table 17. VLT VLAN Configuration Options VLAN Option Description Add VLAN Enter the VLAN ID. Add VLAN Range Automates VLAN creation and automatically populates IP addresses. Enter the following VLAN information: • • Starting VLAN ID — Enter the Starting VLAN ID. The range is 2 to 4094. Number of VLANs — Enter the Number of VLANs. • VLAN Increment.
PAGE 88
NOTE: You must check the VLAN and VRRP Configuration option to view this option. VLAN and VRRP Configuration Configures IP address with VRRP protocol. When the VLAN and VRRP Configuration option is selected the following fields are displayed. • • • Autofill VLAN IP (For VLAN and VRRP Configuration only) Primary IP Secondary IP Virtual IP Enter the starting subnet IP address/prefix for the range of selected VLANS. The IP addresses are automatically populated. Delete VLAN Removes selected VLAN row.
PAGE 89
4. In the VLAN ID field, enter the VLAN ID. 5. In the Primary IP address field, enter the primary IP address. 6. In the Secondary IP address field, enter the secondary IP address. 7. In the Virtual IP address field, enter the virtual IP address 8. Click the Next button to view the Port Channel Configuration screen. Pre-deployment – Step 1c: Port Channel Configuration (Layer 2) Use this screen to optionally add, edit, delete, and automatically populate the port channel configuration.
PAGE 90
To create port channels to increase bandwidth and redundancy: 1. Navigate to the Network > Fabric Name > Configure and Deploy screen. 2. From the Deploy Fabric pull-down menu, select the Pre-deployment Configuration option. 3. Navigate to the Port Channel Configuration screen. 4. From the Switch pull-down menu, select a switch to apply the port channel configuration. 5. Click the Add link to manually add a port channel or the Auto populate link to automatically populate the port channels.
PAGE 91
Enter one or more VLANs to associate with the port. Validation Criteria: The VLANs have to be from the Configured VLANs list and the Untagged VLAN field should be empty. Default: Untagged VLANs 1. Select from the list (click on the icon next to the field entry) 2. Select one or more VLANs to be associated with the port. Select a VLAN to associate with the port. Validation Criteria: Tagged VLAN field should be empty. Default: Table 20.
PAGE 92
Figure 38. Downlink Port Configuration for Layer 2 4. From the Switches pull-down menu, select an access switch. 5. In the Tagged VLANs, click on the icon next and enter one or more VLANs to be associated with the port. 6. When you are finished, click the Next button to go to the Assign Network Identities screen. Protocol Configuration — Layer 3 Distributed Core Fabric: Step 1 To configure the pre-deployment protocol configuration for a Layer 3 distributed core fabric, complete the following tasks.
PAGE 93
Important: The area ID for the interconnect link must not be the same as the area ID for the uplink. To configure the Fabric Link Configuration for a Layer 3 distributed core fabric: 1. 2. Navigate to the Network > Fabric Name > Configure and Deploy screen. From the Deploy Fabric pull-down menu, select the Pre-Deployment Configuration option. The Introduction screen displays. 3. Review the Introduction screen and gather the useful information to prepare your fabric for deployment. 4.
PAGE 94
Figure 39. Downlink Configuration for Layer 3 Distributed Core Fabric To configure the downlinks for a Layer 3 distributed core fabric: 1. Navigate to the Network > Fabric Name > Configure and Deploy screen. 2. From the Deploy Fabric pull-down menu, select the Pre-deployment Configuration option. 3. Navigate to the Downlink Configuration screen. 4. To have the leaves act as a ToR, select the Specify Leaf as ToR option. 5.
PAGE 95
3. Pre-deployment - Step 1c: VLT VLAN Configuration 4. Pre-deployment – Step 1d: Port Channel Configuration 5. Pre-deployment – Step 1e: Downlink Port Configuration Pre-deployment – Step 1a: Fabric link Configuration Before you begin, review the Using the Pre-Deployment Wizard and Pre-deployment Wizard: Introduction sections.
PAGE 96
4. In the Protocol Settings, select a routing protocol (OSPF, IBGP, or eBGP) for the edge port uplinks. The number of uplinks is specified in the Bandwidth and Port Count screen. AFM automatically populates the range of IP addresses that belong to the /30 subnet. a) For OSPF, for each specified uplink, enter the local IP address, remote neighbor IP address, and area ID. A valid area ID area is from 0 to 65535.
PAGE 97
Default: Primary IP Enter the primary IP address. The prefix is auto-populated. Validation Criteria for Primary IP: Valid IP Prefix Range: from 8 to 29 Default Primary IP: Default Prefix: 24 Secondary IP Enter the secondary IP address. The prefix is auto-populated. Address for Secondary IP: Valid IP address Prefix range: from 8 to 29 Default Secondary IP: Default Prefix: 24 VLT VLAN Configuration for Layer 3 with Resiliency (Routed VLT) Figure 40.
PAGE 98
Figure 41. VLT VLAN Configuration Without Using the Enable Layer 3 Protocol in Access Switches Option The following screen shot displays a VLT VLAN Configuration screen using the Enable Layer 3 protocol in Access Switches option. To have the topology for a Layer 3 with Resiliency (Routed VLT) support both access and aggregation devices, select the Enable Layer 3 protocol in Access Switches option. When you use this option, provide the network IP address range using the Add VLAN Range link.
PAGE 99
Figure 43. Adding VLANs and Enabling the Layer Protocol in Access Switches Option To configure a VLT VLAN for a Layer 3 with Resiliency (Routed VLT) topology: 1. Navigate to the Network > Fabric Name > Configure and Deploy screen. 2. From the Deploy Fabric pull-down menu, select the Pre-deployment Configuration option. 3. Navigate to the VLT VLAN Configuration screen. 4. Check the Enable Layer 3 Protocol in Access Switches option. 5. Click the Add VLAN link. The Add VLAN Window is displayed. 6.
PAGE 100
Figure 44. Advanced VLAN IP Configuration Option Pre-deployment – Step 1d: Port Channel Configuration (Layer 3 — Routed VLT) Use this screen to optionally add, edit, delete, and automatically populate the port channel configuration for Layer 3 with Resiliency (Routed VLT) fabric. Once you add a port channel configuration you can copy it. Table 22. Port Channel Configuration Options Field Name Description Add Enter port channel information and enable LACP.
PAGE 101
Figure 46. Port Channel Configuration Screen To create port channels to increase bandwidth and redundancy: 1. Navigate to the Network > Fabric Name > Configure and Deploy screen. 2. From the Deploy Fabric pull-down menu, select the Pre-deployment Configuration option. 3. Navigate to the Port Channel Configuration screen. 4. From the Switch pull-down menu, select a switch to apply the port channel configuration. 5.
PAGE 102
Figure 47. Downlink Port Configuration with VLAN Port Association Option Selected Figure 48. Downlink Port Configuration with Port_VLAN Association Option Selected Table 23. Downlink Port Field Descriptions Field Name Description Configured VLANs Displays list of VLANs specified in the VLT VLAN Configuration screen. Port Name Displays the port name. This a read only field. Tagged VLANs Manual Entry: Enter one or more VLANs to associate with the port.
PAGE 103
Default: Untagged VLANs 1. Select from the list (click on the icon next to the field entry) 2. Select one or more VLANs to be associated with the port. Select a VLAN to associate with the port from the drop down list. Validation Criteria: Tagged VLAN field should be empty. Default: Table 24. Layer 2 Downlink Port Options Option Description Auto-fill Tagged Port For selected VLANs, sequential tagging is applied to the available ports and the number of ports specified on a VLAN.
PAGE 104
Port Name Displays the port name. This a read only field. Tagged VLANs Manual Entry: Enter one or more VLANs to associate with the port. Validation Criteria: The VLANs have to be from the Configured VLANs list and the Untagged VLAN field should be empty. Default: Untagged VLANs 1. Select from the list (click on the icon next to the field entry) 2. Select one or more VLANs to be associated with the port. Select a VLAN to associate with the port.
PAGE 105
Figure 49. Downlink Port Configuration for Layer 2 4. From the Switches pull-down menu, select an access switch. 5. In the Tagged VLANs, click on the icon next and enter one or more VLANs to be associated with the port. 6. When you are finished, click the Next button to go to the Assign Network Identities screen. Pre-deployment – Step 2: Assign Switch Identities To assign the system MAC addresses to the switches in the fabric, use the Assign Switch Identities screen.
PAGE 106
8. Map the system MAC address, serial number, and service tag to each switch. 9. Click Next to the go to the Assign Management IP screen. Pre-Deployment – Step 3: Management IP To assign a management IP address to each switch in the fabric, use the Management IP 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.
PAGE 107
Pre-Deployment – Step 5: Software Images To specify which software images to stage for each type of switch in the fabric from a TFTP or FTP site, use the Software Images screen. The software image must be the same for each type of platform. Place the software image(s) for the switches on the TFTP or FTP site so that the switches can install the appropriate FTOS software image and configuration file from this site.
PAGE 108
With BMP, after a you install a switch, the switch searches the network for a DHCP server. The DHCP server provides the switch with a management IP address and the location of a TFTP or FTP file server. The file server maintains a configuration file and an approved version of FTOS for the Dell Networking S55, S60, S4810, S4820T, S6000, Z9000, and MXL Blade switches. The switch automatically configures itself by loading and installing an embedded FTOS image with the startup configuration file.
PAGE 109
Viewing the DHCP Configuration File NOTE: If you are using an IE browser with the Windows 7 OS, change your indexing options: 1. Navigate to the Control Panel->Indexing Options screen. 2. Click the Advanced button and then click on the File Types Tab. 3. In the Add new extension to list: field, enter “conf” as the extension file type and then click the Add button. 4. Click the OK button. To view the DHCP configuration file created for the fabric: 1.
PAGE 110
Attention: During initial deployment, the BMP process wait time to install the software onto the switches in the fabric is the following: • 10 minutes for a non-stack fabric • 20 minutes for stack fabric. To view a custom configuration file, navigate to the Network > Fabric Name> Configure and Deploy screen. From the CLI Configuration pull-down menu, select the Custom Configuration option. Use the following Deployment Status table to troubleshoot deployment issues. Table 28.
PAGE 111
Deploy screen by selecting the switch from the list and then click on the Deploy Selected link. 10 InProgress Verifying that the switch is eligible for the deploy process NA 11 InProgress Protocol transfer in progress... NA 12 InProgress Device cleanup task done, reload in progress... NA 13 InProgress Complete config upload in progress... NA 14 InProgress Smart script transfer Inprogress... NA 15 InProgress Custom config upload in progress...
PAGE 112
10. Select the Apply configuration changes to the switch option or the Overwrite entire configuration on the switch option. When you deploy a switch, the following options are available: – Apply configuration changes to the switch– Apply new configuration changes from the AFM Server to the switch. – Overwrite entire configuration on the switch – Overwrites the entire current configuration on the switch instead of applying only the changes to the current switch configuration.
PAGE 113
View the Auto-generated Configuration To view the AFM auto-generated configuration: 1. Navigate to the Network > Fabric Name > Configure and Deploy > Deploy Fabric > > Advanced Configuration > View Auto-Generated Configuration screen. 2. From the Deploy Fabric pull-down menu, select the Deploy and Validate option. 3. On the Deploy tab, click the Advanced Configuration link. 4.
PAGE 114
The Switch Specific Custom Configuration screen displays. Figure 50. Switch Specific Custom Configuration The Switch Specific Custom Configuration screen provides support to view the auto-generated configuration and switch-specific custom configuration that is applied to the individual switches in the fabric. Only the switches that are deployed are listed. 4. Enter the switch specific-custom configuration (FTOS CLI commands) in the Switch Specific Custom Configuration area. 5.
PAGE 115
Validation To verify that the discovered fabric matches the planned fabric and correct any errors, use the Validate screen . Mismatches are reported as errors and the corresponding alarms generate. If you fix the errors found during validation, to verify that all the issues were fixed according to the planned fabric, validate the fabric again. Validation Status Validation Sl. No Status Status Details Response Action 1 Required Validation Required NA 2 Complete Validation completed.
PAGE 116
4. 7 Error Switch is not Discovered Verify the switch connectivity from the AFM. 1. 2. 8 9 10 Error Error Error Configuration mismatch errors exists Custom Configuration errors exists Wiring Errors Exists Fix any errors. Navigate to the Network > Fabric Name > Switch Name > Troubleshoot screen. Click the Errors link. 3. Click on the Undiscovered Errors tab to view error details. 4. Fix any errors. Check for switch configuration mismatch errors: 1.
PAGE 117
1. Navigate to the Network > Fabric Name > Configure and Deploy screen. The Configure and Deploy screen displays. 2. In the Switch column, select the switches to validate. 3. Click the Validate Selected link. 4. Review the progress in the Status, Status Details, Response Actions, and Last Validated columns. 5. Correct any errors. 6. If you fix the errors found during validation, to verify that all the issues were fixed according to the planned fabric, validate the fabric again.
PAGE 118
• All the switches in the fabric • All the leafs in the fabric • All the spines in the fabric To add templates: 1. Navigate to the Network > Fabric > Configure and Deploy screen. 2. From the CLI Configuration pull-down, select the Associate Template option. The Templates screen displays. 3. Click the Add Template link. 4. In the Template Name field, specify a unique name for the template. 5. (Optional) In the Description field, enter a description of the template. 6.
PAGE 119
Copying Templates You can copy an existing template, modify it, and then apply it to fabric or switch. For information on how to edit a template, see Editing Templates. When you copy a template, AFM does not copy over any associations to the switches. For information about how to associate templates, see Associating Templates. To copy templates: 1. Navigate to the Network > Fabric > Configure and Deploy screen. 2. From the CLI Configuration pull-down, select the Manage Templates option.
PAGE 120
7. – Leafs — Associates the template to all the leaf switches. – Spines — Associates the template to all the spine switches. Click the Apply button. Editing Template Associations To edit a template association: 1. Navigate to the Network > Fabric > Configure and Deploy screen. 2. From the CLI Configuration pull-down menu, select the Associate Templates option. 3. Select the template to edit the association. 4. Click the Edit Association link. 5. Edit the association. 6. Click the OK button.
PAGE 121
Figure 51. Switch Specific Custom Configuration The Switch Specific Custom Configuration screen provides support to view the auto-generated configuration and switch-specific custom configuration that is applied to the individual switches in the fabric. Only the switches that are deployed are listed. 4. Enter the switch specific-custom configuration (FTOS CLI commands) in the Switch Specific Custom Configuration area. 5.
PAGE 122
To view custom configuration history: 1. Navigate to the Network > Fabric Name > Configure and Deploy screen. 2. From the CLI Configuration pull-down menu, select the View Custom Configuration History option. The Custom Configuration History displays.
PAGE 123
Viewing the Fabric 8 This section contains the following topics: • Dashboard • View Network Summary • View Fabric Summary • Switch Summary Related Links: Fabric Performance Management. Dashboard To view the fabric and system health, use Home > Dashboard screen as shown. Figure 52.
PAGE 124
Figure 53. Dashboard with Color Codes The Dashboard provides the following key performance information: • System — Provides a tabular listing of system health and fabrics being managed by the AFM and lists the corresponding alert count by severity. The Switch Health column displays the number of switches that are alert free and the total switches that are part of the fabric. • Average Port Bandwidth Utilization — Displays the average port bandwidth utilization for all fabrics managed by the AFM.
PAGE 125
Table 30. CPU Utilization Color Codes Color Range Description Green (Good) x < 70 % Represents normal CPU utilization. Yellow (Minor) x > = 70 % and x < 80% Represents low CPU utilization. Red (Critical) x > = 80 % Represents high CPU utilization. NOTE: When the color code is yellow or red, the AFM displays an alarm at the Network > Fabric Name > Switch Name > Alerts and Events > Current screen.
PAGE 126
Figure 54. Network Summary Tabular View Network Topology Graphical View The network topology contains fabric icons.
PAGE 127
• Enable Move: After enabling this option, you can move each fabric icon to a new location in the map. • Revert to Last Saved: Revert to fabric locations to last saved version. • Save Move: Save the location of the fabrics that were moved. • Popup menu: Right-click a fabric to display a menu that contains actions that can be applied to the fabric. The menu contains the fabric name and “Open” menu item, which opens the fabric view.
PAGE 128
• You can display additional performance statistics about a fabric using the Launch Active Link option by navigating to the Network > Fabric level > Tabular screen. From the Action pull-down menu, select the switch row and then click the Launch Active Link option. For information about how to configure the Active Link, navigate to the Administrative > Settings > Active link Settings screen.
PAGE 129
For information about how to configure the Active Link, navigate to the Administrative > Settings > Active Link Settings screen. • Show Tooltips — Displays information (fabric, switch name, model name, IP address, alarm status, and manage state) about a switch when you place the cursor over the switch. • Show All Links — Displays all the links between the spines and the leaves, aggregation and access, or aggregation, access, and core.
PAGE 130
PAGE 131
Troubleshooting 9 This section contains the following topics: • Ping, Traceroute, SSH, and Telnet • Validation Alarms • Deployment and Validation Errors • TFTP/FTP Error • Switch Deployment Status • Validating Connectivity to the ToR For more information about troubleshooting, see Ping, Traceroute, SSH, and Telnet.
PAGE 132
1. Navigate to the Network > Fabric Name > Switch Name > Troubleshoot screen. . 2. Click the SSH tab. 3. In the SSH Command field, enter the SSH command. 4. Click the Send Command button to display the SSH results. Telnet To issue a Telnet command on a switch: 1. Navigate to the Network > Fabric Name > Switch Name > Troubleshoot screen. 2. Click the Telnet tab. 3. In the Telnet Command field, enter the Telnet command. 4. Click the Send Command button to display the Telnet results.
PAGE 133
a. Navigate to the Network> Fabric Name > Configure and Deploy screen. b. From the Deploy Fabric pull-down menu, select the Pre-deployment Configuration option. c. 2. Validation failed because the switch has a model mismatch. 1. Navigate to the Assign Switch Identities screen and check the system MAC address mapping for the associated switches. Verify your change by validating the switch. a. Navigate to the Network> Fabric Name > Configure and Deploy screen. b.
PAGE 134
Validation failed because the switch has a configuration mismatch. 1. Navigate to the Network > Fabric Name > Configure and Deploy screen. 2. Click the Errors link. 3. Select the Configuration Mismatch tab. 4. Review the configuration mismatch and correct the configuration errors.
PAGE 135
Device cleanup task failed Complete configuration upload failed Smart script transfer failed Custom configuration upload failed Backup config failed 2. Restart the deployment of the switch from the Network > Fabric Name > Configure and Deploy by selecting the switch from the list and then click on the Deploy Selected link. 1. Verify the Telnet or SSH connectivity from the AFM. 2.
PAGE 136
Table 33. Configuration Errors Configuration Error Configuration Mismatch Recommended Action 1. On the Deployment and Validation Status screen, select the switch that you want to view. 2. Click the View Mismatch button. 3. Review the configuration mismatch and correct the configuration errors. 4. Restart validation of the switch from the Deploy and Validate screen by selecting the switch from the list and clicking the Start Validation button. Table 34.
PAGE 137
Partial Link a. Navigate to the Network > Fabric Name > Configure and Deploy. b. From the Deploy Fabric pull-down menu, select the Deploy and Validate option. c. Click the Validation tab and then select the switches to validate. d. Click the Deploy Selected link. 1. Verify that the switch is wired according to the wiring plan. 2. Verify the connectivity on the AFM from both of switches of the link. 3. Validate the switch. a. Navigate to the Network > Fabric Name > Configure and Deploy. b.
PAGE 138
Switch Model Mismatch System MAC Address Mismatch 2. If the pre-deployment configuration is updated, you might need to redeploy the switch. 3. Validate the switch. a. Navigate to the Network > Fabric Name > Configure and Deploy screen. b. From the Deploy Fabric pull-down menu, select the Deploy and Validate option. c. Click the Validation tab and then select the switches to validate. d. Click the Deploy Selected link. 1.
PAGE 139
CONFIG GENERATION IN PROGRESS Configuration File Generation In-progress No CONFIG GENERATION FAILED Configuration File Generation Failed Yes Information only. 1. Check the write permission for the AFM installation directory in the AFM server machine. 2. Verify that the disk space is not full in the AFM server. 3. Restart the deployment of the switch from the Network > Fabric Name > Configure and Deployscreen by selecting the switch from the list and then click on the Deploy Selected link.
PAGE 140
3. Verify that the system MAC address in the dhcpd.conf file matches the csv. file that contains the MAC addresses of the switches. 4. Verify that the min.cfg file is in the correct directory on the TFTP/FTP server. 5. Redeploy the switch from the Network > Fabric Name > Configure and Deploy screen by selecting the switch from the list and then click on the Deploy Selected link. NOTE: The switch is in BMP mode. MIN CONFIG UPLOAD COMPLETED Minimum Configuration Upload Successful No Information only.
PAGE 141
a. b. c. Navigate to the Network > Fabric Name > Configure and Deploy screen. From the Deploy Fabric pulldown menu, select the Deploy and Validate option. On the Deploy tab, check the switch to deploy and then click the Deploy Selected link. PROTOCOL CONFIG UPLOAD COMPLETED Protocol Configuration Upload Succesful No Information only. DEVICE DEPLOYMENT SUCCESS Switch Deployment Successful No Information only. UPLINK CONFIG GENERATED Uplink Configuration Generated No Information only.
PAGE 142
REDEPLOYMENT REQUIRED Re-deployment of the switch Yes is required Restart the deployment of the switch. NOTE: The switch is not in BMP mode. 1. Navigate to the Network > Fabric Name > Configure and Deploy screen. 2. From the Deploy Fabric pull-down menu, select the Deploy and Validate option. 3. On the Deploy tab, check the switch to deploy and then click the Deploy Selected link. Use the following table to diagnose AFM deployment tasks that have failed. Table 38.
PAGE 143
Smart script transfer failed Smart script transfer: Failed Verify Telnet/SSH connectivity and deploy again Wiring validation Unable to validate Wiring Verify SNMP connectivity Wiring Errors Exists Review error details in Errors screen Merge configuration changes Apply configuration changes: Failed Verify Telnet/SSH connectivity and deploy again Custom configuration upload Custom configuration upload: Failed Verify Telnet/SSH connectivity and deploy again Backup running configuration Backup co
PAGE 144
PAGE 145
Alerts and Events 10 This section contains the following topics: • Current — Active Alerts • Historical — Alerts and Events Current — Active Alerts To view active alerts at the network, fabric and switch levels, use the Current tab. To acknowledge an active alert, select the active alert and then click the Acknowledge button. To display more information about the active alert, select the active alert. The system displays more information about the alert at the bottom of the screen.
PAGE 146
Figure 56. Fabric Alerts • To filter active alerts at the switch level, navigate to the Network > Fabric Name > Switch Name > Alerts and Events screen. Figure 57. Switch Alerts 1. 2. Click the Current button. Click the filtering icon on the right of the screen. You can use the filter options, from date and to date. The filtering options display.
PAGE 147
3. In the Severity pull-down menu, select one of the following filtering criteria: a) b) c) d) e) f) g) h) i) All Critical Major Minor Cleared Warning Unknown Info Indeterminate 4. In the Source IP field, enter the source IP address. 5. In the Source Name field, enter the source name. 6. In the Description field, enter a description. 7. In the Ack (acknowledgement) pull-down menu, select one of the following: a) All b) Yes c) No 8. Click the Apply button.
PAGE 148
7. In the Ack (acknowledgement) pull-down menu, select one of the following: a) All b) Yes c) No 8. Click the Apply button. 9. If you want to export your results, click the Export link.
PAGE 149
Performance Management 11 You can monitor performance at the network, fabric, switch, and port level.
PAGE 150
Fabric Performance Management To monitor the following for all the switches in the fabric, use the Network > Fabric Name > Performance screen: • Bandwidth utilization • Top 25 port inbound usage • Top 25 port outbound usage • Top 10 highest CPU utilization • Top 10 high memory utilization Switch Performance Management To view historical and real-time data switch level performance, use the Network > Fabric Name > Switch Name > Performance screen .
PAGE 151
Port Performance Management To view a summary of historical and real-time data port performance: 1. Navigate to the Network > Fabric Name > Switch Name > Summary screen. Figure 58. Displaying Summary of Port Performance 2. Select a port and then click on the Performance tab to view port performance. 3. Click the Real-Time Data or Historical button. 4. Select one of the following View Type options to display port performance: Bar, Graphical, or Tabular. 5. Review the performance information.
PAGE 152
• Packets To display detailed historical and real-time data port level performance: 1. Navigate to the Network > Fabric Name > Switch Name > Summary screen. 2. Click the Performance tab at the bottom of the screen. Figure 59. Display Detailed Port Performance 3. In the upper right of the screen, select the format to view the data using the Graphical or Tabular options. 4. In the lower left of the screen near the Performance tab, select the Real-Time Data or Historical Data option.
PAGE 153
4. From the Polling Rate pull-down menu, select the polling rate. a) b) c) d) 15 Minutes (default) 30 Minutes 45 minutes 1 Hour 5. Check the fabric to collect data from. 6. Click the OK. Threshold Settings To configure the monitoring link bundle and Threshold Crossing Alert (TCA) between the spine switches and the leaf switches for a fabric, use the Jobs > Data Collections > Edit Threshold Settings screen. The Average Traffic Threshold option monitors the Layer 3 fabric link bundle.
PAGE 154
Figure 60. Example: TCA Exceeds the Threshold For information about how to view port performance, see Port Performance. Make sure that you select the Real-Time Data option. Reports This section contains the following topics: • Creating New Reports • Editing Reports • Running Reports • Deleting Reports • Duplicating Reports NOTE: To run a report, schedule the data collection to start the task. See Data Collection. Creating New Reports To create a new report: 1.
PAGE 155
6. Click Next. 7. In the Date/Time Range pull-down menu, select a date or time range using one of the following options. If you select the custom range, specify a start and end date. a) b) c) d) 30 days 7 days 24 hours Custom Range 8. Click Next. 9. In the Monitors field, select which monitors to use for the report: CpuUtilization (CPU utilizatizaton), MemUtilization (memory utilization), and then click the >> button. 10.
PAGE 156
4. In the Report Name field, enter the name of the report. 5. (Optional) In the Description field, enter a description. 6. Modify the report as needed. 7. Click the Next button to navigate to different parts of the report that you want to duplicate. 8. Click Finish. Deleting Reports To delete a report: 1. Navigate to the Network > Fabric Name > Reports screen. 2. Select the report to delete. 3. Click the Delete button. The Delete Confirmation window displays. 4. 156 Click Yes.
PAGE 157
Maintenance 12 This section contains the following topics: • Backing Up the Switch Configuration • Scheduling Switch Software Updates • Replacing a Switch • Updating the AFM Back Up Switch To schedule the number of days to keep switch backup files on the AFM, use the Back Up Switch screen. Use this screen to 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.
PAGE 158
1. Navigate to the Network > Fabric Name > Maintenance screen. 2. Click the Switch Backup button to display the switch backup options. 3. Select a backup switch configuration to delete. 4. Click the Delete link to delete the switch backup configuration. 5. Click the Yes button. Editing Description To edit a switch backup description: 1. Navigate to the Network > Fabric Name > Maintenance screen. 2. Click the Switch Backup button to display the switch backup options. 3.
PAGE 159
NOTE: You must replace the switch with the same type of switch. See Replacing a Switch. To decommission a switch: 1. Navigate to the Network > Fabric Name > Switch Name. 2. Click the Switch Replacement tab. The Switch Replacement Summary screen displays. 3. Click the Decommission Switch link. The Decommission Switch screen is displayed. 4. Review and follow the instructions on the Decommission screen. 5.
PAGE 160
7. Click the Next button. The DHCP screen is displayed. 8. Save the replacement switch DHCP configuration file. 9. Review the Summary screen and then click the Finish button. 10. Before you deploy the switch: a) If you are using a remote DHCP server, integrate the new DHCP file, which contains the system MAC address of the replacement switch and then restart the DHCP service. b) Rack your hardware according to the wiring plan. 11. Click the on the Deploy Switch link.
PAGE 161
Activating the AFM Standby Partition Navigate to the Administration > Update Server screen and then click the Activate Available Partition link.
PAGE 162
PAGE 163
Jobs 13 This section contains the following topics: • Displaying Job Results • Scheduling Jobs Displaying Job Results To display the status of your jobs, use the Job Results screen. 1. Navigate to the Jobs > Jobs Results screen. 2. In the upper right of the screen, click the filter icon to filter your job results. 3. In the Job Name field, enter the job name. 4. In the Status pull-down menu, select one of the following filtering options: – All – Success – Failure – In Progress 5.
PAGE 164
NOTE: You can only change the scheduled time. You cannot change the job name, image location, or switch. • Delete — Deletes a job. Select a job and then click the Delete link. • Enable — Enable the job or activate the schedule. • Disable — Disable the job or the schedule, without having to delete the job. Switch Backup To backup a switch running configuration and startup configuration files, use the Switch Backup screen. 1. Navigate to the Jobs > Scheduled Jobs screen. 2.
PAGE 165
– 2 Tier distributed core filtering options — All, Spine, and Leaves – 2 Tier VLT options — All, Aggregation and Access – 3 tier filtering options — All, Core, Aggregation and Access 7. Click the >> button to move the switches to update to the Selected area and the click the Next button. 8. In the Update Location area, if required, select the TFTP or FTP site for the software updates using the Edit TFTP or FTP settings link. 9.
PAGE 166
– Schedule job to start on — Specify a date and time to schedule the job. The Summary screen displays. 9. Review the settings and then click the Finish button. Scheduling Switch Software Updates The Update Software screen displays the summary of software for each switch in the fabric. To create a new schedule job for backup, software image upgrade and software image activation, use the Schedule Switch Software Update option.
PAGE 167
– 9. Schedule job to start on — Schedule the job at a later time. Specify the start date and time for the software update job. In the Summary screen, review the software update software settings and then click the Finish button. Activating Standby Partition Software To activate the software available in the standby partition of the switch as a scheduled job to occur at a later time or to run immediately, use the Schedule Activate Standby Partition option.
PAGE 168
* c. 2 Tier distributed core filtering options — All, Spine, and Leaves * 2 Tier VLT options — All, Aggregation and Access * 3 tier filtering options — All, Core, Aggregation and Access Click the >> button to move the selected switches to the Selected Switches area and then click the Next button. The Schedule screen displays. 7. 8. 168 In the Start area, select one of the following options: – Run Now — Run the job now. – Schedule job to start — Specify when to schedule job.
PAGE 169
Administration 14 This section contains the following topics: • Administrative Settings • Managing User Accounts • Managing User Sessions Administrative Settings To configure administrative settings, use the Administration > Settings screen: • Active Link Settings • CLI Credentials • Client Settings • Data Retention Settings • DHCP Server Settings • NTP Server Settings • SMTP Email • SNMP Configuration • Syslog IP Addresses • System Information • TFTP/FTP Settings NOTE: The AFM
PAGE 170
Important: By default, the web service is turned off in the OMNM server. To use the OMNM web service: 1. On the OMNM server go to the server installation directory. 2. Navigate to the installed.properties file at C:\ProgramFiles\Dell\OpenManage\Network Manager\owareapps \installprops\lib 3. Turn off the Application Server and Synergy Network Management server. 4. Add the following three lines in the installed.properties file: com.dorado.core.ws.disable=false com.dorado.core.ws.legacy.soap.
PAGE 171
• Navigate to the Network > Fabric > Graphical view. Right click the switch icon and then select the Launch Active Link link. • Navigate to the Network > Fabric > Tabular view. Under the Action menu list, select the switch row and then select the Launch Active Link link. The Active Link displays the selected switch view and display performance charts. • Navigate to the Network >Switch > Graphic view. Click the Launch Active Link link.
PAGE 172
2. In the Client Settings area, click Edit. 3. In the GUI Polling Interval (in Seconds) pull-down menu, select one of the following options. The default value is 60 seconds. – 15 Secs – 30 Secs – 60 Secs – 120 Secs 4. In the Pop-out Client Session pull-down menu, select the maximum number of browser windows (from 3 to 7) for each user’s session. The default value is 3. 5. Click OK. Data Retention Settings To configure the amount of time to retain performance history: 1.
PAGE 173
SMTP Email To configure SMTP email: 1. Navigate to the Administration Settings screen 2. In the Secure SMTP Email Settings area, click the Edit link. 3. In the Outgoing Mail Server field, 4. In the Server Port field, enter the port number of the email server. 5. In the User Name field, enter the user name. 6. In the To Email Address(es) , enter the mail addresses separated by comma " ; ". 7.
PAGE 174
TFTP/FTP Settings 1. Navigate to the Administration > Settings screen. 2. From the File Transfer Protocol pull-down menu, select one of the following options: 3. – TFTP (default) – FTP In the TFTP/FTP Settings area, select one of the following options: – Local — AFM provisioned as a TFTP/FTP server. NOTE: When you use the Local option, the TFTP or FTP server must be in the same subnet. – * If you select the local TFTP server option, the TFTP server uses the AFM management IP address.
PAGE 175
NOTE: The AFM root user name is “superuser” and password is “Superuser1”. The system comes with three pre-defined roles with the following permissions: Superuser • Views a summary of user accounts. • Adds, deletes, and edits users. • Locks and unlocks users. • Resets passwords. • Performs configuration changes. • Sets session timeout values. • Terminates AFM users’ sessions at the Administration > User Session screen. Administrator • Performs configuration changes.
PAGE 176
6. In the First Name field, enter the user’s first name. The first name can contain any characters. Length: 1 to 50 characters. 7. (Optional) In the Last Name field, enter the user’s last name. The last name can contain any characters. Length: 1 to 50 characters. 8. From the Role pull-down menu, select one of the following roles: Admin or User. For information about roles, see Managing User Accounts. 9. In the Sessions Allowed pull-down menu, specify the number sessions allowed for the user.
PAGE 177
5. In the Last Name, enter the user’s last name. 6. In the Password field, enter the user’s password. 7. In the Confirm Password field, enter the user’s password. 8. In the Sessions Allowed pull-down menu, specify the number sessions allowed for the user. 9. In the Session Timeout pull-down menu, specify one of the following timeout values: a) b) c) d) 15 minutes 30 minutes 45 minutes 60 minutes 10.
PAGE 178
6. Click OK. For more information about user accounts, see Managing User Accounts. Managing User Sessions To display activeAFM users and terminate users’ sessions, use the User Sessions screen. Only the Superuser can terminate a AFM user’s session. For more information about user accounts, see Managing User Accounts. This screen displays the following information: • Username • Session Login Time • Client IP Address • Current Session To terminate AFM users’ sessions: 1.
PAGE 179
from the perspective of the AFM and only the actions performed by AFM users on the switch are logged. 1. Navigate to the Administration > Audit Log screen. 2. Click the filter icon on the upper right of the screen to display the audit trail options. 3. Enter and select your filter criteria for the User Name field. For example, “superuser”. 4. From the Date From pull-down menu, select the beginning date and time of the operation. 5.