Force10交换机配置手册

合集下载

迈普交换机配置

迈普交换机配置

迈普交换机基本配置一. 基本配置进入特权模式:Switch> enSwitch#进入全局模式:Switch# config terminalSwitch(Config)#退出命令exit举例:Switch#exitSwitch>帮助命令help举例:Switch>helpenable -- Enable Privileged modeexit -- Exit telnet session时钟配置:clock set <HH:MM:SS> <YYYY/MM/DD>功能:设置系统日期和时钟。

参数:<HH:MM:SS >为当前时钟,HH 取值范围为0~23,MM 和SS 取值范围为0~59;< YYYY/MM/DD >为当前年、月和日,YYYY 取值范围为2000~2035,MM 取值范围为1~12,DD 取值范围为1~31。

举例:设置交换机当前日期为2002年8月1日23时0分0秒。

Switch# clock set 23:0:0 2002.8.1相关命令:show clock超时设置:exec timeout <minutes >功能:设置退出特权用户配置模式超时时间。

参数:< minute >为时间值,单位为分钟,取值范围为0~300。

命令模式:全局配置模式。

缺省情况:系统缺省为5分钟。

使用指南:为确保交换机使用的安全性,防止非法用户的恶意操作,当特权用户在做完最后一项配置后,开始计时,到达设置时间值时,系统就自动退出特权用户配置模式。

数值为0表示没有超时。

举例:设置交换机退出特权用户配置模式的超时时间为6分钟。

Switch(Config)# exec timeout 6↵修改交换机的主机名hostname XXX举例:设置提示符为Test。

Switch(Config)#hostname TestTest(config)#保存交换机配置的命令:write重启交换机的命令:reload恢复交换机出厂配置命令:set default举例:Switch#set defaultAre you sure? [Y/N] = ySwitch#writeSwitch#reload更改语言命令:language {chinese|english}功能:设置显示的帮助信息的语言类型。

交换机的基本配置

交换机的基本配置

交换机的基本配置交换机的基本配置一、交换机的几种配置方法本部分包括以下内容:控制台远程登录其它配置方法本部分内容适用于交换机、路由器等网络设备。

控制台登录后,就可以对网络设备进行配置了。

说明:超级终端只需安装一次,下次再使用时可从“开始 | 程序 | 附件 | 通信 | 超级终端”中找到上次安装的超级终端,直接使用即可。

远程登录通过一台连接在网络中的计算机,用Telnet命令登录网络设备进行配置。

远程登录条件:1、网络设备已经配置了IP地址、远程登录密码和特权密码。

2、网络设备已经连入网络工作。

3、计算机也连入网络,并且可以和网络设备通信。

说明:远程登录的计算机不是连接在网络设备Console口上的计算机,而是网络中任一台计算机。

远程登录方法:在计算机的命令行中,输入命令“telnet 网络设备IP地址”,输入登录密码就可以进入网络设备的命令配置模式。

说明:远程登录方式不能用来配置新设备,新设备应该用控制台配置IP地址等参数,以后才能使用远程登录进行配置。

其它配置方法除了控制台和远程登录之外,还有其它一些配置方法配置网络设备。

1、TFTP服务器:TFTP服务器是网络中的一台计算机,你可以把网络设备的配置文件等信息备份到TFTP服务器之中,也可以把备份的文件传回到网络设备中。

由于设备的配置文件是文本文件,所以,你可以用文本编辑软件打开进行修改,再把修改后的配置文件传回网络设备,这样就可以实现配置功能。

你也可以用TFTP服务器把一个已经做好的配置文件上传到一台同型号的设备中实现对它的配置。

2、SSH:SSH是一种安全的配置手段,其功能类似于远程登录。

与T elnet 不同的是,SSH传输中所有信息都是加密的,所以如果需要在一个不能保证安全的环境中配置网络设备,最好使用SSH。

3、Web:有些种类的设备支持Web配置方式,你可以在计算机上用浏览器访问网络设备并配置。

Web配置方式具有较好的直观性,用它可观察到设备的连接情况。

DELL+Force10交换机

DELL+Force10交换机

DELL Force10交换机简明配置手册Mark Wang2015年4月12日目录1简介 (1)2写在前面 (1)3Console使用 (1)4交换机使用技巧 (2)4.1TAB键自动补全 (2)4.2善于使用问号 (2)4.3反向删除命令 (3)5BMP/Jump-Start模式 (3)6接口的基本配置 (4)6.1接口启用 (4)6.2接口速率修改 (5)7交换机管理 (5)7.1启用Telnet/SSH服务 (5)7.2创建用户名和密码 (5)7.3管理IP的配置 (6)7.3.1带内管理IP (6)7.3.2带外管理IP (6)7.4保存交换机配置 (6)7.5重启交换机 (6)7.6恢复默认设置 (7)8交换机时间与日期 (7)8.1本地系统时间 (7)8.2NTP校时服务器 (7)8.3日志时间戳 (7)9Access/Trunk/Hybird配置 (7)9.1例1.配置Access模式 (8)9.2例2.配置Trunk模式 (8)9.3例3.配置Hybird模式 (8)10生成树配置 (9)10.1RSTP协议 (9)10.2PVST协议 (10)10.3MSTP协议 (10)11链路聚合配置 (11)11.1例1.静态聚合 (11)11.2例CP动态聚合 (11)12VRRP配置 (12)12.1Master主机配置VRRP (12)12.2Standby主机配置VRRP (13)13802.1X认证 (13)14LLDP配置 (14)15DHCP服务器 (14)16本地端口镜像 (15)17sflow配置 (15)18上行链路状态跟踪 (15)19恢复密码 (16)20交换机固件更新 (16)21收集日志 (16)22附录一 (17)23附录二 (17)1简介目前DELL有定位为园区/企业级别的PowerConnect系列交换机、N系列交换机以及定位为数据中心级别的Force10系列交换机(下文可能会简称为F10),其中Force10系列交换机还分为S系列、C系列、E系列、Z系列以及刀箱上的MXL/MIO等。

Force10 Networks E-Series ExaScale 升级程序说明书

Force10 Networks E-Series ExaScale 升级程序说明书

