PDF(225.8 KB) View with Adobe Reader on a variety of devices
Updated:March 19, 2015
The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
This document describes how to configure Fibre Channel over Ethernet (FCoE) uplinks. In Cisco Unified Computing System (UCS) Version 2.1 and later Versions, multihop Fibre Channel over Ethernet (FCoE) support was introduced. This support allows uplink consolidation from two separate links to a single uplink that carries both Fibre Channel (FC) and Ethernet.
Note: Unified uplinks are different from unified ports. Any fabric interconnect (FI), which includes generation 1, can have unified uplinks. However, only generation 2 FIs have unified ports.
There are no specific requirements for this document.
The information in this document is based on UCS Manager (UCSM) Version 2.1. You must run at least Version 2.1(1a) in order to use this document.
The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, make sure that you understand the potential impact of any command.
In all of these configurations, you can replace any link with a port-channel of the same type. For example, if the configuration shows one link, it can be configured with one port-channel instead. However, you cannot have an Ethernet and a Unified port in the same port-channel.
FCoE Uplink with virtual Port Channel (vPC)
This configuration contains no unified links, but it is the easiest way to integrate FCoE uplinks into your current environment. This configuration eliminates the need to cross the FC fabrics.
Cross-connected with Pinning
In this configuration, the Nexus 5000 Series switches (N5ks) and FIs are cross-connected, but not port-channeled together. This allows you to have some unified uplinks, but you still maintain a well-known network design.
All Unified Uplinks
This configuration provides the most consolidation. Remember that these links can also be port-channels, but all links must be unified uplinks. This is likely to be the most common implementation.
Configuration on the UCS
There are three steps to configure the UCS:
Configure Virtual Storage Area Network (VSAN).
Configure Unified Uplinks.
Configure Port-channels (optional).
In this configuration, VSAN 500 is out of Fabric A, and VSAN 600 is out of Fabric B. This is the same configuration you would use in order to create a VSAN for a normal FC.
Configure Unified Uplinks
The Unified uplink is hidden in the GUI. In order to make a unified port, you must first configure it as an uplink or a FCoE uplink. Then, you can configure it as a unified port. This configuration does not remove the first role. Instead, it creates an interface that has both.
Make sure to set your VSAN at this point.
At this point, your UCS is configured for unified traffic. This example does not use port-channels. However, you can configure port-channels normally at this point. Make sure to set the VSAN under the VSAN tab for the port-channel.
Configuration on the N5k
Configuration on the N5k consists of 3 steps:
Enable FCoE and default Quality of Service (QoS) settings. Create the FCoE VLAN and bind the VSAN to it.
Configure the Ethernet interface (or port-channel).
Create a virtual Fibre Channel (vFC) and bind it to the Ethernet interface.
Note: The UCS is a N Port Virtualization (NPV) switch by default so the upstream switch needs to be in N Port Identifer Virtulization (NPIV) mode (enter the feature npiv command in order to enable). See Configuring N Port Virtualization for more information on this feature.
Enable FCoE and Default QoS Settings
You can skip this step if the N5k is already configured for FCoE. If the N5k is not configured for FCoE, refer to Appendix A at the end of this document for instruction.
Configure the Ethernet Interfaces (or Port-channels)
This is the configuration for the interface that normally connects to the UCS. Make sure to allow the FCoE VLAN.
There is currently no verification procedure available for this configuration.
There is currently no specific troubleshooting information available for this configuration.
Appendix A - N5k basic FCoE Configuration
In order to configure the N5k for FCoE, enter:
feature fcoe system qos service-policy type network-qos fcoe-default-nq-policy 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
These commands first enable FCoE, and then enable the default QoS policies that are needed for FCoE. If you have custom QoS settings, use those as a base. Here are the default configurations:
policy-map type qos fcoe-default-in-policy class type qos class-fcoe set qos-group 1 class type qos class-default set qos-group 0
policy-map type queuing fcoe-default-in-policy class type queuing class-fcoe bandwidth percent 50 class type queuing class-default bandwidth percent 50 policy-map type queuing fcoe-default-out-policy class type queuing class-fcoe bandwidth percent 50 class type queuing class-default bandwidth percent 50
policy-map type network-qos fcoe-default-nq-policy class type network-qos class-fcoe
pause no-drop mtu 2158 class type network-qos class-default
mtu 1500 multicast-optimize
As you can see, these policies create the FCoE traffic class, mark it for no-drop, and give it dedicated bandwidth. You can modify these as you need (for example, in order to add Jumbo Frames).