Welcome to Fibre Channel (FC) SAN.

This module is part of ISM v3 course that includes 16

modules.
Copyright ©2015 EMC Corporation. All Rights Reserved. Published in the USA. EMC believes the information in this publication is accurate as of its publication date. The information is subject to change
without notice.

THE INFORMATION IN THIS PUBLICATION IS PROVIDED “AS IS.” EMC CORPORATION MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND WITH RESPECT TO THE INFORMATION IN THIS
PUBLICATION, AND SPECIFICALLY DISCLAIMS IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

Use, copying, and distribution of any EMC software described in this publication requires an applicable software license. The trademarks, logos, and service marks (collectively "Trademarks") appearing in
this publication are the property of EMC Corporation and other parties. Nothing contained in this publication should be construed as granting any license or right to use any Trademark without the prior
written permission of the party that owns the Trademark.

EMC, EMC² AccessAnywhere Access Logix, AdvantEdge, AlphaStor, AppSync ApplicationXtender, ArchiveXtender, Atmos, Authentica, Authentic Problems, Automated Resource Manager, AutoStart,
AutoSwap, AVALONidm, Avamar, Bus-Tech, Captiva, Catalog Solution, C-Clip, Celerra, Celerra Replicator, Centera, CenterStage, CentraStar, EMC CertTracker. CIO Connect, ClaimPack, ClaimsEditor,
Claralert ,cLARiiON, ClientPak, CloudArray, Codebook Correlation Technology, Common Information Model, Compuset, Compute Anywhere, Configuration Intelligence, Configuresoft, Connectrix,
Constellation Computing, EMC ControlCenter, CopyCross, CopyPoint, CX, DataBridge , Data Protection Suite. Data Protection Advisor, DBClassify, DD Boost, Dantz, DatabaseXtender, Data Domain, Direct
Matrix Architecture, DiskXtender, DiskXtender 2000, DLS ECO, Document Sciences, Documentum, DR Anywhere, ECS, elnput, E-Lab, Elastic Cloud Storage, EmailXaminer, EmailXtender , EMC Centera, EMC
ControlCenter, EMC LifeLine, EMCTV, Enginuity, EPFM. eRoom, Event Explorer, FAST, FarPoint, FirstPass, FLARE, FormWare, Geosynchrony, Global File Virtualization, Graphic Visualization, Greenplum,
HighRoad, HomeBase, Illuminator , InfoArchive, InfoMover, Infoscape, Infra, InputAccel, InputAccel Express, Invista, Ionix, ISIS,Kazeon, EMC LifeLine, Mainframe Appliance for Storage, Mainframe Data
Library, Max Retriever, MCx, MediaStor , Metro, MetroPoint, MirrorView, Multi-Band Deduplication,Navisphere, Netstorage, NetWorker, nLayers, EMC OnCourse, OnAlert, OpenScale, Petrocloud,
PixTools, Powerlink, PowerPath, PowerSnap, ProSphere, ProtectEverywhere, ProtectPoint, EMC Proven, EMC Proven Professional, QuickScan, RAPIDPath, EMC RecoverPoint, Rainfinity, RepliCare,
RepliStor, ResourcePak, Retrospect, RSA, the RSA logo, SafeLine, SAN Advisor, SAN Copy, SAN Manager, ScaleIO Smarts, EMC Snap, SnapImage, SnapSure, SnapView, SourceOne, SRDF, EMC Storage
Administrator, StorageScope, SupportMate, SymmAPI, SymmEnabler, Symmetrix, Symmetrix DMX, Symmetrix VMAX, TimeFinder, TwinStrata, UltraFlex, UltraPoint, UltraScale, Unisphere, Universal Data
Consistency, Vblock, Velocity, Viewlets, ViPR, Virtual Matrix, Virtual Matrix Architecture, Virtual Provisioning, Virtualize Everything, Compromise Nothing, Virtuent, VMAX, VMAXe, VNX, VNXe, Voyence,
VPLEX, VSAM-Assist, VSAM I/O PLUS, VSET, VSPEX, Watch4net, WebXtender, xPression, xPresso, Xtrem, XtremCache, XtremSF, XtremSW, XtremIO, YottaYotta, Zero-Friction Enterprise Storage.

Revision Date: August 2015

Revision Number: MR-1WP-ISMv3FCS

Copyright 2015 EMC Corporation. All rights reserved. ISM v3 Module 9: Fibre Channel (FC) SAN 1
 This module covers the third platform requirements for SAN, software-defined networking, FC
SAN components, FC architecture, FC SAN topologies, link aggregation, and zoning. This module
also covers virtualization in an FC SAN environment.

Copyright 2015 EMC Corporation. All rights reserved. ISM v3 Module 9: Fibre Channel (FC) SAN 2
 This lesson covers the definition and benefits of SAN, third platform requirements for SAN,
technology solutions for SAN, and software-defined networking.

Copyright 2015 EMC Corporation. All rights reserved. ISM v3 Module 9: Fibre Channel (FC) SAN 3
 Storage area network (SAN) is a network that primarily connects the storage systems
with the compute systems and also connects the storage systems with each other. It
enables multiple compute systems to access and share storage resources. It also enables
data transfer between the storage systems. With long-distance SAN, the data transfer
over SAN can be extended across geographic locations. A SAN usually provides access to
block-based storage systems.

Copyright 2015 EMC Corporation. All rights reserved. ISM v3 Module 9: Fibre Channel (FC) SAN 4
 SANs address the limitations of direct-attached storage (DAS) environment. Unlike a DAS
environment, where the compute systems own the storage, SANs enable both consolidation and
sharing of storage resources across multiple compute systems. This improves the utilization of
storage resources compared to a DAS environment and reduces the total amount of storage that
an organization needs to purchase and manage. With consolidation, storage management
becomes centralized and less complex, which further reduces the cost of managing information.

A SAN may span over wide locations. This enables organizations to connect
geographically dispersed compute systems and storage systems. The long-distance SAN
connectivity enables the compute systems across locations to access shared data. The
long-distance connectivity also enables the replication of data between storage systems
that reside in separate locations. The replication over long-distances helps in protecting
data against local and regional disaster. Further, the long-distance SAN connectivity
facilitates remote backup of application data. Backup data can be transferred through a
SAN to a backup device that may reside at a remote location. This avoids having to ship
tapes (backup media) from the primary site to the remote site and the associated pitfalls
such as packing and shipping expenses and lost tapes in transit.

