HPE FlexNetwork 10500 SERIES User manual

HPE FlexNetwork 10500 Switch Series
FCoE Configuration Guide
P
art number: 5200-1885a
Software
version: 10500-CMW710-R7557P01
Document version: 6W101-20171020

© Copyright 2017 Hewlett Packard Enterprise Development LP
The information contained herein is subject to change without notice. The only warranties for Hewlett Packard
Enterprise products and services are set forth in the express warranty statements accompanying such
products and services. Nothing herein should be construed as constituting an additional warranty. Hewlett
Packard Enterprise shall not be liable for technical or editorial errors or omissions contained herein.
Confidential computer software. Valid license from Hewlett Packard Enterprise required for possession, use, or
copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software
Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor’s
standard commercial license.
Links to third-party websites take you outside the Hewlett Packard Enterprise website. Hewlett Packard
Enterprise has no control over and is not responsible for information outside the Hewlett Packard Enterprise
website.
Acknowledgments
Intel®, Itanium®, Pentium®, Intel Inside®, and the Intel Inside logo are trademarks of Intel Corporation in the
United States and other countries.
Microsoft® and Windows® are trademarks of the Microsoft group of companies.
Adobe® and Acrobat® are trademarks of Adobe Systems Incorporated.
Java and Oracle are registered trademarks of Oracle and/or its affiliates.
UNIX® is a registered trademark of The Open Group.

i
Contents
FCoE overview······························································································1
Storage area network·········································································································································1
FC SAN······························································································································································1
FC protocol·························································································································································2
Basic concepts···········································································································································2
Communication flow···································································································································4
VSAN ·························································································································································4
FC zone······················································································································································5
FCoE··································································································································································5
Basic concepts···········································································································································6
How FCoE works ·······································································································································7
FCoE modes······················································································································································9
FCF mode··················································································································································9
NPV mode················································································································································10
Transit mode············································································································································11
Protocols and standards ··································································································································12
FCoE configuration restrictions and guidelines············································13
Configuring the switch to operate in advanced mode······················································································13
Configuring the FCoE mode·····························································································································13
FCoE features supported in different FCoE modes·························································································13
Configuring VFC interfaces··········································································15
Configuring a VFC interface·····························································································································15
Displaying and maintaining VFC interfaces ·····································································································16
Enabling FCoE ····························································································17
FCoE configuration task list·····························································································································17
Enabling FCoE for a VLAN and mapping the VLAN to a VSAN ······································································17
Configuration restrictions and guidelines·································································································17
Configuration procedure···························································································································17
Setting the FC-MAP value································································································································18
Setting the FKA advertisement interval value··································································································18
Configuration guidelines···························································································································18
Configuration procedure···························································································································19
Setting the FCF priority····································································································································19
Setting the system FCF priority················································································································20
Setting the VFC interface FCF priority·····································································································20
Displaying and maintaining FCoE····················································································································20
FCoE enabling configuration example·············································································································20
Network requirements······························································································································20
Configuration procedure···························································································································21
Configuring VSANs······················································································26
VSAN fundamentals·········································································································································26
Creating a VSAN··············································································································································27
Configuring a trunk VSAN································································································································27
Displaying and maintaining VSANs··················································································································28
VSAN configuration example···························································································································28
Network requirements······························································································································28
Configuration procedure···························································································································28
Verifying the configuration························································································································30
Building a fabric···························································································32
Overview··························································································································································32
Principal switch selection·························································································································32
Domain ID assignment·····························································································································33

