Edit

FCoE Overview

  • The evolution of Fibre Channel has seen the integration of networking capabilities that allow it to extend beyond traditional, dedicated SANs. This is where FCoE comes into play. FCoE merges the strengths of Fibre Channel with the flexibility of Ethernet. FCoE enables organizations to consolidate their storage and data networks onto a single, unified infrastructure, as you can see in the next figure. This convergence simplifies the data center architecture by reducing the need for separate networks, thus lowering costs and operational complexity.

  • FCoE operates by encapsulating Fibre Channel frames within Ethernet packets, enabling them to be transported over standard Ethernet networks. This technology retains the primary benefits of Fibre Channel, such as low latency and high reliability, by leveraging enhancements in Ethernet to ensure reliable and efficient storage traffic. The key components of this technology are:

    • Priority-Based Flow Control (PFC):

      • Purpose: Creates a lossless Ethernet environment.

      • Function: Manages the flow of traffic at the network interface level to ensure that storage data is not dropped during congestion.

    • Enhanced Transmission Selection (ETS):

      • Purpose: Optimizes bandwidth allocation.

      • Function: Allows different types of traffic to coexist on the same network, prioritizing storage traffic when necessary.

    • Data Center Bridging Exchange (DCBX) Protocol:

      • Purpose: Automatically configures and manages network settings.

      • Function: Ensures that all network components are properly aligned to handle FCoE traffic.

  • In a traditional Fibre Channel SAN (Storage Area Network), physical Fibre Channel switches, like the Cisco MDS Multilayer Director, connect to end devices such as hosts using fiber cables. These hosts are equipped with Host Bus Adapters (HBAs), which are specialized network interface cards that facilitate communication between the server and the storage network. The Fibre Channel Protocol runs natively on this network, allowing seamless communication between switches and devices.

  • In an FCoE environment, the setup changes as follows:

    • Converged Network Adapters (CNAs): These replace HBAs

    • Converged I/O: CNAs allow both Fibre Channel and Ethernet data traffic to run on the same Ethernet cable

    • FCoE Functionality: Supported by CNAs and appropriate drivers on the host device

  • The FCoE standard defines two types of endpoints for the Ethernet encapsulation of Fibre Channel frames: FCoE nodes (ENodes) and Fibre Channel Forwarders (FCFs).

    • FCoE nodes (ENodes)

      • These are endpoints that transmit FCoE frames

    • Fibre Channel Forwarders (FCFs)

      • Any Cisco Nexus Switch that can run FCoE can function as an FCF

      • Cisco MDS switches can also be considered FCFs if they support FCoE

      • Processes the Fibre Channel logins

      • Performs encapsulation and de-encapsulation of FCoE frames

      • Consumes one domain ID

      • Forwards FCoE traffic based on the Fibre Channel information within the frames

  • In the next figure, you can see a host that is an FCoE logical endpoint or ENode. The host is attached directly to a Cisco Nexus switch that acts as an FCF.

  • Notice that the Cisco Nexus and the host both have Ethernet and Fibre Channel characteristics. The Cisco Nexus switch is connected to upstream LAN switches using Ethernet interfaces and SAN network using FC interfaces. Inside the switch, the VFC interface handles the separation of the FCoE and Ethernet traffic. The FCoE frames are mapped to the appropriate VSAN, ensuring that they are properly forwarded. In this case, Fibre Channel frames, still encapsulated within Ethernet, are treated according to the SAN policies defined for that particular VSAN.

  • The multiplexer (mux) in the diagram represents the convergence point for Ethernet and FCoE traffic. This convergence enables both traffic types to travel on the same physical link between the switch and the connected server.

  • The next figure shows the ports that are used in FCoE.

  • ENodes present virtual Fibre Channel (VFC) interfaces in the form of Virtual Node (VN) Ports, which can establish FCoE virtual links using the VF Ports of the FCFs. The FCFs present VFC interfaces in the form of VF Ports or Virtual Expansion (VE) Ports. A VF Port establishes FCoE virtual links with the VN Port of a Cisco Network Assistant, and VE Ports enable FCFs to establish FCoE virtual links with one another. These interface types have their equivalents in native Fibre Channel N Ports, F Ports, and E Ports. FCoE takes the same Fibre Channel elements and ports and virtualizes them for use with consolidated I/O.

  • Note: You could say that FCoE consists of two protocols: FCoE and FIP (FCoE Initialization Protocol). FCoE is a data plane protocol and FIP is a control plane protocol. FIP is the FCoE control protocol that is responsible for establishing and maintaining Fibre Channel virtual links between pairs of FCoE devices (ENodes or FCFs). After the devices establish the virtual link, FCoE can transfer payloads over that virtual link; and FIP remains in the background to perform virtual link maintenance functions.

  • In addition to Fibre Channel and FCoE, iSCSI (Internet Small Computer Systems Interface) is another popular protocol for storage networking. It is particularly favored in environments where cost-efficiency and flexibility are primary concerns.

  • How iSCSI Works:

    • iSCSI operates by encapsulating SCSI commands over standard TCP/IP networks.

    • Unlike Fibre Channel, which requires dedicated hardware and infrastructure, iSCSI can run over existing Ethernet networks. This makes it a more accessible option for many organizations.

  • Advantages of iSCSI:

    • Cost-efficiency: iSCSI leverages existing Ethernet networks, reducing the need for additional, specialized hardware.

    • Flexibility: The widespread availability of IP networks allows iSCSI to be easily integrated into existing network infrastructures.

    • Ideal for remote storage and disaster recovery: iSCSI's ability to operate over IP networks makes it suitable for remote storage solutions and disaster recovery scenarios.

  • Considerations:

    • Latency: iSCSI may introduce slightly higher latency compared to Fibre Channel due to the overhead of TCP/IP. However, this is often a trade-off that organizations are willing to make for the benefits of cost and flexibility.

  • Use Cases:

    • iSCSI is particularly useful in environments where cost constraints prevent the deployment of Fibre Channel.

    • It is also ideal where integration with existing network infrastructure is paramount.

  • Fibre Channel, Fibre Channel over Ethernet, and iSCSI offer powerful, reliable solutions for enterprise storage, each with its unique strengths. Fibre Channel remains the gold standard for high-performance, dedicated storage networks, while FCoE provides a flexible, cost-efficient alternative by integrating storage traffic into existing Ethernet networks. iSCSI, on the other hand, offers an accessible, cost-effective solution that uses standard IP networks, making it ideal for a wide range of storage needs. Understanding these technologies is crucial for any organization looking to optimize its data center operations and future-proof its storage infrastructure.

PreviousSANNextMDS Switches

Last updated