Cisco Nexus 5000 Series NX-OS Fibre Channel over ... › ... › 521n11 › b_5k_FCoE_Config_521N11.pdfCisco Nexus 5000 Series NX-OS Fibre Channel over Ethernet Configuration Guide,

Cisco Nexus 5000 Series NX-OS Fibre Channel over EthernetConfiguration Guide, Release 5.2(1)N1(1)First Published: 2012-07-02

Last Modified: 2012-07-02

Americas HeadquartersCisco Systems, Inc.170 West Tasman DriveSan Jose, CA 95134-1706USAhttp://www.cisco.comTel: 408 526-4000 800 553-NETS (6387)Fax: 408 527-0883

Text Part Number: OL-27582-01

THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS,INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND,EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS.

THE SOFTWARE LICENSE AND LIMITEDWARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT SHIPPED WITHTHE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE OR LIMITED WARRANTY,CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY.

The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCB's public domain versionof the UNIX operating system. All rights reserved. Copyright © 1981, Regents of the University of California.

NOTWITHSTANDINGANYOTHERWARRANTYHEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED “AS IS"WITH ALL FAULTS.CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THOSE OFMERCHANTABILITY, FITNESS FORA PARTICULAR PURPOSEANDNONINFRINGEMENTORARISING FROMACOURSEOFDEALING, USAGE, OR TRADE PRACTICE.

IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING, WITHOUTLIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO OR ITS SUPPLIERSHAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, networktopology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentionaland coincidental.

Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: http://www.cisco.com/go/trademarks. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnershiprelationship between Cisco and any other company. (1110R)

© 2012 Cisco Systems, Inc. All rights reserved.

http://www.cisco.com/go/trademarks

http://www.cisco.com/go/trademarks

C O N T E N T S

P r e f a c e Preface vii

Audience vii

Document Conventions vii

Documentation Feedback ix

Obtaining Documentation and Submitting a Service Request ix

C H A P T E R 1 New and Changed Information for this Release 1

New and Changed Information for this Release 1

C H A P T E R 2 Overview 3

Overview 3

FCoE Initiation Protocol 4

FIP Virtual Link Instantiation 4

FCoE Frame Format 4

VLAN Tagging for FCoE Frames 4

FIP Ethernet Frame Format 5

Pre-FIP Virtual Link Instantiation 5

Data Center Bridging Exchange Protocol 6

DCBX Feature Negotiation 6

Lossless Ethernet 7

Logical Link Up/Down 7

Converged Network Adapters 8

C H A P T E R 3 Configuring FCoE 9

Licensing Requirements for FCoE 9

FCoE Topologies 10

Directly Connected CNA Topology 10

Cisco Nexus 5000 Series NX-OS Fibre Channel over Ethernet Configuration Guide, Release 5.2(1)N1(1) OL-27582-01 iii

Remotely Connected CNA Topology 11

FCoE Best Practices 12

Directly Connected CNA Best Practice 12

Remotely Connected CNA Best Practice 14

Guidelines and Limitations 15

Configuring FCoE 16

Configuring QoS 16

Enabling FCoE 16

Disabling FCoE 17

Disabling LAN Traffic on an FCoE Link 18

Configuring the FC-Map 19

Configuring the Fabric Priority 19

Configuring Jumbo MTU 20

Setting the Advertisment Interval 20

Verifying the FCoE Configuration 21

C H A P T E R 4 Configuring FCoE VLANs and Virtual Interfaces 23

Information About Virtual Interfaces 23

Guidelines and Limitations for FCoE VLANs and Virtual Interfaces 24

Configuring Virtual Interfaces 25

Mapping a VSAN to a VLAN 25

Creating a Virtual Fibre Channel Interface 26

Configuring vFC Interface 27

Associating a Virtual Fibre Channel Interface to a VSAN 28

Creating an Implicit Virtual Fibre Channel Port Channel Interface 29

Configuring virtual Fibre Channel – Port Channel Interface 30

Verifying the Virtual Interface 31

Mapping VSANs to VLANs Example Configuration 33

FCoE over Enhanced vPC 34

Configuring FCoE over Enhanced vPC 35

SAN Boot with vPC 37

SAN Boot with vPC Configuration Example 37

C H A P T E R 5 Configuring Cisco Adapter FEX with FCoE 39

Overview 39

Cisco Nexus 5000 Series NX-OS Fibre Channel over Ethernet Configuration Guide, Release 5.2(1)N1(1)iv OL-27582-01

Contents

Guidelines and Limitations 39

Configuring Cisco Adapter FEX with FCoE 40

Cisco Nexus 5000 Series NX-OS Fibre Channel over Ethernet Configuration Guide, Release 5.2(1)N1(1) OL-27582-01 v

Contents

Cisco Nexus 5000 Series NX-OS Fibre Channel over Ethernet Configuration Guide, Release 5.2(1)N1(1)vi OL-27582-01

Contents

Preface

The preface contains the following sections:

• Audience, page vii

• Document Conventions, page vii

• Documentation Feedback, page ix

• Obtaining Documentation and Submitting a Service Request, page ix

AudienceThis publication is for network administrators who configure and maintain Cisco Nexus devices and CiscoNexus 2000 Series Fabric Extenders.

Document Conventions

As part of our constant endeavor to remodel our documents to meet our customers' requirements, we havemodified the manner in which we document configuration tasks. As a result of this, you may find adeviation in the style used to describe these tasks, with the newly included sections of the documentfollowing the new format.

Note

Command descriptions use the following conventions:

DescriptionConvention

Bold text indicates the commands and keywords that you enter literallyas shown.

bold

Italic text indicates arguments for which the user supplies the values.Italic

Square brackets enclose an optional element (keyword or argument).[x]

Cisco Nexus 5000 Series NX-OS Fibre Channel over Ethernet Configuration Guide, Release 5.2(1)N1(1) OL-27582-01 vii


Square brackets enclosing keywords or arguments separated by a verticalbar indicate an optional choice.

[x | y]

Braces enclosing keywords or arguments separated by a vertical barindicate a required choice.

{x | y}

Nested set of square brackets or braces indicate optional or requiredchoices within optional or required elements. Braces and a vertical barwithin square brackets indicate a required choice within an optionalelement.

[x {y | z}]

Indicates a variable for which you supply values, in context where italicscannot be used.

variable

A nonquoted set of characters. Do not use quotation marks around thestring or the string will include the quotation marks.

string

Examples use the following conventions:


Terminal sessions and information the switch displays are in screen font.screen font

Information you must enter is in boldface screen font.boldface screen font

Arguments for which you supply values are in italic screen font.italic screen font

Nonprinting characters, such as passwords, are in angle brackets.< >

Default responses to system prompts are in square brackets.[ ]