Copyright 2015 EMC Corporation. All rights reserved. ISM v3 Module 9: Fibre Channel (FC) SAN 5
 The IT industry is in the middle of a massive technological and structural shift toward what the
industry analyst IDC calls the third platform. Third platform is built on social networking, mobile
computing, cloud services, and big data analytics technologies. Applications that support these
technologies require significantly higher performance, scalability, and availability compared to the
traditional applications. Similar to the compute and storage infrastructure, the SAN infrastructure
must also be ready to support the requirements of third platform applications. Therefore, it is
necessary to establish how the third platform application requirements are translated into the
SAN requirements. This slide provides a list of key requirements for an effective SAN
infrastructure.

Copyright 2015 EMC Corporation. All rights reserved. ISM v3 Module 9: Fibre Channel (FC) SAN 6
 Technology solutions that can meet the third platform requirements for the SANs are:

• Software-defined networking

• SAN implementations:
• Fibre Channel (FC) SAN
• Internet Protocol (IP) SAN
• Fibre Channel over Ethernet (FCoE) SAN

• Virtualization in SAN

Both the software-defined networking and the FC SAN are covered in this module. Module 10,
‘Internet Protocol (IP) SAN’ and module 11, ‘FC over Ethernet (FCoE) SAN’ describe IP SAN and
FCoE SAN respectively. Virtualization in SAN is described along with each of the SAN
implementations.

Copyright 2015 EMC Corporation. All rights reserved. ISM v3 Module 9: Fibre Channel (FC) SAN 7
 Traditionally, a network component such as a switch or a router consists of a data plane and a
control plane. These planes are implemented in the firmware of the network components. The
function of the data plane is to transfer the network traffic from one physical port to another port
by following rules that are programmed into the component. The function of the control plane is
to provide the programming logic that the data plane follows for switching or routing of the
network traffic. Software-defined networking is an approach to abstract and separate the control
plane functions from the data plane functions. Instead of the built-in control functions at the
network components level, the software external to the components takes over the control
functions. The software runs on a compute system or a standalone device and is called network
controller. The network controller interacts with the network components to gather configuration
information and to provide instructions for data plane in order to handle the network traffic.

Copyright 2015 EMC Corporation. All rights reserved. ISM v3 Module 9: Fibre Channel (FC) SAN 8
 Software-defined networking in the SAN provides several benefits. These are described below:

• Centralized control: The software-defined approach provides a single point of control for the
entire SAN infrastructure that may span across data centers. The centralized control plane
provides that programming logic for transferring the SAN traffic, which can be uniformly and
quickly applied across the SAN infrastructure. The programming logic can be upgraded
centrally to add new features and based on application requirements.

• Policy-based automation: With software-defined approach, many hardware-based SAN

management operations such as zoning (described later) can be automated.
Management operations may be programmed in the network controller based on
business policies and best practices. This reduces the need for manual operations that
are repetitive, error-prone, and time-consuming. Policy-based automation also helps
to standardize the management operations.

• Simplified, agile management: The network controller usually provides a management

interface that includes a limited and standardized set of management functions. With policy-
based automation in place, these management functions are available in simplified form,
abstracting the underlying operational complexity. This makes it easy to configure a SAN
infrastructure. This also helps promptly modifying the SAN configuration to respond to the
changing application requirements.

Copyright 2015 EMC Corporation. All rights reserved. ISM v3 Module 9: Fibre Channel (FC) SAN 9
 This lesson covered the definition and benefits of SAN, third platform requirements for SAN,
technology solutions for SAN, and software-defined networking.

Copyright 2015 EMC Corporation. All rights reserved. ISM v3 Module 9: Fibre Channel (FC) SAN 10
 This lesson covers the components of FC SAN, three FC interconnectivity options, and FC port
types.

Copyright 2015 EMC Corporation. All rights reserved. ISM v3 Module 9: Fibre Channel (FC) SAN 11
 Fibre Channel SAN (FC SAN) uses Fibre Channel (FC) protocol for communication. FC protocol
(FCP) is used to transport data, commands, and status information between the compute systems
and the storage systems. It is also used to transfer data between the storage systems.

FC is a high-speed network technology that runs on high-speed optical fiber cables and serial
copper cables. The FC technology was developed to meet the demand for the increased speed of
data transfer between compute systems and mass storage systems. In comparison with Ultra-
Small Computer System Interface (Ultra-SCSI) that is commonly used in the DAS environments,
FC is a significant leap in storage networking technology. The latest FC implementations of 16
GFC offer a throughput of 3200 MB/s (raw bit rates of 16 Gb/s), whereas Ultra640 SCSI is
available with a throughput of 640 MB/s. FC is expected to come with 6400 MB/s (raw bit rates of
32 Gb/s) and 25600 MB/s (raw bit rates of 128 Gb/s) throughput in 2016. Technical Committee
T11, which is the committee within International Committee for Information Technology
Standards (INCITS), is responsible for FC interface standards.

FC supports credit-based flow control mechanism (described later). The flow control mechanism
delivers data as fast as the destination buffer is able to receive it, without dropping frames. FC
also has very little transmission overhead. The FC architecture is highly scalable, and
theoretically, a single FC SAN can accommodate approximately 15 million devices.

Note: FibRE refers to the protocol, whereas fibER refers to a media.

Copyright 2015 EMC Corporation. All rights reserved. ISM v3 Module 9: Fibre Channel (FC) SAN 12
 The key FC SAN components are network adapters, cables, and interconnecting devices. These
components are described below.

• Network adapters: In an FC SAN, the end devices, such as compute systems and storage
systems are all referred to as nodes. Each node is a source or destination of information. Each
node requires one or more network adapters to provide a physical interface for communicating
with other nodes. Examples of network adapters are FC host bus adapters (HBAs) and storage
system front-end adapters. An FC HBA has SCSI-to-FC processing capability. It encapsulates
OS or hypervisor storage I/Os (usually SCSI I/O) into FC frames before sending the frames to
the FC storage systems over an FC SAN.

