1 / 16

Integration of FCoE into SM-HBA-2 Architecture: Overview and Implications

This document provides a comprehensive overview of the integration of Fibre Channel over Ethernet (FCoE) into the SM-HBA-2 architecture. It details the physical and logical elements of Host Bus Adapters (HBAs), including their configurations, performance statistics, and the implications of adding FCoE functionality. Key terminologies such as VN_Port, ENode, and various traffic counters are outlined, along with potential enhancements to the existing architecture. For best clarity, the presentation version (PPT) is recommended due to some unclear slides in the PDF.

sidone
Télécharger la présentation

Integration of FCoE into SM-HBA-2 Architecture: Overview and Implications

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. SM-HBA-2:Integrating FCoE T11/09-530v0 1 October 2009 bob.nixon@emulex.com NOTE: The pdf is unclear on a few slides. Please use the ppt if possible.

  2. Physical HBA 0-1 0-1 PHBA handle, manufacturer, model #, serial #, # Ports 1 0-1 0-1 0-n 0-1 0-n FC Port Fabric Bus Address FC Phy Port statistics Fabric/Nx_Port Phy statistics Protocol statistics HBA 0-n 1 1 1 Phy index, speed, topology, physical attributes VF_ID, in-order delivery, … Fabric name VFID, inorder,… VFID mask variants for different standard buses HBA handle, manufacturer,model #, serial #, firmware version, ... # of Ports traffic counters: frames, words traffic counters: frames, words link error counters FC-4 TYPE, I/O counters: Input operations, output operations, control operations Port index, Port name, Port address, Fabric name, ... # of Phys=1 Fabric/Phy 0-n 0-1 VFID Mask, Port VFID 0-1 1-n 0-n 0-n 1 1 0-n 1 Review the SM-HBA-2 Architecture for FC Bold borders: physical objects

  3. Review the FC-FS-3 Architecture

  4. Physical HBA 0-1 0-1 PHBA handle, manufacturer, model #, serial #, # Ports 1 0-1 0-1 0-n 0-1 0-n VN_Port statistics Fabric/VN_Port PN_Port HBA FC Port VN_Port Fabric/Nx_Port PN_Port statistics Fabric Port statistics Bus Address Protocol statistics Phy statistics FC-4 statistics FC Phy 1 0-n 1 1 Fabric name VFID, inorder,… VFID mask traffic counters: frames, words Port index, Port name, Port address, Fabric name, ... # of Phys=1 traffic counters: frames, words link error counters HBA handle, manufacturer,model #, serial #, firmware version, ... # of Ports Phy index, speed, topology, physical attributes VF_ID, in-order delivery, … Phy index, speed, topology, physical attributes FC-4 TYPE, I/O counters: Input operations, output operations, control operations traffic counters: frames, words link error counters Port index, Port name, Port address, Fabric name, ... # of Phys=1 variants for different standard buses VF_ID, in-order delivery, … traffic counters: frames, words FC-4 TYPE, I/O counters: Input operations, output operations, control operations Fabric/Phy Fabric/PN_Port 0-1 0-n VFID Mask, Port VFID VFID Mask, Port VFID 0-1 1-n 0-n 0-n 1 1 0-n 1  Terminology Translation Bold borders: physical objects

  5. Review FC-BB_E Architecture

  6. What does FC-BB_E have that we don’t??? • FCoE_LEPs • VN_Port MAC address/VLAN ID

  7. What does FC-BB_E have that we don’t??? • FCoE_LEPs • VN_Port MAC address/VLAN ID • Virtual Links • VN_Port MAC address/VLAN ID and FCF-MAC address • economize: a VL is tied to one FCoE_LEP…combine them

  8. What does FC-BB_E have that we don’t??? • FCoE_LEPs • VN_Port MAC address/VLAN ID and FCF-MAC address • Lossless Ethernet MACs • ENode MAC address • …or multiple ENode MAC addresses! There’s a better place

  9. What does FC-BB_E have that we don’t??? • FCoE_LEPs • VN_Port MAC address/VLAN ID and FCF-MAC address • Lossless Ethernet MACs • Ethernet Ports • Physical attributes, e.g., speed • economize: E’ports are 1-1 with a MAC, so combine

  10. What does FC-BB_E have that we don’t??? • FCoE_LEPs • VN_Port MAC address/VLAN ID and FCF-MAC address • Lossless Ethernet MACs • Physical attributes, e.g., speed • FCoE Controllers • ENode MAC address! • FC-BB_E VLAN mask

  11. What does FC-BB_E have that we don’t??? • FCoE_LEPs • VN_Port MAC address/VLAN ID and FCF-MAC address • Lossless Ethernet MACs • Physical attributes, e.g., speed • FCoE Controllers • ENode MAC address • FC-BB_E VLAN mask • Lossless Ethernet Networks • economy: associate any interesting LAN attributes with the MAC

  12. What does FC-BB_E have that we don’t??? Summary: We need: • FCoE_LEPs • VN_Port MAC address/VLAN ID and FCF-MAC address • Lossless Ethernet MACs • Physical attributes, e.g., speed • FCoE Controllers • ENode MAC address • FC-BB_E VLAN mask

  13. Physical HBA 0-1 0-1 PHBA handle, manufacturer, model #, serial #, # Ports 1 0-1 0-1 0-n 0-n 0-1 0-n Port Fabric/VN_Port Fabric Bus Address HBA PHY statistics Protocol statistics PHY Port statistics PHY 0-n 1 1 1 HBA handle, manufacturer,model #, serial #, firmware version, ... # of Ports Phy index, speed, topology, physical attributes VF_ID, in-order delivery, … Fabric name VFID, inorder,… VFID mask Port index, Port name, Port address, Fabric name, ... # of Phys=1 traffic counters: frames, words link error counters variants for different standard buses traffic counters: frames, words FC-4 TYPE, I/O counters: Input operations, output operations, control operations Phy index, speed, topology, physical attributes Fabric/PHY 0-1 0-n 0-1 VFID Mask, Port VFID 0-1 1-n 0-n 0-n 1 1 0-n 1  Adding FCoE into the SM-HBA-2 Architecture Bold borders: physical objects

  14. Physical HBA 0-1 0-1 PHBA handle, manufacturer, model #, serial #, # Ports 1 0-1 0-1 1 0-n 0-1 0-n VN_Port ENode Controller Fabric Bus Address FCoE PHY (Lossless E’net MAC) PHY statistics Protocol statistics Port statistics Fabric/VN_Port HBA 1 0-n 1 1 HBA handle, manufacturer,model #, serial #, firmware version, ... # of Ports Enode MAC address, FC-BB_E VLAN mask traffic counters: frames, words FC-4 TYPE, I/O counters: Input operations, output operations, control operations traffic counters: frames, words link error counters Fabric name VFID, inorder,… VFID mask VF_ID, in-order delivery, … Phy index, speed, topology (?), physical attributes Port index, Port name, Port address, Fabric name, ... # of Phys=1 variants for different standard buses FCoE_LEP Fabric/PHY 0-n 0-n 0-1 Addresses* VFID Mask, Port VFID 0-1 1-n 0-n 0-n 1 1 1 0-n  Adding FCoE into the SM-HBA-2 Architecture Bold borders: physical objects *Addresses: VN_Port MAC,FCF_MAC,VLAN ID

  15. And then there are all the functions… • Most carry over… • But need to modify some parameters from earlier presentations • And create ENode MACs • We’ll go there later

  16. Discussion? 16

More Related