An exclamation point (!) or a pound sign (#) at the beginning of a lineof code indicates a comment line.

!, #

This document uses the following conventions:

Means reader take note. Notes contain helpful suggestions or references to material not covered in themanual.

Note

Means reader be careful. In this situation, you might do something that could result in equipment damageor loss of data.

Caution

Cisco Nexus 5000 Series NX-OS Fibre Channel over Ethernet Configuration Guide, Release 5.2(1)N1(1)viii OL-27582-01

PrefaceDocument Conventions

Documentation FeedbackTo provide technical feedback on this document, or to report an error or omission, please send your commentsto: [email protected].

We appreciate your feedback.

Obtaining Documentation and Submitting a Service RequestFor information on obtaining documentation, using the Cisco Bug Search Tool (BST), submitting a servicerequest, and gathering additional information, see What's New in Cisco Product Documentation.

To receive new and revised Cisco technical content directly to your desktop, you can subscribe to the What'sNew in Cisco Product Documentation RSS feed. RSS feeds are a free service.

Cisco Nexus 5000 Series NX-OS Fibre Channel over Ethernet Configuration Guide, Release 5.2(1)N1(1) OL-27582-01 ix

PrefaceDocumentation Feedback

mailto:[email protected]

http://www.cisco.com/c/en/us/td/docs/general/whatsnew/whatsnew.html

http://www.cisco.com/assets/cdc_content_elements/rss/whats_new/whatsnew_rss_feed.xml

http://www.cisco.com/assets/cdc_content_elements/rss/whats_new/whatsnew_rss_feed.xml

Cisco Nexus 5000 Series NX-OS Fibre Channel over Ethernet Configuration Guide, Release 5.2(1)N1(1)x OL-27582-01

PrefaceObtaining Documentation and Submitting a Service Request

C H A P T E R 1New and Changed Information for this Release

There are no new or changed features in this release.

• New and Changed Information for this Release, page 1

New and Changed Information for this ReleaseThe following table provides an overview of the significant changes made to this configuration guide. Thetable does not provide an exhaustive list of all changes made to this guide or all new features in a particularrelease.

Table 1: New and Changed Information

Where DocumentedReleaseDescriptionFeature

Basic DeviceManagement

7.3(0)N1(1)Added the support forthe EXEC bannerfeature.

EXEC banner

Basic DeviceManagement

7.3(0)N1(1)Added support for 63characters for hostnameand switchname.

63 character hostnameand switchname

Cisco Nexus 5000 Series NX-OS Fibre Channel over Ethernet Configuration Guide, Release 5.2(1)N1(1) OL-27582-01 1

Cisco Nexus 5000 Series NX-OS Fibre Channel over Ethernet Configuration Guide, Release 5.2(1)N1(1)2 OL-27582-01

New and Changed Information for this ReleaseNew and Changed Information for this Release

C H A P T E R 2Overview

This chapter contains the following sections:

• Overview, page 3

• FCoE Initiation Protocol, page 4

• Data Center Bridging Exchange Protocol, page 6

• Lossless Ethernet, page 7

OverviewFibre Channel over Ethernet (FCoE) allows Fibre Channel traffic to be encapsulated over a physical Ethernetlink. FCoE frames use a unique EtherType so that FCoE traffic and standard Ethernet traffic can be carriedon the same link.

Classic Ethernet is a best-effort protocol; in the event of congestion, Ethernet will discard packets, relying onhigher level protocols to provide retransmission and other reliability mechanisms. Fibre Channel traffic requiresa lossless transport layer; as a data storage protocol, it is unacceptable to lose a single data packet. NativeFibre Channel implements a lossless service at the transport layer using a buffer-to-buffer credit system.

For FCoE traffic, the Ethernet link must provide a lossless service. Ethernet links on Cisco Nexus devicesprovide two mechanisms to ensure lossless transport for FCoE traffic: link-level flow control (LL-FC) andpriority flow control (PFC).

IEEE 802.3x link-level flow control allows a congested receiver to signal the far end to pause the datatransmission for a short period of time. The pause functionality is applied to all the traffic on the link.

The priority flow control feature applies pause functionality to specific classes of traffic on the Ethernet link.For example, PFC can provide lossless service for the FCoE traffic and best-effort service for the standardEthernet traffic. PFC can provide different levels of service to specific classes of Ethernet traffic (using IEEE802.1p traffic classes).

Cisco Nexus switches support T11-compliant FCoE on all 10-Gigabit Ethernet interfaces.


FCoE Initiation ProtocolThe FCoE Initialization Protocol (FIP) allows the switch to discover and initialize FCoE-capable entities thatare connected to an Ethernet LAN. Two versions of FIP are supported by the Cisco Nexus device:

• FIP—TheConverged Enhanced Ethernet Data Center Bridging Exchange (CEE-DCBX) protocol supportsT11-compliant Gen-2 CNAs.

• Pre-FIP—The Cisco, Intel, Nuova Data Center Bridging Exchange (CIN-DCBX) protocol supportsGen-1 converged network adapters (CNAs).

The Cisco Nexus device detects the capabilities of the attached CNA and switches to the correct FIP mode.

FIP Virtual Link InstantiationCisco NX-OS support the T11-compliant FIP on Cisco Nexus devices.

FIP is used to perform device discovery, initialization, and link maintenance. FIP performs the followingprotocols:

• FIP Discovery—When a FCoE device is connected to the fabric, it sends out a Discovery Solicitationmessage. A Fibre Channel Forwarder (FCF) or a switch responds to the message with a SolicitedAdvertisement that provides an FCF MAC address to use for subsequent logins.

• FCoEVirtual Link instantiation—FIP defines the encapsulation of fabric login (FLOGI) , fabric discovery(FDISC), logout (LOGO), and exchange link parameters (ELP) frames with the corresponding replyframes. The FCoE devices use these messages to perform a fabric login.

• FCoEVirtual Link maintenance—FIP periodically sends maintenancemessages between the switch andthe CNA to ensure the connection is still valid.

FCoE Frame FormatFCoE is implemented by encapsulating a Fibre Channel frame in an Ethernet packet with a dedicated EtherType,0x8906. That packet has a 4-bit version field. The other header fields in the frame (the source and destinationMAC addresses, VLAN tags, and frame markers) are all standard Ethernet fields. Reserved bits pad the FCoEframe to the IEEE 802.3 minimum packet length of 64 bytes.

A Fibre Channel frame consists of 36 bytes of headers and up to 2112 bytes of data for a total maximum sizeof 2148 bytes. The encapsulated Fibre Channel frame has all the standard headers, which allow it to be passedto the storage network without further modification. To accommodate the maximum Fibre Channel frame inan FCoE frame, the class-fcoe is defined with a default maximum transmission unit (MTU) of 2240 bytes.

VLAN Tagging for FCoE FramesThe Ethernet frames that are sent by the switch to the adapter might include the IEEE 802.1Q tag. This tagincludes a field for the class of service (CoS) value used by the priority flow control (PFC). The IEEE 802.1Qtag also includes a VLAN field.


OverviewFCoE Initiation Protocol

The Cisco Nexus device expects frames from a FIP T11-compliant CNA to be tagged with the VLAN tag forthe FCoE VLAN. Frames that are not correctly tagged are discarded.

The switch expects frames from a pre-FIP CNA to be priority tagged with the FCoE CoS value. The switchwill still accept untagged frames from the CNA.

FIP Ethernet Frame FormatFIP is encapsulated in an Ethernet packet with a dedicated EtherType, 0x8914. The packet has a 4-bit versionfield. Along with the source and destination MAC addresses, the FIP packet also contains a FIP operationcode and a FIP operation subcode. The following table describes the FIP operation codes.

Table 2: FIP Operation Codes

FIP OperationFIP SubcodeFIP Operation Code

Discovery Solicitation0x010x0001

Discovery Advertisement0x02

Virtual Link Instantiation Request0x010x0002

Virtual Link Instantiation Reply0x02

FIP Keep Alive0x010x0003

FIP Clear Virtual Links0x02

FIP VLAN Request0x010x0004

FIP VLAN Notification0x02

Pre-FIP Virtual Link InstantiationPre-FIP virtual link instantiation consists of two phases; link discovery using the Data Center BridgingExchange protocol (DCBX), which is followed by Fabric Login.

The Cisco Nexus device is backward compatible with Gen-1 CNAs that operate in pre-FIP mode.

Pre-FIP is also known as the Cisco, Intel, Nuova Data Center Bridging Exchange (CIN-DCBX) protocol.Note


OverviewFIP Ethernet Frame Format

Data Center Bridging Exchange ProtocolThe Data Center Bridging Exchange (DCBX) protocol is an extension of the Link Layer Discovery Protocol(LLDP). DCBX end points exchange request and acknowledgment messages. For flexibility, parameters arecoded in a type-length-value (TLV) format.

The Cisco Nexus device supports two versions of DCBX:

• CEE-DCBX—The Converged Enhanced Ethernet DCBX is supported on all T11-compliant Gen-2CNAs.

• CIN-DCBX—The Cisco, Intel, Nuova DCBX is supported on Gen-1 converged network adapters(CNAs). CIN-DCBX is used to perform link detection in addition to other functions.

DCBX runs on the physical Ethernet link between the Cisco Nexus device and the CNA. By default, DCBXis enabled on Ethernet interfaces. When an Ethernet interface is brought up, the switch automatically startsto communicate with the CNA.

During the normal operation of FCoE between the switch and the CNA, DCBX provides link-error detection.

DCBX is also used to negotiate capabilities between the switch and the CNA and to send configuration valuesto the CNA.

The CNAs that are connected to a Cisco Nexus device are programmed to accept the configuration valuessent by the switch, allowing the switch to distribute configuration values to all attached CNAs, which reducesthe possibility of configuration errors and simplifies CNA administration.

DCBX Feature NegotiationThe switch and CNA exchange capability information and configuration values. The Cisco Nexus devicessupport the following capabilities:

• FCoE—If the CNA supports FCoE capability, the switch sends the IEEE 802.1p CoS value to be usedwith FCoE packets.

• Priority Flow Control (PFC)—If the adapter supports PFC, the switch sends the IEEE 802.1p CoS valuesto be enabled with PFC.

• Priority group type-length-value (TLV).

• Ethernet logical link up and down signal.

• FCoE logical link up and down signal for pre-FIP CNAs.

The following rules determine whether the negotiation results in a capability being enabled:

• If a capability and its configuration values match between the switch and the CNA, the feature is enabled.

• If a capability matches, but the configuration values do not match, the following occurs:

◦If the CNA is configured to accept the switch configuration value, the capability is enabled usingthe switch value.

◦If the CNA is not configured to accept the switch configuration value, the capability remainsdisabled.


OverviewData Center Bridging Exchange Protocol

• If the CNA does not support a DCBX capability, that capability remains disabled.

• If the CNA does not implement DCBX, all capabilities remain disabled.

The Cisco Nexus device provides CLI commands to manually override the results of the PFC negotiationwith the adapter. On a per-interface basis, you can force capabilities to be enabled or disabled.

Note

The priority flow control (PFC) mode does not send PFC TLV and PFC will not negotiate between CNAand Cisco Nexus 5000 Series switches.

Note

Lossless EthernetStandard Ethernet is a best-effort medium which means that it lacks any form of flow control. In the event ofcongestion or collisions, Ethernet drops packets. The higher level protocols detect the missing data andretransmit the dropped packets.

To properly support Fibre Channel, Ethernet has been enhanced with a priority flow control (PFC) mechanism.

Logical Link Up/DownThe following expansion modules provide native Fibre Channel ports to connect the Cisco Nexus 5000 Seriesswitch to other Fibre Channel devices.

• N5K-M1404 Cisco Nexus 5000 1000 Series Module 4x10GE 4xFC 4/2/1

• N5K-M1008 Cisco Nexus 5000 1000 Series Module 8xFC 4/2/1

• N5K-M1060 Cisco Nexus 5000 1000 Series Module 6xFC 8/4/2/1

On a native Fibre Channel link, some configuration actions (such as changing the VSAN) require that youreset the interface status. When you reset the interface status, the switch disables the interface and thenimmediately reenables the interface.

If an Ethernet link provides FCoE service, do not reset the physical link because this action is disruptive toall traffic on the link.

The logical link up/down feature allows the switch to reset an individual virtual link. The logical link downis signaled with a FIP Clear Virtual Link message.

For pre-FIP CNAs, the switch sends a DCBX message to request the CNA to reset only the virtual FibreChannel interface.

If the CNA does not support the logical link level up/down feature, the CNA resets the physical link. Inthis case, all traffic on the Ethernet interface is disrupted.

DCBX-based FC Logical Link Status signaling applies only to FCoE sessions to pre-FIP CNAs.

Note


OverviewLossless Ethernet

Converged Network AdaptersThe following types of CNAs are available:

• Hardware adapter

◦Works with the existing Fibre Channel host bus adapter (HBA) driver and Ethernet NetworkInterface Card (NIC) driver in the server.

◦Server operating system view of the network is unchanged; the CNA presents a SAN interface anda LAN interface to the operating system.

• FCoE software stack

◦Runs on existing 10-Gigabit Ethernet adapters.

Two generations of CNAs are supported by the Cisco Nexus device:

• A FIP adapter uses the FIP to exchange information about its available capabilities and to negotiate theconfigurable values with the switch.

• A pre-FIP adapter uses DCBX to exchange information about its available capabilities and to negotiatethe configurable values with the switch.

To reduce configuration errors and simplify administration, the switch distributes the configuration data toall the connected adapters.


OverviewConverged Network Adapters

C H A P T E R 3Configuring FCoE


• Licensing Requirements for FCoE, page 9

• FCoE Topologies, page 10

• FCoE Best Practices, page 12

• Guidelines and Limitations, page 15

• Configuring FCoE, page 16

• Verifying the FCoE Configuration, page 21

Licensing Requirements for FCoEOn Cisco Nexus devices, FCoE capability is included in the Storage Protocol Services License.

Before using FCoE capabilities, you must ensure the following:

• The correct license is installed.

• FCoE has been activated on the switch by entering the feature fcoe command in configuration mode.


FCoE Topologies

Directly Connected CNA TopologyThe Cisco Nexus device can be deployed as a Fibre Channel Forwarder (FCF) as shown in the followingfigure.

Figure 1: Directly Connected Fibre Channel Forwarder

The following rules are used to process FIP frames to avoid the FCF being used as a transit between an FCoEnode (ENode) and another FCF. These rules also prevent login sessions between ENodes and FCFs in differentfabrics.

• FIP solicitation and login frames received from the CNAs are processed by the FCF and are not forwarded.

• If an FCF receives solicitations and advertisements from other FCFs over an interface, the followingoccurs:

◦The frames are ignored and discarded if the FC-MAP value in the frame matches the value of theFCF (the FCF is in the same fabric).

◦The interface is placed in the "FCoE Isolated" state if the FC-MAP value in the FIP frame doesnot match that of the FCF (the FCF is in a different fabric).


Configuring FCoEFCoE Topologies

CNAs cannot discover or log in to FCFs that are reachable only through a transit Cisco Nexus FCF. The CiscoNexus device cannot perform the FCoE transit function between a CNA and another FCF due to hardwarelimitations.

Because the Cisco Nexus FCF cannot perform the transit FCoE function, you must design your networktopology so that the active Spanning Tree Protocol (STP) path of FCoE VLANs is always over the directlyconnected links between the CNA and the FCF. Make sure that you configure the FCoE VLAN on the directlyconnected links only.

Remotely Connected CNA TopologyThe Cisco Nexus device can be deployed as a Fibre Channel Forwarder (FCF) for remotely connected CNAs,but not as a FIP snooping bridge, as shown in the following figure.

Figure 2: Remotely Connected Fibre Channel Forwarder

The following rules are used to process FIP frames to avoid the FCF being used as a transit between an ENodeand another FCF. These rules also prevent login sessions between ENodes and FCFs in different fabrics.

• FIP solicitation and login frames received from the CNAs are processed by the FCF and are not forwarded.

• If an FCF receives solicitations and advertisements from other FCFs over an interface, the followingoccurs:

◦The frames are ignored and discarded if the FC-MAP value in the frame matches the value of theFCF (the FCF is in the same fabric).


Configuring FCoERemotely Connected CNA Topology

◦The interface is placed in the "FCoE Isolated" state if the FC-MAP value in the FIP frame doesnot match that of the FCF (the FCF is in a different fabric).

Because the Cisco Nexus FCF cannot perform the transit FCoE function, you must design your networktopology so that the active STP path of FCoE VLANs is always over the directly connected links betweenthe CNA and the FCF. Make sure that you configure the FCoE VLAN on the directly connected links only.

FCoE Best Practices

Directly Connected CNA Best PracticeThe following figure shows a best practices topology for an access network that is using directly connectedCNAs with Cisco Nexus devices.

Figure 3: Directly Connected CNA

Follow these configuration best practices for the deployment topology in the preceding figure:

1 You must configure a unique dedicated VLAN at every converged access switch to carry traffic for eachVirtual Fabric (VSAN) in the SAN (for example, VLAN 1002 for VSAN 1, VLAN 1003 for VSAN 2,and so on). If you enable Multiple Spanning Tree (MST), you must use a separate MST instance for FCoEVLANs.


Configuring FCoEFCoE Best Practices

2 You must configure the unified fabric (UF) links as trunk ports. Do not configure the FCoE VLAN as anative VLAN. You must configure all FCoE VLANs as members of the UF links to allow extensions forVF_Port trunking and VSAN management for the virtual Fibre Channel interfaces.

A unified wire carries both Ethernet and FCoE traffic.Note

3 You must configure the UF links as spanning-tree edge ports.

4 You must not configure the FCoE VLANs as members of Ethernet links that are not designated to carryFCoE traffic because you want to ensure that the scope of the STP for the FCoE VLANs is limited to UFlinks only.

5 If the converged access switches (in the same SAN fabric or in another) need to be connected to each otherover Ethernet links for a LAN alternate path, you must explicitly configure such links to exclude all FCoEVLANs from membership. This action ensures that the scope of the STP for the FCoE VLANs is limitedto UF links only.

6 You must use separate FCoE VLANs for FCoE in SAN-A and SAN-B.

All Gen-1 (pre-FIP) and Gen-2 (FIP) CNAs are supported in a directly connected topology.Note


Configuring FCoEDirectly Connected CNA Best Practice

Remotely Connected CNA Best PracticeThe following figure shows a best practices topology for an access network using remotely connected CNAswith Cisco Nexus devices.

Figure 4: Remotely Connected CNAs

Follow these configuration best practices for the deployment topology in the preceding figure:

1 You must configure a unique dedicated VLAN at every converged access switch to carry traffic for eachVirtual Fabric (VSAN) in the SAN (for example, VLAN 1002 for VSAN 1, VLAN 1003 for VSAN 2,and so on). If you enable MST, you must use a separate MST instance for FCoE VLANs.

2 You must configure the unified fabric (UF) links as trunk ports. Do not configure the FCoE VLAN as anative VLAN. You must configure all FCoE VLANs as members of the UF links to allow extensions forVF_Port trunking and VSAN management for the virtual Fibre Channel interfaces.


Configuring FCoERemotely Connected CNA Best Practice

A unified fabric link carries both Ethernet and FCoE traffic.Note

3 You must configure the CNAs and the blade switches as spanning-tree edge ports.

4 A blade switch must connect to exactly one Cisco Nexus device converged access switch, preferably overan EtherChannel, to avoid disruption due to STP reconvergence on events such as provisioning new linksor blade switches.

5 You must configure the Cisco Nexus device converged access switch with a better STP priority than theblade switches that are connected to it. This requirement allows you to create an island of FCoE VLANswhere the converged access switch is the spanning-tree root and all the blade switches connected to itbecome downstream nodes.

6 Do not configure the FCoE VLANs as members of Ethernet links that are not designated to carry FCoEtraffic because you want to ensure that the scope of the STP for the FCoE VLANs is limited to UF linksonly.

7 If the converged access switches and/or the blade switches need to be connected to each over Ethernetlinks for the purposes of LAN alternate pathing, you must explicitly configure such links to exclude allFCoE VLANs from membership. This action ensures the scope of the STP for FCoE VLANs is limitedto UF links only.

8 You must use separate FCoE VLANs for FCoE in SAN-A and SAN-B.

A remotely connected topology is supported only with Gen-2 (FIP) CNAs.Note

Guidelines and LimitationsFCoE has the following guidelines and limitations:

• FCoE on Cisco Nexus devices support the Gen-1 (pre-FIP) and Gen-2 (FIP) CNAs. FCoE on the CiscoNexus 2232PP fabric extender (FEX) supports Gen-2 CNAs only.

• Enabling FCoE on VLAN 1 is not supported.

• A combination of straight-through and active-active topologies is not supported on the same FEX.

• Direct connect FCoE (that is, a direct connect to CNAs through a bind interface) is not supported on aport channel of a Cisco Nexus device or FEX interface if it is configured to have more than one interface.Direct connect FCoE is supported on port channels with a single link to allow for FCoE from a CNAconnected through a vPC with one 10 GB link to each upstream switch/FEX.

For a description of the default quality of service (QoS) policies for FCoE, see the Quality of Serviceguide for your device. for the Nexus software release that you are using. The available versions of thisdocument can be found at the following URL: http://www.cisco.com/en/US/products/ps9670/products_installation_and_configuration_guides_list.html..

Note


Configuring FCoEGuidelines and Limitations

http://www.cisco.com/en/US/products/ps9670/products_installation_and_configuration_guides_list.html

http://www.cisco.com/en/US/products/ps9670/products_installation_and_configuration_guides_list.html

Configuring FCoE

Configuring QoSYou need to attach the system service policy to configure QoS. The service-policy command specifies thesystem class policy map as the service policy for the system.

SUMMARY STEPS

1. switch# configure terminal2. switch(config)# system qos3. switch(config-sys-qos)# service-policy type {network-qos | qos | queuing} [input | output] fcoe default

policy-name

DETAILED STEPS

PurposeCommand or Action

Enters global configuration mode.switch# configure terminalStep 1

Enters system qos configuration mode.switch(config)# system qosStep 2

Specifies the default FCoE policy map to use as the service policy for thesystem. There are four pre-defined policy-maps for FCoE:

switch(config-sys-qos)# service-policytype {network-qos | qos | queuing}[input | output] fcoe default policy-name

Step 3

• service-policy type queuing input fcoe-default-in-policy

• service-policy type queuing output fcoe-default-out-policy

• service-policy type qos input fcoe-default-in-policy

• service-policy type network-qos fcoe-default-nq-policy

Before enabling FCoE on a Cisco Nexus device, you must attachthe pre-defined FCoE policymaps to the type qos, type network-qos,and type queuing policy maps.

Note

Enabling FCoEYou can enable FCoE on the switch; however, enabling FCoE on VLAN 1 is not supported.


Configuring FCoEConfiguring FCoE

All the Fibre Channel features of the Cisco Nexus device are packaged in the FC Plugin. When you enableFCoE, the switch software checks for the FC_FEATURES_PKG license. If it finds the license, the softwareloads the plugin. If the license is not found, the software loads the plugin with a grace period of 180 days.

After the FC Plugin is loaded, the following occurs:

Note

• All Fibre Channel and FCoE-related CLI are available

• The Fibre Channel interfaces of any installed expansion modules are available

If after 180 days, a valid license is not found, the FC Plugin is disabled. At the next switch reboot, allFCoE commands are removed from the CLI and the FCoE configuration is deleted.

Before You Begin

You must have the FC_FEATURES_PKG (N5010SS or N5020SS) license installed.

SUMMARY STEPS

1. switch# configure terminal2. switch(config)# feature fcoe

DETAILED STEPS



Enables the FCoE capability.switch(config)# feature fcoeStep 2

This example shows how to enable FCoE on the switch:switch# configure terminalswitch(config)# feature fcoe

Disabling FCoEAfter you disable FCoE, all FCoE commands are removed from the CLI and the FCoE configuration is deleted.

SUMMARY STEPS

1. switch# configure terminal2. switch(config)# no feature fcoe


Configuring FCoEDisabling FCoE

DETAILED STEPS



Disables the FCoE capability.switch(config)# no feature fcoeStep 2

This example shows how to disable FCoE on the switch:switch# configure terminalswitch(config)# no feature fcoe

Disabling LAN Traffic on an FCoE LinkYou can disable LAN traffic on an FCoE link.

DCBX allows the switch to send a LAN Logical Link Status (LLS) message to a directly connected CNA.Enter the shutdown lan command to send an LLS-Down message to the CNA. This command causes allVLANs on the interface that are not enabled for FCoE to be brought down. If a VLAN on the interface isenabled for FCoE, it continues to carry SAN traffic without any interruption.

SUMMARY STEPS

1. switch# configure terminal2. switch(config)# interface ethernet slot/port3. switch(config-if)# shutdown lan4. (Optional) switch(config-if)# no shutdown lan

DETAILED STEPS



Specifies an interface to configure, and enters interfaceconfiguration mode.

switch(config)# interface ethernet slot/portStep 2

Shuts down Ethernet traffic on the interface. If the interface is partof an FCoE VLAN, the shutdown has no impact on the FCoEtraffic.

switch(config-if)# shutdown lanStep 3

(Optional)Reenables Ethernet traffic on the interface.

switch(config-if)# no shutdown lanStep 4


Configuring FCoEDisabling LAN Traffic on an FCoE Link

Configuring the FC-Map

We recommend using the "Mapping a VSAN to a VLAN " method for preserving fabric isolation andleaving the FC-MAP default.

Note

You can prevent data corruption due to cross-fabric talk by configuring an FC-Map that identifies the FibreChannel fabric for this Cisco Nexus device. When the FC-Map is configured, the switch discards the MACaddresses that are not part of the current fabric.

SUMMARY STEPS

1. switch# configure terminal2. switch(config)# fcoe fcmap fabric-map3. (Optional) switch(config)# no fcoe fcmap fabric-map

DETAILED STEPS



Configures the global FC-Map. The default value is 0E.FC.00.The range is from 0E.FC.00 to 0E.FC.FF.

switch(config)# fcoe fcmap fabric-mapStep 2

(Optional)Resets the global FC-Map to the default value of 0E.FC.00.

switch(config)# no fcoe fcmap fabric-mapStep 3

This example shows how to configure the global FC-Map:switch# configure terminalswitch(config)# fcoe fcmap 0x0efc2a

Configuring the Fabric PriorityThe Cisco Nexus device advertises its priority. The priority is used by the CNAs in the fabric to determinethe best switch to connect to.

SUMMARY STEPS

1. switch# configure terminal2. switch(config)# fcoe fcf-priority fabric-priority3. (Optional) switch(config)# no fcoe fcf-priority fabric-priority


Configuring FCoEConfiguring the FC-Map

DETAILED STEPS



Configures the global fabric priority. The default value is 128.The range is from 0 (higher) to 255 (lower).

switch(config)# fcoe fcf-priority fabric-priorityStep 2

(Optional)Resets the global fabric priority to the default value of 128.

switch(config)# no fcoe fcf-priority fabric-priorityStep 3

This example shows how to configure the global fabric priority:switch# configure terminalswitch(config)# fcoe fcf-priority 42

Configuring Jumbo MTUThis example shows how to configure the default Ethernet system class to support the jumbo MTU:switch(config)# policy-map type network-qos jumboswitch(config-pmap-nq)# class type network-qos class-fcoeswitch(config-pmap-c-nq)# pause no-dropswitch(config-pmap-c-nq)# mtu 2158switch(config-pmap-nq)# class type network-qos class-defaultswitch(config-pmap-c-nq)# mtu 9216switch(config-pmap-c-nq)# exitswitch(config-pmap-nq)# exitswitch(config)# system qosswitch(config-sys-qos)# service-policy type qos input fcoe-default-in-policyswitch(config-sys-qos)# service-policy type queuing input fcoe-default-in-policyswitch(config-sys-qos)# service-policy type queuing output fcoe-default-out-policyswitch(config-sys-qos)# service-policy type network-qos jumbo

Setting the Advertisment IntervalYou can configure the interval for Fibre Channel fabric advertisement on the switch.

SUMMARY STEPS

1. switch# configure terminal2. switch(config)# fcoe fka-adv-period inverval3. (Optional) switch(config)# no fcoe fka-adv-period interval


Configuring FCoEConfiguring Jumbo MTU

DETAILED STEPS



Configures the advertisement interval for the fabric. The defaultvalue is 8 seconds. The range is from 4 to 60 seconds.

switch(config)# fcoe fka-adv-period invervalStep 2

(Optional)Resets the advertisement interval for the fabric to its default valueof 8 seconds.

switch(config)# no fcoe fka-adv-period intervalStep 3

This example shows how to configure the advertisement interval for the fabric:switch# configure terminalswitch(config)# fcoe fka-adv-period 42

Verifying the FCoE ConfigurationTo verify FCoE configuration information, perform one of these tasks:

PurposeCommand

Displays whether FCoE is enabled on the switch.switch# show fcoe

Displays the contents of the FCoE database.switch# show fcoe database

Displays the FCoE settings for an interface or allinterfaces.

switch# show interface [interface number] fcoe

Displays the queue configuration and statistics.switch# show queuing interface[interface slot/port]

Displays the policy map settings for an interface orall interfaces.

switch# show policy-map interface[interfacenumber]

This example shows how to verify that the FCoE capability is enabled:switch# show fcoeGlobal FCF details

FCF-MAC is 00:0d:ec:6d:95:00FC-MAP is 0e:fc:00FCF Priority is 128FKA Advertisement period for FCF is 8 seconds

This example shows how to display the FCoE database:switch# show fcoe database-------------------------------------------------------------------------------INTERFACE FCID PORT NAME MAC ADDRESS-------------------------------------------------------------------------------vfc3 0x490100 21:00:00:1b:32:0a:e7:b8 00:c0:dd:0e:5f:76


Configuring FCoEVerifying the FCoE Configuration

This example shows how to display the FCoE settings for an interface.switch# show interface ethernet 1/37 fcoeEthernet1/37 is FCoE UP

vfc3 is UpFCID is 0x490100PWWN is 21:00:00:1b:32:0a:e7:b8MAC addr is 00:c0:dd:0e:5f:76


Configuring FCoEVerifying the FCoE Configuration

C H A P T E R 4Configuring FCoE VLANs and Virtual Interfaces


• Information About Virtual Interfaces, page 23

• Guidelines and Limitations for FCoE VLANs and Virtual Interfaces, page 24

• Configuring Virtual Interfaces, page 25

• Verifying the Virtual Interface , page 31

• Mapping VSANs to VLANs Example Configuration , page 33

• FCoE over Enhanced vPC, page 34

• SAN Boot with vPC, page 37

Information About Virtual InterfacesCisco Nexus devices support Fibre Channel over Ethernet (FCoE), which allows Fibre Channel and Ethernettraffic to be carried on the same physical Ethernet connection between the switch and the servers.

The Fibre Channel portion of FCoE is configured as a virtual Fibre Channel interface. Logical Fibre Channelfeatures (such as interface mode) can be configured on virtual Fibre Channel interfaces.

A virtual Fibre Channel interface must be bound to an interface before it can be used. The binding is to aphysical Ethernet interface (when the converged network adapter (CNA) is directly connected to the CiscoNexus device), a MAC address (when the CNA is remotely connected over a Layer 2 bridge), or anEtherChannel when the CNA connects to the Fibre Channel Forwarder (FCF) over a virtual port channel(vPC).

VE Port

A virtual expansion (VE) port acts as an expansion port in an FCoE network. VE ports can connect multipleFCoE switches together in the network. You can bind a VE port to a physical ethernet port or a port channel.

On the Cisco Nexus 5000 and 6000 Series switches, traffic across members of a port channel that a VE_Portis bound to is load balanced based on SID, DID, and OXID.


In order to enable all links to be used in the port-channel for FCoE traffic, enter the port-channel load-balanceethernet source-dest-port command to configure 'port-channel load balancing' to 'source-dest-port'. Theconfiguration 'source-destination-oxid' load balancing is used for FCoE traffic.

Guidelines and Limitations for FCoE VLANs and VirtualInterfaces

FCoE VLANs and Virtual Fiber Channel (vFC) interfaces have these guidelines and limitations:

• Each vFC interface must be bound to an FCoE-enabled Ethernet or EtherChannel interface or to theMAC address of a remotely connected adapter. FCoE is supported on 10-Gigabit Ethernet interfaces.

The Ethernet or EtherChannel interface that you bind to the vFC interface must be configured as follows:

◦The Ethernet or EtherChannel interface must be a trunk port (use the switchport mode trunkcommand).

◦The FCoE VLAN that corresponds to a vFC’s VSAN must be in the allowed VLAN list.

◦You must not configure an FCoE VLAN as the native VLAN of the trunk port.

The native VLAN is the default VLAN on a trunk. Any untagged frames transit thetrunk as native VLAN traffic.

Note

◦You should use an FCoE VLAN only for FCoE.

◦Do not use the default VLAN, VLAN1, as an FCoE VLAN.

◦You must configure the Ethernet interface as PortFast (use the spanning-tree port type edgetrunk command).

You are not required to configure trunking on the server interface even if the switchinterface is configured with trunking enabled. All non-FCoE traffic from the server ispassed on the native VLAN.

Note

• The vFC interface can be bound to Ethernet port channels with multiple member ports connected toFCoE Initialization Protocol (FIP) snooping bridges.

• Each vFC interface is associated with only one VSAN.

• You must map any VSAN with associated vFC interfaces to a dedicated FCoE-enabled VLAN.

• FCoE is not supported on private VLANs.

• If the converged access switches (in the same SAN fabric or in another) need to be connected to eachother over Ethernet links for a LAN alternate path, then you must explicitly configure such links toexclude all FCoE VLANs from membership.

• You must use separate FCoE VLANs for FCoE in SAN-A and SAN-B fabrics.


Configuring FCoE VLANs and Virtual InterfacesGuidelines and Limitations for FCoE VLANs and Virtual Interfaces

• FCoE connectivity to pre-FIP CNAs over virtual port channels (vPCs) is not supported.

• The maximum number of vFCs that can be bound to a port-channel is 48.

Virtual interfaces are created with the administrative state set to down. You must explicitly configure theadministrative state to bring the virtual interface into operation.

Note

Configuring Virtual Interfaces

Mapping a VSAN to a VLANA unique, dedicated VLAN must be configured at every converged access switch to carry traffic for eachVSAN in the SAN (for example, VLAN 1002 for VSAN 1, VLAN 1003 for VSAN 2, and so on). If MultipleSpanning Tree (MST) is enabled, a separate MST instance must be used for FCoE VLANs.

SUMMARY STEPS

1. switch# configure terminal2. switch(config)# vlan vlan-id3. switch(config-vlan)# fcoe [vsan vsan-id]4. switch(config-vlan)# exit5. (Optional) switch(config-vlan)# show vlan fcoe6. (Optional) switch(config-if)# copy running-config startup-config

DETAILED STEPS



Enters VLAN configuration mode. The VLAN number range is from 1to 4096.

switch(config)# vlan vlan-idStep 2

Enables FCoE for the specified VLAN. If you do not specify a VSANnumber, a mapping is created from this VLAN to the VSAN with thesame number.

switch(config-vlan)# fcoe [vsan vsan-id]Step 3

Configures the mapping from this VLAN to the specified VSAN.

Exits VLAN configuration mode. You must exit this mode to executethe configured commands on your Cisco Nexus device.

switch(config-vlan)# exitStep 4

(Optional)Displays information about the FCoE configuration for a VLAN.

switch(config-vlan)# show vlan fcoeStep 5


Configuring FCoE VLANs and Virtual InterfacesConfiguring Virtual Interfaces


(Optional)Saves the change persistently through reboots and restarts by copyingthe running configuration to the startup configuration.

switch(config-if)# copy running-configstartup-config

Step 6

This example shows how to map VLAN 200 to VSAN 2:switch(config)# vlan 200switch(config-vlan)# fcoe vsan 2

Creating a Virtual Fibre Channel InterfaceYou can create a virtual Fibre Channel interface. You must bind the virtual Fibre Channel interface to aphysical interface before it can be used.

SUMMARY STEPS

1. switch# configure terminal2. switch(config)# interface vfc vfc-id3. switch(config-if)# bind {interface {ethernet slot/port | port-channel channel-number} |mac-address

MAC-address}4. (Optional) switch(config-if)# no bind {interface {ethernet slot/port | port-channel channel-number}