• Cables: FC SAN implementations primarily use optical fiber cabling. Copper cables may be
used for shorter distances because it provides acceptable signal-to-noise ratio for distances up
to 30 meters. Optical fiber cables carry data in the form of light. There are two types of optical
cables: multimode and single-mode. Multimode fiber (MMF) cable carries multiple beams of
light projected at different angles simultaneously onto the core of the cable. In an MMF
transmission, multiple light beams traveling inside the cable tend to disperse and collide. This
collision weakens the signal strength after it travels a certain distance – a process known as
modal dispersion. Due to modal dispersion, an MMF cable is typically used for short distances,
commonly within a data center. Single-mode fiber (SMF) carries a single ray of light projected
at the center of the core. The small core and the single light wave help to limit modal
dispersion. Single-mode provides minimum signal attenuation over maximum distance (up to
10 km). A single-mode cable is used for long-distance cable runs, and the distance usually
depends on the power of the laser at the transmitter and the sensitivity of the receiver. A
connector is attached at the end of a cable to enable swift connection and disconnection of the
cable to and from a port. A standard connector (SC) and a lucent connector (LC) are two
commonly used connectors for fiber optic cables.

• Interconnecting devices: The commonly used interconnecting devices in FC SANs are FC

hubs, FC switches, and FC directors. These devices are further detailed in the next slide.

Copyright 2015 EMC Corporation. All rights reserved. ISM v3 Module 9: Fibre Channel (FC) SAN 13
 FC hubs are used as communication devices in Fibre Channel Arbitrated Loop (FC-AL)
implementations (discussed later). Hubs physically connect nodes in a logical loop or a physical
star topology. All the nodes must share the loop because data travels through all the connection
points. Because of the availability of low-cost and high-performance switches, the FC switches are
preferred over the FC hubs in FC SAN deployments.

FC switches are more intelligent than FC hubs and directly route data from one physical port to
another. Therefore, the nodes do not share the data path. Instead, each node has a dedicated
communication path. The FC switches are commonly available with a fixed port count. Some of
the ports can be active for operational purpose and the rest remain unused. The number of active
ports can be scaled-up non-disruptively. Some of the components of a switch such as power
supplies and fans are redundant and hot-swappable (components can be replaced while a device
is powered-on and remains in operation).

FC directors are high-end switches with a higher port count. A director has a modular architecture
and its port count is scaled-up by inserting additional line cards or blades to the director’s chassis.
Directors contain redundant components with automated failover capability. Its key components
such as switch controllers, blades, power supplies, and fan modules are all hot-swappable. These
insure high availability for business critical applications.

Copyright 2015 EMC Corporation. All rights reserved. ISM v3 Module 9: Fibre Channel (FC) SAN 14
 The FC architecture supports three basic interconnectivity options: point-to-point, fibre channel
arbitrated loop (FC-AL), and fibre channel switched fabric (FC-SW). These interconnectivity
options are described below:

• Point-to-point: In this configuration, two nodes are connected directly to each other. This
configuration provides a dedicated connection for data transmission between nodes. However,
the point-to-point configuration offers limited connectivity and scalability and is used in a DAS
environment.

• FC-AL: In this configuration, the devices are attached to a shared loop. Each device contends
with other devices to perform I/O operations. The devices on the loop must “arbitrate” to gain
control of the loop. At any given time, only one device can perform I/O operations on the loop.
Because each device in a loop must wait for its turn to process an I/O request, the overall
performance in FC-AL environments is low. Further, adding or removing a device results in loop
re-initialization, which can cause a momentary pause in loop traffic. As a loop configuration,
FC-AL can be implemented without any interconnecting devices by directly connecting one
device to another two devices in a ring through cables. However, FC-AL implementations may
also use FC hubs through which the arbitrated loop is physically connected in a star topology.

• FC-SW: It involves a single FC switch or a network of FC switches (including FC directors) to

interconnect the nodes. It is also referred to as fabric connect. A fabric is a logical space in
which all nodes communicate with one another in a network. In a fabric, the link between any
two switches is called an interswitch link (ISL). ISLs enable switches to be connected together
to form a single, larger fabric. They enable the transfer of both storage traffic and fabric
management traffic from one switch to another. In FC-SW, nodes do not share a loop; instead,
data is transferred through a dedicated path between the nodes. Unlike a loop configuration,
an FC-SW configuration provides high scalability. The addition or removal of a node in a
switched fabric is minimally disruptive; it does not affect the ongoing traffic between other
nodes.

Copyright 2015 EMC Corporation. All rights reserved. ISM v3 Module 9: Fibre Channel (FC) SAN 15
 The ports in a switched fabric can be one of the following types:
• N_Port: It is an end point in the fabric. This port is also known as the node port. Typically, it is
a compute system port (FC HBA port) or a storage system port that is connected to a switch in
a switched fabric.
• E_Port: It is a port that forms the connection between two FC switches. This port is also
known as the expansion port. The E_Port on an FC switch connects to the E_Port of another FC
switch in the fabric ISLs.
• F_Port: It is a port on a switch that connects an N_Port. It is also known as a fabric port.
• G_Port: It is a generic port on a switch that can operate as an E_Port or an F_Port and
determines its functionality automatically during initialization.

Copyright 2015 EMC Corporation. All rights reserved. ISM v3 Module 9: Fibre Channel (FC) SAN 16
 This lesson covered FC SAN components, three FC interconnectivity options, and various FC port
types.

Copyright 2015 EMC Corporation. All rights reserved. ISM v3 Module 9: Fibre Channel (FC) SAN 17
 This lesson covers FC protocol stack, FC and WWN addressing, and structure and organization of
FC data. This lesson also covers fabric services, fabric login types, and flow control.

Copyright 2015 EMC Corporation. All rights reserved. ISM v3 Module 9: Fibre Channel (FC) SAN 18
 Traditionally, compute operating systems have communicated with peripheral devices over
channel connections, such as Enterprise Systems Connection (ESCON) and SCSI. Channel
technologies provide high levels of performance with low protocol overheads. Such performance is
achievable due to the static nature of channels and the high level of hardware and software
integration provided by the channel technologies. However, these technologies suffer from
inherent limitations in terms of the number of devices that can be connected and the distance
between these devices.

In contrast to channel technology, network technologies are more flexible and provide greater
distance capabilities. Network connectivity provides greater scalability and uses shared bandwidth
for communication. This flexibility results in greater protocol overhead and reduced performance.

The FC architecture represents true channel and network integration and captures some of the
benefits of both channel and network technology. FC protocol provides both the channel speed for
data transfer with low protocol overhead and the scalability of network technology. FC provides a
serial data transfer interface that operates over copper wire and optical fiber.

