Home

Dell Active Fabric Manager Deployment Guide

1. 40 G Downlinks for Layer 2 or Layer 3 with Resiliency Routed VLT DL BW ULBW Type DL Port AVC Access FL Possible Topologies Range VLTi BWBA Capacity amp A Aggregation Access 40Gb 10Gb 60 870 2 40Gb 80 Gb 79000 79000 40Gb 10Gb 60 870 2 40Gb 80 Gb S6000 S6000 3 Tier Topologies for a 10 Gb or 40 Gb ToR mVLT Deployment Layer 2 or Layer 3 with Resiliency Routed VLT Use the following tables as guideline to select the appropriate 3 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 see Deployment Topology AVC Aggregation VLTi Capacity CVC Core VLTi Capacity BW Bandwidth DL Downlink DL BW Downlink Bandwidth FL BWB C amp A FL BW between Core amp Aggregation FL BWB A amp A Fabric Link Bandwidth between Aggregation amp Access UL BW Uplink Bandwidth 40 Table 7 3 Tier ToR mVLT 10 Gb Downlinks DL UL Type DL Port CVC AVC Possible Topologies BW BW Range i Capacity C amp A mun Aggregation 10 10 Stacking 2971 2 40 2 40 NA 80Gb 40Gb Z9000 or S4810 4810 Gb Gb 36288 Gb Gb S6000 10 10 Stacking 2971 2 40 2 40 NA 80Gb 40Gb Z9000 or S4810 4820 Gb Gb 36288 Gb Gb 6000 Stacking 2971 2 40 2 40 80 Gb 160 Z9000 or Z9000 or 4810 ab A 18816 Gb Gb Gb S6000 S6000 Stacking 2971 uu uu 80 Gb
2. 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 When you select an aggregation switch the links to the access switches are displayed Similarly when you select a leaf switch the links to the spine switches are displayed When you select the access switches the links to aggregation switches are displayed When you select the core switches the links to all the switches in the fabric aggregation and access are displayed View Wiring Plan Fabric Name southcore Network Topology EE Graphical wing L Graphical Tabular Display future switches links Topology Options Y 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 Wiring Plan FROM SPINE ee TO LEAF TO PORT LINK TYPE USAGE STATUS southzore Aggregatson 1 0 0 soutbeore Access 1 0 0 Fabric Link Designed soutbeore Aggregation 1 ky southcore Access 2 0 0 Fabric Link Designed southcore Aggregation 1 0 2 southcore Access 3 oo Fabric Link Designed
3. Deploy screen by selecting the switch from the list and then click on the Deploy Selected link InProgress Verifying that the switch is eligible for the deploy NA process E e a msteigen JN DEE ERC fs rors Jane V To deploy a fabric 1 Verify that the software images for the switches are installed on to the TFTP or FTP server 2 Verify that you have configured the correct TFTP or FTP address atthe Administration Settings screen Changing the TFTP server now does not correct the address unless you redo the pre deployment 3 Foraremote DHCP server only verify that the DHCP configuration file generated by the AFM for the switches in the fabric is integrated into the DHCP server This file enables the switch to connect to the DHCP server and download the correct configuration and boot 4 Restart the DHCP server that contains the generated DHCP file that you created in the DHCP Integration screen For information about DHCP integration see DHCP Integration For information about how to view the DHCP configuration file for a fabric see Viewing the DHCP Configuration File Navigate to the Network gt Fabric Name gt Configure and Deploy screen From the Deploy Fabric pull down menu select the Deploy and Validate option The Deploy and Validate screen displays On the Deploy tab select the switches that you want to deploy in the Switch Name column Power up the selected switches The s
4. Type 4 Small Distributed Core Fabric Use the Type 4 Small Distributed Core design when e You require a fabric interlink fabric links bandwidth between the spines and leaves of 10 Gb e The current and future planned uplinks and downlinks on the leaves for your core is less than or equal to 960 ports e The maximum port count for a Type 4 Small Distributed Core fabric with an OS ratio of 3 1 is 768 For an OS ratio of 5 1 the maximum port count is 896 e The leaves act as a switch or ToR leaf switch Within the ToR the downlink protocol can be either VLAN or VLAN and LAG 29 With a Type 4 Small Distributed Core fabric design the 4810 spines connect to the 4810 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 Type 4 Small Core Distributed Core Fabric Bde Boos up to 4 spines Layer 3 10 Gb leaf uplinks to WAN OSPF 10 Gb leaf E Layer 2 Figure 8 Type 4 Small Distributed Core Fabric Design Each S4810 leaf for the Type 4 Small Distributed Core design has the following e Sixteen 10 Gigabit of fabric interlink fabric links port capacity to the spine e Forty eight 10 Gig Ethernet downlinks e Sixty 10 Gig Ethernet ports for servers per node and WAN connectivity VLT Virtual link trunking VLT allows physical links between two chassis to appear as a single virtual link to the network core or other switche
5. conf s end View Configuration Combined Autogenerated and Custom Configuration View Save To Last committed configuration on the switch View Save To 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 Enter the switch specific custom configuration FTOS CLI commands in the Switch Specific Custom Configuration area Under the View Configuration heading click the View button next to the Preview the combined auto generated and custom configuration This option allows you to view the auto generated configuration global custom configuration and switch specific configuration The View Combined Configuration screen displays To view the last applied configuration or save it click the View button or Save To button next to the Last committed configuration on the switch area The AFM displays the timestamp for the last committed configuration on the switch Review the combined configuration and make any necessary changes Click the Save To button to save the combined auto generated and custom configuration Click the Close button Preview Combined Configuration To preview the combined configuration 1 2 3 4 114 Navigate to the Network gt Fabric Name gt Co
6. 155 Deleting Reports ere eei oU D eh dea dent ene ied in ERR AER bash cubdedte 156 12 Mantena ne E 157 EISE jit E E E E 157 Restoring a Switch Configuration ENEE 157 Deleting a Backup Confguraton EE 157 Stiler 158 Updating the Switeh SOftWare duech eerte irae eee et B atrio REM Te E eaa a eren Res deae 158 Replacing a Switch era EI 158 Step 1 Decommission a Switch 158 Step 2 Repl cing a SWE haaa S 159 Step Deploy SWIEO harte ee b ab tib reni nr e Rota A AEE certe EAE 160 Updating the AFM eat e eseu 160 Updating the AFM Server 160 Activating the AFM Standby Partgon esses essen nete treten nter nte tnter tene tent testen tnt 161 IE Ic RR STENIA TELIT I A ede Dl eit I ORO audet tede ra ecd needa Scheduling Jobs ero eter teet cer telae dde Hae eee Habet de Db ORI HER Dee ovo uen Switch Backup Switch Software Updates Switch Software Activation acer terere tantuin rti inr da seas re dort neon rnt seas cesuseeaienseaceasversecter Scheduling Switch Software Updates Activating Standby Partition Software Scheduling a Back Up Switch Configuration EE 167 14 Administration E Administrative Settings Active Link Settings ER Gredentialsssc ccrnu Em Client Settings Data Retention Settings DHGP Server Settings iiie ttn ti Ges tee nod tiere eae eun e dna dn De eene dust vean doa Ua neo dal NTP Server Settings iy SMP CIR SNMP Configuration
7. 20 Gb Aggregation and Access 20 Gb Maximum Available Downlink Ports 2970 Maximum Available Downlink Ports 2916 Acces Ewech CERIN oe ART rrea Ewech CERIN og CAROUXIT M Step 4o 7 Back Next Save and Exit Cancel Configure the filter options for the deployment topology and click the Apply button Click the Next button to go to the Fabric Customization screen Fabric Design Step 3 Fabric Customization To modify the fabric link bandwidth between the aggregation and access switches for 2 tier and 3 tier fabrics use the Fabric Customization screen This screen displays the switch names model and switch role spine leaf aggregation or access For a Layer 2 or Layer 2 with Resiliency Routed VLT deployment topology you can select S4810 or S4820T switches mixed node on the access side Pre requisites To use this feature you must first configure the Advance Configuration option Fabric Link between Aggregation and Access to the maximum bandwidth for each access switch for example 120 Gb at the Network Design Fabric New Fabric Deployment Topology screen If you do not configure this option the Fabric Customization screen will be a 7 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 gt Design Fabric gt New Fabric gt Depl
8. The Summary screen displays a summary of your fabric design To export the fabric design 1 oF WO DN Click one of the following export options Export Wiring Plan Export Summary Export Design Select a display format PDF Table Data Graphical Wiring Plan Both or Visio Click the Generate button Carefully review the design before you commit the changes Click Finish to commit your changes Next Steps After you have designed the fabric do the following to prepare it for deployment 1 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 a Make sure the software version is the same for each type of switch across the fabric b Download the software image for each type of Dell Networking switch c Stage the software images on the TFTP or FTP site Obtain a pool of management IP addresses from the lab or system administrator to use for the switches in the fabric Prepare the DHCP server so that the switches can be assigned a management IP address Download the comma separate values csv file that contains the switch system MAC address provided from Dell manufacturing if available If not available consult Dell customer support If you do not have this file record the system MAC addresses of the switches in the fabric so that you can then map associate the address to the appropriate switch b
9. When the role is a user or administrator only the current logged in user s account information displays e Add User Adds new user accounts You can have up to 50 user accounts but only one Superuser e Edit User Edits user accounts e Change Password Allows a user to change his or her password e Delete User Deletes one or more user accounts The system default user Superuser cannot be deleted e Unlock Unlocks a user who was locked out because he or she exceeded the maximum login attempts To unlock a user select the user and click the Unlock option e Default User During the installation process AFMprompts you to create a Superuser e Reset Default User Superuser Password Contact technical support if you need to reset the Superuser password e Password Rules Enforces special password rules for enhanced security The password must be a minimum of 6 characters and contain one capital letter and one number The password is masked when you enter it e Unsuccessful Login Limit Specifies the unsuccessful login limit for a user s account When the unsuccessful login limit is exceeded the lockout duration is applied e Lockout Duration Specifies the amount of time a user is locked out when he or she exceeds the unsuccessful login limit e Sessions Allowed Specifies the number of sessions a user is allowed e Session Timeout Specifies the session timeout values 174 K NOTE The AFM
10. e View Wiring Plan Displays the wiring plan in tabular network topology and graphical formats which can be exported Related Links e Pre deployment Configuration e Using the Pre deployment Configuration Wizard Fabric Deployment Summary Switch Configuration Phases and States Table 15 Switch Configuration Phases and States Complete Indicates that the design is complete for the switch K NOTE At switch level design Partial Complete is not tracked Partial Complete is only tracked at the fabric level 79 Pre deployment Required Indicates that not all required Pre deployment Configuration information was Configuration 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 K NOTE In a case of remote the DHCP server no errors are reported for the DHCP integration step because itis not an automated step from the AFM you are responsible for manually integrating the DHCP configuration Complete Indicates that Pre deployment Configuration information is complete for the switch Deployment Required Indicates that deployment was never initiated for the switch or the Deployment state was reset due to a Design Pre deployment Configuration change K NOTE Deployment can be initiated re initiated only if Pre deployment Configuration is in a Complete state
11. 2 Verify your change by validating the switch a Navigate to the Network gt Fabric Name gt Configure and Deploy screen b From the Deploy Fabric pull down menu select the Deploy and Validate option c Click on the Validation tab and the check the switch to validate d Click the Validate Selected link Validation failed because the switch has a model mismatch Verify that you have correctly mapped the system MAC address to the associated switches Navigate to the Network gt Fabric Name gt Configure and Deploy screen From the Deploy Fabric pull down menu select the Pre deployment Configuration option 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 Navigate to the Network gt Fabric Name gt Configure and Deploy screen From the Deploy Fabric pull down menu select the Deploy and Validate option Click on the Validation tab and the check the switch to validate Click the Validate Selected link Validation failed because the switch is in a disconnected The switch is not reachable Verify the reachability of the state switch Validation failed because Te 0 1 has a wiring mismatch eae as Reviewing the wiring plan Wire according to the wiring plan to fix the wiring mismatch Make sure that the ports on the switches have accurately mapped Validation failed because Te 0 1 has
12. 60 80 oblD When the schedule is created AFM creates a job ID With real time performance management at the port level a RED solid line appears on the threshold with the label Traffic Utilization Alert Threshold This indicates that TCA has exceeded the threshold When the alarm is cleared the RED solid line disappears 153 TCA Threshold Line Chart anon st Traffic Utilization Alert Threshold attic Uol of Tr TCA Threshold Bar Chart Q Lex Ugen on Mni 36 Lua x l T 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 e Creating New Reports e Editing Reports e Running Reports e Deleting Reports e Duplicating Reports E 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 Navigate to the Network gt Fabric Name gt Reports screen 2 Click the New Report button The Add Modify Reports screen displays In the Report Name field enter the name of the report 4 Optional In the Description field enter a description of the report then click Next In the Type and Output field a Select a report type Switch or Port b Select a report output format Tabular or Chart 154 Click Next In the
13. Default Prefix 24 VLT VLAN Configuration for Layer 3 with Resiliency Routed VLT Fabric Design Layer3core roduc bon v Depoyment Topology Fabric Type Liner 2 Layer 3 WV Layer with Resteecy Rated VLT b Advanced Options gt Deyioymen Type Saat sana SHA KA 6 ate kv 2 Revbency ALT v EEr EEP eegen mm Lg cre ep onm cor fatric Link Bandwidth Fabric Unk Bandwidth Fabre Aggregation and Access per stack 20 Gb Aggregstion and Access 20 Gb Agee Packers A cata Domin rb Fuels 797 Pann menn A vetiel c Overs desh Pan ir T9106 Testen Stacking ecabled imAccess Yes Resitiexy in Access swikhes Yes p D Figure 40 Layer 3 with Resiliency Routed VLT Deployment Topology The following screen shot displays a VLT VLAN Configuration screen without selecting the Enable Layer 3 protocol in Access Switches option By default the VLT VLAN screen for Layer 3 with Resiliency Routed VLT requires that you enter the primary and secondary IP address for the VLAN ID as show in the following screen shot 97 Predeployment Configuration Layer3core ntrodzctior v VLT VLAN Configuration Fabric Lik Configuratice v Enter the required inormation to configure vtan Uphrk Configuration v Enable Layer 2 Protocol in A e witch gt VLT VLAN Configuration AGE VUAN Edit VLAN AGS VLAN Pange zz P ls tep 4 of 12 Delete VL VLAN ID Primary IF AN 5 92 1 1 1
14. e Pre deployment Step 1d Downlink Port Configuration NOTE For pre deployment the Layer 2 VLT and Layer 3 Distributed Core fabrics use the same pre deployment configuration screens from step 2 through step 7 Pre deployment Step 1a Uplink Configuration VLT The Uplink Configuration page displays the port bandwidth and the number of specified ports read only fields entered on the Fabric Name and Type and Port Specification screens To configure the uplink protocol for the edge port uplinks to the WAN use the Uplink Configuration screen For information about uplinks see VLT Terminology K NOTE For OSPF the uplinks or interlinks must be in area 0 85 Predeployment Configuration eastcore Introduction v Uplink Configuration gt Uplink Configuration Port Bandwidth Configure protocol settings below Specified number of uplink ports Protocol Settings Area ID Loopback IP Address Range Prefix switch Name eastcore Ageregation 1 eastcore Aggregation 2 Step 2 of 11 Port NO 47 47 Local IP Prefix 92 1 1 2 92 1 1 5 de di 10 Gb OSPF iBGP epp o 91 1 1 2 Remote IP Prefix Area ID 92 1 1 1 so 92 1 1 6 5 Back Next Saveandexit 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 gt Fabric Name gt Configure and Deploy screen Navigate
15. select a switch or a set of switches 6 Inthe Tagged VLANS click on the icon next and enter one or more VLANs to be associated with the port 7 When you are finished click the Next button to go to the Assign Network Identities screen Pre deployment Step 1d Downlink Port Configuration Layer 2 VLT To add VLANs and associate ports on the different switches for a Layer 2 fabric use the Downlink Port Configuration screen Once that is done you can copy switch VLAN or port VLAN configurations You can be associate one or more tagged VLANs with a port and for untagged VLAN only one is allowed For information about Downlinks see VLT Terminology Table 25 Downlink Port Configuration Layer 2 Field Descriptions Configured VLANs Displays list of VLANs specified in the VLT VLAN Configuration screen 103 Port Name Displays the port name This a read onlyfield 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 lt Blank gt 1 Select from the list click on the icon next to the field entry Select one or more VLANs to be associated with the port Untagged VLANs Select a VLAN to associate with the port Validation Criteria Tagged VLAN field should be empty Default lt Blank gt Table 26 Layer 2 Downlink Port Options Auto fill Tagged Port For selected VLANs sequ
16. southcore Aggregation 1 0 3 southcore Access 4 0 0 Fabric Link Designed southcore Ageregaton 1 0 48 southcore Ageregation 2 0 48 VLTi Link Designed southcore Agereganon 1 0 52 southcore Ageregation 2 0 52 VLTi Link Designed southcore Aggregahon 2 on southcore Access 4 an Fabric Tank Designed southcoce Aggregathon 2 oi sauthcore Access 1 0 1 Fabric Link Designed southzoce Aggregation 2 0 2 southcore Access 2 0 1 Fabric Link Designed southcore Agereganon 2 0 3 southcore Access 3 0 1 Fabric Link Designed 74 Aggregation 1 Aggregation 2 2 Figure 34 Example Visio Output Table 14 Tabular Wiring Plan Output Descriptions Displays the port number on the device to the side Usage Status e Current Represents the links based on your current needs e Future Represents links based on the fabric s future needs Displays usage status current and future expansion To review and export the fabric wiring plan 1 Navigate to the Network gt Design Fabric gt New Fabric gt Output screen 2 Click on the type of wiring plan that you want to export Wiring Graphical or Wiring or Network Topology Graphical or Tabular format 75 je 5 Click the Export link The Generate Wiring Plan window displays Specify the following export options a PDF Table Data Graphical Wiring Plan or Both b Visio Network Topology Click the Generate button Fabric Design Step 6 Summary
17. t Oure n d py VLAN Tagged F Xy So d Autor Tagan Autofil UnT agge gt Dowrdnk Port Confepur abon E wean Urt ated Port PortChannet x O r amp E r amp amp r S CH r Eeer amp E enis tour y map Cot tz Back Next Sive and Exit cu Figure 47 Downlink Port Configuration with VLAN Port Association Option Selected Predeployment Configuration Layer3core Aroductier v Downtink Port Configuration a eg hue v e e A a D J v m eg fefc nye acce H r aver D I v e a y Ze A Tagged VLAM Untagged VLANs a RN EE RS Sj amp f a engene S f amp 5 mnevene amp sg bw SRL err i5 a Back Next Save and Bek Figure 48 Downlink Port Configuration with Port_VLAN Association Option Selected Table 23 Downlink Port Field Descriptions Configured VLANs Displays list of VLANs specified in the VLT VLAN Configuration screen Port Name Displays the port name This a read onlyfield 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 102 Default lt Blank gt 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 Untagged VLANs Select a VLAN to associate with the port from the drop down list Validation Criteria Tagged VLAN field should be empty Default lt Blank gt Table
18. the first syslog IP address entry is the AFM system IP address System Information 1 Navigate to the Administration Settings screen 2 From the System IP Address pull down menu select the IP address used to manage the AFM K NOTE If there are multiple Network Interface Card NIC adapter cards on the AFM select the IP address to manage the AFM 173 TFTP FTP Settings 1 Navigate to the Administration gt Settings screen 2 From the File Transfer Protocol pull down menu select one of the following options TFTP default FIP 3 Inthe TFTP FTP Settings area select one of the following options Local AFM provisioned as a TFTP FTP server E NOTE When you use the Local option the TFTP or FTP server must be in the same subnet Ifyou select the local TFTP server option the TFTP server uses the AFM management IP address Ifyou select the local FTP server option the FTP server uses the AFM management IP address Enter the AFM user name and password Remote External TFTP FTP server Ifyou select the FTP protocol and remote options enter the FTP server IPv4 address user name and password Ifyou select the TFTP protocol and remote options enter the TFTP IPv4 address Managing User Accounts To view and manage user accounts use the Administration gt User Accounts screen e User Accounts Summary View Displays a summary view of user accounts when the user s role is Superuser
19. you might need to redeploy the switch 3 Validate the switch a Navigate to the Network gt Fabric Name gt 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 itch Model Mismatch TE g Switeh Model Mismate Verify that the IP address to switch name mapping is correct in the pre deployment configuration If the pre deployment configuration is updated you might need to redeploy the switch Validate the switch Navigate to the Network gt Fabric Name gt Configure and Deploy From the Deploy Fabric pull down menu select the Deploy and Validate option Click the Validation tab and then select the switches to validate Click the Deploy Selected link e Address A Verify that the IP address to switch name mapping is correct in the pre deployment configuration If the pre deployment configuration is updated you might need to redeploy the switch Validate the switch Navigate to the Network gt Fabric Name gt Configure and Deploy screen From the Deploy Fabric pull down menu select the Deploy and Validate option Click the Validation tab and then select the switches to validate Click the Deploy Selected link Switch Deployment Status Errors Use the following table to troubleshoot switch deployment status errors Table 37 Switc
20. 24 MAOTE VLAN IF Back Next BEER 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 The IP addresses are assigned to all the access and aggregation switches Predeployment Configuration Layer3core troduction sw VLT VLAN Configuration Fabric Link at wi Erter the required Information to configure vir pirk Congr ation J a M Gage Layer 2 Protocol m Accets Switche Fo vix P Range Figure 42 Layer 3 with Resiliency Using the Enable Layer 3 Protocol in Access Switches Option gt VET VLAN Configuration AGS VUN CGR VAM AGO VIN Range had Next Save and The following screen shot displays the results after checking the Enable Layer Protocol in Access Switches option and adding VLANs for a Layer 3 with Resiliency Routed VLT fabric 98 Predeployment Configuration Layer3core AT VLAN Configuration Enter t e required Kerg 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
21. 24 Layer 2 Downlink Port Options Auto fill Tagged Port For selected VLANs sequential tagging is applied to the available ports and the number of ports specified on a VLAN Auto fill Untagged Port For selected VLANs untagging is applied Based on available ports only one port per VLAN is associated Note The number of Port VLAN Port option is disable on the Autofill Tagged Untagged Port screen Copy Switch VLAN Config Copies the VLAN association from the current switch to other switch es in the fabric Copy VLAN Port Config Copies the VLAN association from a selected port to other port s within a switch Port VLAN Association Maps the physical port to the VLAN ID For example maps 1 port to multiple VLANs VLAN Port Association Maps the VLAN ID to physical port interfaces For example maps 1 VLAN to multiple ports To configure downlink ports on the switches 1 Navigate to the Network gt Fabric Name gt Configure and Deploy screen From the Deploy Fabric pull down menu select the Pre deployment Configuration option Navigate to the Layer 3 with Resiliency Routed VLT Downlink Port Configuration screen Pow m Select one of the following options Port VLAN Association Maps the physical port to the VLAN ID For example maps 1 port to multiple VLANs VLAN Port Association Maps the VLAN ID to physical port interfaces For example maps 1 VLAN to multiple ports 5 Fromthe Switches pull down menu
22. 3 2 re rtr tek eb e tr EE ee or ete ie dE AE Syslog Server IP Addresses System InfafmatiOri c ccce recette i d ende Matsui Wane ede cibo orbe eade Ed Ru agi unm Managing User Accounts Lo Ain gas User tou D De A DNE EM IE LI ce LEN eir NEIE RUE 176 Editing a EE 176 Unlocking ECH ET 177 Changing deel 177 Manado U Or OES SONS a E TELE LLL 178 PA LOG A E ERU 178 Introduction 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 You can monitor performance at the network fabric switch and port level You can also display additional performance statistics through AFM using a Dell OpenManage Network Manager OMNM server It automates common network management operations and provides advanced network element discovery remote configuration management and system health monitoring to proactively alert network administrators to potential network problems OMNM provides SOAP based web services to allow 3rd parties to integrate with it AFM supports Dell Networking S4810 S4820T S55 S60 S6000 MXL blade and 29000 switches Problem Challenges to Build a Fabric in
23. 40 Basic 1225 2 40 2 40 NA 80 Gb 80Gb Z9000 or Z9000 or 4810 Gb Gb 21952 Gb Gb 6000 6000 10 40 Basic 1225 2 40 2 40 NA 80 Gb 80Gb Z9000 or Z9000 or 4820 Gb Gb 21952 Gb Gb 6000 6000 41 10 40 Resiliency 2809 2 40 2 40 2 40Gb 80Gb 20Gb 29000 or S4810 4810 36288 G S6000 Gb Gb b Gb 10 40 Resiliency 2809 2 40 2 40 2 40Gb 80Gb 20Gb 29000 or S4810 4820 Gb Gb 36288 Gb Gb 6000 10 40 Resiliency 1345 2 40 2 40 2 40Gb 80Gb 80Gb 29000 or 29000 or 4810 Gb Gb 18816 Gb Gb 6000 6000 10 40 Resiliency 1345 2 40 2 40 2 40Gb 80Gb 80Gb 29000 or Z9000 or 4820 Gb Gb 18816 Gb Gb 6000 6000 AVC Aggregation VLTi Capacity CVC Core VLTi Capacity BW Bandwidth DL Downlink DL BW Downlink Bandwidth FL BWB C amp A Fabric Link Bandwidth between Core and Aggregation Switches FL BWB A amp A Fabric Link Bandwidth between Aggregation and Access Switches UL BW Uplink Bandwidth Table 8 3 Tier ToR mVLT 40 Gb Downlinks Type DL Port CVC AVC Access FL Possible Topologies Range VLTi BWB S Capacity A amp A Core Aggregation b 10 Gb Basic 871 2 40 2 40 NA 80Gb 80Gb 29000 29000 29000 11760 Gb Gb 2 0Gb 80Gb Se000 se000 6000 G b 10Gb Resiliency 785 2 2 40 2 40Gb 80Gb 80Gb 29000 29000 29000 10976 G G b 10Gb Resiliency 785 2 2 2 40Gb 80Gb 80Gb S6000 S6000 6000 10976 G G b 40 Gb Basic 871 NA 8
24. Apply software update and reboot Click the Next button 8 Inthe Schedule screen select one of the following options and then click the Next button Run Now Run the switch software update immediately 166 Schedule job to start on Schedule the job at a later time Specify the start date and time for the software update job 9 Inthe 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 To active the software in the standby partition of the switch 1 Navigate to the Network gt Fabric Name gt Maintenance screen Click the Update Software button Click the Schedule Activate Standby Partition link In the Job Name field specify the name of the job Optional In the Description field enter a description of the job Click the Next button Too om P WwW Mm From the pull down menu select one of the following options 2Tier distributed core filtering options All Spine and Leaves 2Tier VLT options All Aggregation and Access 3tier filtering options All Core Aggregation and Access 8 Select that switches to have their standby partition activated and then click the gt gt to move them to the Selected area and then clic
25. 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 30 days b 7 days c 24 hours d Custom Range Click Next In the Monitors field select which monitors to use for the report CpuUtilization CPU utilizatizaton MemUtilization memory utilization and then click the button In the Query field to determine what nodes to include in the report for a fabric a Selectthe core to query from the first pull down menu b Selectthe type of switches from the 2nd pull down menu In the Available Nodes Ports area select the nodes to include in the report and then click the button In Summary screen review the report settings If you want to run the report now check the Run Report Now option Click the Finish button Editing Reports To edit a report 1 Navigate to the Network gt Fabric Name gt Reports screen Select the report to edit Click the Edit button The Add Modify Report screen displays Edit the report Click the Next button to navigate to different parts of the report In the Summary area review your changes Click Finish Running Reports Before you can run a report schedule the data collection to start the task For information on scheduling data collection see Data Collection To run a report 1 2 3 Navigate to the Network gt Fabric Name gt Reports screen Sele
26. Deployment Topology The AFM displays applicable deployment topologies based your datacenter workload requirements specified in the Fabric Name and Type and Bandwidth and Port Count screens By default AFM selects one of the topologies Click the 3 65 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 e Tier 1 Topology Contains 2 switches and a downlink and uplink configuration There are no fabric links Figure 27 VLT 1 Tier Topology Aggregation Layer For more information about the tier 1 topologies see Designing a Layer 2 VLT and Layer 3 with Resiliency Routed VLT Fabric e Tier 2 Topology Contains 2 layers of switches has fabric interlinks uplinks and downlinks Distributed Core spine and leaf or VLT aggregation and access For more information about tier 2 topologies see Designing a Layer 2 VLT and Layer 3 with Resiliency Routed VLT Fabric and Selecting a Layer 3 Distributed Core Fabric Design EE tom EET GREED Figure 28 Tier 2 VLT Topology Aggregation and Access Layer AN Ne KA S MN C SX ZA Figure 29 Tier 2 Distributed Core Topology Spine
27. ER ml es 291 a 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 Once you add a port channel configuration you can copy it Table 18 Layer 2 Port Channel Configuration Options Enter port channel information and enable LACP Auto Populate Enter port channel information to automatically assign port channels to switches in the fabric and enable LACP Number of Ports per Port Channel Start Port Channel ID Number of Port Channel Port Channel Increment Enable LACP optional Copy Switch Port Channel Copies over switch port channel configuration from another switch You first create a Configuration port channel configuration and then you can copy over to another switch Delete Deletes a selected port channel configuration a selected port channel Deletes a selected port channel configuration E port channel configuration 89 Predeployment Configuration eastcore Introduction v Port Channel Configuration Uptink Configuration Enter the required downlink port channel configuration VLT VLAN Configuration v z Switches eastcore Access 1 gt Port Channel Configuration L Add Edit Delete Auto Populate Copy Switch Port Channel Config Port Channel ID Ports Port Channel Capacity Port Channel Type No Port Channets Conf
28. Gb 10 Gb or 40 Gb are based on the options you have selected in the Fabric Name and Type screen The number of uplink ports downlink ports and bandwidth you enter are the major input parameters in the design phase 53 Fabric Design North_Core 54 Introduction v Fabric Name and Type v width and Port Cour Bandwidth and Port Count o Enter Bandwidth and Port Specifications Bandwidth Specification Uptink Bandwidth in Gb 10 el opi Downlink Bandwidth in 10 el gt Gb e qum Downini Downlink Number of edge ports required by the fabric Current Future Total Uptink Ports 2 0 Downlink Ports 2 o Step 3 of 7 Back Next Save and Exit Cancel To configure bandwidth and port count for the switches in the fabric 1 3 In the Bandwidth Specification a b Select the uplink bandwidth 10 Gb or 40 Gb using the Uplink Bandwidth pull down menu Select the downlink bandwidth 1 Gb 10 Gb or 40 Gb using the Downlink Bandwidth pull down menu When you select the 1 Gb Downlink Bandwidth option the AFM supports deployment topologies with the S55 and S60 switches on the access side When you select the 10 Gb Downlink Bandwidth option the AFM supports all the deployment topologies with the 84810 and S4820T switches on the access side When you select the 40 Gb Downlink Bandwidth option the AFM supports deployment topologies with the 29000 and S6000 switches on the access side In the Number of edg
29. In progress Indicates that deployment is in progress and also provides the latest percentage complete information Indicates that deployment error exists Complete Indicates that deployment was successful for the switch Validation Required Indicates that validation was never initiated for the switch or the Validation state was reset due to a Design Pre deployment Configuration Deployment change K NOTE Validation can be initiated only if deployment is in a Complete state In progress Indicates that deployment is in progress and provides the latest percentage complete information Indicates that one or more validation errors exist Complete Indicates that validation was successful for the switch Operations Allowed in Each Fabric State To determine which operations are allowed during the design pre deployment configuration deployment and validation states use the following table Table 16 Operations Allowed in Each Fabric State Design Pre Deploy Deployment State Validation State Operation Allowed State Configuration State Incomplete Not Started Not Started Not Started Edit Fabric Delete Fabric Complete Not Started Not Started Not Started View Wiring Plan Edit Fabric All fabric attributes Pre deployment Configuration Delete Fabric 80 Complete Complete Complete Complete Incomplete The Not Started system MAC and IP address are not configured for the switches Partial Complete Not Star
30. Layer 3 with Resiliency Routed VLT Layer 2 Layer 3 with Resiliency Routed VLT Layer 2 or Layer 3 with Resiliency Routed VLT Layer 2 or Layer 3 with Resiliency Routed VLT Layer 2 or Layer 3 with Resiliency Routed VLT Layer 2 or Layer 3 with Resiliency Routed VLT 80G 40Gb 2 40 2 40Gb 29000 Gb or 6000 160G 2 40 2 40Gb 29000 Gb 160G 2 40 2 40Gb S6000 Gb 160G 2 40 2 40Gb 79000 G G G 4810 or S4820T MXL b 160G Wi S6000 b 20Gb 2 40 2 40Gb z9000or 4810 or b S6000 4820T 20Gb 2 40 2 40Gb z9000 S4810or Gb S4820T S6000 2 40 2 40Gb z9000 Gb 8 2 40 2 40Gb Gb 80G 0G 6000 15 196 40Gb MXL intra Chassis resilienc y MXL intra Chassis resilienc y Layer 2 or Layer 3 with Resiliency Routed VLT Layer 2 or Layer 3 with Resiliency Routed VLT 80G 80G 2 40 2 40Gb 29000 Gb 2 40 2 40Gb S6000 Gb 29000 MXL 4 48 Designing the Fabric 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 gt Design Fabric gt 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 This Fabric Design Wizard allows
31. Navigate to the Management IP screen In the Default Gateway field enter the address of the default gateway for the management interface In the Management Route field enter the route and prefix of the management interface In the Start Management IP Address Prefix fields enter the starting management IP address and prefix Select the switches to assign a management IP address Click the Auto fill Selected Rows button The system automatically assigns a management IP address to all the selected switches in the fabric eo m ep Sr ZS fa M oL 9 Click Next to go to the Software Images screen Pre Deployment Step 4 SNMP and CLI Credentials Use this screen to configure SNMP and CLI credentials at the fabric level Configure SNMP so that the AFM can perform SNMP queries on the switches in the fabric The values you enter in the SNMP configuration are also used for configuring the switches during the build phase and for monitoring during the run phase The write community string is populated from the AFM global setting which is configure during installation To provision the fabric enter the FTOS CLI user s credentials and enable the configuration credential for all the switches in the fabric This option allows you to remotely make configuration changes to the switches in the fabric To configure SNMP and CLI credentials 1 Navigate to the Network gt Fabric Name gt Configure and Deploy screen 2 From the Deploy Fabric pull down m
32. Port Channel Configuration Screen To create port channels to increase bandwidth and redundancy Navigate to the Network gt Fabric Name gt Configure and Deploy screen From the Deploy Fabric pull down menu select the Pre deployment Configuration option Navigate to the Port Channel Configuration screen oP Fo b gt From the Switch pull down menu select a switch to apply the port channel configuration Fort Channel ype Next Save and Exi Click the Add link to manually add a port channel or the Auto populate link to automatically populate the port channels For more port channel configuration options refer to the Port Channel Options table above for more information 6 Click Next to go to the Downlink Port Configuration screen Pre deployment Step 1e Downlink Port Configuration Layer 3 Routed VLT 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 Downlink Port Configuration screen Once that is done you can copy switch VLAN or port VLAN configurations You can be associate one or more tagged VLANs with a port and for untagged VLAN only one is allowed For information about Downlinks see VLT Terminology 101 Predeployment Configuration Layer3core P nt roduc tion v Downlink Port Configuration x y v o E k a i Cr AN Arsociy a k ER Switches Layerdeorew z
33. Stacking Module ENG HN Figure 9 1 Gb ToR VLT Deployment II LI ad Important All the VLT aggregation switches must be same mode type for aggregation for example 4810 On the VLT access you must configure the same model type AVG Aggregation VLTi Capacity DL Downlink 35 DL BW Down Link Bandwidth FL BWB A amp A Fabric Link Bandwidth between Aggregation amp 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 2 Tier 1 Gb Downlinks DL ULBW Type DL Port AVG Access FL Possible Topologies BW Range VLTi BWBA Capacity amp A Core Aggregation 1Gb 10Gb Stacking 1 2640 2 40 Gb NA 40 Gb Bi or 24G 4810 1Gb 40Gb Si 249g 2 40Gb NA 40 Gb SE vem pe eme Fake am m sm e Use the following table as guideline to select the appropriate 3 Tier Layer 2 VLT or Layer 3 with Additional Resiliency Routed VLT fabric design for a 1 Gb ToR VLT deployment AVG Aggregation VLTi Capacity CVG Core VLTi Capacity DL Downlink DL BW Downlink Bandwidth FL BWB C amp A FL BW between Core amp Aggregation FL BWB A amp A Fabric Link Bandwidth be
34. Type 3 Medium Core Type 4 Small Core e The number of current uplinks and downlinks for the leaves e The number of planned edge ports future uplinks and downlinks for the leaves e Whether you require non blocking line rate performance 24 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 Fixed fabric interlink bandwidth that is based on the fabric type 10 Gb or 40 Gb Important If you do not specify additional links in the fabric design for future expansion in the Bandwidth and Port Count screen you can only expand the downlinks on the existing fabric For information about how to expand a fabric see Editing and Expanding an Existing Fabric Design Gathering Useful Information for a Distributed Core To gather the following useful information for a Layer 3 distributed core fabric before you begin Obtain the comma separated values CSV file that contains the system media access control MAC addresses service tag and serial numbers for each switch provided from Dell manufacturing or manually enter this information Obtain th
35. VLT fabric for workload migration over virtualized environments When designing the Layer 2 VLT fabric consider the following e You can deploy up to 10 fabrics However the fabrics do not communicate with each other e Fora VLT fabric the AFM manages Dell Networking S4810 S4820T S55 S60 S6000 Z9000 and MXL Blade switches A CAUTION If you are already using a deployed switch you must reset the factory settings The switch must be in BMP mode For more information on BMP see DHCP Integration and the F70S Configuration Guide for the Dell Networking 4810 4820T S55 S60 S6000 29000 and MXL switches at https www force10networks com CSPortal20 KnowledgeBase Documentation aspx The number and type of switches in a VLT fabric are based on the following e The number of current uplinks minimum of 2 and downlinks for the access switches e The number of planned edge ports future uplinks and downlinks for the access switches e Whether the access switch needs to act as a switch or ToR Fabric interlink bandwidth the links between the aggregation and access switches e Downlinks which can be 1Gb 10Gb or 40 Gb e The fabric interlink bandwidth 10 Gb or 40 Gb is fixed and based on the fabric type E NOTE If you do not specify additional ports in the fabric design for future expansion in the Bandwidth and Port Count screen you can only expand the downlinks on the existing fabric For information on how to expand a
36. aggregation switches and external switch WAN supports the Layer 3 protocol OSPF iBGP or eBGP e The downlinks from the access 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 Select the VLAN and VRRP Configuration option to support redundancy between the access switch and ToR switches Network gt Basic non eui Summary Alerts and Events Performance Maintenance Configure and Deploy Home Basic non mx LN im Network v Action Y Topology Options t Q i se coche 2Tier Layer 2 VET Topology MXL_inter 2 Tier Layer 3 Resilency Routed VLT Topology Aggregaton Aggregation d Aggregation 2 The fabric link between Agucegation and Access are Access 1 runnipig Layer Protogh Administration Figure 13 Example 2 Tier Layer 2 VLT Fabric Use Case 3 2 tier Layer 3 Distributed Core When you select a 2 tier Layer 3 distributed core fabric e The fabric links between the spine and leaf switches supports the Layer 3 OSPF routing protocol e The uplinks between spine switch and external switch WAN supports the Layer 3 protocol OSPF iBGP or eBGP 57 e The downlinks from the access switches supports the Layer 2 protocol VLAN or VLAN and LAG Ifthe VLAN option is selected the downlinks connecting to server is configured to use the VLAN protocol Ifthe VLAN and L
37. and Leaf e Tier 3 Topology Layer 3 with Resiliency Routed VLT has 3 layers of switches fabric interlinks uplinks and downlinks For more information about the tier 3 topologies see Designing a Layer 2 VLT and Layer 3 with Resiliency Routed VLT Fabric ei TS ag Ee S ee ed s ke No7 J gt lt d n Ze e C n et an s Rd iN A ort x un JUN TN P sif Lasik dip LT CN EN CI crum CEP CEP Gln CEP crm CEP Figure 30 Tier 3 VLT Topology Core Aggregation Access Layer The following illustration and table describes the deployment types for a fabric 66 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 Fabric Design routed_VLT Introduction v Deployment Topology o Fabric Name and Type v Filter option icog Bandwidth and Port Count b Advanced Options gt Deployment Topology Deployment Type Filter 2 Tier Aggregation Access 10Gb Cable Type for Access Tie 54810 S4810 e d Mixed Node Stacking Restiency in Access Devices Stacked Non Stacked Clear Fabric Link Bandwidth Fabric Link Bandwidth Aggregation and Access per stack 20 Gb Aggregation and Access 20 Gb Maximum Available Downlink Ports 2970 Maximum Available Downlink Ports 2916 arra Suites CARTO oe EAR Arras amp witeh SARIN oe SARIIT x Step 40f7 Back Next Save and Exit Cancel
38. design a fabric 1 Fabric Name and Type Displays the fabric name type and description Enables Openstack Neutron Management and Blade Switch deployment 2 Bandwidth and Port Count Displays the number of edge port uplinks to the WAN connection and downlinks for example to servers or ToRs required for the initial deployment as well as for future expansion 3 Deployment Topology Displays the option to select between a Layer 2 or Layer 3 solution and a list of all applicable deployment topologies based on the workload requirements that you entered on the Bandwidth and Port Count and Fabric Name and Type screens This screen also displays Advanced options for configuring VLTi links and fabric links See also Deployment Topology Use Cases 4 Fabric Customization Displays switch names model and switch role aggregation or access and modifies the fabric link bandwidth for 2 tier and 3 tier fabrics For a Layer 2 deployment topology you can select 4810 or 4820T switches mixed node on the access side 5 Output Displays future switches and links and the fabric in the following formats graphical wiring plan tabular wiring plan graphical network topology tabular network topology 6 Summary Displays a summary of the fabric design You can also export the design in XML format and then import the XML design back into AFM Fabric Design Step 1 Fabric Name and Type To simplify and automate t
39. fabric from your DHCP network administrator or network operator If a remote DHCP server is not available AFM also provides a local DHCP The DHCP server must be in the same subnet where the switches are located After you power cycle the 20 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 Obtain IP addresses must be an even number for the uplink configuration from the ISP service The uplink port number range is based on whether a 10 Gb or 40 Gb bandwidth is selected For 10 Gb uplink bandwidth AFM supports 2 to 32 uplinks For 40 Gb uplink bandwidth AFM supports 2 to 8 uplinks Obtain IP addresses or VLAN ID for the downlink configuration for connecting to the server or ToR Gather protocol configuration for uplinks and downlinks Conventional Core Versus Distributed Core This section describes the differences between a conventional core and a distributed core Conventional Core A conventional core is a three tier network that is typically chassis based and is composed of the following Core The core layer routes traffic to and from the internet and th
40. into the Assign Switch Identities screen AFM generates a port MAC address from the pre deployment configuration not a chassis MAC address To integrate the DHCP configuration 1 Navigate to the Network gt Fabric Name gt Configure and Deploy screen 2 From the Deploy Fabric pull down menu select the Pre deployment Configuration option 3 Navigate to the DHCP Integration screen 4 Click Save to and then specify the location to save the generated DHCP configuration file You can also copy and paste the configuration into the DHCP server En Install the DHCP file onto the DHCP server before your deploy the fabric Click Next to go to the Summary screen Pre Deployment Step 7 Summary To review the pre deployment configuration use the Summary screen This screen displays the following information e Specified IP and protocol settings for the fabric uplink and downlink configuration e Software image information for each type of switch e Configuration file transfer status to the remote or local TFTP or FTP server To view the pre deployment configuration Navigate to the Network gt Fabric Name gt Configure and Deploy screen From the Deploy Fabric pull down menu select the Pre deployment Configuration option 1 2 3 Navigate to the Summary screen 4 Carefully review the pre deployment configuration before you commit it 5 Click the Finished button to commit your changes Next Steps 1 Verify that the
41. job to start Specify when to schedule job 8 Inthe Summary screen review your settings and then click the Finish button 168 14 Administration This section contains the following topics e Administrative Settings e Managing User Accounts e Managing User Sessions Administrative Settings To configure administrative settings use the Administration gt Settings screen e Active Link Settings e CLI Credentials e Client Settings e Data Retention Settings e DHCP Server Settings e NTP Server Settings e SMTP Email SNMP Configuration e Syslog IP Addresses e System Information e TFTP FTP Settings NOTE The 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 Active Link Settings To display additional performance statistics through the AFM using a Dell OpenManage Network Manager OMNM server use the Active Link Settings option OMNM monitors and manages Dell network devices It automates common network management operations and provides advanced network element discovery remote configuration management and system health monitoring to proactively alert network administrators to potential network problems OMNM provides SOAP based web services to allow 3rd parties to integrate with it AFM provides integration with the Dell OMNM web application as view only Wh
42. leaf switches for a fabric use the Jobs gt Data Collections gt Edit Threshold Settings screen The Average Traffic Threshold option monitors the Layer 3 fabric link bundle The TCA bandwidth option monitors Layer 2 and Layer 3 fabrics low bandwidth and high bandwidth In Traffic Utilization and Out Traffic Utilization When the average traffic low and high utilization thresholds are both exceeded AFM receives an alarm from the switch on the Alerts gt Active Alerts screen TCA Bandwidth Fabric Average Traffic Low Utilization High Utilization Name Threshold Threshold Threshold southcore 60 36 60 EN 80 el z 60 westcore a northcore Average Traffic Threshold Average Traffic Threshold configures the threshold value for a Layer 3 fabric The monitoring value is only configured on the fabric link between the spine and leaf switches Range 60 90 Low Utilization Low Utilization Threshold sets the value for TCA When the statistics is set below the Low utilization the TCA alarm clears The graphical performance monitoring removes a RED solid line with label as Traffic Utilization Alert Threshold from the chart Range 40 60 High Utilization High Utilization Threshold sets the highest value for TCA When the statistics is beyond the threshold the TCA alarm raises The behavior from graphical performance monitor is to draw a RED solid line with label as Traffic Utilization Alert Threshold on the chart Range
43. option 3 Navigate to the Uplink Configuration screen 95 4 Inthe Protocol Settings select a routing protocol OSPF IBGP or eBGP for the edge port uplinks The number of uplinks is specified in the Bandwidth and Port Count screen AFM automatically populates the range of IP addresses that belong to the 30 subnet a For OSPF for each specified uplink enter the local IP address remote neighbor IP address and area ID A valid area ID area is from 0 to 65535 b For iBGP for each specified uplink enter the local IP address remote neighbor IP address local AS number For the AS number enter a value from 1 to 4294967295 c For eBGP for each specified uplink enter the local IP remote neighbor IP address local AS number and remote AS number For the AS number enter a value from 1 to 4294967295 5 Click Next to go the Downlink Configuration screen Pre deployment Step 1c VLT VLAN Configuration for Layer 3 with Resiliency Fabric Routed VLT Use this screen to configure the VLT VLAN configuration for a Layer 3 with Resiliency Routed VLT fabric This section contains the following topics e VLT VLAN Layer 3 with Resiliency Routed VLT e Advanced VLAN IP Configuration Table 21 VLT VLAN Configuration Options for Layer 3 with Resiliency Routed VLT Fabirc Add VLAN Creates a VLAN row Add VLAN Range Automates VLAN creation and automatically populates IP addresses Enter the following VLAN information St
44. real time data monitoring from this screen K NOTE To view performance enable data collection at the Jobs gt Data Collections screen tarreary Performance 150 Port Performance Management To view a summary of historical and real time data port performance 1 Navigate to the Network gt Fabric Name gt Switch Name gt Summary screen Active Fabric Manager superuser Y Help core gt Spine 2 Summary Alerts and Events Performance Troubleshoot Replace Switch 9 southcore Spine 2 T Tabular C Healthy Minor Bag Stack Link Bl Disables Buden Dani rc D 9 warning southcore Spine2 Port 0 D New Window Geer Interval seconds 15 Traffic Utilization Errors Traffic Errors Throughput o Traffic In Kbps Figure 58 Displaying Summary of Port Performance Select a port and then click on the Performance tab to view port performance Click the Real Time Data or Historical button Select one of the following View Type options to display port performance Bar Graphical or Tabular Soe Ze qe Review the performance information Detailed Port Performance Management You can view detailed port level performance screen in a graphical chart or tabular format e Traffic utilization e Traffic errors e Throughput e Traffic in Kbps 151 e Packets To display detailed historical and real time data port level performance 1 Navigate to the Network gt Fabr
45. schedule jobs use the Jobs gt Scheduled Jobs screen You can also schedule jobs at the Network gt Fabric Name gt Maintenance screen e Add Job Create a new schedule job to do the following Switch Backup Backup a switch running configuration and startup configuration file Switch Software Update Creates a job to upgrade the switch software image Switch Software Activation Activate the software available in the standby partition of the switch as a schedule job to happen at later time or to run immediately e Run Now Starts a job immediately Select a job and then click the Run link e Edit Edit or modify an existing job schedule 163 K 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 gt Scheduled Jobs screen 2 From the Add pull down menu select the Switch Backup option The Switch Backup screen displays 3 Inthe Name field enter the name of the job 4 Optional In the Description field enter a description of the job 5 Clickthe Next button The Selected Switches screen dis
46. screen and gather the useful information to prepare your fabric for deployment 4 Click the Next button The Fabric Link Configuration screen displays 5 Inthe Start IP Address Range Prefix area enter the starting IP address and prefix The prefix must be from 8 to 29 6 Inthe Loopback IP Address Range Prefix area enter the loopback address range and prefix The prefix must be from 8 to 26 7 Inthe Area ID field use the default setting of 0 or enter the area ID The area ID is a value from 0 and 65535 The uplinks or interlinks must be in area 0 for OSPF Pre deployment Step 1b Uplink Configuration The Uplink Configuration screen for a Layer 3 and Layer 3 with Resiliency Routed VLT fabric displays the port bandwidth and the number of specified ports read only fields entered on the Bandwidth and Port Count screen To configure the uplink protocol for the edge port uplinks to the WAN use the Uplink Configuration screen For information about for a uplinks for a Layer 3 distributed core fabric see Distributed Core Terminology NOTE When the Open Shortest Path First OSPF is selected for both uplinks and interlinks one of uplinks or interlinks must be in area 0 To configure the uplink protocol for the edge port uplinks to the WAN for a Layer 3 distributed core fabric 1 Navigate to the Network gt Fabric Name gt Configure and Deploy screen 2 From the Deploy Fabric pull down menu select the Pre deployment Configuration
47. the Data Center e How do you design the fabric e What kind of switch do you buy e Who is going to use Visio to manually document the fabric that is manually document which switch ports connect to another switch e Who is going to draw the cables e How will ensure that this fabric design is accurate Whois going to update the fabric design as change it or expand it e Whois going to configure every switch in the fabric and what kind of errors can happen because this is manually performed e How dol keep track of software versions on each switch e Whois going to validate every switch in the fabric to verify that they have the correct version of software and configuration and that the switches are physically connected to the right switches Solution Active Fabric Manager Automated Fabric Design Automated Configuration Automated Deployment Automated Validation Design Templates NoCLIcommands Automatically deploys dme sino Deest Capacity Planner Noneecto manually each switch inthe fabric ties x Automated fabric expansion configure each switch based on the design de Auto documentation PDF Automatically configures Drawsfabrictopology every switch in the fabric Drawstable of switch port connections 2 About AFM 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 dist
48. the count of switches successfully deployment versus the count of total switches per design the based current port count doesn t include the future port count Indicates that deployment error s exist for one or more switches Partial Indicates that Deployment was successfully completed for one or more switches Complete but not for all switches per design It provides information about number of switches successfully deployed versus the number of total switches in the design E NOTE Deployment on any of the switches is not in progress while in this state Complete Indicates that deployment was successful for the switch Validation Indicates that the validation state for all switches is in state Required In progress Indicates that validation is In progress progress bar to be displayed in UI on one or more switches It provides information about count of switches successfully validated vs count of total switches per design based current port count doesn t include future port count Indicates that validation error s exist for one or more switches Partial Indicates that validation was successfully completed for one or more switches Complete but not all switches per design It provides information about the count of switches successfully validated versus the count of total switches per design K NOTE Validation of any of the switches is not in progress during this state Complete Indicates that validation was successf
49. topology 1 Navigate to the Network gt Fabric Name gt 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 Checkthe Enable Layer 3 Protocol in Access Switches option 5 Clickthe Add VLAN link The Add VLAN Window is displayed 6 Click the Add VLAN Range link and then specify the VLAN range to assign the IP addresses to the switches for the Layer 3 with Resiliency Routed VLT fabric 7 Clickthe Next button to view the Port Channel Configuration screen Advanced VLAN IP Configuration After completing the pre deployment process you can later modify the VLT VLAN configuration for Layer 3 with Resiliency Routed VLT topology using the Advanced VLAN IP Configuration option at the Network Fabric Switch Configure and Deploy screen 99 Active Fabric Manager Network LayerJcore Summary Alerts and Events Performance Maintenance Configure and Deploy LEES Fabric Deployment Summary ki Network v Deploy Fabric v Errors CLI Configuration v View Wiring Plan RE Switch Switch Type sae rad HERES De Layer2core Layer3core Aggregation 1 Aggregation Complete Complete Re S4820TStkB96 Layer3core Aggregation 2 Aggregation Complete Complete Re d Layer3core Access 1 Access Complete Complete Re Layer3core Access 2 Access Complete Complete Re Layer3core Access 3 Access Comple
50. you begin review the Using the Pre Deployment Wizard and Pre deployment Wizard Introduction sections To configure the links that connect the leaves and spines for a Layer 3 distributed core fabric or the links that connect the core access and aggregation switches for a Layer 3 with Resiliency Routed VLT fabric using the OSPF routing protocol use the Fabric link Configuration screen The Port Bandwidth a read only field is automatically determined by the selected fabric type and fabric oversubscription ratio To automate the pre deployment process AFM automatically populates the starting IP address range prefix loop IP address prefix based on the fabric design and sets the area ID for OSPF to 0 Review these settings You can modify the IP address range and loopback address The start prefix for both types of addresses must be from 8 to 29 and the loopback prefix from 8 to 26 For information about how to configure a Layer 2 VLT Fabric Interlink Configuration see Pre deployment Step 1 VLT Fabric Interlink Configuration g 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 Navigate to the Network gt Fabric Name gt Configure and Deploy screen 2 Fromthe Deploy Fabric pull down menu select the Pre Deployment Configuration option The Introduction screen displays 3 Review the Introduction
51. you to perform the following tasks e Create a fabric Editing and Expanding an Existing Fabric e Deleting the Fabric e Import an Existing Fabric Design e Viewing the Wiring Diagram Display the status of the fabric design whether the design pre deployment deployment and validation has been successfully completed Display detailed information about the fabric Before you begin review the Getting Started section To design a fabric complete the following tasks using the Fabric Design Wizard Fabric Design Step 1 Fabric Name and Type Fabric Design Step 2 Bandwidth and Port Count Fabric Design Step 3 Deployment Topology Fabric Design Step 4 Fabric Customization Fabric Design Step 5 Output ea P Fa h gt Fabric Design Step 6 Summary NOTE After you finish designing the fabric prepare it for deployment For more information see Preparing the Fabric for Deployment Network Deployment Summary AFM allows you to design a fabric make changes to the pre deployment configuration deploy the fabric and validate the fabric designed by comparing it to a discovered fabric AFM provides up to date status during each phase of the fabric from design to validate AFM displays any pending steps required that you needed to ensure the fabric is fully functional for each fabric design Fabric Configuration Phases and States The following table describes the four fabric
52. 0 43 40 Gb BW Bandwidth DL Downlink 2 30 for all even numbers only 2 14 for all even numbers only 2 30 for all even numbers only Basic MXL intra Chassis resiliency MXL intra Chassis resiliency MXL intra Chassis resiliency MXL intra Chassis resiliency MXL inter Chassis resiliency MXL inter Chassis resiliency MXL inter Chassis resiliency Layer 2 Layer 3 with Resiliency Routed VLT Layer 2 Layer 3 with Resiliency Routed VLT Layer 2 Layer 3 with Resiliency Routed VLT Layer 2 Layer 3 with Resiliency Routed VLT Layer 2 Layer 3 with Resiliency Routed VLT Layer 2 Layer 3 with Resiliency Routed VLT Layer 2 Layer 3 with Resiliency Routed VLT Layer 2 Layer 3 with Resiliency Routed VLT Layer 2 Layer 3 with Resiliency Routed VLT Layer 3 with Resiliency Routed VLT Layer 3 with Resiliency Routed VLT Layer 3 with Resiliency Routed VLT 20 Gb 2 40 Gb NA NA 2 40 Gb A A A A c c c c c c c c c c c co FL BWB A amp A Fabric Link Bandwidth between Aggregation and Access 44 4810 or S4820T MXL 4810 or S4820T 29000 or S6000 Z9000 S6000 4810 or S4820T 4810 or S4820T 4810 or S4820T 4810 or S4820T 29000 or S6000 4810 or S4820T FL BWB C amp A Fabric Link Bandwidth between Core and Access UL
53. 0Gb 80Gb zeooo z9000 79000 11760 i 80Gb 80Gb seo00 s6000 S6000 2 and 3 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 see MXL Topologies for MXL Blade Deployment NOTE All the VLT aggregation switches must be same model type for example 84810 On the VLT access all the switches must be MXL blades See the tables above in this section for more information 42 10 Gb Blade Switch MXL VLT Deployment 10 Gb MXL Switch Deployment 40 Gb Uplinks 2to 8 2 to 10 chassis 40 Gb stack ports g M1000E MXL Access 4810 VLT Aggregation BW Bandwidth DL Downlink FL BWB A amp A Fabric Link Bandwidth between Aggregation and Access UL BW Uplink Bandwidth VLTi A BW VLTi Aggregation Bandwidth Table 9 MXL Blade 2 Tier Topologies for 10 GB MXL Blade Switch For Layer 2 and Layer 3 with Resiliency Routed VLT LL pL Lo LLL LL LL Pessiule Topologies ULBW Fabric Type Type Basic Layer 2 Layer 3 with Resiliency Routed VLT Basic Layer 2 Layer 3 with Resiliency Routed VLT Basic Layer 2 Layer 3 with Resiliency Routed VLT FL VITiA VLTi MXL BWBA amp BW Access Inter A chassis 20 Gb 80 Gb 80 Gb Aggregation 4810 or S4820T NA 29000 or MXL S6000 NA 29000 or MXL S600
54. 10Gb 40Gb Mixednode 105 2808 2 40 N 40Gb Na S4810 4810 or Stacking Gb S4820T 10Gb 40Gb Mixednode 105 1392 2 40 N 160Gb NA Zz9000 or s6000 4810 or Stacking Gb S4820T 10Gb 40Gb REN 40 Gb SES 4810 Gb 10Gb 40Gb Stacking 105 1392 160 Gb b oid S4810 Gb 10Gb 40Gb Basic 105 3224 ERN poop 4810 Gb A A A A A A A A A A 40Gb Basic 105 1624 79000 or S6000 4810 Gb 10Gb 40Gb Mixednode 105 3224 2 40 NA 20Gb NA s4810 4810 or Basic Gb S4820T 10 Gb ce q c 40Gb Mixed node 105 1624 2 40 NA 80G fna z9000or s6000 4810 or Basic Gb S4820T 10Gb 40Gb BEN EE a 20 Gb EE 4810 Gb 10Gb 40Gb ee ee ae ees 79000 or S6000 4810 Gb 10Gb 40Gb Mixednode 105 2808 2 40 2 40Gb 20Gb Na S4810 4810 or Resiliency Gb S4820T 39 10Gb 40Gb Mixed node 105 1344 2 40 2 40Gb 80G NA 1 Z9000 or S6000 S4810 or Resiliency Gb S4820T AVC Aggregation VLTi Capacity BW Bandwidth DL Downlink DL BW Downlink Bandwidth FL BWB A amp A Fabric Link Bandwidth between Aggregation amp 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 from the switches on the aggregation side For information about tiers see Deployment Topology Table 6 2 Tier ToR mVLT
55. AG option is selected the downlinks between the leafs and ToR is configured to use VLAN VRRP and LAG for redundancy Ston Dy Output Name an Type v dth and Port Count V Network Topology ELT Tabular Wiring ED Graphical fm Tabular ment Topology v Onptay future switches inks Topology Options Customization 2 Tier Layer 3 Distributed Core Topology n Spine 1 Spine Spine 3 Spine 4 Spine 5 Spine 6 Colne 7 Spine o o o o o o o _ V wm owe Te a o7 AO See SSS j T 9 RE o D o we Le o o Ll 8 as DEE e MEA ba And cs c Leaf 4 Leaf 5 Leaf 4 esf 7 Leaf 8 Leaf 5 Leaf 10 Leg Ai Figure 14 Example 2 tier Layer 3 Distributed Core Use Case 4 2 Tier Layer 3 Resiliency Routed VLT When you select a 2 tier Layer 3 with Resiliency Routed VLT fabric e The fabric links between the aggregation and access switches supports the Layer 3 protocol with OSPF in the VLAN interfaces e The uplinks between the aggregation switch and external switch WAN supports the Layer 3 protocol OSPF iBGP or eBGP e The downlinks from the access 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 In this example shown below a Layer 3 with Resiliency Routed VLT fabric Based on the deployment type option selected the different options to be configured in downlink at the access tie
56. Active Fabric Manager AFM Deployment Guide 2 0 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 AMD is a registered trademark and AMD Opteron AMD Phenom and AMD Sempron are trademarks of Advanced Micro Devices Inc Microsoft Windows Windows Server Internet Explorer MS DOS Windows Vista and Active Directory are either trademarks or registered trademarks of Microsoft Corporation in the United States and or other countries Red Hat and Red Hat Enterprise Linux are registered trademarks of Red Hat Inc in the United States and or other countries Novell and SUSE are registered trademarks of Novell Inc in the United States and other countries Oracle is a registered trademark of Oracle Corporation and or its affiliates Citrix Xen XenServer and XenMotion are either registered trademarks or trademarks of Citrix Systems Inc in the United States and or other countries VMware vMotion vCenter vCenter SRM and vSphere are registered trademarks or trademarks of VMware Inc in the United State
57. BW Down Link Bandwidth FL BWB A amp A Fabric Link Bandwidth between Aggregation amp 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 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 5 2 Tier ToR mVLT 10 G Downlinks DLBW UL BW Type DL Port AVC Access FL Possible Topologies Range VLTi BWBA Capacity amp A Core Aggregation Access 10 Gb Mixed node 111 2970 2 40 NA 40 Gb 4810 4810 or Stacking Gb S4820T 38 10Gb 10Gb Mixed node 111 1392 2 40 NA 160Gb NA 29000 or S6000 4810 or Stacking S4820T Gb 10 Gb psc um 4810 10Gb 10Gb Seer EE 160 Gb 4810 10Gb 10Gb pe em 4810 1 b b b 10 Gb 0 10Gb 10Gb Basic 111 1624 79000 or S6000 4810 G 10Gb 10Gb Mixednode 111 3410 2 40 20Gb NA s4810 4810 or Basic G S4820T 10 Gb 10Gb Mixed node 0 Basic 0 0 0 1 S x b b b 11 1624 4810 or G S4820T 10Gb 10Gb aac ol ieee 4810 1 b b b b x b 10Gb 10Gb Resiliency 111 1344 ERE 40 Gb 79000 or S6000 4810 Gb 10Gb 10Gb Mixednode 11 2916 2 40 2 40Gb 20Gb NA s4810 S4810 or Resiliency Gb S4820T 10Gb 10Gb Mixednode 111 1344 2 40 2 40Gb Jongen Na zeoooorseoo0 4810 or Resiliency Gb S4820T
58. BW Uplink Bandwidth VCBW VLTi Core Bandwidth Table 10 3 Tier Deployment Topologies for MXL Blade Switch for Layer 2 and Layer 3 with Resiliency Routed VLT EIL EE Possible Topologies UL Type Fabric Type FL FL VCBW VLTi Core Aggregation Access BW BWB Aggregat A amp A ion BW 10 Gb Basic Layer 2 or 20 Gb 2 40Gb Z9000 4810 or MXL Layer 3 or S4820T with Resiliency 6000 Routed VLT 40 Gb Basic Layer 2 or 2 40Gb Z9000 4810 or MXL Layer 3 or S6000 S4820T with Resiliency Routed VLT 10 Gb Basic Layer 2 or 2 40Gb Z9000 29000 MXL Layer 3 with Resiliency Routed VLT 10 Gb Basic Layer 2 or 2 40Gb S6000 S6000 MXL Layer 3 with Resiliency Routed VLT XL FI E 40 Gb Basic Layer 2 or 2 40Gb zZ9000 Z9000 Layer 3 with Resiliency Routed VLT 40 Gb Basic Layer 2 2 40Gb S6000 6000 Layer 3 with Resiliency Routed VLT 28 336 10 Gb Stack Layer 2 or 2 40Gb Z9000 4810 or M ing Layer 3 or S6000 94820T with Resiliency Routed VLT 45 P c ec c 28 336 40 Gb 46 Stack ing Stack ing Stack ing Stack ing Stack ing MXL intra Chassis resilienc y MXL intra Chassis resilienc y MXL intra Chassis resilienc y MXL intra Chassis resilienc y Layer 2 Layer 3 with Resiliency Routed VLT Layer 2 or Layer 3 with Resiliency Routed VLT Layer 2 Layer 3 with Resiliency Routed VLT Layer 2
59. Configuration amp Enter the VAT VLAN Configuratior w g A C VUAN beet Chaneet Configurar v Swatches Hi Port Kame Tagged VLAM Untapped VLANs Coste rere Ki i A engai rarer E E i Test themat 014 E g g Tenigabit t theenet in ay Teevangabetttremet 0 6 S f CH Erene 8 f E eraot e 5 5 ie Back Nest Seve and Exit Conca EEE ees Figure 49 Downlink Port Configuration for Layer 2 4 From the Switches pull down menu select an access switch 5 Inthe 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 a Important Make sure you associate the switches with the correct system MAC address otherwise your wiring plan will be wrong The following is a sample CVS file Table 27 Sample CSV Format HADL134J20193 Ip 759 0096 02 REV F 00 01 E8 8B 15 77 9RGZTS2 NOTE Before you begin obtain the CSV file that contains the system MAC addresses service tag and serials numbers for each switch provided from Dell manufacturing or manually enter this information To assign switch identities 1 Locate the CSV file that contains the system MAC addresses serial numbers and service tags for the switches in the fabric Contact your D
60. CteitLeaf 1 Deployment error found Ceploy Failed v Major 10 16 148 44 DCteit Lea 4 Deployment erroe found Ceploy Failed y Major 10 14 148 4 DCteitLeaf 8 Deployment error found Ceploy Failed Adminisqade 3 feels found Diplayieg 1 20 Figure 55 Network Alerts e To filter active alerts at the fabric level navigate to the Network gt Fabric Name gt Alerts and Events screen 145 Misteri 1 2 146 S Active Fabric Manager Network gt 550 101 Sumenary Aerts and Events Performance Maintenance Configure and Deploy Alerts and Events C 0 Network e Acknowledge Unacknowledge Clear Stack Replacem Severity Source P Address Source Name Description Ack Date and Time s V mjo 1016 143 152 t Aeren OSTATE Df Changed interface state to down Ma 0 0 No 4 25 2083 12 51 17 Aggregation 1 NV Mele 10 6 148 46 555tk8101 Access t Deployment error found Deploy Failed N 11 28 2093 O42057 Aggregation 2 4h Warning 10 16 148 152 5555tk8101 Access 1 Validation tallied because twitch unit 1 mac not found No 11 28 2013 03 55 09 Access 1 temis found Oholaying 1 3 Figure 56 Fabric Alerts To filter active alerts at the switch level navigate to the Network gt Fabric Name gt Switch Name gt Alerts and Events screen Active Fabric Manager Network tack Replacement gt Aggregation 2 Summary Alerts and Events Performance Troutheshoot Switch Replacement Alerts and Events H
61. DHCP configuration file that you created for the fabric is integrated into the DHCP server so that the switches are assigned a management IP address before you deploy the fabric 2 Power on the switches in the fabric when you have completed the pre deployment process After you power cycle the switches the switches use bare metal provisioning BMP ic Important If you are using a switch that has already been deployed you must reset its factory settings to use it in the fabric The switch must be in BMP mode For more information about BMP see DHCP Integration and refer to the Open Automation Guide at https www force10networks com CSPortal20 KnowledgeBase Documentation aspx Select the Open Automation heading 3 Navigate to the Network gt Fabric Name gt Configure and Deploy screen 4 From the Deploy Fabric pull down menu to deploy and validate the fabric select the Deploy and Validate option 108 Viewing the DHCP Configuration File K NOTE If you are using an IE browser with the Windows 7 OS change your indexing options 1 Navigate to the Control Panel gt Indexing Options screen Click the Advanced button and then click on the File Types Tab In the Add new extension to list field enter conf as the extension file type and then click the Add button Click the OK button oo m To view the DHCP configuration file created for the fabric 1 Navigate to the Network gt Fabric Name Configure and Deplo
62. Deploy screen The Configure and Deploy screen displays In the Switch column select the switches to validate Click the Validate Selected link Review the progress in the Status Status Details Response Actions and Last Validated columns Correct any errors on RM 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 Viewing Deployment and Validation Status To view the deployment and validation status of the fabric 1 Navigate to the Network gt Fabric Name gt Configure and Deploy screen 2 Select the fabric that you want to view 3 From the Deploy Fabric pull down menu select the Deploy and Validate option You can also view the status of the fabric deployment at the Network gt Fabric Name gt Configure and Deploy gt Errors screen Custom CLI Configuration This section contains the following topics e Managing Templates e Associating Templates e Viewing Custom Configuration History e Switch Specific Custom Configuration Managing Templates This section contains the following topics e Adding Templates Editing Templates e Deleting Templates e Copying Templates Adding Templates You can add create a CLI configuration template This is useful for applying a custom configuration to the following e Specific switches in a fabric e Allthe aggregation switches in the fabric e Alte access sw
63. 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 lt Blank gt 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 Untagged VLANs Select a VLAN to associate with the port Validation Criteria Tagged VLAN field should be empty Default lt Blank gt Table 20 Layer 2 Downlink Port Options Auto fill Tagged Port For selected VLANs sequential tagging is applied to the available ports and the number of ports specified on a VLAN Auto fill Untagged Port For selected VLANs untagging is applied Based on available ports only one port per VLAN is associated Note The number of Port VLAN Port option is disable on the Autofill Tagged Untagged Port screen Copy Switch VLAN Config Copies the VLAN association from the current switch to other switch es in the fabric Copy VLAN Port Config Copies the VLAN association from a selected port to other port s within a switch Port VIAN Association VIAN Association Port VIAN Association Maps the physical portto the VLAN ID For example maps 1 port to multiple VLANs Maps the physical port to the VLAN ID For example maps 1 portto multiple VLANs physical port to the VLAN ID For example maps 1 port to multiple VLANs VLAN Port Association Maps the VLAN ID to physical por
64. Gei Z9000 or Z9000 or 4820 Ge De 18816 6000 6000 Basic 3411 2 40 2 40 80Gb 20Gb Z9000 or S4810 4810 db A 41664 Gb Gb S6000 Basic 3411 2 40 2 40 80Gb 20Gb Z9000 or S4810 4820 a ab 41664 Gb Gb 6000 10 10 Basic 1625 2 40 2 40 NA 80 Gb 80Gb Z9000 or Z9000 or 4810 Gb Gb 21952 Gb Gb 6000 6000 10 10 Basic 1625 2 40 2 40 NA 80 Gb 80Gb Z9000 or Z9000 or 4820 Gb Gb 21952 Gb Gb 6000 6000 10 10 Resiliency 2917 2 40 2 40 2 40Gb 80Gb 20Gb 29000 or S4810 4810 Gb Gb 36288 Gb Gb 6000 10 10 Resiliency 2917 2 40 2 40 2 40Gb 80Gb 20Gb Z9000 or 84810 4820 Gb Gb 36288 Gb Gb 6000 10 10 Resiliency 1355 2 40 2 40 2 40 Gb 80Gb 80Gb 29000 or Z9000 or 4810 Gb Gb 18816 Gb Gb 6000 6000 10 10 Resiliency 1355 2 40 2 40 2 40Gb 80Gb 80Gb 29000 or Z9000 or 4820 Gb Gb 18816 Gb Gb 6000 6000 10 40 Stacking 2809 2 40 2 40 NA 80Gb 40Gb Z9000 or S4810 4810 Gb Gb 36288 Gb Gb S6000 10 40 Stacking 2809 2 40 2 40 NA 80Gb 40Gb Z9000 or S4810 4820 Gb Gb 36288 Gb Gb S6000 10 40 Stacking 1393 2 40 2 40 NA 80Gb 160 29000 or Z9000 or 4810 Gb Gb 18816 Gb Gb Gb S6000 S6000 10 40 Stacking 1393 2 40 2 40 NA 80Gb 160 29000 or Z9000 or 4820 Gb Gb 18816 Gb Gb Gb S6000 S6000 10 40 Basic 3225 2 40 2 40 NA 80Gb 20Gb Z9000 or S4810 4810 Gb Gb 41664 Gb Gb S6000 10 40 Basic 3225 2 40 2 40 NA 80Gb 20Gb Z9000 or S4810 4820 Gb Gb 41664 Gb Gb 6000 10
65. Name and Type Bandwidth and Port Count Ke Deployment Topology Fabric Type Layer 2 Layer 3 b Advanced Options Deployment Type Layer 3 with Rettiency Routed VLT 2 Tier Aggregation Access 4310 4810 Mixed Node Stacking Fabric Link Bandwidth Aggregation and Access per stack 20 Gb Maximum Available Downlink Ports 2970 Access Switch 4810 or 4820T Stacking enabled in Access Yes Step 4 of 7 Figure 16 Layer 3 with Resiliency Routed VLT with VLT option Ce 2 Ther Aggregation Access Fabric Link Bandwidth Aggregation and Access 20 Gb Maxdeum Available Downlink Ports 2916 Access Switch 4810 or S4820T Resiliency in Access switches Yes 60 Network gt VLT_non_MXL Summary Alerts and Events Performance Maintenance Configure and Deploy Fabric Deployment Summary Zi Network Deploy Fabric Errors CU Configuration View Wiring Plan Advanced VLAN IP Configuration MXL intra Switch Switch Type M onini gt MXL inter J Loading Data gt Basic non md 0 Item s found Displaying 0 0 Aggregabon 1 Aggregation 2 Switch Details Figure 17 Layer 3 with Resiliency Routed VLT with VLT option Advanced VLAN IP Configuration 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 troduction s Deployment Top
66. P 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 Obtain IP addresses must be an even number for the uplink configuration from the ISP service The uplink port number range is based on the whether a 10 Gb or 40 Gb bandwidth is selected Fora 10 Gb bandwidth AFM supports 2 to 32 uplinks Fora 40 Gb bandwidth AFM supports 2 to 8 uplinks Obtain IP addresses or VLAN ID for the downlink configuration for connecting to the server or ToR Gather protocol configuration for uplinks and downlinks Selecting a Layer 2 and Layer 3 with Resiliency Routed VLT Fabric Design For workload migration over virtualized environments use a Layer 2 VLT fabric design Use the Layer 3 with Resiliency Routed VLT fabric to extend equal cost multi pathing capabilities The AFM supports the following Layer 2 VLT and Layer with 3 with Resiliency Routed VLT fabric designs 1 Tier for 10 Gb and 40 Gb ToR for Layer 2 and Layer 3 Resiliency Routed VLT 2 Tier and 3 Tier Topologies for 1 Gb ToR VLT Deployment for Layer 2 and Layer 3 with Resiliency Routed VLT 10 Gb or 40 Gb Top of Rack Deployment mVLT 2 and 3 Tier 10 Gb ToR mVLT D
67. RP Configuration VLT VLAN Configuration Enter the required information to configure vlan VLAN and VRRP Configuration Add VLAN Edit VLAN Add VLAN Range Delete VLAN VLAN ID FI s 1 Item s found Displaying 1 1 Figure 37 VLT VLAN Configuration without VLAN and VRRP Configuration Table 17 VLT VLAN Configuration Options Add VLAN Enter the VLAN ID Add VLAN Range Automates VLAN creation and automatically populates IP addresses Enter the following VLAN information Starting VLAN ID Enter the Starting VLAN ID The range is 2 to 4094 Number of VLANs Enter the Number of VLANs VLAN Increment If you do not specify an increment the VLAN is incremented by 1 Start Subnet IP Address Prefix IP range to automatically populate VLAN IP addresses IP addresses include primary secondary peer VLAN and VRRP IP 87 K NOTE You must check the VLAN and VRRP Configuration option to view this option VLAN and VRRP Configures IP address with VRRP protocol When the VLAN and VRRP Configuration Configuration option is selected the following fields are displayed e Primary IP e Secondary IP e Virtual IP Autofill VLAN IP Enter the starting subnet IP address prefix for the range of selected VLANS The IP For VLAN and VRRP addresses are automatically populated Configuration only Delete VLAN Removes selected VLAN row Edit VLAN Change the VLAN ID or VLAN ID primary IP address secondary IP address VLAN ID Ent
68. Table 13 Deployment Topology Filter Options Over Subscription Ratio For the layer 3 deployment the following over subscription ratios are Layer 3 distributed core deployment available topology only 1 1 3 1 4 1 5 1 Resiliency in Access Devices Configures Virtual Router Redundancy Protocol VRRP on the downlink 10 Gb Cable Type for Access Tier This option is applicable only for the topologies in which 4810 and S4820T can be swapped with each other SFP e RJ 45 Stacked Non Stacked Selects stacking for the topologies that are applicable When you select stacking you can use VLTi High Stream Buffering high stream buffing The access layer uses S60 switches 67 e low latency The access layer uses S55 switches Resiliency Tn MXL Routed VLT e Intra chassis Within the chassis mVLT Inter chassis resiliency Across 2 chassis VLT This section contains the following topics e Optional Configuring Advanced Options e 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 When you configure the fabric link bandwidth between aggregation and access switches from the Enabled Link Bandwidth Customization option from the Deployment Topology screen the bandwidth selected is shared equally by 2 redundant links For example if you select a fabr
69. Tz Check the switch syslogs for a reload command failure Make any necessary fixes Restart the deployment of the switch from the Network gt Fabric Name gt 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 Information only Verify the connectivity to the TFTP server from switch Check the Validation Status column for errors and fix them Verify that the DHCP server is running Verify that the CFG file correctly has been placed on the TFTP FTP server and that you can ping it from the switch Redeploy the switch K NOTE The switch is not in BMP mode PROTOCOL CONFIG UPLOAD Protocol Configuration COMPLETED Upload Succesful UPLINK CONFIG GENERATED Uplink Configuration Generated a Navigate to the Network gt Fabric Name gt Configure and Deploy screen b From the Deploy Fabric pull down menu select the Deploy and Validate option c On the Deploy tab check the switch to deploy and then click the Deploy Selected link Information only Information only DEVICE DEPLOYMENT Switch Deployment Information only SUCCESS Successful UPLINK CONFIG UPLOAD IN Uplink Configuration Upload PROGRESS In Progress UPLINK CONFIG UPLOAD Uplink Configuration Upload ERROR Error Information only E Verify the connectivity between the AFM server and switch Check the Validation Status column for e
70. a missing link No connectivity is detected to the switch Check the cables Validation failed because only a partial link can be verified Check the connectivity of the link and the connectivity of for Te 0 1 the switch 133 Validation failed b th itch h figurati Viu CN D LL cee 1 Navigate to the Network gt Fabric Name gt Configure and Deploy screen 2 Clickthe Errors link 3 Select the Configuration Mismatch tab 4 Review the configuration mismatch and correct the configuration errors Deployment and Validation Errors This section contains the following topics e Pre deployment Errors e Deployment Errors e Validation Errors Pre deployment Errors Use the following table to troubleshoot pre deployment errors Error Details Recommended Action Failed to transfer minimum Verify the TFTP or FTP connectivity from the AFM For FTP verify configuration file via TFTP FTP the credentials and restart the DHCP Integration step using the Pre deployment Configuration wizard To restart the DHCP Integration Navigate to the Network gt Fabric Name gt Configure and Deploy screen From the Deploy Fabric pull down menu select the Pre deployment Configuration option Restart the DHCP Integration step Overwrite DHCP contents to local Verify the permission of the directory and disk space availability on the AFM DHCP server failed server verify the local DHCP server configuration and then re
71. abled in Access Yes Intrachassis within Chassis resibenc y Yes Figure 23 Example 3 Tier Layer 3 with Resiliency Routed VLT with VLT option Network gt VLT non MXL Summary Alerts and Events Performance Maintenance Configure and Deploy Fabric Deployment Summary 7 Network v Deploy Fabric v Errors COU Configuration v View Wiring Plan Advanced VLAN IP Configuration Mat stra Switch Switch Type eode E ask CAI J Loading Data gt Basic_non_mxl 0 Item s found Displaying 0 0 Aggregation 1 Aggregation 2 Switch Details Figure 24 3 Tier Layer 3 with Resiliency Routed VLT with VLT Option Advanced VLAN IP Configuration 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 wi Introduction v Deployment Topology Fabric Nane and Type fabric Type Layer 2 Bandwidth and Port Count Bowen SO v Deployment Type 3 Tier Core Aggregation Access 79000 4810 MXL Stac king crm nn nn d ki ld wo ow Fabric Link Bandwidth Aggregabon and Access per stack 20 Gb Core and Aggregation 80 Gb Maximum Supported Blades 472 Options Module Port No 4 Bandwidth 10 Gb Stacking enabled in Access Yes Figure 25 Example 3 Tier Layer 3 with Resiliency Routed VLT with Basic Option WV Layer 3 with Resiliency outed VLT 3 Twer Core Aggregation Acce
72. als Pre deployment Step 5 Software Images Pre deployment Step 6 DHCP Integration Mo 5 Boc oM Pre deployment Step 7 Summary Layer 3 with Resiliency Routed VLT 1 Protocol Configuration for Layer 3 fabric Step 1 Pre deployment Step 1a Fabric Link Configuration 82 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 Pre deployment Step 2 Assign Switch Identities Pre deployment Step 3 Management IP Pre deployment Step 4 SNMP and CLI Credentials Pre deployment Step 5 Software Images Pre deployment Step 6 DHCP Integration Mo om P wD Pre deployment Step 7 Summary Pre Deployment Configuration To prepare the fabric for deployment use the Pre deployment Configuration Wizard After you initiate the pre deployment configuration you can only update the fabric description and port count for expanding uplinks and downlinks Prerequisites Before you begin 1 Rack the equipment in the fabric NOTE Before racking the switches make sure that you have the csv file that contains the system MAC addresses for each switch in the fabric If you do not have this file record the system addresses before you rack the switches 2 Power off the switches in th
73. ancing and redundancy in the distributed core There are no uplinks on the spines Edge ports The uplinks and downlinks on the leaves Uplinks An edge port link on the first two leaves in the distributed core fabric that connects to the edge WAN which typically connects to an internet server provider ISP Downlinks An edge port link that connects the leaves to the data access layer for example servers or ToR elements K NOTE Specify an even number of uplinks The minimum number of uplinks is 2 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 ratio that you specify depends on the bandwidth throughput and edge port requirements The interlink over oversubscription ratio does not come off the edge port downlinks As you increase the fabric over subscription ratio The total number of ports for the downlinks increases The number of interconnect links from the leaves to the spines decreases The maximum number of available ports increases For non blocking line rate between the leaves and spines select the 1 1 fabric over subscription ratio This ratio is useful when you require a
74. and VLT simultaneously If both are enabled at the same time unexpected behavior occurs Multi domain VLT An multi domain VLT mVLT configuration allows two different VLT domains connected by a standard Link Aggregation Control protocol LACP LAG to form a loop free Layer 2 topology in the aggregation layer This configuration supports a maximum of 4 units increasing the number of available ports and allowing for dual redundancy of the VLT For more information about mVLT deployments see Selecting a Layer 2 VLT and Layer 3 with Resiliency Routed VLT Fabric Design VLT Terminology The following are key VLT terms Virtual link trunk VLT The combined port channel between an attached device and the VLT peer switches e VLT backup link The backup link monitors the health of VLT peer switches The backup link sends configurable periodic keep alive messages between VLT peer switches e VLT interconnect VLTi The link used to synchronize states between the VLT peer switches Both ends must be on 10 Gb or 40 Gb interfaces e VLT domain This domain includes both VLT peer devices the VLT interconnect and all of the port channels in the VLT connected to the attached devices It is also associated to the configuration mode that must be used to assign VLT global parameters e VLT peer device One of a pair of devices that are connected with the special port channel known as the VLT interconnect VLTi VLT pee
75. and system health use Home gt Dashboard screen as shown Getting Started Dashboard Dashboard E System Application and Server Alerts southcore Average Port Bandwidth Utilization Fabric Inbound There are no items available Top Port Inbound usage Fabric Switch Unit There are no items available Top Port Outbound usage Fabric Switch Unit There are no items available Highest CPU Utilization Fabric Switch Last Value There are no items available Figure 52 Dashboard Alerts Health 0 v 0 A 35 wa A 21 k4 0 4 Outbound Port Inbound Port Outbound Highest Memory Utilization Fabric Switch Last Value There are no items available 123 Average Port Bandwidth Uniization Top Port inbound uiage Figure 53 Dashboard with Color Codes The 124 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 Top Port Usage Displays the top 10 ports usage for all fabrics with following columns Fabric Switch Port number Inbound number with color code bar Outbound number
76. arting VLAN ID Enter the Starting VLAN ID Range 2 to 4094 Number of VLANs Enter the Number of VLANs VLAN Increment If you do not specify an increment the VLAN is incremented by 1 Start Subnet IP Address Prefix IP range to automatically populate VLAN IP addresses IP addresses include primary secondary peer VLAN and VRRP IP K ids You must check the VLAN and VRRP Configuration option to view this option VLAN and VRRP Configures IP address with VRRP protocol When the VLAN and VRRP Configuration Configuration for a Layer3 option is selected the following fields are displayed fabric for Resiliency Routed VLT e Primary IP e Secondary IP e Virtual IP Autofill VLAN IP Enter the starting subnet IP address prefix for the range of selected VLANS The IP For Enable Layer 3 Protocol addresses are automatically populated in Access Switches option only Delete VLAN Removes selected VLAN row Edit VLAN Edit VLAN ID primary IP address and secondary IP address VLAN ID Enter the VLAN ID Range 2 to 4094 96 Default lt Blank gt 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 lt Blank gt 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 lt Blank gt
77. ation anc Core and Aggregation 80 Gb Core and Aggrei Maximum Supported Blades 672 Maximum Suppor Optional Module Optional Module Port No 41 Bandwidth 10 Gb Port No 41 Ban Stacking enabled in Access Yes Intrachassis witt Figure 22 3 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 When you complete the pre deployment configuration the Advanced VLAN IP Configuration option is available atthe Configure and Deploy summary screen 63 64 Fabric Name and Type v 2 Fabric Type Layer 2 V Layer 3 with Restiency Routed VLT Bandwidth and Port Count v En v Deployment Type Lier Core Aggregation Access Tier Core Aggregation Access 79000 4810 MXL 29000 4810 RL Stacking Resiliency VLT Em amp cn co cnr cmp coe coz an nn nn nmn ld Ee H Bi JL Ww au Fabric Link Bandwidth Fabric Link Bandwidth Aggregation and Access per stack 20 Gb Aggregation and Access 20 Gb Core and Aggregation 80 Gb Core and Aggregation 80 Gb Maximum Supported Blades 672 Maximum Supported Blades 672 Optional Module Optional Module Port No 41 Bandwidth 10 Gb Port No 41 Bandwidth 10 Gb Stacking en
78. ays all the links between the spines and the leaves aggregation and access or aggregation access and core e Enter switch name Enter the switch name and click the search icon to locate a switch in the fabric The switch name is case sensitive For additional information about the fabric select the following tabs Detail e Links e Hardware e VLT Domain Switch Summary To view the following switch summary information from a graphical view navigate to the Network gt Fabric Name gt Switch Name screen and then click the Summary tab Make sure that the Graphical button is selected in the upper right of the screen You can also view this information in a tabular view by selecting the Tabular button e Click ona port to display information about the state of the port e Click on the Port Legends arrow to display the port legends e Click on the Launch Active Link from the graphical or tabular view to display additional statistics about a switch through the AFM using a OMNM server For information about how to configure a element management service navigate to the Administrative gt Settings gt Active Link Settings screen e Status e Active Alerts e Speed e Manage State 129 130 Troubleshooting This section contains the following topics Ping Traceroute SSH and Telnet e Validation Alarms e Deployment and Validation Errors e TFTP FTP Error e Switch Deployment Status e Validating Conn
79. btain IP addresses must be an even number for the uplink configuration from the ISP service The uplink port number range is based on whether a 10 Gb or 40 Gb bandwidth is selected Fora 10 Gb bandwidth AFM supports 2 to 32 uplinks Fora 40 Gb bandwidth AFM supports 2 to 8 uplinks Obtain IP addresses for the downlink configuration for connecting to the server or ToR Obtain IP addresses for the fabric link configuration for the spine and leaf switches Gather protocol configuration for uplinks downlinks and fabric link configuration 25 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 e Type 1 Extra Large Core Fabric e Type 2 Large Distributed Core Fabric e 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 For more information about a Layer 3 distributed core see e Overview of a Distributed Core e Key Considerations for Designing a Distributed Core Fabric e Flowchart for Designing and Deploying a Fabric With a Layer 3 distributed core topology you select the Layer 3 option using the Design Wizard on the Deployment Topology screen For information about distributed core see Selecting a Distributed Core Design DL BW Down
80. ce status at the following screens 1 Administration gt Settings gt Active Link Settings Network gt Alerts and Events screen in the Description column Network gt Fabric gt Details oo M Network Switch Summary The Active Link feature is disabled when e The AFM cannot connect to Active Link server e The AFM cannot connect to Active Link web service e The selected switch is un manage by AFM e The Active Link server is not configured The topology view refreshes every 60 seconds default The refresh rate interval can be changed from the Administration Settings Client Settings GUI Polling screen The link status is refreshed every 60 seconds default You start the Active Link at the following levels e AFM UI provides Active Link server status and Active Link WEB Service status at a Administration gt Settings gt Active Link Settings screen b Network gt Fabric gt Details screen c Network gt Switch gt Summary screen By default the topology view and link status refreshes every 60 seconds To change the interval navigate to the Administration Settings screen The Active link is available at the following screens e Navigate to the Network gt Fabric gt Graphical view Under the Action menu list select the Launch Active Link option 170 Navigate to the Network gt Fabric gt Graphical view Right click the switch icon and then select the Launch Active Link link Navigate t
81. cess wait time to install the software onto the switches in the fabric is the following e 10 minutes for a non stack fabric e 20 minutes for stack fabric To view a custom configuration file navigate to the Network gt 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 Deployment Status Status Recommended Action vA vA Error Protocol transfer failed Verify TFTP FTP connectivity verify FTP credentials Error Device cleanup task failed From the AFM verify the switch connectivity using Telnet or SSH Restart the deployment of the switch from the Network gt Fabric Name gt Configure and Deploy screen by selecting the switch from the list and then click on the Deploy Selected link 2 3 5 Error Complete config upload failed _ Verify TFTP FTP or Telnet SSH connectivity For FTP verify credentials Restart the deployment of the switch from the Network gt Fabric Name gt Configure and Deploy screen by selecting the switch from the list and then click on the Deploy Selected link Error Custom config upload failed Verify the login and configuration commands on the switch Error Backup config failed 1 Verify Telnet or SSH connectivity from the AFM Restart the deployment of the switch from the Network gt Fabric Name gt Configure and 110
82. ct the report to run Click the Run button Duplicating Reports To duplicate a report 1 Navigate to the Network gt Fabric Name gt Reports screen Select a report to duplicate Click the Duplicate button The Duplicate screen displays 155 In the Report Name field enter the name of the report Optional In the Description field enter a description Modify the report as needed Click the Next button to navigate to different parts of the report that you want to duplicate Click Finish e oS Deleting Reports To delete a report 1 Navigate to the Network gt Fabric Name gt Reports screen Select the report to delete Click the Delete button The Delete Confirmation window displays 4 Click Yes 156 12 Maintenance 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 This screen has the following options Switch Backup Schedule a back up for a switch running configuration and startup configuration files to run now or schedule it for a later time For information ab
83. d Mode Stocking Mixed Hode Revitency LT d em em a chm CEP CEP CES os umm ame aie at p Fabre Link Bandwidth Fabric Link Bandwidth Aggregation and Access per stack 20 Gb Aggregation and Access 20 0b Maximum Available Downlink Ports 297 Maxim Available Downlink Ports 7935 Access Switeh 54310 of 4820T Access Swich 14810 or 58201 Slacking enabled in Access e Residency in Access switches ver tep dot Tier Aggregation Acces e zeng Mined Mode Basic cuum ceupum uum coke cum aie Fabric Link Bandwidth Aggregation axd Accom 20 amp Wacom Avakable Downlink Ports 2410 Access Switch 5459 or 4820T Back Next Save and Exit Figure 33 Layer 3 with Resiliency Routed VLT Deployment Type screen 1 Navigate to the Network gt Design Fabric gt New Fabric gt Deployment Topology screen 2 Inthe 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 See Conventional Core Versus Distributed Core c Layer 3 with Resilency Routed VLT Use the Layer 3 fabric to extend equal cost multi pathing capabilities See Selecting a Layer 2 VLT and Layer 3 with Resiliency Routed VLT Fabric Design 3 Click o
84. dation Alarms Validation failed because the switch cannot be If you have undiscovered switch errors log on to the discovered switch console to isolate the fault NOTE Make sure that the switch has been power cycled on and check the physical connection Validation failed because the switch has a mismatch MAC address Verify that you have correctly mapped the system MAC address to the associated switches Navigate to the Network gt Fabric Name gt Configure and Deploy screen From the Deploy Fabric pull down menu select the Pre deployment Configuration option 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 Navigate to the Network gt Fabric Name gt Configure and Deploy screen From the Deploy Fabric pull down menu select the Deploy and Validate option Click on the Validation tab and the check the switch to validate Click the Validate Selected link Validation failed because the switch has a name mismatch Verify that you have correctly mapped the system MAC address to the associated switches 132 a Navigate to the Network gt Fabric Name gt Configure and Deploy screen b From the Deploy Fabric pull 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
85. de BMP mode AFM deploys the new configuration which overwrites the entire current configuration onto the switch Ifthe Reset to factory defaults option is not selected AFM deploys the new configuration which overwrites the entire current configuration onto the switch 11 Checkthe progress and status of the deployment in the Status Status Details Response Actions and Last Deployed columns For information about how to view validation errors see Validation Status and Errors See also Troubleshooting For information about the progress and status of selected switches and operations allowed during a fabric state see Operations Allowed During Each Fabric State and Understanding Fabric Phases Advanced Configuration Use the Advanced Configuration screen to do the following e View the Auto Generated Configuration e Associate the Templates to Fabric Switches K NOTE You must first create a template for a fabric before you can associate it For more information see Adding Templates e Add the Switch Specific Custom Configuration e Preview the Combined Configuration 112 View the Auto generated Configuration To view the AFM auto generated configuration 1 Navigate to the Network gt Fabric Name gt Configure and Deploy gt Deploy Fabric gt gt Advanced Configuration gt View Auto Generated Configuration screen From the Deploy Fabric pull down menu select the Deploy and Validate option On the Deploy
86. delete Click the Delete Fabric link Viewing the Wiring Diagram To view and export the wiring diagram of the fabric 1 2 3 4 Navigate to the Network Design Fabric screen Select the fabric and then click the View Wiring Plan link If you want to display future switches and links click the Display future switches links option Click one of the following options a Tabular Wiring Plan b Graphical Wiring Plan c Network Topology Plan d Network Topology Tabular Plan Click the Export link to export the wiring plan 71 78 7 Configuring and Deploying the Fabric After you create a fabric at the Network gt Design Fabric gt New Fabric screen you can configure and deploy the fabric at the Network gt Fabric Name gt 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 e Deploy Fabric Prepares the fabric for deployment and deploys the fabric Pre deployment Configuration Deploying and Validate View DHCP Configuration Errors Displays errors in the fabric Related Links Deployment and Validation Errors Troubleshooting e CU Configuration Template and custom configuration using the FTOS CLI commands Manage Templates Associate Templates Custom Configuration Viewing Custom Configuration History
87. dresses c DHCP TFTP FTP software images Pre deployment 7 Deploy Core Deploy Validate and Edit View DHCP Configurations and Errors D c H gt 2 D Figure 3 Provisioning AFM Site Map To help you navigate the AFM user interface use the following site map Getting Started Dashboard Wizard Step 1 Design the Fabric Step 2 Pre Deployment Configuration Step 3 Deploy the Fabric Summary Alerts and Performance Design Fabric Events Current Historical Map Network View Graphical and Tabular View Summary Alerts and Average Bandwidth Utilization Link Usage Switch Statistics Performance New Fabric Edit Fabric Delete Fabric View Wiring Plan Maintenance Configure and Events Current Historical Fabric View Summary Alerts and Average Bandwidth Utilization Link Usage Switch Statistics Performance Software Updates Backup and Restore Troubleshooting Deploy Fabric Deploy Fabric Pre deployment Configuration Deploy and Validate View DHCP Configuration Errors CLI Configuration View DHCP configuration files Manage Templates Associate Templates Custom Configuration View Custom Configuration History View Wiring Plan Replace a Switch Events Current Historical Device View Graphical and Tabular View Switch and Port Real time and Historical data Ping SSH Traceroute Telnet Decommis
88. e View Deployment and Validation Status 81 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 Pre deployment Step 2 Assign Switch Identities Pre deployment Step 3 Management IP Pre deployment Step 4 SNMP and CLI Credentials Pre deployment Step 5 Software Images Pre deployment Step 6 DHCP Integration Moo 8 SF o Pre deployment Step 7 Summary Layer 3 Distributed Core Fabric Pre deployment To prepare the Layer 3 Distributed Core fabric for deployment complete the following tasks using the Pre deployment Configuration wizard 1 Protocol Configuration for Layer 3 fabric Step 1 Pre deployment Step 1a Fabric Link Configuration Pre deployment Step 1b Uplink Configuration Pre deployment Step 1c Downlink Configuration Pre deployment Step 2 Assign Switch Identities Pre deployment Step 3 Management IP Pre deployment Step 4 SNMP and CLI Credenti
89. e AFM Navigate to the Network gt Fabric Name gt Configure and Deployment screen Click the Errors link Click on the Discovered Errors tab to view error details 115 4 Fixany errors Switch is not Discovered Verify the switch connectivity from the AFM Navigate to the Network gt Fabric Name gt Switch Name gt Troubleshoot screen Click the Errors link Click on the Undiscovered Errors tab to view error details Fix any errors Configuration mismatch errors exists Check for switch configuration mismatch errors Navigate to the Network gt Fabric Name gt Configure and Deployment screen Click the Errors link Click on the Config Mismatch Errors tab to view error details Fix any errors Custom Configuration errors exists Check for switch custom configuration errors Navigate to the Network gt Fabric Name gt Configure and Deployment screen Click the Errors link Click on the Custom Config Errors tab to view error details Fix any errors Wiring Errors Exists Verify the Errors in the Wiring Error tab 1 Navigate to the Network gt Fabric Name gt Configure and Deployment screen Click the Errors link Click on the Wiring Errors tab to view error details 4 Fix any errors Validating the Fabric To verify that the discovered fabric matches the planned fabric and correct any errors 116 1 Navigate to the Network gt Fabric Name gt Configure and
90. e Major alerts Yellow Minor alerts Blue Warning alerts Green Information alerts or no alerts Gray For unmanaged or un deployed fabric e Selection Clicking a fabric icon highlights the icon and displays the fabric data in the Detail tab Show Tooltips Displays tooltip information about a fabric fabric name status active alerts and the total number of switches in the fabric when you place your mouse over a fabric icon 126 e Enable Move After enabling this option you can move each fabric icon to a new location in the map e Revert to Last Saved Revert to fabric locations to last saved version e Save Move Save the location of the fabrics that were moved e 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 e Enter fabric name To locate a fabric enter the name and then click the search icon e Background Map Actions Load or delete a geographical background map for the network e Enter fabric name Enter the fabric name and then click the search icon to locate a fabric in the network Navigate to the Network Summary screen and then click the Graphical tab e Active Fabric Manager Alerts and Events Performance und Map Actions Y Topology Options Show Tooltips Enatte Move Reset to Last Saved ve Move Fabric Summary To display the status of t
91. e option Click the Validation tab and then select the switches to validate Click the Deploy Selected link Table 35 Undiscovered Switch Error Undiscovered Switch Error Recommended Action Verify that the switch has a valid IP address If required correct the pre deployment configuration Verify that the switch is running the minimum required software 1 2 3 From the AFM server verify that the connectivity to the switch exists 4 5 Validate the switch Navigate to the Network gt Fabric Name gt Configure and Deploy From the Deploy Fabric pull down menu select the Deploy and Validate option Click the Validation tab and then select the switches to validate Click the Deploy Selected link Table 36 Discovered Switch Error Discovered Switch Error Recommended Action Disconnected mm d e Verify that the connectivity to the switch exists from the AFM server Verify that the switch is running the minimum required software Validate the switch Navigate to the Network gt Fabric Name gt Configure and Deploy screen From the Deploy Fabric pull down menu select the Deploy and Validate option Click the Validation tab and then select the switches to validate Click the Deploy Selected link itch N Mismatch d Genk 1 SUITED Name Mismate Verify that the IP address to switch name mapping is correct in the pre deployment configuration 137 2 Ifthe pre deployment configuration is updated
92. e Management e Detailed Port Performance e TCA Threshold Setting e Data Collection e Reports Network Performance Management To monitor the following network historical data for all the fabrics use the Network Performance screen e Bandwidth utilization e Top25 port inbound usage e Top 25 port outbound usage Highest CPU utilization e Highest memory utilization For information about the color codes for the historical data see Dashboard Leen m Pet trm De abes Global Mett Average Bandwidth Utilization Bandwsdth Utibzation Link Usage Top 15 Port Inbound usage f abe swan Ut Port 149 Fabric Performance Management To monitor the following for all the switches in the fabric use the Network gt Fabric Name gt Performance screen e Bandwidth utilization e Top 25 port inbound usage e Top25 port outbound usage e Top 10 highest CPU utilization e Top 10 high memory utilization Mir ard Loge Pertormance P Conf eee oni Div Chobel S ats Average Bandwidth Utilization Bandwidth Utilization p A Link Usage Top 25 Port inbound usage lates ve ra Pet Switch Performance Management To view historical and real time data switch level performance use the Network gt Fabric Name Switch Name gt Performance screen By default the historical view is shown in tabular format You can also monitor performance in graphical chart or bar format in the View Type area or move to the
93. e Secure SMTP Email Settings area click the Edit link 3 Inthe Outgoing Mail Server field 4 Inthe Server Port field enter the port number of the email server 5 Inthe User Name field enter the user name 6 Inthe To Email Address es enter the mail addresses separated by comma 7 Inthe Minimum severity level to Email Notification pull down menu select one of the following settings Critical Major Minor Warning 8 Click the OK button SNMP Configuration Configure SNMP so that theAFM can perform SNMP queries on the switches in the fabric The values you enter in the SNMP configuration are also used for configuring the switches during the build phase and for monitoring during the run phase 1 Navigate to the Administration gt Settings screen In the SNMP Configuration area click Edit In the Read Community String field enter the read community string For example public In the Write Community String field enter the write community string For example private In the Port field enter the SNMP port number of the switches The port number is typically 161 In the Trap Host field specify the IP address of the AFMso that the traps are sent to the AFM Click OK no c FW M Syslog Server IP Addresses 1 Navigate to the Administration Settings screen 2 Inthe System IP Addresses area you can configure up to 8 syslog server IP addresses to log events on the switches in the fabric By default
94. e extranet Redundancy and resiliency are the main factors for high availability which requires chassis based core routers Aggregation layer The aggregation layer connects with top of rack ToR switches and aggregates the traffic into fewer high density interfaces such as 10GbE or 40GbE This layer aggregates the traffic to the core layer Access layer ToR The access layer typically contains ToRs A ToR is a small form factor switch that sits on top of the rack and allows all the servers in the rack to be cabled into the switch A ToR has a small 1 to 2 rack unit RU form factor Conventional Core Core Aggregation Access 21 Distributed Core A distributed core is a two tier architecture composed of multiple switches interconnected to provide a scalable high performance 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 The spines move traffic between the leaves bi directionally providing redundancy and load balancing Together the spine and leaf architecture forms the distribute core fabric This two tier network design allows traffic to move more efficiently in the core at a higher bandwidth with lower latencies than most traditional three tier networks Because there i
95. e fabric Gather the useful information listed in Gathering Useful Information for a Layer 3 Distributed Core Fabric or Gathering Useful Information for a Layer 2 VLT Fabric or Gathering Useful Information for a Layer 3 with Resiliency Routed VLT Fabric Use the following pre deployment flowchart as a guide to prepare the fabric for deployment 83 Pre Deployment Flowchart Prerequisites Configuration Bare metal files provisioning 1 Identity uplink 2 Identify downlink IP addresses IP Addresses 3 Assign switch 4 Assign mangement identities IP addresses to switches S Specify FTOS software 6 Integrate DHCP file version for each switch type into DHCP server 7 View summary before initiating deployment 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 84 Assign Switch Identities Assigns a system media access control MAC address to each switch in the fabric You can optionally assign serial numbers and service tags to each switch DHCP Integration Creates a dhcp cfg file that loads the correct software image and then a configuration file for each ty
96. e fabric links between core and aggregation switches supports Layer 3 protocol with OSPF in the VLAN interfaces e The fabric links between the aggregation and access switches supports the Layer 2 protocol the Layer 2 protocol The uplinks between the aggregation switch and external switch WAN supports the Layer 3 protocol OSPF iBGP or eBGP e The downlinks from the access 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 In this 62 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 Introduction v Deployment Topology Fabric Name and Type 2 Fabric Type Layer 2 Layer 3 with Restiency Routed VLT Bandwidth and Port Count b Advanced Options Deployment Topology e Deployment Type 3 Tier Core Aggregation Access 3 Tier Core 29000 4810 MXL v 2900 Stacking Res E m x de aie w cor cop om om d Ud H HH ee Fabric Link Bandwidth Fabric Link Band Aggregation and Access per stack 20 Gb Aggreg
97. e first name can contain any characters Length 1 to 50 characters Optional In the Last Name field enter the user s last name The last name can contain any characters Length 1 to 50 characters From the Role pull down menu select one of the following roles Admin or User For information about roles see Managing User Accounts In the Sessions Allowed pull down menu specify the number sessions allowed for the user You can specify from 1 to 5 sessions The default value is 5 In the Session Timeout pull down menu specify one of the following timeout values The default value is 15 minutes a 15 minutes b 30 minutes c 45 minutes d 60 minutes In the Unsuccessful Login Limit pull down menu select value from 3 to 10 The default value is 5 In the Lockout Duration pull down menu select one of the following options The default value is 30 minutes a 15 minutes b 30 minutes c 45 minutes d 60 minutes e Permanent Click OK Deleting a User To add or delete users you must be a Superuser For more information about user accounts see Managing User Accounts To delete a user 1 2 3 4 Navigate to the Administration User Accounts screen Select the user that you want to delete Click the Delete button Click Yes Editing a User To edit a user you must be a Superuser For more information about user accounts see Managing User Accounts To edit a user 1 176 Navigate t
98. e location of the switches including the rack and row number from your network administrator or network operator Obtain 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 gt Settings gt TFTP FTP screen For information about which software packages to use see the Release Notes Download 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 Place the software images on the TFTP or FTP site so that the switches can install the appropriate FTOS software image and configuration file Obtain the Dynamic Host Configuration Protocol DHCP server address to be used for the fabric from your DHCP network administrator or network operator If a remote DHCP server is not available AFM also provides a local DHCP server The DHCP server must be in the same subnet where the switches are located After you power cycle the 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 pool of IP addresses for the management port for each switch in the fabric O
99. e ports required by the fabric a b c d In the Uplink Ports Current column enter an even number of uplink ports connections to the WAN required by the fabric for initial deployment The minimum number of uplinks is 2 One uplink is for redundancy For a 10 Gb bandwidth AFM supports 2 to 32 uplinks For a 40 Gb Bandwidth AFM supports 2 to 8 uplinks Fora Layer 2 VLT fabric and Layer 3 with Resiliency Routed VLT fabric an edge port link uplinks from the aggregation or core switches that connect outside the fabric For a3 tier itis core for a 2 tier itis aggregation For Layer 3 distributed core an edge port link uplinks on the first two leaves that connects to the edge WAN which typically connects to an internet service provider ISP In the Downlink Ports Current column enter an even number of downlink ports 2 to the maximum number of available ports required by the fabric for initial deployment The default is 2 downlink ports In the Uplink Ports Future column area enter the number of uplink ports connections to the WAN required by the fabric for future expansion of the fabric If the future ports are not reserved you cannot expand the fabric in the future In the Downlink Ports Future column area enter an even number of downlink ports connections to the servers switches or ToR required by the fabric for future expansion of the fabric NOTE When you select the Blade switch MXL deployment option i
100. e the Type 1 Extra Large Distributed Core fabric design when e The line rate performance with a fabric oversubscription ratio of 1 1 between the spines and leaves e 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 The Type 1 Extra Large Distributed Core Design uses a 1 1 spine to leaf ratio As a result the maximum number of spines for this design is 16 and the maximum number of leaves is 32 Each Z9000 or S6000 leaf for the Type 1 Extra Large Distributed Core design has the following e Six hundred forty Gigabit of fabric interlink fabric links maximum capacity to the Spine 16 x 40 Gb e Forty eight 10 Gb ports for server connectivity and WAN connectivity Type 2 Large Distributed Core Fabric Use the Type 2 Large Distributed Core fabric design when e You require a fabric interlink fabric links bandwidth between the spines and leaves of 10 Gb is required e The current and future planned uplinks and downlinks on the leaves for the fabric is less than or equal to 2048 ports e The leaves act as a switch or ToR leaf switch Within the ToR the downlink protocol can be either VLAN or VLAN and LAG With a Type 2 Large Distributed Core fabric design the S4810 spines connect to the S4810 leaves at a fixed 10 Gb The maximum number of spines is 32 and the maximum number of leaves i
101. e to retain performance history 1 Navigate to the Administration Settings screen 2 Inthe Data Retention area click the Edit button 3 Inthe Performance History area enter the number of days you want to retain your performance history The range is from 1 and 180 days 4 Inthe Daily Purge Execution Time pull down menu specify the time to begin purging the performance history data 5 Click OK DHCP Server Settings 1 Navigate to the Administration Settings screen 2 Navigate to the DHCP Server Settings area and select one of the following settings Local AFM provisioned as a DHCP server When you select this option the AFM automatically integrates the generated dhcp config file into the DHCP server on the AFM during pre deployment Remote Use External DHCP server When you select this option manually install the dhcpd conf file that is generated during pre deployment into the DHCP server before you deploy the fabric 3 Click the OK button NTP Server Settings To configure NTP Server Settings 1 e Cen o0 Ps Si Pa 172 Navigate to the Administration Settings screen In the NTP Server Settings area click the Edit link Enter the NTP server primary IP address Enter the IP status address Enter the NTP server secondary IP address Enter the Secondary IP status address Click the OK button SMTP Email To configure SMTP email 1 Navigate to the Administration Settings screen 2 Inth
102. eaves all the aggregation all the access all core switches or a set of switches When a template is associated to an entire fabric all spines or all leaves or all aggregation access or core switches the template is automatically applied to the newly added switches instead of having to create new associations manually You can also edit and delete templates ug Important Each template can have only one association per fabric AFM does not support ordering of templates for sequencing the commands If you want to do this Dell Networking recommends manually combining the templates into a single template This section contains the following topics e Associating Templates e Editing Template Associations e Deleting Template Associations Associating Templates To associate templates 1 Navigate to the Network gt Fabric gt Configure and Deploy screen From the CLI Configuration pull down menu select the Associate Templates option Click the Add Association link In the Template Name pull down menu select the template to use Optionally In the Comments field enter your comments about this association o c fF t Ww In the Select Association area select one the following options All Associates the template to all the switches in the fabric Aggregation Associates the template to all the aggregation switches Access Associates the template to all the access switches Core Ass
103. ectivity to the ToR For more information about troubleshooting see Ping Traceroute SSH and Telnet Ping Traceroute SSH and Telnet To troubleshoot a switch in the fabric use ping traceroute SSH and Telnet Ping e Traceroute SSH Telnet E NOTE SSH or Telnet will work depending upon what you have configured in the switch protocols Ping To ping a switch in a fabric 1 Navigate to the Network gt Fabric Name gt Switch Name gt Troubleshoot screen 2 Click the Ping button to display the ping results Traceroute To traceroute a switch in the fabric 1 Navigate to the Network gt Fabric Name gt Switch Name gt Troubleshoot screen 2 Click the Traceroute button to display the traceroute results SSH To issue an SSH command on a switch 131 1 Navigate to the Network gt Fabric Name gt Switch Name gt Troubleshoot screen 2 Clickthe SSH tab 3 Inthe SSH Command field enter the SSH command 4 Clickthe Send Command button to display the SSH results Telnet To issue a Telnet command on a switch 1 Navigate to the Network gt Fabric Name gt Switch Name gt Troubleshoot screen 2 Click the Telnet tab 3 Inthe Telnet Command field enter the Telnet command 4 Click the Send Command button to display the Telnet results Validation Alarms To troubleshoot alarms that are generated by the AFMwhen you deploy the switch use the following table Table 32 Vali
104. efore you rack the switches Print out the wiring plan and use it to rack and cable the hardware according to the fabric design wiring plan Document the location of the switches including the rack and row Select the fabric you are performing pre deployment on at the Network gt Fabric Name gt Configure and Deploy gt Pre deployment Configuration screen Importing an Existing Fabric Design To import an existing fabric design 1 2 76 Navigate to the Home gt Getting Started screen Click the Importing Existing Design option The Import Existing Design screen displays 3 4 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 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 2 4 Navigate to the Home Getting Started screen Click the Edit Existing Fabric button The Select a Fabric screen displays Select a fabric to edit and then click the OK button The Fabric Designer wizard displays Edit the fabric Deleting the Fabric To delete a fabric 1 2 3 4 Navigate to the Network screen Select the Design Fabric tab Select the fabric to
105. eld enter the starting IP address and prefix Enter a valid IP address and a prefix from 8 to 23 In the Number of ports per port channel enter the number of ports assigned to a port channel for a particular VLAN ID Range from 1 to 16 In the Starting VLAN ID field enter a starting VLAN ID Range from 2 and 4094 From the Protocol Profile pull down menu when the leaves are acting as a leaf switch the switches are directly connected to the server select the Downlink VLAN and VRRP and LAG protocol setting The default setting is Downlink VLAN Click Next to go the Assign Switch Identities screen Protocol Configuration Layer 3 with Resiliency Routed VLT Step 1 To configure the pre deployment protocol configuration for a Layer 3 with Resiliency Routed VLT complete the following tasks 1 2 94 NOTE The Layer 2 VLT Layer 3 Distributed Core and Layer 3 with Resiliency Routed VLT fabrics use the same pre deployment configuration screens from step 2 through step 7 Before you begin review the pre deployment workflow at Using the Pre deployment Configuration Wizard Pre deployment Step 1a Fabric Link Configuration Pre deployment Step 1b Uplink Configuration 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
106. elect the fabric and then switches to update 13 2Tier distributed core filtering options All Spine and Leaves 2Tier VLT options All Aggregation and Access 3tier filtering options All Core Aggregation and Access Click the gt gt button to move the switches to update to the Selected area and the click the Next button 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 In the Path and Image file name to the software updates on selected TFTP or FTP site field specify the path and image file to the switch software update Click the Next button In Update Option select one of the following options and then click the Next button Manual Update is staged to the secondary partition but not applied Automatic Apply software update and reboot The Schedule screen displays On the Schedule screen select one of the following options Run Now Updates the switch software immediately Schedule job to start on Specify a date and time to schedule the job to update the switch software The Summary screen is displayed Review the settings in the Summary screen and then click the Finish button Switch Software Activation To activate the software available in the standby partition of the switch as a scheduled job to happen at later time or to run immediately use the Switch Software Activation opt
107. elected link Custom co figuration upload failed Verify the switch login credentials and commands Restart the deployment of the switch from the Network gt Fabric Name gt Configure and Deploy by selecting the switch from the list and then click on the Deploy Selected link Backup config failed Verify the Telnet SSH connectivity Restart the deployment of the switch from the Network gt Fabric Name gt Configure and Deploy by selecting the switch from the list and then click on the Deploy Selected link Validation Errors Use the following tables to troubleshoot the following validation errors when you deploy a fabric Validation reports any inconsistencies between the design and the discovered fabric The mismatches are reported by AFM as errors and the corresponding alarms that are generated To view validation errors navigate to the Network gt Fabric Name gt Configure and Deploy screen and then click on the Errors link to view the following type of errors e Configuration e Custom Configuration e Custom Configuration Deployment e Discovered Switch Errors e Pre deployment e Undiscovered Switch Errors e Wiring 135 Errors southcore Export Pre deployment Undiscovered Discovered Config Mismatch Custom Config Wiring Errors Errors 4 Errors 0 Errors 0 Errors 0 Errors 40 Custom Config Deployment Errors 0 Switch Name Error Details Last Deployed No Records Found O Items Found Disptayin
108. ell Networking sales representative for this file 2 Navigate to the Network gt Fabric Name gt Configure and Deploy screen 3 From the Deploy Fabric pull down menu select the Pre deployment Configuration screen option 4 Navigate to the Assign Switch Identities screen 5 Click the Browse button and specify the path of the CSV file If you do not have this file manually enter this information in the System MAC Address fields 6 Click the Upload button 7 Click the Choose MAC icon in each row to associate the switch name with the MAC address optional serial number and optional service tags using the CSV file or manually enter this information If you are using a CSV file the Select MAC Address Selection screen is displayed 105 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 To assign a management IP address to the switches in the fabric Navigate to the Network gt Fabric Name gt Configure and Deploy screen From the Deploy Fabric pull down menu select the Pre deployment Configuration option
109. en the Active Link is started it displays another browser to view AFM performance statistics For information about how to install and configure OMNM see http www dell com support Manuals us en 555 Product dell openmanage network manager Refer to the release notes or AFM Installation Guide for the supported versions of OMNM g Important Install the Dell OMNM software onto a different server other than the AFM To activate the performance statics login directly as write permission into Dell OMNM web service 169 E 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 Turn off the Application Server and Synergy Network Management server Add the following three lines in the installed properties file com dorado core ws disable false com dorado core ws legacy soap enabled true oware webservices authrequired false 5 Turn on the Resource Monitoring option to enable performance monitoring 6 Start the Application server and Synergy Network Management server Before you configure the Active Link gather the following OMNM server information e OMNM server IP address e communication protocol HTTP or HTTPS e user name and password The AFM provides the Active Link server and Active Link webs servi
110. ent Configuration Wizard e Pre deployment Step 1a Fabric link Configuration e Pre deployment Step 1b Uplink Configuration e Pre deployment Step 1c Downlink Configuration NOTE For pre deployment the Layer 2 VLT Layer 3 Distributed Core and Layer 3 with Resiliency Routed VLT fabrics use the same pre deployment configuration screens from step 2 through step 7 Pre deployment Step 1a Fabric link Configuration Before you begin review the Using the Pre Deployment Wizard and Pre deployment Wizard Introduction sections To configure the links that connect the leaves and spines for a Layer 3 distributed core fabric or the links that connect the core access and aggregation switches for a Layer 3 with Resiliency Routed VLT fabric using the OSPF routing protocol use the Fabric link Configuration screen The Port Bandwidth a read only field is automatically determined by the selected fabric type and fabric oversubscription ratio To automate the pre deployment process AFM automatically populates the starting IP address range prefix loop IP address prefix based on the fabric design and sets the area ID for OSPF to 0 Review these settings You can modify the IP address range and loopback address The start prefix for both types of addresses must be from 8 to 29 and the loopback prefix from 8 to 26 For information about how to configure a Layer 2 VLT Fabric Interlink Configuration see Pre deploymen
111. ential tagging is applied to the available ports and the number of ports specified on a VLAN Auto fill Untagged Port For selected VLANs untagging is applied Based on available ports only one port per VLAN is associated Note The number of Port VLAN Port option is disable on the Autofill Tagged Untagged Port screen Copy Switch VLAN Config Copies the VLAN association from the current switch to other switch es in the fabric Copy VLAN Port Config Copies the VLAN association from a selected port to other port s within a switch Port VIAN Association VIAN Association Port VIAN Association Maps the physical portto the VLAN ID For example maps 1 port to multiple VLANs Maps the physical port to the VLAN ID For example maps 1 portto multiple VLANs physical port to the VLAN ID For example maps 1 port to multiple VLANs VLAN Port Association Maps the VLAN ID to physical port interfaces For example maps 1 VLAN to multiple ports Copy VLAN Tagged Port Copies the VLAN tagged port configuration from a selected port to other port s within Config a switch To configure downlink ports on the access switches 1 Navigate to the Network gt Fabric Name gt Configure and Deploy screen 2 From the Deploy Fabric pull down menu select the Pre deployment Configuration option 3 Navigate to the Layer 2 VLT Downlink Port Configuration screen 104 Predeployment Configuration Layer2core 7 Dowriink Port
112. enu select the Pre deployment Configuration option 3 Navigate to the SNMP and CLI Credentials screen 4 Navigate to the SNMP Configuration area 5 Inthe Read Community String field enter the read community string For example public 6 Inthe Write Community String field enter the write community string For example private 7 Navigate to the CLI Credentials area 8 Inthe Protocol pull down menu select one of the following options Telnet or SSHv2 9 Inthe User Name field enter the user name 10 In the Password field enter the password 11 Inthe Confirm Password field confirm the password The privilege level is a read only field and is set at 15 12 Inthe Enable Password field enter a password for the privilege level 13 Inthe Confirm Enable Password field confirm the enabled password for the privilege level 14 Click Next 106 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 To change the address of the TFTP or FTP site navigate to the Administration gt Settings gt TFTP FTP screen NOTE Before you begin make sure that you have loaded the
113. eployment Topologies for Layer 2 or Layer 3 with Resiliency 10 Gb Blade Switch MXL for Layer 2 and Layer 3 with Resiliency Routed VLT For information about tiers see Deployment Topology See also Deployment Topology Use Cases For more information about VLT see 34 Overview of VLT Key Core Design Considerations for VLT e Getting Started 1 Tier for 10 Gb and 40 Gb ToR for Layer 2 and Layer 3 Resiliency Routed VLT Table 2 1 Tier for 10 Gb and 40 Gb ToR for Layer 2 and Layer 3 Resiliency Routed VLT Downlink Uplink Port Range Aggregation VLTi Possible Topologies Bandwidth Bandwidth Capaci dii Core Aggregation Access 2 40 Gb S4810 or S4820T Z9000 or S6000 Z9000 or S6000 Ee m ES DS Deeg SS 2 Tier and 3 Tier Topologies for 1 Gb ToR VLT Deployment for Layer 2 and Layer 3 with Resiliency Routed VLT With a 1 Gb ToR VLT Deployment fabric design the 4810 aggregation switches connect to access switches at fixed 10 Gb The maximum number of VLT aggregation is 2 switches and the maximum number of VLT access switches is based on the number of uplinks and downlinks you design in your fabric With this topology the downlinks connect to access S55 or S60 switches using a 1 Gb bandwidth 1 Gb Top of Rack Deployment 40 Gb uplinks 2to 4 VLT Domain 4 x40 Gb S4810 Aggregation 2 40 Gb VLTI per switch S60 Access or 55 Access Switch Stacking Switches
114. er the VLAN ID Range 2 to 4094 Default lt Blank gt 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 lt Blank gt 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 lt Blank gt Default Prefix 24 Virtual IP Enter the virtual IP address The prefix is auto populated Address for Virtual IP Valid IP address Prefix range from 8 to 29 Default Virtual IP lt Blank gt Default Prefix 24 To configure a VLT VLAN 1 Navigate to the Network gt Fabric Name gt Configure and Deploy screen 2 From the Deploy Fabric pull down menu select the Pre deployment Configuration option 3 Navigate to the VLAN Configuration screen Check the VLAN and VRRP Configuration option to the VLAN ID primary IP address secondary IP address and virtual address Click the Add VLAN link The Add VLAN Window is displayed NOTE When you add a VLAN and do not enable the VLAN and VRRP Configuration option you can only enter the VLAN ID and IP address range 88 In the VLAN ID field enter the VLAN ID In the Primary IP address field enter the primary IP address In the Secondary IP address field enter the secondary IP address In the Virtual IP address field enter the virtual IP address
115. er the description of the fabric There is no character restriction The length of the description can be from 1 and 128 characters 6 Ifyou are using the AFM Openstack check the OpenStack Neutron Managed option NOTE When you select this option you cannot enter the VLAN configuration in the AFM Pre Deployment Wizard This is handled by OpenStack which requires the AFM Neutron Plug in installation which orchestrates the Layer 2 VLAN configuration between OpenStack and AFM See the AFM Plug in for Openstack Guide 7 To include blade switches MXLs check the Blade switch MXL deployment option This option is for a Layer 2 fabric or Layer 3 with Resiliency Routed VLT fabric 8 Click Next to go to the Bandwidth and Port Count screen to review the uplink and downlink bandwidth settings Uplinks connect from the fabric up to the next upstream tier of devices towards the core of the network Downlinks connect from the fabric down to the next tier of devices or servers towards the edge of the network Fabric Design Step 2 Bandwidth and Port Count The Bandwidth and Port Count screen displays the default values for the fabric uplinks and downlinks Uplinks connect from the fabric up to the next upstream tier of devices toward the core of the network The minimum number of uplinks is 2 One uplink is for redundancy Downlinks connect from the fabric down to the next tier of devices or servers towards the edge of the network These values 1
116. fabric see Editing and Expanding an Existing Fabric Design 33 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 Obtain the remote Trivial File Transfer Protocol TFTP File Transfer Protocol FTP address from your network administrator or network operator To specify a TFTP FTP site go to Administration gt Settings gt TFTP FTP screen For information about which software packages to use see the Release Notes Download 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 Place the software images on the TFTP FTP site so that the switches can install the appropriate FTOS software image and configuration file Obtain the Dynamic Host Configuration Protocol DHCP server address to use for the fabric from your DHCP network administrator or network operator If a remote DHCP server is not available AFM also provides a local DHCP The DHCP server must be in the same subnet where the switches are located After you power cycle the switches the switches communicate with the DHC
117. g 0 0 Table 33 Configuration Errors Configuration Error Recommended Action figuration Mismatch ae f EORDUTSEDIUMISINIE On the Deployment and Validation Status screen select the switch that you want to view Click the View Mismatch button Review the configuration mismatch and correct the configuration errors 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 Wiring Errors Wiring Error Recommended Action VAR Mismatch Review the wiring plan Wire the switch according to the wiring plan to fix the wiring mismatch Validate the switch from the screen by selecting the switch from the list and clicking on the Start Validation button Missing Tank Review the wiring plan Wire the switch according to the wiring plan to fix the missing link Validate the switch 136 a Navigate to the Network gt Fabric Name gt Configure and Deploy From the Deploy Fabric pull down menu select the Deploy and Validate option Click the Validation tab and then select the switches to validate d Click the Deploy Selected link SEHR Verify that the switch is wired according to the wiring plan Verify the connectivity on the AFM from both of switches of the link Validate the switch Navigate to the Network gt Fabric Name gt Configure and Deploy From the Deploy Fabric pull down menu select the Deploy and Validat
118. gure 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 Optional From the Fabric Link Bandwidth pull down menu select the fabric link bandwidth for each switch that you want to customized abnc Design myfabric ntroduction v Fabric Customization Si Fabric Name and Type Details of Heterogeneous Leaf Node Bandwidth and Port Count Bi Display future switches links Deployment Topology Switch Name Model Fabric Link Bandwidth Role Usage Aggregation 1 Aggregation 2 4810 Aggregation Designed Accest 1 4810 Access Designed Access 2 4810 Access Designed Access 3 4810 Access Designed ACC 4 4810 Access Designed Access 5 4810 Access Designed 6 Item s found Displaying 1 5 Note Decreasing Fabric Link Bandwidth will increase the number of Downlinks Step 5 of 7 Back Neat Save and Edt Cancel Figure 32 Customizing Fabric Link Bandwidth between Switches 10 Click the Next button to go to the Output screen Selecting the Fabric Deployment Type To select the fabric deployment type 69 Fabric Design Layer3core roduc Tee i Deployment Topology Fabric Ni vi Type m a cena au 7 Fabrice Type C tayer Layer Layer 3 with Rertency outes VLT Bandwidth and Port Count v b Advanced Option gt Deployment Topoloty Deployment Type Ther Aggregation Access Tier Aggregation Acces Zeng sar 40 Seng Mixe
119. h Deployment Status Errors Switch Deployment Status Requires Recommended Actions Action NOT STARTED Not Started Start the deployment of the switch from the Network gt Fabric Name gt 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 138 CONFIG GENERATION IN Configuration File No Information only PROGRESS Generation In progress CONFIG GENERATION FAILED Configuration File 1 ue Generation Failed f Check the write permission for the AFM installation directory in the AFM server machine Verify that the disk space is not full in the AFM server Restart the deployment of the switch from the Network gt Fabric Name gt Configure and Deployscreen by selecting the switch from the list and then click on the Deploy Selected link NOTE The switch is in BMP mode CONFIG GENERATION Configuration File Information only SUCCESS Generation Completed Successfully CONFIG FILE TRANSFER IN Configuration File Transfer Information only PROGRESS In progress CONFIG FILE TRANSFER Configuration File Transfer ges FAILED Failed Verify the connectivity to the TFTP server from the AFM server Restart the deployment of the switch from the Network gt Fabric Name gt Configure and Deploy by selecting the switch from the list and then click on the Deploy Selected link NOTE The switch is in BMP mode CONFIG FILE TRANSFER Config
120. he design process AFM provides a fabric design wizard to help you design a Layer 2 Layer 3 or Layer 3 with Resiliency Routed VLT fabric based on the your current and future datacenter capacity requirements See Designing the Fabric Using the Fabric Design Wizard and Supported Fabric Types To generate a physical wiring diagram for the fabric during the design phase enter your data center capacity requirements The wiring diagram is typically given to the network operator who uses it to build the physical network For information about designing a fabric see Selecting Distributed Core and Selecting a Layer 2 and Layer 3 with Resiliency Routed VLT To configure the fabric name and type 1 Navigate to the Fabric Design Wizard at the Network gt Design Fabric screen 2 Click the New Fabric link The Introduction screen is displayed 3 Review the introduction and click the Next button The Fabric Name screen displays 52 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 _ cw 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 EastFabric Spine 1 and EastFabric Leaf1 5 Optional In the Description field ent
121. he fabric in a graphical view Graphical button which is the default view and the tabular view Tabular button for all the switches in the fabric use the Network gt Fabric Name gt Summary screen Displaying the Fabric in a Tabular View With the fabric tabular view you can view the switches in the fabric and check alarms Export your results using the Export link e You can also manage or unmanage a switch using the Manage Unmanage Switch 127 For You can display additional performance statistics about a fabric using the Launch Active Link option by navigating to the Network gt Fabric level gt Tabular screen From the Action pull down menu select the switch row and then click the Launch Active Link option information about how to configure the Active Link navigate to the Administrative gt Settings gt Active link Settings screen For additional information about the fabric select the following tabs Detail Links Hardware VLT Domain Displaying the Fabric in a Graphical View A fabric graphical view provides the topology view of the fabric The fabric type and name display at the top of the fabric view View the leafs associated with a spine by clicking on the spine or the aggregation switches associated with the acc 128 ess switches by clicking a aggregation switch The following options are also available Manage Unmanage Unmanaged switches appear in the fabric but are not actively managed A switch mu
122. ic Deploy Fabric t7 View Deployment Progress Learn More x 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 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 Related links designing a Layer 2 VLT fabric Overview of VLT Key Considerations fo Designing a VLT Fabric Selecting a Layer 2 VLT and Layer 3 with Resiliency Routed VLT Fabric Design Related links for designing a Layer 3 distributed core fabric Overview of a Distributed Core Terminology Designing a Distributed Core 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 P Configure the following settings TFTP FTP SNMP CLI Credentials Prepare the Fabric for Deployment Deploy and Validate the Fabric Validate the deployed fabric against the fabric design PS c m Monitor the fabric health and performance See Pe
123. ic Name gt Switch Name gt Summary screen 2 Click the Performance tab at the bottom of the screen ES Active Fabric Manager re gt Spine t Alerts and Events Performance Troubleshoot Replace Switch southcore Spine 1 Port 0 Interval seconds 15 Traffic Uttization Errors Q Traffic Errors Figure 59 Display Detailed Port Performance 3 Inthe upper right of the screen select the format to view the data using the Graphical or Tabular options 4 inthe lower left of the screen near the Performance tab select the Real Time Data or Historical Data option The default is real time data For real time data from the Interval seconds pull down menu select the interval to collect real time data 15 30 45 60 seconds For historical data from the Date Range pull down menu select one of the following options Last 12 hours 1 d 1 w or 1 m Data Collection To configure the data collection schedule 1 Navigate to the Jobs gt Data Collection screen 2 Clickthe Schedule Data Collection link The Edit Data Collection window displays 3 Checkthe fabrics to enable data collection 152 4 From the Polling Rate pull down menu select the polling rate a 15 Minutes default b 30 Minutes c 45 minutes d 1 Hour Check the fabric to collect data from Click the OK Threshold Settings To configure the monitoring link bundle and Threshold Crossing Alert TCA between the spine switches and the
124. ic link bandwidth of 80 Gb between the aggregation and access switches you can configure 40 GB for each redundant link on the Fabric Customization screen To configure the deployment type so that you can customize the fabric link bandwidth between the aggregation and access switches 1 Inthe Deployment Topology check one of the following options Layer2 Layer 3 with Resiliency Routed VLT 2 Check the Enabled Link Bandwidth Customization option Fabric Design test nt reduc tior v Deployment Topology amp f abric Type Leer 7 C Layer C Layer 3 with Restency Routed VLT Advanced Options z J sa e o y 2 I o 8 a eo 4 of Back Next Spee and Exit Cance Figure 31 Enabled Link Bandwidth Customization Option 3 Inthe Fabric Link Core Aggregation and aggregation and Access option only the applicable options for a select topology are configurable select the fabric bandwidth value from the Aggregation and Access pull down menu For example for 2 tier topology selecting the 120 Gb bandwidth option allows you to later customize the bandwidth from 20 to 120 Gb in increments of 20 Gb in the Fabric Customization screen 4 Click the Refresh Deployment Type button 68 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 Confi
125. igured Step 4 of 11 Back Next Save and Exit To create port channels to increase bandwidth and redundancy Navigate to the Network gt Fabric Name gt Configure and Deploy screen From the Deploy Fabric pull down menu select the Pre deployment Configuration option 1 2 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 For more port channel configuration options refer to the Port Channel Configuration Options table for more information 6 Click Next to go to the Downlink Port Configuration screen Pre deployment Step 1d Downlink Port Configuration Layer 2 VLT To add VLANs and associate ports on the different switches for a Layer 2 fabric use the Downlink Port Configuration screen Once that is done you can copy switch VLAN or port VLAN configurations You can be associate one or more tagged VLANs with a port and for untagged VLAN only one is allowed For information about Downlinks see VLT Terminology Table 19 Downlink Port Configuration Layer 2 Field Descriptions Configured VLANs Displays list of VLANs specified in the VLT VLAN Configuration screen Port Name Displays the port name This a read onlyfield Tagged VLANs Tagged VLANs Manual Enty Manual Enty 0 90
126. ing options a All Associates the template to all the switches in the fabric b Aggregation Associates the template to all the aggregation switches c Access Associates the template to all the access switches d Core Associates the template to all the core switches e Spines Associates template to all the spine switches f Leafs Associates template to all the leaf switches g Custom Associates template with specific switches In the Available Switches select the switches that you want to associate the template with 9 Clickthe Apply button Adding a Switch Specific Custom Configuration Before editing the existing configuration backup the existing running configuration in the flash with a unique name consisting of the date and time To create and apply a customized switch specific configuration and deploy it 1 Navigate to the Network gt Fabric Name gt Configure and Deploy screen 2 From the Deploy Fabric pull down select the Deploy and Validate option 3 On the Deploy tab select the Advanced Configuration link and then click the Add Switch Specific Custom Configuration link 113 8 9 The Switch Specific Custom Configuration screen displays Switch Specific Custom Configuration Select switch Switch Name centraicore Spine 1 Y Autogenerated Configuration centralcore Spine please wait loading gt Associated Templates Switch Specific Custom Configuration conf
127. ion To active the software in the standby partition of the switch 1 2 Navigate to the Jobs Scheduled Jobs screen From the Add pull down menu select the Switch Software Activation option The Activate Standby partition screen displays In the Job Name field enter the name of the job Optional In the Description field enter a description of the job Click the Next button The Switch Select screen displays In the Available Switches area select the fabric and then the switches to update 2Tier distributed core filtering options All Spine and Leaves 2Tier VLT options All Aggregation and Access Stier filtering options All Core Aggregation and Access Click the gt gt button to move the selected switches into the Selected area and then click the Next button The Schedule screen displays Select one of the following options and then click the Next button RunNow Actives the standby partition immediately 165 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 As part of ongoing data center operat
128. ions you must periodically update the software and configurations in the fabric You can update one or more switches Specify the location to get the software updates and then schedule the updates load immediately or schedule it for a later date and time To schedule switch software updates 1 Navigate to the Network gt Fabric Name gt Maintenance screen Click the Update Software button Click the Schedule Switch Software Update link Job Name P oO M Inthe Job Name field enter a unique name for the software job Optionally In the Description field enter a description for the schedule software update The Select Switches screen displays 5 Switch Select a Inthe Available area select the fabric and then the switches to update Tier distributed core filtering options All Spine and Leaves 2TierVLT options All Aggregation and Access Stier filtering options All Core Aggregation and Access b Click the gt gt button to move the selected switches to the Selected Switches area c Click Next e n the Update Location Select the TFTP or FTP site for the software updates using the Edit TFTP or FTP settings link Enter the path and image name of the software file on the TFTP or FTP site for each type of switch Click the Next button M n Update Option Select one of the following options Manual Update is staged to the secondary partition but not applied Automatic
129. istorical Acknowledge Unacknowledge Clear Severity Source P Source Name Dexcrigtion Ack Date Address b Waming 1016 148 201 Stack Replacement Validation failed because fortyGigl 0 52 has a misting link found switch No M Agireqition 2 Stack Replacement Aggregation 2 09 30 Ah warming 10 26 148 201 tech Replacement vals n fated becaus 48 has a 0 c found ze tch e 1 01 Aggregation d Stack Replacement a Wanin 10 104 148 201 Stach Replacement Validation failed bec sur Gott thermet 0 3 has a missing nk found switch No 2 Sara Aggregation 2 Stack Replacement Aggrega tio A waning 101614201 Stack Replacement Validation failed becaute Te bitf thernet 0 1 has a missing tink found pwitch Agp egidon 2 tack Replacement Aggregation Figure 57 Switch Alerts 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 mb o0 Ur ox 8 In the Severity pull down menu select one of the following filtering criteria a All b Critical c Major d Minor e Cleared f Warning g Unknown h Info i Indeterminate In the Source IP field enter the source IP address In the Source Name field enter the source name In the Description field enter a description In the Ack acknowledgement pull down menu select one of the following a All b Yes c No Click the Apply button Historical Alerts a
130. itches in the fabric e Allthe core switches 117 All the switches in the fabric All the leafs in the fabric All the spines in the fabric To add templates 1 SR S JS w 7 Navigate to the Network gt Fabric gt Configure and Deploy screen From the CLI Configuration pull down select the Associate Template option The Templates screen displays Click the Add Template link In the Template Name field specify a unique name for the template Optional In the Description field enter a description of the template In the Configuration Commands area enter the CLI FTOS configuration commands that you want to include in the template Click the OK button For information about how to associate a template to a switch or fabric see Associating Templates Editing Templates To edit templates 1 Navigate to the Network gt Fabric Configure and Deploy screen 2 From the CLI Configuration pull down menu select the Manage Templates option The Templates screen displays 3 Selectthe template that you want to edit 4 Click the Edit Template link The Edit Template window displays 5 Optional In the Template Name field enter a description of the template 6 Inthe Configuration Commands area edit the CLI FTOS configuration 7 Click the OK button Deleting Templates Before you delete a template make sure that template is not being used You cannot delete a template when it is associated wi
131. k the Next button 9 From the Schedule screen select one of the following options and then click the Next button Run Now Schedule the job to run immediately Schedule job to start on Schedule the job to run at later time 10 Review the Summary settings and click the Finished button Scheduling a Back Up Switch Configuration To schedule the number of days to keep the switch backup files in the AFM 1 Navigate to the Network gt Fabric Name gt Maintenance screen 2 Clickthe Switch Backup button to display the switch backup options 3 Clickthe Switch Backup link The Job Name screen displays 4 nthe Name field enter the name of the software job name 5 Inthe Description field optionally enter a description and then click the Next button The Select Switches screen displays 6 Navigate to the Available area a From the Switch Type pull down menu select the type of switches to update b Inthe Available Switches area select the switches to update 167 2Tier distributed core filtering options All Spine and Leaves 2TierVLT options All Aggregation and Access Stier filtering options All Core Aggregation and Access c Click the gt gt button to move the selected switches to the Selected Switches area and then click the Next button The Schedule screen displays 7 Inthe Start area select one of the following options Run Now Run the job now Schedule
132. l cost multi pathing capabilities For information about supported tiers see Selecting a Layer 2 VLT and Layer 3 with Resiliency Routed VLT Fabric Design See also Deployment Topology Use Cases For information about tiers see Deployment Topology To design a fabric based on the capacity requirements for your current and future needs use the fabric design wizard at the Network gt Configure Fabric gt Design New Fabric screen When you first start AFM it starts the Getting Started configuration wizard in the Welcome to Active Fabric Manager screen Getting Started Dashboard Getting Started Welcome to Active Fabric Manager Deploy and manage your fabric infrastructure Ry Step 1 Design the Fabric Import a copy of an existing fabric design design a new fabric or edit a started design Fabric design and edits are based on current workload requirements and future needs Import Existing Design Design New Fabric Edit Existing Fabric View or Print Wiring Plan Learn More 2 Le Step 2 Pre Deployment Configuration Ay Configure networking settings Management IP and system MAC addresses for each node and generate a DHCP configuration file to add to your existing DHCP service SEET Configuration Learn More ey Step 3 Deploy the Fabric Deploy and Validate each switch associated with a fabric Deploy Fabric View Deployment Progress Learn More m Figure 4 Getting Started Welcome to Active Fabric Ma
133. lacing a Switch To decommission a switch 6 Navigate to the Network gt Fabric Name gt Switch Name Click the Switch Replacement tab The Switch Replacement Summary screen displays Click the Decommission Switch link The Decommission Switch screen is displayed Review and follow the instructions on the Decommission screen Click the Save button to save the text file that contains information to submit a Return Material Authorization RMA Send this information to your Dell Networking software support representative to arrange switch replacement at the iSupport Portal at http www force10networks com support Once a replacement switch is available click the Replace Switch link Step 2 Replacing a Switch Pre requisites Before you replace a switch gather the following useful information Obtain the system MAC address service tag and serial number for the new switch to be used for replacement provided from Dell Location of the switch including the rack and row number from your network administrator or operator Remote Trivial File Transfer Protocol TFTP File Transfer Protocol FTP address from your network administrator or operation Last deployed FTOS Software Image for switch being replaced should be on the TFTP FTP site The software images on the TFTP FTP site is used by the switch to install the appropriate FTOS software image and configuration file Dynamic Host Configuration Protocol DHCP server c
134. lect the Deploy and Validate option On the Deploy tab select the Advanced Configuration link and then click the Add Switch Specific Custom Configuration link The Switch Specific Custom Configuration screen displays Switch Specific Custom Configuration Select switch Switch Name centralcore Spine 1 Autogenerated Configuration centralcore Spine please wait loading gt Associated Templates Y Switch Specific Custom Configuration conf s conf end Y View Configuration Combined Autogenerated and Custom Configuration View Save To Last committed configuration on the switch View Save To 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 Enter the switch specific custom configuration FTOS CLI commands in the Switch Specific Custom Configuration area Under the View Configuration heading click the View button next to the Preview the combined auto generated and custom configuration This option allows you to view the auto generated configuration global custom configuration and switch specific configuration The View Combined Configuration screen displays To view the last applied configuration or save it click the View button or Save To button nex
135. link Bandwidth UL BW Uplink Bandwidth i Attention The maximum number of downlinks is based on using 2 uplinks Table 1 2 Tier Layer 3 Distributed Core Topologies Type 0S DL Maximum Maximum Maximum UL Fabric Link Possible Ratio BW of of Spine ofLeaf BW Bandwidth Topologies Spine Downlink Devices Devices Between and Leaf the Spine and Leaf Type 1 Extra Large 10G 2046 40G Z9000 Z9000 or Core S6000 S6000 Type 2 Large Core mi Im 2046 4810 S4810 E EN p f Type 3 Medium 3 1 10G 766 32 4810 S4810 Core Type 3 Medium 10G 1662 Z9000 S4810 or Core 6000 S4810 Type 1 Extra Large Distributed Core Fabric With a Type 1 Extra Large Distributed Core fabric design the 29000 spines or S6000 spines connect to the 29000 leaves S6000 leaves at a fixed 40 Gb line rate The maximum number of leaves is based on the maximum number of ports on the spine 32 ports for the 29000 as shown in the following figure 10G 4810 S4810 Z9000 S4810 or 6000 S4810 26 Type 1 Extra Large Core Distributed Core Fabric i ES RS BEE wt 16 spines up to 32 leaves 10 Gb leaf downlinks and uplinks Layer 2 servers Function Spine Leaf Fabricinterlinks 40 Gb For line rate performance for spine and leaves NOTE The AFM does not configure or manage anything beyond the distributed core fabric Figure 5 Type 1 Extra Large Distributed Core Fabric Design Us
136. logy Graphical View Fabric Summaly xoa a ni n ea En na vri debed ia a iere e aiv sea Depas Displaying the Fabric in a Tabular View 127 Displaying the Fabric in a Graphical View 128 SWITCH SUMM ALY AERE 129 HMA ce Ter EE 131 Ping Traceroute SSH and Telnats orto et oti eee cer edere tte dme Ee a 131 NU EE 131 Traceroute ddi aaar 131 SSH ee r AE ee ieee 131 ZE EE 132 Valid ation El TEE 132 Deployment and Validation Errors EEN 134 Pr deployMent EITOrS eet oko o e Ce pee eMe pure ettet eats debes Mal ee ede et 134 De ployment ErTOLS s oce occus et e igneo rere dep e aee tere encre e Rt pote ane dara aa Ee RR CE Rd Ee 134 Validation Or 135 Switch Deployment Status Errors EEN 138 TETP ETP TE 143 Validating Connectivity to the Tab 143 10 Alerts bau rM Current Active Alerts cicer er dere riri eda e ten epe edet Pede aha eden aada aaia vaada raia Historical Alerts and Event History 11 Performance Management eese seien entente tert tn tarta tata ta tarta satanas ds 149 Network Performance Management 149 Fabric Performance Management 150 Switch Performance Management 150 Port Performance Management Detailed Port Performance Management 151 Data CollectiQn z cis ect reto dere eves Roe Ee tror De D pe orare dk e eet Ae ch gege EE Editing Reports SERERE EP Running Reports BITTER
137. lot of bandwidth and not a lot of ports The following image illustrates a distributed core fabric 23 Type 1 Extra Large Core Distributed Core Fabric 29000 8 Ei ooo E switches i BEES oco ERE up to 16 spines 7A up to 32 leaves 10 Gb leaf downlinks and uplinks ATTO PE For line rate performance for spine and leaves Layer 2 il n NOTE The AFM does not configure or manage anything beyond the distributed core fabric o gt 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 e You can deploy up to 10 fabrics However the fabrics do not communicate with each other e AFM manages Dell 4810 S4820T S6000 and 29000 switches A CAUTION If you are already using a deployed switch reset the factory settings The switch must be in BMP mode For information on BMP see DHCP Integration and the F70S Configuration Guide for either the 4810 S4820T S6000 or Z9000 switches at https www force10networks com CSPortal20 KnowledgeBase Documentation aspx See also Deployment Topology Use Cases The number and type of spines and leaves switches in a distributed core fabric are based on the following e The type of distributed core fabric design Type 1 Extra Large Core Type 2 Large Core
138. lowed in Each Fabric State 80 Using the Pre deployment Wizard NEEN 82 l ayer 2 VLT Fabric Pre deployImiert occe oerte eerte rien m eene e tite en eR Uere eie 82 Layer 3 Distributed Core Fabric Pre deployment EE 82 Layer 3 with Resiliency Routed VLT Pre Deployment Configuration EEN Protocol Configuration Layer 2 VLT Fabric Step 85 Protocol Configuration Layer 3 Distributed Core Fabric Sien 92 Protocol Configuration Layer 3 with Resiliency Routed VLT Step 1 esses 94 Pre deployment Step 2 Assign Switch Identities essere tnn Pre Deployment Step 3 Management IP ENEE Pre Deployment Step 4 SNMP and CLI Credentials Pre Deployment Step 5 Software Images EEN Pre Deployment Step 6 DHCP Integration esses eene tentent tnter nnne nter enin Pre Deployment Step 7 Summary sese essent terne tnter nte ntn tnt tine tent tenen Viewing the DHCP Configuration File Deploying and Validating the Fabrice Deploying the Ge Advanced Configuration Validation Ma A Ea EE Viewing Deployment and Validation Status Custom CLI Configuration Zeie Managing Templates CERES Associating CO Adding a Switch Specific Custom Configuration E Viewing Custom Configuration Histon EE 8 Viewing tig EE DERI ana Ai ee i eR i aie i ed eet ee yos en APTE Network Topology Tabular View Network Topo
139. mation Deployment Required Indicates that deployment was never initiated for the switch or the Deployment state was reset due to Design Pre deployment Configuration change K NOTE Deployment can be initiated re initiated only if Pre deployment Configuration is in state Complete In progress Indicates that Deployment is in progress and also provides the latest percentage complete information Indicates that one or more validation error exists Complete Indicates that validation was successful for the switch Using the Fabric Design Wizard Use the Fabric Design Wizard at the Network gt Design Fabric gt New Fabric screen to design the following types of customized fabrics based on your workload requirements for your current and future needs e Layer 2 Use the Layer 2 VLT fabric for workload migration over virtualized environments See VLT and Selecting a Layer 2 and Layer 3 with Resiliency Routed VLT fabric 51 Layer 3 distributed core Use the Layer 3 distributed core for large fabric deployments See Conventional Core Versus Distributed Core e 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 K NOTE You can also use the Fabric Design Wizard from the Home gt Design New Fabric screen Use the following screens to
140. n is given to your data center operator who uses this information to build the physical network according to the fabric design The fabric design is displayed in the following formats 72 e Graphical Wiring Plan Displays information about how the switches are connected graphically Legend s Designed ged Deployed Future southcore Access 1 Model S4810 DOG LL e X AE xxx 21 TE IE 3 ag At 3 el ed 3 3e aei 3ag 36 1 38 1 3 Q EEEE E SEELESS EEEEEE amp 5s AS SS S amp ei EE 222 i zzz oo o 9 aaa 8 st pont 13 m Down port 15 T Down port 17 en Z Down port 19 e 2 Down port 21 me Down por25 L Down port 27 J Down port 29 13 Down potzi m Down port 33 m Down por 35 3 Down port 37 Down port 39 me Down port 43 i Down port 45 port 47 Downi Be Downlink Downlink Be Downlink E Downlink P Downlink v O Mi SHEI 2 2 port 52 port 60 port 28 DR port 30 port 20 DR port 22 port 10 DR port 12 port 48 port 56 port 0 porto Gs port 2 Dem port 4 Desen port 6 Qs port 8 CO port 14 Gs port 16 es port 18 CO port 24 Qs port 26 es port 32 O port 34 DR pori 35 D port 38 Den port 40 O port 42 Dk port 44 Fes port 46 E HHH 999 GK eis t fir SETTE amp SSEEEE SS SS SS SS SS t ok aHHHHHIEBHHHBHIEHHBHBHIEHBBHHE 43 ejejejere GA OO OO OO OO OO OO CO OD OO OO O e Network Topology
141. n 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 Review the values and then click the Next button to go to the Deployment Topology screen Deployment Topology Use Cases Use the following use cases as a guide to select a deployment topology Use Case 1 1 Tier Layer 2 Fabric Use Case 2 1 Tier Layer 3 with Resiliency Routed VLT Use Case 3 2 tier Layer 3 Distributed Core Use Case 4 2 Tier Layer 3 Resiliency Routed VLT Use Case 5 3 Tier Layer 2 Use Case 6 3 Tier Layer 3 Resiliency Routed VLT Use Case 1 1 Tier Layer 2 Fabric When you select a 1 Tier Layer 2 fabric The uplinks between the 2 aggregation switches and external switch WAN supports the Layer 3 protocol OSPF iBGP or eBGP 55 e 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 introduction v Deployment Topology Fabric Name and Type e Fabric Type 9 Layer 2 Layer 3 Layer 3 with ResBency Routed VLT Bandwidth and Port Count v DEn C v Deployment Type Tier Aggregation JS Lier Aggrega
142. n the deployment topology that contains the appropriate core switches and aggregation switch type that you want in your fabric and for a Layer 3 distributed core fabric the over subscription ratio 4 Optional Click the Advanced Options to configure VLTi links and fabric links a VLTi and Fabric Link options VLTi link e Core Specify the number of links and bandwidth Aggregation Specify the number of links and bandwidth e Access Specify the number of links and bandwidth Fabric Link e Core and Aggregation Specify the bandwidth e Aggregation and Access Specify the bandwidth b Click the Refresh Deployment Type button to apply the Advanced Options to view the new deployment topologies 70 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 Fabric Design routed_VLT Introduction v Deployment Topology o Fabric Name and Type v Filter option icog Bandwidth and Port Count w b Advanced Options gt Deployment Topology Deployment Type Filter 2 Tier A ation Access rri 54810 10Gb Cable Type for Access Tier el Mixed Node Stacking Restiency in Access Devices e Stacked Non Stacked Le Clear Apply Fabric Link Bandwidth Fabric Link Bandwidth Aggregation and Access per stack
143. nager Screen 19 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 e You can deploy up to 10 fabrics However the fabrics do not communicate with each other e AFM manages Dell Networking 4810 S4820T S6000 and Z9000 switches A CAUTION If you are already using a deployed switch you must reset the factory settings The switch must be in BMP mode For more information on BMP see DHCP Integration and the F70S Configuration Guide for the Dell Networking 4810 4820T S6000 and Z9000 switches at https www force10networks com CSPortal20 KnowledgeBase Documentation aspx The number and type of switches in a Layer 3 with Resiliency Routed VLT fabric are based on the following e The number of current uplinks minimum of 2 and downlinks for the access switches e The number of planned edge ports future uplinks and downlinks for the access switches e Whether the access switches need to act as a ToR or access e Fabric interlink bandwidth the links between the aggregation and access switches e Downlinks which can be 1Gb 10Gb or 40 Gb e The fabric interlink bandwidth 10 Gb or 40 Gb is fixed and based on the fabric type A CAUTION If you do not specify additional links in the fabric design for future expansi
144. nd Event History To view historical events at the network fabric or switch level use Alerts and Events screen To filter active alerts at the network level navigate to the Network gt Alerts and Events screen To filter active alerts at the network level navigate to the Network gt Fabric Name gt Alerts and Events screen To filter active alerts at the switch level navigate to the Network gt Fabric Name gt Switch Name gt Alerts and Events screen To filter historical events Click the Historical button Click the filtering icon You can use the filter options from date and to date The filtering options display In the Severity pull down menu select one of the following filtering criteria a All b Critical c Major d Minor e Warning f Cleared g Unknown h Info i Indeterminate In the Source IP field enter the source IP address In the Source Name field enter the source name In the Description field enter the description 147 7 Inthe Ack acknowledgement pull down menu select one of the following a All b Yes c No Click the Apply button If you want to export your results click the Export link 148 11 Performance Management You can monitor performance at the network fabric switch and port level This section contains the following topics e Network Performance Management e Fabric Performance Management e Switch Performance Management e Port Performanc
145. nfigure and Deploy screen From the Deploy Fabric pull down menu select the Deploy and Validate option On the Deploy tab click the Advanced Configuration link Click the Preview Combined Configuration screen The Combined Configuration screen displays Validation To verify that the discovered fabric matches the planned fabric and correct any errors use the Validate screen Mismatches are reported as errors and the corresponding alarms generate If you fix the errors found during validation to verify that all the issues were fixed according to the planned fabric validate the fabric again Validation Status 3 Error HOSTNAME MAC Address MODEL Check for switch mismatch errors Mismatch Navigate to the Network gt Fabric Name Configure and Deployment screen Click the Errors link Click on the Discovered Errors tab to view error details Fix any errors Error HOSTNAME MAC Address MODEL Check for switch mismatch errors Mismatch and STANDBY UNIT down Navigate to the Network gt Fabric Name Configure and Deployment screen Click the Errors link Click on the Discovered Errors tab to view error details Fix any errors 2 Error STANDBY UNIT down Navigate to the Network gt Fabric Name gt Configure and Deployment screen Click the Errors link A Click on the Discovered Errors tab to view error details Fix any errors Error Switch is not reachable Verify the switch connectivity from th
146. o the Administration Settings User Accounts screen Click on the user to edit Click Edit The Edit User Settings screen displays In the First Name field enter the user s first name Sp o zl oa g 11 12 In the Last Name enter the user s last name In the Password field enter the user s password In the Confirm Password field enter the user s password In the Sessions Allowed pull down menu specify the number sessions allowed for the user In the Session Timeout pull down menu specify one of the following timeout values a 15 minutes b 30 minutes c 45 minutes d 60 minutes In the Unsuccessful Login Limit pull down menu select the number of allowed unsuccessful logins 3 to 10 From the Lockout Duration pull down menu select one the following options a 15 minutes b 30 minutes c 45 minutes d 60 minutes e Permanent Click OK Unlocking a User To unlock a user you must be a Superuser For information about user accounts see Managing User Accounts To unlock a user 1 2 3 4 Navigate to the Administration gt Users Accounts screen Select the user you want to unlock Click the Unlock button Click OK Changing Your Password To change your password 1 Go to the upper right of the screen next to your login name A pull down menu displays Select Change Password The Change Current Account Password screen displays In the Current Password field enter your cu
147. o the Network gt Fabric gt 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 gt Switch gt Graphic view Click the Launch Active Link link The Active Link displays the selected switch view and performance charts Navigate to the Network gt Switch gt Tabular view Click the Launch Active Link link The Active Link displays the selected switch view and performance charts To configure active link settings Navigate to the Administration gt Settings screen Navigate to the Active Link Settings area and click the Edit link In the Active Link area check the Integrate to Dell OpenManage Network Manager OMNM option to display additional performance statistics In the Active Link System IP Address field specify the Active Link server IP address of the element management system In the Communication Protocol area select one of the following protocols Use HTTP protocol to connect through AFM Server Use HTTPS protocol to connect through AFM Server In the User Name specify the Active Link user name In the Password field specify the Active Link user password Click the OK button CLI Credentials To provision the fabric enter the FTOS CLI user s credential and enable the configuration credential for all the switches in the fabric This option allows
148. ociates the template to all the core switches Custom Associates the template with specific switches In the Available Switches select the switches to associate to the template 119 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 E gg P WY Im Navigate to the Network gt Fabric gt Configure and Deploy screen From the CLI Configuration pull down menu select the Associate Templates option Select the template to edit the association Click the Edit Association link Edit the association Click the OK button Deleting Template Associations To delete a template association 1 g9 P WO DN Navigate to the Network gt Fabric gt Configure and Deploy screen From the CLI Configuration pull down menu select the Associate Templates option Select the template to delete the association Click the Delete link Click the OK button Adding a Switch Specific Custom Configuration Before editing the existing configuration backup the existing running configuration in the flash with a unique name consisting of the date and time To create and apply a customized switch specific configuration and deploy it 1 2 3 120 Navigate to the Network gt Fabric Name gt Configure and Deploy screen From the Deploy Fabric pull down se
149. ode is yellow or red the AFM displays an alarm at the Network gt Fabric Name gt Switch Name gt Alerts and Events gt Current screen Related links e Alerts Monitor Network Topology To display all the fabrics in the network topology in graphical or tabular view use the Network Summary screen The network topology view contains a collection of fabric icons with status color coded and fabric names There are no links between fabrics Network Topology Tabular View Navigate to the Network Summary screen and then click the Tabular tab 125 Active Fabric Manager superuser Help V Network deci sud te tems l northcore Network E Graphical southcore westcore_482 westcore eastcore southcore centralcore southcore Details Status Active Alerts Total Nodes Figure 54 Network Summary Tabular View Network Topology Graphical View user V Help Y Network Alerts and Events Performance southcore northcore Network westcore 482 Background Map Actions Y Topology Options westcore t Show Tooltips eastcore Enable Move mn LII estcore_4820T southcore northcor centralcore Revert to Last Saved Save Move southcore Details Status Active Alerts Total Nodes The network topology contains fabric icons Each fabric icon has the following functions e Status Displays the status of the fabric using the following colors Red Critical alerts Orang
150. ology fabric Nase and Tyce fab Type Layer 2 Layer 3 Baese th and Port Count y Deployment Type 1 Twr Aggregation Access 4110 4410 Fixed Node Stac king eas dcm ele ole ae othe e em e eem Fabric Link Bandan Aggregation and Access per stack 20 68 Maximum A vattable Downin Port 7970 Access Switch 4810 oe 348201 Stacking enabled i Acces Yet Figure 18 Layer 3 with Resiliency Routed VLT with Basic Option O Layer J wih esibency Routes VLT I Tier Aggregation Access 54810 4410 Mined Mode Reubeek y VLT b oo ae coe Fazei Link Bandwidth Aggregation and Access 20 Gb Paxmm Available Downlink Ports 2914 Accon Switcte 14800 or S548207 Reuiency m Accent gecft ber Yer Zier Aggrequbon Access Sang sam Pines Mode Baue Fabete Link Bandvadth Aggregation exi Access 20 Gb Faxon Available Downlink Portu 240 Access Switch 4190 or 43207 Layer 3 with Resiliency Routed VLT with MXL Blade with interChassis option With this topology you selectthe Deployment Type that has a MXL Blade switch with Resiliency VLT and Interchassis across Chassis resiliency Enter the VLAN ID and the IP range When you complete the pre deployment configuration the Advanced VLAN IP Configuration option is available atthe Configure and Deploy Summary screen v Deployment Topology v Fabric Type Layer 2 Layer 3 with Restiency Routed VLT nt v T TT v De
151. on in the Bandwidth and Port Count screen you can only expand the downlinks on the existing fabric For information on how to expand a fabric see Editing and Expanding an Existing Fabric Design For information about tiers see Deployment Topology See also Deployment Topology Use Cases Gathering Useful Information for a Layer 3 with Resiliency Routed VLT Fabric To gather useful information for a Layer 3 with Resiliency Routed 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 e Obtain the location of the switches including the rack and row number from your network administrator or network operator e Obtain the remote Trivial File Transfer Protocol TFTP File Transfer Protocol FTP address from your network administrator or network operator To specify a TFTP FTP site go to Administration gt Settings gt TFTP FTP screen For information about which software packages to use see the Release Notes e Download 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 Place the software images on the TFTP FTP site so that the switches can install the appropriate FTOS software image and configuration file e Obtain the Dynamic Host Configuration Protocol DHCP server address to use for the
152. on on the server but will not be applied This option does not cause a restart You must manually triggered the update from the AFM server server update page Apply Installation and Restart Server The update is copied to the standby partition on the server The update is applied and the restart automatically occurs once the update completes Click the Update button Activating the AFM Standby Partition Navigate to the Administration gt Update Server screen and then click the Activate Available Partition link 161 162 13 Jobs This section contains the following topics Displaying Job Results e Scheduling Jobs Displaying Job Results To display the status of your jobs use the Job Results screen 1 Navigate to the Jobs gt Jobs Results screen 2 Inthe upper right of the screen click the filter icon to filter your job results 3 Inthe Job Name field enter the job name 4 Inthe Status pull down menu select one of the following filtering options Al Success Failure In Progress 5 Inthe Start From area click the select date and time icon to specify the start from date 6 Inthe Start To area click the select date and time icon to specify the start to date 7 Inthe End Date From area click the select date and time icon to specify the end date from 8 Inthe End Date to area click the select date and time icon to specify the end date to 9 Click the Apply button Scheduling Jobs To
153. onfiguration will need update If remote DHCP server is used then you need to manually update the same based on configuration provided by AFM If local DHCP server is used AFM will update the DHCP server automatically After you power cycle the switches the switches communicate with the DHCP server to obtain an 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 bare metal provisioning BMP To replace a switch 1 2 3 4 Navigate to the Network gt Fabric Name Switch Name screen Click the Switch Replacement tab and then click the Replace Switch link Review the introduction and instructions on the Switch Cabling screen Confirm that the replacement switch is racked cabled and powered on If this is not the case use the following wiring diagram to cable the replacement switch Click the Next button The MAC Replacement screen displays In the MAC Replacement screen enter the following information for the replacement switch a The new serial number in the New Serial Number field b The new service tag in the New Service Tag field c The new system MAC address for the replacement switch in the New MAC address field 159 11 Click the Next button The DHCP screen is displayed Save the replacement switch DHCP configuration file Review the Summary screen and
154. onsiderations for Designing a Layer 2 VLT Fabric Gathering Useful Information for a Layer 2 VLT Fabien Selecting a Layer 2 and Layer 3 with Resiliency Routed VLT Fabric Design 34 6 Designing die Fakt castes ii chee Roten Dra o Por ub odes ri EE M at ia Network Deployment Summary Fabric Configuration Phases and States Switch Configuration Phases and States 51 Using the Fabric Design Wizards 2 5 rg tacet tette e tee de heo EE 51 Fabric Design Step 1 Fabric Name and Type 52 Fabric Design Step 2 Bandwidth and Port Coumt EE 53 Deployment Topology Use Cases ENEE 55 Fabric Design Step 3 Deployment Topology EE 65 Fabric Design Step 3 Fabric Customtsaton EE 71 Fabric Design Stepb DEES ccd innit eo ee ete eb peat cbr aedis debo aee baleen Fabric Design Step 6 Summary Importing an Existing Fabric Design Editing and Expanding an Existing Fabric Design c ccsssssssssssesescsesssesesesesscesscsescsescsesesesssesseesacseseseseaeseseseueseees 77 Deleting the Fabric eee sca ec ett Hehe ead EES 77 Viewing the Wiring Diagram sess eee ntnt tnt rnnt tnnt eneas feae aaa r airada aana eoan sas sess 71 7 Configuring and Deploying the Fabric ccsssssssssssssessesessssssesesessessesesssseesesassnssesassees 79 Fabric Deployment SUimtmaly ioci eterne ecu rete tpe trek de nee pec nee ERE nat pne ara rea aaa ue DRE daa Ra da e Rd ue 8 79 Switch Configuration Phases and States 79 Operations Al
155. ort 143 144 10 Alerts and Events This section contains the following topics e Current Active Alerts e 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 selectthe 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 To unacknowledge an active alert select the active alert and then click the Unacknowledge button You can also clear active alerts To filter active alerts at the network level navigate to the Network gt Alerts and Events screen ctive Fabric Manac Networx Summary Alerts and Everts Pedormance Design Fabric Alerts and Event Acknowledge Unacnowledge Clear Stack Reolacem Source In Severity Adde Source Name Description S55StkB101 7 AUT d Aggregation 2 Stack fiegleccmcnt Aggregation 2 DCS481054810 Wanin 10 16 148 201 Stacl Reglacemeet Validation faled because TenGigabitf thernet 0 3 has a missing Enk ound switch d ES Aggregation 2 Stack Replscoment Aggregs ton redeplo G e Wanin 10 16 148 201 Stack Replacement Validation faled because TenGigabitf thernet 0 1 has missing ink ound switch Addi lag Ageregatinn Stack Replacement Aggregation Addvtan y Major 10 16 148 4 D
156. out this option see Scheduling a Back Up Switch Configuration Edit Description Edits the description of the backup After you have created a back up you can then edit the description of the backup configuration Restore Restores either the startup configuration default or running configuration that has been backed up earlier Delete Deletes a backup configuration Restoring a Switch Configuration To either restore the startup configuration default or running configuration that has been backed up earlier 1 oo Sa qe 6 Navigate to the Network gt Fabric Name gt Maintenance screen Click the Switch Backup button to display the switch backup options Select a backup switch configuration to restore Click the Restore link Select one of the following restore options Restore Startup Config default Restore Running Config Click the OK button Deleting a Backup Configuration To delete a switch backup configuration 157 1 Navigate to the Network gt Fabric Name gt Maintenance screen Click the Switch Backup button to display the switch backup options Select a backup switch configuration to delete Click the Delete link to delete the switch backup configuration Click the Yes button a 4 Sa b Editing Description To edit a switch backup description 1 Navigate to the Network gt Fabric Name gt Maintenance screen Click the Switch Backup button to display the switch back
157. oyment Topology gt Fabric Customization screen 2 From the Fabric Link Bandwidth pull down menu select the fabric link bandwidth for each access switch Fabric Design myfabric Introduction v Fabric Customization Fabric Name and Type v Select preferred switch model and fabric link bandwidth for applicable switches Fabric Link Bandwidth Bandwidth and Port Count v Switch Name Gb Rote Usage Deployment Topology v Aggregation 1 Aggregation 2 Aggregation Designed Access 3 Access 4 80 j Acce Nestgned Acceit Si Acom CV j Acce vertgned Acoets 7 Aecess 8 50 Acce Designed 5 Item s found Displaying 1 5 Note Decreasing Fabric Link Bandwidth will increase the number of Downtnks tep Sof Back Next Save and Exit 3 Click the Next button to go the Output screen Fabric Design Step 5 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 the AFM calculates the number of switches required for the design and displays the physical wiring plan which you can export and print in PDF or Microsoft Visio 2010 The wiring plans display the cabling maps the connections between the switches and the switches and links for current and future expansion Review the wiring plan and then export it to a file Typically after the fabric design is approved the wiring pla
158. pe of switch The DHCP server also uses this file to assign a management IP address to each switch K NOTE Install the DHCP configuration file on the DHCP server before you deploy the fabric Downlink Port Configuration for a Layer 2 VLT fabric or Layer 3 with Resiliency Routed VLT Associates each of the ports of a access switch to one or more VLANs You can associated one or more tagged VLANs and for an untagged VLAN only one is allowed Downlink Configuration for a Layer 3 Distributed Core or Layer 3 with Resiliency Routed VLT fabric An edge port that connects to the access layer for example servers or a ToR Fabric link Configuration for a Layer 3 or Layer 3 with Resiliency Routed VLT fabric For a Layer 3 fabric configures options for the spine and leaf to communicate in the fabric For a Layer 3 with Resiliency Routed VLT fabric the links that connect the core access and aggregation switches in the fabric e Management IP Specifies a management IP address to each switch e Software Images Specifies the TFTP or FTP address local or remote server and the path of the FTOS software image download to each type of switch To stage the software use this address e Output Displays the uplink and downlink configuration on the leaves or access Verify that this information is correct before deploying the switches e Port Channel Configuration Add edit delete and automatically populate the po
159. phases displayed on the Network gt Fabric Name gt Configure and Deploy gt Deploy screen To correct the fabric design and pre deployment configuration before and after you deploy the fabric use this information 49 Table 11 Fabric Configuration Phases and States NN 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 Pre deployment Required Indicates that not all required Pre deployment Configuration information for any Configuration of the switches was provided E NOTE The Pre deployment Configuration state for all switches is in state Required Indicates that deployment error s exist for one or more switches Partial Indicates that Pre deployment was successfully completed for one or more Complete switches but not for all switches per design It provides information about the count of switches successfully deployment versus the count of total switches per design K NOTE Information provided is sufficient to proceed with deployment of the subset of switches Complete Indicates that Pre deployment Configuration information is complete for all switches Deployment Required Indicates that the Deployment state for all switches is in the Required state In progress Indicates that Deployment is In progress the progress bar displays in the UI on one or more switches It also provides information about
160. plays 6 Inthe Available area select the fabric and then switches to backup 2Tier distributed core filtering options All Spine and Leaves 2Tier VLT options All Aggregation and Access Stier filtering options All Core Aggregation and Access 7 Click the gt gt button to move the switches to backup to the Selected Switches area and the click the Next button 8 Onthe Schedule screen select one of the following options Run Now Back ups the switch software immediately Schedule job to start on Specify a date and time to schedule the job to backup the switch software The Summary screen displays 9 Review the settings in the Summary screen and then click the Finish button Switch Software Updates As part of ongoing data center operations you must periodically update the software and configurations in the fabric You can update one or more switches Specify the location from which to get the software updates and then schedule the updates to be performed immediately or schedule it for a later date and time 1 2 164 Navigate to the Jobs Scheduled Jobs screen From the Add pull down menu select the Switch Software Update option The Switch Software Update screen displays In the Job Name field enter the name of the switch software job Optional In the Description field enter a description of the job Click the Next button The Switch Select screen is displayed In the Available area s
161. ployment Type 2 Tier Aggregation Access 2 Tier Aggregation Access rd 4810 MXL 10 MXI Stacking CENE 4 W Fabric Link Bandwidth Fabric Link Bandwidth Aggregation and Access per stack 20Gb Aggregation and Access 20 Gb Maximum Supported Blades 54 Maximum Supported Blades 62 Optional Module Optional Module Port No 41 Bandwidth 10 Gb Port No 41 Bandwidth 10 Gb Stacking enabled in Access Yes Resibency in Access switches Yes Interchassis across Chassis resiliency Yes J d Figure 19 Layer 3 with Resiliency Routed VLT with MXL Blade with interChassis option 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 Introduction v Deployment Topology Fabric Name and Type v 2 Tier Aggregation Access HB TIO MI Bandwidth and Port Count wi Fabric Link Bandwidth Aggregation and Access 20 Gb Maximum Supported Blades 54 Optional Module Port No 41 Bandwidth 10 Gb Intrachassis within Chassis resiliency Yes Figure 20 Layer 3 with Resiliency Routed VLT Blade MXL with IntraChassis option 61 Use Case 5 3 Tier Layer 2 When you select a 3 tier Layer 2 fabric e The fabric links between core and aggrega
162. r 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 58 Fabric Name and Type Bandwidth and Port Count Fabric Type v e Deployment Type I Layer 2 Layer 3 Layer 3 with Resiliency Routed VLT 2 Tier Aggregation Access 4810 4810 Mixed Node Stacking dx xe Aggregation and Access per stack 20 Gb Maximum Available Downlink Ports 2970 Access Switch S4810 or S4820T Stacking enabled in Access Yes Figure 15 Example 2 Tier Layer 3 with Resiliency Routed VLT with Stacking Option 2 Tier Aggregation Access 4810 4810 Mixed Node Resibenc y VLT V Fabric Link Bandwidth Aggregation and Access 20Gb Maximum Available Downlink Ports Access Switch 54810 or S4820T Resiliency in Access switches Yes 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 selectthe Enable Layer 3 Protocol in Access Switches option configure the VLAN ID and then the IP Range When you complete the pre deployment configuration the Advanced VLAN IP Configuration option is available at the Configure and Deploy Summary screen Introduction Fabric
163. r switches have independent management planes A VLT interconnect between the VLT chassis maintains synchronization of Layer 2 and Layer 3 control planes across the two VLT peer switches The VLT interconnect uses either 10 Gb or 40 Gb ports on the switch A separate backup link maintains heartbeat messages across an out of band 00B management network The backup link ensures that node failure conditions are correctly detected and are not confused with failures of the VLT interconnect VLT ensures that local traffic on a chassis does not traverse the VLTi and takes the shortest path to the destination via directly attached links VLT Fabric Terminology The following terms are unique to the design and deployment of a Layer 2 VLT fabric e Core A switch that connects to aggregation switches The role of the core is to provide an interconnect to all the aggregation switches All the ports on the core switch are used to connect the aggregation various rack together e Access A switch that connects switch servers storage devices or top of rack TOR elements The role of the access switch is to provide connectivity to the fabric The access switch connects to all of aggregation switches above it in the fabric 31 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 va
164. r to the AFM Plug in for Openstack Guide After you complete the basic installation of the Active Fabric Manager AFM you must configure it This is done using the Getting Started configuration wizard at the Home gt Getting Started screen After you complete the installation process the AFM automatically launches this wizard The Getting Started configuration wizard provides launch points for designing pre deploying and deploying the fabric Review the steps in the wizard and the online help or AFM Deployment Guide before you begin With this wizard you can also edit and expand an existing fabric design and import an existing design 13 Getting Started Dashboard 9 Getting Started Welcome to Active Fabric Manager Deploy and manage your fabric infrastructure n Step 1 Design the Fabric Import a copy of an existing fabric design design a new fabric or edit a started design Fabric design and edits are based on current workload requirements and future needs Import Existing Design Design New Fabric Edit Existing Fabric m View or Print Wiring Plan Learn More 2 Le Step 2 Pre Deployment Configuration iX Configure networking settings Management IP and system MAC addresses for each node and generate a DHCP configuration file to add to your existing DHCP service Pre deployment Configuration Learn More ey Step 3 Deploy the Fabric Deploy and Validate each switch associated with a fabr
165. rformance Management NOTE To provision the fabric enter the Dell Networking operating system FTOS CLI user s Credentials and enable the configuration credential for all the switches in the fabric For information about this topic see CLI Credentials A CAUTION If you are using a switch that has already been deployed reset its factory settings in the fabric The switch must be in Bare Metal Provision BMP mode Designing and Deploying a Fabric Flowchart The following flowchart shows how to design and deploy a new fabric Design Fabric 1 Select Type of Fabric Layer 2 or 3 Layer 3 Distributed Core Fabric Layer 3 with Resiliency Routed VLT s Layer 2 VLT Fabric Layer 3 only fabric link oversubscription 2 Uplinks and Downlinks CommonL2 L3 Screens Current end future number of ports uplinks to WAN edge Number of ports for the downlinks Port speed for uplinks LOG 40G and downlinks 1G 10G 40Gl 3 Setect Fabric Options Display multiple fabric options based on capacity planning requirements Select fabric type Stack nonstack resiliency in the access 4 Display and Export Wiring Diagram Displaying wiring diagram Export outputs from design phase topology wiring diagram and tabular format 5 Design Complete Send design to Dell representative to obtain quote and order Dell Forcei0 switches Figure 2 Capacity Planning 15 6 Pre deployment phase Link protocols IP ad
166. ributed 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 For information about the AFM workflow see Flowchart for Designing and Deploying a Fabric To learn how to install the AFM including instructions on completing the Initial Setup see the Active Fabric Manager Installation Guide e Getting Started e Fabric Designer Wizard e Pre deployment Wizard e Deploying the Fabric e Alerts e Administration e Performance Management 11 Getting Started This section contains the following topics e Designing and Deploying the Fabric e Flowchart for Designing and Deploying a Fabric Related links e Supported Fabrics Designing the Fabric e AFM Site Map K 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 So 1 ho Help Deployment e wi EMEN Guide f About superuser Y 1 Hdp Y 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 K NOTE If you are using the OpenStack Neutron Managed option refe
167. rious racks together The aggregation switch provides redundancy e Edge ports The uplinks on the aggregation and downlinks on the access e Uplinks An edge port link on the first two aggregation switches in the VLT fabric that connects to outside the fabric e Downlinks An edge port link that connects the access switches to the access layer For example servers or TOR elements e Fabric Interlinks Fabric Links The fabric interlink bandwidth is fixed 10 Gb or 40 Gb Fora 1 Tier links that connect a pair of aggregation switches Fora 2 Tier links that connect the aggregation switches to the access switches Fora 3 Tier links that connect the core aggregation and access switches together VLT Components VLT Health Check VLT Domain Chassis Role Primary Chassis Role Secondary VLT Peer Device SE SESS VLT Peer Device VLT port Typical VLT Topology The VLT domain has VLTi ICL links connecting between VLT peers and VLT port channels connecting to a single access switch to a switch stack a server supporting LACP on its NIC or to another VLT domain as shown in the following illustration The backup link connected through the out of band 00B management network Some hosts can 32 connect through the non VLT ports Typical VLT Topology m Server Port Channel VLT Domain Servers Key Considerations for Designing a Layer 2 VLT Fabric Use the Layer 2
168. root user name is superuser and password is Superuser1 The system comes with three pre defined roles with the following permissions Superuser e Views a summary of user accounts e Adds deletes and edits users e Locks and unlocks users e Resets passwords e Performs configuration changes e Sets session timeout values e Terminates AFM users sessions at the Administration gt User Session screen Administrator e Performs configuration changes e Views performance monitoring e Changes his or her own password User e Views configuration and performance monitoring information e Changes his or her own password Adding a User To add a user account you must be a Superuser For more information about user accounts see Managing User Accounts To add a user 1 Navigate to the Administration gt User Accounts screen 2 Click Add User The Add User screen displays 3 Inthe User Name field enter the user s name Enter a unique name that is alphanumeric Length from 1 to 25 characters 4 Inthe Password field enter the user s password The password length must be from 8 to 32 characters and include 3 of the following categories Atleast 1 upper case letter Lower case letters Atleast 1 numeric digit Atleast 1 special character 5 Inthe Confirm Password field enter the user s password 175 11 13 In the First Name field enter the user s first name Th
169. rrent password In the New Password field enter your new password The password length must be from 8 to 32 characters and include 3 of the following categories Atleast 1 upper case letter Lower case letters Atleast 1 numeric digit Atleast 1 special character In the Confirm Password field confirm your new password 177 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 e Username e Session Login Time e Client IP Address Current Session To terminate AFM users sessions 1 Navigate to the Administration gt User Sessions screen 2 Select the users that you want to log off 3 Click the Force Logoff button 4 Click OK Audit Log To log a chronological sequence of audit records each of which contains information on who has accessed the switch and what operations the user has performed during a given period of time use the Audit Log screen The audit log is 178 from the perspective of the AFM and only the actions performed by AFM users on the switch are logged 1 2 3 4 5 6 a b c d Active Fabric Manager superuser Help Settings User Accoun
170. rrors and fix them Restart the deployment NOTE The switch is not in BMP mode Navigate to the Network gt Fabric Name gt Configure and Deploy screen From the Deploy Fabric pull down menu select the Deploy and Validate option On the Deploy tab check the switch to deploy and then click the Deploy Selected link UPLINK RECONFIGURED Uplink re configured Re Restart the deployment of the switch REDEPLOY REQUIRED deployment of Switch is required K NOTE The switch is not in BMP mode Navigate to the Network gt Fabric Name gt Configure and Deploy screen From the Deploy Fabric pull down menu select the Deploy and Validate option On the Deploy tab check the switch to deploy and then click the Deploy Selected link 141 REDEPLOYMENT REQUIRED Re deployment of the switch Yes Restart the deployment of the switch required NOTE The switch is not in BMP mode 1 Navigate to the Network gt Fabric Name gt 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 AFM Deployment Tasks AFM Deployment Error Status Recommended Action Task Verify switch Eligibility check for VLT switch deployment needs management ip for all its peers eligibility deploymen
171. rt channel configuration You can also copy a switch port channel configuration onto another port e SNMP and CLI Credentials Configures SNMP and CLI credentials at the fabric level Configure SNMP so that the AFM can perform SNMP queries on the switches in the fabric Summary Displays the fabric name location of the software image and DHCP configuration file e VLT VLAN Configuration Specify a VLT VLAN to be applied to the Layer 2 VLT or Layer 3 with Resiliency Routed VLT fabric Include at least one VLAN configuration e Uplink Configuration Specify an even number of uplinks The minimum number of uplinks is 2 One uplink is for redundancy For Layer 3 distributed core an edge port link on the first two leaves that connects to the edge WAN which typically connects to an internet service provider ISP Fora Layer 2 VLT fabric or Layer 3 with Resiliency Routed VLT an edge port link uplinks on the first two aggregation devices that connect outside the fabric Protocol Configuration Layer 2 VLT Fabric Step 1 The pre deployment protocol configuration for Layer 2 fabric consists of the following tasks K NOTE Before you begin review the pre deployment workflow for a Layer 2 fabric at Using the Pre deployment Configuration Wizard e Pre deployment Step 1a Uplink Configuration e Pre deployment Step 1b VLAN Configuration e Pre deployment Step 1c Port Channel Configuration
172. s 64 as shown in the following figure 2 Type 2 Large Core Distributed Core Fabric z up to 32 spines Layer 3 uplinks to WAN OSPF 4810 cmm EE SESS up to 64 leaves TTT T rs teen ree eer em Layer 2 NOTE The AFM does not configure or manage anything beyond the distributed core fabric Figure 6 Type 2 Large Distributed Core Fabric Design Each 4810 leaf for the Type 2 Large Distributed Core fabric design has the following e Forty gigabit of fabric interlink fabric links maximum capacity to the spine 4x 10 Gb Thirty two 10 Gigabit ports will be used for fabric interlink fabric links and thirty two 10 Gb ports are used for the downlinks Type 3 Medium Distributed Core Fabric With a Type 3 Medium Distributed Core design the Z9000 spines S6000 spines connect to the 4810 leaves at a fixed 40 Gb line rate as shown in the following figure The maximum number of leaves is based on the maximum number of ports on the spine 32 ports for the 29000 The maximum number of spines is 16 and the maximum number of leaves is 32 as shown in the following illustration This illustration shows a networking system architecture in a data center are a distributed core fabric containing a set of ToRs to which servers storage devices and network appliances such as load balancers or network security appliances are connected You can run application services network services and network securit
173. s no single point of failure that can disrupt the entire fabric the distributed core architecture is more resilient and as a result there is less negative impact on the network when there is a link or node failure The AFM views the distributed core as one logical switch Distributed Core Architecture Two Tier Spine 01 Spine 02 Leaf 01 Leaf 02 Leaf 03 Leaf 04 HIT UE The uplinks are in the first 2 leafs Downlinks NOTE There are no uplinks on the spines All the leaves have downlinks The uplink should be configured in the first two leaves Key Advantages The key advantages of a distributed core architecture are e Simplified fabric e Higher bandwidth Highly resilient e Higher availability e Low power consumption e Less cooling e Lower latency e Lower cost e Less rack space e Easier to scale 22 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 All the ports on the spine switches are used to connect the leaves various racks together The spines provides load bal
174. s or other countries IBM is a registered trademark of International Business Machines Corporation 2013 12 Rev A0X Contents lge e EE Problem Challenges to Build a Fabric in the Data Center Solution Active Fabric Manager 9 LE nas esac H 11 d Getting SOIH BU ert coe oues cu Tai c tee ac T RAT ate 13 Designing and Deploying a Fahrte 13 Designing and Deploying a Fabric Howchart EE 15 AAEM Site Ma Bu uei EN 17 5 Supported Fabric TE 19 Key Considerations for Designing a Layer 3 with Resiliency Routed VLT Fabien 20 Gathering Useful Information for a Layer 3 with Resiliency Routed VLT Fabric 20 Conventional Core Versus Distributed Core esent enne nnn tnt rnnt tene tent tens tnnt 21 Conventional Ore im nag reir deer ebd eie e A Re bab debe ree e Ne Ee Ra beca in eed 21 Distributed Cores EE 22 Key Advantages i d Lo eR e adr Reti e e ti dte ie EO d asd edt da ates ths 22 Distributed REOE METUIT 23 Key Considerations for Designing a Distributed Core 24 Gathering Useful Information for a Distributed Core Selecting a Layer 3 Distributed Core Fabric Desion essent tenete nnn MET scende eo att ete et oie Mans stata Lo oS EL c a ctia qct bti NO Eo e ML UA Multizdomain VET iae Uic Re e teu be eiie VET TerminolQd o cisterna Der edere arcere ne ec En tle bete itd adeste HURT e VE VET COMPONEN ieaiai aea aie ai aa aa aaa Eaa aaaea aaa aaa aaa a adaa aa aaa Typical VLT Topology Key C
175. s such as Edge Access or Top of Rack ToR VLT reduces the role of Spanning Tree protocols by allowing LAG terminations on two separate distribution or core switches and by supporting a loop free topology A Spanning Tree protocol is needed to prevent the initial loop that may occur prior to VLT being established 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 VLT provides Layer 2 multipathing creating redundancy through increased bandwidth enabling multiple parallel paths between nodes and load balancing traffic where alternative paths exist For information about VLT see the FTOS Configuration Guide for either the S4810 S6000 or the Z9000 at https www force10networks com CSPortal20 KnowledgeBase Documentation aspx For more information about VLT see Selecting a Layer 2 and Layer 3 with Resiliency Routed VLT Fabric Design Virtual link trunking offers the following benefits e Allows a single device to use a LAG across two upstream devices Eliminates Spanning Tree protocol STP blocked ports e Provides a loop free topology e Uses all available uplink bandwidth 30 e Provides fast convergence if either the link or a device fails e Optimized forwarding with Virtual Router Redundancy Protocol VRRP e Provides link level resiliency e Assures high availability A CAUTION Dell Networking recommends not enabling stacking
176. servers switches or ToRs When you enable the ToR configuration the leaves function as a ToR When you disable the ToR configuration the leaves function as a switch The port bandwidth for the downlinks is 1 Gb 10 Gb or 40 Gb a read only field For more information about downlinks see Distributed Core Terminology and VLT Terminology 93 Predeployment Configuration northcore Introduction v Downlink Configuration Fabric Link Configuration v Enter the required information to configure Gowntinks Uptink Configuration v gt Downlink Configuration Port Bandwidth Specified number of downlink ports Generate Downlink Configuration Specify Leaf as TOR Configuration Number of ports per Port Channet Starting VLAN ID Protocol Profile Start IP Address Range Prefix Step 4 of 11 Back Next Save and Exit Cancel Figure 39 Downlink Configuration for Layer 3 Distributed Core Fabric To configure the downlinks for a Layer 3 distributed core fabric 1 2 3 4 5 10 Navigate to the Network gt Fabric Name gt Configure and Deploy screen From the Deploy Fabric pull down menu select the Pre deployment Configuration option Navigate to the Downlink Configuration screen To have the leaves act as a ToR select the Specify Leaf as ToR option Manually configure the downlinks or to automatically generate the downlink configuration check the Generate Downlink Configuration option In the Start IP Address Range Prefix fi
177. sion Switch Replace Switch Deploy Switch 17 Administration Job Results Audit Log Schedule Jobs Data Collection Reports Backup Switch Configuration Files Update switch software Active Software Administration Schedule data collection Edit threshold User Accounts Create Edit Delete Duplicate Run User Sessions AFM Server Upgrade 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 Add User Delete User Edit User Unlocking User Display active AFM users Terminate users sessions AFM Server Upgrade AFM Server Backup Supported Fabric Types The fabric design wizard defines the basic configuration for a Layer 2 VLT Layer 3 distributed core and Layer 3 with Resiliency Routed VLT fabric e 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 e Use the Layer 2 VLT fabric for workload migration over virtualized environments For information about Layer 2 fabrics see VLT and Selecting a Layer 2 VLT and Layer 3 with Resiliency Routed VLT Fabric Design e Use the Layer 3 with Resiliency Routed VLT fabric to extend equa
178. software image for each type of switch on to the TFTP or FTP site NOTE To download the latest FTOS switch software version see the Upload Switch Software section in the AFM Installation Guide To specify which software images to load onto each switch in the fabric from the TFTP or FTP site 1 Navigate to the Network gt Fabric Name gt Configure and Deploy screen 2 From the Deploy Fabric pull down menu select the Pre deployment Configuration option 3 Navigate to the Software Images screen 4 Select the TFTP or FTP site option that contains the software image 5 Enter the path of the software image s to the TFTP or FTP site 6 Click Next to go to the DHCP Integration screen Pre Deployment Step 6 DHCP Integration The DHCP Integration screen uses the information configured at the Assign Switch Identities Management IP and Software Images screens to create a DHCP configuration file named dhcpd cfg which contains the following information e System MAC addresses and fixed management IP addresses for each switch in the fabric e Location of the software images and configurations for the switches on the TFTP or FTP server To automatically integrate the file into the AFM local DHCP server use the default setting Local AFM provisioned to be a DHCP server AFM automatically generates a switch configuration file and transfers it to the local DHCP server on AFM To manually integrate the DHCP configuration into the ex
179. ss 79000 54810 MXL Resiliency VLT emm m n i BE Fabric Link Bandwidth Aggregation and Access 20 6b Core and Aggregation 80 Gb nn hid ww Maximum Supported Blades 672 Optional Module Port No 41 Bandwidth 10 Gb Mnitrac baam within Chassis resifiency Yes 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 Fabric Name and Type v Fabric Type Layer 2 Bandwidth and Port Count v E v Deployment Type Liwer Core Aggregation Access 79000 4810 AXL Fabric Link Bandwidth Aggregation and Access per stack 20 Gb Core and Aggregation 80 Gb Maximum Supported blades 672 Opbonal Module Port No 41 Bandwidth 10 Gb Stacking enabled in Access Yes Layer 3 with Resbeocy Routed VLT 3 Tier Core Aggregation Access 29000 4810 MXL Resibency VLT ws gt lt ay H Aggregation and Access 20 Gb Core and Aggregabon 80 Gb Fabric Link Bandwidth Maximum Supported Blades 672 Optional Module Port Noc41 Bandwidth 10 Gb Intrac hassis within Chassis resibency Yes Figure 26 Tier 3 Layer 3 with Resiliency Routed VLT Blade MXL with IntraChassis option Fabric Design Step 3
180. st be in a managed state to monitor and manage it Launch Active Link Displays additional performance statistics about a fabric in graphical view by navigating to the following screens Network gt Fabric level gt Graphical screen Then right click the switch icon and select the Active Link option Network gt Fabric level gt Graphical screen From the Action pull down menu select the Active Link option bad Active Fabric Manager Network gt SA8105tkB96 Summary Merts afd Events Verl rmance Maintenance Configure aad Ueploy Action V Topology Options Y Q View Switch Topology amp Network Manage Un manage Switch S4820TStkB96 Aggregason 1 Aggregation 2 9 9 R an 0 j am Aggregabon 1 Aggregation 2 Layer2core Layer3core z Access 1 448105tk896 Accevs 1 Details Links Hardware VLT Domain VLANs Port Channets Status Major IP Address Active Alerts 0 MAC Address Modet 4810 01 44F SW image Version Wotal Ports 116 Ports Down Fabric SAB105 tkB96 Manage State Usage Status Deployed Service Tag Active Link Server Status Not Configured Active Link WEB Se For information about how to configure the Active Link navigate to the Administrative gt Settings gt Active Link Settings screen e 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 e Show All Links Displ
181. start the DHCP Integration step using Pre deployment Configuration wizard To restart the DHCP Integration 1 Navigate to the Network gt Fabric Name gt Configure and Deploy screen From the Deploy Fabric pull down menu select the Pre deployment Configuration option Restart the DHCP Integration step Deployment Errors Use the following table to troubleshoot deployment errors Error Details Recommended Action Protocol transfer failed Verify the TFTP or FTP connectivity from the AFM For FTP verify the credentials 134 2 Restart the deployment of the switch from the Network gt Fabric Name gt Configure and Deploy by selecting the switch from the list and then click on the Deploy Selected link Device cle n p taskaited Verify the Telnet or SSH connectivity from the AFM Restart the deployment of the switch from the Network gt Fabric Name gt Configure and Deploy by selecting the switch from the list and then click on the Deploy Selected link SERGE EIS Verify TFTP FTP or Telnet SSH connectivity from the AFM Restart the deployment of the switch from the Network gt Fabric Name gt Configure and Deploy by selecting the switch from the list and then click on the Deploy Selected link GE Verify connectivity to the switch from the AFM Restart the deployment of the switch from the Network gt Fabric Name gt Configure and Deploy by selecting the switch from the list and then click on the Deploy S
182. t Step 1 VLT Fabric Interlink Configuration 92 as 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 Navigate to the Network gt Fabric Name gt Configure and Deploy screen 2 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 Click the Next button The Fabric Link Configuration screen displays 5 Inthe Start IP Address Range Prefix area enter the starting IP address and prefix The prefix must be from 8 to 29 6 Inthe Loopback IP Address Range Prefix area enter the loopback address range and prefix The prefix must be from 8 to 26 7 Inthe Area ID field use the default setting of 0 or enter the area ID The area ID is a value from 0 and 65535 The uplinks or interlinks must be in area 0 for OSPF Pre deployment Step 1b Uplink Configuration The Uplink Configuration screen for a Layer 3 and Layer 3 with Resiliency Routed VLT fabric displays the port bandwidth and the number of specified ports read only fields entered on the Bandwidth and Port Count screen To configure the uplink protocol for the edge port uplinks to the WAN use the Uplink Configuration screen For information about for a uplinks for a La
183. t User Session Server Update 9 Audit Log Summary Filter Export User Name Jate From UserName Date and Time Dat Status Date To Module superuser 04 27 2013 03 30 19 AM superuser 04 25 2013 11 21 40 PM peration LOGIN LOGIN LOGIN 04 16 2013 01 MODIFY 04 16 2013 01 03 37 AM MODIFY OCES 0 Item s found Displaying 1 20 of superuser Audit Log Details User Name Date and Time UTY MANAGER LOGIN 0 11 Itvpel clientModel c31418 Navigate to the Administration Audit Log screen Click the filter icon on the upper right of the screen to display the audit trail options Enter and select your filter criteria for the User Name field For example superuser From the Date From pull down menu select the beginning date and time of the operation From the Date To pull down menu select the end date and time of the operation From the Module pull down menu select one of the following AFM modules Security Activation Security Manager Audit Trail UI Manager 7 From the Status pull down menu select the one of the following status of audit trail operations a b c d e f g Queued In Progress Success Failure Timeout Response Delivered Invalid Request 8 Click the Apply button You also export your results using the Export link 179
184. t Failed Ping verification Failed Verify DHCP offer is received in the device console Power cycle if needed Telnet SSH Telnet SSH session Verify Telnet SSH connection Verify DHCP offer is received in the connectivity verification Failed device console Power cycle if needed verification Reset to factory Reset to factory defaults Verify Telnet SSH connectivity and deploy again defaults task Failed Minimal Minimal config upload Verify Telnet SSH connectivity and deploy again configuration Failed upload to switch ES Minimal config upload on Verify Telnet SSH connectivity and deploy again etiatn euntem Reload of switch of switch Reboot of switch Failed Verify Telnet SSH connectivity and deploy again LM image error Boot image was not loaded Change the boot image path to flash by executing the CLI command from flash through console session Stack unit cleanup Stack unit renumbering Verify Telnet SSH SNMP connectivity task Failed Upgrade standby Upgrade standby Failed Standby MAC not found or reported card problem verify standby switch Full configuration Full config file transfer to Verify the TFTP FTP connectivity Verify FTP credentials file transfer TFTP FTP server Failed TFTP FTP TFTP FTP connection issue Verify TFTP FTP connectivity between the switch and TFTP server connectivity between switch and TFTP server Full configuration Full config upload Failed Verify TFTP FTP and Telnet SSH connectivit
185. t interfaces For example maps 1 VLAN to multiple ports Copy VLAN Tagged Port Copies the VLAN tagged port configuration from a selected port to other port s within Config a switch To configure downlink ports on the access switches 1 Navigate to the Network gt Fabric Name gt Configure and Deploy screen 2 From the Deploy Fabric pull down menu select the Pre deployment Configuration option 3 Navigate to the Layer 2 VLT Downlink Port Configuration screen 91 Predeployment Configuration Layer2core Dowriink Port Configuration amp k v k v J a e AN Cor Port Kame Tagged VLAM Untagged VLANs ero pnt ove g by E en Geb EU emet BS E g J Teniigabettthemat 014 E 5 Lf Tec patet thence CH CH M amp w Erene a f g erGgatitftheene C g Bock Next Seve and Ext Cance Figure 38 Downlink Port Configuration for Layer 2 4 From the Switches pull down menu select an access switch 5 Inthe 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 E NOTE Before you begin review the pre deployment workflow for a Layer 3 distributed core fabric at Using the Pre deploym
186. t to the Last committed configuration on the switch area The AFM displays the timestamp for the last committed configuration on the switch Review the combined configuration and make any necessary changes Click the Save To button to save the combined auto generated and custom configuration Click the Close button Viewing Custom Configuration History To view a complete history of all custom configuration applied to each of the switches use the Custom Configuration History screen Custom Configuration History Displays a list of custom configuration applied to the switch at different times selecting a row in the table displays the corresponding details Applied Custom Configuration Commands Captures all template based custom configuration commands and switch specific custom configuration commands that were applied during deployment or redeployment This includes errors reported by the switch during command execution 121 To view custom configuration history 1 Navigate to the Network gt Fabric Name gt Configure and Deploy screen 2 From the CLI Configuration pull down menu select the View Custom Configuration History option The Custom Configuration History displays 122 Viewing the Fabric This section contains the following topics e Dashboard e View Network Summary e View Fabric Summary e Switch Summary Related Links Fabric Performance Management Dashboard To view the fabric
187. tab click the Advanced Configuration link Click on View Auto Generated Configuration link and wait for the configuration to be displayed Associating Templates You can associate one or more existing configuration templates to the fabric entire fabric all spines all leaves all aggregation switches all core switches all access switches or a set of switches When a template is associated to an entire fabric or all spines all leaves all core switches all aggregation switches and all core switches the template gets automatically applied to the newly added switches instead of the you having to create new associations manually g Important Each template can have only one association per fabric The AFM does not support the ordering of templates for sequencing the commands If you want to do this we recommend that you manually combine the templates into a single template To associate a template 1 Navigate to the Network gt Fabric Name gt Configure and Deploy screen 2 From the Deploy Fabric pull down select the Deploy and Validate option 3 On the Deploy tab click the Advanced Configuration link 4 Click the Associate Templates to Fabric Switches link The Associate Templates screen displays Click the Add Association link In the Template Name pull down menu select the template that you want to use Optionally In the Comments field enter your comments a om In the Select Association area select one the follow
188. te Complete Re Layer3core Access 4 Access Complete Complete Re 6 Item s found Displaying 1 6 7b Administration 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 Enter port channel information and enable LACP Auto Populate Enter port channel information to automatically assign port channels to switches in the fabric and enable LACP Number of Ports per Port Channel Start Port Channel ID Number of Port Channel Port Channel Increment Enable LACP optional Copy Switch Port Channel Copies over switch port channel configuration from another switch You first create a Configuration port channel configuration and then you can copy over to another switch Deletes a selected port channel configuration Enter the port channel configuration 100 Predeployment Configuration Layer3core troduction v Port Cha nel Configuration Fabric Link Configuratior v Enter the required downlink pot Channel comfiguratice kr Configuration Switches LayerIoore Acce DI VLAN Configuration v gt Port Channel Conf guration r Pot Channel ID Forts Fort Channel Capacity wet Configured Figure 46
189. ted Complete Partial complete indicates that at least 1 switch has its system MAC and IP address configured Partial Complete Complete In progress Partial let artial Complete Incomplete Partial Complete Complete Incomplete indicates that the AFM is in the middle of deploying the switches Complete indicates all the switches in the distributed fabric are deployed Complete Not Started Not Started Not Started In progress Stopped Error Complete Not Started In progress Stopped Error Complete View Wiring Plan Edit Fabric All fabric attributes except fabric name Pre deployment Configuration Delete Fabric View Wiring Plan Edit Fabric All fabric attributes except fabric name Pre deployment Configuration View DHCP Configuration Deploy and Validate Fabric View Deployment and Validation Status Delete Fabric View Wiring Plan View DHCP Configuration View Deployment and Validation Status Delete Fabric View Wiring Plan Edit Fabric Allow editing of all fabric attributes except fabric name fabric type interlink over subscription port count and expand fabric Expand Fabric Port Count and uplink Configuration allow additions in Configure Protocol Setting Pre deployment Configuration View DHCP Configuration Deploy and Validate Fabric Validation is only allowed when deployment is partial or fully complet
190. ternal DHCP server select the Remote External DHCP server option After you power cycle the switches the switches use BMP BMP provides the following features e Automatic network switch configuration e Automated configuration updates e Enforced standard configurations e Reduced installation time Simplified operating system upgrades Automated BMP reduces operational expenses accelerates switch installation simplifies upgrades and increases network availability by automatically configuring Dell Networking switches BMP eliminates the need for a network administrator to manually configure a switch resulting in faster installation elimination of configuration errors and enforcing standard configurations 107 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 4810 S4820T S6000 29000 and MXL Blade switches The switch automatically configures itself by loading and installing an embedded FTOS image with the startup configuration file For more information about BMP refer to the Open Automation Guide at https www force10networks com CSPortal20 KnowledgeBase Documentation aspx Select the Open Automation heading UC Important When you enter the system MAC address
191. th one or more switches You can only delete templates that are not being used You can only delete one template at a time If you attempt to delete a template that is being used AFM displays an error message indicating which fabric s the template is associated with K NOTE To delete a template you must have superuser or administrator privileges To delete templates P OY S 118 Navigate to the Network gt Configure and Deploy screen From the CLI Configuration select the Managing Templates pull down menu Select the template and then click the Delete Link option Click Yes 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 gt Fabric gt Configure and Deploy screen 2 From the CLI Configuration pull down select the Manage Templates option The Templates screen displays 3 Click on the Copy Template link The Copy Template displays 4 Select the template to copy 5 Inthe Template Name field enter a unique name for the new template 6 Click the OK button Associating Templates You can associate one or more existing configuration templates to the entire fabric all the spines all the l
192. then click the Finish button 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 Click the on the Deploy Switch link Step 3 Deploy Switch To deploy a replacement switch 1 2 3 Navigate to the Network gt Fabric Name gt Switch Name screen Click the Switch Replacement tab Click the Deploy Switch link Note If you make changes to the switch outside of the AFM for example using Telnet you might need to use the restore option to restore the switch configuration Updating the AFM To view and manage AFM server updates use the Administration Update Server screen Updating the AFM Server 1 160 Navigate to the Administration gt Update Server screen and then click the Update Server link The Update Server screen is displayed In the Select RPM packing file location area choose one of the following options Local Drive DVD USB Remote Server 1 From the Protocol Type pull down menu select the protocol type https ftp or sftp 2 Specify the path of the RPM packaging file 3 Optional Enter the user name 4 Optional Enter the password From the Select the software method area choose one of the following options AFM Upload Download The update is copied to the standby partiti
193. tion 4810 senor CEU EB EE GEB Maximum Available Downlink Ports 110 Maximum Available Downlink Ports 110 Figure 11 Example Tier 1 with Layer 2 VLT fabric Deployment Topology Introduction v Output Fabric Name and Type v Bandwidth and Port Count vd Network Topology ELEC E Tabular Wiring E Gra Deployment Topology v Display future switches Beks Topology Options v Fabric Customization v 1 Tier Layer 2 VLT Topology o E Aggregation Aggregation 2 d Output Uplink Downlink and VLT link Figure 12 Example Tier 1 with Layer 2 VLT fabric Graphical View 56 Use Case 2 1 Tier Layer 3 with Resiliency Routed VLT When you select a 1 tier Layer 3 with Resiliency Routed VLT fabric e The uplinks between the 2 aggregation switches and external switch WAN supports the Layer 3 protocol OSPF iBGP or eBGP e 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 In this example shown below a Layer 3 with Resiliency Routed VLT fabric Based on the deployment type option selected different downlink options are configured in the access tier Use Case 3 2 Tier Layer 2 When you select a 2 tier Layer 2 VLT fabric e The fabric links between aggregation and access switches supports the Layer 2 protocol e The uplinks between the
194. tion switches supports the Layer 3 protocol e The fabric links between aggregation and access switches supports the Layer 2 protocol e The uplinks between the aggregation switches and external switch WAN supports the Layer 3 protocol OSPF iBGP or eBGP e The downlink from the access 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 Select the VLAN and VRRP Configuration option to support redundancy between the access switch and ToR switches latrodactien v Output 3 terLayer 2 VIT Topology Fabs Name sa Type v 17 33 nr 3 ierLayer 3 Resdency outed VLT Topology e p Core 1 rei Bandwidth and ort ost v o Ccpormen Topoleg v 9 Fabr Cusioatation d eg he abyeeTink tepwetr Core and Aggregation are runrirg layer 3 Protoco 1 P 0n Aggregation gyregabond Aggregation AzgregaticnS agpegitior 7 Aggregation d Aggregation e o o o o D 9 i l mm um The fabric link between Cote Agfregation and Access are running Layer 2 or Loyer 3 Protocol o o o c o o Lj o HS HE ae an Ta cra rg Access 4 Access t5 Access t6 Accesos Access A Access 49 Mese 72 Access Figure 21 3 Tier Layer 2 VLT Topology Use Case 6 3 Tier Layer 3 Resiliency Routed VLT When you select a 3 tier Layer 3 with Resiliency Routed VLT fabric e Th
195. to the Uplink Configuration screen Sem and Port Count screen specifies the number of uplinks From the Deploy Fabric pull down menu select the Pre deployment Configuration option In the Protocol Settings select a routing protocol OSPF IBGP or eBGP for the edge port uplinks The Bandwidth The range of IP addresses belong to the 30 subnet is automatically populated by the AFM For OSPF for each specified uplink enter the local IP address remote neighbor IP address and area ID A valid area ID area is 0 to 65535 ForiBGP for each specified uplink enter the local IP address remote neighbor IP address local AS number For the AS number enter a value from 1 to 4294967295 For eBGP for each specified uplink enter the local IP remote neighbor IP address local AS number and remote AS number For the AS number enter a value from 1 to 4294967295 5 Inthe Loopback IP Address Range Prefix enter the loopback IP address and prefx 6 Click Next to go the VLT VLAN Configuration screen Pre deployment Step 1b VLT VLAN Configuration To specify a VLT VLAN to be applied to the Layer 2 fabric manually or automatically use this screen Specify at least one VLAN configuration 86 Predeployment Configuration Layer2core VLAN Ib Primary P Tecondary IF Vital IP x 172 9 amp 0 1 16 Me E 72 403 16 r 05 044 90 r r r ec Back Next Save and E Figure 36 VLT VLAN Configuration with VLAN and VR
196. tween Aggregation amp Access FL BW Fabric Link Bandwidth UL BW Uplink Bandwidth BW Bandwidth Table 4 3 Tier ToR 1 Gb Downlinks for Layer 2 and Layer 3 with Resiliency Routed VLT DL UL Type DL Port Access FL Possible Topologies BW BW Range VLTi BWB E Capacity C amp A A amp A Core Aggregation Access 1Gb 40Gb Stacking 1 2496 2 40 ELI NA 40 Gb 4810 e or 24G 1Gb 10 Gb Stacking 2641 2 40 2 40 NA 40 Gb Eu Ld EE 32256 Gb Gb 36 or 6000 S55 126 Basic Basic Basic 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 see Multi domain VLT Refer to the MXL Topologies for MXL Blade Deployment 37 10 Gh Top of Rack Deployment mVLT 40 Gb Uplinks 2 to 8 29000 VLT Aggregation VLT Domain mVLT Z9000 4 40Gb VLTI 2links 4 40 Gb VLTI Hea 4 40 Gb VLTI 2 links amp 4 ports 2 to 26 2 links amp 4 ports Access Figure 10 10 Gb or 40 Gb ToR VLT Deployment mVLT a Important All the VLT aggregation switches must be same mode type for aggregation for example 29000 On the VLT access you can configure the same model type or mixed the following model types S4810 and S4820T 2 and 3 Tier 10 Gb ToR mVLT Deployment Topologies for Layer 2 or Layer 3 with Resiliency AVC Aggregation VLTi Capacity DL Downlink DL
197. ul for all switches 50 Switch Configuration Phases and States This section describes the phases and possible states for a switch Table 12 Switch Level States State Description Complete Indicates that design is complete for the switch K NOTE At switch level design Partial Complete will not be tracked Partial Complete will only be tracked at the fabric level Pre deployment Required Indicates that not all required Pre deployment Configuration information was Configuration provided Error Indicates that an error occurred during file transfer transfer of minimum configuration file to FTP TFTP server or an error occurred during automatic DHCP integration for local DHCP server K NOTE In case of remote DHCP server no errors will be reported for DHCP integration step as it is not an automated step from AFM user is responsible for manual DHCP integration in this case Complete Indicates that Pre deployment Configuration information is complete for the switch Indicates that deployment error exists Complete Indicates that deployment was successful for the switch Validation Required Indicates that validation was never initiated for the switch or the validation state was reset due to Design Pre deployment Configuration Deployment change K NOTE Validation can be initiated only if Deployment is in state Complete In progress Indicates that deployment is in progress and also provides the latest percentage complete infor
198. up options Select a backup switch configuration to edit Click the Edit Description link to edit the description for switch backup configuration Edit the description Click the OK button Updating the Switch Software The Network gt Fabric Name gt Maintenance gt Update Software screen displays the summary of software for each switch in the fabric This screen has the following options oO 5 RM e Schedule Switch Software Update Creates new schedule job software image upgrade and software image activation e Schedule Activate Standby Partition Activates the software available in the standby partition of the device as a schedule job to happen at later time or to run immediately Replacing a Switch To replace a switch in the fabric 1 Decommission Switch Replace Switch Deploy Switch You must replace the switch with same type of switch Step 1 Decommission a Switch Key Considerations When you decommission replace a switch consider the following e The switch needs to be manually powered off e The switch is automatically placed in an unmanaged state and the AFM stops managing this switch e The new switch should use the factory default setting e ifthe old switch is used reset it to the factory default setting e AFM generates information for Return Material Authorization RMA which you submit to Support 158 K NOTE You must replace the switch with the same type of switch See Rep
199. uration File Information only SUCCESS Transferred Successfully REQUEST TO DISCOVER NODE Request To Discover Switch Yes Power on the switch Restart the deployment of the switch from the Network gt Fabric Name gt 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 Minimum Configuration Information only INPROGRESS Upload In Progress MIN CONFIG UPLOAD ERROR A E Verify the connectivity to the TFTP FTP server from the switch Check the Validation Status column for errors and fix them 139 MIN CONFIG UPLOAD COMPLETED INIT SOFT RELOAD INIT SOFT RELOAD ERROR PROTOCOL CONFIG UPLOAD INPROGRESS PROTOCOL CONFIG UPLOAD ERROR 140 Verify that the system MAC address in the dhcpd conf file matches the csv file that contains the MAC addresses of the switches Verify that the min cfg file is in the correct directory on the TFTP FTP server Redeploy the switch from the Network gt Fabric Name gt Configure and Deploy screen by selecting the switch from the list and then click on the Deploy Selected link K NOTE The switch is in BMP mode Minimum Configuration Information only Upload Successful Initiated Soft Re load on Switch Error During Soft Re load on Yes Switch Protocol Configuration Upload In Progress Protocol Configuration Yes Upload Error i Information only
200. witches must be IP ready Click the Deploy Selected link and wait for the fabric to deploy 111 10 Select the Apply configuration changes to the switch option or the Overwrite entire configuration on the switch option Deploy and Validation Configuration deployment option Deploy Validation The order of deployment and validation is manually followed If both Core Aggregation switches need to be deployed along with one or more Setect Switches to be deployed Aggregation Access switches deploy only one of Core Aggregation switches first followed by applicable Aggregation Access switches then the second Core Aggregation and then manually validate ali switches gt Deploy Selected Advance Select configuration deployment option Switch Name e Apply configuration changes to the switch v eastcore Access 2 Overwrite entire configuration on the switch V Bes ctor eastcore Access 1 Reset to factory defauts eastcore Aggregation 2 eastcore Aggregation 1 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 Ifthe Reset to factory defaults option is selected AFM resets the switch to the factory default mo
201. with color code bar Table 29 Inbound and Outbound Link Utilization Color Codes Green Good Represents normal inbound or outbound link utilization Yellow Minor x gt 80 andx lt 90 Represents low link utilization Red Critical Represents high link utilization K NOTE When the color code is yellow or red the AFM displays an alarm at the Network gt Fabric Name gt Switch Name gt Alerts and Events gt Current screen Highest CPU Utilization Displays the highest 5 CPU utilization in 5 minute intervals for all fabrics with the following information Fabric Switch Last Values number with color code bar Table 30 CPU Utilization Color Codes Green Good Represents normal CPU utilization Yellow Minor x 7096 and x lt 80 Represents low CPU utilization Red Critical Represents high CPU utilization NOTE When the color code is yellow or red the AFM displays an alarm at the Network gt Fabric Name gt Switch Name Alerts and Events Current screen e Highest Memory Utilization Displays the highest 5 memory utilization for all fabric with following information Fabric Switch Last value 96 number with color code Table 31 Memory Utilization Color Codes Green Good Represents normal memory utilization Yellow Minor 82 and lt 92 Represents low memory utilization Red Critical Represents high memory utilization NOTE When the color c
202. y and deploy again Or upload to switch Verify optional modules have been installed per fabric design Verify whether AFM supported software version is used 142 Smart script transfer failed Wiring validation Merge configuration changes Custom configuration upload Backup running configuration Smart script transfer Verify Telnet SSH connectivity and deploy again Failed Unable to validate Wiring Verify SNMP connectivity Wiring Errors Exists Review error details in Errors screen Apply configuration Verify Telnet SSH connectivity and deploy again changes Failed Custom configuration Verify Telnet SSH connectivity and deploy again upload Failed Backup config Failed Verify Telnet SSH connectivity and deploy again TFTP FTP Error To troubleshoot TFTP FTP when the deployment status is TFTP FTP Failed use the following table Table 39 Deployment Status Configuration Errors Deployment Error Category Error Details Recommended Action Status TFTP FTP Failed Configuration Deployment Error occurred during Error TFTP FTP Check the TFTP FTP connectivity on the network Make sure that you have specified the correct TFTP FTP address at the Administration gt Settings screen Validating Connectivity to the ToR To validate the leaves or access downlink connections to the ToR 1 Ping the ToRs from the leaves or access 2 Confirm the VLAN configured on the leaf or access is the same on the p
203. y screen From the Deploy Fabric pull down menu select the View DHCP Configuration option From the Deploy pull down menu select View DHCP Configuration For more information on DHCP see DHCP Integration Deploying and Validating the Fabric This section contains the following topics e Deploying the Fabric Validating the Fabric e Viewing Deployment and Validation Status Deploying the Fabric To deploy the fabric use the Network gt Fabric Name Configure and Deploy gt Deploy Fabric gt Deploy and Validate screen When you deploy a fabric make sure that the fabric design matches the deployed fabric AFM prompts you to fix any errors when you deploy the fabric Network gt eastcore Summary Alerts and Events Performance Maintenance Configure and Deploy 9 Fabric Deployment Summary Deploy Fabricy Errors OU Configurationy View Wiring Plan c Pre deployment Configuration Step 1 Step 2 SCH h Type Design Pre deployment Deployment Validation Aggregaton 1 View DHCP Configuration tess Complete Required Required E Aggregaton 2 eastcore Access 2 Unit 0j Access Complete Complete Bao Recui ed Access 1 eastcore Access 1 Unit 0 Access Complete Complete Error Required eastcore Aggregation 2 Aggregation Complete Complete Error Required eastcore Aggregation Aggregation Complete Complete Complete Error westcore 5 Item s found Displaying 1 5 109 a gt Attention During initial deployment the BMP pro
204. y services either on physical machines or virtual machines 28 Type 3 Medium Core Distributed Core Fabric Am E o BEE o o ties Layer 3 10 Gb leaf uplinks to WAN OSPF 4810 K e ee Eesbech x ES 3 Ee up to 32 leaves switches 10 Gb leaf downlinks and uplinks Layer 2 d 1Gb servers Function EET Fabric Interlinks NOTE The AFM does not configure or manage anything beyond the distributed core fabric Figure 7 Type 3 Medium Distributed Core Fabric Design Use the Type 3 Medium Distributed Core design when e You require a fabric interlink fabric links bandwidth between the spines and leaves at a 40 Gb line rate e The current and future planned uplinks and downlinks on the leaves for your distributed core fabric is less than or equal to 1536 ports e The leaves act as a switch or ToR leaf switch Within the ToR the protocol can be either VLAN or VLAN and LAG Each Z9000 spine S6000 spine for the Type 3 Medium Distributed Core design has the following e Six hundred and forty Gigabit of interlink fabric links maximum capacity to the spine 16 x 40 Gig e Six hundred and forty 10 Gig Ethernet ports for WAN connectivity Each S4810 leaf for the Type 3 Medium Distributed Core design has the following e One hundred and sixty Gigabit of interlink fabric links maximum capacity to the spine 4x 40 Gig e Forty eight 10 Gig Ethernet ports for WAN connectivity
205. yer 3 distributed core fabric see Distributed Core Terminology NOTE When the Open Shortest Path First OSPF is selected for both uplinks and interlinks one of uplinks or interlinks must be in area 0 To configure the uplink protocol for the edge port uplinks to the WAN for a Layer 3 distributed core fabric 1 Navigate to the Network gt Fabric Name gt Configure and Deploy screen From the Deploy Fabric pull down menu select the Pre deployment Configuration option Navigate to the Uplink Configuration screen P a N In the Protocol Settings select a routing protocol OSPF IBGP or eBGP for the edge port uplinks The number of uplinks is specified in the Bandwidth and Port Count screen AFM automatically populates the range of IP addresses that belong to the 30 subnet a For OSPF for each specified uplink enter the local IP address remote neighbor IP address and area ID A valid area ID area is from 0 to 65535 b For iBGP for each specified uplink enter the local IP address remote neighbor IP address local AS number For the AS number enter a value from 1 to 4294967295 c For eBGP for each specified uplink enter the local IP remote neighbor IP address local AS number and remote AS number For the AS number enter a value from 1 to 4294967295 5 Click Next to go the Downlink Configuration screen Pre deployment Step 1d Downlink Configuration Layer 3 Downlinks are edge port links which connect to
206. you to remotely make configuration changes to the switches in the fabric To configure the CLI credentials and enable the configuration credential for all the switches in the fabric 1 2 3 4 5 6 7 8 9 Navigate to the Administration gt Settings screen In the CLI Credentials area click the Edit button In the Protocol pull down menu select one of the following options Telnet or SSHv2 In the User Name field enter the user name In the Password field enter the password In the Confirm Password field confirm the password The privilege level is a read only field and is set at 15 In the Enable Password field enter a password for the privilege level In the Confirm Enable Password field confirm the enabled password for the privilege level Click OK Client Settings To configure the maximum number of browser windows for each user s session and the polling interval from the AFM to the switches in the fabric 1 Navigate to the Administration Settings screen 171 5 In the Client Settings area click Edit In the GUI Polling Interval in Seconds pull down menu select one of the following options The default value is 60 seconds 15 Secs 30Secs 60Secs 120 Secs 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 Click OK Data Retention Settings To configure the amount of tim

Dell Active Fabric Manager Deployment Guide

Contents

Download Pdf Manuals

Related Search

Related Contents