ii
FC address assignment···························································································································34
Fabric building configuration task list···············································································································34
Building a fabric statically·························································································································34
Building a fabric dynamically····················································································································35
Enabling or disabling the fabric configuration feature······················································································35
Setting a fabric name·······································································································································36
Setting the switch priority·································································································································36
Configuring the allowed domain ID list·············································································································37
Configuring a domain ID for a switch···············································································································37
Configuring the persistent FC ID feature ·········································································································38
Setting the maximum number of logged-in nodes ···························································································38
Setting fabric timers ·········································································································································39
Setting fabric timers in system view·········································································································39
Setting fabric timers in VSAN view···········································································································39
Configuring the fabric reconfiguration feature··································································································40
Enabling the automatic reconfiguration feature························································································40
Manually initiating a fabric reconfiguration·······························································································41
Configuring a VFC interface to reject incoming RCF requests ········································································41
Enabling SNMP notifications····························································································································41
Configuring RSCN aggregation························································································································42
RSCN·······················································································································································42
RSCN aggregation···································································································································42
Configuration procedure···························································································································42
Configuring and obtaining FC4 information of nodes·······················································································43
Enabling SCSI-FCP information autodiscovery ·······················································································43
Configuring the default FC4 information for a node·················································································43
Configuring Smart SAN····································································································································44
Overview··················································································································································44
Configuration procedure···························································································································44
Displaying and maintaining a fabric ·················································································································45
Fabric building configuration examples············································································································45
Static fabric building configuration example·····························································································45
Dynamic fabric building configuration example························································································49
Configuring FC routing and forwarding ························································56
Overview··························································································································································56
Routing table and FIB table······················································································································56
Direct routes·············································································································································57
Static routes·············································································································································58
FSPF routes·············································································································································58
Configuring static FC routes·····························································································································59
Configuration restrictions and guidelines·································································································59
Configuration procedure···························································································································59
Configuring FSPF·············································································································································60
FSPF configuration task list ·····················································································································60
Enabling FSPF·········································································································································60
Setting the shortest SPF calculation interval····························································································60
Setting the minimum LSR arrival interval·································································································61
Setting the minimum LSR refresh interval································································································61
Setting the FSPF cost for an interface·····································································································61
Setting the hello interval for an interface··································································································62
Setting the dead interval for an interface ·································································································62
Setting the LSR retransmission interval for an interface··········································································62
Disabling FSPF for an interface···············································································································63
Configuring FSPF GR······························································································································63
Displaying and maintaining FC routing and forwarding ···················································································64
FC routing configuration examples ··················································································································64
Static FC routing configuration example··································································································64
FSPF configuration example····················································································································69
Configuring FC zones··················································································73
Overview··························································································································································73

iii
Zoning mode············································································································································73
Zone database·········································································································································73
Pairwise····················································································································································76
Zone distribution in basic zoning mode····································································································76
Zone distribution in enhanced zoning mode ····························································································78
Zone merge in basic zoning mode···········································································································79
Zone merge in enhanced zoning mode····································································································81
Access control··········································································································································82
FC zone configuration task list·························································································································82
Configuring a zoning mode······························································································································83
Configuring the Pairwise feature······················································································································84
Configuring zone aliases··································································································································84
Configuring zones············································································································································85
Configuring a peer zone···································································································································85
Configuring zone sets ······································································································································85
Configuring the default zone policy··················································································································86
Configuring the zone distribution and merge type ···························································································86
Configuring a merge control mode···················································································································87
Enabling hard zoning ·······································································································································87
Overview··················································································································································87
Configuration restrictions and guidelines·································································································88
Configuration procedure···························································································································88
Activating a zone set and distributing it to the entire fabric··············································································88
Triggering a complete distribution····················································································································89
Renaming zone aliases, zones, and zone sets································································································89
Copying zone aliases, zones, and zone sets···································································································90
Deleting the zone database ·····························································································································90
Enabling SNMP notifications····························································································································90
Displaying and maintaining FC zones··············································································································91
FC zone configuration example ·······················································································································91
Network requirements······························································································································91
Requirements analysis·····························································································································92
Configuration procedure···························································································································92
Verifying the configuration························································································································94
Configuring NPV··························································································96
Overview··························································································································································96
Downlink interface and downlink··············································································································96
Uplink interface and uplink·······················································································································96
Downlink-to-uplink interface mappings ····································································································97
Load balancing·········································································································································97
NPV configuration task list·······························································································································97
Configuring uplink interfaces and downlink interfaces·····················································································97
Configuring uplink interfaces····················································································································98
Configuring downlink interfaces···············································································································98
Configuring downlink-to-uplink interface mappings ·························································································98
Manually initiating a load-balancing process ···································································································99
Configuring automatic load balancing··············································································································99
Displaying and maintaining NPV······················································································································99
NPV configuration example····························································································································100
Network requirements····························································································································100
Configuration procedure·························································································································100
Verifying the configuration······················································································································102
Configuring FIP snooping ··········································································104
Overview························································································································································104
FIP snooping network diagram ··············································································································104
How FIP snooping works ·······················································································································104
FIP snooping configuration task list ···············································································································105
Enabling FIP snooping···································································································································106
Configuring the operating mode of an Ethernet interface ··············································································106
Setting the FC-MAP value······························································································································106