FC protocol forms the fundamental construct of the FC SAN infrastructure. FC protocol

predominantly is the implementation of SCSI over an FC network. SCSI data is encapsulated and
transported within FC frames. SCSI over FC overcomes the distance and the scalability limitations
associated with traditional direct-attached storage. Storage devices attached to the FC SAN
appear as locally attached devices to the operating system (OS) or hypervisor running on
the compute system.

Copyright 2015 EMC Corporation. All rights reserved. ISM v3 Module 9: Fibre Channel (FC) SAN 19
 It is easier to understand a communication protocol by viewing it as a structure of independent
layers. FCP defines the communication protocol in five layers: FC-0 through FC-4 (except FC-3
layer, which is not implemented).

FC-4 Layer: It is the uppermost layer in the FCP stack. This layer defines the application
interfaces and the way Upper Layer Protocols (ULPs) are mapped to the lower FC layers. The FC
standard defines several protocols that can operate on the FC-4 layer. Some of the protocols
include SCSI, High Performance Parallel Interface (HIPPI) Framing Protocol, ESCON,
Asynchronous Transfer Mode (ATM), and IP.

FC-2 Layer: It provides FC addressing, structure, and organization of data (frames, sequences,
and exchanges). It also defines fabric services, classes of service, flow control, and routing.

FC-1 Layer: It defines how data is encoded prior to transmission and decoded upon receipt. At
the transmitter node, an 8-bit character is encoded into a 10-bit transmission character. This
character is then transmitted to the receiver node. At the receiver node, the 10-bit character is
passed to the FC-1 layer, which decodes the 10-bit character into the original 8-bit character. FC
links, with a speed of 10 Gbps and above, use 64-bit to 66-bit encoding algorithm. This layer also
defines the transmission words such as FC frame delimiters, which identify the start and the end
of a frame and the primitive signals that indicate events at a transmitting port. In addition to
these, the FC-1 layer performs link initialization and error recovery.

FC-0 Layer: It is the lowest layer in the FCP stack. This layer defines the physical interface,
media, and transmission of bits. The FC-0 specification includes cables, connectors, and optical
and electrical parameters for a variety of data rates. The FC transmission can use both electrical
and optical media.

Copyright 2015 EMC Corporation. All rights reserved. ISM v3 Module 9: Fibre Channel (FC) SAN 20
 An FC address is dynamically assigned when a node port logs on to the fabric. The FC
address has a distinct format, as shown on the slide. The first field of the FC address
contains the domain ID of the switch. A domain ID is a unique number provided to each
switch in the fabric. Although this is an 8-bit field, there are only 239 available addresses
for domain ID because some addresses are deemed special and reserved for fabric
services. For example, FFFFFC is reserved for the name server, and FFFFFE is reserved
for the fabric login service. The area ID is used to identify a group of switch ports used
for connecting nodes. An example of a group of ports with common area ID is a port card
on the switch. The last field, the port ID, identifies the port within the group.

Therefore, the maximum possible number of node ports in a switched fabric is calculated
as:

239 domains X 256 areas X 256 ports = 15,663,104 ports.

Copyright 2015 EMC Corporation. All rights reserved. ISM v3 Module 9: Fibre Channel (FC) SAN 21
 Each device in the FC environment is assigned a 64-bit unique identifier called the World Wide
Name (WWN). The FC environment uses two types of WWNs: World Wide Node Name (WWNN)
and World Wide Port Name (WWPN). WWNN is used to physically identify FC network adapters
and WWPN is used to physically identify FC adapter ports or node ports. For example, a dual-port
FC HBA has one WWNN and two WWPNs.

Unlike an FC address, which is assigned dynamically, a WWN is a static name for each device on
an FC network. WWNs are similar to the Media Access Control (MAC) addresses used in IP
networking. WWNs are burned into the hardware or assigned through software. Several
configuration definitions in an FC SAN use WWN for identifying storage systems and FC HBAs.
WWNs are critical for FC SAN configuration as each node port has to be registered by its WWN
before the FC SAN recognizes it. The name server in an FC SAN environment keeps the
association of WWNs to the dynamically created FC addresses for node ports. The figure on the
slide illustrates the WWN structure examples for a storage system and an HBA.

Copyright 2015 EMC Corporation. All rights reserved. ISM v3 Module 9: Fibre Channel (FC) SAN 22
 In an FC network, data transport is analogous to a conversation between two people,
whereby a frame represents a word, a sequence represents a sentence, and an exchange
represents a conversation.

Exchange: An exchange operation enables two node ports to identify and manage a set
of information units. Each upper layer protocol (ULP) has its protocol-specific information
that must be sent to another port to perform certain operations. This protocol-specific
information is called an information unit. The structure of these information units is
defined in the FC-4 layer. This unit maps to a sequence. An exchange is composed of one
or more sequences.

Sequence: A sequence refers to a contiguous set of frames that are sent from one port
to another. A sequence corresponds to an information unit, as defined by the ULP.

Frame: A frame is the fundamental unit of data transfer at FC-2 layer. An FC frame
consists of five parts: start of frame (SOF), frame header, data field, cyclic redundancy
check (CRC), and end of frame (EOF). The SOF and EOF act as delimiters. The frame
header is 24 bytes long and contains addressing information for the frame. The data field
in an FC frame contains the data payload, up to 2,112 bytes of actual data – in most
cases the SCSI data. The CRC checksum facilitates error detection for the content of the
frame. This checksum verifies data integrity by checking whether the content of the
frames are received correctly. The CRC checksum is calculated by the sender before
encoding at the FC-1 layer. Similarly, it is calculated by the receiver after decoding at the
FC-1 layer.

Copyright 2015 EMC Corporation. All rights reserved. ISM v3 Module 9: Fibre Channel (FC) SAN 23
 All FC switches, regardless of the manufacturer, provide a common set of services as
defined in the FC standards. These services are available at certain predefined addresses.
Some of these services are Fabric Login Server, Fabric Controller, Name Server, and
Management Server.

• Fabric Login Server: It is located at the predefined address of FFFFFE and is used
during the initial part of the node’s fabric login process.

• Name Server (formally known as Distributed Name Server): It is located at the

predefined address FFFFFC and is responsible for name registration and management
of node ports. Each switch exchanges its Name Server information with other switches
in the fabric to maintain a synchronized, distributed name service.