TeraScale to ExaScale Upgrade ProcedureThe E-Series TeraScale is easily upgraded to Force10 Networks E-Series ExaScale. These upgrade requirements outline the necessary components and procedures required to upgrade the E1200i with FTOS version 8.1.1.0. Direct any questions regarding the upgrade to Force10 Networks’ Customer Support.E-mail:***************************Web: /support/Telephone:US and Canada: 866.965.5800International: 408.965.5800Supported HardwareHardware Catalog Number Minimum Software Version RequiredE1200i Chassis (Note 1)CH-E1200I-ACCH-E1200I-DC8.1.1.1AC Power Supply 2800W CC-E1200I-2800W-AC8.1.1.1 DC Power Entry Module CH-E1200I-DC8.1.1.1 Route Processor Module—ExaScale LC-EH-RPM8.1.1.1 Switch Fabric Module (Note 2)CC-E-SFM38.1.1.1 10 port 10GE line card (10M CAM)LC-EH-10GE-10S8.1.1.1 10 port 10GE line card (40M CAM)LC-EJ-10GE-10S8.1.1.1 Fan Tray CC-E-1200I-Fan8.1.1.1Upgrading HardwareExaScale SFM RequirementsE-Series ExaScale systems and FTOS Release 8.1.1.1 require SFM version 752-00265-03 Rev 01 or higher. Earlier SFMs do not support line rate following the ExaScale 8.1.1.1 FPGA upgrade.Do not mix SFMs. All the SFMs in the chassis must run the required minimum software version.The automatic upgrade process takes place regardless of the SFMs you have installed. If you have one or more SFMs that are earlier than 752-00265-03 Rev 01, a SYSLOG message (Message1) appears during the upgrade . Message 1 SYSLOG messages during FPGA Automatic Upgrade00:00:52: %RPM1-P:CP %TSM-5-SFM_OLDER_VERSION: Older version of SFM 8 detected00:00:52: %RPM1-P:CP %TSM-5-SFM_FOUND: Found SFM 800:00:51: %RPM1-P:CP %TSM-5-SFM_OLDER_VERSION: Older version of SFM 7 detected00:00:51: %RPM1-P:CP %TSM-5-SFM_FOUND: Found SFM 700:00:51: %RPM1-P:CP %TSM-5-SFM_FOUND: Found SFM 600:00:50: %RPM1-P:CP %TSM-5-SFM_FOUND: Found SFM 500:00:49: %RPM1-P:CP %TSM-5-SFM_FOUND: Found SFM 400:00:48: %RPM1-P:CP %TSM-5-SFM_FOUND: Found SFM 300:00:48: %RPM1-P:CP %TSM-5-SFM_FOUND: Found SFM 200:00:47: %RPM1-P:CP %TSM-5-SFM_FOUND: Found SFM 100:00:47: %RPM1-P:CP %TSM-5-SFM_FOUND: Found SFM 0The show sfm command includes information for any SFM that needs to be upgraded (Figure3).FPGA UpgradesFTOS version 8.1.1.1 introduces an automatic FPGA Upgrade process. It allows easy upgrades to newer SFM version by implementing an auto-detection of mismatched SFM version. The upgrade to the mismatched SFMs is done automatically.Manual upgrade are still supported for one or all SFMs.Automatic upgrade during boot, reboot, reload, or restartThe FPGA auto upgrade takes place when any SFMs in the chassis run an FPGA version lower than the version running during the boot, reboot, reload and restart operations. During the auto upgrade process, the system displays messages relaying the status of the upgrade process (Figure1). To verify the result of the SFM version upgrade, use the show sfm command.Figure 1 FPGA Automatic Upgrade Messages**************************************************************************** Warning Warning Warning** -------------------------------------------------------------------------------------** Starting auto upgrade of SFMs to newer version 0x0.0.3* Please wait until upgradation of all 5 SFMS is complete.** SFM will restart itself after upgradation of all 5 SFM is complete !***************************************************************************SFM 0/5 upgrade startedSFM 0/5 is upgraded to revision 0x0.0.3.SFM 1/5 upgrade startedSFM 1/5 is upgraded to revision 0x0.0.3.SFM 2/5 upgrade startedSFM 2/5 is upgraded to revision 0x0.0.3.SFM 3/5 upgrade startedSFM 3/5 is upgraded to revision 0x0.0.3.SFM 4/5 upgrade startedSFM 4/5 is upgraded to revision 0x0.0.3.*************************************************************** Warning Warning Warning** -----------------------------------------------------------** Auto upgrade on all 5 SFM to version 0x0.0.3 is complete.** Rebooting chassis ....**************************************************************Verify the result of the SFM version upgrade using the show sfm command.Automatic upgrade for one or more new SFMsThe FPGA auto upgrade takes place when any newly inserted SFM runs an FPGA version lower than the version running on the SFMs in the chassis. During this auto upgrade process, the system displays messages relaying the status of the upgrade process (Figure2). To verify the result of the individual SFM version upgrade, use the show sfm slot command.Figure 2 New SFM Automatic Upgrade Messages**************************************************************************** Warning Warning Warning** -----------------------------------------------------------------------** Starting auto upgrade of SFMs to newer version 0x0.0.3* Please wait until upgradation of 1 SFM is complete.** SFM will reset itself after upgradation of 1 SFM is complete !***************************************************************************SFM 0/9 upgrade startedSFM 0/9 is upgraded to revision 0x0.0.3.*************************************************************** Warning Warning Warning** -----------------------------------------------------------** Auto upgrade on 1 SFM to version 0x0.0.3 is complete.** Resetting SFM .... Please wait ....**************************************************************SFM 0/9 reset started00:08:29: %RPM1-P:CP %TSM-6-SFM_USR_RESET: SFM 0 reset by userreset SFM 0 successful !*************************************************************** Warning Warning Warning** -----------------------------------------------------------** Resetting on 1 SFM to revision 0x0.0.3 is complete !**************************************************************TeraScale to ExaScale UpgradeBe sure you have the correct ExaScale hardware ready for installation prior to beginning this upgrade. Refer to Supported Hardware for the list of hardware required for E-Series ExaScale with FTOS 8.1.1.1.Step Command Syntax Command Mode Purpose1Turn the On/Standby switch toStandby (AC).Turn the Remote Power Source toOff (DC).Power-off the chassis.2Replace the TeraScale RPMs, SFMs and linecards with ExaScale RPMs, SFMs and linecards.Refer to the RPM, SFM and Linecard documentation for installation and replacement details.3Turn the On/Standby switch to ON(AC)Turn the Remote Power Switch to ON(DC).Power on the chassis4The chassis automatically powers up with a ExaScale image if the RPM has been programmed to boot from particular FTP location or Flash that points to a TeraScale image. If no image is configured, go to Steps 5 and 6.5Ctrl+Shift+6Stop the chassis in boot user mode andconfigure it to boot from FTP or Flashand reload.6boot change{primary|secondary|default}After entering the keywords anddesired option, press Enter. Thesoftware prompts you to enter thefollowing:• boot device (ftp, tftp, flash, slot0)• image file name• IP address of the server with theimage• username and password (only forFTP)BOOT_USER Tell the system where to access theExaScale FTOS image used to boot thesystem:•Enter primary to configure the bootparameters used in the first attemptto boot the system.•Enter secondary for when theprimary operating system bootselection is not available.Enter default to configure bootparameters used if the secondaryoperating system boot parameterselection is not available. The defaultlocation should always be the internalflash device (flash:), and a verifiedimage should be stored there.7reload BOOT_USER Restart the chassis to boot with thespecified ExaScale image.8show chassis EXEC Privilege We can confirm using the show chassiscommand.Step Command Syntax Command Mode Purpose Force10#show chassis-- Manufacturing Info --Chassis Type : E600iChassis Mode : ExaScaleChassis Epoch : 10.4 micro-secondsChassis MAC : 00:01:e8:41:cb:36Serial Number : TY000001140Part Number : 7520023900Vendor Id : 04Date Code : 01012008Country Code : 01Product Rev : 03ExaScale to TeraScale DowngradeStep Command SyntaxCommand Mode Purpose1chassis chassis-mode terascaleEXEC PrivilegeChange the chassis mode to TeraScale.2Turn the On/Standby switch to Standby (AC).Turn the Remote Power Source to Off (DC).Power-off the chassis.3Replace the ExaScale RPMs, SFMs and linecards with TeraScale RPMs, linecards and SFMs.Refer to the RPM, SFM and Linecard documentation for installation and replacement details.4Turn the On/Standby switch to ON (AC)Turn the Remote Power Switch to ON (DC).Power on the chassisThe chassis automatically powers up with a TeraScale image if the RPM has been programmed to boot from particular FTP location or Flash that points to a TeraScale image. If no image is configured, go to Steps 5 and 6.5Ctrl+Shift+6when prompted during boot mode Stop the chassis in boot user mode and configure it to boot from FTP or Flash and reload.6boot change{primary|secondary|default }After entering the keywords and desired option, press Enter . The software prompts you to enter the following:• boot device (ftp, tftp, flash, slot0)• image file name• IP address of the server with the image• username and password (for FTP)BOOT_USERTell the system where to access the TeraScale FTOS image used to boot the system:•Enter primary to configure the boot parameters used in the first attempt to boot the system.•Enter secondary for when the primary operating system boot selection is not available.Enter default to configure boot parameters used if the secondary operating system boot parameter selection is not available. The default location should always be the internal flash device (flash:), and a verified image should be stored there.7reload BOOT_USERRestart the chassis to boot with the specified TeraScale image.Force10#chassis chassis-mode terascaleChassis mode changed to TeraScale mode. Please reload chassis now.System configuration has been modified. Save? [yes/no]: y Proceed with reload [confirm yes/no]:yStep Command Syntax Command Mode Purpose8show chassis EXEC Privilege We can confirm using the show chassiscommand.Force10#show chassis-- Manufacturing Info --Chassis Type : E1200Chassis Mode : TeraScaleChassis Epoch : 10.4 micro-secondsChassis MAC : 00:01:e8:05:db:05Serial Number : 7520010900Part Number : 0Vendor Id : 04Date Code : 11252003Country Code : 01Product Rev : 02。

戴尔网络和Force10 S4820T交换机配置指南说明书

戴尔网络和Force10 S4820T交换机配置指南说明书