iv
Displaying and maintaining FIP snooping······································································································107
FIP snooping configuration example··············································································································107
Network requirements····························································································································107
Configuration procedure·························································································································107
Verifying the configuration······················································································································109
Configuring FCS························································································110
Overview························································································································································110
Starting a topology discovery·························································································································112
Stopping a topology discovery·······················································································································113
Displaying and maintaining FCS····················································································································113
FCS configuration example····························································································································113
Network requirements····························································································································113
Configuration procedure·························································································································114
Verifying the configuration······················································································································114
Configuring FDMI·······················································································117
Overview························································································································································117
Displaying and maintaining FDMI ··················································································································120
Configuring FC ping···················································································121
Overview························································································································································121
Configuration procedure·································································································································121
FC ping configuration example ······················································································································121
Network requirements····························································································································121
Configuration procedure·························································································································121
Verifying the configuration······················································································································123
Configuring FC tracert ···············································································125
Overview························································································································································125
Configuration procedure·································································································································126
FC tracert configuration example···················································································································126
Network requirements····························································································································126
Configuration procedure·························································································································126
Verifying the configuration······················································································································130
Comprehensive FCoE configuration examples··········································131
FCoE configuration example (in standalone mode)·······················································································131
Network requirements····························································································································131
Requirements analysis···························································································································132
Configuration restrictions and guidelines·······························································································133
Configuration procedures·······················································································································133
Verifying the configurations····················································································································142
FCoE configuration example (in IRF mode)···································································································143
Network requirements····························································································································143
Requirements analysis···························································································································144
Configuration restrictions and guidelines·······························································································145
Configuration prerequisites····················································································································145
Configuration procedures·······················································································································145
Verifying the configuration······················································································································157
Appendixes································································································161
Appendix A Fabric address assignment ········································································································161
Appendix B Well-known fabric addresses······································································································161
Document conventions and icons······························································163
Conventions···················································································································································163
Network topology icons··································································································································164
Support and other resources ·····································································165
Accessing Hewlett Packard Enterprise Support·····························································································165
Accessing updates·········································································································································165

v
Websites ················································································································································166
Customer self repair·······························································································································166
Remote support······································································································································166
Documentation feedback ·······················································································································166
Index··········································································································168

1
FCoE overview
Storage area network
A SAN is any high-performance network whose primary purpose is to enable storage devices to
communicate with computer systems and with each other.
ASAN enables the universal connectivity of servers and disk devices. Compared to the conventional
client/server computer system, a SAN delivers the following benefits:
•
Allows the servers to share data and directly access data created by one another without
having to copy it.
•
Improves storage scalability.
•
Centralizes the management of data backup, access, and security.
Most SANs use FC or Ethernet to interconnect devices. An FC SAN uses the FC protocol suite for
communication, and an Ethernet SAN uses the TCP/IP protocol suite for communication.
This document covers only the FC SAN.
FC SAN
Figure 1 shows three FC SAN networking methods. The first two networking methods are simple and
can connect only a limited number of devices.
•
Point-to-point connection—Directly connects a server and a disk device.
•
Arbitrated loop—Supports up to 126 devices.
•
Switched fabric—Connects servers and disk devices through FC switches. In a switched
fabric, the servers and disk devices are called "nodes." A fabric uses 24-bit addressing and
supports thousands of devices.