• Fabric Controller: Each switch has a Fabric Controller located at the predefined
address FFFFFD. The Fabric Controller provides services to both node ports and other
switches. The Fabric Controller is responsible for managing and distributing Registered
State Change Notifications (RSCNs) to the node ports registered with the Fabric
Controller. If there is a change in the fabric, RSCNs are sent out by a switch to the
attached node ports. The Fabric Controller also generates Switch Registered State
Change Notifications (SW-RSCNs) to every other domain (switch) in the fabric. These
RSCNs keep the name server up-to-date on all switches in the fabric.

• Management Server: FFFFFA is the FC address for the Management Server. The
Management Server is distributed to every switch within the fabric. The Management
Server enables the FC SAN management software to retrieve information and
administer the fabric.

Copyright 2015 EMC Corporation. All rights reserved. ISM v3 Module 9: Fibre Channel (FC) SAN 24
 Fabric services define three login types:
• Fabric login (FLOGI): It is performed between an N_Port and an F_Port. To log on to the
fabric, a node sends a FLOGI frame with the WWNN and WWPN parameters to the login service
at the predefined FC address FFFFFE (Fabric Login Server). In turn, the switch accepts the
login and returns an Accept (ACC) frame with the assigned FC address for the node.
Immediately after the FLOGI, the N_Port registers itself with the local Name Server on the
switch, indicating its WWNN, WWPN, port type, class of service, assigned FC address, and so
on. After the N_Port has logged in, it can query the name server database for information
about all other logged in ports.
• Port login (PLOGI): It is performed between two N_Ports to establish a session. The initiator
N_Port sends a PLOGI request frame to the target N_Port, which accepts it. The target N_Port
returns an ACC to the initiator N_Port. Next, the N_Ports exchange service parameters relevant
to the session.
• Process login (PRLI): It is also performed between two N_Ports. This login relates to the FC-
4 ULPs, such as SCSI. If the ULP is SCSI, N_Ports exchange SCSI-related service parameters.

Copyright 2015 EMC Corporation. All rights reserved. ISM v3 Module 9: Fibre Channel (FC) SAN 25
 Flow control is the process to regulate the data transmission rate between two devices so that a
transmitting device does not overflow a receiving device with data. A fabric uses the buffer-to-
buffer credit (BB_Credit) mechanism for flow control. The BB_Credit management may occur
between any two FC ports.

In a fabric, an FC frame is received and stored in a receive buffer where it is processed by the
receiving FC port. If another frame arrives while the receiving port is processing the first frame, a
second receive buffer is needed to hold the new frame. If all the receive buffers are filled up with
received frames and the transmitting port sends another frame, then the receiving port would not
have a receive buffer available to hold the new frame and the frame would be dropped. BB_Credit
mechanism ensures that the FC ports do not run out of buffers and do not drop frames.

With BB_Credit mechanism, the transmitting and receiving ports agree on the number of buffers
available or BB_Credits during the port login process. The credit value is decremented when a
frame is transmitted and incremented upon receiving a response. A receiver ready (R_RDY) is
sent from the receiving port to the transmitting port for every free buffer on the receiving side.
The transmitting port increments the credit value per R_RDY it receives from the receiving port.
The transmitting port maintains a count of available credits and continues to send frames if the
count is greater than zero. If the available credits reaches zero, then further transmission of
frames is suspended until the credit count becomes a nonzero value.

In the figure shown on the slide, a data frame is sent from the N_Port of a compute system to the
F_Port of an FC switch. Once the frame is processed and passes the F_Port, the buffer is released
and an R_RDY is sent to the transmitting N_Port, allowing the buffer to be marked as available.
Each port-to-port data transmission occurs in this manner throughout the fabric.

Copyright 2015 EMC Corporation. All rights reserved. ISM v3 Module 9: Fibre Channel (FC) SAN 26
 This lesson covered FC protocol stack, FC and WWN addressing, and structure and organization of
FC data. This lesson also covered fabric services, fabric login types, and flow control.

Copyright 2015 EMC Corporation. All rights reserved. ISM v3 Module 9: Fibre Channel (FC) SAN 27
 This lesson covers FC SAN topologies such as single-switch, mesh, and core-edge. This lesson
also covers link aggregation and types of zoning.

Copyright 2015 EMC Corporation. All rights reserved. ISM v3 Module 9: Fibre Channel (FC) SAN 28
 FC switches (including FC directors) may be connected in a number of ways to form different
fabric topologies. Each topology provides certain benefits.

In a single-switch topology, the fabric consists of only a single switch. Both the compute
systems and the storage systems are connected to the same switch. A key advantage of
a single-switch fabric is that it does not need to use any switch port for ISLs. Therefore, every
switch port is usable for compute system or storage system connectivity. Further, this topology
helps eliminate FC frames traveling over the ISLs and consequently eliminates the ISL delays.

A typical implementation of a single-switch fabric would involve the deployment of an FC director.

FC directors are high-end switches with a high port count. When additional switch ports are
needed over time, new ports can be added via add-on line cards (blades) in spare slots available
on the director chassis. To some extent, a bladed solution alleviates the port count scalability
problem inherent in a single-switch topology.

Copyright 2015 EMC Corporation. All rights reserved. ISM v3 Module 9: Fibre Channel (FC) SAN 29
 A mesh topology may be one of the two types: full mesh or partial mesh. In a full mesh, every
switch is connected to every other switch in the topology. A full mesh topology may be
appropriate when the number of switches involved is small. A typical deployment would involve
up to four switches or directors, with each of them servicing highly localized compute-to-storage
traffic. In a full mesh topology, a maximum of one ISL or hop is required for compute-to-storage
traffic. However, with the increase in the number of switches, the number of switch ports used for
ISL also increases. This reduces the available switch ports for node connectivity.
In a partial mesh topology, not all the switches are connected to every other switch. In this
topology, several hops or ISLs may be required for the traffic to reach its destination. Partial
mesh offers more scalability than full mesh topology. However, without proper placement of
compute and storage systems, traffic management in a partial mesh fabric might be complicated
and ISLs could become overloaded due to excessive traffic aggregation.

Copyright 2015 EMC Corporation. All rights reserved. ISM v3 Module 9: Fibre Channel (FC) SAN 30
 The core-edge topology has two types of switch tiers: edge and core.

The edge tier is usually composed of switches and offers an inexpensive approach to adding more
compute systems in a fabric. The edge-tier switches are not connected to each other. Each switch
at the edge tier is attached to a switch at the core tier through ISLs.