|mac-addressMAC-address}5. (Optional) switch(config)# no interface vfc vfc-id

DETAILED STEPS



Creates a virtual Fibre Channel interface (if it does notalready exist) and enters interface configuration mode.

switch(config)# interface vfc vfc-idStep 2

The virtual Fibre Channel interface ID range is from 1 to8192.

Binds the virtual Fibre Channel interface to the specifiedinterface.

switch(config-if)# bind {interface {ethernet slot/port| port-channel channel-number} |mac-addressMAC-address}

Step 3

(Optional)Unbinds the virtual Fibre Channel interface from thespecified interface.

switch(config-if)# no bind {interface {ethernetslot/port | port-channel channel-number} |mac-addressMAC-address}

Step 4


Configuring FCoE VLANs and Virtual InterfacesCreating a Virtual Fibre Channel Interface


(Optional)Deletes a virtual Fibre Channel interface.

switch(config)# no interface vfc vfc-idStep 5

This example shows how to bind a virtual Fibre Channel interface to an Ethernet interface:switch# configure terminalswitch(config)# interface vfc 4switch(config-if)# bind interface ethernet 1/4

This example shows how to bind a virtual Fibre Channel interface to a Cisco Nexus 2232PP Fabric Extender(FEX) Ethernet interface:switch# configure terminalswitch(config)# interface vfc 1001switch(config-if)# bind interface ethernet 100/1/1