2
Figure 1 FC SAN networking
NOTE:
•
An FC SAN refers to a network that includes FC switches and nodes.
•A fabric refers to a transmission network that includes FC switches.
FC protocol
The servers, FC switches, and disk devices in an FC SAN must all support FC.
Basic concepts
WWN
The world wide name (WWN) is a 64-bit address. It identifies a fabric or an entity (such as an FC
switch, node, or port) in an FC SAN. The upper-layer protocol of FC uses WWNs for communication.
Each entity has a factory-assigned, globally unique WWN.
FC address
The FC protocol accesses communication entities in an FC SAN through FC addresses. An FC
address is also known as an "FC ID."
Disk
Server
1) Point-to-point
connection 2) Arbitrated loop
Disk
Server
Fabric
Disk
Server
FC switch
3) Switched fabric
Server
Disk
Disk

3
Figure 2 shows the structure of an FC address. The FC address is 24 bits long and contains the
following 8-bit fields:
•
Domain_ID—Adomain represents a switch and all N_Ports connected to the switch. For more
information about N_Ports, see "Port modes." A domain ID, which is in the range of 1 to 239,
uniquely identifies an FC switch. Different FC switches in the same fabric have different domain
IDs.
•
Area_ID—One or more N_Ports on the same node can be assigned to an area, which is
identified by an area ID.
•
Port_ID—The Port_ID field identifies an N_Port.
Figure 2 Structure of an FC address
An FC address can uniquely identify an N_Port on a node. Different N_Ports on the same node have
different FC addresses. FC switches use domain IDs to route messages between each other.
The FC protocol standardizes the FC address usage. For more information, see "Appendixes."
Port modes
In a switched fabric, nodes and FC switches communicate through interfaces operating in different
modes.
Figure 3 Port modes
A node supports the following port modes:
•
N_Port—Directly connects to a fabric.
•
NL_Port—Connects to a fabric through an arbitrated loop.
An FC switch provides the following port modes:
•
E_Port—Connects to an E_Port on another FC switch.
•
F_Port—Connects to an N_Port on a node or an NP_Port on another FC switch.
•
NP_Port—Connects to an F_Port on another FC switch. For more information about NP_Ports,
see "Configuring NPV."
E_Ports connect FC switches to form a fabric, and F_Ports connect the nodes to FC switches in the
fabric.
Domain_ID Area_ID Port_ID
FC_ID
0723 15
E_Port E_Port
F_Port
F_Port
F_Port
F_Port
N_Port
N_Port N_Port
N_Port
Server
Disk Disk
Disk
FC switch FC switch

