FCoE Slides Only

Fibre Channel over Ethernet:
An Introduction
Session ID: SSA01
Peter Mescher
STG Solution Central Team, RTP, NC, USA
2008 IBM Corporation
New Enterprise Forum: Information Infrastructure - IBM System Storage and Storage Networking Technical Symposium
Disclaimers
NOTES:
All statements regarding IBM's future direction and intent are subject to change or withdrawal without notice, and represent goals and
objectives only.
Information about non-IBM products is obtained from the manufacturers of those products or their published announcements. IBM has not
tested those products and cannot confirm the performance, compatibility, or any other claims related to non-IBM products. Questions on the
capabilities of non-IBM products should be addressed to the suppliers of those products.
Prices are suggested US list prices and are subject to change without notice. Starting price may not include a hard drive, operating system
or other features. Contact your IBM representative or Business Partner for the most current pricing in your geography.
Any proposed use of claims in this presentation outside of the United States must be reviewed by local IBM country counsel prior to such
use.
The information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these
changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the
program(s) described in this publication at any time without notice.
Any references in this information to non-IBM Web sites are provided for convenience only and do not in any manner serve as an
endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web
sites is at your own risk.
IBM makes no representation or warranty regarding third-party products or services including those designated as ServerProven,
ClusterProven or BladeCenter Interoperability Program products. Support for these third-party (non-IBM) products is provided by non-IBM
Manufacturers.
IBM may have patents or pending patent applications covering subject matter in this document. The furnishing of this document does not
give you any license to these patents. Send license inquires, in writing, to IBM Director of Licensing, IBM Corporation, New Castle Drive,
Armonk, NY 10504-1785 USA.
17-Aug-08
Agenda
Overview of Fibre Channel over Ethernet (FCoE) as a
product
Protocol Summary
17-Aug-08
What Is Fibre Channel over Ethernet?

A direct mapping of Fibre Channel onto Ethernet
Aims to reduce cost through sharing of Ethernet
infrastructure
New standard specified by ANSI T11 Committee
within FC-BB-5
Backed by virtually entire storage networking industry,
including IBM, Brocade, Cisco, QLogic, HP, and Intel
17-Aug-08
General Characteristics
Simple No complicated flow control or frame loss
detection
Entire standard 24 pages
Viable alternative to native Fibre Channel

Generally intended for, but not limited to, 10Gb
Ethernet
17-Aug-08
Basic FCoE Installation
17-Aug-08
Why use FCoE?

Large hosts generally use two networks right now:
Ethernet and Fibre Channel
FCoE eliminates need for additional Host Adapters
Reduces Cost
Reduces slot and bus space usage
Very helpful for Blades
17-Aug-08
FCoE vs. FCIP/iFCP

Not really equivalent
FCoE Direct replacement for FC links
FCIP/iFCP Generally used for Distance Extension
FCoE unsuitable for long distances or complex
networks
No FCIP or iFCP storage devices or HBAs
17-Aug-08
FCoE vs. iSCSI

FCoE
iSCSI
Local-area, lossless links no

routing allowed
Allows many hops, lossy

connections, high latency
Simple encapsulation of Fibre

Channel
Substantial complexity on top

of TCP very different from
FCP
Low overhead 1% over

regular FC
Overhead varies typically

higher.
Fibre Channel wellunderstood by storage

administrators
TCP/IP well-understood by
just about everybody else
Substantial frame loss

catastrophic
Frame loss merely painful

17-Aug-08
FCoE vs. iSCSI long-term

No overwhelming advantages for one vs. other
FCoE appropriate for existing SAN installs
More SCSI-like
No complex, gateway for non-iSCSI-native systems
iSCSI serious choice for new solutions

Takes advantage of substantial existing IP infrastructure
and knowledge
Lossless Network needed for FCoE helpful to both

iSCSI likely will win, in the end
10
17-Aug-08
Software vs. Hardware Implementations

FCoE is available as a software driver for most
operating systems
Primary use is proof-of-concept and interoperability test
Virtually all production deployments expected to be

hardware based
New Converged Network Adapters (CNA)
In reality, FC HBAs with an Ethernet MAC layer
11
17-Aug-08
FCoE Disadvantages
No flow control (not even buffer credits)
Relies on one or more optional Ethernet extensions
802.3-2005 PAUSE mechanism
802.1Qau Congestion Management
Required to deal with potential FC congestion, even if

Ethernet uncongested
Assumes high-quality network

Lossless Ethernet network required
12
17-Aug-08
Possible Industry Deployment

FCoE intended for 10Gb Ethernet links

1Gb functional, not recommended
1. Blades with Ethernet/FCoE splitter on in-Chassis

switch
2. Edge switches / Director blades
3. Entire Directors / Core Ethernet switches (same
thing?)
4. Storage
13
17-Aug-08
Summary of FCoE as a Product

FCoE, in summary:
A new standard designed to converge Fibre Channel
SANs and Ethernet networks
Simple in concept and design
Will be initially used with smaller servers
Fundamentally different from iFCP and FC/IP
In competition with iSCSI
Questions? (Information on protocol details to follow)

14
17-Aug-08
Terms
FCoE Mapper (FCM) Provides translation between
Ethernet and Fibre Channel
Present in NICs and switches
FCoE Forwarder (FCF) Ethernet / Fibre Channel

switch
Also provides FCoE discovery and login services
Does not need actual Fibre Channel ports
FCoE ENode (ENode) Ethernet port w/ FCoE

