FCOE
1
FCoE maps Fibre Channel directly over Ethernet while being independent of the Et hernet forwarding scheme. The FCoE protocol specification replaces the FC0 and F C1 layers of the Fibre Channel stack with Ethernet. By retaining the native Fibr e Channel constructs, FCoE was meant to integrate with existing Fibre Channel ne tworks and management software. Data centers used Ethernet for TCP/IP networks and Fibre Channel for storage are a networks (SANs). With FCoE, Fibre Channel becomes another network protocol run ning on Ethernet, alongside traditional Internet Protocol (IP) traffic. FCoE ope rates directly above Ethernet in the network protocol stack, in contrast to iSCS I which runs on top of TCP and IP. As a consequence, FCoE is not routable at the IP layer, and will not work across routed IP networks. Since classical Ethernet had no priority-based flow control, unlike Fibre Channe l, FCoE required enhancements to the Ethernet standard to support a priority-bas ed flow control mechanism (to reduce frame loss from congestion). The IEEE stand ards body added priorities in the data center bridging Task Group. Fibre Channel required three primary extensions to deliver the capabilities of F ibre Channel over Ethernet networks: Encapsulation of native Fibre Channel frames into Ethernet Frames. Extensions to the Ethernet protocol itself to enable an Ethernet fabric in which frames are not routinely lost during periods of congestion. Mapping between Fibre Channel N_port IDs (aka FCIDs) and Ethernet MAC addresses. "Converged" network adapter Computers can connect to FCoE with converged network adapters (CNAs), which cont ain both Fibre Channel host bus adapter (HBA) and Ethernet Network Interface Car d (NIC) functionality on the same adapter card. CNAs have one or more physical E thernet ports. FCoE encapsulation can be done in software with a conventional Et hernet network interface card, however FCoE CNAs offload (from the CPU) the low level frame processing and SCSI protocol functions traditionally performed by Fi bre Channel host bus adapters. Application[edit] The main application of FCoE is in data center storage area networks (SANs). FCo E has particular application in data centers due to the cabling reduction it mak es possible, as well as in server virtualization applications, which often requi re many physical I/O connections per server. With FCoE, network (IP) and storage (SAN) data traffic can be consolidated using a single network. This consolidation can: reduce the number of network interface cards required to connect to disparate st orage and IP networks reduce the number of cables and switches reduce power and cooling costs
description
FCoE maps Fibre Channel directly over Ethernet while being independent of the Ethernet forwarding scheme. The FCoE protocol specification replaces the FC0 and FC1 layers of the Fibre Channel stack with Ethernet. By retaining the native Fibre Channel constructs, FCoE was meant to integrate with existing Fibre Channel networks and management software.Data centers used Ethernet for TCP/IP networks and Fibre Channel for storage area networks (SANs). With FCoE, Fibre Channel becomes another network protocol running on Ethernet, alongside traditional Internet Protocol (IP) traffic. FCoE operates directly above Ethernet in the network protocol stack, in contrast to iSCSI which runs on top of TCP and IP. As a consequence, FCoE is not routable at the IP layer, and will not work across routed IP networks.Since classical Ethernet had no priority-based flow control, unlike Fibre Channel, FCoE required enhancements to the Ethernet standard to support a priority-based flow control mechanism (to reduce frame loss from congestion). The IEEE standards body added priorities in the data center bridging Task Group.Fibre Channel required three primary extensions to deliver the capabilities of Fibre Channel over Ethernet networks:Encapsulation of native Fibre Channel frames into Ethernet Frames.Extensions to the Ethernet protocol itself to enable an Ethernet fabric in which frames are not routinely lost during periods of congestion.Mapping between Fibre Channel N_port IDs (aka FCIDs) and Ethernet MAC addresses."Converged" network adapterComputers can connect to FCoE with converged network adapters (CNAs), which contain both Fibre Channel host bus adapter (HBA) and Ethernet Network Interface Card (NIC) functionality on the same adapter card. CNAs have one or more physical Ethernet ports. FCoE encapsulation can be done in software with a conventional Ethernet network interface card, however FCoE CNAs offload (from the CPU) the low level frame processing and SCSI protocol functions traditionally performed by Fibre Channel host bus adapters.Application[edit]The main application of FCoE is in data center storage area networks (SANs). FCoE has particular application in data centers due to the cabling reduction it makes possible, as well as in server virtualization applications, which often require many physical I/O connections per server.With FCoE, network (IP) and storage (SAN) data traffic can be consolidated using a single network. This consolidation can:reduce the number of network interface cards required to connect to disparate storage and IP networksreduce the number of cables and switchesreduce power and cooling costs
Transcript of FCOE
FCoE maps Fibre Channel directly over Ethernet while being independent of the Ethernet forwarding scheme. The FCoE protocol specification replaces the FC0 and FC1 layers of the Fibre Channel stack with Ethernet. By retaining the native Fibre Channel constructs, FCoE was meant to integrate with existing Fibre Channel networks and management software.
Data centers used Ethernet for TCP/IP networks and Fibre Channel for storage area networks (SANs). With FCoE, Fibre Channel becomes another network protocol running on Ethernet, alongside traditional Internet Protocol (IP) traffic. FCoE operates directly above Ethernet in the network protocol stack, in contrast to iSCSI which runs on top of TCP and IP. As a consequence, FCoE is not routable at the IP layer, and will not work across routed IP networks.
Since classical Ethernet had no priority-based flow control, unlike Fibre Channel, FCoE required enhancements to the Ethernet standard to support a priority-based flow control mechanism (to reduce frame loss from congestion). The IEEE standards body added priorities in the data center bridging Task Group.
Fibre Channel required three primary extensions to deliver the capabilities of Fibre Channel over Ethernet networks:
Encapsulation of native Fibre Channel frames into Ethernet Frames.Extensions to the Ethernet protocol itself to enable an Ethernet fabric in which frames are not routinely lost during periods of congestion.Mapping between Fibre Channel N_port IDs (aka FCIDs) and Ethernet MAC addresses.
"Converged" network adapterComputers can connect to FCoE with converged network adapters (CNAs), which contain both Fibre Channel host bus adapter (HBA) and Ethernet Network Interface Card (NIC) functionality on the same adapter card. CNAs have one or more physical Ethernet ports. FCoE encapsulation can be done in software with a conventional Ethernet network interface card, however FCoE CNAs offload (from the CPU) the low level frame processing and SCSI protocol functions traditionally performed by Fibre Channel host bus adapters.
Application[edit]The main application of FCoE is in data center storage area networks (SANs). FCoE has particular application in data centers due to the cabling reduction it makes possible, as well as in server virtualization applications, which often require many physical I/O connections per server.
With FCoE, network (IP) and storage (SAN) data traffic can be consolidated using a single network. This consolidation can:
reduce the number of network interface cards required to connect to disparate storage and IP networksreduce the number of cables and switchesreduce power and cooling costs