Dell Networking S4820T and Dell Force10 S4820TSwitch Configuration Guide for PS Series SANsDell Storage EngineeringFebru ary 2016RevisionsTHIS WHITE PAPER IS FOR INFORMATIONAL PURPOSES ONLY, AND MAY CONTAIN TYPOGRAPHICAL ERRORS AND TECHNICAL INACCURACIES. THE CONTENT IS PROVIDED AS IS, WITHOUT EXPRESS OR IMPLIED WARRANTIES OF ANY KIND.© 2013–2016 Dell Inc. All rights reserved. Dell, the DELL logo, and the DELL badge are trademarks of Dell Inc. Other trademarks and trade names may be used in this document to refer to either the entities claiming the marks and names or their products. Dell disclaims any proprietary interest in the marks and names of others.Table of contents1Introduction (5)1.1Audience (5)1.2Switch details (5)1.3Cabling diagram (7)2Dell recommended switch configuration (8)2.1Hardware configuration (8)2.2Delete startup configuration (8)2.3Configure out of band (OOB) management port (8)2.4Configure route for OOB management port (optional) (9)2.5Configure login credentials (9)2.6Enable switch ports (9)2.7Enable Jumbo Frames (10)2.8Configure flow control (10)2.9Configure spanning tree on edge ports (10)2.10Configure port channel for LAG (10)2.11Configure QSFP ports for LAG (10)2.12Save configuration (11)2.13Configure additional switch (11)3Configure Data Center Bridging (DCB) (optional) (12)3.1Disable 802.3x flowcontrol on SFP+ ports (12)3.2Disable 802.3x flowcontrol on all QSFP ports (12)3.3Enable DCB and reload (12)3.4Create tagged VLAN for all ports and port-channels (12)3.5Configure DCB policies (13)3.6Apply policies to switch ports (13)3.7Save configuration (13)3.8Configure additional switches (14)4Reverting from DCB to non-DCB configuration (optional) (15)4.1Disable DCB (15)4.2Remove DCB policies and apply standard flow control (15)4.3Revert to default VLAN ID on switch and arrays (15)4.4Save configuration (16)4.5Reload (16)4.6Verify DCB status (16)4.7Configure additional switch (16)5Optional stack configuration (17)5.1Delete startup configuration on the first switch (17)5.2Configure stack on the first switch (17)5.3Delete startup configuration on the second switch (18)5.4Configure stack on the second switch (18)5.5Verify stack configuration (18)5.6Configure out of band (OOB) management port (19)5.7Configure route for OOB management port (optional) (19)5.8Configure login credentials (19)5.9Configuring switch ports (19)5.10Save configuration (20)Additional resources (21)1IntroductionThis document illustrates how to configure Dell Networking or Dell™ Force10 S4820T switches for usewith Dell PS Series storage using Dell best practices. The recommended configuration uses linkaggregation groups (LAGs) for inter-switch connections. Optional steps are provided in section 3 to enable Data Center Bridging (DCB).1.1AudienceThis switch configuration guide describes an optimal configuration following Dell best practices for a PSSeries iSCSI SAN and is intended for storage or network administrators and deployment personnel.1.2Switch detailsThe table below provides an overview of the switch configuration.1.3Cabling diagramThe cabling diagram shown below represents the Dell recommend method for deploying your servers and PS arrays.Figure 1Cabling diagram2Dell recommended switch configurationThese steps show you how to configure two Dell Networking or Force10 S4820T switches with a LinkAggregation Group (LAG). The switches are interconnected using two of the 40 GbE Quad Small Form-factor Pluggable (QSFP) uplink ports, and the LAG is configured for Dynamic Link Aggregation ControlProtocol (LACP).2.1Hardware configuration1.Power on the two switches.2.Connect a serial cable to the serial port of the first switch.ing Putty or another terminal utility, open a serial connection session to the switch.4.Open your terminal emulator and configure it to use the serial port (usually COM1 but this may varydepending on your system). Configure serial communications for 9600,N,8,1 and no flow control.5.Connect the (QSFP) LAG cables between the switches, by connecting port 48 on switch 1 to port 48on switch2 and port 52 on switch 1 to port 52 on switch 2. See this configuration in Figure 1.2.2Delete startup configurationFTOS>enableFTOS#delete startup-configProceed to delete startup-config [confirm yes/no]yesFTOS#reloadSystem configuration has been modified. Save? [yes/no]noProceed with reload [confirm yes/no]yes2.3Configure out of band (OOB) management portFTOS>enablePassword:FTOS>#configFTOS(conf)#interface Managementethernet 0/0FTOS(conf-if-ma-0/0)#ip address ipaddress maskFTOS(conf-if-ma-0/0)#exit2.4Configure route for OOB management port (optional)FTOS (conf)#management route X.Y.Z.0 /24 A.B.C.12.5Configure login credentialsFTOS(conf)#username admin privilege 15 password 0yourpasswordFTOS(conf)#enable password level 15 0yourpasswordFTOS(conf)#exit2.6Enable switch portsFTOS#configureFTOS(conf)#interface tengigabitethernet 0/0FTOS(conf-if-te-0/0)#switchportFTOS(conf-if-te-0/0)#no shutdownFTOS(conf-if-te-0/0)#exitFTOS(conf)#exitFTOS#configureFTOS(conf)#interface range tengigabitethernet 0/0 – 47FTOS(conf-if-range-te-0/0-47)#switchportFTOS(conf-if-range-te-0/0-47)#no shutdown2.7Enable Jumbo FramesFTOS#configureFTOS(conf)# interface range tengigabitethernet 0/0 – 47FTOS(conf -if-range-te-0/0-47)#mtu 120002.8Configure flow controlFTOS(conf)#interface range tengigabitethernet 0/0 – 47FTOS(conf-if-range-te-0/0-47)#flowcontrol rx on tx off 2.9Configure spanning tree on edge portsFTOS(conf-if-range-te-0/0-47)#spanning-tree rstp edge-portFTOS(conf-if-range-te-0/0-47)#exitFTOS(conf)#protocol spanning-tree rstpFTOS(conf-rstp)#no disableFTOS(conf-rstp)#exit2.10Configure port channel for LAGThese commands create a port channel or LAG.FTOS(conf)#interface Port-channel 1FTOS(conf-if-po-1)#mtu 12000FTOS(conf-if-po-1)#switchportFTOS(conf-if-po-1)#no shutdownFTOS(conf-if-po-1)#exit2.11Configure QSFP ports for LAGThis step assigns the 40Gb QSFP ports to the Port Channel.FTOS(conf)#interface range fortyGigE 0/48 , fortyGigE 0/52FTOS(conf-if-range-fo-0/48,fo-0/52)#mtu 12000FTOS(conf-if-range-fo-0/48,fo-0/52)#no shutdownFTOS(conf-if-range-fo-0/48,fo-0/52)#flowcontrol rx on tx offFTOS(conf-if-range-fo-0/48,fo-0/52)#port-channel-protocol lacpFTOS(conf-if-range-fo-0/48,fo-0/52-lacp)#port-channel 1 mode activeFTOS(conf-if-range-fo-0/48,fo-0/52-lacp)#exitFTOS(conf-if-range-fo-0/48,fo-0/52)#exitFTOS(conf)#exit2.12Save configurationFTOS#copy running-config startup-config2.13Configure additional switchRepeat the commands from section 2 to configure the second switch.3Configure Data Center Bridging (DCB) (optional) To enable DCB mode on the switch, use the following commands.3.1Disable 802.3x flowcontrol on SFP+ portsFTOS#configureFTOS(conf)#interface range tengigabitethernet 0/0 - 47FTOS(conf-if-range-te-0/0-47)#no flowcontrol rx on tx offFTOS(conf-if-range-te-0/0-47)#exit3.2Disable 802.3x flowcontrol on all QSFP portsFTOS(conf)#interface range fortyGigE 0/48 , fortyGigE 0/52FTOS(conf-if-range-fo-0/48,fo-0/52)#no flowcontrol rx on tx offFTOS(conf-if-range-fo-0/48,fo-0/52)#exit3.3Enable DCB and reloadFTOS(conf)#dcb enableFTOS(conf)#exitFTOS#copy running-config startup-configFTOS#reload3.4Create tagged VLAN for all ports and port-channelsFTOS>enableFTOS#configureFTOS(conf)#interface vlan vlan-idFTOS (conf-if-vl-vlan-id*)#no shutdownFTOS (conf-if-vl-vlan-id*)#tagged tengigabitethernet 0/0-47FTOS (conf-if-vl-vlan-id*)#tagged port-channel 1FTOS (conf-if-vl-vlan-id*)#exit3.5Configure DCB policiesFTOS(conf)#dcb-map profile-nameFTOS(conf-dcbmap-profile-name*)#priority-group 0 bandwidth 50 pfc offFTOS(conf-dcbmap-profile-name*)#priority-group 1 bandwidth 50 pfc onFTOS(conf-dcbmap-profile-name*)#priority-pgid 0 0 0 0 1 0 0 0FTOS(conf-dcb-profile-name*)#exit3.6Apply policies to switch portsFTOS(conf)#interface range ten 0/0 – 47FTOS(conf-if-range-te-0/0-47)# dcb-map profile-nameFTOS(conf-if-range-te-0/0-47)#exitFTOS(conf)#interface range fortyGigE 0/48 , fortyGigE 0/52FTOS(conf-if-range-fo-0/48,fo-0/52)# dcb-map profile-nameFTOS(conf-if-range-fo-0/48,fo-0/52)#exitFTOS(conf)#exit3.7Save configurationFTOS#copy running-config startup-config3.8Configure additional switchesRepeat the commands from section 3 to configure DCB on additional switches.4Reverting from DCB to non-DCB configuration (optional) One method to revert from a DCB configured switch to a non-DCB configured switch is to delete thecurrent configuration (startup-config) and follow the steps in section 2. If deleting the currentconfiguration is not an option, then use the following procedure to unconfigure DCB and enable standardflow control.4.1Disable DCBFTOS#configureFTOS(conf)#no dcb enableFTOS(conf)#exit4.2Remove DCB policies and apply standard flow controlFTOS#configureFTOS(conf)#interface range tengigabitethernet 0/0 - 47FTOS(conf-if-range-te-0/0-47)# no dcb-map profile-nameFTOS(conf-if-range-te-0/0-47)#flowcontrol rx on tx offFTOS(conf-if-range-te-0/0-47)#exitFTOS(conf)#interface range fortyGigE 0/48 , fortyGigE 0/52FTOS(conf-if-range-fo-0/48,fo-0/52)#no dcb-map profile-nameFTOS(conf-if-range-fo-0/48,fo-0/52)#flowcontrol rx on tx offFTOS(conf-if-range-fo-0/48,fo-0/52)#exitFTOS(conf)#exit4.3Revert to default VLAN ID on switch and arraysOnce DCB is disabled on the switch, the PS arrays will no longer use the VLAN ID that was configuredwhen DCB was enabled. The arrays will revert to the default or native VLAN. Therefore, a valid VLAN mustbe configured for all host servers, switches, and PS array members. A valid VLAN can use the default ornative VLAN ID (typically 0 or 1) or a specific VLAN can be configured (for example, VLAN 100). If a non-default VLAN is configured, then any ports connected to the arrays must be configured as “untagged”.Use the steps below to configure the native VLAN on the switch.FTOS#configureFTOS(conf)#no interface vlan vlan-id4.4Save configurationFTOS#copy running-config startup-config4.5ReloadFTOS#reloadSystem configuration has been modified. Save? [yes/no]yesProceed with reload [confirm yes/no]yes4.6Verify DCB statusFTOS#show dcb4.7Configure additional switchRepeat the commands from section 4 to disable DCB on any additional switches.5Optional stack configurationOne advantage of stacked switches is that they can be managed as a single switch; however firmwareupdates will update all members of the stack simultaneously and therefore should only be done duringplanned downtime.5.1Delete startup configuration on the first switchFTOS>enableFTOS#delete startup-configProceed to delete startup-config [confirm yes/no]yesFTOS#reloadSystem configuration has been modified. Save? [yes/no]noProceed with reload [confirm yes/no]yes5.2Configure stack on the first switchFTOS>enableFTOS#configFTOS(conf)#stack-unit 0 priority 1FTOS(conf)#stack-unit 0 stack-group 12FTOS(conf)#stack-unit 0 stack-group 13FTOS(conf)#exitFTOS#copy running-config startup-configFTOS#reload5.3Delete startup configuration on the second switchFTOS>enableFTOS#delete startup-configProceed to delete startup-config [confirm yes/no]yesFTOS#reloadSystem configuration has been modified. Save? [yes/no]noProceed with reload [confirm yes/no]yes5.4Configure stack on the second switchFTOS>enableFTOS#stack-unit 0 renumber 1FTOS#configFTOS(conf)#stack-unit 1 priority 1FTOS(conf)#stack-unit 1 stack-group 12FTOS(conf)#stack-unit 1 stack-group 13FTOS(conf)#exitFTOS# copy running-config startup-configFTOS#reload5.5Verify stack configurationFrom the first switch (Master) CLI, confirm that the stack has formed:FTOS#show redundancy5.6Configure out of band (OOB) management portFTOS#configFTOS(conf)#interface ManagementEthernet 0/0FTOS(conf-if-ma-0/0)#no shutdownFTOS(conf-if-ma-0/0)#ip address ipaddress maskFTOS(conf-if-ma-0/0)#no shutdownFTOS(conf-if-ma-0/0)#exit5.7Configure route for OOB management port (optional)FTOS(conf)#management route X.Y.Z.0 /24 A.B.C.15.8Configure login credentialsFTOS(conf)#username admin privilege 15 password 0 yourpasswordFTOS(conf)#enable password level 15 0 yourpassword5.9Configuring switch portsFTOS(conf)#interface range tengigabitethernet 0/0 – 47FTOS(conf-if-range-te-0/0-47)#mtu 12000FTOS(conf-if-range-te-0/0-47)#switchportFTOS(conf-if-range-te-0/0-47)#spanning-tree rstp edge-portFTOS(conf-if-range-te-0/0-47)#flowcontrol rx on tx offFTOS(conf-if-range-te-0/0-47)#no shutdownFTOS(conf-if-range-te-0/0-47)#exitFTOS(conf)#interface range tengigabitethernet 1/0 – 47FTOS(conf-if-range-te-1/0-47)#mtu 12000FTOS(conf-if-range-te-1/0-47)#switchportFTOS(conf-if-range-te-1/0-47)#spanning-tree rstp edge-portFTOS(conf-if-range-te-1/0-47)#flowcontrol rx on tx offFTOS(conf-if-range-te-1/0-47)#no shutFTOS(conf-if-range-te-1/0-47)#exitFTOS(conf)#exitFTOS(conf)#protocol spanning-tree rstpFTOS(conf-rstp)#no disableFTOS(conf-rstp)#exitFTOS(conf)#exit5.10Save configurationFTOS# copy running-config startup-configReload the stack to allow settings to take effect:FTOS#reload21 SCG1005Dell Networking and Force10 S4820T Switch Configuration Guide for PS Series SANsAdditional resources/support is focused on meeting your needs with proven services and support. is an IT Community where you can connect with Dell Customers and Dell employees for the purpose of sharing knowledge, best practices, and information about Dell products and yourinstallations.Referenced or recommended Dell publications:∙Dell PS Series Configuration Guide:/dell-groups/dtcmedia/m/mediagallery/19852516∙Dell Storage Compatibility Matrix:/techcenter/storage/w/wiki/5069.dell-storage-compatibility-matrix-ps-series-sc-series-fs-seriesFor PS Series best practices white papers, reference architectures, and sizing guidelines for enterpriseapplications and SANs, refer to PS Series Technical Documents.。

交换机配置

交换机配置