The core tier is usually composed of directors that ensure high fabric availability. In addition,
typically all traffic must either traverse this tier or terminate at this tier. In this configuration, all
storage systems are connected to the core tier, enabling compute-to-storage traffic to traverse
only one ISL. Compute systems that require high performance may be connected directly to the
core tier and consequently avoid ISL delays.

The core-edge topology increases connectivity within the FC SAN while conserving the overall port
utilization. It eliminates the need to connect edge switches to other edge switches over ISLs.
Reduction of ISLs can greatly increase the number of node ports that can be connected to the
fabric. If fabric expansion is required, then administrators would need to connect additional edge
switches to the core. The core of the fabric is also extended by adding more switches or directors
at the core tier. Based on the number of core-tier switches, this topology has different variations,
such as single-core topology and dual-core topology. To transform a single-core topology to dual-
core, new ISLs are created to connect each edge switch to the new core switch in the fabric.

Copyright 2015 EMC Corporation. All rights reserved. ISM v3 Module 9: Fibre Channel (FC) SAN 31
 Link aggregation combines two or more parallel ISLs into a single logical ISL, called a port-
channel, yielding higher throughput than a single ISL could provide. For example, the aggregation
of 10 ISLs into a single port-channel provides up to 160 Gb/s throughput assuming the bandwidth
of an ISL is 16 Gb/s. Link aggregation optimizes fabric performance by distributing network traffic
across the shared bandwidth of all the ISLs in a port-channel. This allows the network traffic for a
pair of node ports to flow through all the available ISLs in the port-channel rather than restricting
the traffic to a specific, potentially congested ISL. The number of ISLs in a port channel can be
scaled depending on application’s performance requirement.

This slide illustrates two examples. The example on the left is based on an FC SAN infrastructure
with no link aggregation enabled. Four HBA ports H1, H2, H3, and H4 have been configured to
generate I/O activity to four storage system ports S1, S2, S3, and S4 respectively. The HBAs and
the storage systems are connected to two separate FC switches with three ISLs between the
switches. Let us assume that the bandwidth of each ISL is 8 Gb/s and the data transmission rate
for the port-pairs {H1,S1}, {H2,S2}, {H3,S3}, and {H4,S4} are 5 Gb/s, 1.5 Gb/s, 2 Gb/s, and
4.5 Gb/s. Without link aggregation, the fabric typically assigns a particular ISL for each of the
port-pairs in a round-robin fashion. It is possible that port-pairs {H1,S1} and {H4,S4} are
assigned to the same ISL in their respective routes. The other two ISLs are assigned to the port-
pairs {H2,S2} and {H3,S3}. Two of the three ISLs are under-utilized, whereas the third ISL is
saturated and becomes a performance bottleneck for the port-pairs assigned to it. The example
on the right has aggregated the three ISLs into a port-channel that provides throughput up to 24
Gb/s. Network traffic for all the port-pairs are distributed over the ISLs in the port-channel, which
ensures even ISL utilization.

Copyright 2015 EMC Corporation. All rights reserved. ISM v3 Module 9: Fibre Channel (FC) SAN 32
 Zoning is an FC switch function that enables node ports within the fabric to be logically
segmented into groups and communicate with each other within the group.
Whenever a change takes place in the name server database, the fabric controller sends
a Registered State Change Notification (RSCN) to all the nodes impacted by the change.
If zoning is not configured, the fabric controller sends the RSCN to all the nodes in the
fabric. Involving the nodes that are not impacted by the change increases the amount of
fabric-management traffic. For a large fabric, the amount of FC traffic generated due to
this process can be significant and might impact the compute-to-storage data traffic.
Zoning helps to limit the number of RSCNs in a fabric. In the presence of zoning, a fabric
sends the RSCN to only those nodes in a zone where the change has occurred.
Zoning also provides access control, along with other access control mechanisms, such
as LUN masking. Zoning provides control by allowing only the members in the same zone
to establish communication with each other.

Zone members, zones, and zone sets form the hierarchy defined in the zoning process. A
zone set is composed of a group of zones that can be activated or deactivated as a single
entity in a fabric. Multiple zone sets may be defined in a fabric, but only one zone set can
be active at a time. Members are the nodes within the FC SAN that can be included in a
zone. FC switch ports, FC HBA ports, and storage system ports can be members of a
zone. A port or node can be a member of multiple zones. Nodes distributed across
multiple switches in a switched fabric may also be grouped into the same zone. Zone sets
are also referred to as zone configurations.

Copyright 2015 EMC Corporation. All rights reserved. ISM v3 Module 9: Fibre Channel (FC) SAN 33
 Zoning can be categorized into three types:
• WWN zoning: It uses World Wide Names to define zones. The zone members are the unique
WWN addresses of the FC HBA and its targets (storage systems). A major advantage of WWN
zoning is its flexibility. If an administrator moves a node to another switch port in the fabric,
the node maintains connectivity to its zone partners without having to modify the zone
configuration. This is possible because the WWN is static to the node port.
• Port zoning: It uses the switch port ID to define zones. In port zoning, access to node is
determined by the physical switch port to which a node is connected. The zone members are
the port identifiers (switch domain ID and port number) to which FC HBA and its targets
(storage systems) are connected. If a node is moved to another switch port in the fabric, port
zoning must be modified to allow the node, in its new port, to participate in its original zone.
However, if an FC HBA or storage system port fails, an administrator just has to replace the
failed device without changing the zoning configuration.
• Mixed zoning: It combines the qualities of both WWN zoning and port zoning. Using mixed
zoning enables a specific node port to be tied to the WWN of another node.

The figure on the slide shows three types of zoning on an FC network.

Copyright 2015 EMC Corporation. All rights reserved. ISM v3 Module 9: Fibre Channel (FC) SAN 34
 This lesson covered FC SAN topologies such as single-switch, mesh, and core-edge. This lesson
also covered link aggregation and types of zoning.

Copyright 2015 EMC Corporation. All rights reserved. ISM v3 Module 9: Fibre Channel (FC) SAN 35
 This lesson covers port virtualization that comprises both N_Port ID virtualization (NPIV) and
N_Port virtualization (NPV). This lesson also covers block-level storage virtualization and virtual
SAN.

Copyright 2015 EMC Corporation. All rights reserved. ISM v3 Module 9: Fibre Channel (FC) SAN 36
 N_Port ID virtualization (NPIV) enables a single N_Port (such as an FC HBA port) to
