FCOE_技术介绍.ppt

* * * * * * * * * * * * * * * * * * * * * * * * Unchanged from previous FC standard VN_Port: Virtual N_Port VF_Port: Virtual F_Port VE_Port: Virtual E_Port Added to support FCoE FCoE_LEP (FCoE Link Endpoint): The data forwarding component that handles FC frame encapsulation/decapsulation, and transmission/reception of FCoE frames. FCoE Controller: the entity that implement the FIP protocol FC-BB-5 TERMINOLOGY FCOE: INITIAL DEPLOYMENT FCOE: ADDING BLADE SERVERS FCOE: ADDING NATIVE FCOE STORAGE FCOE: ADDING VE_PORTS FCoE frames have: MAC addresses (hop-by-hop) FC addresses (end-to-end) FCOE ADDRESSING AND FORWARDING FCOE MAC ADDRESSES VE_Ports and VF_Ports always use MAC addresses derived from the switch pool VN_Ports may use two types of MAC addresses: SPMA (Server Provided MAC Addresses) FPMA (Fabric Provided MAC Addresses) MAC Addresses are negotiated in FIP Initial deployment will use FPMA only THE MAPPED MAC ADDRESSES A dedicated MAC address for each FC-ID Assigned by the FC fabrics Consistent with the FC model OUIs with U/L = 1 (Local addressing), called FC-MAPs Multiple FC-MAPs may be supported (one per FC fabric) INITIAL LOGIN FLOW LADDER 1, 2, 4, (8), 10 Gbps 1, 10 . . . Gbps 10, 20 Gbps THE MOST ASKED QUESTION: IS FCOE ROUTABLE? FCoE IS FCOE ROUTABLE? Most folks mean “Is FCoE IP-routable” The answer is NO, there is no IP layer in FCoE This was a design goal to keep FCoE simple FC-BB-5 contains FCIP that is “IP-routable” FCoE is FC-routable FCoE switches may forward FC frames across different Ethernet clouds FCoE switches may forward FC frames over the Internet using FCIP STANDARDS STATUS Feature / Standard Standards Status Priority Flow Control (PFC)IEEE 802.1Qbb PAR approved, Editor Claudio De Santi (Cisco), 1st draft published, expected approval 04/09 Bandwidth Management IEEE 802.1Qaz PAR approved, Editor Craig Carlson (Qlogic), 1st draft published, expected approval 07/09 Congestion Management IEEE 802.1Qau PAR approved, in advanced development