通常,动态vlan的实现需要借助相应的智能管理软件。动态vlan更加灵活,但增加了交换机的负担。
-----------------------------------------------------------------------------------------------------------
动态valn:将PC的MAC地址或IP地址指定给vlan。这样,交换机需要建立一个vlan数据库,将Vlan的编号或名称与ip地址、mac地址、协议号等信息关联起来,
当数据包到来时判断其IP地址、MAC地址、协议类型等信息,然后根据这些信息查询vlan数据库,确定该数据包属于的vlan,并自动将当前连接的端口指定到该vlan。
Enter configuration commands, one per line. End with CNTL/Z.
Switch(config)#vlan 2 //创建vlan2
Switch(config-vlan)#name caiwu //命名为caiwu“财务”
Switch(config-vlan)#exit
Switch(config-line)#
5)配置交换机的特权模式口令
如果使用远程登录的方式控制交换机,要求交换机必须配置特权模式口令
Switch(config)#enable password 123
Switch(config)#
6)在PC上运行Telnet
PC>telnet 192.168.1.254
4)配置交换机的Telnet服务
Switch(config)#line vty 0 5 //进入交换机虚拟控制口,最多可以有6个连接

思科交换机基本配置命令

思科交换机基本配置命令

思科交换机基本配置命令目录1、基本概念介绍 (2)2、密码、登陆等基本配置 (2)3、CISCO设备端口配置详解 (4)4、VLAN的规划及配置 (6)4.1核心交换机的相关配置 (6)4.2接入交换机的相关配置 (8)5、配置交换机的路由功能 (9)6、配置交换机的DHCP功能 (9)7、常用排错命令 (10)1、基本概念介绍IOS: 互联网操作系统,交换机和路由器常用操作系统VLAN: 虚拟lanVTP: VLAN TRUNK PROTOCOLDHCP: 动态主机配置协议ACL:访问控制列表三层交换机:具有三层路由转发能力的交换机2、密码、登陆等基本配置本节介绍cisco路由器或者交换机的基本配置,本教程用的是cisco的模拟器做的介绍,一些具体的端口显示可能与实际的设备不符,但并不影响基本配置命令的执行。

Router># 显示稳定后,出现最初的提示符,提示符“>”表示目前所处的状态为用户模式。

Router>Router>en# 如果在当前状态下没有重复的命令,可以用“TAB”键来补齐命令Router>enable# 从用户模式(user mode)进入到特权模式(exec mode),提示符变为“#”Router#configure terminal#在特权模式下输入configure terminal进入全局配置模式(global configuration mode),在这之下输入的命令叫做全局命令,一旦输入,将对整个router产生即时影响。

*Mar 1 00:44:26.491: %SYS-5-CONFIG_I: Configured from console by console t # 在输入命令的过程中,IOS会出现一些即时提示。

Enter configuration commands, one per line. End with CNTL/Z.Router(config)#exit # 退出当前模式Router(config)#hostname test# 更改当前设备的名字,主要是为了便于区分设备。

思科交换机简单配置(通用教程)

思科交换机简单配置(通用教程)

端口镜像配置
• Cisco 3560G配置
全局配置下:
Switch(config)#monitor session 1 destination interface gigabitEthernet 0/1 Switch(config)#monitor session 1 source interface gigabitEthernet 0/2 both Switch(config)#monitor session 1 source interface gigabitEthernet 0/3 both
• 双工模式: Switch(config-if)#duplex ? auto Enable AUTO duplex configuration full Force full duplex operation half Force half-duplex operation
Switch(config-if)#duplex auto Switch(config-if)# • 端口描述 Switch(config-if)#description vlan 10 trunk Switch(config-if)#
• 全局模式下进入端口后,可以对端口进行配置。 Switch#conf t Switch(config)#interface gigabitEthernet 0/1 Switch(config-if)# 批量修改端口 range命令
端口速率: Switch(config-if)#speed ? 10 Force 10 Mbps operation 100 Force 100 Mbps operation 1000 Force 1000 Mbps operation auto Enable AUTO speed configuration Switch(config-if)#speed auto Switch(config-if)#

DELL+Force10交换机

DELL+Force10交换机

DELL+Force10交换机DELL Force10交换机简明配置手册Mark Wang2015年4月12日目录1简介 (1)2写在前面 (1)3Console使用 (1)4交换机使用技巧 (2)4.1TAB键自动补全 (2)4.2善于使用问号 (2)4.3反向删除命令 (3)5BMP/Jump-Start模式 (3)6接口的基本配置 (4)6.1接口启用 (4)6.2接口速率修改 (5)7交换机管理 (5)7.1启用Telnet/SSH服务 (5)7.2创建用户名和密码 (5)7.3管理IP的配置 (6)7.3.1带内管理IP (6)7.3.2带外管理IP (6)7.4保存交换机配置 (6)7.5重启交换机 (6)7.6恢复默认设置 (7)8交换机时间与日期 (7)8.1本地系统时间 (7)8.2NTP校时服务器 (7)8.3日志时间戳 (7)9Access/Trunk/Hybird配置 (7)9.1例1.配置Access模式 (8)9.2例2.配置Trunk模式 (8)9.3例3.配置Hybird模式 (8)10生成树配置 (9)10.1RSTP协议 (9)10.2PVST协议 (10)10.3MSTP协议 (10)11链路聚合配置 (11)11.1例1.静态聚合 (11)11.2例CP动态聚合 (11)12VRRP配置 (12)12.1Master主机配置VRRP (12)12.2Standby主机配置VRRP (13)13802.1X认证 (13)14LLDP配置 (14)15DHCP服务器 (14)16本地端口镜像 (15)17sflow配置 (15)18上行链路状态跟踪 (15)19恢复密码 (16)20交换机固件更新 (16)21收集日志 (16)22附录一 (17)23附录二 (17)1简介目前DELL有定位为园区/企业级别的PowerConnect系列交换机、N系列交换机以及定位为数据中心级别的Force10系列交换机(下文可能会简称为F10),其中Force10系列交换机还分为S系列、C系列、E系列、Z系列以及刀箱上的MXL/MIO等。

交换机操作说明

交换机操作说明

交换机操作说明
一、连接交换机
首先,将交换机的电源线插入电源插座,然后将网线连接至交换机的LAN口,再将另一端连接至电脑或其他网络设备的LAN口。

二、登录管理界面
打开电脑上的浏览器,在地址栏中输入交换机的默认IP地址,按下回车键。

输入正确的用户名和密码登录管理界面。

三、设置交换机参数
在管理界面中,可以按需设置交换机的基本参数,包括端口速度、VLAN配置、QoS设置等。

确保所做改动符合网络规划要求。

四、查看端口状态
在管理界面中,可以查看每个端口的连接状态、速率、流量情况等信息。

及时发现问题并采取措施解决。

五、检查配置保存
在修改完参数后,务必点击保存或应用按钮,将设置生效并保存至交换机。

避免设置因为未保存而丢失。

六、退出管理界面
在完成所有设置后,记得登出管理界面,确保交换机安全度。

以上即为交换机的操作说明,希望能帮助您正确使用交换机,保障网络稳定运行。

戴尔Force10配置指南说明书

戴尔Force10配置指南说明书