function as multiple virtual N_Ports. Each virtual N_Port has a unique WWPN identity in
the FC SAN. This allows a single physical N_Port to obtain multiple FC addresses.
Hypervisors leverage NPIV to create virtual N_Ports on the FC HBA and then assign the
virtual N_Ports to virtual machines (VMs). A virtual N_Port acts as a virtual FC HBA port.
This enables a VM to directly access LUNs assigned to it (see the figure on the slide).
NPIV enables an administrator to restrict access to specific LUNs to specific VMs using
security techniques like zoning and LUN masking; similarly to the assignment of a LUN to
a physical compute system. To enable NPIV, both the FC HBAs and the FC switches must
support NPIV. The physical FC HBAs on the compute system, using their own WWNs, must have
access to all LUNs that are to be accessed by VMs running on that compute system.

Copyright 2015 EMC Corporation. All rights reserved. ISM v3 Module 9: Fibre Channel (FC) SAN 37
 The proliferation of compute systems in a data center causes increased use of edge switches in a
fabric. As the edge switch population grows, the number of domain IDs may become a concern
because of the limitation on the number of domain IDs in a fabric. N_Port virtualization (NPV)
addresses this concern by reducing the number of domain IDs in a fabric. Edge switches
supporting NPV do not require a domain ID. They pass traffic between the core switch and the
compute systems. NPV-enabled edge switches do not perform any fabric services, and instead
forward all fabric activity, such as login and name server registration to the core switch.

All ports at the NPV edge switches that connect to the core switch are established as NP_Ports
(not E_Ports). The NP_Ports connect to an NPIV-enabled core director or switch. If the core
director or switch is not NPIV-capable, the NPV edge switches do not function. As the switch
enters or exits from NPV mode, the switch configuration is erased and it reboots. Therefore,
administrators should take care when enabling or disabling NPV on a switch. The figure on the
slide shows a core-edge fabric that comprises two edge switches in NPV mode and one core
switch (an FC director).

Copyright 2015 EMC Corporation. All rights reserved. ISM v3 Module 9: Fibre Channel (FC) SAN 38
 Block-level storage virtualization aggregates block storage devices (LUNs) and enables
provisioning of virtual storage volumes, independent of the underlying physical storage. A
virtualization layer, which exists at the SAN, abstracts the identity of block-based storage systems
and creates a storage pool by aggregating LUNs from the storage systems. Virtual volumes are
created from the storage pool and assigned to the compute systems. Instead of being directed to
the LUNs on the individual storage systems, the compute systems are directed to the virtual
volumes provided by the virtualization layer. The virtualization layer maps the virtual volumes to
the LUNs on the individual storage systems. The compute systems remain unaware of the
mapping operation and access the virtual volumes as if they were accessing the physical storage
attached to them. Typically, the virtualization layer is managed via a dedicated virtualization
appliance to which the compute systems and the storage systems are connected.
The figure on the slide shows two compute systems, each of which has one virtual volume
assigned. These virtual volumes are mapped to the LUNs in the storage systems. When an I/O is
sent to a virtual volume, it is redirected to the mapped LUNs through the virtualization layer at
the FC SAN. Depending on the capabilities of the virtualization appliance, the architecture may
allow for more complex mapping between the LUNs and the virtual volumes.

Block-level storage virtualization enables extending the virtual volumes non-disruptively to meet
application’s capacity scaling requirements. It also provides the advantage of non-disruptive data
migration. In a traditional SAN environment, LUN migration from one storage system to another
is an offline event. After migration, the compute systems are updated to reflect the new storage
system configuration. In other instances, processor cycles at the compute system were required
to migrate data from one storage system to the other, especially in a multivendor environment.
With a block-level storage virtualization solution in place, the virtualization layer handles the
migration of data, which enables LUNs to remain online and accessible while data is migrating. No
physical changes are required because the compute system still points to the same virtual volume
on the virtualization layer. However, the mapping information on the virtualization layer should be
changed. These changes can be executed dynamically and are transparent to the end user.

Copyright 2015 EMC Corporation. All rights reserved. ISM v3 Module 9: Fibre Channel (FC) SAN 39
 The use case is based on the block-level storage virtualization across data centers that
allow compute systems at different locations to share and concurrently access same
virtual volume. According to the use case, two data centers are separated by geographic
distance (see the figure on the slide). Each data center includes an FC SAN infrastructure
that supports block-level storage virtualization through the deployment of the
virtualization appliance. The storage virtualization solution provides the capability to
connect the virtualization appliances at the two data centers. The connected
virtualization appliances are managed centrally and work as a single virtualization layer
stretched across the data centers. This enables the pooling of LUNs across data centers.
Virtual volumes are created from the storage pool. These virtual volumes are accessible
from both the data centers. Compute systems at both the data centers can perform I/O
operations to these shared volumes concurrently. This enables real-time data
collaboration over distance, which is a key requirement for big data applications.

Copyright 2015 EMC Corporation. All rights reserved. ISM v3 Module 9: Fibre Channel (FC) SAN 40
 Virtual SAN (also called virtual fabric) is a logical fabric on an FC SAN, which enables
communication among a group of nodes regardless of their physical location in the fabric. In a
VSAN, a group of node ports communicate with each other using a virtual topology defined on the
physical SAN. Multiple VSANs may be created on a single physical SAN. Each VSAN behaves and
is managed as an independent fabric. Each VSAN has its own fabric services, configuration, and
set of FC addresses. Fabric-related configurations in one VSAN do not affect the traffic in another
VSAN. A VSAN may be extended across sites, enabling communication among a group of nodes,
in either site with a common set of requirements.
VSANs improve SAN security, scalability, availability, and manageability. VSANs provide enhanced
security by isolating the sensitive data in a VSAN and by restricting the access to the resources
located within that VSAN. For example, a cloud provider typically isolates the storage pools for
multiple cloud services by creating multiple VSANs on an FC SAN. Further, the same FC address
can be assigned to nodes in different VSANs, thus increasing the fabric scalability. The events
causing traffic disruptions in one VSAN are contained within that VSAN and are not propagated to
other VSANs. VSANs facilitate an easy, flexible, and less expensive way to manage networks.
Configuring VSANs is easier and quicker compared to building separate physical FC SANs for
various node groups. To regroup nodes, an administrator simply changes the VSAN configurations
without moving nodes and recabling.

