migrating and understanding the differences between the ...€¦ · december 9, 2008 update...

December 9, 2008 Update

Migrating and Understanding the Differences between SFTOS and FTOS on the S-Series 1

This document is designed to help network administrators familiar with managing S-Series systems running SFTOS to transition to managing S-Series systems running FTOS 7.7.1.0 or later, with software conversion procedures and a comparison of FTOS functionality and configuration procedures to SFTOS, with an emphasis on key differences. This document is not intended as a detailed configuration guide. This document contains the following major sections:

• Feature Comparison between FTOS and SFTOS on page 3• System Management in FTOS and SFTOS on page 9

• Managing a Stack of S-Series Switches on page 12• Managing the Configuration on page 13

• Installing Software on S-Series on page 14• Converting from SFTOS to FTOS 7.7.1.1 on page 16• Converting from SFTOS to FTOS on Stacked Units on page 19• Upgrading S-Series from FTOS 7.6.1.0 to FTOS 7.7.1.1 on page 19• Downgrading from FTOS 7.7.1.1 to FTOS 7.6.1.0 on page 22• Upgrading from FTOS 7.7.1.0 to FTOS 7.7.1.1 on page 24• Upgrading to FTOS 7.8.1.0 on page 26• Upgrading the S-Series Boot Code on page 28• Converting from FTOS 7.7.1 to SFTOS on page 30• Converting from FTOS 7.6.1.0 to SFTOS on page 33

• Basic Software Configuration on page 35

While SFTOS and FTOS have very similar Command Line Interfaces (CLIs), the differences are significant enough that this document does not attempt to show how to edit an S-Series configuration done in SFTOS to make it work in FTOS. You are not advised to attempt to do so.

For detailed command and configuration explanations, see the FTOS Command Reference for the S-Series and the FTOS Configuration Guide for the S-Series.

FTOS Migration BenefitsMigrating to FTOS 7.7.1.0 or later from SFTOS provides significant technology and operational management benefits, including:

• Standardizing on a single operating system simplifies operations for networks with E-Series, C-Series, and/or S-Series systems.

• A modern kernel architecture, featuring process modularization and memory protection, with NetBSD as the underlying FTOS operating system.

• Enhanced operational manageability with environmental monitoring and alarm reporting

Migrating and Understanding the Differences between the SFTOS and FTOS Operating Systems for the Force10 Networks S-Series

2

• Debug commands• Industry-standard CLI• Layer 3 port channels• DHCP relay multiple servers• OSPF passive interface• ACL enhancements

For a detailed feature comparison, see Feature Comparison between FTOS and SFTOS on page 3.

Switch Architecture Represented in FTOS CommandsThe S-Series platform has a much different architecture than the C-Series and E-Series. As such, some architectural concepts represented in FTOS commands designed for C-Series and E-Series do not pertain to the S-Series. For example, command parameters for modular fan trays, line cards, RPMs (Route Processor Modules), and SFMs (Switch Fabric Modules) are generally not relevant to the S-Series.

For example, the reset command for the C-Series and E-Series is:

reset {linecard number [hard | power-cycle] | rpm number [hard | power-cycle ] | sfm slot | standby}

Most of those keywords are not relevant to the S-Series, such as linecard, rpm, and sfm, but the command is otherwise useful for the S-Series, so the FTOS Command Reference presents two commands — one with those keywords for the C-Series and E-Series— the other, without those keywords, for the S-Series:

reset stack-unit 0-7

As a standard, when those commands are adapted for the S-Series, a new parameter is used — stack-unit unit-ID — such as shown above. The unit-ID parameter is for designating a particular S-Series stack member.

Port-PipeThe port-pipe concept, familiar to C-Series and E-Series users, is applied by FTOS to the Forwarding Processor (FP) in the S-Series. The FP directs traffic between ports:

• The S25N, S25P, and S25V models have one FP, and therefore, one port-pipe.• The S50N and S50V models have two FPs, reflected in FTOS commands as two port-pipes.

• port-pipe 0 controls ports 1–24 • port-pipe 1 controls ports 25–48, plus each port-pipe controls two of the potential 10Gig XFPs in the

back of the switch.

This information can help you both to understand show command output that contains port-pipe information, and to allocate ports so that traffic is more balanced across the FPs.

For details on FTOS features available for the S-Series, see the feature introductions in each chapter, and the individual command statements. For more, see the FTOS on S-Series Release Notes and the FTOS Configuration Guide.


Feature Comparison between FTOS and SFTOSThis section is intended to be an overview comparison of features of SFTOS 2.5 and FTOS on the S-Series, which network administrators who are more familiar with SFTOS than FTOS can use as an introduction to configuring S-Series systems in FTOS.

Table 1 compares hardware support on the S-Series by FTOS and SFTOS, while Table 2 on page 4 compares FTOS software features on the S-Series to SFTOS support. Both tables use a green checkmark ( ) to indicate Yes.

In most cases, FTOS offers more support for a particular feature, for example, clock control or environmental monitoring, but the table simply notes that the feature is available in both.

Table 1 FTOS and SFTOS Hardware Support

Hardware Support FTOS SFTOS