4
Communication flow
FC switches provide data transmission services. Through FC switches, a server sends instructions
and data to disk devices and reads data from disk devices.
Figure 4 FC SAN communication model
The following takes a server accessing a disk device as an example to see how data communication
occurs in an FC SAN.
1. The server and the disk device send fabric login (FLOGI) packets to register with the FC
switches. Then, the FC switches assign FC addresses to each directly-connected node.
A FLOGI packet contains information that includes the port WWN, node WWN, and the
expected FC address.
2. The registered server and disk device send name service registration requests to their
respective access FC switches to register name service information, including FC4 information.
Finally, each FC switch in the fabric stores the name service information of all nodes. For more
information about FC4 information, see "Configuring and obtaining FC4 information of nodes."
3. To access a disk device, the server must obtain the list of disk devices in the fabric and their
WWNs and FC addresses. For this purpose, the server must send a name service query
request to its directly-connected FC switch.
4. After the server obtains the FC address of the disk device, the server can send FC frames
destined to the FC address to the FC switch nearby.
5. When the FC switch receives the FC frame from the server, it performs the following operations:
Queries its FIB table for a data forwarding path according to the destination FC address.
Forwards the FC frame to the next-hop FC switch.
6. The next-hop FC switch forwards the FC frame in the same way, until the FC switch at the last
hop forwards the FC frame to the destination disk device.
NOTE:
A
FIB table is generated by the FC switch through calculation based on the FC routing protocol or
configured static routes.
VSAN
In actual applications, the data is insecure if the data of all users is transmitted in the same FC SAN.
Youcan divide one physical FC SAN into multiple virtual storage area networks (VSANs). VSANs are
separated from one another and provide independent services. This enhances adaptability and
security of the network and offers more effective services for users. For more information about
VSANs, see "Configuring VSANs."
Server Disk
FC switch FC switch
Fabric

5
FC zone
The VSAN technique divides one physical SAN into multiple logical SANs. AVSAN, however, cannot
perform access control over the servers and disk devices (or the N_Ports) connected to a fabric.
N_Ports in the same VSAN can access one another only if these N_Ports register name services.
This creates data security risks.
Zoning can solve the preceding problem by dividing a VSAN into zones and adding N_Ports to
different zones for different purposes. N_Ports in different zones are separated to implement access
control.
For more information about FC zones, see "Configuring FC zones."
FCoE
A data center using the FC SAN technology typically includes separate local area networks (LANs)
and SANs. LANs carry traditional Ethernet/IP services, and SANs carry network storage services.
To provide services for LANs and use SANs for storage simultaneously in a traditional network, the
servers must use independent Ethernet adapters and FC adapters. In addition, the IP switches and
the FC switches are also independent and have independent network connections. Such a network
needs many switches, network adapters, and cables, and it brings high investments and
maintenance costs and low scalability.
FCoE was introduced to solve this problem. FCoE transports FC over Ethernet. In an FCoE solution:
•
The server uses an FCoE-capable Ethernet adapter.
•
The FCoE forwarder (FCF) switch integrates the functions of both the traditional IP switch and
FC switch.
FCoE reduces the number of network adapters, switches, and cables, and the network operation
and maintenance workload. In all, FCoE reduces the total cost.
Figure 5 FCoE for I/O consolidation
As shown in Figure 5:
•
In the traditional network, the server is connected to the LAN through an Ethernet interface and
to the SAN through an FC interface.
•
In the FCoE network, the server is connected to the LAN and SAN through one FCoE-capable
FCF switch. The link between the server and the FCF switch can transmit both Ethernet frames
and FC frames.
LAN SAN LAN SAN
Traditional network
Ethernet switch
Ethernet switch FC switch Ethernet switch
FCF switch
FC switch
FCF switch
Server Server
I/O consolidation with FCoE
Ethernet
FC
FCoE

6
Basic concepts
As shown in Figure 6, the link between the FCF switch and the ENode can receive and send both
Ethernet frames and FC frames. ENodes can transport FC over Ethernet. ENodes include servers
and disk devices.
Figure 6 FCoE network diagram
VFC interface and VN interface
A virtual fibre channel (VFC) interface is a logical interface manually created on an FCF switch to
simulate the functionality of a physical FC interface.
To use a VFC interface, bind it to a physical Ethernet interface.
You can connect either an ENode or an FCF switch to a VFC interface.
VFC interfaces support E mode, F mode (default), and NP mode.
The virtual node (VN) interface is a logical interface on an ENode to simulate the function of a
physical FC interface.
FIP protocol
FCoE initialization protocol (FIP) is an FCoE control protocol that establishes and maintains virtual
links.
FIP establishes a virtual link between the VFC interface of an FCF switch and either of the following:
•
A VN interface of an ENode.
•
A VFC interface of another FCF switch.
The virtual links provide a physical infrastructure for transmitting FC frames over Ethernet.
FCoE frames
To transmit an FC frame over Ethernet, FCoE encapsulates the FC frame in an FCoE frame by
adding an Ethernet frame header to the FC frame.
An FCoE frame uses Ethernet II encapsulation, which has the following fields in the Ethernet header:
•
EtherType 0x8906.
•
Destination MAC address/source MAC address—The definitions of this field are different for
switches and nodes.
For a switch, this field is the FCoE MAC address of the switch (which can be displayed by
using the display fcoe command).
LAN SAN
Ethernet
switch
FCF switch
FCF switch
Server
Ethernet
FCoE
Ethernet interface
VFC interface
VFC interface
VFC interface
Ethernet
interface
VN interface

