Sunday, September 7, 2014

FCOE Design Considerations

  No comments    
categories: ,
#Cisco #Routers
#CCNA R&S, CCNP and CCIE Students

#Cisco Systems Engineer
#Specially Routing Students
# Network Engineers
#Cisco TAC Engineers
#Cisco CCIE Students- Data Centre Guys
#CCIE DC TAC Engineers


Fibre Channel over local area network (FCoE) could be a network technology that encapsulates Fibre Channel frames over local area network networks. this enables Fibre Channel to use ten Gigabit local area network networks (or higher speeds) whereas protective the Fibre Channel protocol. The specification was a part of the International Committee for data Technology Standards T11 FC-BB-5 customary printed in 2009.

FCoE maps Fibre Channel directly over local area network whereas being freelance of the local area network forwarding theme. The FCoE protocol specification replaces the FC0 and FC1 layers of the Fibre Channel stack with local area network. By holding the native Fibre Channel constructs, FCoE was meant to integrate with existing Fibre Channel networks and management package.
Data centers used local area network for TCP/IP networks and Fibre Channel for enclosure networks (SANs). With FCoE, Fibre Channel becomes another network protocol running on local area network, aboard ancient web Protocol (IP) traffic. FCoE operates directly on top of local area network within the network protocol stack, in distinction to iSCSI that runs on high of TCP and information processing. As a consequence, FCoE isn't routable at the information processing layer, and can not work across routed information processing networks.

Since classical local area network had no priority-based flow management, not like Fibre Channel, FCoE needed enhancements to the local area network customary to support a priority-based flow management mechanism (to cut back frame loss from congestion). The IEEE standards body additional priorities within the knowledge center bridging Task cluster.
Fibre Channel needed 3 primary extensions to deliver the capabilities of Fibre Channel over local area network networks:

Encapsulation of native Fibre Channel frames into local area network Frames.
Extensions to the local area network protocol itself to alter associate local area network material during which frames aren't habitually lost during times of congestion.
Mapping between Fibre Channel N_port IDs (aka FCIDs) and local area network mack addresses.
"Converged" network adapter

Computers will connect with FCoE with converged network adapters (CNAs), that contain each Fibre Channel host bus adapter (HBA) and local area network Network Interface Card (NIC) practicality on a similar adapter card. CNAs have one or additional physical local area network ports. FCoE encapsulation are often wiped out package with a traditional local area network network interface card, but FCoE CNAs offload (from the CPU) the low level frame process and small computer system interface protocol functions historically performed by Fibre Channel host bus adapters




Most deployments will (should) have redundant 5k’s as part of the setup.  So let’s take a look at a pretty common setup that you might see out in the wild from a logical perspective.  Drawing1


So this can be however i prefer to gestate the fundamental setup (Yes I do know I’m missing items, this can be the ‘big picture’). each the native FC storage and therefore the knowledge network terminate into the 5Ks.  At that time, the FC VSAN gets mapped to a VLAN.

The VLAN is what’s passed to the 2K and on to the server. therefore in my illustration, the inexperienced links area unit storage and therefore the orange area unit knowledge.  Pretty easy right?  I’m hoping you caught the actual fact that the link between the 5Ks solely shows the info network. have you ever worked out why? although we tend to map the VSAN to a VLAN its still for the foremost half ‘its own thing’.

That being aforesaid, commonplace FC style ideas inherit play. one in every of those being having twin materials to every server.  If we tend to allowed that VLAN across the trunk between the 2 5Ks we’d be breaking that rule.  You’ll conjointly have to be compelled to take things like MPIO under consideration furthermore since you’ll have redundant active methods to identical storage. the info network remains trunked between the 5Ks to facilitate a VPC configuration.  Now, on to the config



0 comments:

Post a Comment

Popular Posts