Dell Force10 Configuration Guide for the MXL 10/40GbESwitch IO ModulePublication Date: March 2013Notes, Cautions, and WarningsNOTE: A NOTE indicates important information that helps you make better use of your computer.CAUTION: A CAUTION indicates either potential damage to hardware or loss of data and tells you how to avoid the problem.WARNING: A WARNING indicates a potential for property damage, personal injury, or death.Information in this publication is subject to change without notice.© 2013 Dell Force10. All rights reserved.Reproduction of these materials in any manner whatsoever without the written permission of Dell Inc. is strictly forbidden.Trademarks used in this text: Dell™, the DELL logo, Dell Precision™, OptiPlex™, Latitude™, PowerEdge™, PowerVault™, PowerConnect™, OpenManage™, EqualLogic™, KACE™, FlexAddress™ and V ostro™ 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®, MS-DOS® and Windows Vista® are either trademarks or registered trademarks of Microsoft Corporation in the United States and/or other countries. Red Hat Enterprise Linux® and Enterprise Linux® are registered trademarks of Red Hat, Inc. in the United States and/or other countries. Novell® is a registered trademark and SUSE ™ is a trademark 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®, Virtual SMP®, vMotion®, vCenter®, and vSphere®are registered trademarks or trademarks of VMWare, Inc. in the United States or other countries.Other trademarks and trade names may be used in this publication to refer to either the entities claiming the marks and names or their products. Dell Inc. disclaims any proprietary interest in trademarks and trade names other than its own.March 20131About this Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23 Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .24Information Symbols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .24Related Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .242Configuration Fundamentals. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25 Accessing the Command Line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25CLI Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26 Navigating CLI Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27 The do Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29Undoing Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30Obtaining Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .31Entering and Editing Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .32Command History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .33Filtering show Command Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .33Multiple Users in Configuration Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .353Getting Started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .37 Console access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .37 Serial Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .37External Serial Port with a USB Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .39 Boot Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .39Default Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .42Configure a Host Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .42Access the System Remotely . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .42 Access the MXL Switch Remotely . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .42Configure the Management Port IP Address. . . . . . . . . . . . . . . . . . . . . . . . . . . .43Configure a Management Route . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .43Configure a Username and Password. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .44 Configure the Enable Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .44Configuration File Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .45 Copy Files to and from the System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .45Important Points to Remember . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .45 Save the Running-Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .46View Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .47View Configuration Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .48 File System Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .49View the Command History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .50Upgrading and Downgrading FTOS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .50|12|www.dell.com|support.dell.com 4Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .51Configure Privilege Levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .51Create a Custom Privilege Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .51Removing a Command from EXEC Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .52Move a Command from EXEC Privilege Mode to EXEC Mode. . . . . . . . . . . . . .52Allow Access to CONFIGURATION Mode Commands . . . . . . . . . . . . . . . . . . . .52Allow Access to INTERFACE, LINE, ROUTE-MAP , and ROUTER Mode. . . . . .52Apply a Privilege Level to a Terminal Line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .55Configure Logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .55Log Messages in the Internal Buffer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .55Configuration Task List for System Log Management . . . . . . . . . . . . . . . . . . . . . . . .55Disable System Logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .56Send System Messages to a Syslog Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .56Configure a Unix System as a Syslog Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .56Change System Logging Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .56Display the Logging Buffer and the Logging Configuration . . . . . . . . . . . . . . . . . . . . . . .57Configure a UNIX Logging Facility Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .59Synchronize log messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .60Enable timestamp on Syslog Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .61File Transfer Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .61Configuration Task List for File Transfer Services . . . . . . . . . . . . . . . . . . . . . . . . . . .61Enable the FTP Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .62Configure the FTP Server Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .62Configure FTP Client Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .63Terminal Lines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .63Configure Login Authentication for Terminal Lines . . . . . . . . . . . . . . . . . . . . . . . . . .64Time Out of EXEC Privilege Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .65Telnet to Another Network Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .66Lock CONFIGURATION Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .66Viewing the Configuration Lock Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .67Recovering from a Forgotten Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .68Recovering from a Forgotten Enable Password . . . . . . . . . . . . . . . . . . . . . . . . . . . .68Recovering from a Failed Start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .695Access Control Lists (ACLs) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .71Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .71IP Access Control Lists (ACLs) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .72Implementing ACLs on FTOS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .72ACLs and VLANs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .73ACL Optimization. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .73Determine the Order in Which ACLs are Used to Classify Traffic . . . . . . . . . . . .73IP Fragment Handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .74IP Fragments ACL Examples. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .74Layer 4 ACL Rules Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .75 Configure a Standard IP ACL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .76Configure an Extended IP ACL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .78Configure Filters with a Sequence Number. . . . . . . . . . . . . . . . . . . . . . . . . . . . .79Configure Filters Without a Sequence Number. . . . . . . . . . . . . . . . . . . . . . . . . .79 Established Flag . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .80 Configuring Layer 2 and Layer 3 ACLs on an Interface . . . . . . . . . . . . . . . . . . . . . . . . . .81Assign an IP ACL to an Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .81 Counting ACL Hits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .82 Configuring Ingress ACLs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .83Configuring Egress ACLs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .84 Egress Layer 3 ACL Lookup for Control-Plane IP Traffic . . . . . . . . . . . . . . . . . . . . .84 IP Prefix Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .85 Implementation Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .86Configuration Task List for Prefix Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .86Configure a Prefix List. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .86Use a Prefix List for Route Redistribution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .89 ACL Resequencing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .90 Resequencing an ACL or Prefix List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .91 Route Maps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .92 Implementation Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .92Important Points to Remember . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .92Configuration Task List for Route Maps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .93Create a Route Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .93Configure Route Map Filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .95Configure a Route Map for Route Redistribution. . . . . . . . . . . . . . . . . . . . . . . . .97Configure a Route Map for Route Tagging . . . . . . . . . . . . . . . . . . . . . . . . . . . . .97Continue Clause . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .986Bare Metal Provisioning (BMP). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .101 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .101Auto-Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .103 BMP Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .103MAC-Based IP Assignment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .103DHCP Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .104IP Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .105Domain Name Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .105 Boot Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .106System Boot and Set-Up Behavior . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1067Content Addressable Memory (CAM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .109 CAM Allocation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .109Test CAM Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .110|34|w w w .d e l l .c o m | s u p p o r t .d e l l .c o m View CAM-ACL Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .111CAM Optimization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1128Data Center Bridging (DCB) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113Ethernet Enhancements in Data Center Bridging . . . . . . . . . . . . . . . . . . . . . . . . . . . . .113Priority-Based Flow Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .114Enhanced Transmission Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .115Data Center Bridging Exchange Protocol (DCBX) . . . . . . . . . . . . . . . . . . . . . . . . .117Data Center Bridging in a Traffic Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .117Enabling Data Center Bridging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .118QoS dot1p Traffic Classification and Queue Assignment . . . . . . . . . . . . . . . . . . . . . . .119Configuring Priority-Based Flow Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .120Configuring Lossless Queues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .122Configuring the PFC Buffer in a Switch Stack . . . . . . . . . . . . . . . . . . . . . . . . . . . . .123Configuring Enhanced Transmission Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .124ETS Prerequisites and Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .124Creating a QoS ETS Output Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .125Creating an ETS Priority Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .127Applying an ETS Output Policy for a Priority Group to an Interface . . . . . . . . . . . .128ETS Operation with DCBX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .129Configuring Bandwidth Allocation for DCBX CIN . . . . . . . . . . . . . . . . . . . . . . . . . .129Applying DCB Policies in a Switch Stack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .131Configuring DCBX Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .132DCBX Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .132DCBX Port Roles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .133DCB Configuration Exchange . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .134Configuration Source Election . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .135Propagation of DCB Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .135Auto-Detection and Manual Configuration of the DCBX Version . . . . . . . . . . . . . .136DCBX Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .136DCBX Prerequisites and Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .137DCBX Configuration Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .138Configuring DCBX on an Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .138Configuring DCBX Globally on the Switch. . . . . . . . . . . . . . . . . . . . . . . . . . . . .140DCBX Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .141An error in DCBX operation is displayed using the following syslog messages:141Debugging DCBX on an Interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .142Verifying DCB Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .143PFC and ETS Configuration Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .153Using PFC and ETS to Manage Data Center Traffic . . . . . . . . . . . . . . . . . . . . . . . .153Using PFC and ETS to Manage Converged Ethernet Traffic in a Switch Stack . . .156Hierarchical Scheduling in ETS Output Policies . . . . . . . . . . . . . . . . . . . . . . . . . . .1579Dynamic Host Configuration Protocol (DHCP) . . . . . . . . . . . . . . . . . . . . . . . . . .159 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .159 DHCP Packet Format and Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .160Assigning an IP Address Using DHCP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .161 Implementation Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .162Configuration Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .162Configure the System to be a DHCP Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .162 Configuration Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .163Related Configuration Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .163 Configure the Server for Automatic Address Allocation . . . . . . . . . . . . . . . . . . . . . .163Create an IP Address Pool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .163Exclude Addresses from the Address Pool . . . . . . . . . . . . . . . . . . . . . . . . . . . .164Specify an Address Lease Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .164 Specify a Default Gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .164Enable DHCP Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .165Configure a Method of Hostname Resolution . . . . . . . . . . . . . . . . . . . . . . . . . . . . .165Address Resolution using DNS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .165Address Resolution using NetBIOS WINS . . . . . . . . . . . . . . . . . . . . . . . . . . . .166 Create Manual Binding Entries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .166Debug DHCP Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .167DHCP Clear Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .167 Configure the System to be a Relay Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .167Configure the System to be a DHCP Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .169 DHCP Client on a Management Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .175DHCP Client Operation with other Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .176Stacking. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .176VLT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .176VLAN and Port Channels. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .176DHCP Snooping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .176DHCP Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .176VRRP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .177 Configure Secure DHCP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .178 Option 82 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .178DHCP Snooping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .179Enable DCHP Snooping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .179Add a Static Entry in the Binding Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .180Clear the Binding Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .180Display the Contents of the Binding Table. . . . . . . . . . . . . . . . . . . . . . . . . . . . .180 Drop DHCP Packets on Snooped VLANs Only . . . . . . . . . . . . . . . . . . . . . . . . . . .181Dynamic ARP Inspection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .182Bypass the ARP Inspection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .184 Source Address Validation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .184IP Source Address Validation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .185|56|w w w .d e l l .c o m | s u p p o r t .d e l l .c o m DHCP MAC Source Address Validation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .185IP+MAC Source Address Validation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18510FIP Snooping. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .187Fibre Channel over Ethernet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .187Ensuring Robustness in a Converged Ethernet Network . . . . . . . . . . . . . . . . . . . . . . .187FIP Snooping on Ethernet Bridges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .189FIP Snooping in a Switch Stack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .191Configuring FIP Snooping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .191Enabling the FIP Snooping Feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .192Enabling FIP Snooping on VLANs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .192Configuring the FC-MAP Value . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .192Configuring a Port for a Bridge-to-FCF Link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .193Impact on other Software Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .193FIP Snooping Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .193FIP Snooping Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .194Configuration Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .194Displaying FIP Snooping Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .195FIP Snooping Configuration Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20211GARP VLAN Registration Protocol (GVRP) . . . . . . . . . . . . . . . . . . . . . . . . . . . .205Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .205Important Points to Remember . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .205Configuring GVRP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .206Related Configuration Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .207Enabling GVRP Globally . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .208Enabling GVRP on a Layer 2 Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .208Configuring GVRP Registration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .208Configuring a GARP Timer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20912Internet Group Management Protocol (IGMP). . . . . . . . . . . . . . . . . . . . . . . . . . . 211Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .211IGMP Version 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .211Joining a Multicast Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .212Leaving a Multicast Group. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .212IGMP Version 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .213Joining and Filtering Groups and Sources. . . . . . . . . . . . . . . . . . . . . . . . . . . . .214Leaving and Staying in Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .215IGMP Snooping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .215IGMP Snooping Implementation Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . .216Configuring IGMP Snooping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .216Related Configuration Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .216。

Force10交换机配置手册

Force10交换机配置手册

Force10 S25N/S50N交换机配置手册目录前言........................................................... 错误!未定义书签。

1. FORCE10 S系列交换机登陆初始配置 ............................. 错误!未定义书签。

使用CONSOLE口登陆方式.......................................... 错误!未定义书签。

用以太网线使用TELNET方式....................................... 错误!未定义书签。

2.创建VLAN ..................................................... 错误!未定义书签。

创建一个基于端口的V LAN......................................... 错误!未定义书签。

3.配置TRUNK .................................................... 错误!未定义书签。

创建一个TRUNK.................................................. 错误!未定义书签。

4.开启端口FLOW-CONTROL 、SPANNING-TREE、和EDGED-PORT ........... 错误!未定义书签。

前言1. Force10 S系列交换机登陆初始配置使用console口登陆方式第一步:如图所示,建立本地配置环境。

S25的Console口是标准的RJ45口,所以需要用标准网线连接一个RJ45/串口转换器(在交换机的包装箱里带有),网口连接交换机的Console口,串口与PC机(或终端)的串口连接。

通过Console口搭建本地配置环境第二步:在PC机上运行终端仿真程序(如Windows 的Terminal或Windows 9X/Windows 2000/Windows XP的超级终端等,以下配置以Windows XP为例),选择与交换机相连的串口,设置终端通信参数:传输速率为9600bit/s、8位数据位、1位停止位、无校验和无流控,如图所示。

Dell Force10 S-Series S60高性能访问交换机说明书

Dell Force10 S-Series S60高性能访问交换机说明书

S-Series S60 high-performance access switch The Dell Force10 S-Series S60 is a high-performance 1/10 GbE access switch optimized for lowering operational costs at the network edge. The S60 answers the key challenges related to network congestion in data center ToR (Top-of-Rack) and service provider aggregation deployments. As the use of bursty applications and services continue to increase, huge spikes in network traffic that can cause network congestion and packet loss, also become more common. The S60 is equipped with the industry’s largest packet buffer (1.25 GB), enabling it to deliver lower application latency and maintain predictable network performance even when faced with significant spikes in network traffic. Providing 48 line-rate GbE ports and up to four optional 10 GbE uplinks in just 1-RU, theS60 conserves valuable rack space. Further, the S60 design delivers unmatched configuration flexibility, high reliability, and power and cooling efficiency to reduce costs.In addition to delivering a compact and scalable design, the S60 also supports the Dell Force10 Open Automation Framework, which provides advanced network automation and virtualization capabilities for virtual data center environments. The Open Automation Framework is comprised of a suite of inter-related network management tools that can be used together or independently to provide a network that is more flexible, available and manageable while reducing operational expenses. Applications• Line-rate 1/10 GbE server aggregation at the ToR in high-performance data center environments• Design with the E-Series virtualized switch/router to cre-ate a flat, two-tier, non-blocking 1/10 GbE data center network design• High-performance GbE aggregation, switching and routing in service provider edge or access networks Key features• The 1-RU S60 switch delivers 48 GbE access interfaces – 44 10/100/1000Base-T copper ports (RJ45)– 4 GbE ports that can be configured for fiber or copper (SFP)• Plus, the S60 provides two optional high-speed slots that support any of the following uplink modules:– 2-port 10 GbE (SFP+ modules)– 2-port 12 Gbps stacking module– 1-port 24 Gbps stacking module• Ultra-deep packet buffering (1.25 GB) eliminates congestion associated with bursty applications and services • Energy-efficient, versatile design supports the lowest power consumption in its class as well asreversiblefront-to-back or back-to-front airflow• High-capacity 176 Gbps switch fabric delivers line-rate, low-latency switching• Highly scalable Layer-2 and Layer-3 switching with a full complement of standards-based IPv4 and IPv6 features for unicast and multicast applications• Force10’s Open Automation Framework adds VM-awareness as well as automated configuration and provisioning capabilities to simplify the management of virtual network environments• Carrier-class, NEBS Level 3 Certified product design supports redundant, hot-swappable power supplies (AC or DC) and fans• Stacking technology enables up to 12 S60 switches to be managed as a single unit• Modular Dell Force10 Operating System (FTOS) software delivers inherent stability as well as advanced monitoring and serviceability functions• VirtualView™ real-time network and application traffic monitoring for virtualized data centers• Supports 9,252 byte jumbo framesWire-speed 1/10GbEwith Ultra-deep packet buffering delivers consistent & efficient application performanceDell Force10 S-SeriesS60 high-performance 1/10 GbE access switch with Ultra-deep packet bufferingNon-blocking, line-rate switching and routing; stackable 48-port GbE switch with up to four 10 GbE ports in just 1RU; ultra-deep packet buffering; integrated network automation and virtualization technologywith Dell Force10’s Open Automation Framework; flexible, resilient and energy-efficient design.Learn more at /Networking© 2011 Dell Inc. All rights reserved. Force10 Networks, Adit, E-Series, Traverse, and TraverseEdge are registered trademarks and Axxius, C-Series, ExaScale, FTOS,MASTERseries, P-Series, S-Series, TeraScale, TransAccess, and VirtualView are trademarks of Dell Inc. All other company names are trademarks of their respective holders. Information in this document is subject to change without notice. Dell Inc. assumes no responsibility for any errors that may appear in this document.SS789_Dell_Force10_S60_091211_110111Specifications: S60 high-performance 1/10 GbE access switchOrder Number Description225-2499 S60 switch*, AC, rear to front airflow 225-2450 S60 switch*, AC, front to rear airflow 225-2451 S60 switch*, DC, rear to front airflow 225-2500 S60 switch*, DC, front to rear airflow 331-5233 2-port 10 GbE high-speed uplink module (SFP+)331-5235 2-port 12 Gigabit high-speed stacking module 331-5234 1-port 24 Gigabit high-speed stacking module 331-5261 4m 12 Gbps S60/S50/S25 stacking cable 331-5263 4m 24 Gbps S60/S50/S25 stacking cable 331-5264 60cm 12 Gbps S60/S50/S25 stacking cable 331-5265 60cm 24 Gbps S60/S50/S25 stacking cable 331-5231 Fan module with rear to front airflow 331-5232 Fan module with front to rear airflow 331-5225 AC power supply module331-5226 AC power supply module, reverse airflow 331-5227 DC power supply module331-5228 DC power supply module, reverse airflow 421-6955Layer 3 FTOS software upgrade, latest versionSFP and SFP+ modules are ordered separately*Each S60 switch includes 44 10/100/1000 Base-T ports, 4 GbE (SFP) interfaces and 2 high-speed slots, dual hot-swappable fans, and 1 AC or DC power supply module. The S60 I/O panel is considered the rear, the power supply panel is considered the front.Physical44 10/100/1000Base-T RJ45 ports 4 GbE SFP ports1 RJ45 console/management port with RS232 signaling 2 USB 2.0 ports (1 USB A, 1 USB B)Optional uplink 2 line-rate ports 10 Gigabit Ethernet SFP+modules: 2 line-rate ports 12 Gigabit Stacking1 line-rate port 24 Gigabit StackingSize: 1 RU, 1.7 h x 17.32 w x 16.73” d (4.3 h x 44 w x 42.5 cm d)Weight: 14.39 lbs (6.54 kg)ISO 7779 A-weighted sound pressure level: 59.6 dBA at 73.4°F (23°C)Power supply: 100–240 VAC 50/60 Hz, –44 to -60 VDC Max. thermal output: 531 BTU/h Max. current draw per system: 2 A at 100/120 VAC, 1 A at 200/240 VAC, 3.6 A at -48 VDC Max. power consumption: 225 W Max. operating specifications: Operating temperature: 32° to 122°F (0° to 50°C) Operating humidity: 10 to 85% (RH), non-condensing Max. non-operating specifications: Storage temperature: –40° to 158°F (–40° to 70°C) Storage humidity: 5 to 95% (RH), non-condensing Reliability: MTBF 169,315 hoursRedundancyRing stacking topology with dynamic master electionDual modular slots with up to four 10 GbE ports Link aggregation across stack members Hot swappable redundant AC or DC power Hot swappable redundant fansPerformanceMAC addresses: 32K IPv4 routes: 16K IPv6 routes: 8K Switch fabric capacity: 176 Gbps Forwarding capacity 132 Mpps Link aggregation: 8 links per group, 128 groups per stack Stacking capacity: 96 Gbps per stack member Queues per port: 4 queues VLANs: 4096Line-rate Layer 2 switching: all protocols, including IPv4 and IPv6Line-rate Layer 3 routing: IPv4 and IPv6LAG load balancing: based on Layer 2, IPv4 or IPv6 headers Switching latency: <9 µs for 64 byte frames Packet buffer memory: 1.25GB CPU memory: 2GBIEEE Compliance802.1AB LLDP 802.1ag Connectivity fault Management 802.1D Bridging, STP 802.1p L2 Prioritization802.1Q VLAN Tagging, Double VLAN Tagging, GVRP 802.1s MSTP 802.1w RSTP 802.1X Network Access Control 802.3ab Gigabit Ethernet (1000BASE-T)802.3ac Frame Extensions for VLAN Tagging 802.3ad Link Aggregation with LACP 802.3ae 10 Gigabit Ethernet (10GBASE-X)802.3ak 10 Gigabit Ethernet (10GBASE-CX4)802.3i Ethernet (10BASE-T)802.3u Fast Ethernet (100BASE-TX)802.3x Flow Control 802.3z Gigabit Ethernet (1000BASE-X)ANSI/TIA-1057 LLDP-MED Force10 PVST+MTU 9,252 bytesRFC and I-D ComplianceGeneral Internet Protocols768 UDP 1321 MD5 793 TCP 1350 TFTP854 Telnet 2474 Differentiated Services 959 FTP3164 SyslogGeneral IPv4 Protocols791 IPv4 1812 Routers792 ICMP 1858 IP Fragment Filtering 826 ARP2131 DHCP (relay)1027 Proxy ARP 2338 VRRP1035 DNS (client)3021 31-bit Prefixes 1042 Ethernet T ransmission 3046 DHCP Option 821191 Path MTU Discovery 3069 Private VLAN1305 NTPv3 3128 Tiny Fragment Attack 1519 CIDRProtection1542 BOOTP (relay)General IPv6 Protocols1981 Path MTU Discovery 2463 ICMPv6(partial) 1858 IP Fragment Filtering 2460 IPv6 2675 Jumbograms 2461 Neighbor Discovery 3587 Global Unicast(partial) Address Format 2462 Stateless Address 4291 AddressingAutoconfiguration (partial)RIP1058 RIPv1OSPF2154 MD51587 NSSA 2328 OSPFv22370 Opaque LSABGP1997 Communities 2385 MD52439 Route Flap Damping 2796 Route Reflection 2842 Capabilities 2858 Multiprotocol Extensions 2918 Route Refresh 3065 Confederations 4360 Extended Communities 4893 4-byte ASN 5396 4-byte ASN representations draft-ietf-idr-bgp4-20 BGPv4draft-ietf-idr-restart-06 Graceful Restart draft-michaelson-4byte-as-representation-05 4-byte ASN Representation (partial)Multicast1112 IGMPv12236 IGMPv23376 IGMPv3draft-ietf-pim-sm-v2-new-05 PIM-SMNetwork Management1155 SMIv11156 Internet MIB 1157 SNMPv11212 Concise MIB Definitions 1215 SNMP T raps 1493 Bridges MIB1850 OSPFv2 MIB1901 Community-based SNMPv22011 IP MIB 2012 TCP MIB 2013 UDP MIB 2024 DLSw MIB 2096 IP Forwarding Table MIB 2570 SNMPv32571 Management Frameworks 2572 Message Processing and Dispatching 2574 SNMPv3 USM 2575 SNMPv3 VACM 2576 Coexistence Between SNMPv1/v2/v32578 SMIv22579 Textual Conventions for SMIv22580 Conformance Statements for SMIv22618 RADIUS Authentication MIB 2665 Ethernet-like Interfaces MIB 2674 Extended Bridge MIB 2787 VRRP MIB 2819 RMON MIB (groups 1, 2, 3, 9)2863 Interfaces MIB 2865 RADIUS 3273 RMON High Capacity MIB 3416 SNMPv23418 SNMP MIB 3434 RMON High Capacity Alarm MIB 3580 802.1X with RADIUS 5060 PIM MIB ANSI/TIA-1057 LLDP-MED MIB draft-grant-tacacs-02 TACACS+draft-ietf-idr-bgp4-mib-06 BGP MIBv1IEEE 802.1AB LLDP MIB IEEE 802.1AB LLDP DOT1 MIB IEEE 802.1AB LLDP DOT3 MIB ruzin-mstp-mib-02 MSTP MIB (traps) sFlowv5 MIB (version 1.3) FORCE10-BGP4-V2-MIB Force10 BGP MIB(draft-ietf-idr-bgp4-mibv2-05) FORCE10-IF-EXTENSION-MIB FORCE10-LINKAGG-MIBFORCE10-COPY-CONFIG-MIB FORCE10-MON-MIBFORCE10-PRODUCTS-MIB FORCE10-SS-CHASSIS-MIB FORCE10-SMIFORCE10-SYSTEM-COMPONENT-MIB FORCE10-TC-MIBFORCE10-TRAP-ALARM-MIBRegulatory ComplianceSafetyUL/CSA 60950-1, 1st Edition EN 60950-1, 1st EditionIEC 60950-1, 1st Edition Including all National Deviations and Group DifferencesEN 60825-1 Safety of Laser Products Part 1: Equipment Classification Requirements and User’s Guide EN 60825-2 Safety of Laser Products Part 2: Safety of Optical Fibre Communication Systems FDA Regulation 21 CFR 1040.10 and 1040.11EmissionsAustralia/New Zealand: AS/NZS CISPR 22: 2006, Class A Canada: ICES-003, Issue-4, Class AEurope: EN 55022: 2006 (CISPR 22: 2006), Class A Japan: VCCI V3/2007.04 Class AUSA: FCC CFR 47 Part 15, Subpart B, Class AImmunityEN 300 386 V1.3.3: 2005 EMC for Network Equipment EN 55024: 1998 + A1: 2001 + A2: 2003EN 61000-3-2: Harmonic Current Emissions EN 61000-3-3: Voltage Fluctuations and Flicker EN 61000-4-2: ESDEN 61000-4-3: Radiated Immunity EN 61000-4-4: EFT EN 61000-4-5: SurgeEN 61000-4-6: Low Frequency Conducted ImmunityRoHSAll S-Series components are EU RoHS compliant.。

思科交换机基本配置命令

思科交换机基本配置命令
test(config)#
test#conf s
Translating "s"...domain server (255.255.255.255)
% Unknown command or computer name, or unable to find computer address
#在做配置的时如果出现输入错误的情况,ios系统会以为用户输入的是一个域名,就会做长时间的搜寻,试图找到这个域名对应的ip地址,这段时间比较长
Hardware is Gigabit Ethernet Port, address is 001a.6db4.a3c1 (bia 001a.6db4.a3c1)
#此端口的MAC地址
......
Auto-duplex, Auto-speed, link type is auto, media type is 10/100/1000-TX
test(config)#no ip domain-lookup#在全局配置模式下,将ip域名的搜寻功能关闭就可以了
test#conf x#将上述功能关闭以后,再有输入错误的情况会直接提示你输入错误。
^
% Invalid input detected at '^' marker.
test(config)#ip domain-name 202.102.128.68
half Force half-duplex operation#强制此端口为半双工模式
test(config-if)#duplex auto#强制此端口的双工模式为自适应模式
test(config-if)#end#用end命令可直接退回到特权模式,用exit是一层一层的退出。

交换机简单配置说明

交换机简单配置说明

交换机简单配置命令说明1、交换机的几种模式简介 (1)2、交换机的相关配置命令 (2)1)配置密码的命令 (2)2)给交换机命名 (2)3)配置管理vlan的命令 (2)4)配置ACL的命令 (3)5)进入端口配置trunk的命令 (3)6)进入端口配置vlan的命令 (3)7)配置群体端口的命令 (3)8)设置三层交换机的system-guard功能 (4)9)设置三层交换机的风暴控制功能 (4)10)配置生成树命令(可以选用此配置用在和用户PC相连的21接入交换机上) (4)11)设置二层交换机缺省网关命令(21交换机的配置命令) (5)12)配置802。