abilities (software or hardware)
15
17-Aug-08
Terms (cont.)
FC-MAP Fabric ID
Usually 0E:FC:0z (z = a Fabric ID number, which
defaults to 0.)
Used for first three bytes of Fabric-Assigned MAC
Addresses
16
17-Aug-08
FCoE Standard
Listed in ANSI T11, FC-BB-5, Chapter 7
Two protocols in one standard:
FCoE The encapsulation standard
FCoE Initialization Protocol (FIP) Protocol to provide
device discovery and login services
Use different EtherTypes
Facilitates FIP snooping by non FCF switches
17
17-Aug-08
FCoE and the Protocol Stack
18
17-Aug-08
FCoE Frame Format
Other than normal Ethernet headers, no per-frame

overhead
Mini-Jumbo Ethernet frames strongly suggested
Not a difficult requirement; virtually all do
19
17-Aug-08
FCoE Frame Forwarding

Relies on Ethernet Spanning Tree or other forwarding
scheme
No built-in routing such as FSPF
Load balancing generally poor
20
17-Aug-08
More-Complex FCoE Topology
21
17-Aug-08
FCoE Network Without Much FC
22
17-Aug-08
Addressing
Two options
Server Provided MAC Address (SPMA)
Typical Ethernet standard globally unique address
Fabric Provided MAC Address (FPMA)

Format XX:XX:XX:YY:YY:YY
XX:XX:XX = FC-MAP
YY:YY:YY = FCID
No relation to WWPN of adapter
23
17-Aug-08
Addressing (cont.)
Multiple MACs per adapter expected
One for regular Ethernet traffic (i.e. TCP/IP)
ENode MAC Address
One for each FCoE address

VN_Port MAC Address
NPIV supported
24
17-Aug-08
FCoE Discovery
Utilizes special Fabric Initialization Protocol (FIP)

frames
Separate from regular FCoE frames
Used for FLOGI/FDISC, LOGO, ELP and FCoE
discovery
Source MAC probably burned-in MAC Address
25
17-Aug-08
FCoE Discovery and FC Login Process

1. Send multi-cast Ethernet frame to All-FCF-MACs
standard address (or specific FCF) with Discovery
Solicitation payload.
Contains:
26
MAC Address used to receive response

The hosts name
Maximum Receive Size
If an FCF itself, include FC-MAP (if using FPMA)
17-Aug-08
FCoE Discovery and FC Login Process (cont.)

2. FCF responds with Discovery Advertisement
Advertisement contains:
Priority 1-byte value used to determine which FCFMAC to use, if multiple respond
MAC Address of the FCF-MAC
If using FPMA, the FC-MAP of the FCF
Name of the Switch
Name of the Fabric
27
17-Aug-08
FCoE Discovery and FC Login Process (cont.)

3. ENode sends FIP FLOGI
Just like FC FLOGI, only in a FIP frame
Returned FCID also used to build FPMA MAC
Address
For FCFs, FIP ELP sent instead
For NPIV, FIP FDISC is used

Works just like FC counterpart
4. The FCF responds with a FIP LS_ACC (or

ELP_SW_ACC)
28
17-Aug-08
Summary
FCoE has two parts

FCoE frames simple Ethernet frame plus Fibre
Channel frame.
FIP protocol handles device discovery, fabric login
functions, and address assignment
29
17-Aug-08

FCoE Slides Only

Загружено:

Сведения о документе

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

FCoE Slides Only

Загружено:

Авторское право:

Доступные форматы

Fibre Channel over Ethernet:

2008 IBM Corporation

2008 IBM Corporation

2008 IBM Corporation

What Is Fibre Channel over Ethernet?

2008 IBM Corporation

Viable alternative to native Fibre Channel

2008 IBM Corporation

Basic FCoE Installation

2008 IBM Corporation

Why use FCoE?

2008 IBM Corporation

FCoE vs. FCIP/iFCP

No FCIP or iFCP storage devices or HBAs

2008 IBM Corporation

FCoE vs. iSCSI

Local-area, lossless links no

Allows many hops, lossy

Simple encapsulation of Fibre

Substantial complexity on top

Low overhead 1% over

Overhead varies typically

Fibre Channel wellunderstood by storage

Substantial frame loss

Frame loss merely painful

2008 IBM Corporation

FCoE vs. iSCSI long-term

iSCSI serious choice for new solutions

Lossless Network needed for FCoE helpful to both

2008 IBM Corporation

Software vs. Hardware Implementations

Virtually all production deployments expected to be

2008 IBM Corporation

Required to deal with potential FC congestion, even if

Assumes high-quality network

2008 IBM Corporation

Possible Industry Deployment

FCoE intended for 10Gb Ethernet links

1. Blades with Ethernet/FCoE splitter on in-Chassis

2008 IBM Corporation

Summary of FCoE as a Product

Questions? (Information on protocol details to follow)

2008 IBM Corporation

FCoE Forwarder (FCF) Ethernet / Fibre Channel

FCoE ENode (ENode) Ethernet port w/ FCoE

2008 IBM Corporation

2008 IBM Corporation

2008 IBM Corporation

FCoE and the Protocol Stack

2008 IBM Corporation

FCoE Frame Format

Other than normal Ethernet headers, no per-frame

2008 IBM Corporation

FCoE Frame Forwarding

2008 IBM Corporation

More-Complex FCoE Topology

2008 IBM Corporation

FCoE Network Without Much FC

2008 IBM Corporation

Fabric Provided MAC Address (FPMA)

No relation to WWPN of adapter

2008 IBM Corporation

One for each FCoE address

2008 IBM Corporation