7
For a node, this field is the fabric provided MAC address (FPMA) of the node. As shown in
Figure 7, an FPMA contains the following elements:
−The FC-MAP as the 24 most significant bits.
−The FC ID of the VN interface as the 24 least significant bits.
The FC-MAP takes the value of the switch FC-MAP, 0x0efc00 by default and configurable
by using the fcoe fcmap command.
Figure 7 FPMA composition
How FCoE works
This section describes how FCoE works on the FCF switch (rather than on the ENode).
Figure 8 Block diagrams of the ENode and the FCF switch
Procedure for receiving and sending FC frames over Ethernet
An FC frame is transmitted over Ethernet using the following workflow:
1. FIP establishes a virtual link between the VFC interface of the FCF switch and one of the
following interfaces:
A VN interface of an ENode.
A VFC interface of another FCF switch.
2. After the virtual link is established, the FCF switch encapsulates the FC frame in an FCoE frame
and sends it out.
3. After receiving the FCoE frame, the FCF switch removes its Ethernet header to send the
original FC frame to the upper layer for processing.
How FIP works
FIP establishes and maintains virtual links between a VFC interface and a VN interface or between
VFC interfaces.
FIP uses Discovery Solicitation packets and Discovery Advertisement packets. Discovery
Advertisement packets include the following types:
•
Solicited Discovery Advertisement—A reply for a Discovery Solicitation.
FC-MAP FC_ID
48 bits
MAC address
24 bits 24 bits
FC-MAP FC_ID
Virtual link
ENode FCF
VN interface VFC interface
FC layer
Ethernet
layer
Ethernet
interface Ethernet
interface
FC layer
Ethernet
layer

8
•
Unsolicited Discovery Advertisement—Periodically sent to advertise the presence of a
virtual link or maintain an existing virtual link.
The following example shows how a virtual link is established between an FCF switch and an
ENode.
Figure 9 FIP operation
As shown in Figure 9, the following workflow is used to establish a virtual link:
1. The ENode sends a Discovery Solicitation containing its FCoE MAC address.
2. After receiving the Discovery Solicitation, the FCF switch acts differently depending on whether
the receiving VFC interface is bound to an FCoE MAC address.
If it is not bound to an FCoE MAC address, the switch learns the FCoE MAC address and
replies with a solicited Discovery Advertisement. The fcf priority field of the solicited
Discovery Advertisement transports the FCF priority of the VFC interface.
If it is bound to an FCoE MAC address, the switch identifies whether the FCoE MAC
address in the Discovery Solicitation matches the bound FCoE MAC address.
−If they match, the switch replies with a solicited Discovery Advertisement, whose fcf
priority field carries the FCF priority of the VFC interface.
−If they do not match, the switch discards the Discovery Solicitation.
3. The FCF switch periodically sends unsolicited Discovery Advertisements, whose fcf priority
field carries the FCF priority of the system.
The sending interval is specified by using the fcoe fka-adv-period command and defaults to 8
seconds.
4. After receiving the Discovery Advertisements, the ENode determines the FCF switch with the
highest priority according to the fcf priority field. Then, the ENode sends a FLOGI request to
that switch for login.
5. After receiving the FLOGI request, the FCF switch identifies whether the source MAC address
matches its learned or bound FCoE MAC address.
If they match, the FCF switch sends a FLOGI LS_ACC, which indicates that the
establishment of the virtual link is completed.
If they do not match, the FCF switch discards the FLOGI request.
(1) Send Discovery Solicitation
Learn FCoE MAC address
FCF ENode
(2) Send solicited Discovery
Advertisement
(3) Send solicited Discovery
Advertisements periodically
(4) Send FLOGI request
Check FCoE MAC address
(5) Send FLOGI LS_ACC
(6) Send solicited Discovery
Advertisements periodically