1X的相关命令 (5)13)保存配置的命令 (6)3、交换机的一些查看命令简介 (6)4、交换机的优化配置建议 (8)35等三层交换机启用的安全优化策略 (8)21交换机的安全配置策略 (8)优化配置模拟拓扑图 (9)优化配置命令如下: (9)1、交换机的几种模式简介Switch> 用户模式(此模式只可以简单的查看一些交换机的配置和一些简单的修改如果原来配置有密码的,还要输入密码才可以进入)Switch> enable 用户模式输入enable将进入配置模式就是下面的示例,当然,命令可以简写为en:Switch#配置模式(这个模式可以查看一些交换机的配置,还可以对一些简单的设置配置,例如时间。

)Switch#configure terminal要想对交换机有进一步的操作权限,就必须进入全局配置模式,配置模式下可以通过config terminal 命令来达到这个目的,当然也可以使用简写命令con t Switch(config)# 全局配置模式(用户可以在这种状态下执行许多对交换机的配置命令,例如:命名、配置密码、设置服务、路由等等。

)但是仅仅有全局配置模式还是不够的,用户如果要细致的对每项参数进行配置,还必须进入到各自的参数单元中,下面举几个例子Switch(config)# interface gigabitEthernet 4/1从全局配置模式下进入到g 4/1接口模式下Switch(config)# interface vlan 111从全局配置模式下进入到vlan 111接口模式下则模式变为下面所示:Switch (config-if)#接口模式另外就是建立vlan的模式中,如下所示:Switch(config)# vlan 111Switch(config-vlan)#vlan 模式再举一例,就是配置ACL和动态路由的情况都是从全局配置模式下进入他们各自的子接口的:Switch(config)# ip access-list extended deny-portSwitch(config-ext-nacl)#exitSwitch(config)# router ospfSwitch(config-route)# exit好,上面是对交换机的几种工作模式做了个简单的讲解,现在具体来说一下几个交换机的简单的配置命令,这些命令都是通用的(二层和三层如果有区别的话我会注明)2、交换机的相关配置命令1)配置密码的命令Switch(config)# enable secret level 1 0 111 设置远程登陆密码为111(密码级别为1,加密模式为0表示明文模式输入)Switch(config)# enable secret level 15 0 111设置com口登陆密码为111(密码级别为15,加密模式为0表示明文模式输入)2)给交换机命名Switch(config)# hostname ### 给交换机命名###3)配置管理vlan的命令Switch# con t 用户模式进入全局配置模式命令Switch(config)# vlan 10这里假设管理vlan为vlan 10,建立vlan 10Switch(config-vlan)# exit退出Switch(config)# int vlan 10 进入vlan接口模式Switch(config-if)# ip address 192.168.1.254 255.255.255.0给vlan分配IP地址192.168.1.254 Switch(config-if)# no shut 激活vlan(这一步一定不要遗忘)Switch(config-if)# exit退出vlan端口模式4)配置ACL的命令Switch(config)# Ip access-list exten deny-port 建立acl访问控制列表Switch(config-ext-nacl)# deny tcp any any eq 135 对常用病毒的端口封堵规则Switch(config-ext-nacl)# deny tcp any any eq 139Switch(config-ext-nacl)# deny tcp any any eq 593Switch(config-ext-nacl)# deny tcp any any eq 4444Switch(config-ext-nacl)# deny udp any any eq 4444Switch(config-ext-nacl)# deny udp any any eq 135Switch(config-ext-nacl)# deny udp any any eq 137Switch(config-ext-nacl)# deny udp any any eq 138Switch(config-ext-nacl)# deny tcp any any eq 445Switch(config-ext-nacl)# deny udp any any eq 445Switch(config-ext-nacl)# deny udp any any eq 593Switch(config-ext-nacl)# deny tcp any any eq 593Switch(config-ext-nacl)# deny tcp any any eq 3333Switch(config-ext-nacl)# deny tcp any any eq 5554Switch(config-ext-nacl)# deny udp any any eq 5554Switch(config-ext-nacl)# permit ip any any 这个条件可别疏忽了:允许IP内网出去外网Switch(config-ext-nacl)# exit 退出acl配置模式5)进入端口配置trunk的命令tch(config)# interface fastethernet 0/24 进入端口0/24中Switch(config-if)# switchport mode trunk 把端口模式设置为trunk口(trunk为和交换机相连的通讯口,它会对不同的vlan间通讯的信息报文打上一个表示vlan的tag标记)Switch(config-if)# exit 退出端口模式6)进入端口配置vlan的命令Switch(config)# interface fastethernet 0/1进入到0/1接口Switch(config-if)# switchport access vlan 10把端口fastethernet 1/1加入进vlan 10 中Switch(config-if)# exit 退出端口模式7)配置群体端口的命令Switch(config)# interface range fastethernet 0/1-××多口配置命令配置1-××接口Switch(config-if)# switchport access vlan 10把端口加入进vlan 10 中Switch(config-if)# Ip access-group deny-port in把刚才配置的acl访问控制列表加入到具体端口中去Switch(config-if)# exit退出端口模式8)设置三层交换机的system-guard功能Switch(config)# interface fa 0/1进入接口模式fa 0/1 口Switch(config-if) # system-guard enable启用system-guard 功能还有详细的具体表项命令参考如下SWITCH(config-if)# system-guard ? 在system-guard 功能上细分,还可以人为的设置对攻击包的判断阀值enable Enable system guard on interfaceisolate-time Specify interval for isolate time in secondssame-ip-attack-packets Specify same ip attack pktsscan-ip-attack-packets Specify scan ip attack pkts9)设置三层交换机的风暴控制功能Switch(config)# interface fa 0/1 进入接口模式fa 0/1 口Switch(config-if) # storm-control broadcast 端口启用广播风暴控制SWITCH(config-if)# storm-control ?broadcast Broadcast address storm controlmulticast Multicast address storm controlunicast Unicast address storm control还有细分的风暴包数目控制,可以人为的设置对风暴包的判断阀值(特定在65上,35目前还没有这个选项),示例如下:SWITCH(config-if)# storm-control broadcast ?level set the storm levelpps packets per-second<cr>10)配置生成树命令(可以选用此配置用在和用户PC相连的21接入交换机上)Switch(config)# spanning-tree 在交换机上启用生成树Switch(config)# spanning-tree mode stp/mstp/rstp 这条命令可以设置生成树的状态,默认是mstp(有3种生成树,stp,mstp,rstp),一般可以不去改动Switch(config)# spanning-tree mst 0 priority 8192 设置生成树的优先级,默认为32768,优先级越低,成为根的可能性越大,当然了,如果全网开生成树的情况下,核心设备的优先级必须设置成最高,一般核心的priority设成4096,汇聚的设为8192,接入的次之或不改动默认设置Switch(config)# spanning-tree portfast bpdufilter default 在生成树速端口上启用对接入用户的bpdu包过滤的功能(这条是针对:此端口下面是接的PC用户)Switch(config)# interface fa 0/1 进入接口模式fa 0/1 口Switch(config-if) # spanning-tree portfast 在端口上启用带bpdu过滤的速端口设置Switch(config-if) # end 退出接口模式Switch#wri11)设置二层交换机缺省网关命令(21交换机的配置命令)Switch(config)# ip default-gateway 192.168.1.254给交换机配置网关为192.168.1.254Switch (config)# exit 退出全局配置模式12)配置802。

