HP 5920 User manual
HP 5920 & 5900 Switch Series
FC and FCoE
Configuration Guide
Part number: 5998-6630
Software version: Release 2416
Document version: 6W100-20150130
Legal and notice information
© Copyright 2015 Hewlett-Packard Development Company, L.P.
No part of this documentation may be reproduced or transmitted in any form or by any means without
prior written consent of Hewlett-Packard Development Company, L.P.
The information contained herein is subject to change without notice.
HEWLETT-PACKARD COMPANY MAKES NO WARRANTY OF ANY KIND WITH REGARD TO THIS
MATERIAL, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY
AND FITNESS FOR A PARTICULAR PURPOSE. Hewlett-Packard shall not be liable for errors contained
herein or for incidental or consequential damages in connection with the furnishing, performance, or
use of this material.
The only warranties for HP 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. HP shall not be liable for technical or editorial errors or omissions contained
herein.
i
Contents
FC and 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······························································································································································· 10
NPV mode······························································································································································ 10
Transit mode ·························································································································································· 11
Protocols and standards ················································································································································ 12
FC and FCoE configuration guidelines·····················································································································13
Configuring the switch to operate in advanced mode or expert mode ··································································· 13
Configuring an FCoE mode ·········································································································································· 13
FC and FCoE features supported in different FCoE modes ······················································································· 13
Configuring FC interfaces··········································································································································15
Changing the port type between a Layer 2 Ethernet interface and an FC interface·············································· 15
Configuring an FC interface ········································································································································· 15
Displaying and maintaining FC interfaces ·················································································································· 16
Configuring VFC interfaces ·······································································································································17
Configuring a VFC interface········································································································································· 17
Displaying and maintaining VFC interfaces················································································································ 18
Configuring FC link aggregation······························································································································19
Overview········································································································································································· 19
Basic concepts································································································································································ 19
FC aggregation group, member interface, and FC aggregate interface························································ 19
Member interface status········································································································································ 19
How FC link aggregation works ·································································································································· 19
FC aggregate interface operating mode ············································································································ 19
Choosing Selected member interfaces················································································································ 20
Speed of an FC aggregate interface ·················································································································· 20
Load sharing mode ··············································································································································· 20
FC link aggregation networking guidelines ················································································································ 21
FC link aggregation configuration task list·················································································································· 22
Configuring an FC aggregate interface ······················································································································ 22
Assigning an FC interface to an FC aggregation group ··························································································· 23
Enabling local-first load sharing··································································································································· 24
Displaying and maintaining FC link aggregation ······································································································ 24
FC link aggregation configuration example ··············································································································· 25
Network requirements··········································································································································· 25
Configuration procedure ······································································································································ 25
Verifying the configuration··································································································································· 26
ii
Enabling FCoE····························································································································································28
FCoE enabling configuration task list ·························································································································· 28
Enabling FCoE for a VLAN and mapping the VLAN to a VSAN ············································································· 28
Configuration restrictions and guidelines ··········································································································· 28
Configuration procedure ······································································································································ 29
Configuring an FC-MAP value······································································································································ 29
Configuring an FKA advertisement interval value ······································································································ 29
Configuring the FCF priority ········································································································································· 31
Configuring the system FCF priority ···················································································································· 31
Configuring the VFC interface FCF priority ········································································································ 31
Displaying and maintaining FCoE ······························································································································· 31
FCoE enabling configuration example ························································································································ 32
Network requirements··········································································································································· 32
Configuration procedure ······································································································································ 32
Configuring VSANs ···················································································································································37
VSAN fundamentals······················································································································································· 37
Creating a VSAN··························································································································································· 41
Configuring the trunk mode ·········································································································································· 41
Configuring an access VSAN······································································································································· 42
Assigning an interface to a VSAN as an access port······················································································· 42
Assigning interfaces to a VSAN as access ports in bulk ·················································································· 42
Configuring a trunk VSAN············································································································································ 43
Displaying and maintaining VSANs ···························································································································· 43
VSAN configuration examples ····································································································································· 43
VSAN configuration example by using FC interfaces······················································································· 43
VSAN configuration examples by using VFC interfaces··················································································· 46
Building a fabric·························································································································································50
Overview········································································································································································· 50
Principal switch selection······································································································································ 50
Domain ID assignment ·········································································································································· 51
FC address assignment········································································································································· 52
Fabric building configuration task list·························································································································· 52
Building a fabric statically···································································································································· 53
Building a fabric dynamically ······························································································································ 53
Enabling or disabling the fabric configuration feature ······························································································ 54
Setting a fabric name ···················································································································································· 54
Setting the switch priority ·············································································································································· 54
Configuring an allowed domain ID list························································································································ 55
Configuring a domain ID for a switch ························································································································· 56
Binding the WWN of an N_Port to an FC address··································································································· 56
Configuring fabric timers ·············································································································································· 57
Configuring fabric timers in system view············································································································ 57
Configuring fabric timers in VSAN view ············································································································ 57
Configuring fabric reconfiguration······························································································································· 58
Enabling the automatic reconfiguration feature································································································· 58
Manually initiating a fabric reconfiguration······································································································· 58
Configuring an FC interface to reject incoming RCF requests ·················································································· 59
Enabling SNMP notifications ········································································································································ 59
Configuring RSCN aggregation··································································································································· 59
RSCN······································································································································································ 59
RSCN aggregation················································································································································ 60
Configuration procedure ······································································································································ 60
Configuring and obtaining FC4 information of nodes ······························································································ 60
iii
Enabling SCSI-FCP information autodiscovery··································································································· 61
Configuring the default FC4 information for a node························································································· 61
Displaying and maintaining a fabric ··························································································································· 62
Fabric building configuration examples ······················································································································ 62
Static fabric building configuration example ····································································································· 62
Dynamic fabric building configuration example································································································ 65
Configuring FC routing and forwarding ··················································································································70
Overview········································································································································································· 70
Routing table and FIB table ·································································································································· 70
Direct routes ··························································································································································· 71
Static routes···························································································································································· 72
FSPF routes ····························································································································································· 72
Configuring static FC routes·········································································································································· 73
Configuration restrictions and guidelines ··········································································································· 73
Configuration procedure ······································································································································ 74
Configuring FSPF···························································································································································· 74
FSPF configuration task list ··································································································································· 74
Enabling FSPF ························································································································································ 74
Configuring the shortest SPF calculation interval ······························································································· 75
Configuring the minimum LSR arrival interval ···································································································· 75
Configuring the minimum LSR refresh interval···································································································· 75
Configuring the FSPF cost for an interface ········································································································· 76
Configuring the hello interval for an interface ··································································································· 76
Configuring the dead interval for an interface ·································································································· 77
Configuring the LSR retransmission interval for an interface ············································································ 77
Disabling FSPF for an interface···························································································································· 77
Configuring FSPF GR ············································································································································ 78
Displaying and maintaining FC routing and forwarding ·························································································· 78
FC routing configuration examples ······························································································································ 79
Static FC routing configuration example by using FC interfaces ····································································· 79
Static FC routing configuration example by using VFC interfaces··································································· 84
FSPF configuration example by using FC interfaces·························································································· 89
FSPF configuration example by using VFC interfaces ······················································································· 93
Configuring FC zones················································································································································97
Overview········································································································································································· 97
Zoning mode·························································································································································· 97
Zone database······················································································································································· 97
Pairwise ································································································································································100
Zone distribution in basic zoning mode ···········································································································100
Zone distribution in enhanced zoning mode ···································································································102
Zone merge in basic zoning mode ···················································································································103
Zone merge in enhanced zoning mode············································································································105
Access control······················································································································································106
FC zone configuration task list ···································································································································106
Configuring a zoning mode ·······································································································································107
Configuring the Pairwise feature································································································································108
Configuring zone aliases ············································································································································108
Configuring zones························································································································································109
Configuring zone sets··················································································································································109
Configuring the default zone policy···························································································································110
Configuring the zone distribution and merge type ··································································································110
Configuring a merge control mode····························································································································110
Enabling hard zoning··················································································································································111
iv
Activating a zone set and distributing it to the entire fabric ···················································································112
Triggering a complete distribution ·····························································································································112
Renaming zone aliases, zones, and zone sets·········································································································113
Copying zone aliases, zones, and zone sets ···········································································································113
Deleting the zone database········································································································································114
Enabling SNMP notifications ······································································································································114
Displaying and maintaining FC zones ······················································································································114
FC zone configuration example ·································································································································115
Network requirements·········································································································································115
Requirements analysis·········································································································································116
Configuration procedure ····································································································································116
Verifying the configuration·································································································································117
Configuring NPV····················································································································································· 120
Overview·······································································································································································120
Downlink interface and downlink······················································································································120
Uplink interface and uplink ································································································································121
Downlink-to-uplink interface mappings ·············································································································121
Disruptive load balancing ··································································································································121
NPV configuration task list ··········································································································································121
Configuring uplink interfaces and downlink interfaces····························································································122
Configuring uplink interfaces ·····························································································································122
Configuring downlink interfaces························································································································122
Configuring downlink-to-uplink interface mappings·································································································123
Initiating a disruptive load-balancing process ··········································································································123
Displaying and maintaining NPV·······························································································································123
NPV configuration examples ······································································································································124
NPV configuration example by using FC interfaces························································································124
NPV configuration example by using VFC interfaces ·····················································································127
Configuring FIP snooping······································································································································· 132
Overview·······································································································································································132
FIP snooping network diagram ··························································································································132
How FIP snooping works ····································································································································133
FIP snooping configuration task list····························································································································134
Enabling FIP snooping·················································································································································134
Configuring the operating mode of an Ethernet interface·······················································································134
Configuring the FC-MAP value ···································································································································135
Displaying and maintaining FIP snooping·················································································································135
FIP snooping configuration example··························································································································136
Network requirements·········································································································································136
Configuration procedure ····································································································································136
Verifying the configuration·································································································································138
Configuring FCS······················································································································································ 140
Overview·······································································································································································140
Starting a topology discovery·····································································································································142
Stopping a topology discovery···································································································································143
Displaying and maintaining FCS ·······························································································································143
FCS configuration example·········································································································································143
Network requirements·········································································································································143
Configuration procedure ····································································································································144
Verifying the configuration·································································································································144
Configuring FDMI···················································································································································· 147
Overview·······································································································································································147
v
Displaying and maintaining FDMI ·····························································································································148
Configuring FC ping··············································································································································· 150
Overview·······································································································································································150
Configuration procedure·············································································································································150
FC ping configuration examples ································································································································150
FC ping configuration example by using FC interfaces··················································································150
FC ping configuration examples by using VFC interfaces··············································································153
Configuring FC tracert············································································································································ 157
Overview·······································································································································································157
Configuration procedure·············································································································································158
FC tracert configuration examples ·····························································································································158
FC tracert configuration example by using FC interfaces···············································································158
FC tracert configuration example by using VFC interfaces ············································································163
Comprehensive FC and FCoE configuration examples························································································ 168
FCoE configuration example by using VFC interfaces (in standalone mode) ·······················································168
Network requirements·········································································································································168
Requirements analysis·········································································································································169
Configuration procedures···································································································································170
Verifying the configuration·································································································································179
FCoE configuration example by using VFC interfaces (in IRF mode) ·····································································180
Network requirements·········································································································································180
Requirements analysis·········································································································································181
Configuration procedures···································································································································182
Verifying the configuration·································································································································195
FC and FCoE configuration example by using FC interfaces and VFC interfaces (in standalone mode) ··········198
Network requirements·········································································································································198
Requirements analysis·········································································································································199
Configuration procedures···································································································································200
Verifying the configuration·································································································································208
FC and FCoE configuration example by using FC interfaces and VFC interfaces (in IRF mode)························210
Network requirements·········································································································································210
Requirements analysis·········································································································································211
Configuration procedures···································································································································212
Verifying the configuration·································································································································224
Appendixes······························································································································································ 228
Appendix A Fabric address assignment····················································································································228
Appendix B Well-known fabric addresses ················································································································228
Support and other resources ·································································································································· 230
Contacting HP ······························································································································································230
Subscription service ············································································································································230
Related information······················································································································································230
Documents····························································································································································230
Websites·······························································································································································230
Conventions ··································································································································································231
Index ········································································································································································ 233
1
FC and FCoE overview
Only the HP FlexFabric 5900CP-48XG-4QSFP+ Switches (JG838A) and HP StoreFabric
5900CP-48XG-4QSFP+8Gb FC B-fan Trays Converged Switches (E7W29A) support FC.
Fibre Channel (FC) is a data transmission protocol used in a storage area network (SAN). Fibre Channel
over Ethernet (FCoE) transports FC over Ethernet. The following sections describe FC and FCoE.
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.
A SAN 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 Fibre Channel (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.
•The point-to-point connection directly connects a server and a disk device.
•The arbitrated loop supports up to 126 devices.
•The switched fabric connects servers and disk devices to an FC switched fabric. 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 that 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—A domain 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.
•G_Port—Operates in auto mode to negotiate the operating mode with its peer.
{If the peer is an E_Port, the G_Port works as an E_Port.
{If the peer is an N_Port or NP_Port, the G_Port works as an F_Port.
4
{If both ends are G_Ports, they both work as E_Ports.
{If the peer is an F_Port, the negotiation fails.
•NP_Port—Connects to an F_Port on another FC switch. For more information about NP_Port, see
"Configuring NPV."
E_Ports connect FC switches to form a fabric, and F_Ports connect the nodes to FC switches in the fabric.
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 their directly-connected nodes.
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 for all nodes. For more information
about FC4 information, see "Configuring and obtaining FC4 information of nodes."
3. The server sends a name service query request to its access FC switch to obtain the list of disk
devices in the fabric and their WWNs and FC addresses.
4. The server sends an FC frame destined to the FC address to its access FC switch.
5. The access FC switch queries its FIB table and forwards the FC frame to the next-hop FC switch.
{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. You
can 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
5
of the network and offers more effective services for users. For more information about VSANs, see
"Configuring VSANs."
FC zone
The VSAN technique divides one physical SAN into multiple logical SANs. A VSAN, 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 switch (FCoE forwarder) 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
LAN SAN LAN SAN
Traditional network
Ethernet switch
Ethernet switch FC switch Ethernet
switch
FCF switch
FC switch
FC switch
Server Server
I/O consolidation with FCoE
Ethernet
FC
FCoE
6
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 FCoE-capable FCF switch. Then, the FCF switch
is connected to the LAN through an Ethernet interface and to the SAN through an FC interface. The
link between the server and the FCF switch can transmit both Ethernet packets and FC frames.
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 function 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:
•The VN interface of an ENode.
•The VFC interface of another FCF switch.
The virtual links provide a physical infrastructure for transmitting FC frames over Ethernet.
VFC interface
LAN SAN
Ethernet
switch
FCF switch
FC switch
ENode
Ethernet
FC
FCoE
FC interface
VN interface
Ethernet
interface
7
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, it is the FCoE MAC address of the switch (which can be displayed by using the
display fcoe command).
{For a node, it is the fabric provided MAC address (FPMA) of the node. As shown in Figure 7, an
FPMA is composed of 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 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:
Virtual link
ENode FCF
VN interface VFC interface
FC layer
Ethernet
layer
Ethernet
interface Ethernet
interface
FC layer
Ethernet
layer
8
{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.
•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
carried in the Discovery Solicitation matches the bound FCoE MAC address.
(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
−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 the establishment of the
virtual link.
{If they do not match, the FCF switch discards the FLOGI request.
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, it deletes the virtual link.
FCoE modes
The switch supports the following FCoE modes:
•FCF mode—A switch operating in this mode is called an FCF switch. Its VFC interfaces support E
mode (E_Port) and F mode (F_Port).
•NPV mode—A switch 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—A switch operating in this mode is called a Transit switch. Its Ethernet interfaces can
operate in ENode mode or FCF mode.
An FC or 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 FC or FCoE capabilities.
10
FCF mode
An FCF switch encapsulates FC frames in Ethernet frames and uses FCoE virtual links to simulate physical
FC links. In this way, an FCF switch provides standard FC switching capabilities and features on a
lossless Ethernet network.
Figure 10 FCF network diagram
In an FCoE environment as shown in Figure 10, an FCF switch can perform the following operations:
•Connect to an Ethernet switch through an Ethernet interface.
•Connect to an FC switch through an FC interface.
•Connect to an ENode or FCF switch through a VFC interface. In this case, an FCoE virtual link is
established between the Ethernet interfaces of the two devices. The FCoE virtual link provides
communication over a lossless Ethernet network. The peer end of the FCoE virtual link can be a VN
interface or a VFC interface.
Each FCF switch is assigned a domain ID. Each FC SAN supports a maximum number 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
VFC interface
LAN SAN
Ethernet
switch
FCF switch
FC switch
ENode
Ethernet
FC
FCoE
FC interface
VN interface
Ethernet
interface
11
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."
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.
12
Figure 14 Network diagram for NPV and Transit switches
The primary responsibilities of Transit switches are filtering and forwarding FCoE protocol packets. They
can recognize and control FCoE frames 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
FC and FCoE configuration guidelines
Configuring the switch to operate in advanced
mode or expert mode
The switch supports FC and FCoE only when it is operating in advanced mode or expert mode. For more
information about system operating modes, see Fundamentals Configuration Guide.
The switch supports FCoE over S-channel only when it is operating in expert mode. FCoE over S-Channel
allows you bind a VFC interface to an S-channel interface. For more information about binding a VFC
interface to an S-channel interface, see FC and FCoE Command Reference.
Configuring an FCoE mode
An FC and FCoE-capable switch can operate in FCF, NPV, Transit, or non-FCoE mode.
To configure a switch operating in one FCoE mode to operate in another FCoE mode, follow these steps:
1. Configure the switch to operate in 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, FC- and FCoE-related configurations in the
original FCoE mode are cleared.
To configure an FCoE mode for a switch:
Ste
p
Command
Remarks
1. Enter system view. system-view N/A
2. Configure an FCoE mode
for the switch.
fcoe-mode { fcf | npv |
transit }
By default, a switch operates in non-FCoE
mode.
Before configuring FC and FCoE features
on a switch, you must configure an FCoE
mode for the switch.
3. Display an FCoE mode of
the switch. display fcoe-mode Available in any view.
FC and 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 FC and FCoE features, as shown in Table 1.You can choose to configure different
features based on the FCoE mode of a switch.
Other manuals for 5920
18
This manual suits for next models
1
Table of contents
Other HP Network Router manuals
HP
HP MSR SERIES Installation manual
HP
HP 5920 User manual
HP
HP ProCurve MSM317 User manual
HP
HP FlexFabric 12900 series User manual
HP
HP 5500 HI Series User manual
HP
HP VSR1000 User manual
HP
HP Pavilion a6600 User manual
HP
HP A58x0AF Bck(pwr)-Frt(ports) Assembly instructions
HP
HP 6125XLG User manual
HP
HP 5830 series User manual
HP
HP MSR900-W User manual
HP
HP ProCurve Networking J8453A User manual
HP
HP SCSI-Fibre Channel Router User manual
HP
HP FlexFabric 12500E User manual
HP
HP J2600A User manual
HP
HP 6125XLG User manual
HP
HP 5900 User manual
HP
HP MSR930 Series User manual
HP
HP MSR930 Series Assembly instructions
HP
HP FlexNetwork 6616 User manual