This example shows how to bind a virtual Fibre Channel interface to create a vPC:switch# configure terminalswitch(config)# interface vfc 3switch(config-if)# bind interface port-channel 1

This example shows how to bind a virtual Fibre Channel interface on a Cisco Nexus 2232PP FEX to createa vPC:switch# configure terminalswitch(config)# interface vfc 1001switch(config-if)# bind interface ethernet 100/1/1

An error message is displayed if you attempt to bind the interface to a Cisco Nexus FEX that does notsupport FCoE.

Note

This example shows how to bind a virtual Fibre Channel interface to a MAC address:switch# configure terminalswitch(config)# interface vfc 2switch(config-if)# bind mac-address 00:0a:00:00:00:36

This example shows how to bind a virtual Fibre Channel interface to a Cisco Nexus 2232PP FEX MACaddress:switch# configure terminalswitch(config)# interface vfc 1001switch(config-if)# bind mac-address 00:01:0b:00:00:02

This example shows how to delete a virtual Fibre Channel interface:switch# configure terminalswitch(config)# no interface vfc 4

Configuring vFC InterfaceThe following steps show how to configure vPC interface to a member port of a multi-member port-channel.


Configuring FCoE VLANs and Virtual InterfacesConfiguring vFC Interface

You can un-configure a 4-port vPC only after removing member ports from port-channel. You canun-configure only on a single member port-channel.