9
6. The FCF switch also periodically sends unsolicited Discovery Advertisements to maintain
established virtual links. If the ENode fails to receive an unsolicited Discovery Advertisement
within a period 2.5 times the FKA advertisement interval, it deletes the virtual link.
FCoE modes
The switch supports the following FCoE modes:
•
FCF mode—Aswitch operating in this mode is called an FCF switch. Its VFC interfaces support
E mode (E_Port) and F mode (F_Port).
•
NPV mode—Aswitch operating in this mode is called an N Port Virtualization (NPV) switch. Its
VFC interfaces support F mode (F_Port) and NP mode (NP_Port).
•
Transit mode—Aswitch operating in this mode is called a Transit switch. Its Ethernet
interfaces can operate in ENode mode or FCF mode.
An FCoE-capable switch can operate in the following modes:
•
FCF mode—When the switch operates in this mode, it can perform one of the following
operations:
Connect to the E_Port on another FCF switch through its E_Port.
Connect to the N_Port on a node or the NP_Port on an NPV switch through its F_Port.
•
NPV mode—When the switch operates in this mode, it can perform one of the following
operations:
Connect to the N_Port on a node through its F_Port.
Connect to the F_Port on an FCF switch through its NP_Port.
•
Transit mode—When the switch operates in this mode, you can perform one of the following
tasks:
Configure an Ethernet interface to operate in ENode mode, so that the Ethernet interface
can receive traffic from only an ENode.
Configure an Ethernet interface to operate in FCF mode, so that the Ethernet interface can
receive traffic from only an FCF switch.
•
Non-FCoE mode—When the switch operates in this mode, it is a standard switch and does not
provide any FCoE capabilities.
FCF mode
An FCF switch encapsulates FC frames in Ethernet frames and uses FCoE virtual links to simulate
physical FC links. An FCF switch provides the FC switch features on a lossless Ethernet network.

10
Figure 10 FCF network diagram
In an FCoE environment as shown in Figure 10, FCF switches communicate with the ENode over a
lossless Ethernet network. The end of an FCoE virtual link on an FCF switch is a VFC interface. The
peer end of an FCoE virtual link can be a VN interface on an ENode or a VFC interface on another
FCF switch.
Like an FC switch, each FCF switch is assigned a domain ID. Each FC SAN supports a maximum of
239 domain IDs, so an FC SAN cannot have more than 239 switches.
NPV mode
An FC SAN needs a large number of edge switches that are connected directly to nodes. NPV
switches are developed to expand the number of switches in an FC SAN.
Figure 11 NPV network diagram
As shown in Figure 11, the NPV switch resides between nodes and the core switch on the edge of
the fabric. The core switch is a switch operating in FCF mode. The NPV switch is connected to the
nodes through its F_Ports and to the core switch through its NP_Port. The NPV switch forwards
traffic from its connected nodes to the core switch.
The NPV switch appears as an FCF switch to nodes and as a node to the core switch.
For more information about NPV, see "Configuring NPV."
LAN SAN
Ethernet
switch
FCF switch
FCF switch
Server
Ethernet
FCoE
Ethernet interface
VFC interface
VFC interface
VFC interface
Ethernet
interface
VN interface
NP_Port F_Port
F_Port
F_Port
N_Port
N_Port
Node
Node
Core switch
NPV switch
Fabric