放心使用的交换机——Force10 E300交换机

放心使用的交换机——Force10 E300交换机

放心使用的交换机——Force10 E300交换机
佚名
【期刊名称】《网管员世界》
【年(卷),期】2006(000)004
【摘要】在遇到DoS攻击的时候,交换机的CPU往往会由于受到攻击利用率达到100%,从而影响了数据包的正常转发。

一旦出现这种情况,网管员要么拔掉所有的线缆,要么对设备进行重新启动,从而影响了设备的正常性能。

Force10的E300交换机在产品设计的时候考虑到了CPU的过载保护,在遇到上述情况的时候,它可以保证CPU的负载不会达到100%而导致网络瘫痪,
【总页数】1页(P26)
【正文语种】中文
【中图分类】TP368.3
【相关文献】
1.Belvedere Trading选用Force10交换机降低网络延时 [J], 魏斌
2.FORCE10公司推出C系列万兆以太网交换机 [J],
3.Force10网络公司推出C系列十吉比特以太网交换机 [J],
4.NYSE Euronext先进的数据中心部署Force10交换机产品 [J],
5.Force10推出绿色核心交换机 [J], 赵光磊
因版权原因,仅展示原文概要,查看原文内容请购买。

Force10配置

Force10配置

Force10网络设备串口连接和简单配置由于Force10的网络设备缺省状态下所有的端口都是Shutdown 的,因此需要通过串口登录到网络设备对其进行简单的配置。