Note

SUMMARY STEPS

1. Create a multi-member port-channel.2. Add individual member port to a multi-member port-channel.3. Associate vPC to a member port of a multi-member port-channel.

DETAILED STEPS

Step 1 Create a multi-member port-channel.switch(config-vlan)# interface port-channel 500switch(config-vlan)# [no]fcoe multi-vfc

Step 2 Add individual member port to a multi-member port-channel.switch(config-vlan)# interface ethernet 100/1/1switch(config-vlan)# channel-group 500switch (config)# interface ethernet 100/1/2switch(config-if)# channel-group 500

Step 3 Associate vPC to a member port of a multi-member port-channel.switch(config)# interface vfc 10011switch(config-vlan)# bind interface ethernet 100/1/1switch(config-vlan)# interface vfc 10012switch (config)# bind interface ethernet 100/1/2

Associating a Virtual Fibre Channel Interface to a VSANA unique, dedicated VLAN must be configured at every converged access switch to carry traffic for eachVirtual Fabric (VSAN) in the SAN (for example, VLAN 1002 for VSAN 1, VLAN 1003 for VSAN 2, andso on). If MST is enabled, a separate MST instance must be used for FCoE VLANs.

SUMMARY STEPS

1. switch# configure terminal2. switch(config)# vsan database3. switch(config-vsan)# vsan vsan-id interface vfc vfc-id4. (Optional) switch(config-vsan)# no vsan vsan-id interface vfc vfc-id