11
Transit mode
FCoE supports FC SANs built on lossless Ethernet networks, and allows Transit switches to be
added between FCF switches and ENodes. Figure 12 shows a scenario where ENodes are
connected to FCF switches through a Transit switch.
Figure 12 Transit network diagram
Ethernet interfaces on a Transit switch can operate in ENode mode or FCF mode.
•
An Ethernet interface connected to an ENode must be configured to operate in ENode mode.
•
An Ethernet interface connected to an FCF switch must be configured to operate in FCF mode.
When Transit switches are interconnected, you must configure Ethernet interfaces to operate in the
correct modes. As shown in Figure 13, ENode 2 can register with only FCF switch 2. To register
ENode 2 with FCF switch 1, you must swap the operating modes of the Ethernet interfaces that
connect the two Transit switches.
Figure 13 Transit cascading network diagram
Figure 14 shows a network scenario where both Transit and NPV switches are present.
Figure 14 Network diagram for NPV and Transit switches
FCF
mode
ENode
mode
ENode
mode
FCF switch
Transit switch
Fabric
ENode
FCF switch
FCF
mode
FCF
mode
ENode
mode
ENode
mode
FCF switch 2
Transit switch 1
Fabric
ENode 2
FCF switch 1
FCF
mode
ENode 1
ENode
mode
Transit switch 2
FCF
mode
FCF
mode
ENode
mode
ENode
mode
FCF switch
Transit switch
Fabric
ENode
FCF switch
NPV switch

12
The primary responsibilities of Transit switches are filtering and forwarding FCoE protocol packets.
They can recognize and control FCoE packets as compared to standard Ethernet switches. However,
they do not provide FCoE traffic processing capabilities as complex as FCF switches or NPV
switches.
Protocols and standards
•
FC-FS-3, Fibre Channel - Framing and Signaling - 3
•
FC-SW-5, Fibre Channel - Switch Fabric - 5
•
FC-LS-2, Fibre Channel - Link Services - 2
•
FC-GS-6, Fibre Channel - Generic Services - 6
•
FC-BB-5, Fibre Channel - Back Bone – 5

13
FCoE configuration restrictions and
guidelines
Only the following interface modules support FCoE:
•
EC interface modules.
•
SE interface modules:
LSU1CGC2SE0 (JG916A).
LSUM2GP44TSSE0 (JH191A, JH199A).
LSUM2GT48SE0 (JH192A, JH200A).
•
SF interface modules.
•
SG interface modules.
Configuring the switch to operate in advanced
mode
The switch supports FCoE only when it is operating in advanced mode. For more information about
system operating modes, see Fundamentals Configuration Guide.
Configuring the FCoE mode
An FCoE-capable switch can operate in the FCF, NPV, Transit, or non-FCoE mode.
To configure a switch operating in an FCoE mode to operate in another FCoE mode, follow these
steps:
1. Configure the switch to operate in the non-FCoE mode.
2. Configure the switch to operate in the target FCoE mode.
After you configure the switch to operate in non-FCoE mode, all FCoE-related settings in the original
FCoE mode except VFC interfaces are cleared.
To configure an FCoE mode for a switch:
Step
Command
Remarks
1. Enter system view. system-view N/A
2. Configure an FCoE mode
for the switch. fcoe-mode { fcf | fcf-npv |
npv | transit }
By default, a switch operates in non-FCoE
mode.
The fcf-npv keyword is not supported in
the current software version.
3. Display the FCoE mode
of the switch. display fcoe-mode Available in any view.
FCoE features supported in different FCoE modes
The switch supports the following FCoE modes: FCF mode, NPV mode, and Transit mode. Each
mode supports different FCoE features, as shown in Table 1. You can choose to configure different
features based on the FCoE mode of a switch.