串口访问:网络连接图如下图所示,由于现在的笔记本大都不支持串口,因此需要一根USB 转串口的转接线,这个转接线Force10是不提供的;另外还需要一个RJ45到DB9的转换头,这个转换头Force10是提供的; 另外还有就是网络设备RJ45串口到转换头的RJ45线。

对于S 系列产品(S2410除外),该RJ45线是普通的RJ45线缆,由于是普通的线缆,所以Force10不为S 系列产品提供独立的RJ45线; 对于S2410,C 系列和E 系列,该RJ45线是反线,Force10的C 系列,E 系列和S2410会配置这样的RJ45线缆,安装时请仔细检查。

电脑超级终端设置如下:• 9600 baud rate• no parity笔记本RJ45到DB9转换头Force10网络设备USB 转串口线RJ45线• 8 data bits• 1 stop bit• No flow control简单配置:在高性能计算的网络应用中,最典型也最简单的配置就是划分VLAN,并将相应的端口加入VLAN中。

只需要经过下列两个步骤就可以完成这些操作:1. 将物理端口no shutdown, 并设置为二层交换端口switchport2. 创建VLAN端口,并将物理端口加入VLAN,根据需要配置VLAN端口的IP地址举例: 将S50的所有48个口放入VLAN 10enableconfigureinterface range gi0/1 – 48 // 用range可以对48个口同时操作,S50的端口号是从1开始的; 中划线(-)的前后都有空格no shutdown // 激活端口switchport //设置为交换端口exitinterface vlan 10 //创建VLAN 10untagged gi0/1-48 //将48个端口加入VLAN10,中划线(-)前后没有空格ip address 10.10.10.1/24 //设置VLAN 10的IP地址no shutdown举例: 将C300的板卡1 和板卡3的96个口加入VLAN 100enableconfigureinterface range gi1/0 – 47switchportno shutdownexitinterface range gi3/0 – 47switchportno shutdownexitinterface vlan 100untagged gi 1/0-47untagged gi3/0-47ip address 192.168.100.1/24no shutdown设置用户名密码:在配置模式下:username xxxx password yyyy 打开telnet server功能在配置模式下:ip telnet server enable。

  1. 1、下载文档前请自行甄别文档内容的完整性,平台不提供额外的编辑、内容补充、找答案等附加服务。
  2. 2、"仅部分预览"的文档,不可在线预览部分如存在完整性等问题,可反馈申请退款(可完整预览的文档不适用该条件!)。
  3. 3、如文档侵犯您的权益,请联系客服反馈,我们会尽快为您处理(人工客服工作时间:9:00-18:30)。

Force10 S25N/S50N交换机配置手册目录前言........................................................... 错误!未定义书签。

1. FORCE10 S系列交换机登陆初始配置 ............................. 错误!未定义书签。

使用CONSOLE口登陆方式.......................................... 错误!未定义书签。

用以太网线使用TELNET方式....................................... 错误!未定义书签。

2.创建VLAN ..................................................... 错误!未定义书签。

创建一个基于端口的V LAN......................................... 错误!未定义书签。

3.配置TRUNK .................................................... 错误!未定义书签。

创建一个TRUNK.................................................. 错误!未定义书签。

4.开启端口FLOW-CONTROL 、SPANNING-TREE、和EDGED-PORT ........... 错误!未定义书签。

前言1. Force10 S系列交换机登陆初始配置使用console口登陆方式第一步:如图所示,建立本地配置环境。

S25的Console口是标准的RJ45口,所以需要用标准网线连接一个RJ45/串口转换器(在交换机的包装箱里带有),网口连接交换机的Console口,串口与PC机(或终端)的串口连接。

通过Console口搭建本地配置环境第二步:在PC机上运行终端仿真程序(如Windows 的Terminal或Windows 9X/Windows 2000/Windows XP的超级终端等,以下配置以Windows XP为例),选择与交换机相连的串口,设置终端通信参数:传输速率为9600bit/s、8位数据位、1位停止位、无校验和无流控,如图所示。

新建连接连接端口设置端口通信参数设置第三步:点击确定,进入超级终端,键入回车,之后将出现命令行提示符(如force10>),如图所示。

以太网交换机配置界面第四步:键入命令,配置以太网交换机或查看以太网交换机运行状态。

需要帮助可以随时键入“?”,具体的配置命令请参考本手册中相关部分的内容。

第五步:基础配置模式和命令:FTOS,也即Force10操作系统,是运行在Force10交换机/路由器系列产品上的操作系统。

FTOS基于NetBSD,类似于Unix。

硬件抽象层(HAL)用于使FTOS应用可在整个产品系列中移植,而无须为每个平台重写该应用软件。

所以对Forec10的所有系列交换机来说,调试配置基本类似,略有不同。

FTOS CLI有三种模式:Exec(默认模式,权限受限,主要用来查询系统信息);Exec Privileged(特权模式,可以查看配置信息、管理配置文件、进行诊断、启动或关闭debug 等);Configuration(配置模式,可以对系统进行配置操作)通过Console口进行FTOS后,默认进入Exec模式,显示如下:force 10>输入enable,此时提示输入enable密码,如果为新机,默认密码为空,如果为已配置过的switch,请输入enable密码(下文会有设置enable密码的方法)。

然后系统会进入特权模式:force10#输入configure,FTOS会进入配置模式:force10(conf)#注意不同模式下,提示符的变化!默认用户名:force10 默认密码为空;默认enable密码为空退出配置模式命令为:exit,退出特权模式命令:disable设定或修改enable密码的命令:例如设定enable密码为force10时force10(conf)#enable password force10注:enable密码对所有的登录用户名都是一样的。

创建新的用户名和密码的命令:例如创建用户名为dayang,密码为dayang时,force10(conf)#username dayang password dayang切换当前登录的用户名的命令:例如由force10切换至dayang的用户名force10(conf)#hostname dayangdayang(conf)#在所有的模式中,可通过Tab键来补全命令,?来查询帮助。

在配置模式中,所有的配置命令都可以通过在原有命令之前加no来取消。

例如:force10(conf)#interface vlan 100创建VLAN100,并进入VLAN100的配置模式force10(conf)#no interface vlan 100删除VLAN100用以太网线使用telnet方式由于Force10 S系列交换机没有单独的管理网口,而且默认的VLAN ID(VLAN 1)不能设置IP地址,因此如果要想以Telnet方式管理交换机,必须在交换机新建任意1个VLAN,将此VLAN配置一个IP地址,之后就可以通过属于此VLAN的客户端机器,通过telnet此地址进入FTOS,对所有的交换机端口进行访问和配置。

VLAN的创建和IP地址设置方法请参加章节:创建VLAN。

2.创建Vlan创建一个基于端口的Vlan注意:Vlan ID,Force10交换机的ID范围是0-4095。

由于0和4095不能使用,所以VLAN ID的取值范围一般为1-4094,但Vlan ID 1默认是交换机缺省Vlan,所以当真正需要配置Vlan时,ID号请从2开始。

本例中,创建VLAN100,并将千兆端口GigabitEthernet 0/1到0/24和万兆端口0/25到26加入到指定VLAN中。

要加入VLAN的端口,必须处于二层模式(switchport),如果之前处于三层模式(no switchport),必须先将其改成二层模式,其方法如下例所示:force10(conf)#interface range gi 0/1 – 24进入千兆端口1到12号的多端口配置模式,请注意此命令,可进入指定连续范围内的端口,另外注意,- 的前后都有空格。

force10(conf-if-range-gi-0/1-24)# switchport设为switchport状态force10(conf-if-range-gi-0/1-24)#exit退出端口配置模式force10(conf)#interface vlan 100创建VLAN100,并进入VLAN100的配置模式force10(conf-if-vl-100)#untagged gigabitethernet 0/1-24将千兆端口1-24加入VLAN100force10(conf-if-vl-100)#untagged tengigabitethernet 0/25-26将万兆端口25-26加入VLAN100force10(conf-if-vl-100)#no shutdown将VLAN100设为启动状态force10(conf-if-vl-100)#ip address 设定VLAN100的IP地址force10(conf-if-vl-100)#show config!interface Vlan 100ip address untagged GigabitEthernet 0/1-24untagged TenGigabitEthernet 0/25-26no shutdown可通过此命令显示VLAN100的配置信息force10(conf-if-vl-100)#关于VLAN untagged和tagged,详细说明可以去查阅书籍或网络,在此用两句话做概要说明:untagged的端口主要用来连接外部的服务器、工作站或者存储的网络端口;tagged 的端口主要是用来做交换机内部互联的网络端口。

多个非连续端口只需分多次分别输入端口号即可。

port GigabitEthernet 0/X,这个X 代表需要加入Vlan的端口号,Force10交换机端口号从1开始排列。

3.配置trunk创建一个trunkForce10交换机的端口汇聚可以通过port-channel来实现。

组网需求:以太网交换机Switch A使用4个端口(GigabitEthernet0/9~GigabitEthernet0/12)汇聚接入以太网交换机Switch B,实现流量在各成员端口中的负载分担。

注意:以下只列出对Switch A的配置,对Switch B也需要作相同的配置,才能实现端口汇聚。

配置之前,首先需要把要加入Portchannel的成员端口设为三层模式。

force10(conf)#interface range gi 0/9 – 12进入千兆端口9到12号的多端口配置模式force10(conf-if-range-gi-0/9-12)#no switchport设为非switchport状态force10(conf-if-range-gi-0/9-12)#exit退出端口配置模式force10(conf)#interface port-channel 66创建并进入port-channel 66force10(conf-if-po-66)#no shutdown将port-channel设为启动状态force10(conf-if-po-66)#channel-member gi 0/9-12将gigabitethernet端口9到12共4个端口加入port-channel 66force10(conf-if-po-66)#以上是以9至12端口做的配置举例,具体情况请根据现场决定4.开启端口Flow-control 、Spanning-Tree、和Edged-port说明:Force10的spanning-tree和flow-control默认都是关闭的。

portfast是思科的名称,force10叫edged-port,中文名称是边缘端口,这里配置开启edged-port相当于开启思科交换机中的portfast功能以下是交换机开启rapid spanning-tree的命令force10(conf)#protocol spanning-tree rstp进入rstp配置模式force10(conf-rstp)#no disable开启rstpforce10(conf-rstp)#exit以下为指定端口的设置方式:以配置端口1为举例force10(conf)#interface gigabitethernet 0/1进入端口1force10(conf-if-gi-0/1)#spanning-tree rstp edge-port将端口1设为edge portforce10(conf-if-gi-0/1)#flowcontrol rx on tx on开启flowcontrolforce10(conf-if-gi-0/1)#exit注:可以通过interface range命令进入批量端口的配置模式,进行批量设置。

相关文档
最新文档