{"id":3824,"date":"2022-10-27T11:03:30","date_gmt":"2022-10-27T11:03:30","guid":{"rendered":"https:\/\/wiki.thomasandsofia.com\/?p=3824"},"modified":"2022-10-28T21:52:50","modified_gmt":"2022-10-28T21:52:50","slug":"ns-san-storage","status":"publish","type":"post","link":"https:\/\/wiki.thomasandsofia.com\/?p=3824","title":{"rendered":"N&#038;S SAN Storage"},"content":{"rendered":"<p><a href=\"\/nas-and-san-storage\/\">Home<\/a><\/p>\n<h1>Fibre Channel Part 1 &#8211; FCP and WWPN<\/h1>\n<p><a href=\"https:\/\/learn.flackbox.com\/courses\/81445\/lectures\/5204536\" target=\"_blank\" rel=\"noopener\">https:\/\/learn.flackbox.com\/courses\/81445\/lectures\/5204536<\/a><\/p>\n<h2>Terminology<\/h2>\n<p><strong>Aliases: Easy to identify WWPNs and WWNNs<\/strong><\/p>\n<ul>\n<li>Alias EXCHANGE-SERVER = WWPN 01:23:45:67:89:ab:cd:ef<\/li>\n<li>Configurable on both storage systems and Switches<\/li>\n<li>Much easier to identify during troubleshooting and configuration<\/li>\n<\/ul>\n<p><strong>Client: The host accessing storage<\/strong><\/p>\n<p><strong>FC HBA: Fibre Channel Host Bus Adaptor<\/strong><\/p>\n<ul>\n<li>See <strong>HBA<\/strong><\/li>\n<\/ul>\n<p><strong>FCP: Fibre Channel Protocol<\/strong><\/p>\n<ul>\n<li>SAN specific. Original SAN protocol but still very popular<\/li>\n<li>Dedicated hardware, adapters, switches on all layers of the OSI model<\/li>\n<li>Used to send SCSi commands over the Fibre Channel network<\/li>\n<li>Very stable and reliable. Lossless, unlike TCP and UDP<\/li>\n<li>Bandwidths of 1, 2, 4, 8, 16, 32, 128 Gbps<\/li>\n<li>Uses WWN World Wide Names for addressing<\/li>\n<\/ul>\n<p><strong>HBA: Host Bus Adaptor<\/strong><\/p>\n<ul>\n<li>Controller board for network ports. Often plug into the MoBo&#8217;s PCIe slots<\/li>\n<li>Possible to have Multi-port HBAs<\/li>\n<li>Generally used for Fibre Channel Ports(<strong>FC HBA<\/strong>)<\/li>\n<\/ul>\n<p><strong>LUN: Logical Unit Number<\/strong><\/p>\n<ul>\n<li>Represents a disk that will be presented to the host.<\/li>\n<li>Can be thought of as a Storage device. Might be a disk partition, whole disk, or combination of disks.<\/li>\n<li>Used with SAN<\/li>\n<\/ul>\n<p><strong>NAS: Network Attached Storage<\/strong><\/p>\n<ul>\n<li>File level. Typical shared storage between multiple usesrs<\/li>\n<li>Cannot be used to boot a device<\/li>\n<\/ul>\n<p><strong>SAN: Storage Area Network<\/strong><\/p>\n<ul>\n<li>Block level. Appears as a disk mounted directly to the device.<\/li>\n<li>Can be used to boot a device<\/li>\n<\/ul>\n<p><strong>SCSI: Small Computer System Interface<\/strong><\/p>\n<p><strong>Target: The storage system<\/strong><\/p>\n<p><strong>WWN: World Wide Names<\/strong><\/p>\n<ul>\n<li>8 byte address of 16 hex characters &#8211; 01:23:45:67:89:ab:cd:ef<\/li>\n<\/ul>\n<p><strong>WWNN: World Wide Node Name<\/strong><\/p>\n<ul>\n<li>Assigned to a node in the storage network<\/li>\n<li>A WWNN can identify multiple network interfaces of a single network node\n<ul>\n<li>You might have a multi-port HBA<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<p><strong>WWPN: World Wide Port Name<\/strong><\/p>\n<ul>\n<li>Like a MAC address. You can only have 1 WWPN per port (Physical Interface)\n<ul>\n<li>Globally unique<\/li>\n<li>Burned into each port by manufacturer<\/li>\n<\/ul>\n<\/li>\n<li>Multi-port HBAs will have different WWPNs on each port<\/li>\n<li>Primarily concerned with WWPNs vs WWNNs when configuring Fibre Channel networks.<\/li>\n<\/ul>\n<h1><\/h1>\n<h1>Fibre Channel Part 2 &#8211; Security<\/h1>\n<p><a href=\"https:\/\/learn.flackbox.com\/courses\/81445\/lectures\/5204538\" target=\"_blank\" rel=\"noopener\">https:\/\/learn.flackbox.com\/courses\/81445\/lectures\/5204538<\/a><\/p>\n<p><strong>Zoning<\/strong><br \/>\n<a href=\"https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2022\/10\/Zoning.png\"><img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-full wp-image-3825\" src=\"https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2022\/10\/Zoning.png\" alt=\"\" width=\"1063\" height=\"583\" srcset=\"https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2022\/10\/Zoning.png 1063w, https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2022\/10\/Zoning-300x165.png 300w, https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2022\/10\/Zoning-1024x562.png 1024w, https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2022\/10\/Zoning-768x421.png 768w, https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2022\/10\/Zoning-150x82.png 150w\" sizes=\"auto, (max-width: 1063px) 100vw, 1063px\" \/><\/a><\/p>\n<ul>\n<li>Zoning is configured on the switches to control which hosts are allowed to communicate with each other<\/li>\n<li>Initiators (servers) will be allowed to communicate with targets (storage systems) but initiators will not be allowed to communicate with each other of Fibre Channel\n<ul>\n<li>Initiators talk to each other over TCP, not FCP<\/li>\n<\/ul>\n<\/li>\n<li>Note that in the diagram, both hosts connect to the storage over the same WWPN (NETAPP-CTRL1)<\/li>\n<li>Zoning is generally configured on 1 switch then configured to auto-replicated to others<\/li>\n<li><span style=\"color: #ff0000;\">Zoning prevents unauthorized hosts from reaching the storage system, but does not prevent a host from accessing the wrong LUN!\u00a0 See LUN Masking<\/span><\/li>\n<\/ul>\n<p><strong>Zone Set: A group of Zone configurations<\/strong><\/p>\n<ul>\n<li>See Zone diagram<\/li>\n<\/ul>\n<h2><strong>LUN Masking<\/strong><\/h2>\n<p><a href=\"https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2022\/10\/LUN-Masking.png\"><img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-full wp-image-3830\" src=\"https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2022\/10\/LUN-Masking.png\" alt=\"\" width=\"1087\" height=\"585\" srcset=\"https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2022\/10\/LUN-Masking.png 1087w, https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2022\/10\/LUN-Masking-300x161.png 300w, https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2022\/10\/LUN-Masking-1024x551.png 1024w, https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2022\/10\/LUN-Masking-768x413.png 768w, https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2022\/10\/LUN-Masking-150x81.png 150w\" sizes=\"auto, (max-width: 1087px) 100vw, 1087px\" \/><\/a><\/p>\n<ul>\n<li>Used to ensure the correct host is connecting to the correct LUN.\n<ul>\n<li>In the Zone diagram, both hosts can reach all LUNs on the storage.<\/li>\n<li>This can cause corrupt data and is a security concern.<\/li>\n<\/ul>\n<\/li>\n<li>Configured on the Storage system to lock a LUN down to the host or hosts authorized to access it.<\/li>\n<li><span style=\"color: #ff0000;\">To secure storage, you need to configure Zoning on the Switches and LUN Masking on the Storage systems<\/span><\/li>\n<\/ul>\n<h1><\/h1>\n<h1>Fibre Channel Part 3 &#8211; Fabric Login<\/h1>\n<p><a href=\"https:\/\/learn.flackbox.com\/courses\/81445\/lectures\/5204537\" target=\"_blank\" rel=\"noopener\">https:\/\/learn.flackbox.com\/courses\/81445\/lectures\/5204537<\/a><\/p>\n<h2>Switch Domain IDs<\/h2>\n<ul>\n<li>Each switch in the Fibre Channel network is assigned a unique Domain ID<\/li>\n<li>One switch is automatically assigned as the Principle Switch.\n<ul>\n<li>The Principle switch assigns the Domain IDs to the other switches<\/li>\n<\/ul>\n<\/li>\n<li>Each switch learns about the other switches in the network and how to route to them based on their Domain ID.<\/li>\n<\/ul>\n<h2>FLOGI Fabric Login<\/h2>\n<p><a href=\"https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2022\/10\/flogi.png\"><img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-full wp-image-3832\" src=\"https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2022\/10\/flogi.png\" alt=\"\" width=\"751\" height=\"412\" srcset=\"https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2022\/10\/flogi.png 751w, https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2022\/10\/flogi-300x165.png 300w, https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2022\/10\/flogi-150x82.png 150w\" sizes=\"auto, (max-width: 751px) 100vw, 751px\" \/><\/a><\/p>\n<ul>\n<li>When a server or storage&#8217;s HBA powers on, it sends a FLOGI (Fabric LOGIn) request to its locally attached Fibre channel switch.\n<ul>\n<li>FLOGI Request includes the HBA Port&#8217;s WWPN<\/li>\n<\/ul>\n<\/li>\n<li>The switch will assign it a 24 bit FCID Fibre Channel ID address<\/li>\n<li>The FCID assigned to hosts is made up of the switch&#8217;s Domain ID and the switch port the host is plugged into<\/li>\n<li>FCIDs are similar to IP addresses (but not exactly). It&#8217;s used byfibre channel switches to route traffic between servers and their storage<\/li>\n<li>Switches maintain a table of FCID to WWPN address mappings and which port the host is located on.<\/li>\n<\/ul>\n<h2>FCNS Fibre Channel Name Service<\/h2>\n<p><a href=\"https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2022\/10\/fcns.png\"><img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-full wp-image-3833\" src=\"https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2022\/10\/fcns.png\" alt=\"\" width=\"1434\" height=\"788\" srcset=\"https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2022\/10\/fcns.png 1434w, https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2022\/10\/fcns-300x165.png 300w, https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2022\/10\/fcns-1024x563.png 1024w, https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2022\/10\/fcns-768x422.png 768w, https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2022\/10\/fcns-150x82.png 150w\" sizes=\"auto, (max-width: 1434px) 100vw, 1434px\" \/><\/a><\/p>\n<ul>\n<li>Fibre channel switches share the FLOGI database information with each other using the FCNS Fibre Channel Name Service<\/li>\n<li>Each switch in the network learns where each WWPN is and how to route traffic.<\/li>\n<\/ul>\n<h2>PLOGI Port Login<\/h2>\n<p><a href=\"https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2022\/10\/Zoning.png\"><img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-full wp-image-3825\" src=\"https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2022\/10\/Zoning.png\" alt=\"\" width=\"1063\" height=\"583\" srcset=\"https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2022\/10\/Zoning.png 1063w, https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2022\/10\/Zoning-300x165.png 300w, https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2022\/10\/Zoning-1024x562.png 1024w, https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2022\/10\/Zoning-768x421.png 768w, https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2022\/10\/Zoning-150x82.png 150w\" sizes=\"auto, (max-width: 1063px) 100vw, 1063px\" \/><\/a><\/p>\n<ul>\n<li>After the FLOGI Fabric Login process is complete, the initiator will send the PLOGI Port Login.<\/li>\n<li>Based on the zoning configuration on the switch, the host will learn its available target WWPNs<\/li>\n<\/ul>\n<h2>PRLI Process Login<\/h2>\n<ul>\n<li>Finally, the initiator host will send a PRLI Proccess Login to its target storage.<\/li>\n<li>The storage system will grant access to the host based on its configured LUN masking.<\/li>\n<\/ul>\n<h2>Conclusion<\/h2>\n<p>As long as LUN masking is setup on the Storage and Zoning is configured on the switches, all of this happens automatically!<\/p>\n<p>&nbsp;<\/p>\n<h1>Fibre Channel Part 4 &#8211; Redundancy and Multipathing<\/h1>\n<p><a href=\"https:\/\/learn.flackbox.com\/courses\/81445\/lectures\/5204539\" target=\"_blank\" rel=\"noopener\">https:\/\/learn.flackbox.com\/courses\/81445\/lectures\/5204539<\/a><\/p>\n<h2>Redundant SAN Fabrics<\/h2>\n<p><a href=\"https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2022\/10\/redundantsan.png\"><img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-full wp-image-3835\" src=\"https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2022\/10\/redundantsan.png\" alt=\"\" width=\"1362\" height=\"768\" srcset=\"https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2022\/10\/redundantsan.png 1362w, https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2022\/10\/redundantsan-300x169.png 300w, https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2022\/10\/redundantsan-1024x577.png 1024w, https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2022\/10\/redundantsan-768x433.png 768w, https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2022\/10\/redundantsan-150x85.png 150w\" sizes=\"auto, (max-width: 1362px) 100vw, 1362px\" \/><\/a><\/p>\n<p>&nbsp;<\/p>\n<ul>\n<li>Storage is mission critical. Access should provide no single point of failure.<\/li>\n<li>Redundant Fibre Channel networks should be put in place, known as Fabric A and Fabric B (or SAN A and SAN B)<\/li>\n<li>Each server and storage system host will be connected to both fabrics with redundant HBA Ports.<\/li>\n<li>Fibre Channel switches distribute shared information to each other such as Domain IDs, the FCNS database, and zoning.<\/li>\n<li><span style=\"color: #ff0000;\">If an error in Fabric A was able to propagate to Fabric B, this would bring down both fabrics and drop the servers connection to their storage.<\/span><\/li>\n<li>For this reason switches in different sides of the fabric are NOT cross connected to each other. Both sides of the fabric are kept physically separate<\/li>\n<li>End hosts are connected to both fabrics, but the switches are not.<\/li>\n<\/ul>\n<h3>True Redundant Configuration<\/h3>\n<p>This would include redundant Storage Controllers as well as redundant servers!<\/p>\n<p><a href=\"https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2022\/10\/redundant2.png\"><img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-full wp-image-3836\" src=\"https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2022\/10\/redundant2.png\" alt=\"\" width=\"1218\" height=\"784\" srcset=\"https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2022\/10\/redundant2.png 1218w, https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2022\/10\/redundant2-300x193.png 300w, https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2022\/10\/redundant2-1024x659.png 1024w, https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2022\/10\/redundant2-768x494.png 768w, https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2022\/10\/redundant2-150x97.png 150w\" sizes=\"auto, (max-width: 1218px) 100vw, 1218px\" \/><\/a><\/p>\n<p>&nbsp;<\/p>\n<h3>TPG Target Portal Groups<\/h3>\n<p><a href=\"https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2022\/10\/tpg.png\"><img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-full wp-image-3837\" src=\"https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2022\/10\/tpg.png\" alt=\"\" width=\"1203\" height=\"333\" srcset=\"https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2022\/10\/tpg.png 1203w, https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2022\/10\/tpg-300x83.png 300w, https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2022\/10\/tpg-1024x283.png 1024w, https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2022\/10\/tpg-768x213.png 768w, https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2022\/10\/tpg-150x42.png 150w\" sizes=\"auto, (max-width: 1203px) 100vw, 1203px\" \/><\/a><\/p>\n<ul>\n<li>All ports on the storage system which initiators can access their storage through are added to a Target Portal Group<\/li>\n<li>Example: Ports CTRL1-A,CTRL1-B,CTRL2-A,CTRL2-B are added to a Target Portal Group<\/li>\n<li>Used for Security and\/or Performance<\/li>\n<\/ul>\n<h2>ALUA &#8211; Asymmetric Logical Unit Assignment<\/h2>\n<ul>\n<li>Defines Optimized paths for connection to the LUN.<\/li>\n<li>There are likely 2 or of these as long as\n<ul>\n<li>The number of &#8220;hops&#8221; remains the same.<\/li>\n<li>You terminate at the controller that owns the desired LUN<\/li>\n<\/ul>\n<\/li>\n<li>These can easily go through both Fabric A or Fabric B since &#8216;hop counts&#8217; would be the same.<\/li>\n<\/ul>\n<h2>Multipathing<\/h2>\n<ul>\n<li>During the Process Login, initiators will detect ports available to connect to their storage in the TPG (Target Portal Group) and ALUA will notify which are the preferred paths.<\/li>\n<li>Multipathing software on the initiator will choose which path or paths to take to the storage.\n<ul>\n<li>Will typically take the optimized path<\/li>\n<\/ul>\n<\/li>\n<li>All popular operating systems have multipathing software which supports active\/active or active\/standby paths.\n<ul>\n<li>Active\/Active should auto load balance.<\/li>\n<\/ul>\n<\/li>\n<li>The client will automatically fail over to an alternate path if the one it is using fails.<\/li>\n<\/ul>\n<h2>Conclusion<\/h2>\n<ul>\n<li>Client connectivity to SAN storage is fundamentally different to how Ethernet networking works\n<ul>\n<li>In Ethernet networking, all of the routing and switching decisions are handled by network infrastructure devices<\/li>\n<li>In SAN storage, multipathing intelligence is enabled on the client end hosts.<\/li>\n<\/ul>\n<\/li>\n<li>In Fibre Channel, the initiator will automatically detect the available paths to its storage through the FLOGI, PLOGI and PRLI process<\/li>\n<li>Multipathing software on the initiator will then choose which path or paths to use.<\/li>\n<\/ul>\n<h1><\/h1>\n<h1>FCoE Overview<\/h1>\n<p><a href=\"https:\/\/learn.flackbox.com\/courses\/81445\/lectures\/5208174\" target=\"_blank\" rel=\"noopener\">https:\/\/learn.flackbox.com\/courses\/81445\/lectures\/5208174<\/a><\/p>\n<p>FCoE &#8211; Fibre Channel over Ethernet<\/p>\n<ul>\n<li>Viewed as &#8220;The Next Big Thing&#8221; in storage networking when it first came out.\n<ul>\n<li>Has been falling out of favor over the past few years.<\/li>\n<li>More likely to find ISCI when deploying SAN over an Ethernet network.<\/li>\n<\/ul>\n<\/li>\n<li>All MFGs support it.<\/li>\n<li>FCoE became possible with 10Gbps Ethernet. Enough bandwidth to support both data and storage traffic on the same physical network infrastructure.\n<ul>\n<li>1G was a bit too slow.<\/li>\n<\/ul>\n<\/li>\n<li>FCoE uses the FCP (Fibre Channel Protocol), but encapsulates it in an Ethernet header<\/li>\n<li>QOS is used to guarantee the required bandwidth to the storage traffic<\/li>\n<li>It retains the reliability and performance of Fibre Channel<\/li>\n<\/ul>\n<h3>Traditional FC Network<\/h3>\n<p><a href=\"https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2022\/10\/fcoe.png\"><img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-full wp-image-3838\" src=\"https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2022\/10\/fcoe.png\" alt=\"\" width=\"1301\" height=\"828\" srcset=\"https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2022\/10\/fcoe.png 1301w, https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2022\/10\/fcoe-300x191.png 300w, https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2022\/10\/fcoe-1024x652.png 1024w, https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2022\/10\/fcoe-768x489.png 768w, https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2022\/10\/fcoe-150x95.png 150w\" sizes=\"auto, (max-width: 1301px) 100vw, 1301px\" \/><\/a><\/p>\n<ul>\n<li>There are\n<ul>\n<li>4 ports\n<ul>\n<li>2 Ethernet NICs<\/li>\n<li>2 FC HBAs<\/li>\n<\/ul>\n<\/li>\n<li>4 Cables<\/li>\n<li>4 Switches<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<h3>FCoE Network<\/h3>\n<p><a href=\"https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2022\/10\/fcoe2.png\"><img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-full wp-image-3839\" src=\"https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2022\/10\/fcoe2.png\" alt=\"\" width=\"1248\" height=\"694\" srcset=\"https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2022\/10\/fcoe2.png 1248w, https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2022\/10\/fcoe2-300x167.png 300w, https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2022\/10\/fcoe2-1024x569.png 1024w, https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2022\/10\/fcoe2-768x427.png 768w, https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2022\/10\/fcoe2-150x83.png 150w\" sizes=\"auto, (max-width: 1248px) 100vw, 1248px\" \/><\/a><\/p>\n<ul>\n<li>Shared Infrastructure using 10Gbps.<\/li>\n<li>Does require a CNA &#8211; Converged Network Adaptor\n<ul>\n<li>Same as regular Ethernet card, but supports FCoE<\/li>\n<\/ul>\n<\/li>\n<li>Cut infrastructure in half.<\/li>\n<li>Still works the same as FCP, but is encapsulated.\n<ul>\n<li>Still have WWPNs, uses FLOGI, PLOGI, PRLI Process.<\/li>\n<li>Still uses MAC addresses for TCP\/IP<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<h3>How this works<\/h3>\n<ul>\n<li>Virtualize the Physical Interface into two virtual interfaces\n<ul>\n<li>Virtual NIC with a MAC addr. for Ethernet data<\/li>\n<li>Virtual HBA with a WWPN for storage traffic.<\/li>\n<li>Storage and data traffice are split into two different VLANS<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<h4>Data VLan<\/h4>\n<p><a href=\"https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2022\/10\/datavlan.png\"><img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-full wp-image-3840\" src=\"https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2022\/10\/datavlan.png\" alt=\"\" width=\"1616\" height=\"973\" srcset=\"https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2022\/10\/datavlan.png 1616w, https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2022\/10\/datavlan-300x181.png 300w, https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2022\/10\/datavlan-1024x617.png 1024w, https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2022\/10\/datavlan-768x462.png 768w, https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2022\/10\/datavlan-1536x925.png 1536w, https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2022\/10\/datavlan-150x90.png 150w\" sizes=\"auto, (max-width: 1616px) 100vw, 1616px\" \/><\/a><\/p>\n<h4>Storage VLAN<\/h4>\n<p><a href=\"https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2022\/10\/FCPvlan.png\"><img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-full wp-image-3841\" src=\"https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2022\/10\/FCPvlan.png\" alt=\"\" width=\"1674\" height=\"988\" srcset=\"https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2022\/10\/FCPvlan.png 1674w, https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2022\/10\/FCPvlan-300x177.png 300w, https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2022\/10\/FCPvlan-1024x604.png 1024w, https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2022\/10\/FCPvlan-768x453.png 768w, https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2022\/10\/FCPvlan-1536x907.png 1536w, https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2022\/10\/FCPvlan-150x89.png 150w\" sizes=\"auto, (max-width: 1674px) 100vw, 1674px\" \/><\/a><\/p>\n<h3>All together now, 1, 2, 3.<\/h3>\n<p><a href=\"https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2022\/10\/fcoe3.png\"><img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-full wp-image-3842\" src=\"https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2022\/10\/fcoe3.png\" alt=\"\" width=\"1672\" height=\"993\" srcset=\"https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2022\/10\/fcoe3.png 1672w, https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2022\/10\/fcoe3-300x178.png 300w, https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2022\/10\/fcoe3-1024x608.png 1024w, https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2022\/10\/fcoe3-768x456.png 768w, https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2022\/10\/fcoe3-1536x912.png 1536w, https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2022\/10\/fcoe3-150x89.png 150w\" sizes=\"auto, (max-width: 1672px) 100vw, 1672px\" \/><\/a><\/p>\n<h2>Lossless FCoE<\/h2>\n<ul>\n<li>FCP is lossless.\u00a0 It ensures that no frames are lost in transit between the initiantor and target<\/li>\n<li>Ethernet is NOT lossless.\u00a0 TCP recognizes when a packet does not reach its destination and resends.\n<ul>\n<li>This is expected and is normal SOP.<\/li>\n<\/ul>\n<\/li>\n<li>FCoE uses FCP, which assumes a lossless network, so we need a way to ensure the storage packets are not lost while traversing the Ethernet network.<\/li>\n<li>PFC Priority Flow Control FCoE <strong>extension for Ethernet<\/strong> is used to ensure lossless delivery.<\/li>\n<li>PFC works on a hop by hop basis<\/li>\n<li>Each NIC and switch in the path between the initiator and target <strong>must<\/strong> be FCoE capable.<\/li>\n<li>FCoE capable NICs are known as CNA Converged Network Adaptors<\/li>\n<\/ul>\n<p>&nbsp;<\/p>\n<h1>FCoE Lab Demo<\/h1>\n<p><a href=\"https:\/\/learn.flackbox.com\/courses\/81445\/lectures\/5204540\">https:\/\/learn.flackbox.com\/courses\/81445\/lectures\/5204540<\/a><\/p>\n<p>&nbsp;<\/p>\n<h1>iSCSI Overview<\/h1>\n<p><a href=\"https:\/\/learn.flackbox.com\/courses\/81445\/lectures\/5204542\" target=\"_blank\" rel=\"noopener\">https:\/\/learn.flackbox.com\/courses\/81445\/lectures\/5204542<\/a><\/p>\n<p>SAN Protocol that runs over Ethernet Networks<\/p>\n<ul>\n<li>iSCI Internet Small Computer System Interface protocol<\/li>\n<li>Runs over Ethernet and was originally viewed as less expensive alternative to Fibre Channel<\/li>\n<li>Higher packet overhead than FC, lower reliability and performance<\/li>\n<li>Mature and popular SAN technology.<\/li>\n<li>Can share Ethernet or can have its own dedicated network infrastructure<\/li>\n<li>TOE (TCP Offload Engine) cards are specialist adapters which can be used to offload the storage TCP\/IP processing from a server&#8217;s CPU.\n<ul>\n<li>These are sometimes called iSCSI HBAs.<\/li>\n<li>Can still be used for normal Ethernet networks<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<h2>iSCSI Addressing<\/h2>\n<ul>\n<li>Fibre Channel using World Wide Names to identify initiators and targets<\/li>\n<li>iSCSI uses IQN iSCSI Qualified Names\n<ul>\n<li>or less common EUI Extended Unique Identifier)<\/li>\n<\/ul>\n<\/li>\n<li>The IQN can be up to 255 characters\n<ul>\n<li>iqn.yyyy-mm.naming-authority:uniqueName<\/li>\n<li>Ex: iqn.1991-05.com.microsoft:testHost<\/li>\n<\/ul>\n<\/li>\n<li>The IQN is assigned to the host as a whole, similar to the WWNN in FC<\/li>\n<li>iSCSI runs over Ethernet, so individual ports are addressed by IP<\/li>\n<li>iSCSI does not support FLOGI\/PLOGI\/PLRI Process, so administrators must explicity point the initiator at its target by specifying one of the IP addresses in the Target Portal Group\n<ul>\n<li>It will then discover the target&#8217;s IQN and other ports in the TPG<\/li>\n<li>Example: if the target has 4 ips, once it connects to one, it will learn the remaining 3.<\/li>\n<\/ul>\n<\/li>\n<li>Multipathing software on the initiator can then choose which path or paths to take<\/li>\n<li>Although it runs on Ethernet, iSCSI is still a SAN protocol with multipathing intelligence on the initiator.<\/li>\n<\/ul>\n<h2>iSCSI Security<\/h2>\n<ul>\n<li>LUN Masking is configured the same way, except it uses the IQN vs. the WWPN to identify the client.<\/li>\n<li>Zoning is not supported<\/li>\n<li>Password based authentication is typically configured on the initiator and darget to guard against spoofing attacks<\/li>\n<li>End to end IPSec encryption can be enabled to enhance security.<\/li>\n<\/ul>\n<h2>San Protocol Stack Comparison<\/h2>\n<p><a href=\"https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2022\/10\/sanprotocolstack.png\"><img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-full wp-image-3846\" src=\"https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2022\/10\/sanprotocolstack.png\" alt=\"\" width=\"1374\" height=\"656\" srcset=\"https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2022\/10\/sanprotocolstack.png 1374w, https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2022\/10\/sanprotocolstack-300x143.png 300w\" sizes=\"auto, (max-width: 1374px) 100vw, 1374px\" \/><\/a><\/p>\n<p>&nbsp;<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Home Fibre Channel Part 1 &#8211; FCP and WWPN https:\/\/learn.flackbox.com\/courses\/81445\/lectures\/5204536 Terminology Aliases: Easy to identify WWPNs and WWNNs Alias EXCHANGE-SERVER = WWPN 01:23:45:67:89:ab:cd:ef Configurable on both storage systems and Switches Much easier to identify during troubleshooting and configuration Client: The host accessing storage FC HBA: Fibre Channel Host Bus Adaptor See HBA FCP: Fibre Channel ..<\/p>\n<div class=\"clear-fix\"><\/div>\n<p><a href=\"https:\/\/wiki.thomasandsofia.com\/?p=3824\" title=\"read more...\">Read more<\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[80],"tags":[],"class_list":["post-3824","post","type-post","status-publish","format-standard","hentry","category-nas-and-san-storage"],"_links":{"self":[{"href":"https:\/\/wiki.thomasandsofia.com\/index.php?rest_route=\/wp\/v2\/posts\/3824","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/wiki.thomasandsofia.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/wiki.thomasandsofia.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/wiki.thomasandsofia.com\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/wiki.thomasandsofia.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=3824"}],"version-history":[{"count":9,"href":"https:\/\/wiki.thomasandsofia.com\/index.php?rest_route=\/wp\/v2\/posts\/3824\/revisions"}],"predecessor-version":[{"id":3849,"href":"https:\/\/wiki.thomasandsofia.com\/index.php?rest_route=\/wp\/v2\/posts\/3824\/revisions\/3849"}],"wp:attachment":[{"href":"https:\/\/wiki.thomasandsofia.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=3824"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/wiki.thomasandsofia.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=3824"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/wiki.thomasandsofia.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=3824"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}