S-Series models:• S2410C (Cat # S2410-01-10GE-24CP) No (2.4.1.11)

• S2410P (Catalog # S2410-01-10GE-24P) No (2.4.1.11)

• S25N (Catalog # S25-01-GE-24T) No

• S25P (Catalog # S25-01-GE-24P)

• S25V (Catalog # S25-01-GE-24V) No

• S50 (Catalog # SA-01-GE-48T) No

• S50V (Catalog # S50-01-GE-48T-V)

• S50N (Catalog # S50-01-GE-48T-AC)

• S50N (Catalog # S50-01-GE-48T-AC)

• S50N-DC (Cat.# S50-01-GE-48T-DC)

Ethernet Ports• 10/100/1000• 1GbE• 10GbE

AC and DC Power

Clock

Console Port

LEDs

Power Over Ethernet (PoE)

Stacking Port

4 Feature Comparison between FTOS and SFTOS

Table 2 focuses on features available now for S-Series in either FTOS or SFTOS. FTOS has many more features not listed here, because they have not yet been ported to the S-Series. “N/S” stands for “Not Supported”, and generally indicates features that are in the software but not supported on the S-Series.

Table 2 FTOS and SFTOS Software Features

Software Features

FTOS7.8.1

SW-SB-basic-latest

FTOS7.8.1

SW-SB-latest

FTOS7.7.1

SW-SB-basic-latest

FTOS7.7.1

SW-SB-latestSFTOS

Layer2

SFTOSLayer3

802.1x N/S N/S

802.1x with Dynamic VLAN Assignment N/S N/S

802.1x with Guest VLAN and Authentication VLAN

N/S N/S

ACLs: Extended IP, Egress No No No No No No

ACLs: Extended IP, Ingress No No No

ACLs: Standard IP, Egress No No No No No No

ACLs: Standard IP, Ingress No No No

ACLs: Extended MAC, Egress No No No No No No

ACLs: Extended MAC, Ingress

ACLs: Standard MAC, Egress No No No No No No

ACLs: Standard MAC, Ingress

Application Core Dump No No

ARP and Proxy ARP

Calculated Rate Intervals

BGP No No No No No

BPDU Guard No No

Clock Commands

Configuration Scripting No No No No

DHCP Relay Agent

DHCP Server No No No No

DHCP Snooping No No

Dual Images No No No No

DVMRP No No No No N/S N/S


Environmental Monitoring No No

Extended Ping No No

FTP No No

GARP N/S N/S

GMRP No No No No N/S N/S

GVRP N/S N/S

IGMP v1/2 No No No No

IGMP v3 No No No No No

IGMP Snooping

Interface Range

IPv6:• IPv6 management No No No No

• IPv6 static routing No No No No

• IPv6 protocols No No No No No No• IPv6 ACLs No No No No No No

IRDP No No No No

LACP

Layer 2 Protocol Tunneling (BPDU Tunneling)

No No No No N/S N/S

LLDP

LLDP-MED No No

Logging Buffered

Logging Facility

Logging of CLI Commands

Loopback Interface

MAC-based VLANs No No No No N/S N/S

MSTP (802.1s)

Table 2 FTOS and SFTOS Software Features (Continued)

Software Features

FTOS7.8.1

SW-SB-basic-latest

FTOS7.8.1

SW-SB-latest

FTOS7.7.1

SW-SB-basic-latest

FTOS7.7.1

SW-SB-latestSFTOS

Layer2

SFTOSLayer3


Native VLAN

NTP Client No No

Offline Diagnostics No No

OSPF 1583-Forwarding No No No

OSPF Authentication with Plain Text, MD5

No No No

OSPF Graceful Restart *(Helper Role only in 7.7.1.0)

No No No No

OSPF NSSA No No No

OSPF Passive Interface No No No No

OSPF Redistribution No No No

OSPF Stub Area No No No

OSPF Up to Four Paths No No No

OSPF Virtual Link No No No

PIM-DM No No No No N/S N/S

PIM-SM No No No No

PIM-SSM No No No No No

Ping No

Port Monitoring

Power Over Ethernet (PoE) CLI Control

Private VLANs No No

Protocol-based VLAN No No No No N/S N/S

PVST+ (802.1w and 802.1d) No No

QoS — Interface QoS:• Bandwidth management No No

• Dot1p priority marking No

• Egress rate limiting No No No No No No


Software Features

FTOS7.8.1

SW-SB-basic-latest

FTOS7.8.1

SW-SB-latest

FTOS7.7.1

SW-SB-basic-latest

FTOS7.7.1

SW-SB-latestSFTOS

Layer2

SFTOSLayer3


• Egress rate shaping No No No

• Honor incoming dot1p values. No

• Ingress rate policing

• Priority queuing No

No

No

No

NoNo

NoN/S

QoS — Service Policies:• Match Layer 2 (dot1p) No No No No No

• Match Layer 3 (DSCP, IP prec, particular IPs)

No

• Match VLAN No No No No No

• Rate shaping No

• Match packets to assigned queue No

• Color-aware traffic policing No No No No No

• Mark dot1p No No No No No

• Mark DSCP No

• Rate police No

RADIUS Accounting No No No No

RADIUS Authentication (Enable) No No

RADIUS Authentication (Login)

RADIUS Authorization

Router Information Protocol (RIP) No No

RMON

RSTP (802.1w)

SCP No No

sFlow No No

SNMPv1/v2/v3

SNTP Client

Spanning Tree Edge Port

SSH Client No No


Software Features

FTOS7.8.1

SW-SB-basic-latest

FTOS7.8.1

SW-SB-latest

FTOS7.7.1

SW-SB-basic-latest

FTOS7.7.1

SW-SB-latestSFTOS

Layer2

SFTOSLayer3


SSH Server v1/v2

Stacking

Static LAG

Static Routes No

Storm Control Broadcasts

Storm Control Multicasts No No

STP (Spanning Tree Protocol) (802.1d)

Syslog

TACACS Accounting

TACACS Authentication

TACACS Authorization No No

TACACS Authorization of Commands No No

Telnet Client and Server

Time Domain Reflectometer (TDR) No No

TFTP

Time Set

VLAN Stacking (Q-in-Q; Stackable VLANs)

N/S N/S

VLANs Tagged/Untagged

VRRP No No No

Web Interface No No No No N/S N/S


Software Features

FTOS7.8.1

SW-SB-basic-latest

FTOS7.8.1

SW-SB-latest

FTOS7.7.1

SW-SB-basic-latest

FTOS7.7.1

SW-SB-latestSFTOS

Layer2

SFTOSLayer3


System Management in FTOS and SFTOSThis section discusses the following configuration topics:• Managing System Access on page 9• Using the CLI on page 9• Setting up Management Interfaces on page 10• Enabling SNMP on page 10• Enabling Telnet to the Switch on page 11• Managing System Users on page 11• Managing a Stack of S-Series Switches on page 12• Managing the Configuration on page 13• Installing Software on S-Series on page 14• Enabling Ports in FTOS on page 34

Managing System AccessFTOS provides the same methods of system management access as SFTOS, including console, SSH, Telnet, and SNMP. FTOS does not include a Web interface. However, you can use the Web interface provided by the Node Manager component of Force10 Management System (FTMS).

FTOS on the S-Series does not use a management VLAN or a ManagementEthernet IP address. The switch is managed through any port that is accessible through an IP address.

Using the CLIFTOS and SFTOS have basically equivalent CLI structures. The nomenclature and prompts differ slightly:

Table 3: CLI Modes

FTOS Prompt FTOS Mode Name SFTOS Mode Name

Force10> EXEC User Exec

Force10# EXEC Privilege Privileged Exec

Force10(conf)# CONFIGURATION Global Config

Force10(conf-if)#Force10(conf-if-gi-0/0)#

INTERFACE Interface Config

Force10(conf-if-po-0)# Interface Port Channel Config

Force10(conf-if-vl-0)# Interface Vlan Config

Force10(conf-router_ospf)# ROUTER OSPF Router OSPF Config

10 System Management in FTOS and SFTOS

FTOS and SFTOS use most of the same CLI conventions for command input, but FTOS has more features:

* Most FTOS show commands have pipe options (|), including grep, except, find, and no-more (see the bottom of Figure 2 on page 14). For details, see “Filtering show Commands” in the FTOS Command Reference.

** When the CLI displays “----More---”, you can press any alphanumeric key to cause the CLI to cease displaying output and display the prompt.

Setting up Management Interfaces

Enabling SNMPFTOS 7.7.1.0 and later, and SFTOS both support SNMP v1/v2/v3. The SNMP configuration commands and traps provided for the S-Series by FTOS are essentially the same as for the C-Series and E-Series.

1. Configure access to an SNMP community (CONFIGURATION mode):

Table 4: Command Line Interface Features

CLI Feature FTOS SFTOS

Access to command help using a question mark (?) at the prompt, next to a partial or full command, and with a space following a partial or full command: Force10#?

Force10#sh?

Force10#show ?

Yes Yes

Display the configuration of the selected interface with the show config command. Yes No

Execute show commands from all modes by using the prefix do, for example: do show version.

Yes No

Pipe options with show commands.* Yes No

Tab speedkey for command completion Yes Yes

Spacebar for display continuation Yes Yes

Any key other than the Spacebar for ending display output** Yes Yes

Command control of the number of terminal lines Yes Yes

Note: FTOS allows you to manage an S-Series switch through any of its Ethernet ports that has an IP address. There is no facility for configuring a specific management IP address or management VLAN.

FTOS Command Syntax SFTOS Command Syntax

[no] snmp-server community community-name {ro | rw} [security-name name [access name]]

[no] snmp-server community community-name


2. Configure the system to send SNMP notifications:

For details on SNMP command options in FTOS, see the “SNMP and Syslog Commands” chapter in the FTOS Command Reference for the S-Series or the “Management” chapter in the FTOS Configuration Guide for the S-Series.

To display the SNMP configuration with FTOS, use the show running-config snmp command.

Enabling Telnet to the SwitchTelnet access to the switch is enabled by default. SSH access is also available. If SSH is enabled, Telnet should be disabled for security purposes before establishing the SSH connection. For details on SSH, see the “Security” chapter in the FTOS Configuration Guide for the S-Series.

To disable Telnet access, execute the no ip telnet server enable command in CONFIGURATION mode. To reenable Telnet access, execute the ip telnet server enable command.

Managing System UsersThe S-Series can be managed through the console port or through any Ethernet port. By default, with either FTOS or SFTOS, the console port does not require a username or password, while Ethernet ports do. For both, the default username is admin, without a password.

The command syntax for creating a local log-in user is very similar, with FTOS offering an extra option for encryption:

The show users command is available in both FTOS and SFTOS.

Secure SHell (SSH) access is supported by both FTOS and SFTOS.

Both FTOS and SFTOS support AAA user management, including RADIUS and TACACS+, along with the show commands for AAA management.

For FTOS details, see the Security chapter in the FTOS Configuration Guide.


[no] snmp-server host ip-address [traps | informs] [version 1 | 2c | 3] [auth | no auth | priv] [community-string] [udp-port port-number] [notification-type]} (CONFIGURATION mode)

[no] snmptrap name ip-address

(Global Config mode)

[no] snmp-server enable traps [notification-type] [notification-option] (CONFIGURATION mode)snmp trap link-status(Interface mode)

[no] snmp-server enable trap violation

(Interface Config mode)Note: Except for this trap, SFTOS enables all traps unless specifically disabled through other commands.


username name password [encryption-type] password username name passwd password

12 System Management in FTOS and SFTOS

Neither FTOS nor SFTOS allow you to require that a CLI user have another password to progress beyond the EXEC (User Exec in SFTOS) level. This password is commonly called the enable password, because the command to access the next mode is enable.

Managing a Stack of S-Series SwitchesFTOS 7.7.1.0 and later include the facility for managing a stack of S-Series switches. The functionality is somewhat different from SFTOS, with more emphasis on high availability, by establishing a backup unit to immediately become the management unit (stack master) in a failover.

The command syntax for equivalent functions is different. For example:

For details, see:

• S-Series Stacking Commands chapter in the FTOS Command Reference for the S-Series• The Managment chapter and the Stacking S-Series Switches chapter in the FTOS Configuration Guide for the

S-Series


enable [password | secret] [level level] [encryption-type] passwordNote: As you can see, the FTOS command syntax includes options for encryption and privilege levels, while the SFTOS command launches a prompt sequence to create or change the password.

Force10 #enable passwd

Enter new password:*******Confirm new password:*******Password Changed!


show system {stack-unit 0-7 | stack-ports [status | topology]}

show stack-port [counters | diag]

stack-unit 0-7 provision {S25N|S25P|S25V|S50N|S50V}

member unit switchindex

Use two commands:stack-unit 0-7 priority 0-14

redundancy force-failover stack-unit

movemanagement fromunit tounit

stack-unit 0-7 renumber 0-7 switch oldunit renumber newunit

FTOS does not have a special stacking mode to enter stacking commands, as in SFTOS.

stack


Managing the ConfigurationFTOS and SFTOS share the concepts of a running-config and a startup-config, and provide similar facilities for managing them — displaying the configs, copying the running-config to the startup-config, uploading and downloading the configs, editing the config offline, and so forth.

FTOS can display selected parts of the running-config if you specify the part of the running-config that you want to see as a parameter of show running-config — for example, show running-config logging. FTOS provides more options with the show running-config command; see the FTOS Command Reference for details.

Other useful configuration commands in FTOS include:

• show file flash://startup-config• show startup-config• show redundancy

Other Useful show Commands for ManagementFTOS and SFTOS share the most commonly used show commands for management, such as the show version, show hardware, show interface, show logging, show memory, show tech-support, and show users commands.

FTOS also provides other system overview commands, such as show inventory, show processes, show system stack-unit, show system stack-ports, and show software. FTOS provides better hardware monitoring, including commands such as show environment (Figure 1) and show alarms (Figure 2). For details, see the “Control and Monitoring Commands” chapter in the FTOS Command Reference for S-Series.

Figure 1 Example Output of the show environment Command

The show system command provides output similar to the above output for the show environment command, but it also shows more details about a selected stack member or all members.

Force10#show environment all

-- Fan Status ----------------------------------------------------------------------------------Unit TrayStatus Fan0 Fan1 Fan2 Fan3 Fan4 Fan5 0 up up up up up up up

-- Power Supplies --Unit Bay Status Type--------------------------------------------------------------------------- 0 0 up AC 0 1 absent

-- Unit Environment Status --Unit Status Temp Voltage --------------------------------------------------------------------------- 0* online 50C ok

14 Installing Software on S-Series

Figure 2 Example Output of the show alarms Command

Note, in the example of using the show alarms command in Figure 2, that FTOS provides command help when you follow the command with a question mark, in the same way as SFTOS. However, notice that one of the options is a pipe (“|”), which you can follow with one of several arguments. The pipe option is available with every show command. For details on using those options, see the section “Filtering show Commands” in the “CLI Basics” chapter of the FTOS Command Reference for the S-Series.

SFTOS management CLI features that are not included in FTOS for the S-Series include:

• Configuration scripts (However, uploading, text-editing, and downloading the running-config or startup-config is supported by FTOS in the same way as SFTOS.)

• The clear config command (Instead, delete the startup-config (use the delete flash://command) or rename it (for example, rename startup-config startup-config.old. Then enter reload.)

• Dual-image management commands (Only one FTOS image can be stored on an S-Series system.)

Installing Software on S-SeriesThis document covers the following installation scenarios:

• Converting from SFTOS to FTOS 7.7.1.1 on page 16• Converting from SFTOS to FTOS on Stacked Units on page 19• Upgrading S-Series from FTOS 7.6.1.0 to FTOS 7.7.1.1 on page 19• Downgrading from FTOS 7.7.1.1 to FTOS 7.6.1.0 on page 22• Upgrading from FTOS 7.7.1.0 to FTOS 7.7.1.1 on page 24• Upgrading to FTOS 7.8.1.0 on page 26• Upgrading the S-Series Boot Code on page 28• Converting from FTOS 7.7.1 to SFTOS on page 30• Converting from FTOS 7.6.1.0 to SFTOS on page 33

Before downloading software to the S-Series from a network resource, you must:

1. Enable a connected port. See Enabling Ports in FTOS on page 34.

2. Give the port an IP address, as shown in Figure 3 on page 15.

Force10#show alarms ?threshold Alarm thresholds| Pipe through a command<cr>Force10#show alarms

-- Minor Alarms --Alarm Type Duration---------------------------------------------------------------------------No minor alarms

-- Major Alarms --Alarm Type Duration---------------------------------------------------------------------------No major alarmsForce10#show alarms threshold ?| Pipe through a command<cr>Force10#show alarms threshold

-- Temperature Limits (deg C) ----------------------------------------------------------------------------- Minor Minor Off Major Major Off Shutdown


Configure an IP route for the address, as shown in Figure 3 on page 15, and enable IP routing if the FTP server is not on the local subnet.

The write memory and reload commands are the same in FTOS as in SFTOS, as is the copy command. However, the copy command is not supported in FTOS for upgrading the FTOS image. FTOS 7.7.1.0 and later support FTP, SCP, and TFTP. However, the FTOS image can be too large to download via TFTP. For command syntax, see the File Management chapter in the FTOS Command Reference.

FTOS does not support dual image management for the S-Series, so the SFTOS option of {image1 | image2} in the copy command is not available, nor are the other dual-image management commands from SFTOS, such as boot system and update bootcode, which are in SFTOS 2.5.1.0 and above.

Figure 3 Example of Preparing for an FTP Transfer

Two examples of downloading the FTOS software image through FTP are shown in Figure 4 and Figure 5.

Figure 4 Using the upgrade system command in Two Steps

Figure 5 Using the upgrade system command in One Step

Force10(conf)#interface gigabitethernet 0/22Force10(conf-if-gi-0/22)#no shutdownForce10(conf-if-gi-0/22)#ip address 10.10.10.10/23 Force10(conf-if-gi-0/22)#exitForce10(conf)#ip route 0.0.0.0/0 ?A.B.C.D Forwarding router's address gigabitethernet Gigabit Ethernet interface loopback Loopback interface null Null interface port-channel Port-Channel interface tenGigabitethernet TenGigabit Ethernet interface vlan Vlan interface Force10(conf)#ip route 0.0.0.0/0 10.10.10.10Force10#ping 10.10.10.10

Force10#upgrade system ftp:Address or name of remote host []: 10.10.10.10Source file name []: //work/FTOS-SB-7.7.1.1.binUser name to login remote host: ftpPassword to login remote host:

Force10#upgrade system ftp://ftp:[email protected]//work/FTOS-SB-7.7.1.1.bin

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!Erasing SSeries ImageUpgrade Table of Contents, Please Wait..........!..........................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................!

22132660 bytes successfully copied


Converting from SFTOS to FTOS 7.7.1.1

To convert an S-Series to FTOS 7.7.1.1 that is running SFTOS 2.5.2 or higher, download the appropriate Zip file from iSupport to an FTP server. The Zip file contains:

• FTOS-SB-SFTOS-7711-INT.bin: FTOS 7.7.1.1 software in a form that handles the conversion from SFTOS.• Release Notes: The FTOS 7.7.1.1 Release Notes contain a feature list, the upgrade procedure for FTOS

upgrades, and caveats.• Migration Guide (this document): Contains a feature comparison between SFTOS and FTOS and all software

installation procedures.• Conversion Procedure: This document contains the software installation section extracted from the Migration

guide.

The iSupport page is set up in a wizard format to ensure that you download the correct Zip file for your system and the desired software installation.

Before beginning the installation, be sure you have access to the FTP server containing the image files.

Overview: Installing FTOS 7.7.1.0 or later is basically a 5-step procedure:

1. Prepare SFTOS to accept the FTOS image. Save your configuration as a model for reconfiguring. The SFTOS configuration cannot be applied to FTOS.

2. Copy the FTOS image to the unit.

3. Boot the system with that image.

4. Verify that FTOS is correctly installed and then reconfigure. Note that the filename differs from the image name that is displayed by show version.

To convert from SFTOS to FTOS 7.7.1.1:

Caution: You cannot maintain your SFTOS configuration through the conversion to FTOS. As a best practice, you should back up the SFTOS configuration, both to use as a model for creating a similar FTOS configuration and to have it available if you decide to revert the switch to SFTOS.

Caution: You must be running SFTOS version 2.5.2.2 or higher to directly convert to FTOS. To upgrade from an earlier version you must first upgrade to version 2.5.2.2.

Note: You may convert a stand-alone unit, or a stack. If you are upgrading a stack, maintain console connections to each unit in the stack as management configurations are erased during the conversion procedure and you must verify some steps on each unit.

Table 5: Converting from SFTOS to FTOS 7.7.1.1

Step Task Command Mode

1. All configuration statements are erased during the upgrade procedure. Save a copy of your SFTOS configuration so that you can map it to an FTOS configuration using Migrating and Understanding the Differences between the SFTOS and FTOS Operating Systems for the Force10 Networks S-Series (generally referred to as the “Migration Guide”).

2. Enter the command show tech-support and capture the output in case you need assistance from the Force10 Technical Assistance Center.

show tech-support EXEC Privilege


3. Copy the intermediate FTOS system image FTOS-SB-SFTOS-7711-INT.bin to the internal flash memory as image2.

copy tftp://ip-address/filepath image2 EXEC Privilege

4. After the copy process completes:On a stand-alone unit, configure the switch to boot from image2 using the command boot system image2, as shown in Figure 6.If you have a stack, you must change the boot image for every stack unit using the command boot system unit-id image2.

boot system image2

or

boot system unit-id image2

EXEC Privilege

5. Verify that the unit will boot using image2 upon the next reload using the command show bootvar, as shown in Figure 6.If you have a stack, verify that each unit is configured to boot using image2 using the command show bootvar unit-id.

show bootvar

show bootvar unit-id

EXEC Privilege

Figure 6 Configuring the Unit to Boot Using Image2

Table 5: Converting from SFTOS to FTOS 7.7.1.1 (Continued)


Force10-S50V#boot system image2Activating image image2 …Force10-S50V#show bootvar

Image Descriptions

image1 : default image image2 :

Images currently available on Flash

-------------------------------------------------------------------- unit image1 image2 current-active next-active --------------------------------------------------------------------

1 x.x.x.x 2.5.2.31 image{1|2} image2


6. Reload the unit or stack. During boot sequence the unit displays the messages in Figure 7.

reload EXEC Privilege

Figure 7 Booting the Unit using Image2

Warning: DO NOT SAVE YOUR CONFIGURATION. Enter “No” whenever prompted in this procedure. Contact the Force10 Technical Assistance Center in case of error.

7. Verify that the unit is running FTOS version 7.7.1.1.

show version EXEC Privilege

8. Compare the output of show system stack-unit to the show tech-support output you captured in Step 2, to see any variation in the stack unit ID. See Converting from SFTOS to FTOS on Stacked Units.

show system stack-unit EXEC Privilege

Table 5: Converting from SFTOS to FTOS 7.7.1.1 (Continued)


Force10-S50V#reload

Boot Menu Version 01.00.46 11-15-2007

Select an option. If no selection in 2 seconds then operational code will start.

1 - Start operational code. 2 - Start Boot Menu.Select (1, 2):

Operational Code Date: Sat May 31 12:24:28 2008Uncompressing.....

50% 100%||||||||||||||||||||||||||||||||||||||||||||||||||Application Flash Reprogramming..........................................................................................................................................................................Application Flash Reprogramming.....done.

VPD Sector programming

VPD Sector programming... done.

Reprogramming boot flash....

Erase complete.................Reprogramming boot flash....done... Rebooting in 10 sec.[output omitted]


Converting from SFTOS to FTOS on Stacked UnitsTo convert an S-Series stack running SFTOS to FTOS, follow the procedure, above — Converting from SFTOS to FTOS 7.7.1.1 on page 16.

There is a difference between the unit ID selection algorithm on SFTOS and FTOS. Therefore, the management unit on the SFTOS stack might not be the management unit after the conversion to FTOS.

In general, the unit with the highest MAC address becomes unit 0. Of the remaining units, the units with the lowest MAC address have the highest unit ID.

Therefore, you are advised to first connect to each of the console ports in the stack so that you can quickly discover the new management unit (“stack master” in FTOS).

Upgrading S-Series from FTOS 7.6.1.0 to FTOS 7.7.1.1

To upgrade an S-Series to FTOS 7.7.1.1 from FTOS 7.6.1.0, download the software from iSupport to an FTP server. The software is in a Zip file that contains:

• FTOS-SB-7.6.1.0-INT.bin: FTOS software• u-boot.2.8.1.0.bin: You must first upgrade to this boot code before installing FTOS 7.7.1.• FTOS-SB-7.7.1.1.bin: The highest FTOS image currently available (to which you are upgrading)• Release Notes: The FTOS 7.7.1.1 Release Notes contain a feature list, this upgrade procedure, and caveats.• Migration Guide (this document): This document contains a feature comparison between SFTOS and FTOS

and all software installation procedures.• Conversion Procedure: This document contains the software installation section extracted from the Migration

guide.

The iSupport page is set up in a wizard format to ensure that you download the correct Zip file for your system and the desired software installation.

Before beginning the upgrade, be sure you have access to the FTP server containing the image files.

Upgrading the S-Series from FTOS 7.6 to FTOS 7.7 is basically a 5-step procedure:

1. Upgrade the boot code.

2. Upgrade to the intermediate system image.

3. Reload the system.

4. Upgrade from the intermediate FTOS image to FTOS 7.7.1.1.

5. Reload the system.

Caution: Force10 recommends that you have at least 16 MB of memory when running FTOS version 7.6.1.0 or 22 MB when running version 7.7.1.1 before upgrading the system image on a stand-alone unit. Display the available memory on a unit using the show processes memory stack-unit 0 command. If you have less than the recommended available memory, reduce the size of your configuration to free memory before upgrading.

Caution: Force10 recommends that you have at least 34 MB of memory when running version 7.7.1.1 before upgrading the system image on stacked units. Display the available memory on a unit using the command show processes memory stack-unit 0. If you have less than the recommended available memory, reduce the size of your configuration to free memory before upgrading.


To upgrade the S-Series to 7.7.1.0:

Table 6: Upgrading to FTOS 7.7.1.0


1. Verify that you have access to the FTP server containing the intermediate image file FTOS-SB-7.6.1.0-INT.bin, the boot code file u-boot.2.8.1.0.bin, and the FTOS image to which you are upgrading, FTOS-SB-7.7.1.1.bin.

2. Upgrade the boot flash image, as shown in Figure 8.

upgrade boot ftp://userid:password@hostip/filepath

EXEC Privilege

Figure 8 Upgrading the Boot Flash Image via FTP

3. Upgrade to the intermediate system image, as shown in Figure 9.

upgrade system ftp://userid:password@hostip/filepath

EXEC Privilege

Figure 9 Upgrading to the Intermediate System Image via FTP


4. Upon a successful completion of the copy process, reload the unit, as shown in Figure 10.


Figure 10 Reloading the S-Series

5. Verify that the unit is running FTOS-SB-7.6.1.0-INT.bin.


Force10#upgrade boot ftp://[email protected]//home/myname/u-boot.2.8.1.0.bin

!!!!!!!Erasing SSeries BootImageUpgrade Table of Contents, please wait.!.....................................................................!1048576 bytes successfully copied

Force10#upgrade system ftp://[email protected]//home/myname/FTOS-SB-7.6.1.0-INT.bin

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!Erasing Sseries ImageUpgrade Table of Contents, please wait.!..............................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................!13095237 bytes successfully copied

Force10#reloadProceed with reload [confirm yes/no]: yes.00:09:11: %STKUNIT0-M:CP %CHMGR-5-RELOAD: User request to reload the chassis


After reloading the unit, FTOS displays the “InValid Magic” and “System ready” messages shown in the message, below, to indicate that the NVRAM is erased, as expected.

6. Upgrade to FTOS version 7.7.1.1, as shown in Figure 11.


EXEC Privilege

Figure 11 Upgrading the FTOS Image via FTP





9. Clear file system sectors (recommended)

format flash:

You must include the colon (:) when entering this command.

EXEC Privilege

Caution: The format flash: commnd deletes all files, including Configuration files.

10. Write the running configuration to the memory, and create the startup-config file.

write mem Exec Privilege

Message 1 InValid Magic and System Ready

Software Image[3] Hdr Checksum : 0xb9c13975Software Image[3] Data Checksum : 0x8164655bStarting Force10 application

S_SERIES: SSNvInit - InValid Magic, so reset the NV structure. S_SERIES: SSNvInit - InValid Magic, so reset the NV structure.

00:00:16: %STKUNIT0-M:CP %CHMGR-5-SYSTEM_READY: System ready

Table 6: Upgrading to FTOS 7.7.1.0 (Continued)


Force10#upgrade system ftp://[email protected]//home/myname/FTOS-SB-7.7.1.1.bin!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!Erasing Sseries ImageUpgrade Table of Contents, please wait!..............................................................................!..............................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................!

14275705 bytes successfully copiedForce10#


Erasing the NVRAM affects the following configurations:

• chassisSerialNum—FTOS automatically reads the serial number from EEPROM and updates it in the NVRAM if there is a mismatch.

• Last reload reason—FTOS erases this value if the unit was last reloaded by the user.• SSH—SSH host keys are stored in NVRAM. FTOS regenerates then when FTOS applies the startup-config

and the ip ssh server enable configuration. However, if the SSH client has “Strict Host Key” checking enabled, the SSH client denies access to the FTOS SSH server. To resolve this issue, you must modify the SSH client settings so that it uses the new key.

Downgrading from FTOS 7.7.1.1 to FTOS 7.6.1.0

Caution: Do not downgrade the boot code if you upgraded it in the procedure Upgrading S-Series from FTOS 7.6.1.0 to FTOS 7.7.1.1. The boot code is backwards compatible.

Table 7: Downgrading from FTOS 7.7.1.0 to FTOS 7.6.1.0


1. Verify that you have access to the FTP server containing the intermediate image file FTOS-SB-7.6.1.0-INT.bin, and the FTOS image to which you are downgrading, FTOS-SB-7.6.1.0.bin.

2. Downgrade to the intermediate system image, as shown in Figure 9.


EXEC Privilege



4. Verify that the unit is running FTOS-SB-7.6.1.0-INT.bin.


5. Downgrade to FTOS version 7.6.1.0, as shown in Figure 12.


EXEC Privilege

Figure 12 Downgrading the FTOS Image via FTPForce10#upgrade system ftp://[email protected]//home/myname/FTOS-SB-7.6.1.0{x}.bin!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!Erasing Sseries ImageUpgrade Table of Contents, please wait!............................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................!



During reload, FTOS displays the erasure and “InValid Magic” messages shown in Message 2, to indicate that the NVRAM is erased, as expected.



• Last reload reason—FTOS erases this value if the unit was last reloaded by the user.• SSH—SSH host keys are stored in NVRAM. FTOS regenerates them when FTOS applies the startup-config

and the ip ssh server enable configuration. However, if the SSH client has “Strict Host Key” checking enabled, the SSH client denies access to the FTOS SSH server. To resolve this issue, you must modify the SSH client settings so that it uses the new key.







Erasing Sseries Eeprom Secondary Table of Contents, please wait.Erasing Sseries Eeprom Primary Table of Contents, please wait.S_SERIES: SSNvInit - InValid Magic, so reset the NV structure.

Table 7: Downgrading from FTOS 7.7.1.0 to FTOS 7.6.1.0 (Continued)



Upgrading from FTOS 7.7.1.0 to FTOS 7.7.1.1

Caution: Force10 recommends that you have at least 22 MB when running version 7.7.1.0 before upgrading the system image on a stand-alone unit. Display the available memory on a unit using the command show processes memory stack-unit 0. If you have less than the recommended available memory, reduce the size of your configuration to free memory before upgrading.

Caution: Force10 recommends that you have at least 34 MB of memory when running version 7.7.1.0 before upgrading the system image on stacked units. Display the available memory on a unit using the command show processes memory stack-unit 0. If you have less than the recommended available memory, reduce the size of your configuration to free memory before upgrading.

Table 8: Upgrading from FTOS 7.7.1.0 to FTOS 7.7.1.1


Force10 recommends that you back up your startup configuration and any important files or directories to an external media prior to upgrading the system.



EXEC Privilege

Figure 13 Upgrading the FTOS Image via FTP

2. For stacking, propagate the upgrade to all stacked units.

upgrade system stack-unit all Exec Privilege

Figure 14 Upgrading the FTOS Image via FTP - Stacked Units

Force10#upgrade system ftp://[email protected]//home/myname/FTOS-SB-7.7.1.1.bin!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

Erasing Sseries ImageUpgrade Table of Contents, please wait!..............................................................................!..........................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................!


Force10#upgrade system ftp:Address or name of remote host []: 10.10.10.10Source file name []: E7.7.1/E7.7.1.1/FTOS-SB-7.7.1.1.bin User name to login remote host: ftpPassword to login remote host: !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!Erasing Sseries ImageUpgrade Table of Contents, please wait!...........................................................................................................................................................................................................................................................................................................................................................................!14563252 bytes successfully copiedForce10#

Force10#upgrade system stack-unit all!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!


After reloading the unit, FTOS displays the “InValid Magic” and “System ready” messages shown in Message 3 to indicate that the NVRAM is erased, as expected.

3. Upon a successful completion of the copy process, reload the unit.





Figure 16 Output example for show version command


format flash:


EXEC Privilege

Caution: The format flash: command deletes all files, including Configuration files.


write mem Exec Privilege


Software Image[3] Hdr Checksum : 0xb9c13975Software Image[3] Data Checksum : 0x8164655bStarting Force10 application

S_SERIES: SSNvInit - InValid Magic, so reset the NV structure. S_SERIES: SSNvInit - InValid Magic, so reset the NV structure.

00:00:16: %STKUNIT0-M:CP %CHMGR-5-SYSTEM_READY: System ready

Table 8: Upgrading from FTOS 7.7.1.0 to FTOS 7.7.1.1 (Continued)


Force10#show versionForce10 Networks Real Time Operating System SoftwareForce10 Operating System Version: 1.0Force10 Application Software Version: E7.7.1.1Copyright (c) 1999-2008 by Force10 Networks, Inc.Build Time: Fri Sep 12 10:58:00 PDT 2008Build Path: /sites/sjc/work/sw/build/build4/Release/E7-7-1/SW/SRCR6 uptime is 1 week(s), 2 day(s), 9 hour(s), 39 minute(s)

System Type: S50VControl Processor: MPC8451E with 254361600 bytes of memory.

32M bytes of boot flash memory.

1 48-port E/FE/GE with POE (SB) 48 GigabitEthernet/IEEE 802.3 interface(s)Force10#




• Last reload reason—FTOS erases this value if the unit was last reloaded by the user.

SSH—SSH host keys are stored in NVRAM. FTOS regenerates then when FTOS applies the startup-config and the ip ssh server enable configuration. However, if the SSH client has “Strict Host Key” checking enabled, the SSH client denies access to the FTOS SSH server. To resolve this issue, you must modify the SSH client settings so that it uses the new key.

Upgrading to FTOS 7.8.1.0

Caution: FTOS 7.7.1.1 users upgrading from 7.7.1.0 a may lose stacking configuration information if the Master Priority and Unit Numbers are configured differently from the default assignments. Master, Standby and Member units will be reassigned to the default settings during the upgrade process, causing unpredicatable configuration issues.

Caution: FTOS 7.8.1.0 is accompanied by a new boot code — 2.8.1.1. FTOS 7.8.1.0 must be installed on the switch before installing the new boot code because older system images have a restriction on the size of the boot code that excludes boot code 2.8.1.1. Attempting to install the boot code first will result in messages similar to the following % Error: Failed to save FTOS image release record to file.% Error: Upgrade Boot image failed.

See Upgrading the S-Series Boot Code on page 28.

Caution: When your system is running version 7.7.1.0, Force10 recommends that it have at least 22 MB free CPU memory before upgrading the system image on a stand-alone unit and at least 34 MB free CPU memory before upgrading the system image on stacked units.Caution: When your system is running version 7.7.1.1, Force10 recommends that it have at least 22 MB free CPU memory before upgrading the system image on a stand-alone unit or on stacked units.Display the available memory on a unit using the command show processes memory stack-unit 0. If you have less than the recommended available memory, reduce the size of your configuration to free memory before upgrading.Caution: Force10 recommends that your system have at least 22 MB free CPU memory when running version 7.8.1.0 before upgrading the system image on a stand-alone unit or on stacked units.

Table 9: Upgrading to FTOS 7.8.1.0


Force10 recommends that you back up your startup configuration and any important files or directories to an external media prior to upgrading the system.




EXEC privilege

Figure 17 Upgrading the FTOS Image via FTP - Standalone unit

2. For stacked units, propagate the upgrade to other units.

upgrade system stack-unit {all | 0-7} EXEC privilege

Figure 18 Upgrading the FTOS Image via FTP - Stacked Units

3. Upon a successful completion of the copy process, reload the unit.

reload EXEC privilege



show version EXEC privilege

Figure 20 Output example for show version command


Force10#upgrade system ftp:Address or name of remote host []: 10.10.10.10Source file name []: E7.8.1/E7.8.1.0/FTOS-SB-7.8.1.0.binUser name to login remote host: ftpPassword to login remote host: !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!Erasing Sseries ImageUpgrade Table of Contents, please wait!....................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................!14563252 bytes successfully copiedForce10#

Force10#upgrade system stack-unit all!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!


Force10#show versionForce10 Networks Real Time Operating System SoftwareForce10 Operating System Version: 1.0Force10 Application Software Version: E7.8.1.0Copyright (c) 1999-2008 by Force10 Networks, Inc.Build Time: Fri Sep 12 10:58:00 PDT 2008Build Path: /sites/sjc/work/sw/build/build4/Release/E7-7-1/SW/SRCR6 uptime is 1 week(s), 2 day(s), 9 hour(s), 39 minute(s)

System Type: S50VControl Processor: MPC8451E with 254361600 bytes of memory.

32M bytes of boot flash memory.

1 48-port E/FE/GE with POE (SB) 48 GigabitEthernet/IEEE 802.3 interface(s)Force10#


SSH — SSH host keys are stored in NVRAM. FTOS regenerates then when FTOS applies the startup-config and the ip ssh server enable configuration. However, if the SSH client has “Strict Host Key” checking enabled, the SSH client denies access to the FTOS SSH server. To resolve this issue, you must modify the SSH client settings so that it uses the new key.

Upgrading the S-Series Boot Code FTOS 7.8.1.0 is accompanied by a new boot code — 2.8.1.1. Force10 recommends this upgrade, but it is not mandatory. The new boot code enables you to boot the system from an FTOS image residing on a network TFTP source. For details on using the Network Boot facility, see the “Recovering from a Failed Start” section of the Management chapter in the FTOS Configuration Guide for the S-Series.

Boot code 2.8.1.1 is backward-compatible with FTOS 7.7.1.1, but the Network Boot facility is only supported by booting from an FTOS 7.8.1.0 image.

Other features included with boot code 2.8.1.1 include:

• Hardware watchdog support in u-boot. If the u-boot mode is idle for 64 seconds, then the box resets itself.• The OK status LED starts blinking as soon as the box is powered up.• Password recovery commands are available in BOOT_USER mode (bli mode): ignore enable password,

ignore startup-config• restore factory defaults command available in bli mode.• Other BOOT_USER commands are available. See the BOOT_USER Mode chapter in the FTOS Command

Reference for the S-Series.


format flash:


EXEC privilege

The format flash: command deletes all files, including Configuration files. Please implement the write mem command (step 6) to rebuild the startup-config.


write mem

If this command is not entered, configuration settings will be lost when the system is reloaded.

EXEC privilege

Caution: FTOS 7.8.1.0 users upgrading from 7.7.1.0a may lose stacking configuration information if the Master Priority and Unit Numbers are configured differently from the default assignments. Master, Standby and Member units will be reassigned to the default settings during the upgrade process, causing unpredicatable configuration issues.



Using the upgrade boot command is shown in Figure 21:

Caution: FTOS 7.8.1.0 must be installed on the switch before installing the new boot code because older system images have a restriction on the size of the boot code that excludes boot code 2.8.1.1. Attempting to install the boot code first will result in messages similar to the following % Error: Failed to save FTOS image release record to file.% Error: Upgrade Boot image failed.Caution: The boot code upgrade for the non-management members of a stack cannot be accomplished using the upgrade boot stack-unit all command. Instead, you must separate the stack members and upgrade them as standalone units, and then rejoin them into a stack. This issue is tracked in PR 80924.

Table 10: Upgrading the S-Series Boot Code


1. Upgrade the switch/stack to FTOS 7.8.1.0

upgrade system

See Upgrading to FTOS 7.8.1.0 on page 26. EXEC privilege

2. Reboot the system so that it boots up using the FTOS 7.8.1.0 image.

reload EXEC privilege

3. Separate stack members and upgrade each switch separately to boot code 2.8.1.1.

upgrade boot {ftp | scp | tftp} url

After entering the source keyword, you can either follow it with the full url location of the source file in this form: //userid:password@hostip/filepathor Press Enter to launch a prompt sequence.

EXEC privilege

4. Reboot the system. reload EXEC privilege

5. Verify that the new boot code is installed. The Boot flash field should display the version as 2.8.1.1.Note: A boot code image earlier than 2.8.1.1 displays "Present" in the boot flash field, even if FTOS 7.8.1.0 is installed.

show system stack-unit EXEC privilege

6. Rejoin stack members.


Figure 21 Upgrading the Boot Code on S-Series

Converting from FTOS 7.7.1 to SFTOS

To convert an S-Series from FTOS 7.7.1.0 to SFTOS, download the appropriate Zip file from iSupport to an FTP server. The Zip file contains:

• FTOS-SB-7.6.1.0-INT.bin: FTOS software that prepares for the conversion• SFTOS-INT.img: SFTOS software that prepares for the installation of an official SFTOS image• SFTOS Release Notes: The SFTOS Release Notes for version 2.5.3.2 are included, which is currently the

most recent version.• Migration Guide (this document):This document contains a feature comparison between SFTOS and FTOS

and all software installation procedures.• Conversion Procedure: This document contains the software installation section extracted from the Migration

guide.

Overview:

1. Prepare the system to accept SFTOS.

2. Install the intermediate FTOS image — FTOS-SB-7.6.1.0-INT.bin

3. Install the intermediate SFTOS image — SFTOS-INT.img

4. Reenter the inventory information.

5. Install SFTOS 2.5.x.x

Caution: You can only convert a stand-alone unit from FTOS to SFTOS. Caution: You can only convert from FTOS to SFTOS on units that you previously upgraded from SFTOS to FTOS using the image FTOS-SB-SFTOS-INT.bin. If you followed any other conversion path, the unit displays an error message when you perform this procedure. Otherwise, an error message will be displayed, and the installation will quit.

Note: For converting from 7.7.1.1 to SFTOS, the direct path is currently not working. See PR 78048.

Downgrade to 7.7.1.0 first.

Force10#upgrade boot ?ftp: Copy from remote file system (ftp://userid:password@hostip/filepath)scp: Copy from remote file system (scp://userid:password@hostip/filepath)tftp: Copy from remote file system (tftp://hostip/filepath)Force10#$upgrade boot ftp://username:[email protected]/u-boot-2.8.1.1.bin!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!Erasing Sseries ImageUpgrade Table of Contents, please wait.!......................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................!12946259 bytes successfully copiedForce10#reload


To convert from FTOS to SFTOS:

Table 11: Converting from FTOS 7.7.1 to SFTOS


1. Clear all configurations from the unit by deleting the startup-config and reloading the unit. Note: Clearing your configuration frees the required memory for the conversion.

delete startup-configreload

EXEC Privilege

2. Reconfigure a management connection to the unit.Note: This procedure is in the Getting Started chapter of the FTOS Configuration Guide for the S-Series.

3. Enter the command show systemstack-unit unit-id and capture the output; you will need this information to complete the conversion.

show systemstack-unit unit-id EXEC Privilege

4. Copy the intermediate FTOS system image FTOS-SB-7.6.1.0-INT.bin to the internal flash memory.


EXEC Privilege

Figure 22 Converting from SFTOS to the Intermediate FTOS Image

5. Reload the unit. reload EXEC Privilege


6. Create a restricted mode password. enable restrict password CONFIG

7. Enter restricted mode. f10-1231 password abracadabra31 EXEC Privilege

8. Verify that your privilege level is set to 31. show privilege EXEC Privilege

9. Copy the intermediate SFTOS image SFTOS-INT.img to the internal flash memory, as shown in Figure 23. When the unit prompts you to save your configuration, enter “No”; the unit then automatically reboots.Note: You may only transfer the image via FTP or SCP. TFTP is not available.


EXEC Privilege

Force10#upgrade system ftp://myname:[email protected]//home/myname/FTOS-SB-7.6.1.0-INT.binErasing Sseries ImageUpgrade Table of Contents, please wait

.!........................................................

........................................................

........................................................

........................................................

........................................................

........................................................

.......................................................

........................................................



Figure 23 Converting from the intermediate FTOS image to the intermediate SFTOS image.

10. During bootup, the unit prompts you to start operation code or start the boot menu, as shown in Figure 24. Select option 2.


11. Upon selecting option 2, the unit presents a menu of options, as shown in Figure 25. Select the hidden option 30, as shown.


Table 11: Converting from FTOS 7.7.1 to SFTOS (Continued)


Force10-S50V#upgrade system ftp://myname:[email protected]//home/myname/SFTOS-INT.img!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!% Info: Image converted to SFTOS, you will need to reprogram the Manufacturing information to use the switch.System configuration has been modified. Save? [yes/no]: NO

Proceed with reload [confirm yes/no]: yes

Upon completing this boot cycle the unit will come up with SFTOS version 2.5.2.2

Boot Menu Version 01.00.45 10-13-2006

Select an option. If no selection in 2 seconds thenoperational code will start.

1 - Start operational code.2 - Start Boot Menu.Select (1, 2):2

Options available1 - Start operational code2 - Change baud rate3 - Retrieve event log using XMODEM4 - Load new operational code using XMODEM5 - Display operational code vital product data6 - Run flash diagnostics7 - Update boot code8 - Delete operational code9 - Reset the system10 - Restore configuration to factory defaults (delete config files)11 - Activate Backup Image[Boot Menu] 30


Converting from FTOS 7.6.1.0 to SFTOSIf you want to convert from FTOS version 7.6.1.0 to SFTOS, contact the Technical Assistance Center.

12. Upon selecting option 30, the unit presents another menu of options, as shown in Figure 26. Select option 8.

Figure 26 Selecting an Option from the Boot Menu

13. Upon selecting option 8, the unit prompts you for some manufacturing information that was erased during the conversion, as shown in Figure 27. This information is in the output you captured in Step 2. If you make any error during this process, allow the unit to complete the boot process, and begin again from Step 6.

Figure 27 Programming the EEPROM with Manufacturing Information

14. Once you enter all the information, select option 0 which returns you to the Boot Menu, and then select 9 to reset the system.

15. Convert from the intermediate SFTOS image any official SFTOS image using the SFTOS upgrade procedure in the SFTOS release notes.

Table 11: Converting from FTOS 7.7.1 to SFTOS (Continued)


Boot code utilities menuOptions are:1 - Read/Write memory2 - Display PCI bus3 - Display PCI bus details4 - Display core info and bus speeds5 - Display file system details6 - RAM test7 - File system directory listing8 - Generate and store VPD info9 - CPLD diagnostics10 - Switch diagnostics11 - Format file system12 - File system test13 - Print VPD info14 - Check Filesystem15 - Upload Image in FFS16 - Read Temperature Monitor17 - Read I2C devices18 - HW modules19 - Read RTC20 - Set RTC0 - Return to main menuSelect option (0-20): 8

Enter the six byte starting MAC address (example: 000629328140)-> 0001e8d5f867Entered MAC: 00:01:E8:00:00:00

Enter a serial number (no greater than 20 chars) -> DL123456789

Enter a date code in the form MMYYYY -> 072007

Enter a Part Number -> 759003600

Enter a Revision -> E


Enabling Ports in FTOSThe most fundamental difference between the SFTOS and FTOS CLIs is the port ID convention:

Table 12 Port ID Conventions

To select a port for configuration in FTOS, use one of the following command keywords to identify its capacity, followed by the stack unit ID and port information:

• 1-Gigabit Ethernet interface: Enter the keyword gigabitethernet. • 10-Gigabit Ethernet interface: Enter the keyword tengigabitethernet.

For example, port 22 in stack member 1 would be selected with the command gigabitethernet 1/22.

When FTOS is first installed, all ports are disabled by default. Enabling ports in FTOS is done with the no shutdown command, either globally or per interface, as in SFTOS:

• Enable a specific port by selecting the port, as described above (see Figure 28 on page 35).• Enable a range of ports, as illustrated in Figure 29 on page 35.

Finally, in FTOS, to enable a port, you must set it in either Layer 2 or Layer 3 mode:

• Layer 2 mode: Use the switchport command (Figure 29).• Layer 3 mode: Assign an IP address to the port with the ip address command (Figure 28).

As in SFTOS, FTOS ports are set by default to auto-negotiate their speed and duplex mode. FTOS commands that set port speeds are similar to SFTOS, although auto-negotiation in FTOS has more options, as shown below. For details, see the “Interfaces” chapter in the FTOS Command Reference for the S-Series):

FTOS Port ID Examples SFTOS Port ID Examples

gigabitethernet 0/22 1/0/22

tengigabitethernet 0/52 1/0/52


speed {10 | 100 | 1000 | auto}duplex {half | full}

speed {10 | 100 | 1000} {half-duplex | full-duplex}}auto-negotiate

(no global CONFIGURATION mode equivalent; use the INTERFACE RANGE mode)

speed all {10 | 100 | 1000} {half-duplex | full-duplex}}auto-negotiate all

negotiation auto mode ?

forced-master Force port to master modeforced-slave Force port to slave mode

(no equivalent)


Figure 28 Example of Enabling a Layer 3 Port

When you enable a range of ports with FTOS, you use the same interface range command (CONFIGURATION mode) that you use in SFTOS, but the command options are as described above — gigabitethernet (for ports 1 through 48) (Figure 29) and tengigabitethernet (for ports 49 through 52).

Figure 29 Example of Enabling a Range of Ports

Other FTOS commands that enable interfaces, such as interface vlan vlan-id (see Creating VLANs on page 36) and interface port-channel channel-number, are the same as in SFTOS. For more on the interface and interface range commands, see the “Interfaces” chapter in the FTOS Command Reference for the S-Series.

Inspecting the configuration in FTOS is similar to SFTOS in the options and output of the commands show interface and show interfaces, although the order of the output differs between FTOS and SFTOS. FTOS also provides the show config command from within the INTERFACE mode.

Basic Software ConfigurationThis section discusses the following configuration topics:

• Creating VLANs• Enabling Spanning Tree Protocol on page 37• Creating Link Aggregation Groups (LAGs) on page 38• Creating Access Control Lists (ACLs) on page 40• Using Quality of Service (QoS) on page 44• Using OSPF on page 47• Using Virtual Router Redundancy Protocol (VRRP) on page 50• Using IGMP Snooping on page 51

Note: FTOS 7.7.1.0 adds IEEE 802.3af support on the S-Series, the Power over Ethernet (PoE) standard for sending power through copper ports. See the Power over Ethernet (PoE) chapter in the FTOS Command Reference, which contains PoE commands designed specifically for the S-Series.

Force10#configForce10(conf)#interface gigabitethernet 0/22Force10(conf-if-gi-0/22)#no shutdownForce10(conf-if-gi-0/22)#ip address 10.10.10.1/24Force10(conf-if-gi-0/22)#exitForce10(conf)#

Force10(config)#interface range gigabitethernet 0/1 - 20Force10(config-if-range)#no shutdownForce10(config-if-range)#switchportForce10(config-if-range)#exitForce10(conf)#

36 Basic Software Configuration

Creating VLANsVirtual LAN (VLAN) support in FTOS follows the same IEEE 802.1Q standard (Virtual Bridged Local Area Networks) conventions as SFTOS.

VLANs are Layer 2 constructs, so the interfaces that comprise a VLAN must also be in Layer 2 mode. A key difference in FTOS is that FTOS does not automatically place an interface in Layer 2 mode, as does SFTOS. To place an interface in Layer 2 mode using FTOS, use the switchport command (see Figure 29 on page 35).

Table 13: Comparison between SFTOS and FTOS of VLAN Support

To create a VLAN, FTOS uses the same interface vlan vlan-id command in CONFIGURATION mode as in SFTOS. FTOS also uses the same tagged and untagged commands used in SFTOS to add ports and Port Channels to the VLAN. In both FTOS and SFTOS, all untagged interfaces must be in a VLAN, and an unassigned untagged interface is placed in the default VLAN 1.

Figure 30 Example of Creating a VLAN in FTOS

As described above, FTOS has the same facility as SFTOS to configure VLANs from either the INTERFACE RANGE mode or INTERFACE VLAN mode.

Support of VLANs in FTOS Support of VLANs in SFTOS

On the S-Series, both FTOS and SFTOS support 1024 VLANs at one time, any of which can have a VLAN ID up to 3965.

Guest and Authentication VLANs no Guest and Authentication VLANs

no Private VLANs Private VLANs

no Policy-based VLANs Policy-based VLANs

Both FTOS and SFTOS allow VLANs to include Port Channels (LAGs) (tagged and untagged).

Both FTOS and SFTOS support Native VLANs (see Table ).

Both FTOS and SFTOS support GVRP.

Both FTOS and SFTOS support Stackable VLANs (VLAN-Stacking).

Force10#configForce10(conf)#interface vlan 22Force10(conf-if-vlan)#untagged gi 0/2Force10(conf-if-vlan)#tagged gi 0/3Force10(conf-if-vlan)#exitForce10(conf)#


Native VLAN Support

For more on using the FTOS CLI to create VLANs, see the “Interfaces” chapters in the FTOS Command Reference for S-Series and the FTOS Configuration Guide.

Enabling Spanning Tree ProtocolBoth SFTOS and FTOS support various flavors of the Spanning Tree Protocol (SPT) on the S-Series, as displayed in this table:

1. As described above (see Enabling Ports in FTOS on page 34), FTOS uses the switchport command to configure Layer 2 ports, which you must do before you make a port available to a Spanning Tree topology. (To remove an interface from the topology, use the no switchport command.)

2. As with SFTOS, you must globally (CONFIGURATION mode) enable the STP protocol that you want to use:

With FTOS, you do not need to enable specific ports for the spanning tree. Another feature that you can enable in FTOS includes EdgePort — SFTOS also has this feature but the FTOS enabling command is different. In RSTP, the command is spanning-tree rstp edge-port, in INTERFACE mode.


portmode hybrid

Set a port (physical ports only) to accept both tagged and untagged frames. A port configured this way is identified as a hybrid port in report displays.

tagged interface native

Set VLAN 1 as the native VLAN for the interface with the interface tagged for VLAN 1.untagged interface

Set VLAN 1 as the native VLAN for the interface with the interface untagged for VLAN 1.

ProtocolFTOS Support (on S-Series) SFTOS Support

Spanning Tree Protocol (STP) yes yes

Multiple Spanning Tree Protocol (MSTP) yes yes

Per-VLAN Spanning Tree Protocol Plus (PVST+) yes no

Rapid Spanning Tree Protocol (RSTP) yes yes

Protocol FTOS Command

Multiple Spanning Tree Protocol (MSTP) Force10(conf)#protocol spanning-tree mstp

Force10(conf-mstp)#no disable

Per-VLAN Spanning Tree Protocol Plus (PVST+) Force10(conf)#protocol spanning-tree pvst


Rapid Spanning Tree Protocol (RSTP) Force10(conf)#protocol spanning-tree rstp



Creating Link Aggregation Groups (LAGs)Both FTOS and SFTOS support IEEE 802.3 (802.3ad), enabling the configuration of LAGs, also called Port Channels, as either dynamic or static. The major difference is that SFTOS configures dynamic LAGs by default, using Link Aggregation Control Protocol (LACP), while FTOS does not.

Port Channel Support

Of course, the number of LAGs is constrained by the number of available ports, because a LAG must consist of at least one port.

Basic LAG commands are almost the same in FTOS and SFTOS, as shown in this table. For details on FTOS commands, see the “Interfaces” and the “LACP” chapters in the FTOS Command Reference for the S-Series:

The clear port-channel command in SFTOS for removing all LAGs is not available in FTOS.

FTOS SFTOS

Maximum Port Channel IDs 52 (single S-Series switch)128 (stack maximum)

48

Maximum Members per Port Channel 8 8

Purpose Command Syntax SFTOSVariation

FTOSVariation

Create or delete the LAG. [no] interface port-channel 1-128

Enable the LAG. no shutdown

Place the LAG in Layer 2 mode. switchport Always in Layer 2 mode

Add an IP address to the LAG. ip address A.B.C.D mask Not available

Add or delete one or more ports to the LAG. Set a range with hyphens or commas between port IDs.

[no] channel-member interface interface = unit/slot/port

interface = gigabitethernet slot/port

(or, for 10G ports:)tengigabitethernet slot/port

Configure load-balancing. (Load-balancing is hard-wired on the S-Series; manual overrides are not available in either FTOS or SFTOS.)

Display summary LAG settings. show interface port-channel brief

Display settings for a specific LAG. show interface port-channel 1–128


Using Link Aggregation Control Protocol (LACP)SFTOS configures dynamic LAGs by default, while FTOS does not. While you use the protocol static and protocol lacp commands in SFTOS to manage the state of the LAG — static or dynamic — in FTOS, you create a dynamic LAG by enabling LACP for specific ports, as shown in the following command sequence:

Table 15: LACP Modes

You must do the same configuration for both ends of the LAG.

Figure 31 Example of Configuring LACP

Table 14 Using LACP

Step Command Syntax Command Mode Purpose

1. interface interface CONFIGURATION Access the port specified by interface, in the form gigabitethernet slot/port.

2. no shutdown INTERFACE Enable the port.

3. port-channel-protocol LACP INTERFACE Enable LACP on the port and enter LACP mode.

4. port-channel number mode [active] [passive] [off]

LACP Configure the LACP mode, as shown in Table 15.

Mode Function

active An interface is in an active negotiating state in this mode. LACP runs on any link configured in the active state and also automatically initiates negotiation with other ports by initiating LACP packets.

passive An interface is not in an active negotiating state in this mode. LACP runs on any link configured in the passive state. Ports in a passive state respond to negotiation requests from other ports that are in active states. Ports in a passive state respond to LACP packets.

off An interface cannot be part of a dynamic port channel in the off mode. LACP will not run on a port configured in the off mode.

Force10(conf)#interface Gigabitethernet 3/15Force10(conf-if-gi-3/15)#no shutdownForce10(conf-if-gi-3/15)#port-channel-protocol LACPForce10(conf-if-gi-3/15)#port-channel 32 mode active...Force10(conf)#interface Gigabitethernet 3/16Force10(conf-if-gi-3/16)#no shutdownForce10(conf-if-gi-3/16)#port-channel-protocol LACPForce10(conf-if-gi-3/16)#port-channel 32 mode passive...Force10(conf)#interface Gigabitethernet 4/15Force10(conf-if-gi-4/15)#no shutdownForce10(conf-if-gi-4/15)#port-channel-protocol LACPForce10(conf-if-gi-4/15)#port-channel 32 mode active


In addition to the above commands, FTOS provides more LACP command options than does SFTOS:

See the FTOS Configuration Guide for an example of setting up of LACP on a port. See the FTOS Command Reference for the S-Series for example outputs of the show lacp command.

Creating Access Control Lists (ACLs)Both SFTOS and FTOS provide these basic kinds of ACL (ingress-only) on the S-Series:

• Extended MAC ACLs • Standard and extended IP ACLs

Both SFTOS and FTOS provide a loopback ACL to protect access to switch management.

FTOS also provides standard MAC ACLs and IP prefix lists to redistribute OSPF routes meeting specific criteria.

ACL LimitationsWhile SFTOS has a hard limit of 100 ACLs, each with no more than nine rules applied to inbound traffic, FTOS limits are determined by the system memory and its allocation of MAC addresses. Further, FTOS divides ports into port-pipes on the S-Series — one port-pipe on the S25 models and two on the S50N and S50V. The maximum number of ACL rules per port-pipe is 768 Layer 2 rules and 768 Layer 3 rules.

Both SFTOS and FTOS allow more than one ACL on an interface, but SFTOS restricts the total number of rules to nine, including the implicit deny rule. With FTOS, you can assign multiple ingress ACLs. FTOS allows the maximum of 768 rules to be all assigned to one ACL or divided into any number of ACLs.

Purpose FTOS Command Syntax Notes

Clear Port Channel counters. clear lacp port-channel-number counters Without a Port Channel specified, the command clears all Port Channel counters

Debug LACP (configuration, events etc.)

[no] debug lacp [config | events | pdu [in | out | [interface [in | out] ] ] ]

Enter the keyword config to debug LACP configuration information.Enter the keyword events to debug LACP event information.Enter the keyword pdu to debug LACP PDUs.

Configure the port priority to influence which ports will be put in standby mode when a hardware limitation does not allow all compatible ports from aggregating.

[no] lacp port-priority priority-value Range: 1 to 65535Default: 32768The higher the value number, the lower the priority.

Display the LACP matrix. show lacp port-channel-number [sys-id | counters]

FTOS does not have the show ports command.


With either SFTOS and FTOS, you can assign both Layer 2 (MAC) and a Layer 3 (IP) ACL to an interface at the same time.

The basic sequence of ACL creation and application is the same:

• Name an ACL.• Create one or more rules for that ACL.• Assign the ACL to an interface. (You can also add rules later to the ACL.)

• FTOS also enables you to assign an ACL to a terminal line.• While SFTOS enables you to assign an ACL globally, FTOS does not.

The commands and filter options differ significantly, as shown in Table 16 (MAC ACLS) and Table 17 (IP ACLS):

Table 16MAC ACL Commands


Create an extended MAC ACL:

mac access-list extended name mac access-list extended name

Create an extended MAC ACL:

seq sequence-number {deny | permit} {any | host mac-address | mac-source-address mac-source-address-mask} {any | host mac-address | mac-destination-address mac-destination-address-mask} [ethertype operator] [count [byte]] [log] [monitor]• count: Count packets processed by the

filter.• byte: Count bytes processed by the filter.• log: Log the packets.• monitor: Monitor traffic on the monitoring

interface specified in the flow-based monitoring session.

{deny|permit} {srcmac | any} {dstmac | any} [assign-queue queue-id_0-6] [cos 0-7] [ethertypekey] [0x0600-0xFFFF] [redirect unit/slot/port] [vlan {eq 0-4095]Note: The srcmac and dstmac values in this syntax statement are the same as the mac-address and mac-destination-address in the FTOS command.

Attach a specified MAC ACL to an interface:

mac access-group name {in [vlan vlan-range] | out}

mac access-group name [1-4294967295] in

Note that, in FTOS, you assign the sequence number of rules when creating the ACL, while, in SFTOS, you assign sequence numbers to ACLs here. SFTOS enacts the rules of a particular ACL in the sequence in which they were added to the ACL.


Table 17IP ACL Commands


Create a standard IP ACL:

ip access-list standard access-list-name access-list 1-99

Add a rule to the standard IP ACL:

{deny | permit} {source [mask] | any | host ip-address} [count [byte] | log ] [order] [monitor]

access-list 1-99 {deny | permit} {every | srcip srcmask} [log] [assign-queue queue-id] [{mirror | redirect} unit/slot/port]

Attach a specified IP ACL to an interface:

ip access-group access-list-name in [implicit-permit] [vlan vlan-range]

ip access-group ACLnumber in [1-4294967295]

Create an extended IP ACL:

ip access-list extended access-list-name access-list 100-199


For details on ACLs in FTOS, see the ACL chapters in the FTOS Command Reference for the S-Series and the FTOS Configuration Guide for the S-Series.

Add a rule to the extended IP ACL:

deny {ip | ip-protocol-number} {source mask | any | host ip-address} {destination mask | any | host ip-address} [count [byte] | log ] [order] [monitor]

• Configure an egress filter that drops specified ARP packets:deny arp {destination-mac-address mac-address-mask | any} vlan vlan-id {ip-address | any | opcode code-number} [count [byte] | log ] [order] [monitor]

• Configure an egress filter that drops specified types of Ethernet packets:deny ether-type protocol-type-number {destination-mac-address mac-address-mask | any} vlan vlan-id {source-mac-address mac-address-mask | any} [count [byte] | log] [order] [monitor]

• Configure a filter to drop all or specific ICMP messages:deny icmp {source mask | any | host ip-address} {destination mask | any | host ip-address} [message-type] [count [byte] | log ] [order] [monitor]

• Configure a filter that drops TCP packets meeting the filter criteria:deny tcp {source mask | any | host ip-address} [bit] [operator port [port]] {destination mask | any | host ip-address} [bit] [operator port [port]] [count [byte] | log ] [order] [monitor]

• Configure a filter to drop UDP packets meeting the filter criteria:deny udp {source mask | any | host ip-address} [operator port [port]] {destination mask | any | host ip-address} [operator port [port]] [count [byte] | log ] [order] [monitor]Versions of the commands above use permit instead of deny to permit packets based on those filter criteria.

access-list 100-199 {deny | permit} {every | icmp | igmp | ip | tcp | udp | protocol_number} {any | srcip srcmask} {any | eq {portkey | 0-65535}{any | dstip dstmask} [eq {portkey | 0-65535}] [precedence precedence | tos tos tosmask | dscp dscp] [log] [assign-queue queue-id] [redirect unit/slot/port]

Table 17IP ACL Commands (Continued)



Using Quality of Service (QoS)FTOS has both the Class of Service and Diffserv functionality of SFTOS, along with the ability to assign rate policing directly to an interface, rather than through a policy map.

The Class of Service command mapping between FTOS and SFTOS is displayed in Table 18:

Table 18Class of Service Commands

The Diffserv command mapping between FTOS and SFTOS is displayed below.

Purpose FTOS Syntax SFTOS Syntax

Set dot1p priority per port. (The FTOS commands are not yet enabled for the S-Series. Use a Policy QoS to match and map.)

• classofservice dot1p-mapping userpriority trafficclass

• classofservice ip-dscp-mapping ipdscp trafficclass

Honor 802.1p markings on incoming switched traffic on the selected interface.

service-class dynamic dot1p classofservice trust dot1p

Set the CoS Trust Mode for all interfaces to IP DSCP.

trust diffserv classofservice trust ip-dscp

Set the CoS Trust Mode for all interfaces to Untrusted.

(This is default behavior, with no CLI required.)

classofservice trust untrusted

Show commands show interfaces [interface] rate [limit | police]

• show classofservice dot1p-mapping

• show classofservice ip-dscp-mapping

• show classofservice ip-precedence-mapping

• show classofservice trust


Table 19 Policy-Based QoS Commands

While the full per-port rate policing functionality of FTOS is not implemented on the S-Series, the following input policy and output policy commands are available, as shown in Table 20 and Table 21:


Enable Diffserv not required diffserv

Create a class map to match packets to a specified class.

class-map {match-all | match-any} class-map-name [layer2]

class-map match-all classmapname

Specify Layer 3 class-map match criteria.

• match ip access-group access-group-name [set-ip-dscp value]

• match ip precedence ip-precedence-list [set-ip-dscp value]

• match ip dscp dscp-list [set-ip-dscp value]

• match dstip• match dstl4port• match ip dscp• match ip precedence• match ip tos• match protocol• match srcip• match srcl4port• match protocol

Specify Layer 2 class-map match criteria.

(Layer 2, policy-based QoS is not supported.)

• match cos• match destination-address• match ethertype• match mac dot1p• match secondary-cos• match secondary-vlan• match source-address mac

Create a policy map. policy-map-input policy-map-name [layer2]

policy-map policyname in

Assign a policy to an interface. • service-policy input policy-map-name [layer2]

• service-policy output policy-map-name

[no] service-policy in policy-map-name

Match based on the VLAN ID. (not available in FTOS) match vlan

Show commands • show qos class-map [class-name]

• show qos policy-map {summary [interface] | detail [interface]}

• show class-map [classname]• show policy-map

[policyname]• show diffserv service

{<lucindaRgOb>unit/slot/port | 1-3965 | brief} in


Table 20 Input Policy Commands

*FTOS supports four queues on the S-Series for data traffic, mapped to the eight dot1p-priority values and eight E-Series queues as shown in Table 28 in the QoS chapter of the FTOS Configuration Guide for the S-Series.

Table 21 Outgoing Policy Commands

For details on QoS in FTOS, see the QoS chapters in the FTOS Command Reference for the S-Series and the FTOS Configuration Guide for the S-Series.

See also the Storm Control commands in the Storm Control chapter in the FTOS Command Reference for the S-Series and the the QoS chapter in the FTOS Configuration Guide for the S-Series.

Purpose FTOS Syntax SFTOS

Police the incoming traffic rate. rate police committed-rate [burst-KB] [peak peak-rate [burst-KB]] [vlan vlan-id]

conform-color class-map-name [exceed-color class-map-name]

Trust DSCP or dot1p value. trust {diffserv | dot1p | ipv6-diffserv}

Not available

Assign a class map and QoS policy to different queues.*

service-queue queue-id [class-map class-map-name] [qos-policy qos-policy-name]

assign-queue queueid

Shape the traffic output of the selected interface.

rate shape rate [burst-KB]

Configure a unicast queue as a strict-priority (SP) queue.*

strict-priority queue unicast queue number

number = queue number (0 to 3 on S-Series)*

[no] cos-queue strict queue-id-1 [queue-id-2 … queue-id-n>

Purpose FTOS Syntax SFTOS

Police the outgoing traffic rate.

rate-limit committed-rate [burst-KB ] [peak peak-rate [burst-KB ]]

• police-simple {1-4294967295 1-128 conform-action {drop | set-prec-transmit 0-7 | set-dscp-transmit 0-63 | set-cos-transmit 0-7 | set-secondary-cos-transmit 0-7 | transmit} [violate-action drop]}

Shape the interface’s traffic output.

rate-shape rate [burst-KB] traffic-shape bw

Mark outgoing traffic. set {ip-dscp value | mac-dot1p value }(DSCP marking is available on S-Series in FTOS 7.7.1.0)

• mark cos• mark ip-dscp dscpval• mark ip-precedence

Configure bandwidth management.

bandwidth-percentage percentage Not available

Configure WRED. • threshold min number max number

• wred-profile wred-profile-nam• wred {yellow | green}

profile-name

Not available


Using OSPFFTOS on the S-Series supports Layer 3 routing via static routes and OSPF.

Table 22 has examples using FTOS and SFTOS to create a basic OSPF implementation:

Table 22 OSPF Configuration Example

For a more detailed comparison of OSPF configuration using SFTOS and FTOS, see the tech tip Configuring OSPF MD5 between E-Series and S-Series at:

https://www.force10networks.com/CSPortal20/KnowledgeBase/ConfiguringOSPFMD5BetweenEandS.aspx

FTOS SFTOS

router ospf 1 network 111.1.1.0/24 area 2

interface gigabitethernet 1/18no shutdownip address 111.1.1.1/24!

ip routing!router ospf router-id 111.1.1.2 enable!interface 1/0/18 no shutdownip address 111.1.1.2 255.255.255.0ip ospf ip ospf areaid 0.0.0.2

Table 23 OSPF Command Mapping

Function FTOS SFTOS

Enable RFC-2328 flooding behavior.

flood-2328 [no] 1583compatibility

Configure an area to be an NSSA.

area area-id nssa [default-information-originate] [no-redistribution][no-summary]

• [no] area areaid nssa• area areaid nssa

default-info-originate [metric] [{comparable | non-comparable}]

• area areaid nssa no-redistribute• area areaid nssa no-summary• area areaid nssa translator-role

{always | candidate} • area areaid nssa

translator-stab-intv stabilityinterval

• area areaid range ipaddr subnetmask {summarylink | nssaexternallink} [advertise | not-advertise]


Create a stub area and specify whether to send a summary LSA.

area area-id stub [no-summary] • area areaid stub• [no] area areaid stub

summarylsa

Create a virtual link. area area-id virtual-link router-id [[authentication-key [encryption-type] key] | [message-digest-key keyid md5 [encryption-type] key]] [dead-interval seconds] [hello-interval seconds] [retransmit-interval seconds] [transmit-delay seconds]

• [no] area areaid virtual-link neighbor

• area areaid virtual-link neighbor authentication {none | {simple key} | {encrypt key keyid}}

• area areaid virtual-link neighbor dead-interval 1-65535

• area areaid virtual-link neighbor hello-interval 1-65535

• area areaid virtual-link neighbor transmit-delay 0-3600

Set an administrative distance and adjust which OSPF routes the system will prefer.

distance ospf [external dist3] [inter-area dist2] [intra-area dist1]

distance ospf {intra | inter | type1 | type2} 0-255

Configure distribute lists. • distribute-list prefix-list-name in [interface]

• distribute-list prefix-list-name out [bgp | connected | isis | rip | static]

[no] distribute-list 1-199 out {rip | static | connected}

Specify how the OSPF interface cost is calculated based on the reference bandwidth method.

auto-cost [reference-bandwidth ref-bw]

Not available

Configure FTOS to generate a default external route into an OSPF routing domain.

default-information originate [always] [metric metric-value] [metric-type type-value] [route-map map-name]

default-information originate [always] [metric 0-16777215] [metric-type {1 | 2}]

Set the OSPF ASBR to advertise one external route.

summary-address ip-address mask [not-advertise] [tag tag-value]

Not available

Configure OSPF area authentication.

ip ospf message-digest-key keyid md5 key

• ip ospf authentication {none | simple key}

• ip ospf authentication-key key keyid

Table 23 OSPF Command Mapping (Continued)


For details on OSPF in FTOS, see the OSPF chapters in the FTOS Command Reference for the S-Series and the FTOS Configuration Guide for the S-Series.

Assign an interface to an OSPF area and specify interface characteristics.

• area {0-65535 | A.B.C.D}• ip ospf cost• ip ospf dead-interval seconds• ip ospf hello-interval seconds• ip ospf message-digest-key

keyid md5 key• ip ospf mtu-ignore• ip ospf network {broadcast |

point-to-point}• ip ospf priority number• ip ospf retransmit-interval

seconds• ip ospf transmit-delay seconds

• ip ospf areaid areaid• ip ospf cost 1-65535• ip ospf dead-interval seconds• ip ospf hello-interval seconds• [no] ip ospf mtu-ignore• ip ospf priority 0-255• ip ospf retransmit-interval

seconds• ip ospf transmit-delay seconds

Configure a grace period while OSPF chages its interface authentication type.

ip ospf auth-change-wait-time seconds

Not available

Log adjacency changes. log-adjacency-changes Not available

Specify the maximum number of best paths to a given destination.

maximum-paths number maximum-paths maxpaths

Specify redistribution into OSPF.

redistribute {connected | rip | static} [metric metric-value | metric-type type-value] [route-map map-name] [tag tag-value]

redistribute {rip | static | connected} [metric 0-16777215] [metric-type {1 | 2}] [tag 0-4294967295] [subnets]

Define which interfaces run OSPF and the OSPF area for those interfaces.

network ip-address mask area area-id

Not available

Set the time interval between when the E-Series receives a topology change and starts anshortest path first (spf) calculation.

timers spf delay holdtime

Range: 0 to 4294967295 seconds for both delay and holdtime

Not available

Create a passive interface.

passive-interface interface Not available

Table 23 OSPF Command Mapping (Continued)


Using Virtual Router Redundancy Protocol (VRRP) VRRP is one way to eliminate a single point of failure in a routed network. VRRP is enabled by default with both FTOS and SFTOS.

FTOS provides an enhanced implementation of VRRP with the ability to monitor the state of any interface by a virtual group. FTOS supports 128 VRRP groups on the S-Series, and each VRRP group can track up to 12 interfaces, which may affect the priority of the VRRP group. If the state of the tracked interface goes down, the VRRP group’s priority is decreased by a default value of 10 (also known as cost). If the tracked interface’s state goes up, the VRRP group’s priority is increased by 10.

Table 24 shows an example of the sequence of commands and their options used to configure VRRP with SFTOS and FTOS.

Table 24 VRRP Configuration Comparison

For details on VRRP in FTOS, see the VRRP chapters in the FTOS Command Reference for the S-Series and the FTOS Configuration Guide for the S-Series.


interface gigabitethernet 0/3 vrrp-group 1-255

advertise-interval seconds

description text

priority 1-255authentication-type [encryption-type] passwordpreempt

track interface [priority-cost cost]

ip routinginterface 1/0/6 ip vrrp group_id

ip vrrp group_id timers advertise 1-255

ip vrrp group_id priority 1-255ip vrrp group_id authentication {none | simple

[key]} [no] ip vrrp group_id preempt


Using IGMP SnoopingFTOS 7.6.1.0 introduced IGMPv1/v2 snooping on S-Series standalone and stack master units. In FTOS 7.8.1.0, IGMPv1/v2 snooping is now also supported on stack member units.

SFTOS requires two commands to enable IGMP snooping, while FTOS requires one, as shown in Table 25.

Table 25 IGMP Snooping Commands


Enable [disable] the IGMP snooping feature

(function included in the ip igmp snooping enable command)

[no] igmp enable

Enable [disable] IGMP snooping globally.

[no] ip igmp snooping enable igmp interfacemode enable all

Enable [disable] IGMP snooping on an interface

(no equivalent) [no] igmp

Set the interval between successive Group-Specific Query messages.

ip igmp snooping last-member-query-interval milliseconds

(only on VLAN interface, not the physical interface and Port Channel)

ip igmp last-member-query-interval 0-255

(on VLAN and physical, not Port Channel)

Enable IGMP snooping fast-leave for the selected VLAN.

[no] ip igmp snooping fast-leave [no] igmp fast-leave

Control the flooding behavior of unregistered multicast data packets.

[no] ip igmp snooping flood [no] igmp enable

Clear the tables managed by the IGMP snooping function

(no equivalent) clear igmpsnooping

migrating and understanding the differences between the ...€¦ · december 9, 2008 update...

Documents