Configuring FCoE VLANs and Virtual InterfacesAssociating a Virtual Fibre Channel Interface to a VSAN

DETAILED STEPS



Enters VSAN configuration mode.switch(config)# vsan databaseStep 2

Configures the association between the VSAN and virtual FibreChannel interface.

switch(config-vsan)# vsan vsan-id interfacevfc vfc-id

Step 3

The VSAN number must map to a VLAN on the physical Ethernetinterface that is bound to the virtual Fibre Channel interface.

(Optional)Disassociates the connection between the VSAN and virtual FibreChannel interface.

switch(config-vsan)#no vsan vsan-id interfacevfc vfc-id

Step 4

This example shows how to associate a virtual Fibre Channel interface to a VSAN:switch# configure terminalswitch(config)# vsan databaseswitch(config-vsan)# vsan 2 interface vfc 4

Creating an Implicit Virtual Fibre Channel Port Channel InterfaceYou can create a virtual Fibre Channel (vFC), and implicitly bind it to an Ethernet interface or a port-channelusing a single command. For this, the vFC identifier must match the Ethernet interface or port-channel identifier.The Ethernet interface can be a module (slot or port) or a Fabric Extender (FEX) interface (chassis, slot orport).

You cannot create an implicit vFC in a breakout port.Note

Configuring virtual Fibre Channel Interface

Before You Begin

• Ensure you have installed the correct license for FCoE.

• Ensure you have enabled FCoE.

Step 1 Enter global configuration mode:switch# configure terminal

Step 2 Create a VFC (if it does not already exist):Additionally, vfc slot/port binds the vFC to an Ethernet slot/port interface. vfc chassis/slot/port binds the vFC to a FEXinterface.


Configuring FCoE VLANs and Virtual InterfacesCreating an Implicit Virtual Fibre Channel Port Channel Interface

switch(config) # interface vfc {id | slot/port | chassis/slot/port

Step 3 Bring up the vFC interface:switch(config-if) # no shutdown

Step 4 Exit the interface configuration mode:switch(config-if) # exit

Configuring virtual Fibre Channel Interface

This example shows how to implicitly bind a virtual Fibre Channel interface to an Ethernet interface:switch# configure terminalswitch(config)# interface vfc 101/1/1switch(config-if)# no shutdown....Switch# show interface vfc 101/1/1

vfc101/1/1 is trunkingBound interface is Ethernet101/1/1Hardware is EthernetPort WWN is 20:00:00:2a:6a:15:d2:7bAdmin port mode is F, trunk mode is onsnmp link state traps are enabledPort mode is TFPort vsan is 600Trunk vsans (admin allowed and active) (1,500,600)Trunk vsans (up) (600)Trunk vsans (isolated) ()Trunk vsans (initializing) (1,500)1 minute input rate 0 bits/sec, 0 bytes/sec, 0 frames/sec1 minute output rate 0 bits/sec, 0 bytes/sec, 0 frames/sec49 frames input, 5516 bytes0 discards, 0 errors

49 frames output, 5772 bytes0 discards, 0 errors

last clearing of "show interface" counters Fri Oct 30 06:19:33 2015Interface last changed at Fri Oct 30 06:19:33 2015

Configuring virtual Fibre Channel – Port Channel Interface

Step 1 Enter global configuration mode:switch# configure terminal

Step 2 Create a vFC that implicitly binds to the Ethernet port-channel based on its number:The port number range is from 257 to 4096.

switch(config) # interface vfc-port-channel port number

Step 3 Bring up the vFC port:switch(config-if) # no shutdown

Step 4 Exit from the current interface configuration mode:


Configuring FCoE VLANs and Virtual InterfacesCreating an Implicit Virtual Fibre Channel Port Channel Interface

switch(config-if) # exit

Configuring virtual Fibre Channel - Port Channel Interface

The example shows how you can create a vFC-port-channel that implicitly binds to Ethernet port-channel:switch# configure terminalswitch(config)# interface vfc-port-channel 300switch(config-if)# no shutdown....switch# show interface vfc-port-channel 258

vfc-po258 is trunkingBound interface is port-channel258Hardware is EthernetPort WWN is 21:01:8c:60:4f:59:31:3fAdmin port mode is E, trunk mode is onsnmp link state traps are enabledPort mode is TEPort vsan is 600Trunk vsans (admin allowed and active) (1,100,500,600)Trunk vsans (up) (600)Trunk vsans (isolated) ()Trunk vsans (initializing) (1,100,500)1 minute input rate 3448 bits/sec, 431 bytes/sec, 4 frames/sec1 minute output rate 9064 bits/sec, 1133 bytes/sec, 4 frames/sec977735 frames input, 77172556 bytes0 discards, 0 errors


last clearing of "show interface" counters Thu Oct 29 06:35:41 2015Interface last changed at Thu Oct 29 06:35:41 2015

Verifying the Virtual InterfaceTo display configuration information about virtual interfaces, perform one of the following tasks:

PurposeCommand

Displays the detailed configuration of the specifiedFibre Channel interface.

switch# show interface vfc vfc-id

Displays the status of all interfaces.switch# show interface brief

Displays the mapping of FCoE VLANs to VSANs.switch# show vlan fcoe


Configuring FCoE VLANs and Virtual InterfacesVerifying the Virtual Interface

This example shows how to display a virtual Fibre Channel interface bound to an Ethernet interface:switch# show interface vfc 3vfc3 is up

Bound interface is Ethernet1/37Hardware is Virtual Fibre ChannelPort WWN is 20:02:00:0d:ec:6d:95:3fAdmin port mode is F, trunk mode is onsnmp link state traps are enabledPort mode is F, FCID is 0x490100Port vsan is 9311 minute input rate 0 bits/sec, 0 bytes/sec, 0 frames/sec1 minute output rate 0 bits/sec, 0 bytes/sec, 0 frames/sec0 frames input, 0 bytes0 discards, 0 errors


Interface last changed at Thu May 21 04:44:42 2009This example shows how to display a virtual Fibre Channel interface bound to a MAC address:switch# show interface vfc 1001vfc1001 is down

Bound MAC is 00:0a:00:00:00:01Hardware is Virtual Fibre ChannelPort WWN is 23:e8:00:0d:ec:6d:95:3fAdmin port mode is F, trunk mode is onsnmp link state traps are enabledPort vsan is 9011 minute input rate 0 bits/sec, 0 bytes/sec, 0 frames/sec1 minute output rate 0 bits/sec, 0 bytes/sec, 0 frames/sec0 frames input, 0 bytes0 discards, 0 errors


This example shows how to display the status of all the interfaces on the switch (some output has been removedfor brevity):switch# show interface brief-------------------------------------------------------------------------------Interface Vsan Admin Admin Status SFP Oper Oper Port

Mode Trunk Mode Speed ChannelMode (Gbps)

-------------------------------------------------------------------------------fc3/1 1 auto on trunking swl TE 2 --fc3/2 1 auto on sfpAbsent -- -- --...fc3/8 1 auto on sfpAbsent -- -- ---------------------------------------------------------------------------------Interface Status IP Address Speed MTU Port