Copyright 2015 EMC Corporation. All rights reserved. ISM v3 Module 9: Fibre Channel (FC) SAN 41
 To configure VSANs on a fabric, an administrator first needs to define VSANs on fabric switches.
Each VSAN is identified with a specific number called VSAN ID. The next step is to assign a VSAN
ID to the F_Ports on the switch. By assigning a VSAN ID to an F_Port, the port is included in the
VSAN. In this manner, multiple F_Ports can be grouped into a VSAN. For example, an
administrator may group switch ports (F_Ports) 1 and 2 into VSAN 10 (ID) and ports 6 to 12 into
VSAN 20 (ID). If an N_Port connects to an F_Port that belongs to a VSAN, it becomes a member
of that VSAN. The switch transfers FC frames between switch ports that belong to the same
VSAN.

Note: VSAN versus Zone

Both VSANs and zones enable node ports within a fabric to be logically segmented into groups.
But they are not same and their purposes are different. There is a hierarchical relationship
between them. An administrator first assigns physical ports to VSANs and then configures
independent zones for each VSAN. A VSAN has its own independent fabric services, but the fabric
services are not available on a per-zone basis.

Copyright 2015 EMC Corporation. All rights reserved. ISM v3 Module 9: Fibre Channel (FC) SAN 42
 VSAN trunking allows network traffic from multiple VSANs to traverse a single ISL. It supports a
single ISL to permit traffic from multiple VSANs along the same path. The ISL through which
multiple VSAN traffic travels is called a trunk link. VSAN trunking enables a single E_Port to be
used for sending or receiving traffic from multiple VSANs over a trunk link. The E_Port capable of
transferring multiple VSAN traffic is called a trunk port. The sending and receiving switches must
have at least one trunk E_Port configured for all of or a subset of the VSANs defined on the
switches.
VSAN trunking eliminates the need to create dedicated ISL(s) for each VSAN. It reduces the
number of ISLs when the switches are configured with multiple VSANs. As the number of ISLs
between the switches decreases, the number of E_Ports used for the ISLs also reduces. By
eliminating needless ISLs, the utilization of the remaining ISLs increases. The complexity of
managing the FC SAN is also minimized with a reduced number of ISLs.
The figure on the slide shows a VSAN trunking configuration contrasted with a network
configuration without VSAN trunking. In both the cases, the switches have VSAN 10, VSAN 20,
and VSAN 30 configured. If VSAN trunking is not used, three ISLs are required to transfer traffic
between the three distinct VSANs. When trunking is configured, a single ISL is used to transfer all
VSAN traffic.

Copyright 2015 EMC Corporation. All rights reserved. ISM v3 Module 9: Fibre Channel (FC) SAN 43
 VSAN tagging is the process of adding or removing a marker or tag to the FC frames that contains
VSAN-specific information. Associated with VSAN trunking, it helps isolate FC frames from
multiple VSANs that travel through and share a trunk link. Whenever an FC frame enters an FC
switch, it is tagged with a VSAN header indicating the VSAN ID of the switch port (F_Port) before
sending the frame down to a trunk link. The receiving FC switch reads the tag and forwards the
frame to the destination port that corresponds to that VSAN ID. The tag is removed once the
frame leaves a trunk link to reach an N_Port.

Copyright 2015 EMC Corporation. All rights reserved. ISM v3 Module 9: Fibre Channel (FC) SAN 44
 This lesson covered N_Port ID virtualization (NPIV), N_Port virtualization (NPV), block-level
storage virtualization, and virtual SAN.

Copyright 2015 EMC Corporation. All rights reserved. ISM v3 Module 9: Fibre Channel (FC) SAN 45
 The Concepts in Practice section covers EMC Connectrix and EMC VPLEX.

Note:

For the latest information on EMC products, visit [Link].

Copyright 2015 EMC Corporation. All rights reserved. ISM v3 Module 9: Fibre Channel (FC) SAN 46
 EMC Connectrix family is a group of networked storage connectivity products. EMC offers the
following connectivity products under the Connectrix brand:

• Enterprise directors: They are ideal for large enterprise connectivity. They offer high port
density and high component redundancy. They are deployed in high-availability or large-scale
environments.

• Departmental switches: They are designed to meet workgroup-level, department-level, and

enterprise-level requirements. They provide high availability through features such as non-
disruptive software and port upgrade, and redundant and hot-swappable components.

• Multi-purpose switches: They support various protocols such as FC, iSCSI, FCIP, FCoE, and
FICON. They include FCoE switches, FCIP gateways, and iSCSI gateways. Multiprotocol
capabilities offer many benefits, including long-distance SAN extension, greater resource
sharing, and simplified management.

EMC VPLEX provides solution for block-level storage virtualization and data mobility both within
and across data centers. It forms a pool of distributed block storage resources and enables
creating virtual storage volumes from the pool. These virtual volumes are then allocated to the
compute systems. VPLEX provides non-disruptive data mobility among storage systems to
balance the application workload and to enable both local and remote data access. VPLEX also
provides the capability to mirror data of a virtual volume both within and across locations. It uses
a unique clustering architecture and advanced data caching techniques that enable multiple
compute systems located across two locations to access a single copy of data. VPLEX Virtual
Edition (VPLEX/VE) is deployed as a set of virtual appliances that implement VPLEX technology on
VMware ESXi infrastructure. VPLEX/VE stretches ESXi infrastructure over distance, allowing an
ESXi cluster to span across two physical sites.

Copyright 2015 EMC Corporation. All rights reserved. ISM v3 Module 9: Fibre Channel (FC) SAN 47
 This module covered third platform requirements for SAN and software-defined networking. It
also covered FC SAN components including network adapters, cables, and interconnecting
devices; FC connectivity options such as point-to-point, FC-AL, FC-SW; and fabric port types such
as N_Port, E_Port, F_Port, and G_Port. It included FC protocol stack and addressing, structure
and organization of FC data, fabric services, login types, and flow control. This module also
covered fabric topologies such as single-switch, mesh, and core-edge; link aggregation; different
types of zoning including WWN zoning, port zoning, and mixed zoning; port virtualization such as
NPIV and NPV; block-level storage virtualization; and virtual SAN.

This concludes the training.

Copyright 2015 EMC Corporation. All rights reserved. ISM v3 Module 9: Fibre Channel (FC) SAN 48