NOTE: A NOTE indicates important information that helps you make better use of your computer.
CAUTION: A CAUTION indicates potential damage to hardware or loss of data if instruction are not followed.
WARNING: A WARNING indicates a potential for property damage, personal injury, or death.
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 Vostro™ are trademarks of Dell Inc. Intel
Core™ and Celeron
Opteron™, AMD Phenom™, and AMD Sempron™ are trademarks of Advanced Micro Devices, Inc. Microsoft
®
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
countries. Novell
registered trademark of Oracle Corporation and/or its affiliates. Citrix
or trademarks of Citrix Systems, Inc. in the United States and/or other countries. VMware
®
are registered trademarks of Intel Corporation in the U.S. and other countries. AMD® is a registered trademark and AMD
®
®
is a registered trademark and SUSE ™ is a trademark of Novell Inc. in the United States and other countries. Oracle® is a
and Enterprise Linux® are registered trademarks of Red Hat, Inc. in the United States and/or other
®
, Xen®, XenServer® and XenMotion® are either registered trademarks
®
, Virtual SMP®, vMotion®, vCenter®, and vSphere®
®
, Pentium®, Xeon®,
®
, Windows®, Windows
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.
November 2011 P/N —
New Features
SFTOS 2.5.3 improves SFTOS internals only, with no new features.
SFTOS 2.5.2 adds:
•A substantial support interface that is not accessible through the standard CLI modes and is not
publicly documented
•Support for new S-Series platforms, including the S50N, S50N-DC, and S25P-DC
Other Changes to the Document
Changes in this edition include:
•The major change in this edition is that the example configuration sequence for VLAN Stacking is
corrected. See Configuring a VLAN Tunnel (DVLAN or VLAN-Stack) on page 229.
Changes to this book in the previous edition included:
•The SFTOS Web User Interface (Web UI) chapter is removed, because changes to SFTOS 2.5.2.1 were
not promulgated to the Web UI, which made some parts of the Web UI unreliable or non-functional.
•The ACL chapter now states that both MAC and IP ACLs can be applied to the same interface.
•Both the VLAN and LAG chapters state more explicitly that the Default VLAN, VLAN 1, cannot be
changed, and will not allow a LAG or tagged port as a member of it.
•Related Dell Force10 Documents and Additional Information on page 16
•Contact Information on page 17
•Documentation Feedback on page 17
•The iSupport Website on page 17
•Objectives
•Audience
•Conventions
•Related Dell Force10 Documents and Additional Information
1
Objectives
This document provides configuration instructions and examples for the following S-Series switches:
•S50
•S50V
•S50N, S50N-DC
•S25P, S25P-DC
It includes information on the protocols and features found in SFTOS
protocols is included to describe the capabilities of SFTOS.
For more complete information on protocols, refer to other documentation and IETF RFCs.
Note: For S2410 documentation, see the S2410 Documentation CD-ROM.
™
. Background on networking
About this Guide | 15
Audience
This document is intended for system administrators who are responsible for configuring or maintaining
networks. This guide assumes you are knowledgeable in Layer 2 and Layer 3 networking technologies.
Introduction to the Guide
This guide provides examples of the use of E-Series switches in a typical network. It describes the use and
advantages of specific functions provided by the E-Series, and includes instructions on how to configure
those functions using the Command Line Interface (CLI).
www.dell.com | support.dell.com
Some E-Series switches operate purely as a Layer 2 switch, some also as a Layer 3 router or a combination
switch/router. The switch also includes support for network management and Quality of Service functions
such as Access Control Lists and Differentiated Services. Which functions you choose to activate will
depend on the size and complexity of your network; this document provides detailed information on some
of the most-used functions. For details on SFTOS features, see SFTOS Features on page 19.
Note: Note that, while BGP and bandwidth allocation are not supported in this release, they may
appear in the command output examples in this document.
Conventions
This document uses the following conventions to describe command syntax:
ConventionDescription
keywordKeywords are in bold and should be entered in the CLI as listed.
parameter
{X}Keywords and parameters within braces must be entered in the CLI.
[X]Keywords and parameters within brackets are optional.
x | y Keywords and parameters separated by bar require you to choose one.
Parameters are in italics and require a variable—sometimes a number, sometimes a word,
sometimes either—to be entered in the CLI.
Shown between less-than and greater-than signs in the CLI help: <parameter>
Related Dell Force10 Documents and Additional Information
The following documents provide information on using Dell Force10 S-Series switches and SFTOS
software. All of the documents are available on the Documents tab of iSupport (the Dell Force10 support
website — http://www.force10networks.com/support:
•SFTOS Command Reference
16|About this Guide
•SFTOS Configuration Guide
•SFTOS and S-Series Release Notes
•S50 Quick Reference (also included as a printed booklet with the system)
•Hardware installation guides
•MIBs files
•S-Series Tech Tips and FAQ
Except for the Tech Tips and FAQ documents, all of the documents listed above are also on the S-Series
CD-ROM. Training slides are also on the S-Series CD-ROM. Currently, access to user documentation on
iSupport (see The iSupport Website on page 17) is available without a customer account. However, in the
future, if you need to request an account for access, you can do so through that website.
Contact Information
For technical support, see The iSupport Website on page 17. For other questions, contact Dell Force10
using the following address:
Dell Force10, Inc.
350 Holger Way
San Jose, CA 95134
USA
Documentation Feedback
If appropriate, please include the following information with your comments:
•Document name
•Document part number
•Page number
•Software release version
Technical Support
The iSupport Website
Dell Force10 iSupport provides a range of support programs to assist you with effectively using Dell
Force10 equipment and mitigating the impact of network outages. Through iSupport you can obtain
technical information regarding Dell Force10 products, access to software upgrades and patches, and open
and manage your Technical Assistance Center (TAC) cases. Dell Force10 iSupport provides integrated,
secure access to these services.
About this Guide | 17
Accessing iSupport Services
The URL for iSupport is www.force10networks.com/support/. To access iSupport services you must have
a userid and password. If you do not have one, you can request one at the website:
1. On the Dell Force10 iSupport page, click the Account Request link.
2. Fill out the User Account Request form and click Send. You will receive your userid and password by
email.
3. To access iSupport services, click the Log in link, and enter your userid and password.
Contacting the Technical Assistance Center
www.dell.com | support.dell.com
How to Contact Dell Force10
TAC
Information to Submit When
Opening a Support Case
Managing Your CaseLog in to iSupport, and select the Service Request tab to view all open cases and RMAs.
Downloading Software
Updates
Technical DocumentationLog in to iSupport, and select the Documents tab. This page can be accessed without
Log in to iSupport at www.force10networks.com/support/, and select the Service Request
tab.
•Your name, company name, phone number, and email address
•Preferred method of contact
•Model number
•Software version number
•Symptom description
•Screen shots illustrating the symptom, including any error messages
•Serial number, if requesting an RMA
Log in to iSupport, and select the Software Center tab.
logging in via the Documentation link on the iSupport page.
Web: www.force10networks.com/support/
Telephone:
US and Canada: 866.965.5800
International: 408.965.5800
For more on using the iSupport website and accessing services, see the Dell Force10 Service and Support
Guide.
18|About this Guide
SFTOS Features
This chapter contains these major sections:
•Overview of SFTOS Features on page 19
•Layer 2 Package Feature Details on page 20
•Layer 3 Package Feature Details on page 22
•Notable Differences between S-Series and E-Series on page 24
•Port Naming Convention on page 26
The SFTOS software is available in two packages—the “Layer 2 Package” (“Switching”) and the “Layer 3
Package” (“Routing”). The Layer 2 Package consists of the core software that comes installed on every
S-Series switch (with the exception of the Stacking module, which is not included on the S2410), while the
Layer 3 Package includes both the core software and software that supports Layer 3 of the OSI 7-Layer
Model. The Layer 3 Package is only available for some S-Series models.
2
Overview of SFTOS Features
The functions supported by SFTOS software include:
•Access control lists, used to control access to specified resources (see
(DiffServ) on page 177)
•Differentiated Services, which you can use to define traffic classes and how they will be treated,
including traffic acceptance, transmission and bandwidth guarantees. See
Services (DiffServ) on page 177.
•Layer 2 Switching:
•Bridging support (the default) for IEEE 802.1D — Spanning Tree plus IEEE 802.1w — Rapid
Reconfiguration and IEEE 802.1s — Multiple Spanning Tree (see
•Virtual LAN (VLAN) operation conforming to IEEE 802.1Q, including Generic Attribute
Registration Protocol (GARP), GARP Multicast Registration Protocol (GMRP) and GARP VLAN
Registration Protocol (GVRP) (see VLANs on page 207
•Support for extensions to the Ethernet protocol:
— VLAN tagging, required for VLAN support (formerly IEEE 802.3ac, now included in
IEEE 802.3-2002)
— Link Aggregation, which you may choose to implement to improve bandwidth and
reliability for critical connections (formerly IEEE 802.3ad) (see
Aggregation) (see also Chapter 17, Layer 3 Routing, for use of LAGs in Layer 3)
Using Differentiated Services
Using Differentiated
Chapter 10, Spanning Tree)
)
Chapter 11, Link
SFTOS Features | 19
— Flow Control at the MAC layer: you may configure the switch or a port to temporarily
halt traffic when necessary to prevent overload (formerly IEEE 802.3x)
•Additional functions you can use to manage the network including IGMP Snooping (see
Chapter 15, IGMP Snooping), Port Mirroring (see Chapter 16, Port Mirroring), and Broadcast
Storm Recovery.
•Layer 3 Routing (see
•Base routing protocols, including support for the Address Resolution Protocol (ARP), IP Mapping,
the
Internet Control Message Protocol (ICMP) and Classless Inter-Domain Routing
(CIDR)
•Support for protocols used by routers to exchange network topology information:
— Routing Information Protocol (RIP) versions 1 and 2, recommended for use in small
to medium sized networks
www.dell.com | support.dell.com
•Support for the Virtual Router Redundancy Protocol (VRRP) used to improve the reliability of
network connections
•Support for the MD5 Message-Digest Algorithm defined in RFC 1321 used for digital signature
applications
•Support for the use of Dynamic Host Configuration Protocol (DHCP) to assign IP addresses,
including the Relay Agent Information option defined in RFC 3046
•VLAN Routing (see
processed by the Layer 3 routing function.
— Open Shortest Path First (OSPF) version 2, used in larger, more complex networks
Chapter 17, Layer 3 Routing)
VLAN Routing on page 262): Allows traffic received on a VLAN port to be
Layer 2 Package Feature Details
The core Layer 2 Package software provides support for the following features:
Basic Routing and Switching Support
•BootP (RFC 951, RFC 1542)
•BootP/DHCP Relay and Server (RFC 2131)
•Host Requirements (RFC 1122)
•UDP (RFC 768)
•IP (RFC 791)
•ICMP (RFC 792)
•TCP (RFC 793)
•STP (Spanning Tree Protocol) (IEEE 802.1d)
•Rapid Spanning Tree (IEEE 802.1w)
•MSTP (IEEE 802.1s)
•10 GigE (IEEE 802.3ae)
•1000 Base-T (IEEE 802.3ab)
•Flow Control (IEEE 802.3x)
•IEEE 802.3ad
20|SFTOS Features
•16k MAC Address Table
•Jumbo Frame Support
QoS
•802.1p Priority Marking
•ACL Entries (L2 + L3)
•Bandwidth-based Rate Limiting
•Priority Queues
•Layer 2 Classification
•Layer 3 DSCP
•Wirespeed ACLs (L2/L3/L4)
VLAN
•IEEE 802.1q Support
•Frame Extensions (IEEE 802.3ac)
•GVRP, GARP, GMRP
•Port-based VLANs
•Protocol-based VLANs
•Supported Number of VLANs
Multicast Protocols
•IGMP Snooping
•Layer 2 Multicast Forwarding
Security and Packet Control Features
•Access Profiles on Routing Protocols
•DOS Protection
•IEEE 802.1x
•Ingress Rate Limiting
•Login Access Control
•MAC-based Port Security
•Port Mirroring
•RADIUS
•SSH2 Server Support
Management
•External Redundant Power System
SFTOS Features | 21
•HTML-based Management
•HTTPS/SSL
•RMON Groups
•SNMP v1/v2c
•SNTP Support
•SSHv2
•Syslog
•Telnet (RFC 854)
•TFTP (RFC 783)
www.dell.com | support.dell.com
Stacking
•Stacking Multiple Units
•LAG across Units in a Stack
•Hot Insertion and Removal of Units in a Stack
•Auto Master Election
•Auto Configuration
Layer 3 Package Feature Details
The “Layer 3 Package” (“Routing image”) version (optional for certain S-Series models) of SFTOS
includes all of the features listed above, along with the following features.
Extended Routing and Switching Support
•4k IPv4 Routing Table Entry
•ARP (RFC 826)
•CIDR (RFC 1519)
•IPv4 (RFC 1812)
•IPv4 Router Discovery (RFC 1256)
•Proxy ARP (RFC 1027)
•VRRP (RFC 2338)
Routing Protocol Support
•RIPv1/v2
•OSPF (RFC 2328, 1587, 1765, 2370)
•Static Routes
22|SFTOS Features
Multicast Protocols
•IGMP v1/v2 (RFC 1112, 2236)
•PIM-SM-edge
•DVMRP
•PIM-DM
Management
•ECMP
SFTOS Features | 23
Load Balancing
•LAG Load Balancing: For IPv4 packets, LAG load balancing is provided automatically by a hash
algorithm that is based on an XOR (eXclusive OR) of the 3 LSBs (Least Significant Bits) of the source
and destination IP addresses.
For all other packet types, the 3 LSBs of the source and destination MAC addresses are used. Broadcast,
unknown unicast, and Layer 2 multicast packets are sent over a single port in the LAG. MAC addresses must
be learned first in order for load balancing to take place.
ECMP Load Balancing: ECMP (Equal Cost Multi-path Routing) is supported for OSPF, not for RIP.
•
2048 IP routes of the 3072 routes that are supported by SFTOS can be ECMP routes. Six ECMP paths
are supported.
www.dell.com | support.dell.com
ECMP load balancing is like LAG load balancing in that it is provided automatically by a hash algorithm that
is based on an XOR (eXclusive OR) of the 3 LSBs (Least Significant Bits) of the source and destination IP
addresses.
Use the maximum-paths command to set the number of paths. For details, see the maximum-paths command in
Chapter 20, “OSPF Commands”, of the SFTOS Command Reference.
Notable Differences between S-Series and E-Series
This section describes the major differences in how command usage on the S-Series differs from the
E-Series. Users familiar with the E-Series CLI will notice enough similarities in the CLI environment on
the S-Series that they can quickly learn the variations in syntax and usage.
The primary goal of SFTOS Release 2.3 (and associated dot releases) was to make SFTOS more like
FTOS. Of course, there are still differences because FTOS requires more commands, usually with more
detailed options than in SFTOS, to support the more complex E-Series switches.
Note: As you can see in some command descriptions, below, the major difference between
SFTOS and FTOS is that in commands that contain a port reference, FTOS expresses the location
as slot/port, while SFTOS uses unit/slot/port. For physical identifiers, unit is the stack member
number in an S50 stack. For details, see Port Naming Convention on page 26.
•The
•CLI command modes: SFTOS Release 2.3 modifies the command mode tree of SFTOS to be more
•Creating a static route: The SFTOS command
24|SFTOS Features
aaa authentication command: This FTOS command is available in SFTOS as authentication.
like FTOS, so that their modes are basically equivalent at the base, differing toward the leaves.
next-hop router, while
ip route supports only IP addresses for setting the
ip route in the FTOS also supports physical interfaces. In other words:
— In SFTOS Layer 3, you can only put an IP address as the source and destination:
ip route source-ip-addressmaskdestination-ip-address
— In FTOS, you can have a physical interface as a destination as well as an IP address:
ip route source-ip-addressmask {destination interface | ip address}
•Displaying the MAC address table: Both FTOS and SFTOS have the show mac-address-table
command, but the SFTOS command provided different results than the FTOS command before
SFTOS Release 2.3. The SFTOS syntax still contains the unit/slot/port form cited above, for example,
show mac-addr-table interface 1/0/4.
•Displaying port information: FTOS and SFTOS have different sets of the show interface and show
interfaces commands. SFTOS also has a similar show port command for displaying whether a port is
up or not, as shown in Figure 2-1:
Figure 2-1. Using the show port Command
(Force10 S50) #show port 1/0/2
Admin Physical Physical Link Link LACP
Intf Type Mode Mode Status Status Trap Mode
------ ------ ------- ---------- ---------- ------ ------- ------1/0/2 Enable Auto Down Enable Enable
(Force10 S50) #
•Displaying system information: The FTOS command
show linecard is similar to show version in
SFTOS, which shows basic information, including the running software version and up time. Other
similar commands in SFTOS are
show hardware and show sysinfo, and show tech-support provides
the results of a group of those similar commands.
•The
terminal length command: This FTOS command (often shortened to “term len”) was not available
in SFTOS before SFTOS Release 2.3.
•The
service timestamps command: This FTOS command is not available in SFTOS. SFTOS sets
timestamps automatically.
•OSPF area ID: In SFTOS, OSPF only accepts the IP address format for the area ID, not the number
within a range.
•File management:
Table 2-1. Switch File Management
FTOS references system file locations as: SFTOS references system file locations as:
flash:// nvram:
slot0://system:
•Management address: SFTOS Release 2.3 modifies the creation of a management address to be more
like FTOS, but there are still some differences.
•Setting the size of the logging buffer: The FTOS command
logging buffered has a parameter that
enables you to set the size of the buffer, while SFTOS does not. Both FTOS and SFTOS invoke debug
logging with the number 7 as the severity level parameter. For example, the
logging buffered 7.
SFTOS command is
SFTOS Features | 25
•Software naming convention: E-Series software uses this naming convention: FTOS-EF-x.x.x.x
Through version 2.3.1.5, the S-Series used a different format that ends with an “.opr” extension.
Starting with SFTOS 2.4.1, SFTOS software image file names have a new naming format that is more
descriptive and is consistent with the E-Series software naming convention:
"SFTOS-<platform>-<version>-<switching | routing>.bin"
for example: SFTOS-S2410-2.4.1.1-switching.bin.
Port Naming Convention
SFTOS supports stacking (one virtual switch made by connecting several switches) with the port naming
convention “
www.dell.com | support.dell.com
in the stack, slot 0, port 11. If the port were in unit 2 of the stack, the command should be
0/11.
In more detail, the physical entities that define this convention are as follows:
•Unit—The switch ID in a stack of switches (begins with the number 1, so the ports of a standalone
switch are numbered
•Slot—slot numbers for modular entities within the switch. Although S-Series switches have optional
port modules that might qualify for a slot number, S-Series switches currently always list the slot
number as 0 (listing all physical ports as
channel.
•Port—physical interface (port numbers are sequential starting at 1).
unit/slot/port<lucindaRgOb>”. For example, in show interface 1/0/11, 1/0/11 represents unit 1
1/slot/port).
show interface 2/
unit/0/port) unless representing a logical entity, such as a port
Logical interface identifiers are automatically generated by SFTOS. They also use the unit/slot/port
convention, but:
•Logical unit numbers are always 0.
•Logical slot numbers are sequential and start with a 1.
•Logical interface numbers (in the third position) are also sequential starting at 1 for each slot.
VLAN routing interfaces and port channels (LAGs) are logical entities. Logical interface identifiers are
defined by the system upon creation.
26|SFTOS Features
Getting Started
This chapter summarizes the following basic tasks:
•Connecting to the Console Port on page 29
•Command Line Interface (CLI) Overview on page 31
•Checking Status on page 32
— Displaying Statistics on page 36
— Viewing the Software Version and Switch Numbers on page 32
— Showing Network Settings on page 34
— Displaying Supported Features and System Up-time on page 34
— Verifying Details about the Switch on page 32
•User Management on page 36
— Creating a User and Password on page 36
— Showing and Removing Created Users on page 37
— Setting SNMP Read/Write Access on page 37
— Setting the Enable Password on page 38
•Enabling Interfaces on page 38
— Enabling Ports on page 38
— Setting the Management IP Address on page 39
— Enabling Telnet to the Switch on page 39
— Configuring an Interface with an IP Address on page 40
— Setting up SNMP Management on page 41
•Creating VLANS on page 41
•Managing Configuration and Software Files on page 43
— Downloading and Uploading Files on page 44
— Downloading a Software Image on page 45
— Installing System Software on page 50
— Managing the Configuration on page 56
— Saving the Startup Configuration to the Network on page 57
— Clearing the Running Configuration on page 57
— Configuring from the Network on page 58
— Restoring the System to the Factory Default Configuration on page 58
— Resetting the Pre-configured System on page 59
— Using Configuration Scripts on page 60
— Creating a Configuration Script on page 60
3
Getting Started | 27
Setting up a Management Connection to the Switch
You have a choice of methods to manage the switch. You can access the SFTOS command line interface
(CLI) through either the console port on the switch or through an out-of-band method such as Telnet or
SSH. To use any method other than the console port (VT100 emulation), you must first configure a
management IP address on the switch. This chapter includes the procedures that connect you to the console
and to set up a management IP address:
•Console connection (VT100 interface): See Connecting to the Console Port on page 29.
•Management IP address: See Setting the Management IP Address on page 39. See also Showing
Network Settings on page 34.
www.dell.com | support.dell.com
After setting up the management IP address, you can use one of the following connection methods:
•Simple Network Management Protocol (SNMP): For details on setting up SNMP, see Setting
SNMP Read/Write Access on page 37 and Setting up SNMP Management on page 71.
Note: The Dell Force10 Management System (FTMS) is a graphical network management
software product that provides a global view of your complete Dell Force10 network. FTMS
includes Node Manager, which not only provides GUI-based device management, it also includes
the ability to execute CLI commands, either individually from Node Manager or by having Node
Manager open a Telnet window to the device.
•Telnet: See Enabling Telnet to the Switch on page 39. To use SSH to enable secure access over Telnet,
see Enabling SSH on page 142.
Note: You can also use a configuration script to set up the switch. The maximum number of
configuration file command lines is 2000. See Using Configuration Scripts on page 60.
28|Getting Started
Connecting to the Console Port
fn00162s50
To access the console port, follow the procedure below:
StepTask
1Caution: Install a straight-through RJ-45 copper cable (for example, an Ethernet cable) into the console
port. This is different from many other implementations that require a crossover (rollover) cable. If connecting
to a terminal server and using an Ethernet crossover cable, daisychain another crossover cable to effectively get
a straight-through cable connection. Many console terminal servers use octopus cables that are crossover
cables. As above, connect an additional crossover cable.
2
Connect the RJ-45/DB-9 adapter that is shipped with the switch to the RJ-45 cable.
Note: The console port pinout:
Connect the adapter to a laptop.
Once a connection is established, ensure the following terminal settings (default settings) at both ends: 9600
baud rate, no parity, 8 data bits, 1 stop bit, no flow control (console port only).
If you want to change the settings (such as if you want to download software at a higher speed), you must
change the serial configuration on both the switch and computer. See the command options in the following
step. For more on changing settings, see the hardware guide or the Quick Reference.
Getting Started | 29
StepTask (continued)
5
Enter Line Config mode by logging in, entering Privileged Exec mode (enable command), Global Config
mode (config command), then lineconfig. In Line Config mode, use the serial timeout command to set the
console inactivity timeout (0 for no timeout; up to 160 minutes):
Figure 3-2. Using the Line Config Mode and the serial timeout Command
User:admin
Password:
Force10 >enable
Password:
Force10 #configure
Force10 (Config)#lineconfig
www.dell.com | support.dell.com
Force10 (Line)#?
exit To exit from the mode.
serial Configure EIA-232 parameters and inactivity timeout.
session-limit Configure the maximum number of outbound telnet
sessions allowed.
session-timeout Configure the outbound telnet login inactivity
timeout.
transport Displays the protocol list to use for outgoing
connections.
Force10 (Line)#serial ?
baudrate Set the serial baudrate.
timeout Configure the serial port login inactivity timeout.
Force10 (Line)#serial timeout ?
<0-160> Enter time in minutes.