Channel-------------------------------------------------------------------------------Ethernet1/1 hwFailure -- -- 1500 --Ethernet1/2 hwFailure -- -- 1500 --Ethernet1/3 up -- 10000 1500 --...Ethernet1/39 sfpIsAbsen -- -- 1500 --Ethernet1/40 sfpIsAbsen -- -- 1500 ---------------------------------------------------------------------------------Interface Status IP Address Speed MTU-------------------------------------------------------------------------------mgmt0 up 172.16.24.41 100 1500-------------------------------------------------------------------------------

-------------------------------------------------------------------------------Interface Vsan Admin Admin Status SFP Oper Oper Port

Mode Trunk Mode Speed ChannelMode (Gbps)

-------------------------------------------------------------------------------vfc 1 1 F -- down -- -- --...


Configuring FCoE VLANs and Virtual InterfacesVerifying the Virtual Interface

This example shows how to display the mapping between the VLANs and VSANs on the switch:switch# show vlan fcoeVLAN VSAN Status-------- -------- --------15 15 Operational20 20 Operational25 25 Operational30 30 Non-operational

Mapping VSANs to VLANs Example ConfigurationThe following example shows how to configure the FCoE VLAN and a virtual Fibre Channel interface:

SUMMARY STEPS

1. Enable the associated VLAN and map the VLAN to a VSAN.2. Configure the VLAN on a physical Ethernet interface.3. Create a virtual Fibre Channel interface and bind it to a physical Ethernet interface.4. Associate the virtual Fibre Channel interface to the VSAN.5. (Optional) Display membership information for the VSAN.6. (Optional) Display the interface information for the virtual Fibre Channel interface.

DETAILED STEPS

Step 1 Enable the associated VLAN and map the VLAN to a VSAN.switch(config)# vlan 200switch(config-vlan)# fcoe vsan 2switch(config-vlan)# exit

Step 2 Configure the VLAN on a physical Ethernet interface.switch# configure terminalswitch(config)# interface ethernet 1/4switch(config-if)# spanning-tree port type edge trunkswitch(config-if)# switchport mode trunkswitch(config-if)# switchport trunk allowed vlan 1,200switch(config-if)# exit

Step 3 Create a virtual Fibre Channel interface and bind it to a physical Ethernet interface.switch(config)# interface vfc 4switch(config-if)# bind interface ethernet 1/4switch(config-if)# exit

By default, all virtual Fibre Channel interfaces reside on VSAN 1. If the VLAN to VSANmapping is to a VSANother than VSAN 1, then proceed to Step 4.

Note

Step 4 Associate the virtual Fibre Channel interface to the VSAN.switch(config)# vsan databaseswitch(config-vsan)# vsan 2 interface vfc 4switch(config-vsan)# exit


Configuring FCoE VLANs and Virtual InterfacesMapping VSANs to VLANs Example Configuration

Step 5 (Optional) Display membership information for the VSAN.switch# show vsan 2 membershipvsan 2 interfaces

vfc 4

Step 6 (Optional) Display the interface information for the virtual Fibre Channel interface.switch# show interface vfc 4

vfc4 is upBound interface is Ethernet1/4Hardware is Virtual Fibre ChannelPort WWN is 20:02:00:0d:ec:6d:95:3fPort WWN is 20:02:00:0d:ec:6d:95:3fsnmp link state traps are enabledPort WWN is 20:02:00:0d:ec:6d:95:3fAPort WWN is 20:02:00:0d:ec:6d:95:3fsnmp link state traps are enabledPort mode is F, FCID is 0x490100Port vsan is 9311 minute input rate 0 bits/sec, 0 bytes/sec, 0 frames/sec1 minute output rate 0 bits/sec, 0 bytes/sec, 0 frames/sec0 frames input, 0 bytes 0 discards, 0 errors0 frames output, 0 bytes 0 discards, 0 errorsInterface last changed at Thu Mar 11 04:44:42 2010

FCoE over Enhanced vPCAlthough Ethernet traffic is dual homed between a FEX and a switch pair in an enhanced vPC topology, FCoEtraffic must be single-homed to maintain SAN isolation. Therefore, while enhanced vPC supports FCoE, asingle homed FEX topology can be a better choice when SAN isolation and high FCoE bandwidth are required.

Consider the following disadvantages of enhanced vPC for a single-homed topology:

• A typical SAN network maintains two fabrics, SAN A and SAN B, with traffic isolated between thetwo. In an enhanced vPC topology, each switch must be paired (single homed) with a FEX to ensurethat FCoE traffic from one FEX is sent to only one switch, while Ethernet traffic is dual homed betweeneach FEX and both switches. Because FCoE traffic from the FEX flows to only one switch while Ethernettraffic flows to both, the traffic load for the FEX uplinks is not evenly balanced.

• In a FEX with eight uplink ports, Ethernet traffic can use all eight ports, while the single-homed FCoEtraffic is limited by this topology to using only four of those ports, restricting the maximum bandwidthavailable for FCoE. As a further restriction, the default QoS template for the shared link allocates onlyhalf the link bandwidth to FCoE traffic, with the other half allocated to Ethernet traffic.

• In an enhanced vPC topology with FCoE, the host vPC is limited to two ports, one to each FEX.


Configuring FCoE VLANs and Virtual InterfacesFCoE over Enhanced vPC

The following figure shows the FCoE traffic flow in a systemwith two CiscoNexus 2000 FEXs, each associatedwith a different Cisco Nexus device.

Figure 5: FCoE over Enhanced vPC

Configuring FCoE over Enhanced vPCFCoE traffic must be single homed to maintain SAN isolation. You must first associate a FEX with only oneswitch. When the FEX and switch are associated, you can then create a virtual Fibre Channel (vFC) interfaceand bind it to a port.

After pairing the FEX and switch on the first peer, you repeat the configuration on the second peer using adifferent port number to ensure SAN traffic isolation. The different configuration will not cause a consistencyerror because the FCoE portion of the enhanced vPC configuration is not subject to the vPC consistency check.

Before You Begin

Review the limitations in FCoE over Enhanced vPC, on page 34.


Configuring FCoE VLANs and Virtual InterfacesConfiguring FCoE over Enhanced vPC

SUMMARY STEPS

1. switch# configure terminal2. switch(config) # fex fex-chassis_ID3. switch(config-fex) # fcoe4. switch(config-fex) # interface vfc vfc-id5. switch(config-if) # bind interface ethernet [fex-chassis-ID/]slot/port6. switch(config-if) # no shutdown7. (Optional) switch(config-if) # end8. (Optional) switch(config)# copy running-config startup-config

DETAILED STEPS



Enters configuration mode for the specified FEX.switch(config) # fex fex-chassis_IDStep 2

The range for fex-chassis_ID is from 100 to 199.

Configures the FEX to send FCoE traffic only to this switch.switch(config-fex) # fcoeStep 3

Enters configuration mode for the virtual Fibre Channel interface. Ifthe interface does not already exist, this command also creates thatinterface.

switch(config-fex) # interface vfc vfc-idStep 4

The range of vfc-id is from 1 to 8192.

Binds the vFC interface to the specified physical Ethernet interface.switch(config-if) # bind interface ethernet[fex-chassis-ID/]slot/port

Step 5

The range for fex-chassis_ID is from 100 to 199. The slot must be1.For FCoE, the range for port is from 1 to 32.

Returns the interface to its default operational state.switch(config-if) # no shutdownStep 6

(Optional)Return to privileged EXEC mode.

switch(config-if) # endStep 7

(Optional)Saves the change persistently through reboots and restarts by copyingthe running configuration to the startup configuration.

switch(config)# copy running-configstartup-config

Step 8

This example shows how to pair each FEX to a switch for FCoE traffic:nexus5000-sanA# configure terminalnexus5000-sanA(config) # fex 101nexus5000-sanA(config-fex) # fcoenexus5000-sanA(config-fex) # interface vfc 1nexus5000-sanA(config-if) # bind interface ethernet 101/1/1nexus5000-sanA(config-if) # no shutdownnexus5000-sanA(config-if) # endnexus5000-sanA# copy running-config startup-config


Configuring FCoE VLANs and Virtual InterfacesConfiguring FCoE over Enhanced vPC

nexus5000-sanA#

nexus5000-sanB# configure terminalnexus5000-sanB(config) # fex 102nexus5000-sanB(config-fex) # fcoenexus5000-sanB(config-fex) # interface vfc 1nexus5000-sanB(config-if) # bind interface ethernet 102/1/1nexus5000-sanB(config-if) # no shutdownnexus5000-sanB(config-if) # endnexus5000-sanB# copy running-config startup-confignexus5000-sanB#

SAN Boot with vPCA Cisco Nexus Series switch can use SAN boot if the following conditions are met:

• The FEX that contains the port assigned to the vPC must be associated with the Cisco Nexus switch.

• Only one VFC interface is bound to a vPC member. You cannot bind multiple interfaces to multiplemembers.

If you want to ensure backward compatibility for all previous configurations and supported topologies,you must configure the FEX in a straight-through FEX topology that does not use Enhanced vPC.

Note

SAN Boot with vPC Configuration ExampleIn this example, virtual Fibre Channel interface 1 is bound to physical Ethernet interface 101/1/1 on FabricA and on interface 102/1/1 on Fabric B. The interface is also associated with virtual port channel 1 on bothfabrics.nexus5000-sanA(config) # interface vfc 1nexus5000-sanA(config-if) # bind interface eth 101/1/1nexus5000-sanA(config) # interface eth 101/1/1nexus5000-sanA(config-if) # channel-group 1 mode activenexus5000-sanA(config-if) # interface port-channel 1nexus5000-sanA(config-if) # vpc 1nexus5000-sanA(config-if) #

nexus5000-sanB(config) # interface vfc 1nexus5000-sanB(config-if) # bind interface eth 102/1/1nexus5000-sanB(config) # interface eth 102/1/1nexus5000-sanB(config-if) # channel-group 1 mode activenexus5000-sanB(config-if) # interface port-channel 1nexus5000-sanB(config-if) # vpc 1nexus5000-sanB(config-if) #


Configuring FCoE VLANs and Virtual InterfacesSAN Boot with vPC


Configuring FCoE VLANs and Virtual InterfacesSAN Boot with vPC Configuration Example

C H A P T E R 5Configuring Cisco Adapter FEX with FCoE


• Overview, page 39

OverviewThe Cisco Adapter Fabric Extender (FEX) feature allows you to create an FCoE connection to a FEX so thatyou can establish an FCoE connection to a server with a virtual interface card (VIC) adapter.

For example, you could use this feature to connect your Nexus switch to a Cisco UCS C-Series Rack-MountServer that contains a Cisco UCS P81E Virtual Interface Card, or you could connect it to a third-party serverthat has a Broadcom BCM57712 Convergence Network Interface Card (C-NIC) installed.

The switch connects to the FEX through a virtual port channel (vPC) while the FEX connects to the serverusing a standard FCoE link between the FEX and the VIC adapter.

Guidelines and LimitationsIf you are using Enhanced vPC, the FEX can be associated with one and only one Cisco Nexus fabric forFCoE forwarding.

If you are using FabricPath, you must use a dedicated link for FCoE traffic.

If you are using a Cisco UCS C-Series Rack-Mount Server with a Cisco UCS P81E Virtual Interface Card(VIC), you must do the following:

• Configure the VIC in Network Interface Virtualization (NIV) mode, which makes the two unified portsappear to the system as virtual Host Bus Adapters (vHBAs).

• You cannot connect to the FEX through a VNP port. If this type of connection is used, NIVmode cannotbe enabled on the VIC.

• You must set the NIC mode on the Cisco UCS C-Series Rack-Mount Server to active-standby.


The HP chassis has internal HP-branded VirtualConnect cards (the specific model is HP VC FlexFabric10Gb/24-Port Module), which runs its own internal host-hiding NPV processes for both FC and Ethernetsides of things. Then the external links of that card go upstream to regular Cisco 2232PP FEX's, whichare then attached to our Nexus core.

Note

Configuring Cisco Adapter FEX with FCoE

SUMMARY STEPS

1. configure terminal2. install feature-set virtualization3. feature-set virtualization4. fex fex-chassis-ID5. fcoe6. interface ethernet [fex-chassis-ID/slot/port]7. switchport mode vntag8. interface vethernet veth-id9. bind interface ethernet [fex-chassis-ID/]slot/port channel channel-no10. switchport mode {trunk|access}11. (Optional) switchport trunk allowed vlan vlan-ID12. (Optional) switchport access vlan vlan-ID13. interface vfc vfc-id14. bind interface vethernet veth-num15. no shutdown

DETAILED STEPS


Enters global configuration mode.configure terminal

Example:switch# configure terminalswitch(config)#

Step 1

Installs the virtualization feature set.install feature-set virtualization

Example:switch(config) # install feature-setvirtualizationswitch(config) #

Step 2


Configuring Cisco Adapter FEX with FCoEConfiguring Cisco Adapter FEX with FCoE


Enables the virtualization feature.feature-set virtualization

Example:switch(config) # feature-set virtualizationswitch(config)#

Step 3

Enters configuration mode for the specified FEX.fex fex-chassis-IDStep 4

Example:switch(config) # fex 101switch(config-fex) #

The range for fex-chassis_ID is from 100 to 199.

Enables Fibre Channel over Ethernet traffic on the FEX.fcoe

Example:switch(config-fex) # fcoeswitch(config-fex) #

Step 5

Enters configurationmode for the specified Ethernet interface.interface ethernet [fex-chassis-ID/slot/port]Step 6

Example:switch(config-fex)# interface ethernet 101/1/1switch(config-if)#

The range for fex-chassis-ID is from 100 to 199. The slotFor FCoE, the range for port is from 1 to 32.

Configures the interface in port mode.switchport mode vntag

Example:switch(config-if) # switchport mode vntagswitch(config-if) #

Step 7

Creates a virtual Ethernet interface and enters configurationmode for that interface.

interface vethernet veth-id

Example:switch(config-if) # interface vethernet 2switch(config-if) #

Step 8

The range of veth-id is from 1 to 1,048,575.

If you have two Cisco Nexus Series switchesconfigured for redundancy, the virtual Ethernetinterface ID must be unique on each switch.

Note

Binds the specified Ethernet interface to the specified portchannel.

bind interface ethernet [fex-chassis-ID/]slot/portchannel channel-no

Step 9

Example:switch(config-if) # bind interface ethernet101/1/1 channel 1switch(config-if) #

The range for fex-chassis-ID is from 100 to 199. The slotmust be 1. For FCoE, the range for port is from 1 to 32. Therange for channel-no is from 1 to 4096.

Configures the interface as a trunk port or an access port.switchport mode {trunk|access}

Example:switch(config-if) # switchport mode trunkswitch(config-if) #

Step 10




(Optional)If you configured the interface as a trunk port, use thiscommand to specify the VLAN for FCoE traffic.

switchport trunk allowed vlan vlan-ID

Example:switch(config-if) # switchport trunk allowedvlan 33switch(config-if) #

Step 11

The range for vlan-ID is from 1 to 4094, except for theVLANs reserved for internal use.

(Optional)If you configured the interface as an access port, use thiscommand to specify the VLAN for FCoE traffic.

switchport access vlan vlan-ID

Example:switch(config-if) # switchport access vlan 33switch(config-if) #

Step 12

Creates a virtual Fibre Channel interface on the switch andenters configuration mode.

interface vfc vfc-id

Example:switch(config-if) # interface vfc 4switch(config-if) #

Step 13

The range of vfc-id is from 1 to 8192.

Binds the virtual Fibre Channel interface to the specifiedvirtual Ethernet interface.

bind interface vethernet veth-num

Example:switch(config-if) # bind interface veth 2switch(config-if) #

Step 14

The range of veth-num is from 1 to 1048575.

Returns the interface to its default operational state.no shutdown

Example:switch(config-if) # no shutdownswitch(config-if) #

Step 15

This example show how to configure Cisco Adapter FEX with FCoE on SAN fabric A using FEX 101 andthe Ethernet interface on channel 1 configured as a trunk port.nexus5000-sanA(config)#configure terminalnexus5000-sanA(config)# install feature-set virtualizationnexus5000-sanA(config)# feature-set virtualizationnexus5000-sanA(config)# fex 101nexus5000-sanA(config-fex)# fcoenexus5000-sanA(config-fex)# interface ethernet 101/1/1nexus5000-sanA(config-if)# switchport mode vntagnexus5000-sanA(config-if)# interface veth 2nexus5000-sanA(config-if)# bind interface eth 101/1/1 channel 1nexus5000-sanA(config-if)# switchport mode trunknexus5000-sanA(config-if)# switchport trunk allowed vlan 33nexus5000-sanA(config-if)# interface vfc 4nexus5000-sanA(config-if)# bind interface veth 2nexus5000-sanA(config-if)# no shutdown

This example shows how to configure Cisco Adapter FEX with FCoE on SAN fabric B using FEX 102 andEthernet interface on channel 2 as an access port:nexus5000-sanB(config)#configure terminalnexus5000-sanB(config)# install feature-set virtualizationnexus5000-sanB(config)# feature-set virtualizationnexus5000-sanB(config)# fex 102nexus5000-sanB(config-fex)# fcoe



nexus5000-sanB(config-fex)# interface ethernet 102/1/1nexus5000-sanB(config-if)# switchport mode vntagnexus5000-sanB(config-if)# interface veth 5nexus5000-sanB(config-if)# bind interface eth 102/1/1 channel 2nexus5000-sanB(config-if)# switchport mode accessnexus5000-sanB(config-if)# switchport access vlan 40nexus5000-sanB(config-if)# interface vfc 6nexus5000-sanB(config-if)# bind interface veth 5nexus5000-sanB(config-if)# no shutdown





Documents

Cisco Nexus 5000 Series NX-OS Fibre Channel over ... › ... › 521n11 › b_5k_FCoE_Config_521N11.pdfCisco Nexus 5000 Series NX-OS Fibre Channel over Ethernet Configuration Guide,